Question 760
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. 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.
- Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
- A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
- Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
Explanation
Correct Answer
A:Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy. This tests the actual condition identified in the controlled acceptance rehearsal: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. It is meaningful because An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
Incorrect Answers
B:Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service. This measurement may prove the unrelated Q-in-Q outer tag mismatch condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. A relevant acceptance result here is: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
C: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: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. A relevant acceptance result here is: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
D: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: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. A relevant acceptance result here is: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
Question 761
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.
- 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 multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
Explanation
Correct Answer
D:The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect. This tests the actual condition identified in the controlled acceptance rehearsal: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. It is meaningful because An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
Incorrect Answers
A: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: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. A relevant acceptance result here is: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
B: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: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. A relevant acceptance result here is: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
C:The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct. This measurement may prove the unrelated BGP local preference egress condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. A relevant acceptance result here is: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
Question 762
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- 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.
- All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
- The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.
Explanation
Correct Answer
C:All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable. This tests the actual condition identified in the controlled acceptance rehearsal: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. It is meaningful because LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
Incorrect Answers
A: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 controlled acceptance rehearsal was resolved. The specific observed fault is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. A relevant acceptance result here is: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
B: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 controlled acceptance rehearsal was resolved. The specific observed fault is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. A relevant acceptance result here is: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
D:The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch. This measurement may prove the unrelated NSR backup routing synchronization condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. A relevant acceptance result here is: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
Question 763
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.
- The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.
- The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
- The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
Explanation
Correct Answer
D:The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent. This tests the actual condition identified in the controlled acceptance rehearsal: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. It is meaningful because BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
Incorrect Answers
A: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: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. A relevant acceptance result here is: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
B: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: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. A relevant acceptance result here is: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
C:The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect. This measurement may prove the unrelated EBGP multihop peering condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. A relevant acceptance result here is: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
Question 764
During a controlled acceptance rehearsal of the same defect on a separate test network, 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 intended core device is reported as root and a designated backup root is stable after an election test.
- A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.
- The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
- The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.
Explanation
Correct Answer
C: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 controlled acceptance rehearsal: 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
A: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: 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.
B: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: 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 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: 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 765
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.
- The intended core device is reported as root and a designated backup root is stable after an election test.
- 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.
Explanation
Correct Answer
B:The intended core device is reported as root and a designated backup root is stable after an election test. This tests the actual condition identified in the controlled acceptance rehearsal: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. It is meaningful because Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
Incorrect Answers
A: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: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. A relevant acceptance result here is: The intended core device is reported as root and a designated backup root is stable after an election test.
C: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 controlled acceptance rehearsal was resolved. The specific observed fault is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. A relevant acceptance result here is: The intended core device is reported as root and a designated backup root is stable after an election test.
D: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 controlled acceptance rehearsal was resolved. The specific observed fault is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. A relevant acceptance result here is: The intended core device is reported as root and a designated backup root is stable after an election test.
Question 766
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- 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.
- ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.
- Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
Explanation
Correct Answer
D:Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs. This tests the actual condition identified in the controlled acceptance rehearsal: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. It is meaningful because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
Incorrect Answers
A: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: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. A relevant acceptance result here is: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
B: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: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. A relevant acceptance result here is: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
C:ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops. This measurement may prove the unrelated OSPF backbone connectivity condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. A relevant acceptance result here is: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
Question 767
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. 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 observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
- The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
- The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
Explanation
Correct Answer
B:The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list. This tests the actual condition identified in the controlled acceptance rehearsal: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. It is meaningful because A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.
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 SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. A relevant acceptance result here is: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
C: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 SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. A relevant acceptance result here is: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
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 controlled acceptance rehearsal was resolved. The specific observed fault is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. A relevant acceptance result here is: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
Question 768
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
- The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
- Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
- The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
Explanation
Correct Answer
A:A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set. This tests the actual condition identified in the controlled acceptance rehearsal: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. It is meaningful because GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
Incorrect Answers
B:The designated router is primary under normal conditions and the backup takes over promptly during an injected outage. This measurement may prove the unrelated VRRP master priority failover condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. A relevant acceptance result here is: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
C:Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery. This measurement may prove the unrelated VRRP preemption oscillation condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. A relevant acceptance result here is: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
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 controlled acceptance rehearsal was resolved. The specific observed fault is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. A relevant acceptance result here is: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
Question 769
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
- The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
- A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
- The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
Explanation
Correct Answer
B:The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path. This tests the actual condition identified in the controlled acceptance rehearsal: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. It is meaningful because LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.
Incorrect Answers
A: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 controlled acceptance rehearsal was resolved. The specific observed fault is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. A relevant acceptance result here is: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
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 controlled acceptance rehearsal was resolved. The specific observed fault is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. A relevant acceptance result here is: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
D:The 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 provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. A relevant acceptance result here is: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
Question 770
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.
- Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.
- Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
- The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
Explanation
Correct Answer
D:The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops. This tests the actual condition identified in the controlled acceptance rehearsal: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. It is meaningful because A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
Incorrect Answers
A:The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch. This measurement may prove the unrelated NSR backup routing synchronization condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. A relevant acceptance result here is: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
B:Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test. This measurement may prove the unrelated Graceful restart helper expectations condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. A relevant acceptance result here is: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
C:Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery. This measurement may prove the unrelated VRRP preemption oscillation condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. A relevant acceptance result here is: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests