Question 240
During production incident triage, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
- No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
- An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
- Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
Explanation
Correct Answer
B:No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix. This tests the actual condition identified in the live production incident: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. It is meaningful because Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
Incorrect Answers
A:The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals. This measurement may prove the unrelated OSPF hello dead timer mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. A relevant acceptance result here is: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
C:An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable. This measurement may prove the unrelated DR priority zero misconception condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. A relevant acceptance result here is: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
D:Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination. This measurement may prove the unrelated OSPF LSDB discrepancy condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. A relevant acceptance result here is: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
Question 241
During production incident triage, engineers observe: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
- Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
- Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
- Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
Explanation
Correct Answer
D:Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB. This tests the actual condition identified in the live production incident: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. It is meaningful because OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
Incorrect Answers
A:The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals. This measurement may prove the unrelated OSPF hello dead timer mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. A relevant acceptance result here is: Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
B:Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination. This measurement may prove the unrelated OSPF LSDB discrepancy condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. A relevant acceptance result here is: Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
C:Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs. This measurement may prove the unrelated OSPF authentication key mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. A relevant acceptance result here is: Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
Question 242
During production incident triage, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
- A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
- The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
- The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.
Explanation
Correct Answer
B:A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router. This tests the actual condition identified in the live production incident: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. It is meaningful because Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
Incorrect Answers
A:IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions. This measurement may prove the unrelated IS-IS ISO family missing condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. A relevant acceptance result here is: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
C:The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links. This measurement may prove the unrelated IS-IS narrow metric ceiling condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. A relevant acceptance result here is: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
D:The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable. This measurement may prove the unrelated IS-IS DIS election surprise condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. A relevant acceptance result here is: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
Question 243
During production incident triage, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
- Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
- Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
- An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
Explanation
Correct Answer
C:Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations. This tests the actual condition identified in the live production incident: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. It is meaningful because RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
Incorrect Answers
A:The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination. This measurement may prove the unrelated MPLS interface not enabled condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. A relevant acceptance result here is: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
B:Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned. This measurement may prove the unrelated LDP discovery and IGP mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. A relevant acceptance result here is: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
D:An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction. This measurement may prove the unrelated LDP TCP 646 establishment condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. A relevant acceptance result here is: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
Question 244
During production incident triage, engineers observe: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
- No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
- Both peers reach Full adjacency in the same area and the intended routes are learned.
- Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
Explanation
Correct Answer
A:Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination. This tests the actual condition identified in the live production incident: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. It is meaningful because Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
Incorrect Answers
B:No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix. This measurement may prove the unrelated OSPF passive interface condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. A relevant acceptance result here is: Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
C:Both peers reach Full adjacency in the same area and the intended routes are learned. This measurement may prove the unrelated OSPF area ID mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. A relevant acceptance result here is: Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
D:Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub. This measurement may prove the unrelated Stub area external LSA expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. A relevant acceptance result here is: Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
Question 245
During production incident triage, engineers observe: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.
- No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
- Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.
- Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
Explanation
Correct Answer
A:ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops. This tests the actual condition identified in the live production incident: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. It is meaningful because Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
Incorrect Answers
B:No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix. This measurement may prove the unrelated OSPF passive interface condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. A relevant acceptance result here is: ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.
C:Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations. This measurement may prove the unrelated Point-to-point OSPF network type condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. A relevant acceptance result here is: ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.
D:Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs. This measurement may prove the unrelated OSPF authentication key mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. A relevant acceptance result here is: ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.
Question 246
During production incident triage, engineers observe: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
- The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
- An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.
- Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
Explanation
Correct Answer
C:An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment. This tests the actual condition identified in the live production incident: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. It is meaningful because An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
Incorrect Answers
A:The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer. This measurement may prove the unrelated IPv6 static link-local next hop condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. A relevant acceptance result here is: An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.
B:The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0. This measurement may prove the unrelated OSPFv3 neighbor uses link-local condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. A relevant acceptance result here is: An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.
D:Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution. This measurement may prove the unrelated IPv6 BGP NLRI family omitted condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. A relevant acceptance result here is: An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.
Question 247
During production incident triage, engineers observe: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
- An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
- A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
- The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.
Explanation
Correct Answer
B:An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction. This tests the actual condition identified in the live production incident: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. It is meaningful because LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
Incorrect Answers
A:The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination. This measurement may prove the unrelated MPLS interface not enabled condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. A relevant acceptance result here is: An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
C:A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress. This measurement may prove the unrelated Incoming label missing in LFIB condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. A relevant acceptance result here is: An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
D:The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label. This measurement may prove the unrelated Penultimate hop popping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. A relevant acceptance result here is: An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
Question 248
During production incident triage, engineers observe: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
- The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
- A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
- IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
Explanation
Correct Answer
A:The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links. This tests the actual condition identified in the live production incident: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. It is meaningful because IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
Incorrect Answers
B:The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability. This measurement may prove the unrelated IS-IS level-one area mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. A relevant acceptance result here is: The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
C:A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged. This measurement may prove the unrelated IS-IS level capability mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. A relevant acceptance result here is: The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
D:IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions. This measurement may prove the unrelated IS-IS ISO family missing condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. A relevant acceptance result here is: The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
Question 249
During production incident triage, engineers observe: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
- The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.
- The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
- The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
Explanation
Correct Answer
C:The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path. This tests the actual condition identified in the live production incident: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. It is meaningful because LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.
Incorrect Answers
A:An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction. This measurement may prove the unrelated LDP TCP 646 establishment condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. A relevant acceptance result here is: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
B:The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label. This measurement may prove the unrelated Penultimate hop popping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. A relevant acceptance result here is: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
D:The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled. This measurement may prove the unrelated RSVP link protection plan condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. A relevant acceptance result here is: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
Question 250
During production incident triage, engineers observe: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
- The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
- The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
- The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
Explanation
Correct Answer
D:The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems. This tests the actual condition identified in the live production incident: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. It is meaningful because ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
Incorrect Answers
A:The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover. This measurement may prove the unrelated Administrative preference overrides static condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. A relevant acceptance result here is: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
B:The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy. This measurement may prove the unrelated Martian-address acceptance condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. A relevant acceptance result here is: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
C:The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked. This measurement may prove the unrelated RIB group forwarding copy condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. A relevant acceptance result here is: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests