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.
Question 731
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
- Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
- Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.
- 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:Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path. This tests the actual condition identified in the controlled acceptance rehearsal: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. It is meaningful because Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.
Incorrect Answers
A: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 controlled acceptance rehearsal was resolved. The specific observed fault is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. A relevant acceptance result here is: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.
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 controlled acceptance rehearsal was resolved. The specific observed fault is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. A relevant acceptance result here is: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.
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 controlled acceptance rehearsal was resolved. The specific observed fault is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. A relevant acceptance result here is: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.
Question 732
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. 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.
- The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
- The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
- VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
Explanation
Correct Answer
A:The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110. This tests the actual condition identified in the controlled acceptance rehearsal: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. It is meaningful because An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
Incorrect Answers
B: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 customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. A relevant acceptance result here is: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
C:The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears. This measurement may prove the unrelated MAC move instability condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. A relevant acceptance result here is: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
D: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 customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. A relevant acceptance result here is: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
Question 733
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
- Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
- A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
- The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
Explanation
Correct Answer
C:A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress. This tests the actual condition identified in the controlled acceptance rehearsal: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. It is meaningful because MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
Incorrect Answers
A: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 controlled acceptance rehearsal was resolved. The specific observed fault is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. A relevant acceptance result here is: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
B:Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations. This measurement may prove the unrelated RSVP LSP directionality condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. A relevant acceptance result here is: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
D:The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list. This measurement may prove the unrelated SR-MPLS node-SID shortest path condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. A relevant acceptance result here is: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
Question 734
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- 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.
- The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
Explanation
Correct Answer
D:The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits. This tests the actual condition identified in the controlled acceptance rehearsal: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. It is meaningful because RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
Incorrect Answers
A: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 controlled acceptance rehearsal was resolved. The specific observed fault is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. A relevant acceptance result here is: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
B: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 controlled acceptance rehearsal was resolved. The specific observed fault is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. A relevant acceptance result here is: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
C: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 new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. A relevant acceptance result here is: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
Question 735
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- 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.
- The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.
- A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.
Explanation
Correct Answer
A:Each VLAN reports its planned root and forwarding links with no loops during a controlled failover. This tests the actual condition identified in the controlled acceptance rehearsal: 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
B: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 controlled acceptance rehearsal 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 port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops. This measurement may prove the unrelated Root protection against rogue core condition, but it does not demonstrate that the current controlled acceptance rehearsal 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:A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop. This measurement may prove the unrelated RSTP alternate port activation condition, but it does not demonstrate that the current controlled acceptance rehearsal 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 736
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the 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.
- The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
- The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
- The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.
Explanation
Correct Answer
B:The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct. This tests the actual condition identified in the controlled acceptance rehearsal: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. It is meaningful because Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
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 IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. A relevant acceptance result here is: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
C:The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes. This measurement may prove the unrelated BGP IPv6 family inactive condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. A relevant acceptance result here is: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
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 IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. A relevant acceptance result here is: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
Question 737
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
- Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.
- Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
- Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
Explanation
Correct Answer
D: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 controlled acceptance rehearsal: 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
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: 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.
B: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 controlled acceptance rehearsal 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 sides report compatible MTU and move through Exchange to Full with a synchronized LSDB. This measurement may prove the unrelated OSPF MTU ExStart stall condition, but it does not demonstrate that the current controlled acceptance rehearsal 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 738
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
- The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.
- The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
- The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.
Explanation
Correct Answer
C:The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes. This tests the actual condition identified in the controlled acceptance rehearsal: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. It is meaningful because BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
Incorrect Answers
A:A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy. This measurement may prove the unrelated BGP AS-path comparison condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. A relevant acceptance result here is: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
B:The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes. This measurement may prove the unrelated BGP MED comparison scope condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. A relevant acceptance result here is: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
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: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. A relevant acceptance result here is: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
Question 739
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
- Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
- VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
- The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
Explanation
Correct Answer
C:VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs. This tests the actual condition identified in the controlled acceptance rehearsal: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. It is meaningful because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
Incorrect Answers
A:Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy. This measurement may prove the unrelated IRB routed gateway missing condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. A relevant acceptance result here is: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
B:Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port. This measurement may prove the unrelated Unknown unicast flooding behavior condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. A relevant acceptance result here is: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
D: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: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. A relevant acceptance result here is: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
Question 740
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. 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.
- The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
- The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
- An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
Explanation
Correct Answer
C:The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path. This tests the actual condition identified in the controlled acceptance rehearsal: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. It is meaningful because RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
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: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. A relevant acceptance result here is: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
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 controlled acceptance rehearsal was resolved. The specific observed fault is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. A relevant acceptance result here is: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
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 controlled acceptance rehearsal was resolved. The specific observed fault is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. A relevant acceptance result here is: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests