Refer to the exhibit. An engineer is designing a multicampus Layer 3 infrastructure using EIGRP as the routing protocol. The design must provide quick replies to queries in the event of a downlink…

Configuring core layer switches as stub routers is incorrect because the core is designed to provide full reachability and propagate routes across the entire network, not act as an endpoint that restricts query propagation.

Configuring both access and core layers as stub routers is inappropriate for the core layer, as it would hinder the core's ability to propagate necessary routes.

Configuring distribution layer switches to summarize routes to the core layer reduces the number of routes propagated upstream, which decreases the core routing table size and limits the scope of EIGRP queries, improving convergence and stability.

Configuring access layer switches as EIGRP stub routers prevents EIGRP queries from propagating into the access layer, thereby limiting the query scope, reducing CPU utilization on access layer devices, and speeding up convergence throughout the network.

Access layer switches typically advertise directly connected networks and are best configured as stubs to limit query scope; route summarization is usually performed at higher aggregation points like the distribution layer.