A network engineer is troubleshooting an OSPFv2 neighbor relationship between two routers, R1 and R2, connected via a direct GigabitEthernet0/0 interface. R1's interface is configured with an MTU of 1500 bytes. When issuing the command `show ip ospf interface gigabitethernet0/0` on R2, the engineer observes the following truncated output:
GigabitEthernet0/0 is up, line protocol is up
Internet Address 10.0.12.2/24, Area 0
Process ID 1, Router ID 10.0.12.2, Network Type BROADCAST, Cost: 1
Transmit Delay is 1 sec, State DR, Priority 1
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
IP MTU bytes 1400
When running `show ip ospf neighbor` on R1, the neighbor status for R2 is listed as `EXSTART/ -`. Which statement correctly identifies the root cause of this stuck neighbor state and the appropriate command to bypass this requirement on R2?
- The neighbor is stuck in EXSTART/EXCHANGE because Database Description (DBD) packets are dropped due to the MTU size mismatch; executing `ip ospf mtu-ignore` on R2's interface allows adjacency formation.Cevap
- BThe neighbor is stuck in EXSTART because the OSPF Area ID string 'Area 0' on R2 does not match R1's dotted-decimal 'Area 0.0.0.0'; executing `ip ospf 1 area 0.0.0.0` on R2's interface resolves the mismatch.
- CThe neighbor is stuck in EXSTART because R2's Router Priority of 1 creates a conflict during Master/Slave negotiation; executing `ip ospf priority 0` on R2's interface forces it into Slave status.
- DThe neighbor is stuck in EXSTART because R2's interface is operating in BROADCAST mode while R1 is operating in POINT_TO_POINT mode; executing `ip ospf network point-to-point` on R2's interface is required.