A company has many spoke sites with two data centers. The company wants to exchange the routing information between the data centers and the spoke sites using EIGRP. All locations belong to a single A

Splitting the network into two separate ASs would add unnecessary complexity and goes against the requirement of having all locations within a single EIGRP AS.

Exchanging all routes without summarization would lead to excessively large routing tables, increased convergence times, and higher resource consumption, which is inefficient for a large hub-and-spoke network.

Summarizing routes between the hubs is not the primary optimization point; the focus should be on summarizing the numerous granular routes originating from the spokes to reduce the overall routing table size.

Making each spoke site router a stub router reduces their processing overhead by limiting query scope and prevents them from being transit points for network traffic, improving stability.

Summarizing routes from the spoke sites toward the hubs minimizes the size of routing tables on the hub routers, reduces EIGRP update traffic, and enhances overall network scalability and efficiency.