Question 720
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
- A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
- The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.
- The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.
Explanation
Correct Answer
B:A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged. This tests the actual condition identified in the controlled acceptance rehearsal: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. It is meaningful because BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
Incorrect Answers
A:The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available. This measurement may prove the unrelated BGP import policy leak condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. A relevant acceptance result here is: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
C:The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct. This measurement may prove the unrelated IBGP transit split horizon condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. A relevant acceptance result here is: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
D:The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry. This measurement may prove the unrelated BGP peer flap from mismatched hold timers condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. A relevant acceptance result here is: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
Question 721
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.
- The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
- The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
- Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.
Explanation
Correct Answer
C:The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability. This tests the actual condition identified in the controlled acceptance rehearsal: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. It is meaningful because IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
Incorrect Answers
A: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 controlled acceptance rehearsal was resolved. The specific observed fault is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. A relevant acceptance result here is: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
B:The intended prefix appears at the expected level without management or unrelated customer routes being leaked. This measurement may prove the unrelated IS-IS route export scope condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. A relevant acceptance result here is: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
D:Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks. This measurement may prove the unrelated IS-IS overload-state recovery condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. A relevant acceptance result here is: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
Question 722
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
- A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
- A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
- Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.
Explanation
Correct Answer
C:A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains. This tests the actual condition identified in the controlled acceptance rehearsal: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. It is meaningful because Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
Incorrect Answers
A:The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110. This measurement may prove the unrelated Access VLAN membership condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. A relevant acceptance result here is: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
B:A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN. This measurement may prove the unrelated Provider VLAN customer isolation condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. A relevant acceptance result here is: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
D:Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface. This measurement may prove the unrelated Flexible VLAN tagging logical units condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. A relevant acceptance result here is: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
Question 723
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.
- The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
- Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
- The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
Explanation
Correct Answer
B:The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer. This tests the actual condition identified in the controlled acceptance rehearsal: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. It is meaningful because An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
Incorrect Answers
A:Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary. This measurement may prove the unrelated ICMPv6 packet-too-big handling condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. A relevant acceptance result here is: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
C: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 controlled acceptance rehearsal was resolved. The specific observed fault is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. A relevant acceptance result here is: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
D: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 controlled acceptance rehearsal was resolved. The specific observed fault is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. A relevant acceptance result here is: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
Question 724
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
- The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
- Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
- Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
Explanation
Correct Answer
B: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 controlled acceptance rehearsal: 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
A: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 controlled acceptance rehearsal 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:Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate. This measurement may prove the unrelated OSPF metric path preference condition, but it does not demonstrate that the current controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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 725
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.
- The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
- The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
- A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
Explanation
Correct Answer
C:The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database. This tests the actual condition identified in the controlled acceptance rehearsal: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. It is meaningful because IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
Incorrect Answers
A:LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly. This measurement may prove the unrelated IS-IS LSP lifetime anomaly condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. A relevant acceptance result here is: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
B:The intended prefix appears at the expected level without management or unrelated customer routes being leaked. This measurement may prove the unrelated IS-IS route export scope condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. A relevant acceptance result here is: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
D: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 controlled acceptance rehearsal was resolved. The specific observed fault is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. A relevant acceptance result here is: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
Question 726
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
- VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
- Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
- A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
Explanation
Correct Answer
C:Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service. This tests the actual condition identified in the controlled acceptance rehearsal: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. It is meaningful because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
Incorrect Answers
A:The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context. This measurement may prove the unrelated Virtual switch instance membership condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. A relevant acceptance result here is: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
B:VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs. This measurement may prove the unrelated Trunk allowed VLAN omission condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. A relevant acceptance result here is: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
D:A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains. This measurement may prove the unrelated Native VLAN mismatch condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. A relevant acceptance result here is: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
Question 727
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
- A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
- The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.
- Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
Explanation
Correct Answer
D:Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design. This tests the actual condition identified in the controlled acceptance rehearsal: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. It is meaningful because BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
Incorrect Answers
A:The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available. This measurement may prove the unrelated BGP import policy leak condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. A relevant acceptance result here is: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
B:A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged. This measurement may prove the unrelated BGP TCP transport blocked condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. A relevant acceptance result here is: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
C:The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct. This measurement may prove the unrelated IBGP transit split horizon condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. A relevant acceptance result here is: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
Question 728
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
- Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
- The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
- The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
Explanation
Correct Answer
C:The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins. This tests the actual condition identified in the controlled acceptance rehearsal: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. It is meaningful because OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
Incorrect Answers
A:Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate. This measurement may prove the unrelated OSPF metric path preference condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. A relevant acceptance result here is: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
B: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 controlled acceptance rehearsal was resolved. The specific observed fault is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. A relevant acceptance result here is: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
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 controlled acceptance rehearsal was resolved. The specific observed fault is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. A relevant acceptance result here is: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
Question 729
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.
- A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.
- The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
- The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
Explanation
Correct Answer
C:The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled. This tests the actual condition identified in the controlled acceptance rehearsal: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. It is meaningful because RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.
Incorrect Answers
A: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 controlled acceptance rehearsal was resolved. The specific observed fault is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. A relevant acceptance result here is: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
B:A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling. This measurement may prove the unrelated Explicit-null forwarding condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. A relevant acceptance result here is: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
D:The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node. This measurement may prove the unrelated Segment routing SID advertisement condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. A relevant acceptance result here is: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
Question 730
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.
- Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
- The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
- The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
Explanation
Correct Answer
C:The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0. This tests the actual condition identified in the controlled acceptance rehearsal: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. It is meaningful because OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
Incorrect Answers
A:The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0. This measurement may prove the unrelated IS-IS IPv6 reachability TLVs condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. A relevant acceptance result here is: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
B: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 controlled acceptance rehearsal was resolved. The specific observed fault is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. A relevant acceptance result here is: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
D: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 controlled acceptance rehearsal was resolved. The specific observed fault is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. A relevant acceptance result here is: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests