You save $69.98
R1 and R2 share an Ethernet subnet and both run OSPFv2 area 0. R1 remains in INIT after receiving R2 Hellos. Which observation most directly explains INIT rather than an area mismatch?
INIT means R1 has seen a Hello from R2 but has not seen its own router ID in the neighbor list; bidirectional communication has not been established.
Priority influences DR election but does not explain why the local router ID is absent from received Hellos.
A loopback host mask is ordinary and is not evidence of missing bidirectional Hello recognition.
Unrelated static route preference does not determine whether R2 lists R1 in its Hello neighbor field.
Two directly connected OSPFv2 Ethernet routers are configured for area 0 and have unique IDs. One side uses 10-second Hello and 40-second Dead timers; the other uses 30-second Hello and 120-second Dead timers. No adjacency forms. Which corrective action targets the actual mismatch?
Neighboring OSPF interfaces normally require compatible Hello and Dead intervals; incompatible timer values are rejected during neighbor establishment.
Priority affects DR eligibility, not timer compatibility.
Process IDs have local significance and need not match for two Cisco routers to become neighbors.
Adding a default route does not repair OSPF Hello/Dead timer negotiation.
Two OSPFv2 routers share a routed link and their IPv4 addresses are in the same /30, but one interface belongs to area 0 and the other to area 10. What is the smallest correct repair?
An OSPF adjacency needs matching area identity on the common link; a single-area deployment normally places both interfaces in area 0.
OSPF process ID is local and does not reconcile mismatched area IDs in Hellos.
Matching MTU helps database exchange but does not fix area mismatch during neighbor discovery.
Cost controls SPF path calculation rather than the area compatibility prerequisite.
A CCNA lab uses OSPFv2 between two routers on a point-to-point link. Both become FULL neighbors. Which statement about a DR election is correct for this link type?
OSPF point-to-point adjacency does not require an Ethernet broadcast-style DR/BDR election; the two routers form a direct FULL adjacency.
Router-ID tie breaking matters on broadcast multiaccess networks, not point-to-point DR election.
Point-to-point OSPF has no BDR role.
Hello timer settings do not select a DR on a point-to-point link.
A single-area OSPFv2 broadcast VLAN has no existing DR or BDR. R1 priority 1, R2 priority 50, R3 priority 5, and R4 priority 0 are present before election. Which router is elected DR?
The highest nonzero OSPF interface priority wins a fresh broadcast DR election. Priority 50 beats 5 and 1; priority zero is not eligible.
An OSPF priority of zero makes an interface ineligible for DR/BDR.
Election favors higher—not lower—eligible priority.
No such midrange-priority preference exists in OSPF broadcast election.
Four OSPFv2 routers enter a broadcast segment simultaneously. R1 and R2 have priority 100; router IDs are R1=10.10.10.1 and R2=10.10.10.9. The others have priority 10. Which DR wins the initial election?
Both priority-100 routers are eligible; among equal priorities the higher numeric router ID 10.10.10.9 wins the DR tie-break.
OSPF router ID tie breaking uses the higher numeric ID.
Lower priority loses to an eligible priority-100 router.
A broadcast segment elects one DR and a BDR; not all routers are DR.
An Ethernet OSPFv2 segment already has an operational DR with priority 1. A new router joins with priority 200 and a higher router ID. What should the engineer expect immediately?
OSPF DR/BDR roles on broadcast links are nonpreemptive; a late, higher-priority neighbor does not simply replace an established DR.
OSPF does not preempt an incumbent DR solely because a new eligible router has a higher priority.
Different OSPF interface priorities are allowed and do not inherently prevent adjacency.
An existing BDR is also not automatically preempted solely by a late priority increase.
R1 is DR, R2 is BDR, and R3 is DROTHER on a stable OSPFv2 broadcast VLAN. R1 fails and its neighbor timers expire. What is the expected first role transition?
The BDR is the designated standby for DR failure; once the original DR is lost, R2 promotes to DR and a new BDR can be elected.
The standing BDR has priority to replace a failed DR, not an arbitrary DROTHER.
Router process IDs are locally significant and not part of failover selection.
Following neighbor loss, OSPF removes the failed DR and updates roles.
On a broadcast OSPFv2 LAN, router R4 has interface priority 0. It has the largest router ID and reaches FULL state with the DR. What does priority 0 mean?
Priority zero disables DR/BDR eligibility, not OSPF Hello exchange or adjacency with the elected DR/BDR.
Router ID only breaks ties among eligible nonzero-priority interfaces.
The election priority does not independently disable IPv4 forwarding.
Priority zero precludes both DR and BDR election.
A new OSPFv2 network has a manually configured router-id 2.2.2.2, loopback 10.10.10.10, and physical-interface IPv4 address 192.168.100.1. The OSPF process starts after the configuration. Which ID is selected?
An explicitly configured OSPF router ID overrides automatically chosen loopback or physical interface IPv4 addresses.
Highest physical interface only applies when there is no explicit router ID and no preferred loopback.
Loopbacks are preferred only for automatic selection, not over an explicit router-id statement.
A valid router ID is needed to run OSPF; it is selected before adjacency formation.
An OSPFv2 router has no explicit router-id command. Loopback0 is 10.20.30.1/32 and Gi0/0 is 172.28.6.1/24; both are up when the process starts. Which router ID is chosen?
With no explicit router ID, Cisco IOS prefers a loopback IPv4 address even when a physical interface has a numerically higher IPv4 address.
Loopback preference overrides the ordinary highest-active-interface rule.
Process IDs are local numeric identifiers, not automatically used as router IDs.
A subnet mask is not substituted for the loopback interface address.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (760 Questions, Last Updated on Nov 4, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
