Refer to the exhibit. While troubleshooting the OSPF adjacency between routers R1 and R2 an engineer noticed that both routers are stuck in the EXCHANGE/EXSTART state. What should the engineer fix…

An IPv4 address mismatch would prevent the OSPF adjacency from reaching the INIT state, as hello packets would not be processed correctly by the neighboring router.

An OSPF area mismatch would typically prevent adjacency formation beyond the INIT or Two-Way state, as area IDs are exchanged in hello packets and must match for full adjacency.

An OSPF network type mismatch can lead to issues with DR/BDR election or neighbor discovery, but it doesn't specifically cause the adjacency to halt in the EXCHANGE/EXSTART state due to packet exchange failure like an MTU mismatch does.

During the EXCHANGE/EXSTART states, OSPF routers exchange Database Description (DD) packets to negotiate a master/slave relationship and synchronize their Link State Databases (LSDBs). An MTU mismatch between the connected interfaces can cause these DD packets to be fragmented or dropped, preventing the successful completion of the LSDB synchronization process.