Exam Bundle

That observation verifies acl counter troubleshooting in a different situation, such as when a new permit rule is blamed for a dropped service even though its hit counter never increases. For the reported acl implicit deny incident at a telecommunications branch in Oslo, the required acceptance evidence is: Specified allowed traffic passes while unmatched packets are denied. This other result does not test that condition directly.

That observation verifies urpf strict asymmetric routes in a different situation, such as when legitimate multihomed source traffic is dropped by strict uRPF because the best reverse path uses another interface. For the reported acl implicit deny incident at a telecommunications branch in Oslo, the required acceptance evidence is: Specified allowed traffic passes while unmatched packets are denied. This other result does not test that condition directly.

That observation verifies router control-plane versus interface acl in a different situation, such as when an engineer relies on a transit ACL to protect all router CPU services even though router-destined flows use different paths. For the reported acl implicit deny incident at a telecommunications branch in Oslo, the required acceptance evidence is: Specified allowed traffic passes while unmatched packets are denied. This other result does not test that condition directly.

That approach is relevant to phase 3 nhrp redirect shortcut, such as when a phase 3 DMVPN uses only hub transit even for established spoke-to-spoke flows because redirect and shortcut mechanisms are absent. That is a different root cause from the phase 2 next-hop-self fault observed at a provider edge operations team in Singapore. Applying that approach alone would not establish the required result: Spokes resolve the actual remote spoke next hop and build direct traffic paths.

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 phase 2 next-hop-self fault observed at a provider edge operations team in Singapore. Applying that approach alone would not establish the required result: Spokes resolve the actual remote spoke next hop and build direct traffic paths.

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 phase 2 next-hop-self fault observed at a provider edge operations team in Singapore. Applying that approach alone would not establish the required result: Spokes resolve the actual remote spoke next hop and build direct traffic paths.

That observation verifies phase 3 nhrp redirect shortcut in a different situation, such as when a phase 3 DMVPN uses only hub transit even for established spoke-to-spoke flows because redirect and shortcut mechanisms are absent. For the reported phase 2 next-hop-self incident at a provider edge operations team in Singapore, the required acceptance evidence is: Spokes resolve the actual remote spoke next hop and build direct traffic paths. 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 phase 2 next-hop-self incident at a provider edge operations team in Singapore, the required acceptance evidence is: Spokes resolve the actual remote spoke next hop and build direct traffic paths. This other result does not test that condition directly.

That observation verifies static hub mapping at spoke in a different situation, 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. For the reported phase 2 next-hop-self incident at a provider edge operations team in Singapore, the required acceptance evidence is: Spokes resolve the actual remote spoke next hop and build direct traffic paths. This other result does not test that condition directly.

That approach is relevant to ospf e1 e2 route preference, such as when two otherwise valid OSPF external alternatives are compared without considering their E1 and E2 metric semantics. That is a different root cause from the eigrp external ad comparison fault observed at a multinational data center in Frankfurt. Applying that approach alone would not establish the required result: The matching OSPF route is preferred over the external EIGRP route under unmodified default AD values.

That approach is relevant to ospf e1 versus e2 metric type, such as when traffic toward a redistributed external prefix should account for internal path cost, but all paths are evaluated only on the external metric. That is a different root cause from the eigrp external ad comparison fault observed at a multinational data center in Frankfurt. Applying that approach alone would not establish the required result: The matching OSPF route is preferred over the external EIGRP route under unmodified default AD values.

That approach is relevant to ospf external summarization, such as when an ASBR redistributing several adjacent external routes tries to use an ABR area range to summarize them. That is a different root cause from the eigrp external ad comparison fault observed at a multinational data center in Frankfurt. Applying that approach alone would not establish the required result: The matching OSPF route is preferred over the external EIGRP route under unmodified default AD values.

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 eigrp external ad comparison incident at a multinational data center in Frankfurt, the required acceptance evidence is: The matching OSPF route is preferred over the external EIGRP route under unmodified default AD values. This other result does not test that condition directly.

That observation verifies eigrp seed metric on redistribution in a different situation, such as when oSPF routes do not appear in EIGRP after redistribution because no usable seed metric was assigned. For the reported eigrp external ad comparison incident at a multinational data center in Frankfurt, the required acceptance evidence is: The matching OSPF route is preferred over the external EIGRP route under unmodified default AD values. This other result does not test that condition directly.

That observation verifies ospf external subnets redistribution in a different situation, such as when a redistribution statement is intended to carry multiple classless subnets into OSPF but only classful behavior is observed in the configured IOS context. For the reported eigrp external ad comparison incident at a multinational data center in Frankfurt, the required acceptance evidence is: The matching OSPF route is preferred over the external EIGRP route under unmodified default AD values. This other result does not test that condition directly.

That approach is relevant to dhcp relay udp filtering, 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. That is a different root cause from the dhcpv6 duid identity fault observed at a regional network operations center in Bristol. Applying that approach alone would not establish the required result: The reserved DHCPv6 lease maps to the intended client identity.

That approach is relevant to dhcp giaddr subnet selection, such as when a central DHCP server selects the wrong scope for remote clients because the relay's gateway address is unexpected. That is a different root cause from the dhcpv6 duid identity fault observed at a regional network operations center in Bristol. Applying that approach alone would not establish the required result: The reserved DHCPv6 lease maps to the intended client identity.

That approach is relevant to stateless dhcpv6 with slaac, such as when a VLAN wants SLAAC-generated addresses with DHCPv6 providing other information, but the router advertises the managed-address stateful flag. That is a different root cause from the dhcpv6 duid identity fault observed at a regional network operations center in Bristol. Applying that approach alone would not establish the required result: The reserved DHCPv6 lease maps to the intended client identity.

That observation verifies dhcpv6 relay missing in a different situation, such as when iPv6 clients on a remote link cannot contact the centralized stateful DHCPv6 server through their local router. For the reported dhcpv6 duid identity incident at a regional network operations center in Bristol, the required acceptance evidence is: The reserved DHCPv6 lease maps to the intended client identity. This other result does not test that condition directly.

That observation verifies dhcp giaddr subnet selection in a different situation, such as when a central DHCP server selects the wrong scope for remote clients because the relay's gateway address is unexpected. For the reported dhcpv6 duid identity incident at a regional network operations center in Bristol, the required acceptance evidence is: The reserved DHCPv6 lease maps to the intended client identity. 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 dhcpv6 duid identity incident at a regional network operations center in Bristol, the required acceptance evidence is: The reserved DHCPv6 lease maps to the intended client identity. This other result does not test that condition directly.

That approach is relevant to ldp discovery versus adjacency, such as when uDP-based LDP link discovery is observed, but the engineer assumes label exchange is healthy without verifying the TCP session. That is a different root cause from the ldp session transport reachability fault observed at a data center carrier in Toronto. Applying that approach alone would not establish the required result: LDP discovery and the transport TCP session remain Established and label bindings are exchanged.

That approach is relevant to label stack for vpn, such as when an MPLS VPN packet arrives with an outer transport label and inner service label; an operator interprets both labels as unrelated IP headers. That is a different root cause from the ldp session transport reachability fault observed at a data center carrier in Toronto. Applying that approach alone would not establish the required result: LDP discovery and the transport TCP session remain Established and label bindings are exchanged.

That approach is relevant to provider core label loss, such as when core IGP routes are stable but the ingress PE has no remote label for the required egress PE FEC. That is a different root cause from the ldp session transport reachability fault observed at a data center carrier in Toronto. Applying that approach alone would not establish the required result: LDP discovery and the transport TCP session remain Established and label bindings are exchanged.

That observation verifies ldp discovery versus adjacency in a different situation, such as when uDP-based LDP link discovery is observed, but the engineer assumes label exchange is healthy without verifying the TCP session. For the reported ldp session transport reachability incident at a data center carrier in Toronto, the required acceptance evidence is: LDP discovery and the transport TCP session remain Established and label bindings are exchanged. This other result does not test that condition directly.

That observation verifies lsp versus ip reachability in a different situation, such as when iCMP works between provider loopbacks but a customer VPN is unreachable; the engineer concludes this proves MPLS label switching works. For the reported ldp session transport reachability incident at a data center carrier in Toronto, the required acceptance evidence is: LDP discovery and the transport TCP session remain Established and label bindings are exchanged. 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 ldp session transport reachability incident at a data center carrier in Toronto, the required acceptance evidence is: LDP discovery and the transport TCP session remain Established and label bindings are exchanged. This other result does not test that condition directly.

That approach is relevant to ospf virtual link transit, such as when an attempted virtual link traverses a stub transit area, causing backbone repair to fail. That is a different root cause from the pbr on wrong interface fault observed at a multinational data center in Frankfurt. Applying that approach alone would not establish the required result: Matching inbound traffic follows the policy next hop while unmatched traffic continues normal routing.

That approach is relevant to longest prefix before ad, such as when a host matches an OSPF /24 and a lower-AD static /16; operations assumes the static summary must forward the packet. That is a different root cause from the pbr on wrong interface fault observed at a multinational data center in Frankfurt. Applying that approach alone would not establish the required result: Matching inbound traffic follows the policy next hop while unmatched traffic continues normal routing.

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 pbr on wrong interface fault observed at a multinational data center in Frankfurt. Applying that approach alone would not establish the required result: Matching inbound traffic follows the policy next hop while unmatched traffic continues normal routing.

That observation verifies longest prefix before ad in a different situation, such as when a host matches an OSPF /24 and a lower-AD static /16; operations assumes the static summary must forward the packet. For the reported pbr on wrong interface incident at a multinational data center in Frankfurt, the required acceptance evidence is: Matching inbound traffic follows the policy next hop while unmatched traffic continues normal routing. This other result does not test that condition directly.

That observation verifies ibgp next-hop preservation in a different situation, such as when a router learns an eBGP route through iBGP but its NEXT_HOP points at an unreachable border address. For the reported pbr on wrong interface incident at a multinational data center in Frankfurt, the required acceptance evidence is: Matching inbound traffic follows the policy next hop while unmatched traffic continues normal routing. This other result does not test that condition directly.

That observation verifies bfd versus routing discovery in a different situation, such as when an engineer deploys BFD and assumes it will discover routes without an associated routing or tracking client. For the reported pbr on wrong interface incident at a multinational data center in Frankfurt, the required acceptance evidence is: Matching inbound traffic follows the policy next hop while unmatched traffic continues normal routing. This other result does not test that condition directly.