An engineer is designing a DMVPN network where OSPF has been chosen as the routing protocol. A spoke-to-spoke data propagation model must be set up. Which two design considerations must be taken…

Setting spoke OSPF priority to 0 prevents spokes from ever being elected DR or BDR, ensuring the hub is always the DR. This is required because the hub is the only device with full multipoint GRE visibility and must distribute routing updates with correct next-hop addresses to all spokes.

Setting the hub priority to 255 alone does not prevent spokes from becoming DR if the hub is unavailable; the correct design sets spoke priority to 0, which guarantees the hub wins election regardless of priority values.

Point-to-multipoint network type causes OSPF to overwrite the next-hop with the advertising router's own address, breaking spoke-to-spoke forwarding because spokes cannot resolve the correct tunnel destination for direct paths.

Mixing network types between hub and spokes creates OSPF adjacency incompatibilities since both ends of an adjacency must use compatible network types to form a proper neighbor relationship.

Configuring OSPF network type as broadcast on all interfaces enables DR/BDR election and causes OSPF to preserve the original next-hop address in LSAs rather than replacing it with the advertising router's address - this next-hop preservation is essential for spoke-to-spoke traffic to resolve the correct NHRP tunnel endpoint and build direct tunnels.