Exam Bundle

That observation verifies mpls interface activation in a different situation, such as when an IGP core forwards ordinary IP packets but labeled traffic fails because MPLS forwarding is absent on a core-facing interface. For the reported mpls ldp binding mismatch incident at a multisite enterprise WAN in Houston, the required acceptance evidence is: LFIB next hop and outgoing label align with the valid underlying IGP path. This other result does not test that condition directly.

That observation verifies provider core label loss in a different situation, such as when core IGP routes are stable but the ingress PE has no remote label for the required egress PE FEC. For the reported mpls ldp binding mismatch incident at a multisite enterprise WAN in Houston, the required acceptance evidence is: LFIB next hop and outgoing label align with the valid underlying IGP path. This other result does not test that condition directly.

That observation verifies mpls label swapping in a different situation, such as when a core operator assumes each transit router forwards solely on the customer destination IP rather than the incoming MPLS label. For the reported mpls ldp binding mismatch incident at a multisite enterprise WAN in Houston, the required acceptance evidence is: LFIB next hop and outgoing label align with the valid underlying IGP path. This other result does not test that condition directly.

That approach is relevant to route-map attachment direction, such as when a prefix policy meant to constrain inbound BGP routes is applied only outbound to the peer. That is a different root cause from the incorrect summary prefix length fault observed at a bank network operations team in London. Applying that approach alone would not establish the required result: External RIBs no longer steer unrelated destinations into the summary path.

That approach is relevant to pbr set next-hop and packet selection, such as when a route-map modifies packets from an unintended subnet because its ACL permits every source. That is a different root cause from the incorrect summary prefix length fault observed at a bank network operations team in London. Applying that approach alone would not establish the required result: External RIBs no longer steer unrelated destinations into the summary path.

That approach is relevant to redistribution route-map omission, such as when a router leaks sensitive static prefixes into OSPF because redistribute static has no route policy. That is a different root cause from the incorrect summary prefix length fault observed at a bank network operations team in London. Applying that approach alone would not establish the required result: External RIBs no longer steer unrelated destinations into the summary path.

That observation verifies redistribution route-map omission in a different situation, such as when a router leaks sensitive static prefixes into OSPF because redistribute static has no route policy. For the reported incorrect summary prefix length incident at a bank network operations team in London, the required acceptance evidence is: External RIBs no longer steer unrelated destinations into the summary path. This other result does not test that condition directly.

That observation verifies bgp remote as incorrect in a different situation, such as when a BGP peer sends an OPEN notification and rejects the relationship because the configured remote-as does not match its actual ASN. For the reported incorrect summary prefix length incident at a bank network operations team in London, the required acceptance evidence is: External RIBs no longer steer unrelated destinations into the summary path. This other result does not test that condition directly.

That observation verifies mutual redistribution metric integrity in a different situation, such as when bGP-origin routes entering EIGRP are given arbitrary seed metrics that make a slow backup path appear better than intended. For the reported incorrect summary prefix length incident at a bank network operations team in London, the required acceptance evidence is: External RIBs no longer steer unrelated destinations into the summary path. This other result does not test that condition directly.

That approach is relevant to dhcp default router option, such as when clients obtain an IPv4 address and mask but have no valid default gateway because the pool's default-router option is incorrect. That is a different root cause from the dhcp duplicate leased ip fault observed at a corporate IT backbone in Chicago. Applying that approach alone would not establish the required result: New DHCP leases are unique and no overlapping static assignment remains.

That approach is relevant to dhcpv6 relay missing, such as when iPv6 clients on a remote link cannot contact the centralized stateful DHCPv6 server through their local router. That is a different root cause from the dhcp duplicate leased ip fault observed at a corporate IT backbone in Chicago. Applying that approach alone would not establish the required result: New DHCP leases are unique and no overlapping static assignment remains.

That approach is relevant to dhcp relay helper address, such as when broadcast DHCPDISCOVER packets from remote VLAN clients never reach the central DHCP server. That is a different root cause from the dhcp duplicate leased ip fault observed at a corporate IT backbone in Chicago. Applying that approach alone would not establish the required result: New DHCP leases are unique and no overlapping static assignment remains.

That observation verifies ipv4 dhcp excluded range in a different situation, such as when a router DHCP pool assigns IP addresses already reserved for statically configured infrastructure devices. For the reported dhcp duplicate leased ip incident at a corporate IT backbone in Chicago, the required acceptance evidence is: New DHCP leases are unique and no overlapping static assignment remains. This other result does not test that condition directly.

That observation verifies dhcp default router option in a different situation, such as when clients obtain an IPv4 address and mask but have no valid default gateway because the pool's default-router option is incorrect. For the reported dhcp duplicate leased ip incident at a corporate IT backbone in Chicago, the required acceptance evidence is: New DHCP leases are unique and no overlapping static assignment remains. This other result does not test that condition directly.

That observation verifies dhcp relay udp filtering in a different situation, such as when router helpers are correctly configured but remote clients time out because DHCP request/response UDP transport is blocked between relay and server. For the reported dhcp duplicate leased ip incident at a corporate IT backbone in Chicago, the required acceptance evidence is: New DHCP leases are unique and no overlapping static assignment remains. This other result does not test that condition directly.

That approach is relevant to static hub mapping at spoke, such as when a spoke cannot send initial NHRP requests because it has no mapping from the hub's tunnel address to the reachable NBMA address. That is a different root cause from the spoke nhrp registration age fault observed at a private transport network in Zurich. Applying that approach alone would not establish the required result: The hub retains current spoke mappings without expiration-related traffic loss.

That approach is relevant to nhrp cache verification, such as when a direct spoke route exists but its tunnel next hop lacks a corresponding NHRP resolution entry. That is a different root cause from the spoke nhrp registration age fault observed at a private transport network in Zurich. Applying that approach alone would not establish the required result: The hub retains current spoke mappings without expiration-related traffic loss.

That approach is relevant to dmvpn nhs omission, such as when a spoke tunnel comes up but never registers with the hub because no Next Hop Server target is configured. That is a different root cause from the spoke nhrp registration age fault observed at a private transport network in Zurich. Applying that approach alone would not establish the required result: The hub retains current spoke mappings without expiration-related traffic loss.

That observation verifies spoke multicast static mapping in a different situation, such as when a DMVPN spoke reaches the hub by unicast but its multicast routing hellos never reach the hub tunnel. For the reported spoke nhrp registration age incident at a private transport network in Zurich, the required acceptance evidence is: The hub retains current spoke mappings without expiration-related traffic loss. This other result does not test that condition directly.

That observation verifies dmvpn nhs omission in a different situation, such as when a spoke tunnel comes up but never registers with the hub because no Next Hop Server target is configured. For the reported spoke nhrp registration age incident at a private transport network in Zurich, the required acceptance evidence is: The hub retains current spoke mappings without expiration-related traffic loss. This other result does not test that condition directly.

That observation verifies dmvpn nhrp network id mismatch in a different situation, such as when the hub and spoke use different NHRP network identifiers despite otherwise consistent tunnel addressing. For the reported spoke nhrp registration age incident at a private transport network in Zurich, the required acceptance evidence is: The hub retains current spoke mappings without expiration-related traffic loss. This other result does not test that condition directly.

That approach is relevant to bgp address family activation, such as when an IPv6 BGP peer is Established for IPv4 but does not exchange IPv6 unicast routes because the IPv6 address family is inactive. That is a different root cause from the bgp remote as incorrect fault observed at an airport infrastructure network in Dubai. Applying that approach alone would not establish the required result: BGP moves into Established and valid prefixes appear in the neighbor summary.

That approach is relevant to ibgp loopback update-source, such as when an iBGP session configured to peer loopback-to-loopback remains Idle because the local source defaults to the physical interface. That is a different root cause from the bgp remote as incorrect fault observed at an airport infrastructure network in Dubai. Applying that approach alone would not establish the required result: BGP moves into Established and valid prefixes appear in the neighbor summary.

That approach is relevant to ebgp nonconnected loopback, such as when bGP TCP connectivity over loopbacks fails because a multihop eBGP peer relies on a default one-hop TTL. That is a different root cause from the bgp remote as incorrect fault observed at an airport infrastructure network in Dubai. Applying that approach alone would not establish the required result: BGP moves into Established and valid prefixes appear in the neighbor summary.

That observation verifies bgp rib failure in a different situation, such as when a prefix is visible as valid and best in BGP but cannot install into the RIB because another protocol has a preferable route. For the reported bgp remote as incorrect incident at an airport infrastructure network in Dubai, the required acceptance evidence is: BGP moves into Established and valid prefixes appear in the neighbor summary. This other result does not test that condition directly.

That observation verifies ibgp loopback update-source in a different situation, such as when an iBGP session configured to peer loopback-to-loopback remains Idle because the local source defaults to the physical interface. For the reported bgp remote as incorrect incident at an airport infrastructure network in Dubai, the required acceptance evidence is: BGP moves into Established and valid prefixes appear in the neighbor summary. This other result does not test that condition directly.

That observation verifies ebgp nonconnected loopback in a different situation, such as when bGP TCP connectivity over loopbacks fails because a multihop eBGP peer relies on a default one-hop TTL. For the reported bgp remote as incorrect incident at an airport infrastructure network in Dubai, the required acceptance evidence is: BGP moves into Established and valid prefixes appear in the neighbor summary. This other result does not test that condition directly.

That approach is relevant to aaa login authentication omitted, such as when remote access fails after AAA configuration because no supported authentication method list is bound to the relevant VTY lines. That is a different root cause from the aaa accounting records fault observed at a finance network core in Zurich. Applying that approach alone would not establish the required result: The accounting server receives attributable start/stop or command records for tested sessions.

That approach is relevant to aaa method list not applied, such as when the intended named login method list exists but VTY access continues to use another authentication path. That is a different root cause from the aaa accounting records fault observed at a finance network core in Zurich. Applying that approach alone would not establish the required result: The accounting server receives attributable start/stop or command records for tested sessions.

That approach is relevant to aaa server unavailable versus reject, such as when a router is configured TACACS+ then local, but an explicit reject from the active TACACS+ server is expected to trigger local fallback. That is a different root cause from the aaa accounting records fault observed at a finance network core in Zurich. Applying that approach alone would not establish the required result: The accounting server receives attributable start/stop or command records for tested sessions.

That observation verifies aaa source interface mismatch in a different situation, such as when aAA requests leave from an unexpected source IP that the policy server does not recognize as an authorized network device. For the reported aaa accounting records incident at a finance network core in Zurich, the required acceptance evidence is: The accounting server receives attributable start/stop or command records for tested sessions. This other result does not test that condition directly.

That observation verifies radius authentication transport in a different situation, such as when a router's RADIUS server is reachable by ICMP but RADIUS requests time out because authentication and accounting UDP ports are blocked. For the reported aaa accounting records incident at a finance network core in Zurich, the required acceptance evidence is: The accounting server receives attributable start/stop or command records for tested sessions. This other result does not test that condition directly.

That observation verifies aaa method list not applied in a different situation, such as when the intended named login method list exists but VTY access continues to use another authentication path. For the reported aaa accounting records incident at a finance network core in Zurich, the required acceptance evidence is: The accounting server receives attributable start/stop or command records for tested sessions. This other result does not test that condition directly.