A network engineer wants to limit the EIGRP query scope to avoid high CPU and memory utilization on low-end routers as well as limiting the possibility of a stuck-in-active routing event between HQ…

Question

Options

• AConfigure different Autonomous System number per each branch office and HQ and redistribute
• BConfigure all routers at branch offices as EIGRP stub and allow only directly connected networks
• CConfigure all routers at branch offices as EIGRP stub
• DConfigure all routers at HQ and branch offices as EIGRP stub

• A
  13% (5)
• B
  5% (2)
• C
  80% (32)
• D
  3% (1)

Explanation

EIGRP stub routing tells upstream (HQ) routers that a branch router is a stub and should not be queried when HQ is searching for an alternate path. This limits the EIGRP query domain, directly reducing the risk of Stuck-In-Active (SIA) events and lowering CPU/memory overhead on branch routers. Option B is too restrictive ('directly connected only') and would prevent branch routers from advertising summary or redistributed routes. Option A (separate ASNs with redistribution) is complex and creates more administrative overhead. Option D would make HQ routers stubs, which is incorrect - HQ must remain a full EIGRP participant. Configuring only branch routers as stubs is the targeted, correct approach.

No community discussion yet for this question.