You are designing a new Ethernet-based metro-area network for an enterprise customer to connect 50 sites within the same city OSPF will be the routing protocol used. The customer is primarily…

A multipoint Metro-E service provides shared Layer 2 connectivity across sites over a single service instance, reducing the number of routed interfaces and IP subnets required compared to separate P2P circuits, directly addressing address conservation.

Using unnumbered (single address per router) interfaces maximizes address conservation but complicates troubleshooting and does not directly address convergence time, making it a less balanced recommendation.

P2P links between routers in a hub-and-spoke design cause OSPF to use the point-to-point network type, eliminating DR/BDR election overhead and speeding convergence, while /30 or /31 subnets conserve IPv4 addresses.

Address aggregation at site routers reduces routing table size but does not conserve link-level IPv4 addresses or directly improve OSPF convergence time.

Manually determining DR/BDR is only relevant on multi-access OSPF networks; with P2P links as in option C, DR/BDR election does not occur and this step is unnecessary.