Courseiva

CCNA OSPF Questions

54 of 129 questions · Page 2/2 · OSPF topic · Answers revealed

76
MCQeasy

What is the default OSPF hello interval on a broadcast multi-access network (e.g., Ethernet)?

A.10 seconds
B.30 seconds
C.5 seconds
D.40 seconds
AnswerA

OSPF sends hello packets every 10 seconds on broadcast multi-access segments such as Ethernet, satisfying the default timer requirement. This interval lets routers detect neighbours quickly while avoiding excessive overhead. It differs from NBMA and point-to-multipoint networks, which default to 30 seconds.

Why this answer

On a broadcast multi-access network like Ethernet, OSPF defaults to a hello interval of 10 seconds. This is defined in RFC 2328 and is used to quickly detect neighbor failures while keeping control traffic overhead manageable. The corresponding dead interval is 40 seconds (4 times the hello interval).

Exam trap

Cisco often tests the distinction between hello and dead intervals, and candidates confuse the 40-second dead interval with the hello interval, or incorrectly recall the NBMA hello interval of 30 seconds.

How to eliminate wrong answers

Option B is wrong because 30 seconds is the default hello interval for OSPF on non-broadcast multi-access (NBMA) networks, not broadcast multi-access. Option C is wrong because 5 seconds is not a standard OSPF hello interval; it is sometimes used in tuned configurations but is not the default. Option D is wrong because 40 seconds is the default dead interval on broadcast networks, not the hello interval.

77
MCQmedium

A network engineer runs the following command on Router R9: R9# show ip ospf interface brief Interface PID Area IP Address/Mask Cost State Nbrs F/C Gi0/0 1 0 192.168.1.9/24 10 DR 2/2 Gi0/1 1 1 10.0.0.9/24 20 BDR 1/1 Lo0 1 0 9.9.9.9/32 1 LOOP 0/0 Based on this output, what can be concluded?

A.R9 is the Designated Router on the segment connected to Gi0/1.
B.R9 has two fully adjacent neighbors on Gi0/0.
C.The loopback interface Lo0 is advertised as a /24 network.
D.R9 is an Area Border Router.
AnswerB

The 'Nbrs F/C' column for Gi0/0, which stands for Fully adjacent neighbors / Count of all neighbors, displays 2/2. This means that R9 has exactly two neighbors on that interface, and both have reached the 'Full' state, indicating fully adjacent neighbors with synchronized link-state databases. Therefore, the statement that R9 has two fully adjacent neighbors on Gi0/0 is a factual conclusion directly supported by the output.

Why this answer

The output shows that on interface Gi0/0, R9 has a state of DR (Designated Router) and 2 fully adjacent neighbors (Nbrs F/C = 2/2). The '2/2' indicates 2 neighbors in a full state out of 2 total neighbors, meaning both neighbors have completed the OSPF adjacency process. Therefore, R9 has two fully adjacent neighbors on Gi0/0, making option B correct.

Exam trap

Cisco often tests the misinterpretation of the 'Nbrs F/C' field, where candidates confuse the total neighbor count with the number of fully adjacent neighbors, or assume that being in the DR state on one interface implies DR status on all interfaces.

How to eliminate wrong answers

Option A is wrong because on Gi0/1, R9 is in the BDR (Backup Designated Router) state, not DR; the DR on that segment would be another router. Option C is wrong because the loopback interface Lo0 is configured with a /32 mask (as shown by 9.9.9.9/32), and OSPF advertises it as a host route (/32) by default, not as a /24 network. Option D is wrong because R9 has interfaces in Area 0 and Area 1, but the output does not show any interface in a different area that would indicate it is an ABR; an ABR must have at least one interface in Area 0 and one in another non-backbone area, which is true here, but the output does not confirm that R9 is actually performing ABR functions (e.g., it could be a simple multi-area router without LSA type 3 generation), and the question asks what can be concluded from the output—being in two areas does not automatically mean it is an ABR without further evidence of route redistribution between areas.

78
MCQeasy

What is the default OSPF hello interval on an Ethernet link?

A.10 seconds
B.30 seconds
C.40 seconds
D.5 seconds
AnswerA

On Ethernet broadcast multi-access networks, OSPF's default hello interval is 10 seconds. This value is defined in RFC 2328 for broadcast and point-to-point interfaces, and the associated dead interval is 40 seconds (4 times the hello). The 10-second hello keeps neighbor adjacency establishment quick while maintaining a reasonable control-plane overhead.

Why this answer

The default OSPF hello interval on an Ethernet link is 10 seconds, as specified in RFC 2328. Ethernet is a broadcast multi-access network type, and OSPF uses a 10-second hello interval on such networks to maintain neighbor adjacencies and detect failures within the dead interval (default 40 seconds, or 4 times the hello interval).

Exam trap

Cisco often tests the confusion between the OSPF hello interval and dead interval, where candidates mistakenly select 40 seconds (the dead interval) instead of 10 seconds (the hello interval) on Ethernet links.

How to eliminate wrong answers

Option B (30 seconds) is wrong because 30 seconds is the default hello interval for OSPF on non-broadcast multi-access (NBMA) networks, such as Frame Relay, not on Ethernet. Option C (40 seconds) is wrong because 40 seconds is the default OSPF dead interval on Ethernet, not the hello interval; candidates often confuse the two. Option D (5 seconds) is wrong because 5 seconds is the default hello interval for OSPF on point-to-point and point-to-multipoint networks, not on Ethernet broadcast multi-access links.

79
MCQeasy

An enterprise network uses OSPF in the core and EIGRP in the campus distribution layer. The engineer needs to redistribute routes between the two protocols. Which design consideration is most important to prevent routing loops?

A.Set appropriate administrative distance values for redistributed routes.
B.Use route maps to filter all redistributed routes.
C.Enable OSPF on all EIGRP interfaces.
D.Use a single routing protocol throughout the network.
AnswerA

Setting administrative distance (AD) for redistributed routes is essential because AD determines the trustworthiness of routing sources. When routes are redistributed between OSPF and EIGRP, their default AD values may cause a redistributed route (e.g., an EIGRP external route with AD 170) to be preferred over the original protocol's internal route, leading to routing loops or suboptimal paths. By explicitly setting AD values, you ensure that routes from the original protocol are always preferred, maintaining loop-free and predictable routing behavior.

Why this answer

Setting appropriate administrative distance values for redistributed routes is crucial to prevent routing loops when redistributing between OSPF and EIGRP. By default, EIGRP has an administrative distance of 170 for external routes and 90 for internal routes, while OSPF uses 110. If redistributed routes are not assigned a higher administrative distance, a router might prefer a redistributed route over a directly learned route, creating a feedback loop where routes are re-injected into the original protocol.

Adjusting the administrative distance ensures that redistributed routes are less preferred than native routes, breaking the loop.

Exam trap

Cisco often tests the misconception that route filtering (option B) is the primary loop-prevention mechanism, but the real trap is that administrative distance must be adjusted to prevent the redistribution feedback loop, especially when multiple routers perform mutual redistribution.

How to eliminate wrong answers

Option B is wrong because using route maps to filter all redistributed routes is overly restrictive and can prevent necessary route propagation, but it does not directly address the root cause of routing loops, which is the preference for redistributed routes over native ones. Option C is wrong because enabling OSPF on all EIGRP interfaces would merge the two routing domains, defeating the purpose of redistribution and potentially causing instability, but it does not prevent loops in a multi-protocol environment. Option D is wrong because using a single routing protocol throughout the network is a valid design choice but is not a consideration for preventing loops during redistribution; the question specifically asks about redistributing between two protocols, so this option avoids the problem rather than solving it.

80
MCQhard

A network engineer executes the following command on Router R5: R5# show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 10.0.0.6 1 FULL/DR 00:00:35 192.168.1.6 GigabitEthernet0/0 10.0.0.7 1 FULL/BDR 00:00:32 192.168.1.7 GigabitEthernet0/0 10.0.0.8 1 2WAY/DROTHER 00:00:38 192.168.1.8 GigabitEthernet0/0 Based on this output, what can be concluded about the OSPF network?

A.The OSPF network type is point-to-point.
B.Router R5 is the DR on this segment.
C.The OSPF network type is broadcast.
D.All neighbors are in the FULL state.
AnswerC

The neighbor states FULL/DR, FULL/BDR, and 2WAY/DROTHER are only possible on OSPF network types that perform DR/BDR election, such as broadcast or NBMA. On a broadcast multiaccess network like Ethernet, OSPF elects a DR and BDR to reduce adjacencies, and DROTHER routers remain in 2WAY with each other. The router's output clearly shows a neighbor as the DR and another in the DROTHER state, confirming the network type is broadcast.

Why this answer

The output shows neighbors in states FULL/DR, FULL/BDR, and 2WAY/DROTHER, which are characteristic of a broadcast multiaccess network where a Designated Router (DR) and Backup Designated Router (BDR) are elected. The presence of a 2WAY/DROTHER state indicates that non-DR/BDR routers maintain a two-way adjacency without exchanging full LSDBs, which only occurs on broadcast or non-broadcast multiaccess (NBMA) networks. Since the network type is not point-to-point (which would show only FULL states) and the DR/BDR roles are present, the OSPF network type must be broadcast.

Exam trap

Cisco often tests the misconception that all OSPF neighbors must be in FULL state for proper operation, but on broadcast networks, DROTHER routers remain in 2WAY state with each other to reduce LSA flooding overhead.

How to eliminate wrong answers

Option A is wrong because a point-to-point network would show only FULL state neighbors with no DR/BDR election, and the output clearly shows DR/BDR roles. Option B is wrong because Router R5's own state is not shown in the output; the 'State' column reflects the neighbor's state relative to R5, and since R5 sees a DR and BDR but is not listed as DR itself, R5 is likely a DROTHER. Option D is wrong because the neighbor 10.0.0.8 is in the 2WAY/DROTHER state, not FULL, so not all neighbors are in FULL state.

81
MCQeasy

What is the default OSPF hello interval on an Ethernet link in Cisco IOS?

A.10 seconds
B.30 seconds
C.40 seconds
D.5 seconds
AnswerA

On OSPF broadcast multi-access networks such as Ethernet, the default hello interval is 10 seconds, and the associated dead interval is 40 seconds (four times the hello). This is the standard value defined in RFC 2328 for broadcast and point-to-point network types, ensuring timely neighbor discovery and liveness detection without excessive control-plane overhead. Because both routers must agree on the hello interval to form an adjacency, the Ethernet default of 10 seconds is the correct answer.

Why this answer

In Cisco IOS, the default OSPF hello interval for broadcast multi-access networks such as Ethernet is 10 seconds. This value is defined in RFC 2328 and is used to maintain neighbor adjacencies; if a hello is not received within the dead interval (default 40 seconds, or 4 times the hello interval), the neighbor is declared down.

Exam trap

Cisco often tests the default OSPF hello interval on Ethernet (10 seconds) versus the dead interval (40 seconds) or the hello interval on other network types (e.g., NBMA at 30 seconds), so candidates must memorize the exact per-network-type defaults.

How to eliminate wrong answers

Option B (30 seconds) is wrong because 30 seconds is the default hello interval for OSPF on non-broadcast multi-access (NBMA) networks like Frame Relay, not Ethernet. Option C (40 seconds) is wrong because 40 seconds is the default OSPF dead interval on Ethernet, not the hello interval. Option D (5 seconds) is wrong because 5 seconds is the default hello interval for OSPF on point-to-point links in some implementations, but not the default for Ethernet broadcast networks in Cisco IOS.

82
MCQhard

A network engineer issues the following command on Router R6: R6# debug ip ospf hello OSPF: Send hello to 224.0.0.5 via GigabitEthernet0/0 (192.168.1.6) OSPF: Rcv hello from 1.1.1.1, GigabitEthernet0/0, area 0.0.0.0 Neighbor state is 2WAY, options 0x2 OSPF: End of hello processing Based on this output, what can be concluded?

A.R6 has formed a full adjacency with neighbor 1.1.1.1.
B.The hello packet was sent to the DR/BDR multicast address 224.0.0.6.
C.R6 and 1.1.1.1 are neighbors, but a full adjacency may not yet be formed.
D.The OSPF network type is point-to-point.
AnswerC

The 2WAY state confirms that R6 and 1.1.1.1 have exchanged Hello packets that include each other's Router ID, making them OSPF neighbors. However, 2WAY is only a preliminary step; a full adjacency (FULL) requires an exchange of Database Description packets, Link-State Requests, and Link-State Updates to synchronize their OSPF link-state databases. Moreover, on broadcast multi-access networks, a router forms FULL adjacencies only with the DR/BDR, so two non-DR routers can remain in 2WAY without ever reaching FULL. Thus, being neighbors does not guarantee a full adjacency exists.

Why this answer

The debug output shows the neighbor state is 2WAY, which indicates that R6 has received a hello from 1.1.1.1 and bidirectional communication is established, but a full adjacency has not yet been formed. In OSPF, the 2WAY state is a prerequisite for advancing to the ExStart state and eventually to FULL, but on multiaccess networks, the router must also wait for the Designated Router (DR) and Backup Designated Router (BDR) election process to complete before proceeding. Therefore, option C correctly states that R6 and 1.1.1.1 are neighbors, but a full adjacency may not yet be formed.

Exam trap

Cisco often tests the distinction between the 2WAY and FULL states, and the trap here is that candidates mistakenly assume that receiving a hello packet means a full adjacency has been formed, ignoring the multi-step OSPF neighbor state machine and the role of DR/BDR elections on broadcast networks.

How to eliminate wrong answers

Option A is wrong because the neighbor state is 2WAY, not FULL; a full adjacency is only achieved after the database description (DBD), LSR, LSU, and LSAck exchanges in the ExStart, Exchange, Loading, and FULL states. Option B is wrong because the hello packet was sent to 224.0.0.5, which is the AllSPFRouters multicast address used for OSPF hello packets on broadcast and point-to-point networks, not the DR/BDR multicast address 224.0.0.6. Option D is wrong because the use of multicast address 224.0.0.5 and the presence of a 2WAY state (which implies a DR/BDR election process) strongly suggest a broadcast network type, not point-to-point; on a point-to-point link, neighbors typically transition directly to FULL without a 2WAY state.

83
Multi-Selecteasy

Which two statements about OSPF neighbor states are true? (Choose two.)

Select 2 answers
A.The 2-Way state indicates that both routers have seen their own router ID in the neighbor's hello packet.
B.The Full state indicates that the routers have synchronized their LSDBs and are fully adjacent.
C.In the ExStart state, routers exchange Database Description packets containing LSA headers.
D.In the Exchange state, routers send Link State Requests and receive Link State Updates.
E.The Down state is the final state when a neighbor is unreachable.
AnswersA, B

2-Way is declared once each router sees its own Router ID listed in the neighbour's Hello packet, proving two-way reachability. This bidirectional confirmation is the defining mechanism of the state, so the statement accurately describes when it is reached.

Why this answer

Option A is correct because the 2-Way state is reached when a router receives a Hello packet from a neighbor that contains its own Router ID in the neighbor list field, confirming bidirectional communication. Option B is correct because Full state means the two routers have successfully completed database synchronization, so their link-state databases (LSDBs) are identical and they are fully adjacent. Option C is incorrect because Database Description (DBD) packets with LSA headers are exchanged in the Exchange state, not the ExStart state; ExStart only negotiates the master/slave relationship and initial DBD sequence numbers.

Option D is incorrect because Link State Requests and Link State Updates are exchanged in the Loading state, not the Exchange state. Option E is incorrect because Down is the initial state, not the final state, when no Hello packets have been received from the neighbor.

Exam trap

The trap here is confusing the ExStart/Exchange/Loading states — candidates often mix up which packets (DBD, LSR, LSU) are exchanged in which state, and mistakenly think Down is a terminal state rather than the initial one.

84
MCQmedium

A network administrator is deploying Control Plane Policing (CoPP) on a Cisco IOS XE router that peers BGP with two ISPs. After applying a policer to the control plane, the BGP sessions tear down repeatedly while OSPF adjacencies stay stable. The administrator confirms CPU utilization is low. Which action should be taken to resolve the issue?

A.Apply the CoPP policy to the data plane interfaces using the service-policy input command.
B.Increase the CIR of the policer class matching BGP traffic and permit the BGP class in the control-plane service policy.
C.Disable CEF switching on the router so BGP packets are process-switched and bypass the policer.
D.Enable NetFlow on the WAN interfaces and export records to a collector for BGP traffic analysis.
AnswerB

BGP session teardown with low CPU indicates the policer is dropping BGP keepalives before they reach the control plane. Raising the committed information rate for the BGP class and explicitly permitting that class in the control-plane policy allows the protocol traffic to pass at the required rate, restoring adjacency stability without disabling CoPP for other traffic.

Why this answer

CoPP policies inspect and police traffic punted to the route processor. When a policer for a critical routing protocol is too restrictive, protocol hellos and keepalives are dropped, causing peering failures even though CPU load is low. Adjusting the policer rate and ensuring the protocol class is permitted restores the required control-plane traffic while retaining protection against abuse.

Exam trap

The trap here is assuming that low CPU utilization proves CoPP is working correctly, when in fact a too-strict policer silently discards essential routing protocol keepalives.

85
MCQhard

A network engineer is configuring a Cisco IOS router to support OSPFv3 for IPv6. The router is connected to two OSPFv3 areas: area 0 and area 1. The engineer wants to summarize the IPv6 routes from area 1 into area 0 using the prefix 2001:DB8:1::/48. Which command should be used on the area border router (ABR)?

A.area 1 range 2001:DB8:1::/48
B.summary-address 2001:DB8:1::/48
C.ipv6 ospf summary-prefix 2001:DB8:1::/48
D.area 0 range 2001:DB8:1::/48
AnswerA

This command configures inter-area route summarization for OSPFv3 on the ABR. The 'area 1 range' command tells the ABR to advertise a single summary route for the specified prefix into other areas. It must be configured under IPv6 router OSPF configuration mode. This is the correct way to summarize OSPFv3 routes between areas.

Why this answer

In OSPFv3, inter-area route summarization is configured on an ABR using the 'area <area-id> range <prefix>' command. The area ID specifies the source area whose routes are to be summarized. Here, routes from area 1 are summarized into area 0 using the prefix 2001:DB8:1::/48.

The other commands either do not exist, are for external summarization, or specify the wrong area.

Exam trap

The trap here is confusing inter-area summarization with external summarization, or using the wrong area ID in the command.

86
MCQmedium

A network engineer is configuring OSPF in a multi-area design. The engineer wants to reduce the amount of LSA flooding and the size of the LSDB in area 0. Which OSPF feature should be implemented on the ABR to achieve this goal?

A.Configure area 0 as a stub area.
B.Configure the ABR with an area filter-list to filter type 3 LSAs.
C.Configure OSPF database overflow protection.
D.Configure the ABR as an ASBR.
AnswerB

The area filter-list command on an ABR filters type 3 summary LSAs entering or leaving an area, directly and proactively reducing the number of LSAs in area 0's link-state database. Only type 3 LSAs that describe inter-area prefixes are affected, so selected routes are omitted from the ABR's summary advertisements without disrupting the backbone's transit role or intra-area operations. This is the only option that reduces LSDB size while maintaining correct OSPF design.

Why this answer

Configuring an area filter-list on the ABR allows the engineer to filter Type 3 summary LSAs entering or leaving area 0. This directly reduces LSA flooding and shrinks the LSDB in area 0 by preventing specific inter-area prefixes from being advertised into the backbone, without altering the area type or requiring additional redistribution.

Exam trap

The trap here is that candidates often assume area 0 can be made a stub area to reduce LSAs, but Cisco tests the fact that area 0 is a transit area and cannot be a stub, making the filter-list the correct tool for this specific goal.

How to eliminate wrong answers

Option A is wrong because area 0 cannot be configured as a stub area; OSPF requires area 0 to be a transit area and stub areas cannot have virtual links or ASBRs, making this configuration invalid. Option C is wrong because OSPF database overflow protection limits the total number of LSAs in the LSDB to prevent memory exhaustion, but it does not selectively reduce LSA flooding or the LSDB size in area 0 as requested. Option D is wrong because configuring the ABR as an ASBR would introduce external LSAs (Type 5) into the OSPF domain, increasing the LSDB size and flooding, which is the opposite of the goal.

87
MCQmedium

A network engineer is configuring Control Plane Policing (CoPP) on a Cisco IOS-XE router that also runs OSPF, BGP, and SSH management. The engineer needs to protect the control plane while ensuring that routing protocol traffic and management sessions are not disrupted. Which CoPP design approach best meets these requirements?

A.Configure a CoPP policy that only rate-limits ICMP and Telnet, leaving all other control plane traffic unclassified and unpolished.
B.Apply a single CoPP policy that classifies all control plane traffic into one class and rate-limits it to a conservative value.
C.Apply the CoPP policy to all data plane interfaces in the inbound direction, which will indirectly protect the control plane.
D.Create multiple granular classes (for example, routing protocols, management, and exception traffic) and apply class-specific policers, while ensuring control plane traffic is not dropped by the default class.
AnswerD

Granular classification lets the engineer allocate adequate bandwidth to OSPF, BGP, and SSH while policing less critical or malicious traffic more aggressively. The default class should be configured to not drop, or to drop only after all classified traffic is serviced, so that unclassified but legitimate control plane packets are not silently discarded and routing or management sessions remain stable.

Why this answer

CoPP protects the route processor by classifying and policing traffic destined to the control plane. Granular classes allow routing protocols and management traffic to receive enough bandwidth, while the default class should be configured not to drop so that legitimate unclassified traffic survives. This design balances protection with operational stability for OSPF, BGP, and SSH.

Exam trap

The trap here is assuming a single conservative CoPP policer is sufficient, when it actually throttles legitimate routing and management traffic along with attacks.

88
MCQhard

A network engineer is configuring a Cisco IOS router to authenticate OSPF neighbors using MD5. The engineer enters the following commands under the OSPF process: area 0 authentication message-digest, and under the interface: ip ospf message-digest-key 1 md5 Cisco123. However, the neighbor relationship does not form. What is the most likely cause?

A.The area authentication command must be configured on all routers in the area, but the interface command is optional.
B.The key ID must match on both routers, but the key string can be different.
C.The key ID and key string must match on both routers, and the area authentication command must be consistent.
D.The router must be reloaded for the MD5 key to take effect.
AnswerC

For OSPF MD5 authentication to succeed, both routers must have the same key ID, the same key string, and the same authentication type configured for the area or interface. The area authentication command enables MD5 for the area, and the interface command provides the key. If any of these parameters differ, the neighbor relationship will not form.

Why this answer

OSPF MD5 authentication requires consistent configuration on both neighbors: the same key ID, the same key string, and the same authentication mode (area or interface). The area authentication command enables MD5 for the area, and the interface command provides the key. If any of these differ, OSPF authentication fails, and the routers will not become adjacent.

Exam trap

The trap here is assuming that only the key string matters, when in fact the key ID and the area authentication mode must also match.

89
MCQmedium

A network engineer issues the following command on Router R8: R8# show ip ospf neighbor detail Neighbor 1.1.1.1, interface address 192.168.1.1 In the area 0 via interface GigabitEthernet0/0 Neighbor priority is 1, State is FULL, 6 state changes DR is 192.168.1.2, BDR is 192.168.1.1 Options is 0x42 (L LSR LSRR L LSR) Dead timer due in 00:00:34 Neighbor is up for 00:12:45 Index 1/1/1, retransmission queue length 0, number of retransmission 0 First 0x0(0)/0x0(0)/0x0(0) Next 0x0(0)/0x0(0)/0x0(0) Last retransmission scan length is 0, last retransmission scan time is 0 msec Based on this output, what can be concluded?

A.Router 1.1.1.1 is the Designated Router on this segment.
B.Router 1.1.1.1 is the Backup Designated Router.
C.The neighbor state is 2WAY.
D.The dead timer is 40 seconds.
AnswerB

The neighbor entry shows that 1.1.1.1 has an interface address of 192.168.1.1 and is in the FULL state. On the same line, the BDR field lists 192.168.1.1, which means this neighbor occupies the Backup Designated Router role for this multi-access segment. Because the BDR is the router that takes over if the DR fails, and the output explicitly assigns that address to this router, it is correct to conclude that 1.1.1.1 is the BDR.

Why this answer

The output shows 'BDR is 192.168.1.1', which is the interface address of neighbor 1.1.1.1. This directly indicates that router 1.1.1.1 is the Backup Designated Router on this segment. The neighbor state is FULL, confirming adjacency is fully established.

Exam trap

Cisco often tests the distinction between the neighbor's Router ID (1.1.1.1) and its interface address (192.168.1.1), causing candidates to confuse which router is the DR or BDR based on the Router ID rather than the explicit DR/BDR fields.

How to eliminate wrong answers

Option A is wrong because the DR is 192.168.1.2, not 1.1.1.1; the neighbor's interface address is 192.168.1.1, which is the BDR. Option C is wrong because the neighbor state is explicitly shown as 'FULL', not 2WAY; 2WAY is a lower state before adjacency formation. Option D is wrong because the dead timer is shown as 00:00:34, which is 34 seconds remaining, not 40 seconds; the default dead interval is 40 seconds, but the timer counts down.

90
MCQeasy

A network engineer runs the following command on Router R1: R1# show ip route 192.168.2.0 Routing entry for 192.168.2.0/24 Known via "ospf 1", distance 110, metric 20, type inter area Last update from 10.0.0.2 on GigabitEthernet0/0, 00:05:23 ago Routing Descriptor Blocks: * 10.0.0.2, via GigabitEthernet0/0, 00:05:23 ago Route metric is 20, traffic share count is 1 Based on this output, what can be concluded?

A.The route is an OSPF intra-area route
B.The route is an OSPF inter-area route
C.The route is an OSPF external route
D.The route is learned via EIGRP
AnswerB

The routing table line states 'Known via ospf 1' and includes the route tag 'type inter area', which is unambiguously how Cisco marks OSPF inter-area routes. These routes are propagated between areas via Type 3 summary LSAs, and the ABR advertises the prefix into the current area. This matches the 'inter area' classification exactly, making the route an OSPF inter-area route.

Why this answer

The output shows 'type inter area' and a metric of 20, which is the default OSPF metric for inter-area routes (type 3 LSAs). The administrative distance of 110 confirms OSPF as the routing protocol. Therefore, the route is an OSPF inter-area route, making option B correct.

Exam trap

Cisco often tests the distinction between OSPF route types by showing the 'type inter area' or 'type intra area' keyword in the show ip route output, and candidates may confuse the metric value (20) with external route metrics, forgetting that inter-area routes also use a default metric of 20 when no cost is explicitly configured.

How to eliminate wrong answers

Option A is wrong because the output explicitly states 'type inter area', not intra-area; intra-area routes would show 'type intra area' and typically have a lower metric. Option C is wrong because OSPF external routes (type 5 or 7 LSAs) would display 'type external' or 'type NSSA external' and often have a metric of 20 for E1/E2 routes, but the output clearly says 'inter area'. Option D is wrong because the administrative distance is 110 (OSPF default), not 90 or 170 (EIGRP default distances), and the output shows 'Known via ospf 1', not EIGRP.

91
MCQmedium

An engineer is designing an MPLS L3VPN service for a customer that requires overlapping IP addresses between two sites. The customer uses OSPF as the PE-CE protocol. The engineer configures VRFs on the PE routers and assigns unique route distinguishers (RDs) and route targets (RTs). However, the customer reports that routes from one site are not being installed in the other site's VRF. What is the most likely cause?

A.The route-target export on PE1 does not match the route-target import on PE2.
B.The overlapping IP addresses cause a routing loop in OSPF.
C.OSPF cannot carry overlapping prefixes in different VRFs.
D.The route distinguisher is not unique between the two sites.
AnswerA

In MPLS L3VPN, route targets (RTs) are BGP extended communities that control the redistribution of VPN routes between VRFs. The exporting PE attaches an export RT to a VPNv4 route; the importing PE only places that route into a VRF if the route's RT matches the VRF's import RT. In this scenario, PE1's export RT does not match PE2's import RT, so even though the VPNv4 route reaches PE2 via BGP, it is not installed in the VRF routing table, leaving the prefix unreachable.

Why this answer

In MPLS L3VPN, route targets (RTs) control the import and export of VPN routes between VRFs. For routes from one site to be installed in another site's VRF, the route-target export on the exporting PE must match the route-target import on the importing PE. If they do not match, the routes are not imported, even if route distinguishers (RDs) are unique and OSPF is properly configured.

Exam trap

The trap here is that candidates often confuse the role of route distinguishers (RDs) with route targets (RTs), thinking that unique RDs are sufficient for route exchange, when in fact RTs control the import/export policy between VRFs.

How to eliminate wrong answers

Option A is correct because mismatched route targets prevent route import between VRFs. Option B is wrong because overlapping IP addresses do not cause routing loops in OSPF; OSPF operates within each VRF independently, and overlapping addresses are handled by VRFs isolating routing tables. Option C is wrong because OSPF can carry overlapping prefixes in different VRFs; each VRF maintains its own OSPF process and routing table, so overlapping prefixes are not a problem.

Option D is wrong because route distinguishers (RDs) are used to make prefixes unique across the MPLS core, but they do not affect route import/export; mismatched RDs do not prevent route installation as long as RTs match.

92
MCQmedium

A network engineer is troubleshooting a routing loop between two OSPF areas. To verify the path that packets are taking, the engineer decides to use the Cisco IOS Embedded Event Manager (EEM) to generate a syslog message when the OSPF neighbor state changes. Which EEM applet configuration is required to trigger on the OSPF neighbor state change?

A.event tag ospf-neighbor timer watchdog time 60
B.event tag ospf-neighbor cli pattern "show ip ospf neighbor"
C.event tag ospf-neighbor syslog pattern "%OSPF-5-ADJCHG"
D.event tag ospf-neighbor snmp oid 1.3.6.1.2.1.14.10.1.6
AnswerC

This applet uses a syslog event detector that matches the OSPF adjacency change syslog message. When the router logs a %OSPF-5-ADJCHG message, the EEM applet triggers. This is a common method to monitor OSPF neighbor state changes without polling. The pattern must match the exact syslog text, and the tag is used to associate actions.

Why this answer

The correct configuration uses a syslog event detector to match the OSPF adjacency change message. When OSPF neighbor state changes, the router generates a %OSPF-5-ADJCHG syslog message. An EEM applet with a syslog event detector and the appropriate pattern will trigger actions based on that message.

This provides immediate, event-driven monitoring without polling. The other options either use inappropriate event detectors or incorrect syntax for this purpose.

Exam trap

The trap here is confusing the CLI event detector with the syslog event detector; the CLI detector triggers on command input, not on syslog messages.

93
MCQmedium

Consider the following configuration snippet on a Cisco IOS-XE router: interface GigabitEthernet0/1 ip address 10.1.1.1 255.255.255.0 ip pim sparse-mode ip igmp version 3 ! router ospf 1 network 10.1.1.0 0.0.0.255 area 0 ! What is the effect of this configuration?

A.The interface will participate in PIM sparse-mode and IGMPv3, but PIM sparse-mode requires an RP to be configured or learned.
B.The interface will operate in PIM dense-mode because no RP is configured.
C.IGMPv3 is incompatible with PIM sparse-mode and will be ignored.
D.The router will automatically use dense-mode because OSPF is enabled.
AnswerA

PIM sparse-mode is explicitly enabled on the interface with the ip pim sparse-mode command, which also activates IGMPv3 as the host membership protocol. In sparse mode, routers must send explicit join messages toward a rendezvous point (RP) to build multicast distribution trees. Without a configured or dynamically learned RP (e.g., via Auto-RP or BSR), the router cannot construct these shared trees, and multicast forwarding will fail. Therefore, the interface does participate in both PIM sparse-mode and IGMPv3, but the missing RP is a critical operational requirement.

Why this answer

The configuration explicitly enables PIM sparse-mode on the interface, which requires a rendezvous point (RP) to be known—either statically configured or dynamically learned via Auto-RP or BSR. The `ip igmp version 3` command enables IGMPv3, which is fully compatible with PIM sparse-mode and allows for source-specific multicast (SSM) support. OSPF is only used for unicast routing and does not affect PIM mode selection.

Exam trap

Cisco often tests the misconception that PIM sparse-mode automatically reverts to dense-mode when no RP is configured, but in reality, sparse-mode requires an explicit RP and will not forward traffic without one.

How to eliminate wrong answers

Option B is wrong because PIM sparse-mode does not fall back to dense-mode when no RP is configured; instead, the interface will simply not forward multicast traffic until an RP is learned. Option C is wrong because IGMPv3 is fully compatible with PIM sparse-mode and is actually required for SSM; it is not ignored. Option D is wrong because OSPF has no influence on PIM mode—PIM mode is determined solely by the `ip pim sparse-mode` or `ip pim dense-mode` command on the interface.

94
MCQhard

A network administrator is troubleshooting an issue where OSPF routes are not being learned from a neighbor. The administrator checks the OSPF configuration and sees that both routers are in the same area. The neighbor state is stuck in EXSTART. What is the most likely cause?

A.The router ID is the same on both routers.
B.The area ID is different.
C.The hello timer is set to 30 seconds on one router.
D.The interface MTU does not match.
AnswerD

An MTU mismatch is the classic cause of an OSPF neighbor being stuck in EXSTART; during the Database Description exchange, each router advertises its outgoing interface MTU in the DBD packet header. If one router's interface has a lower MTU, it discards DBD packets that declare a larger MTU, so the neighboring router never receives a valid acknowledgment and remains in EXSTART. Because OSPF does not initialize the DBD exchange until both MTUs are verified equal, the adjacency stalls at the point where the Master/Slave election occurs, exactly matching the reported symptom.

Why this answer

When OSPF neighbors are stuck in the EXSTART state, it typically indicates a problem with the Database Description (DBD) packet exchange process. The most common cause is an MTU mismatch between the interfaces, because OSPF will not proceed to the Exchange state if the DBD packet is larger than the interface MTU and gets silently dropped. This prevents the routers from agreeing on the master/slave relationship and exchanging link-state information.

Exam trap

The trap here is that candidates often confuse the EXSTART state with issues like hello/dead timer mismatches or area mismatches, which actually prevent the adjacency from reaching the 2-WAY state, not the EXSTART state.

How to eliminate wrong answers

Option A is wrong because duplicate router IDs would cause a neighbor state of DOWN or a conflict that prevents adjacency formation entirely, not a state stuck in EXSTART. Option B is wrong because if the area ID were different, the routers would not even reach the 2-WAY state, let alone EXSTART; they would remain in INIT or DOWN. Option C is wrong because mismatched hello timers would prevent the routers from reaching the 2-WAY state (they would stay in INIT), not cause them to get stuck in EXSTART.

95
Multi-Selecthard

A network engineer is deploying VXLAN with an EVPN control plane in a data center. The underlay is a routed Layer 3 network using OSPF. The engineer must ensure that the VXLAN data plane and EVPN control plane operate correctly. Which two statements about this deployment are true? (Choose two.)

Select 2 answers
A.EVPN uses BGP as its control plane to distribute MAC and IP address reachability information among VTEPs.
B.The VXLAN Tunnel Endpoint (VTEP) must have a unique IP address in the underlay, and this address is used as the source for VXLAN encapsulated traffic.
C.EVPN requires the underlay to be a Layer 2 network so that BGP peering can be established without routing.
D.The VTEP must be configured with the same IP address on all leaf switches to allow anycast tunneling.
E.VXLAN requires the underlay network to run a multicast routing protocol such as PIM to replicate broadcast, unknown unicast, and multicast traffic.
AnswersA, B

EVPN is a BGP address family (L2VPN EVPN) that carries MAC and IP reachability information. VTEPs peer with each other or with route reflectors using MP-BGP and advertise EVPN routes. This replaces flood-and-learn for MAC learning and provides control-plane learning, making the statement correct for an EVPN deployment.

Why this answer

In a VXLAN-EVPN deployment, each VTEP needs a unique underlay IP address used as the source for encapsulated traffic, and EVPN relies on MP-BGP to distribute MAC and IP reachability. Multicast is optional and typically replaced by ingress replication, anycast VTEP is a design choice, and the underlay must be Layer 3 for scalability. These two statements accurately describe the core requirements.

Exam trap

The trap here is assuming VXLAN always requires multicast in the underlay, which is only true for flood-and-learn without a control plane.

96
MCQmedium

Consider the following OSPF configuration on router R2: interface GigabitEthernet0/0 ip address 192.168.1.2 255.255.255.0 ip ospf 1 area 0 ip ospf hello-interval 5 ! router ospf 1 router-id 2.2.2.2 network 192.168.1.0 0.0.0.255 area 0 Which statement is true about this configuration?

A.The OSPF dead interval is automatically set to 20 seconds.
B.The OSPF dead interval remains at the default of 40 seconds.
C.This configuration will cause OSPF to use MD5 authentication.
D.The OSPF network type changes to point-to-point.
AnswerA

When you configure 'ip ospf hello-interval 5' on an interface, Cisco IOS automatically recalculates the OSPF dead interval to four times the hello interval, producing a dead interval of 20 seconds (4 × 5 = 20). This automatic adjustment preserves the default 4-to-1 ratio, ensuring that neighbor hold-down timing remains consistent with the hello interval. To achieve a different dead interval, you would need to explicitly configure 'ip ospf dead-interval'.

Why this answer

The OSPF dead interval is automatically set to four times the hello interval when the hello interval is manually configured. By default, OSPF uses a hello interval of 10 seconds and a dead interval of 40 seconds on broadcast networks. However, when you explicitly set the hello interval to 5 seconds using the 'ip ospf hello-interval 5' command, the router automatically adjusts the dead interval to 20 seconds (4 × 5 seconds) to maintain the standard ratio, unless the dead interval is also manually configured.

Exam trap

Cisco often tests the automatic relationship between the OSPF hello and dead intervals, and the trap here is that candidates assume the dead interval remains at the default value (40 seconds) even after changing the hello interval, rather than understanding it scales proportionally to 4× the new hello interval.

How to eliminate wrong answers

Option B is wrong because the OSPF dead interval does not remain at the default of 40 seconds; it is automatically recalculated to 20 seconds when the hello interval is changed to 5 seconds. Option C is wrong because the configuration shown does not include any authentication commands such as 'ip ospf authentication message-digest' or 'ip ospf message-digest-key', so MD5 authentication is not enabled. Option D is wrong because the network type remains as the default broadcast (multi-access) for GigabitEthernet interfaces; changing the network type to point-to-point requires the explicit command 'ip ospf network point-to-point'.

97
Multi-Selecthard

A network engineer is configuring a new Cisco IOS router for OSPFv2 in a multi-area OSPF domain. The router will be an Area Border Router (ABR) connecting Area 0 and Area 10. The engineer must ensure that the router correctly summarizes routes from Area 10 into Area 0 and that it does not become a designated router (DR) on any broadcast network. Which two configuration steps are required to meet these requirements? (Choose two.)

Select 2 answers
A.Set the OSPF interface priority to 0 on all interfaces that participate in OSPF.
B.Configure the router with the 'area 10 stub' command under the OSPF routing process.
C.Configure the router with the 'auto-cost reference-bandwidth 100000' command under the OSPF routing process.
D.Configure the router with the 'area 10 range 10.10.0.0 255.255.0.0' command under the OSPF routing process.
E.Configure the router with the 'passive-interface default' command under the OSPF routing process.
AnswersA, D

Setting the OSPF interface priority to 0 prevents the router from being elected as a designated router (DR) or backup designated router (BDR) on broadcast networks. This meets the requirement that the router does not become a DR. The priority is configured per interface with the 'ip ospf priority 0' command under the interface configuration.

Why this answer

To summarize routes from Area 10 into Area 0, the ABR must use the 'area 10 range' command. To prevent the router from becoming a DR, the OSPF interface priority must be set to 0 on all participating interfaces. These two steps directly satisfy the requirements.

The other options either configure stub areas, alter cost calculations, or suppress OSPF on interfaces, none of which meet the stated goals.

Exam trap

The trap here is assuming that configuring an area as stub or changing the reference bandwidth will influence summarization or DR election, when these are unrelated OSPF features.

98
MCQmedium

A network engineer is deploying Control Plane Policing (CoPP) on a Cisco IOS XE router that runs BGP, OSPF, and SSH management. The engineer applies a CoPP policy-map to the control plane with a class that matches BGP traffic and sets police rate 8000 conform-action transmit exceed-action drop. After applying the policy, BGP sessions intermittently flap during route convergence. Which action should the engineer take to resolve the issue while maintaining control plane protection?

A.Apply the CoPP policy to all router interfaces as an input service policy instead of to the control plane.
B.Remove the CoPP policy from the control plane interface and rely on interface ACLs instead.
C.Increase the police rate for the BGP class or change the exceed-action to transmit, after verifying the offered rate.
D.Change the CoPP policy to use priority queuing instead of policing for the BGP class.
AnswerC

The intermittent BGP flaps during convergence indicate that legitimate BGP control traffic is exceeding the 8,000 pps police rate and being dropped by the exceed-action. Increasing the police rate or changing the exceed-action to transmit for the BGP class restores session stability while still policing other control plane traffic. Verification of the offered rate is essential to size the policer correctly.

Why this answer

BGP session flapping immediately after applying a policer that drops exceeded traffic points to legitimate BGP control packets being dropped because the configured rate is too low for convergence bursts. The correct remediation is to right-size the policer for the BGP class, either by raising the rate or by permitting excess traffic, after confirming the actual offered rate from the control plane.

Exam trap

The trap here is assuming that any control plane drops must be caused by an attack rather than by an undersized policer that drops legitimate routing protocol traffic.

99
MCQmedium

Given the following configuration on a Cisco IOS-XE device: router ospf 1 network 10.0.0.0 0.255.255.255 area 0 ! interface GigabitEthernet0/0 ip address 10.1.1.1 255.255.255.0 ip ospf cost 10 ! interface GigabitEthernet0/1 ip address 10.2.2.1 255.255.255.0 ! Which statement is true about OSPF operation?

A.Both interfaces will have an OSPF cost of 10.
B.GigabitEthernet0/0 will have an OSPF cost of 10, and GigabitEthernet0/1 will have a default cost based on its bandwidth.
C.Both interfaces will have the same OSPF cost because they are in the same area.
D.OSPF will not run on either interface because the network command uses a wildcard mask of 0.255.255.255.
AnswerB

The interface-level ip ospf cost 10 overrides the reference-bandwidth calculation on GigabitEthernet0/0, fixing its cost at 10. GigabitEthernet0/1 has no explicit cost, so IOS-XE derives the default from its bandwidth. Both interfaces fall within network 10.0.0.0 0.255.255.255 area 0.

Why this answer

The ip ospf cost 10 command is applied only to GigabitEthernet0/0, explicitly setting its OSPF cost to 10. GigabitEthernet0/1 does not have a cost configured, so OSPF will use the default cost calculated from the interface's bandwidth (reference bandwidth divided by interface bandwidth). Therefore, GigabitEthernet0/0 has cost 10, and GigabitEthernet0/1 has the default cost.

Exam trap

The trap here is assuming that a cost configured on one interface applies to all interfaces in the same area, or misunderstanding the wildcard mask in the network command.

How to eliminate wrong answers

Option A is wrong because the cost is configured only on GigabitEthernet0/0; GigabitEthernet0/1 does not inherit that cost. Option C is wrong because OSPF cost is per-interface and not determined by the area; interfaces in the same area can have different costs. Option D is wrong because the network command with wildcard 0.255.255.255 matches any interface with an IP address in the 10.0.0.0/8 range, which includes both 10.1.1.1 and 10.2.2.1, so OSPF will run on both interfaces.

100
MCQhard

A network engineer is configuring a Cisco IOS router to authenticate OSPFv2 neighbors using MD5. The engineer wants to ensure that only routers with the correct key can form adjacencies, and that the key is not sent in clear text. Which command sequence correctly enables MD5 authentication on an interface?

A.ip ospf authentication-key <key> and ip ospf authentication
B.ip ospf authentication message-digest and ip ospf message-digest-key 1 md5 <key>
C.area 0 authentication message-digest and ip ospf message-digest-key 1 md5 <key>
D.ip ospf authentication null and ip ospf message-digest-key 1 md5 <key>
AnswerB

The interface-level command ip ospf authentication message-digest enables MD5 authentication for OSPF on that interface. The ip ospf message-digest-key command defines the key ID and MD5 key. Together, they satisfy the requirement to authenticate neighbors using MD5 without sending the key in clear text.

Why this answer

To enable MD5 authentication on a specific OSPF interface, you use the interface command ip ospf authentication message-digest and then define the key with ip ospf message-digest-key. This ensures that OSPF packets are authenticated with MD5 and the key is not transmitted in clear text, meeting the scenario's security requirement.

Exam trap

The trap here is confusing plaintext authentication with MD5, or using area-wide authentication when interface-level is required, which can leave other interfaces unprotected or misconfigured.

101
Multi-Selecthard

Which three statements about OSPF area types are correct? (Choose three.)

Select 3 answers
A.A stub area blocks Type 5 AS External LSAs but allows Type 3 Summary LSAs and a default route.
B.A totally stubby area blocks both Type 5 and Type 3 LSAs, injecting only a default route into the area.
C.A not-so-stubby-area (NSSA) allows Type 5 LSAs to be imported from external networks.
D.A standard area can contain Type 1, 2, 3, 4, and 5 LSAs.
E.A totally NSSA blocks Type 3 LSAs but allows Type 5 LSAs from external sources.
AnswersA, B, D

Stub areas block Type 5 AS External LSAs at the ABR, preventing external flooding, while Type 3 Summary LSAs still enter and the ABR injects a default route. This matches the stated stub behaviour exactly.

Why this answer

Option A is correct because a stub area, configured with the area stub command, blocks Type 5 AS External LSAs at the ABR while still permitting Type 3 Summary LSAs, and the ABR injects a default route (Type 3 LSA 0.0.0.0) so internal routers can reach external destinations. Option B is correct because a totally stubby area (area stub no-summary) blocks both Type 5 AS External LSAs and Type 3 Summary LSAs, leaving only a single default route injected by the ABR plus intra-area Type 1 and 2 LSAs. Option D is correct because a standard OSPF area carries Type 1 Router LSAs, Type 2 Network LSAs, Type 3 Summary LSAs, Type 4 ASBR Summary LSAs, and Type 5 AS External LSAs.

Option C is incorrect because an NSSA does not import Type 5 LSAs; it uses Type 7 LSAs for external routes originated inside the area, which the ABR translates to Type 5 when flooding into the backbone. Option E is incorrect because a totally NSSA blocks Type 3 Summary LSAs (except the default route) and does not allow Type 5 LSAs; external routes inside it are carried as Type 7 LSAs.

Exam trap

The trap here is confusing the LSA types blocked by stub, totally stubby, NSSA, and totally NSSA areas—especially the role of Type 7 LSAs in NSSAs and the fact that totally stubby areas block Type 3 LSAs while stub areas do not.

102
MCQmedium

interface GigabitEthernet0/1 ip address 10.1.1.1 255.255.255.0 mpls ip mpls label protocol ldp ! router ospf 1 network 10.1.1.0 0.0.0.255 area 0 ! router ldp interface GigabitEthernet0/1 ! What is the effect of this configuration?

A.MPLS forwarding is enabled on GigabitEthernet0/1, and LDP will distribute labels for all routes in the routing table.
B.Only OSPF routes are labeled; static routes are excluded from LDP label distribution.
C.The 'mpls label protocol ldp' command is redundant because LDP is the default.
D.The configuration will fail because 'router ldp' requires an LDP router-id to be set.
AnswerA

The `mpls ip` command on GigabitEthernet0/1 enables MPLS frame-mode switching on that interface, and because `mpls label protocol ldp` is set, LDP runs on that interface. By default, LDP advertises a label for every IPv4 prefix in the routing table, regardless of whether the route was learned via OSPF, configured as static, or directly connected. Therefore, the statement that all routing-table routes receive labels is correct.

Why this answer

The `mpls ip` command under the interface enables MPLS forwarding, and the `router ldp` configuration with the interface specified activates LDP on that interface. LDP will then distribute labels for all routes in the routing table (including OSPF, static, connected, etc.) by default, as LDP does not filter based on routing protocol. The `mpls label protocol ldp` command is indeed redundant since LDP is the default label distribution protocol in Cisco IOS, but it does not break the configuration.

Exam trap

Cisco often tests the misconception that LDP only labels OSPF or IGP routes, when in fact LDP distributes labels for all routes in the routing table by default, including static and connected routes.

How to eliminate wrong answers

Option B is wrong because LDP distributes labels for all routes in the routing table, not just OSPF routes; there is no implicit filtering by routing protocol. Option C is wrong because while `mpls label protocol ldp` is redundant (LDP is the default), the configuration still works and the statement 'redundant' does not make the option correct as the question asks for the effect, not a critique of redundancy. Option D is wrong because `router ldp` does not require an explicit LDP router-id to be set; if not configured, the router will use the highest loopback IP or the highest interface IP as the LDP router-id automatically.

103
MCQmedium

A network engineer runs the following command on Router R7: R7# show ip ospf neighbor vrf CUSTOMER-E Neighbor ID Pri State Dead Time Address Interface 10.0.0.8 1 FULL/DR 00:00:35 10.0.1.2 GigabitEthernet0/0.500 10.0.0.9 1 FULL/BDR 00:00:31 10.0.2.2 GigabitEthernet0/0.600 Based on this output, what can be concluded?

A.OSPF is not configured for VRF CUSTOMER-E
B.There is only one OSPF neighbor in VRF CUSTOMER-E
C.OSPF is operating within VRF CUSTOMER-E with two neighbors
D.The DR is 10.0.0.9
AnswerC

Correct. The OSPF process is bound to VRF CUSTOMER-E, and its neighbor table shows two fully established adjacencies (state FULL/DR and FULL/BDR), confirming active link-state routing within the VRF. This is consistent with having at least two OSPF routers sharing a common segment, and the neighbor states indicate that database synchronization is complete.

Why this answer

The command `show ip ospf neighbor vrf CUSTOMER-E` explicitly queries OSPF neighbors within the VRF named CUSTOMER-E. The output shows two neighbors (10.0.0.8 and 10.0.0.9) with states FULL/DR and FULL/BDR, confirming that OSPF is actively operating inside that VRF. Therefore, option C is correct because it accurately states that OSPF is operating within VRF CUSTOMER-E with two neighbors.

Exam trap

Cisco often tests the misconception that the DR is always the neighbor with the highest IP address or the first listed, but the DR is explicitly indicated by the state field (FULL/DR), not by the Neighbor ID or IP address.

How to eliminate wrong answers

Option A is wrong because the command successfully returned neighbor details, which would not happen if OSPF were not configured for VRF CUSTOMER-E; a missing OSPF configuration under the VRF would produce an empty output or an error. Option B is wrong because the output clearly lists two neighbors (10.0.0.8 and 10.0.0.9), not one. Option D is wrong because the DR (Designated Router) is identified by the neighbor with state FULL/DR, which is 10.0.0.8, not 10.0.0.9 (the BDR).

104
MCQhard

A network engineer is developing a Python script to configure OSPF on a Cisco IOS XE device using the NETCONF protocol. The script establishes an SSH session and sends a <edit-config> RPC with the target datastore set to 'running'. The configuration is applied successfully, but after a device reload, the OSPF configuration is missing. The engineer verifies that the <edit-config> operation included the 'default-operation' parameter set to 'merge'. What is the most likely reason for the configuration loss?

A.The <edit-config> operation was applied to the 'candidate' datastore instead of the 'running' datastore, and the candidate was not committed.
B.The 'default-operation' parameter should have been set to 'replace' instead of 'merge' to ensure the configuration is saved to NVRAM.
C.The NETCONF session was not closed properly, causing the device to roll back the configuration upon session termination.
D.The NETCONF <edit-config> operation modifies the running configuration but does not automatically save it to the startup configuration; a separate <copy-config> or <commit> to startup is required.
AnswerD

NETCONF <edit-config> on Cisco IOS XE modifies the running configuration. To persist changes across a reload, the running configuration must be copied to the startup configuration. This can be done with a <copy-config> RPC targeting the 'startup' datastore or by using the 'copy running-config startup-config' command. Without this step, the configuration is lost on reload, which matches the scenario.

Why this answer

NETCONF <edit-config> operations on Cisco IOS XE modify the running configuration. To persist changes across a reload, the running configuration must be explicitly saved to the startup configuration using a <copy-config> RPC or equivalent. The scenario describes a classic case where the configuration is applied but not saved, leading to loss after reload.

The other options incorrectly attribute the loss to datastore targeting, merge behavior, or session handling.

Exam trap

The trap here is assuming that NETCONF automatically saves changes to startup, when it only modifies the running configuration.

105
MCQmedium

A network engineer is deploying a new branch office with a Cisco Catalyst 9300 switch. The switch must participate in the corporate OSPF domain but must not become a designated router (DR) or backup designated router (BDR) on any broadcast segment. Which configuration should the engineer apply to the switch's OSPF interface?

A.ip ospf priority 0
B.ip ospf network point-to-point
C.ip ospf database-filter all out
D.ip ospf cost 65535
AnswerA

Setting the OSPF interface priority to 0 makes the router ineligible to become DR or BDR on that broadcast segment. The priority value is carried in Hello packets and used in the DR election; a priority of 0 explicitly excludes the interface from the election, ensuring the switch remains a DROTHER and only forms adjacencies with the DR and BDR.

Why this answer

The OSPF interface priority determines which routers are eligible to become DR or BDR on a broadcast or non-broadcast multi-access segment. A priority of 0 makes the router ineligible for these roles, so it will remain a DROTHER regardless of its router ID. This is the correct way to ensure the switch never becomes DR or BDR while still participating in OSPF.

Exam trap

The trap here is assuming that any OSPF interface setting that alters adjacency behavior, such as changing the network type, will also prevent DR/BDR election without side effects.

106
MCQmedium

A network engineer is deploying a VXLAN EVPN fabric. The underlay is a routed Layer 3 network using OSPF. Hosts in the same subnet are attached to leaf switches that are not directly connected. The engineer must ensure that the fabric provides optimal forwarding for East-West traffic without tromboning through a centralized gateway. Which VXLAN component should be configured to accomplish this?

A.Anycast distributed gateway with the same MAC and IP on all leaf switches
B.OSPF area 0 with stub areas on all leaf switches to reduce LSAs
C.Static VXLAN tunnel endpoints mapped to each leaf switch's loopback address
D.VXLAN Network Identifier (VNI) mapping to a single centralized gateway
AnswerA

An anycast distributed gateway configures the same gateway IP and MAC on every leaf switch, so each leaf can route traffic locally for its directly attached hosts. This avoids sending traffic to a centralized gateway and prevents suboptimal tromboning. It is the standard VXLAN EVPN design for optimal East-West forwarding.

Why this answer

An anycast distributed gateway places the same gateway IP and MAC on every leaf switch, allowing each leaf to route traffic for its local hosts. This eliminates the need to send traffic to a centralized gateway, providing optimal East-West forwarding. It is a key feature of VXLAN EVPN fabrics for efficient inter-subnet routing.

Exam trap

The trap here is assuming that any gateway configuration will automatically optimize East-West traffic, when in fact only a distributed anycast gateway avoids tromboning.

107
MCQmedium

Examine the following configuration for a Cisco IOS-XE device: interface GigabitEthernet0/0 ip address 10.0.0.1 255.255.255.252 ipv6 address 2001:db8::1/64 ipv6 ospf 1 area 0 ! interface GigabitEthernet0/1 ip address 192.168.1.1 255.255.255.0 ipv6 address 2001:db8:1::1/64 ipv6 ospf 1 area 0 ! ipv6 router ospf 1 router-id 2.2.2.2 Which statement is true about OSPFv3 operation?

A.OSPFv3 will form adjacencies over both interfaces using the configured IPv6 addresses.
B.OSPFv3 will form adjacencies over both interfaces using link-local addresses.
C.OSPFv3 will only run on GigabitEthernet0/0 because the router-id is not configured for GigabitEthernet0/1.
D.OSPFv3 requires an explicit network command under the OSPFv3 process to enable on interfaces.
AnswerB

OSPFv3 runs per-link over IPv6 and forms adjacencies using link-local addresses (fe80::/10), which are automatically generated on each interface. The configured global addresses are irrelevant to neighbour discovery, so adjacencies establish on both GigabitEthernet0/0 and GigabitEthernet0/1.

Why this answer

OSPFv3 forms adjacencies using IPv6 link-local addresses (fe80::/10), not the global unicast addresses configured on the interfaces. The `ipv6 ospf 1 area 0` command enables OSPFv3 on the interface, and the router automatically uses the link-local address as the source for hello packets. The global IPv6 addresses (2001:db8::1/64 and 2001:db8:1::1/64) are used for reachability but not for neighbor establishment.

Exam trap

The trap here is assuming OSPFv3 uses global IPv6 addresses for adjacencies like OSPFv2 uses IPv4 addresses; candidates often forget that OSPFv3 relies on link-local addresses for neighbor formation.

How to eliminate wrong answers

Option A is wrong because OSPFv3 does not use global IPv6 addresses for adjacency formation; it uses link-local addresses. Option C is wrong because the router-id is configured globally under the OSPFv3 process (router-id 2.2.2.2), and OSPFv3 does not require per-interface router-ids; adjacencies can form on both interfaces. Option D is wrong because OSPFv3 does not use the network command; instead, it is enabled per-interface using the `ipv6 ospf <process-id> area <area-id>` interface command.

108
MCQmedium

Examine the following configuration snippet: interface GigabitEthernet0/1 ip address 192.168.1.1 255.255.255.0 ip ospf network point-to-point ip ospf hello-interval 10 ip ospf dead-interval 40 ! router ospf 1 network 192.168.1.0 0.0.0.255 area 0 What is the effect of this configuration?

A.OSPF adjacency will form with a neighbor using hello/dead intervals of 10/40 seconds.
B.OSPF adjacency will not form because the hello interval is too low for point-to-point.
C.The network command under router ospf will be ignored because the interface has an explicit network type.
D.OSPF will use the default broadcast network type because the point-to-point keyword is misspelled.
AnswerA

This is correct because the interface has been explicitly configured as point-to-point, which uses a default hello interval of 10 seconds and a dead interval of 40 seconds on Cisco IOS. These timers match the neighbor's timers, so the two routers will form a full adjacency. Additionally, the point-to-point network type suppresses DR/BDR election, making adjacency establishment straightforward and deterministic.

Why this answer

The configuration sets the OSPF network type to point-to-point on the interface, which allows OSPF to form an adjacency with a neighbor using the configured hello interval of 10 seconds and dead interval of 40 seconds. These intervals are valid for point-to-point networks, and the network command under router ospf correctly enables OSPF on the interface. Therefore, an adjacency will form as long as the neighbor's intervals match.

Exam trap

Cisco often tests the misconception that the network command is ignored when an explicit ip ospf network type is configured, but in reality both work together—the network command enables OSPF on the interface, and the ip ospf network command only changes the OSPF network type.

How to eliminate wrong answers

Option B is wrong because a hello interval of 10 seconds is not too low for point-to-point; the default hello interval for point-to-point is 10 seconds, and it can be set lower (e.g., 1 second) without preventing adjacency formation as long as the neighbor matches. Option C is wrong because the network command under router ospf is not ignored; it is still used to determine which interfaces participate in OSPF, and the explicit network type on the interface only overrides the default network type, not the network command. Option D is wrong because the keyword 'point-to-point' is correctly spelled in the configuration snippet, and OSPF will use the point-to-point network type, not the default broadcast type.

109
Drag & Dropmedium

Drag and drop the steps of OSPFv3 IPv6 neighbor adjacency formation into the correct order, from first to last.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5

Why this order

OSPFv3 neighbor formation follows the same state machine as OSPFv2: Down, Init, 2-Way, ExStart, Exchange, Loading, Full. The steps reflect the key actions at each state.

110
MCQhard

A network engineer is implementing Control Plane Policing (CoPP) on a Cisco IOS XE router to protect against control plane overload. The router has management traffic (SSH, SNMP) and routing protocol traffic (OSPF, BGP). After applying the CoPP policy, the engineer notices that OSPF adjacencies are flapping. Which action should the engineer take to resolve this issue while maintaining control plane protection?

A.Increase the rate limit for the OSPF class in the CoPP policy.
B.Configure OSPF to use a different DSCP value so it matches a higher-priority class in the CoPP policy.
C.Remove the CoPP policy from the control plane and reapply it after OSPF stabilizes.
D.Apply the CoPP policy only to the management plane interface instead of the control plane.
AnswerA

OSPF adjacency flapping indicates that OSPF hello packets are being dropped due to the policer rate being too low. Increasing the rate limit for the OSPF class allows legitimate OSPF control traffic to pass while still protecting the control plane from excessive traffic. This is the correct action because it directly addresses the dropped OSPF packets without removing protection entirely.

Why this answer

OSPF adjacency flapping after CoPP deployment indicates that OSPF hello packets are being dropped by the policer. The CoPP policy likely has a rate limit for OSPF that is too low for the network's requirements. Increasing the rate limit for the OSPF class allows OSPF traffic to pass while still enforcing a policer to protect against excess traffic.

This maintains control plane protection and resolves the flapping.

Exam trap

The trap here is assuming that any CoPP issue requires removing the policy, when in fact tuning the rate limits for specific classes is the correct approach to balance protection and protocol operation.

111
Matchingmedium

Drag and drop each OSPF router role on the left to its matching function on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Generates Type 2 Network LSA and maintains full adjacencies with all routers on the segment

Becomes DR if the current DR fails; also maintains full adjacencies

Forms adjacencies only with DR and BDR; does not form full adjacencies with other DROTHERs

Redistributes routes from other routing protocols into OSPF

Connects two or more OSPF areas and advertises inter-area routes

Why these pairings

DR (Designated Router) generates Network LSAs and manages adjacencies on multi-access networks; BDR (Backup DR) takes over if the DR fails; DROTHER routers form full adjacencies only with DR and BDR; ASBR redistributes routes from other protocols; ABR connects multiple areas.

112
MCQeasy

A network engineer is troubleshooting an automated configuration change that caused a routing loop. The change was pushed via an Ansible playbook that modified OSPF cost values on multiple routers simultaneously. What is the most likely reason for the loop?

A.OSPF does not support changing costs on multiple routers at the same time
B.OSPF uses hop count as a metric, and the changes caused a count-to-infinity issue
C.The changes were applied simultaneously without allowing OSPF to converge between updates
D.The OSPF cost values were changed to non-standard values that OSPF cannot process
AnswerC

When OSPF cost changes are deployed simultaneously across multiple routers without a convergence interval, each router temporarily holds a different version of the link-state database (LSDB). This inconsistency causes the Shortest Path First (SPF) calculations on different routers to produce divergent, potentially looping paths until LSAs are fully flooded and SPF re-runs on all nodes. The correct practice is to stage changes incrementally, allowing each LSA to propagate and the SPF recalculation to complete before the next cost modification is applied.

Why this answer

Applying OSPF cost changes simultaneously on multiple routers without allowing convergence between updates can cause transient routing loops. OSPF relies on the SPF algorithm to calculate loop-free paths based on consistent link-state databases across the network. When costs are changed on multiple routers at once, some routers may have outdated LSAs, leading to inconsistent forwarding tables and temporary loops until all routers reconverge.

Exam trap

Cisco often tests the misconception that OSPF can handle simultaneous changes without issue, but the trap here is that candidates overlook the need for convergence between updates, confusing protocol capability with operational best practices.

How to eliminate wrong answers

Option A is wrong because OSPF fully supports changing costs on multiple routers simultaneously; the issue is not a protocol limitation but the lack of convergence between updates. Option B is wrong because OSPF uses cost (based on bandwidth) as its metric, not hop count; hop count is used by RIP, and count-to-infinity is a RIP-specific problem. Option D is wrong because OSPF can process any positive integer cost value (1 to 65535) as defined in RFC 2328; non-standard values are not a cause of loops.

113
MCQmedium

A network engineer is deploying a Cisco Nexus 9000 leaf switch in a VXLAN EVPN fabric. The underlay uses OSPF for loopback reachability, and the engineer must now enable the control plane that carries MAC and IP address reachability information for the overlay. Which technology must be enabled on the leaf switch to distribute this overlay reachability information?

A.LISP with a Map-Server and Map-Resolver
B.OSPFv3 with the IPv6 unicast address family
C.MP-BGP with the Layer 2 EVPN address family
D.PIM sparse mode with an Anycast-RP
AnswerC

EVPN uses MP-BGP with the L2VPN EVPN address family to advertise MAC addresses, IP-to-MAC bindings, and VTEP reachability in a VXLAN fabric. Enabling this address family in the leaf's BGP configuration lets the switch exchange Type 2 and Type 3 routes with the spine route reflectors, which is exactly the overlay control plane required here.

Why this answer

In a VXLAN EVPN fabric, the underlay (here OSPF) provides loopback-to-loopback reachability between VTEPs, while the overlay control plane is MP-BGP with the L2VPN EVPN address family. Enabling that address family allows the leaf to advertise MAC and IP address routes and VTEP membership through the spine route reflectors, replacing flood-and-learn with a scalable, standards-based control plane.

Exam trap

The trap here is assuming the routing protocol that provides underlay loopback reachability also carries overlay MAC and IP reachability information.

114
MCQhard

A network engineer is implementing VXLAN with a Cisco Nexus 9000 series switch acting as a VTEP. The underlay network is OSPF, and the overlay uses BGP EVPN. The engineer notices that VM traffic between two hosts on different VTEPs is not being encapsulated. Which action should be taken to ensure VXLAN traffic is properly encapsulated and forwarded?

A.Ensure that the underlay OSPF cost is equal on all links to allow ECMP for VXLAN traffic.
B.Configure a VRF for the overlay and redistribute the VRF routes into OSPF.
C.Enable VXLAN feature and configure the NVE interface with a source interface and a VNI mapping to the VLAN.
D.Configure a VXLAN tunnel interface with the source interface as the loopback0 and the destination as the remote VTEP's loopback0.
AnswerC

To enable VXLAN encapsulation, the `feature nv overlay` and `feature vn-segment-vlan-based` must be enabled, and an NVE interface must be configured with a source interface (usually a loopback) and a VNI mapped to the VLAN. The NVE interface is the VTEP, and without it, VXLAN encapsulation does not occur.

Why this answer

VXLAN encapsulation requires the NVE interface to be configured with a source interface and VNI-to-VLAN mapping. Enabling the VXLAN features and configuring the NVE interface are essential steps. Without these, the switch will not encapsulate traffic, even if the underlay and overlay routing are correct.

Exam trap

The trap here is confusing underlay routing issues with overlay encapsulation; the lack of encapsulation is due to missing NVE configuration, not OSPF or BGP.

115
MCQhard

A service provider is migrating from a traditional IP core to an MPLS core. The engineer has configured LDP on all core routers and verified that LDP sessions are established. However, some prefixes learned via OSPF are not being assigned labels. The 'show mpls ldp bindings' command shows missing bindings for certain routes. What is the most likely cause?

A.The routes are not present in the global routing table on the router.
B.The OSPF process is not redistributed into LDP.
C.LDP is configured to only assign labels to BGP routes.
D.The 'mpls ldp autoconfig' command is missing on OSPF.
AnswerA

The correct reason is that LDP binds labels only to prefixes that are actively installed in the global routing table (RIB). In this scenario, even though OSPF may be advertising the routes through neighboring routers, those specific destinations are absent from the router's RIB, so there is no forwarding equivalence class (FEC) for LDP to assign a label binding to. Since LDP is a pure RIB consumer, any route missing from the global table—due to filtering, administrative distance issues, or passive interfaces—will never receive a label.

Why this answer

LDP assigns labels to every prefix present in the global routing table by default. If a prefix is not in the routing table (e.g., because it is a directly connected subnet that is not advertised via OSPF or is filtered by a route-map), LDP will not generate a label binding for it. The 'show mpls ldp bindings' command only displays bindings for routes that exist in the routing table, so missing bindings indicate the routes are absent from the global RIB.

Exam trap

The trap here is that candidates assume LDP requires a special configuration to work with OSPF, but in reality LDP automatically labels all routes in the global routing table, so missing bindings point to the routes not being present in the RIB rather than a protocol interaction issue.

How to eliminate wrong answers

Option B is wrong because LDP does not require redistribution from OSPF; it works directly with the IP routing table and automatically assigns labels to all IGP-learned prefixes. Option C is wrong because LDP is not selective by default — it assigns labels to all routes in the global routing table, not just BGP routes. Option D is wrong because 'mpls ldp autoconfig' is a Cisco command used to enable LDP on OSPF interfaces, not to control which prefixes receive labels; missing it would prevent LDP sessions from forming on those interfaces, but the question states LDP sessions are already established.

116
MCQhard

An engineer is troubleshooting a network where OSPF neighbors are stuck in the EXSTART state. What is the most likely cause?

A.Dead timer mismatch
B.Authentication misconfiguration
C.Mismatched OSPF area IDs
D.MTU mismatch between the routers
AnswerD

During the EXSTART/EXCHANGE phase, OSPF routers exchange database description (DBD) packets that can be as large as the interface MTU; if one router's MTU is lower, the larger DBD packet will be dropped or fragmented, and the neighbor will never leave EXSTART because it keeps waiting for a valid DBD sequence. The interface MTU mismatch is a classic cause of OSPF adjacencies stuck in EXSTART, as the router with the smaller MTU silently discards the oversized multicast packets. This can be diagnosed by checking the 'show ip ospf neighbor' state and by ensuring both ends have the same MTU or by enabling 'ip ospf mtu-ignore' as a workaround.

Why this answer

The EXSTART state in OSPF indicates that routers have formed a bidirectional communication (2-Way state) and are now attempting to exchange Database Description (DBD) packets to negotiate the master/slave relationship and the initial sequence number. An MTU mismatch between the routers is the most common cause of neighbors being stuck in EXSTART because the router with the smaller MTU will drop DBD packets that exceed its interface MTU, preventing the exchange from progressing to the Loading state.

Exam trap

Cisco often tests the EXSTART state as a symptom of MTU mismatch, but candidates frequently confuse it with authentication or area ID mismatches, which actually prevent adjacency formation at earlier stages like INIT or 2-Way.

How to eliminate wrong answers

Option A is wrong because a dead timer mismatch typically causes neighbors to be stuck in the INIT or 2-Way state, not EXSTART, as the routers will fail to receive Hello packets within the dead interval. Option B is wrong because authentication misconfiguration usually prevents OSPF neighbors from forming adjacency at all, often resulting in the INIT state or no neighbor relationship, not EXSTART. Option C is wrong because mismatched OSPF area IDs prevent the formation of any adjacency beyond the 2-Way state, as routers will not exchange Hello packets with mismatched area IDs, and they will not reach EXSTART.

117
MCQmedium

A network engineer runs the following command on Router R1: R1# show ip route vrf CUSTOMER-A VRF CUSTOMER-A: Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route Gateway of last resort is 10.0.1.1 to network 0.0.0.0 10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks C 10.0.0.0/30 is directly connected, GigabitEthernet0/0.100 L 10.0.0.1/32 is directly connected, GigabitEthernet0/0.100 B 10.0.2.0/24 [200/0] via 192.168.1.2, 00:12:34 Based on this output, what can be concluded?

A.VRF CUSTOMER-A has a BGP-learned route to 10.0.2.0/24
B.VRF CUSTOMER-A is not using BGP for routing
C.The default route is learned via BGP
D.GigabitEthernet0/0.100 is not associated with VRF CUSTOMER-A
AnswerA

The correct answer is confirmed by the routing table entry for VRF CUSTOMER-A. The prefix 10.0.2.0/24 is prefixed with 'B', which designates a route learned via the Border Gateway Protocol. The next-hop of 192.168.1.2 is the BGP peer address or an eBGP neighbor, proving that BGP is actively exchanging routes within this VRF. Additionally, the route is present in the VRF's isolated routing table, meaning the BGP session is associated with the VRF via the address-family configuration.

Why this answer

The output shows a BGP-learned route to 10.0.2.0/24 with the code 'B' and the administrative distance [200/0], indicating it is an external BGP route. The route is installed in the VRF CUSTOMER-A routing table, confirming that VRF CUSTOMER-A is using BGP and has learned this prefix via BGP from the next-hop 192.168.1.2.

Exam trap

Cisco often tests the distinction between the 'Gateway of last resort' and BGP-learned default routes; candidates may incorrectly assume the default route is BGP-learned because BGP is present in the table, but the output explicitly shows the gateway is 10.0.1.1, not a BGP next-hop.

How to eliminate wrong answers

Option B is wrong because the presence of a BGP-learned route (code 'B') in the VRF table proves that VRF CUSTOMER-A is using BGP for routing. Option C is wrong because the default route (Gateway of last resort) is set to 10.0.1.1, which is not a BGP-learned route; it is likely a static or connected default, and no BGP default route is shown in the table. Option D is wrong because the directly connected subnet 10.0.0.0/30 and local host route 10.0.0.1/32 are both on GigabitEthernet0/0.100, which is listed under VRF CUSTOMER-A, proving the interface is associated with the VRF.

118
MCQmedium

Router R1 has the following OSPF configuration: interface GigabitEthernet0/0 ip address 10.1.1.1 255.255.255.0 ip ospf 1 area 0 ip ospf network point-to-point ! router ospf 1 router-id 1.1.1.1 network 10.0.0.0 0.255.255.255 area 0 What is the effect of the 'ip ospf network point-to-point' command on this interface?

A.It disables OSPF on the interface.
B.It changes the OSPF network type to point-to-point, eliminating DR/BDR election and reducing hello timer to 10 seconds.
C.It enables OSPF authentication on the interface.
D.It sets the OSPF cost to 1.
AnswerB

The `ip ospf network point-to-point` command changes the interface's OSPF network type to point-to-point, which suppresses DR/BDR election and treats the link as a direct point-to-point connection. On NBMA media this also lowers the hello interval from 30 seconds to 10 seconds and the dead interval from 120 seconds to 40 seconds, allowing faster neighbor detection and convergence while eliminating type-2 network LSA generation.

Why this answer

The 'ip ospf network point-to-point' command changes the OSPF network type on the interface from the default (broadcast for Ethernet) to point-to-point. This eliminates the need for a Designated Router (DR) and Backup Designated Router (BDR) election, as point-to-point links have only two neighbors. Additionally, the OSPF hello timer on a point-to-point network defaults to 10 seconds (versus 30 seconds for non-broadcast), and the dead timer is 40 seconds.

Exam trap

Cisco often tests the misconception that 'ip ospf network point-to-point' disables OSPF or changes timers to 30 seconds, when in fact it eliminates DR/BDR and sets hello to 10 seconds.

How to eliminate wrong answers

Option A is wrong because the command does not disable OSPF; it modifies the network type while OSPF remains active. Option C is wrong because OSPF authentication is configured separately using 'ip ospf authentication' or 'ip ospf authentication-key' commands, not by changing the network type. Option D is wrong because the OSPF cost is not set to 1 by this command; cost is derived from interface bandwidth (default 100 Mbps / bandwidth) or manually set with 'ip ospf cost'.

119
MCQmedium

interface GigabitEthernet0/0 ip address 10.0.0.1 255.255.255.252 ip ospf network point-to-multipoint ip ospf hello-interval 30 ! router ospf 1 network 10.0.0.0 0.0.0.3 area 0 What is the effect of this configuration?

A.OSPF will use a 30-second hello interval and form adjacencies with all neighbors without DR/BDR election.
B.OSPF will use a 10-second hello interval and elect a DR/BDR.
C.OSPF will use a 30-second hello interval and elect a DR/BDR.
D.OSPF will use a 10-second hello interval and form adjacencies with all neighbors without DR/BDR.
AnswerA

In point-to-multipoint mode, OSPF treats each remote router as if connected by a separate point-to-point link, so a DR/BDR election is unnecessary and never occurs. The default hello interval for this network type is 30 seconds, and full adjacencies are formed with every neighbor individually. This allows the network to function correctly over non-broadcast multipoint topologies like Frame Relay or DMVPN without relying on a central hub-and-spoke election process.

Why this answer

The configuration sets the OSPF network type to point-to-multipoint, which by default uses a 30-second hello interval and does not perform DR/BDR election. The explicit 'ip ospf hello-interval 30' command confirms this interval, overriding any default. Therefore, OSPF will form adjacencies with all neighbors without electing a DR/BDR.

Exam trap

Cisco often tests the default hello intervals for different OSPF network types, and the trap here is that candidates mistakenly assume a 10-second hello interval (which is the default for broadcast and point-to-point networks) applies to point-to-multipoint, or that point-to-multipoint still requires DR/BDR election.

How to eliminate wrong answers

Option B is wrong because the hello interval is explicitly set to 30 seconds, not 10 seconds, and point-to-multipoint does not elect a DR/BDR. Option C is wrong because while the hello interval is correctly 30 seconds, point-to-multipoint networks do not elect a DR/BDR. Option D is wrong because the hello interval is 30 seconds, not 10 seconds, and although point-to-multipoint correctly avoids DR/BDR election, the hello interval mismatch makes this option incorrect.

120
Drag & Dropmedium

Drag and drop the steps of EIGRP redistribution from OSPF with metric seeding into the correct order, from first to last.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5

Why this order

First, the EIGRP routing process must be entered. Then, the redistribute command is used with the OSPF process and a metric. Optionally, route-map filtering can be applied.

Finally, verification ensures routes appear in the EIGRP topology table.

121
MCQmedium

Review the following OSPF configuration: router ospf 1 network 192.168.1.0 0.0.0.255 area 0 network 10.0.0.0 0.255.255.255 area 1 default-information originate always metric 20 metric-type 1 ! What is the effect of the 'default-information originate always metric 20 metric-type 1' command?

A.It injects a default route into OSPF only if a default route exists in the routing table, with metric 20 and type E1.
B.It injects a default route into OSPF unconditionally, with metric 20 and type E1.
C.It injects a default route into OSPF with metric 20 and type E2, but only if a default route exists.
D.It injects a default route into OSPF with metric 20 and type E1, but only for area 0.
AnswerB

This is the correct behavior for the OSPF 'default-information originate always' command. The 'always' keyword forces the router to originate and advertise a default route unconditionally, regardless of whether a default route is present in its routing table. The metric 20 and metric-type 1 specify that the route is advertised as an external type 1 (E1) route, which includes the cumulative internal cost to the ASBR. This matches the command syntax 'default-information originate always metric 20 metric-type 1'.

Why this answer

The 'default-information originate always' command injects a default route into the OSPF link-state database unconditionally, even if no default route exists in the routing table. The 'metric 20' sets the OSPF cost to 20, and 'metric-type 1' makes it an E1 (Type 1) external route, meaning the metric includes the internal cost to the ASBR plus the external cost.

Exam trap

Cisco often tests the distinction between 'default-information originate' (conditional) and 'default-information originate always' (unconditional), and the difference between metric-type 1 (E1) and metric-type 2 (E2), to see if candidates understand the exact behavior of each keyword.

How to eliminate wrong answers

Option A is wrong because the 'always' keyword causes the default route to be injected unconditionally, not only if a default route exists in the routing table. Option C is wrong because the command specifies 'metric-type 1', which results in an E1 route, not an E2 route; additionally, the 'always' keyword removes the condition of a pre-existing default route. Option D is wrong because the 'default-information originate' command applies to the entire OSPF process, not just area 0; the network statements define which interfaces participate in which areas, but the default route is advertised into all areas unless filtered.

122
MCQeasy

What is the default OSPF hello interval on an Ethernet link in a Cisco router?

A.10 seconds
B.30 seconds
C.5 seconds
D.40 seconds
AnswerA

The default OSPF HelloInterval on an Ethernet broadcast multi-access link is 10 seconds. Every 10 seconds a router sends an OSPF Hello packet out each OSPF-enabled interface to discover neighboring routers and maintain the neighbor relationship. This value is defined in RFC 2328 and is also the default for point-to-point links, but 10 seconds is the correct default specifically for the Ethernet network type in this question.

Why this answer

The default OSPF hello interval on an Ethernet link (which is a broadcast multi-access network type) is 10 seconds. This is defined in RFC 2328 and is the default on Cisco routers for broadcast and point-to-point network types. The hello interval determines how often a router sends hello packets to discover and maintain neighbor relationships.

Exam trap

Cisco often tests the default OSPF hello interval on Ethernet (broadcast) networks, and the trap here is that candidates confuse it with the dead interval (40 seconds) or with the hello interval used on other network types like NBMA (30 seconds).

How to eliminate wrong answers

Option B (30 seconds) is wrong because 30 seconds is the default hello interval for OSPF on NBMA (Non-Broadcast Multi-Access) networks, such as Frame Relay, not on Ethernet. Option C (5 seconds) is wrong because 5 seconds is not a standard OSPF hello interval; it might be confused with the default dead interval multiplier (4x hello) or with EIGRP's default hello interval on some media. Option D (40 seconds) is wrong because 40 seconds is the default OSPF dead interval on broadcast networks (4 x 10 seconds), not the hello interval.

123
MCQmedium

A network engineer is configuring a Cisco IOS router to authenticate OSPF neighbors using MD5 cryptographic authentication on an interface. The engineer enters the following commands: interface GigabitEthernet0/0, ip ospf authentication message-digest, ip ospf message-digest-key 1 md5 Cisco123. However, the OSPF adjacency with the neighbor router is not forming. Which additional configuration is required on the neighbor router to establish the adjacency?

A.Configure the neighbor with the command area 0 authentication message-digest.
B.Configure the neighbor with the command ip ospf authentication-key Cisco123.
C.Configure the same key ID and password on the neighbor's interface with ip ospf message-digest-key 1 md5 Cisco123.
D.Configure the neighbor with the command ip ospf authentication null.
AnswerC

For OSPF MD5 authentication to succeed, both routers must have the same key ID and password configured on their interfaces. The neighbor must have the identical message-digest-key command with the same key number and MD5 password. Without this matching configuration, authentication will fail, and the adjacency will not form.

Why this answer

OSPF MD5 authentication requires both neighbors to have the same key ID and password configured on their interfaces. The engineer configured MD5 on one router, so the neighbor must have the identical 'ip ospf message-digest-key' command. Without matching keys, authentication fails and the adjacency does not form.

Exam trap

The trap here is assuming that enabling MD5 authentication on one side is sufficient, or confusing plain text authentication with MD5 authentication.

124
Multi-Selectmedium

Which two statements about OSPF network types are true? (Choose two.)

Select 2 answers
A.On a broadcast multiaccess network, OSPF elects a DR and BDR to reduce LSA flooding.
B.The OSPF point-to-point network type requires a DR/BDR election.
C.On a non-broadcast multiaccess (NBMA) network, OSPF can use the neighbor command to manually discover neighbors.
D.The OSPF point-to-multipoint network type always elects a DR.
E.The default OSPF network type for a loopback interface is point-to-point.
AnswersA, C

Broadcast multiaccess segments elect a DR and BDR, which form adjacencies with all routers and originate network LSAs on the segment's behalf. This reduces full-mesh adjacency count and consequent LSA flooding across the shared medium.

Why this answer

Option A is correct because on a broadcast multiaccess network OSPF does elect a DR and BDR, which reduces the number of adjacencies and LSA flooding by having all other routers form full adjacencies only with the DR/BDR. Option C is correct because on an NBMA network OSPF does not automatically discover neighbors via multicast, so the neighbor command is used to manually specify neighbor IP addresses and enable unicast Hello packets. Option B is incorrect because the point-to-point network type does not require a DR/BDR election; it forms a direct adjacency.

Option D is incorrect because point-to-multipoint treats the network as a collection of point-to-point links and does not elect a DR/BDR. Option E is incorrect because the default OSPF network type for a loopback interface is loopback, which is advertised as a stub host route, not point-to-point.

Exam trap

350-401 often tests whether candidates remember that point-to-point and point-to-multipoint network types skip DR/BDR election, while broadcast and NBMA do not — and that loopback defaults to the loopback network type, not point-to-point.

125
MCQeasy

A network engineer is designing an OSPF network with multiple areas. The engineer wants to ensure that routers in area 2 can reach networks in area 0, but they should not learn any external routes from other ASs. Which OSPF area type should be configured for area 2?

A.Stub area
B.Not-so-stubby area (NSSA)
C.Totally stubby area
D.Standard area
AnswerA

A stub area is the correct choice because it filters out Type 5 (external) LSAs, preventing the router from learning external routes. Instead, the ABR automatically injects a default route (0.0.0.0/0) into the stub area, which routers use to forward traffic to destinations outside the OSPF domain. This satisfies the requirement of not learning external routes while still allowing full outbound connectivity.

Why this answer

A stub area blocks Type 5 LSAs (external routes from other ASs) while allowing Type 3 summary LSAs from area 0. This ensures routers in area 2 can reach networks in area 0 via inter-area routes but do not learn external routes, meeting the requirement exactly.

Exam trap

Cisco often tests the distinction between stub and totally stubby areas: candidates confuse 'blocking external routes' with 'blocking all routes except the default,' forgetting that a stub area still allows inter-area summary LSAs (Type 3) from area 0.

How to eliminate wrong answers

Option B (NSSA) is wrong because it allows Type 7 LSAs to carry external routes into the area, which would still introduce external routes from other ASs, violating the requirement. Option C (totally stubby area) is wrong because it blocks both Type 5 and Type 3 LSAs, preventing routers in area 2 from learning inter-area routes to networks in area 0. Option D (standard area) is wrong because it permits all LSA types, including Type 5 external LSAs, so routers would learn external routes from other ASs.

126
MCQeasy

A network engineer is configuring OSPF on a router that has multiple interfaces in the same area. The engineer wants to ensure that the router does not become the designated router (DR) on any of these interfaces. What should the engineer do?

A.Set the OSPF priority to 0 on all interfaces.
B.Configure the OSPF network type as point-to-point on all interfaces.
C.Use the 'ip ospf dr-priority' command to set a high priority on other routers.
D.Configure the router as an ABR.
AnswerA

In OSPF, DR/BDR election on broadcast multi-access networks is determined by the interface priority (range 0-255). Setting the 'ip ospf priority 0' command on every local interface makes the router ineligible to ever be elected as DR or BDR, because OSPF only considers routers with a non-zero priority as candidates. This is the standard, granular way to prevent a specific router from taking that control-plane role without altering the network type or affecting other routers' eligibility.

Why this answer

Setting the OSPF priority to 0 on all interfaces prevents the router from participating in the DR/BDR election process. A router with priority 0 will never become the DR or BDR on any segment, regardless of its Router ID or other factors. This is the only method that guarantees the router will not be elected as DR on any interface.

Exam trap

The trap here is that candidates often confuse DR/BDR election prevention with network type changes, thinking that point-to-point is the only way to avoid DR election, but the priority 0 method is the direct and correct answer for preventing a specific router from becoming DR without altering the network type.

How to eliminate wrong answers

Option B is wrong because configuring the OSPF network type as point-to-point eliminates the need for a DR/BDR election entirely, but it does not prevent the router from becoming the DR on interfaces that are not point-to-point; it changes the election behavior on those specific interfaces, but the question asks for a solution that works on all interfaces without altering the network type. Option C is wrong because setting a high priority on other routers does not guarantee that this router will not become the DR; if those other routers are not present or have lower Router IDs, this router could still be elected. Option D is wrong because configuring the router as an ABR (Area Border Router) has no effect on DR/BDR election; ABR status is about routing between areas, not about interface election roles.

127
Matchingmedium

Drag and drop each OSPF LSA type on the left to its matching description on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Describes the router's own directly connected links and neighbors

Generated by the Designated Router to describe all routers attached to a multi-access segment

Advertises networks from one area into another area (inter-area routes)

Advertises the location of an Autonomous System Boundary Router (ASBR)

Advertises routes redistributed from another routing domain (external routes)

Why these pairings

LSA Type 1 (Router LSA) describes a router's own links; Type 2 (Network LSA) is generated by the DR; Type 3 (Summary LSA) advertises inter-area routes; Type 4 (ASBR Summary LSA) advertises the location of an ASBR; Type 5 (AS External LSA) advertises external routes.

128
MCQhard

Refer to the exhibit. R1 has two equal-cost OSPF E2 routes to 10.1.1.0/24 via two different next hops. However, when tracing to 10.1.1.1, all traffic uses the path through 10.0.1.2. What is the most likely reason?

A.One route has a higher administrative distance.
B.A default route is overriding the specific route.
C.The route via 10.0.2.2 is an E1 route.
D.OSPF E2 routes do not factor interface cost; but the router uses the interface cost as a tie-breaker for equal-cost routes.
AnswerD

OSPF E2 routes advertise the external metric from the ASBR and intentionally discard the internal cost accumulated along the path, so two E2 routes with the same metric appear equal. However, Cisco IOS and many other implementations avoid a random choice by applying a tie-breaking rule: when the E2 metric and AD are identical, the router compares the OSPF interface cost (or the cost to the ASBR) and prefers the path with the lower cost. In the exhibit, the two E2 routes have equal external metrics, but the route via the interface with lower cost is installed, while the other is held as a candidate. Thus, the apparent equal-cost routes are not truly equal for forwarding because interface cost breaks the tie.

Why this answer

OSPF E2 routes do not include the internal cost to the ASBR; the cost shown in the routing table is the external metric only. When two E2 routes have the same external metric, Cisco IOS uses the interface cost as a tie-breaker to select the best next hop. In this scenario, the interface to 10.0.1.2 has a lower cost than the interface to 10.0.2.2, so all traffic is forwarded via 10.0.1.2.

Exam trap

Cisco often tests the subtle tie-breaking behavior for OSPF E2 routes, where candidates mistakenly assume that equal-cost E2 routes will always be load-balanced, ignoring the interface cost tie-breaker that Cisco IOS applies.

How to eliminate wrong answers

Option A is wrong because administrative distance is a per-protocol preference and both routes are OSPF E2 routes, so they share the same AD (110 by default). Option B is wrong because a default route would only be used if no specific route to 10.1.1.0/24 existed; the router has two specific routes and will use them, not a default. Option C is wrong because if the route via 10.0.2.2 were an E1 route, it would include the internal cost to the ASBR, making its total metric higher than the E2 route, and it would not be considered equal-cost; the question states both are equal-cost E2 routes.

129
MCQeasy

In OSPF, which LSA type is used to describe routes to networks within the same area and is generated by the router that owns the network?

A.Type 1 (Router LSA)
B.Type 2 (Network LSA)
C.Type 3 (Summary LSA)
D.Type 5 (External LSA)
AnswerA

Type 1 Router LSAs are originated by every OSPF router to advertise its own active interfaces and connected neighbors, including link type, link ID, interface IP, and metric. These LSAs are always confined to the area in which they are generated and form the base graph that Dijkstra's SPF algorithm processes. Because every router must describe itself before any other LSA can be interpreted, Type 1 is the most basic and essential LSA type.

Why this answer

Type 1 (Router LSA) is correct because each OSPF router generates a Type 1 LSA to describe its directly connected links and networks within the same area. This LSA is flooded only within the originating area and is the fundamental building block for intra-area route calculation using the SPF algorithm.

Exam trap

Cisco often tests the distinction between the router that originates the LSA (Type 1) versus the DR that generates the LSA for the network segment (Type 2), causing candidates to confuse the 'owner' of the network with the DR's role.

How to eliminate wrong answers

Option B (Type 2 Network LSA) is wrong because it is generated by the Designated Router (DR) on a broadcast or NBMA network to describe the routers attached to that segment, not by the router that owns the network. Option C (Type 3 Summary LSA) is wrong because it is generated by an Area Border Router (ABR) to advertise routes from one area to another, not for intra-area networks. Option D (Type 5 External LSA) is wrong because it is generated by an Autonomous System Boundary Router (ASBR) to advertise routes redistributed from outside the OSPF domain, not for networks within the same area.

← PreviousPage 2 of 2 · 129 questions total

Ready to test yourself?

Try a timed practice session using only OSPF questions.