Question 100 Traffic balances equally across two EIGRP next hops that have very different physical rates; the engineer wants proportional forwarding without manipulating topology. Which lasting design or operational safeguard best prevents this particular issue from recurring? Match all EIGRP AFs and VRF bindings to documented tenant routing boundaries. Review summary and distribution policies jointly when adding backup path capacity. Record hub-spoke network type and split-horizon requirements in the overlay baseline. Define documented unequal-cost load-balancing policy and validate it on the target software version. ExplanationCorrect Answer D:Define documented unequal-cost load-balancing policy and validate it on the target software version. This addresses the recurring cause: EIGRP variance and traffic-share mechanisms can influence unequal-cost path installation and forwarding. A targeted acceptance check is: Inspect both installed EIGRP next hops and controlled flow distribution after changing supported settings. Other Answers A:Match all EIGRP AFs and VRF bindings to documented tenant routing boundaries. EIGRP variance and traffic-share mechanisms can influence unequal-cost path installation and forwarding. B:Review summary and distribution policies jointly when adding backup path capacity. EIGRP variance and traffic-share mechanisms can influence unequal-cost path installation and forwarding. C:Record hub-spoke network type and split-horizon requirements in the overlay baseline. EIGRP variance and traffic-share mechanisms can influence unequal-cost path installation and forwarding.
Question 101 A named-mode EIGRP IPv6 neighbor is absent after migration because the interface's address-family participation is disabled. Which corrective action most directly resolves the documented failure without suppressing unrelated safeguards? Enable the intended IPv6 address-family and its interface activation in the named EIGRP configuration. Review split horizon on the hub multipoint interface and apply the design-appropriate exception only where needed. Verify platform support and the EIGRP traffic-share behavior and metric inputs rather than changing BGP attributes. Check EIGRP distribute lists and summary advertisements toward that downstream neighbor. ExplanationCorrect Answer A:Enable the intended IPv6 address-family and its interface activation in the named EIGRP configuration. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. Confirm IPv6 EIGRP neighbor and route displays show the expected link and prefixes. Other Answers B:Review split horizon on the hub multipoint interface and apply the design-appropriate exception only where needed. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. C:Verify platform support and the EIGRP traffic-share behavior and metric inputs rather than changing BGP attributes. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. D:Check EIGRP distribute lists and summary advertisements toward that downstream neighbor. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship.
Question 102 A named-mode EIGRP IPv6 neighbor is absent after migration because the interface's address-family participation is disabled. Which technical mechanism best explains the behavior observed in this scenario? Authentication failure causes otherwise correctly addressed EIGRP hello packets to be rejected rather than forming a neighbor. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. A feasible path in the local topology does not guarantee its more-specific prefix is advertised past outbound policy. ExplanationCorrect Answer B:Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. This explains why the initial condition produces the observed failure. The direct repair is: Enable the intended IPv6 address-family and its interface activation in the named EIGRP configuration. Validate through: Confirm IPv6 EIGRP neighbor and route displays show the expected link and prefixes. Other Answers A:Authentication failure causes otherwise correctly addressed EIGRP hello packets to be rejected rather than forming a neighbor. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. C:Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. D:A feasible path in the local topology does not guarantee its more-specific prefix is advertised past outbound policy. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship.
Question 103 A named-mode EIGRP IPv6 neighbor is absent after migration because the interface's address-family participation is disabled. After applying the correction, which verification evidence most directly demonstrates that this issue is resolved? Compare RD, FD and computed metrics and show only the eligible path entering the routing table. Restore a stable uplink neighbor and verify the summarized branch route is received. Confirm IPv6 EIGRP neighbor and route displays show the expected link and prefixes. Inspect outbound advertisements and downstream topology entries for the affected specific routes. ExplanationCorrect Answer C:Confirm IPv6 EIGRP neighbor and route displays show the expected link and prefixes. This checks the affected traffic or control-plane behavior, not merely a generic up/down indicator. The underlying mechanism is: Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. Other Answers A:Compare RD, FD and computed metrics and show only the eligible path entering the routing table. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. B:Restore a stable uplink neighbor and verify the summarized branch route is received. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. D:Inspect outbound advertisements and downstream topology entries for the affected specific routes. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship.
Question 104 A named-mode EIGRP IPv6 neighbor is absent after migration because the interface's address-family participation is disabled. Which lasting design or operational safeguard best prevents this particular issue from recurring? Match all EIGRP AFs and VRF bindings to documented tenant routing boundaries. Classify EIGRP sites by transit role and keep stub policies consistent with their advertised routes. Review summary and distribution policies jointly when adding backup path capacity. Test IPv4 and IPv6 address families independently during named-mode migration. ExplanationCorrect Answer D:Test IPv4 and IPv6 address families independently during named-mode migration. This addresses the recurring cause: Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. A targeted acceptance check is: Confirm IPv6 EIGRP neighbor and route displays show the expected link and prefixes. Other Answers A:Match all EIGRP AFs and VRF bindings to documented tenant routing boundaries. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. B:Classify EIGRP sites by transit role and keep stub policies consistent with their advertised routes. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship. C:Review summary and distribution policies jointly when adding backup path capacity. Named EIGRP uses address-family and AF-interface configuration scopes; global IPv4 activation does not imply IPv6 neighborship.
Question 105 An EIGRP route's metric worsens after a link speed upgrade because interface bandwidth was left at an old configured value. Which corrective action most directly resolves the documented failure without suppressing unrelated safeguards? Correct the interface bandwidth reference and validate EIGRP composite metric components, not the physical speed alone. Correct the EIGRP autonomous-system membership or named address-family relationship to match the intended adjacency. Do not treat this backup as a feasible successor; verify an alternative path or allow query-based recalculation. Bind the intended EIGRP IPv6 address family to the correct VRF context and verify interface membership. ExplanationCorrect Answer A:Correct the interface bandwidth reference and validate EIGRP composite metric components, not the physical speed alone. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. Compare effective interface bandwidth/delay and resultant route metric before and after correction. Other Answers B:Correct the EIGRP autonomous-system membership or named address-family relationship to match the intended adjacency. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. C:Do not treat this backup as a feasible successor; verify an alternative path or allow query-based recalculation. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. D:Bind the intended EIGRP IPv6 address family to the correct VRF context and verify interface membership. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput.
Question 106 An EIGRP route's metric worsens after a link speed upgrade because interface bandwidth was left at an old configured value. Which technical mechanism best explains the behavior observed in this scenario? Authentication failure causes otherwise correctly addressed EIGRP hello packets to be rejected rather than forming a neighbor. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. DUAL waits for replies before completing an active diffusing computation; missing replies can trigger SIA handling. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. ExplanationCorrect Answer B:EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. This explains why the initial condition produces the observed failure. The direct repair is: Correct the interface bandwidth reference and validate EIGRP composite metric components, not the physical speed alone. Validate through: Compare effective interface bandwidth/delay and resultant route metric before and after correction. Other Answers A:Authentication failure causes otherwise correctly addressed EIGRP hello packets to be rejected rather than forming a neighbor. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. C:DUAL waits for replies before completing an active diffusing computation; missing replies can trigger SIA handling. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. D:Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput.
Question 107 An EIGRP route's metric worsens after a link speed upgrade because interface bandwidth was left at an old configured value. After applying the correction, which verification evidence most directly demonstrates that this issue is resolved? Display expected IPv6 routes in the tenant VRF and none leaked into the global table. Verify stub neighbor status and that query propagation no longer crosses the leaf sites during a controlled failover. Compare effective interface bandwidth/delay and resultant route metric before and after correction. Correlate the active topology entry, outstanding queries, neighbor resets and underlying transport loss. ExplanationCorrect Answer C:Compare effective interface bandwidth/delay and resultant route metric before and after correction. This checks the affected traffic or control-plane behavior, not merely a generic up/down indicator. The underlying mechanism is: EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. Other Answers A:Display expected IPv6 routes in the tenant VRF and none leaked into the global table. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. B:Verify stub neighbor status and that query propagation no longer crosses the leaf sites during a controlled failover. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. D:Correlate the active topology entry, outstanding queries, neighbor resets and underlying transport loss. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput.
Question 108 An EIGRP route's metric worsens after a link speed upgrade because interface bandwidth was left at an old configured value. Which lasting design or operational safeguard best prevents this particular issue from recurring? Record hub-spoke network type and split-horizon requirements in the overlay baseline. Bound query scope with hierarchy or stubs and monitor routing-control plane congestion. Review summary and distribution policies jointly when adding backup path capacity. Audit routing-relevant interface bandwidth and delay settings after circuit replacement. ExplanationCorrect Answer D:Audit routing-relevant interface bandwidth and delay settings after circuit replacement. This addresses the recurring cause: EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. A targeted acceptance check is: Compare effective interface bandwidth/delay and resultant route metric before and after correction. Other Answers A:Record hub-spoke network type and split-horizon requirements in the overlay baseline. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. B:Bound query scope with hierarchy or stubs and monitor routing-control plane congestion. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput. C:Review summary and distribution policies jointly when adding backup path capacity. EIGRP default metric calculation uses configured bandwidth and delay inputs rather than measuring instantaneous line throughput.
Question 109 An EIGRP spoke receives no branch summary after adding a passive-interface statement to the only uplink interface. Which corrective action most directly resolves the documented failure without suppressing unrelated safeguards? Remove unintended passive treatment for the transit interface while keeping LAN interfaces passive as planned. Correct the EIGRP autonomous-system membership or named address-family relationship to match the intended adjacency. Do not treat this backup as a feasible successor; verify an alternative path or allow query-based recalculation. Bind the intended EIGRP IPv6 address family to the correct VRF context and verify interface membership. ExplanationCorrect Answer A:Remove unintended passive treatment for the transit interface while keeping LAN interfaces passive as planned. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. Restore a stable uplink neighbor and verify the summarized branch route is received. Other Answers B:Correct the EIGRP autonomous-system membership or named address-family relationship to match the intended adjacency. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. C:Do not treat this backup as a feasible successor; verify an alternative path or allow query-based recalculation. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. D:Bind the intended EIGRP IPv6 address family to the correct VRF context and verify interface membership. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency.
Question 110 An EIGRP spoke receives no branch summary after adding a passive-interface statement to the only uplink interface. Which technical mechanism best explains the behavior observed in this scenario? DUAL waits for replies before completing an active diffusing computation; missing replies can trigger SIA handling. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. EIGRP neighborship requires compatible AS or address-family settings on participating interfaces. Split horizon ordinarily prevents re-advertising a route out the interface on which it was learned. ExplanationCorrect Answer B:Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. This explains why the initial condition produces the observed failure. The direct repair is: Remove unintended passive treatment for the transit interface while keeping LAN interfaces passive as planned. Validate through: Restore a stable uplink neighbor and verify the summarized branch route is received. Other Answers A:DUAL waits for replies before completing an active diffusing computation; missing replies can trigger SIA handling. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. C:EIGRP neighborship requires compatible AS or address-family settings on participating interfaces. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency. D:Split horizon ordinarily prevents re-advertising a route out the interface on which it was learned. Passive EIGRP interfaces do not transmit the neighbor discovery traffic needed for a routing adjacency.
