Question 210
During production incident triage, engineers observe: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
- The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
- The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
- The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
Explanation
Correct Answer
B:The designated router is primary under normal conditions and the backup takes over promptly during an injected outage. This tests the actual condition identified in the live production incident: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. It is meaningful because VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
Incorrect Answers
A:All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable. This measurement may prove the unrelated LACP partner mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. A relevant acceptance result here is: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
C:The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops. This measurement may prove the unrelated LAG member imbalance after failure condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. A relevant acceptance result here is: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
D:The session remains stable during representative load yet detects an injected forwarding fault within the approved interval. This measurement may prove the unrelated BFD detect timer too aggressive condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. A relevant acceptance result here is: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
Question 211
During production incident triage, engineers observe: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.
- Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
- The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
- The intended core device is reported as root and a designated backup root is stable after an election test.
Explanation
Correct Answer
B:Each VLAN reports its planned root and forwarding links with no loops during a controlled failover. This tests the actual condition identified in the live production incident: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. It is meaningful because VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
Incorrect Answers
A:The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available. This measurement may prove the unrelated Unexpected BPDU on edge port condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. A relevant acceptance result here is: Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
C:The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored. This measurement may prove the unrelated Loop protection after BPDU loss condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. A relevant acceptance result here is: Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
D:The intended core device is reported as root and a designated backup root is stable after an election test. This measurement may prove the unrelated Root bridge election priority condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. A relevant acceptance result here is: Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
Question 212
During production incident triage, engineers observe: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
- The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
- The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
- The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
Explanation
Correct Answer
C:The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP. This tests the actual condition identified in the live production incident: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. It is meaningful because LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.
Incorrect Answers
A: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: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. A relevant acceptance result here is: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
B:The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits. This measurement may prove the unrelated RSVP reservable bandwidth shortage condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. A relevant acceptance result here is: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
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: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. A relevant acceptance result here is: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
Question 213
During production incident triage, engineers observe: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.
- Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.
- An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.
- Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.
Explanation
Correct Answer
C:An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated. This tests the actual condition identified in the live production incident: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. It is meaningful because GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
Incorrect Answers
A:A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed. This measurement may prove the unrelated GRE confidentiality misconception condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. A relevant acceptance result here is: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.
B:Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity. This measurement may prove the unrelated GRE encapsulation MTU overhead condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. A relevant acceptance result here is: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.
D:Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer. This measurement may prove the unrelated GRE tunnel endpoint mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. A relevant acceptance result here is: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.
Question 214
During production incident triage, engineers observe: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. 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.
- An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
- Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
- The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
Explanation
Correct Answer
C:Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate. This tests the actual condition identified in the live production incident: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. It is meaningful because OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
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: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. A relevant acceptance result here is: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
B: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: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. A relevant acceptance result here is: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
D:The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised. This measurement may prove the unrelated OSPF export policy omission condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. A relevant acceptance result here is: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
Question 215
During production incident triage, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
- The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
- 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
A:Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned. This tests the actual condition identified in the live production incident: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. It is meaningful because LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
Incorrect Answers
B:The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP. This measurement may prove the unrelated Missing LDP FEC label mapping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. A relevant acceptance result here is: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
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: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. A relevant acceptance result here is: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
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: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. A relevant acceptance result here is: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
Question 216
During production incident triage, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
- The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
- 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:The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised. This tests the actual condition identified in the live production incident: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. It is meaningful because External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
Incorrect Answers
B: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 PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. A relevant acceptance result here is: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
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: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. A relevant acceptance result here is: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
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: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. A relevant acceptance result here is: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
Question 217
During production incident triage, engineers observe: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
- All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
- The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
- A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
Explanation
Correct Answer
A:Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery. This tests the actual condition identified in the live production incident: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. It is meaningful because VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
Incorrect Answers
B:All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable. This measurement may prove the unrelated LACP partner mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. A relevant acceptance result here is: Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
C:The session remains stable during representative load yet detects an injected forwarding fault within the approved interval. This measurement may prove the unrelated BFD detect timer too aggressive condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. A relevant acceptance result here is: Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
D:A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set. This measurement may prove the unrelated GRES forwarding versus routing continuity condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. A relevant acceptance result here is: Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
Question 218
During production incident triage, engineers observe: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
- Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
- The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
- With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
Explanation
Correct Answer
C:The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked. This tests the actual condition identified in the live production incident: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. It is meaningful because Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
Incorrect Answers
A:The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems. This measurement may prove the unrelated Equal-cost multipath eligibility condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. A relevant acceptance result here is: The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
B:Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded. This measurement may prove the unrelated Per-flow hash expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. A relevant acceptance result here is: The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
D:With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate. This measurement may prove the unrelated Static backup blackhole condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. A relevant acceptance result here is: The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
Question 219
During production incident triage, engineers observe: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
- Both switches report the same region digest and expected instance-specific spanning-tree paths.
- Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
- The intended core device is reported as root and a designated backup root is stable after an election test.
Explanation
Correct Answer
A:The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored. This tests the actual condition identified in the live production incident: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. It is meaningful because Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.
Incorrect Answers
B:Both switches report the same region digest and expected instance-specific spanning-tree paths. This measurement may prove the unrelated MSTP region mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. A relevant acceptance result here is: The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
C:Each VLAN reports its planned root and forwarding links with no loops during a controlled failover. This measurement may prove the unrelated Per-VLAN spanning-tree path condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. A relevant acceptance result here is: The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
D:The intended core device is reported as root and a designated backup root is stable after an election test. This measurement may prove the unrelated Root bridge election priority condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. A relevant acceptance result here is: The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
Question 220
During production incident triage, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. 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.
- The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
- A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
- The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.
Explanation
Correct Answer
C:A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged. This tests the actual condition identified in the live production incident: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. It is meaningful because An IS-IS adjacency needs compatible protocol levels as well as link reachability.
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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. A relevant acceptance result here is: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
B: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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. A relevant acceptance result here is: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. A relevant acceptance result here is: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests