Question 520
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
- Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
- Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
- Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
Explanation
Correct Answer
D:Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path. In the controlled acceptance rehearsal, the reported evidence is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. The intervention follows the governing fact that MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. Closure requires the corresponding specific confirmation: The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
Incorrect Answers
A:Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. This action was designed for the separate RSVP reservable bandwidth shortage case, not the controlled acceptance rehearsal being assessed. The present observation is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. Its governing mechanism is: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. The narrower applicable remedy is: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
B:Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. This action was designed for the separate RSVP link protection plan case, not the controlled acceptance rehearsal being assessed. The present observation is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. Its governing mechanism is: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. The narrower applicable remedy is: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
C:Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design. This action was designed for the separate RSVP LSP directionality case, not the controlled acceptance rehearsal being assessed. The present observation is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. Its governing mechanism is: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. The narrower applicable remedy is: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
Question 521
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
- Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
- Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
- Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
Explanation
Correct Answer
D:Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition. In the controlled acceptance rehearsal, the reported evidence is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The intervention follows the governing fact that RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. Closure requires the corresponding specific confirmation: A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.
Incorrect Answers
A:Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted. This action was designed for the separate Root protection against rogue core case, not the controlled acceptance rehearsal being assessed. The present observation is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Its governing mechanism is: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The narrower applicable remedy is: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
B:Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment. This action was designed for the separate Unexpected BPDU on edge port case, not the controlled acceptance rehearsal being assessed. The present observation is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Its governing mechanism is: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The narrower applicable remedy is: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
C:Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN. This action was designed for the separate Per-VLAN spanning-tree path case, not the controlled acceptance rehearsal being assessed. The present observation is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Its governing mechanism is: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The narrower applicable remedy is: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
Question 522
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.
- Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
- Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
- Move the access port to the approved VLAN and verify logical interface membership and learning.
Explanation
Correct Answer
C:Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end. In the controlled acceptance rehearsal, the reported evidence 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. The intervention follows the governing fact that A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. Closure requires the corresponding specific confirmation: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
Incorrect Answers
A:Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing. This action was designed for the separate IRB routed gateway missing case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The narrower applicable remedy is: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
B:Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port. This action was designed for the separate Unknown unicast flooding behavior case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The narrower applicable remedy is: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
D:Move the access port to the approved VLAN and verify logical interface membership and learning. This action was designed for the separate Access VLAN membership case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The narrower applicable remedy is: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
Question 523
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
- Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
- Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
- Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
Explanation
Correct Answer
B:Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters. In the controlled acceptance rehearsal, the reported evidence is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The intervention follows the governing fact that BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. Closure requires the corresponding specific confirmation: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
Incorrect Answers
A:Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the controlled acceptance rehearsal being assessed. The present observation is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Its governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The narrower applicable remedy is: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
C:Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability. This action was designed for the separate BGP TCP transport blocked case, not the controlled acceptance rehearsal being assessed. The present observation is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Its governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The narrower applicable remedy is: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
D:Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate. This action was designed for the separate IBGP transit split horizon case, not the controlled acceptance rehearsal being assessed. The present observation is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Its governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The narrower applicable remedy is: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
Question 524
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
- Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
- Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
- Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
Explanation
Correct Answer
D:Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. In the controlled acceptance rehearsal, the reported evidence 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. The intervention follows the governing fact that An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. Closure requires the corresponding specific confirmation: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
Incorrect Answers
A:Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design. This action was designed for the separate BGP MED comparison scope case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The narrower applicable remedy is: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
B:Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The narrower applicable remedy is: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
C:Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. This action was designed for the separate BGP local preference egress case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The narrower applicable remedy is: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
Question 525
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
- Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
- Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
- Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
Explanation
Correct Answer
D:Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation. In the controlled acceptance rehearsal, the reported evidence is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The intervention follows the governing fact that LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. Closure requires the corresponding specific confirmation: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
Incorrect Answers
A:Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response. This action was designed for the separate BFD detect timer too aggressive case, not the controlled acceptance rehearsal being assessed. The present observation is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. Its governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The narrower applicable remedy is: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
B:Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target. This action was designed for the separate GRES forwarding versus routing continuity case, not the controlled acceptance rehearsal being assessed. The present observation is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. Its governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The narrower applicable remedy is: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
C:Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover. This action was designed for the separate NSR backup routing synchronization case, not the controlled acceptance rehearsal being assessed. The present observation is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. Its governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The narrower applicable remedy is: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
Question 526
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
- Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
- Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
- Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
Explanation
Correct Answer
D:Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. In the controlled acceptance rehearsal, the reported evidence is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The intervention follows the governing fact that Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. Closure requires the corresponding specific confirmation: IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
Incorrect Answers
A:Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state. This action was designed for the separate Duplicate IS-IS system ID case, not the controlled acceptance rehearsal being assessed. The present observation is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Its governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The narrower applicable remedy is: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
B:Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. This action was designed for the separate IS-IS narrow metric ceiling case, not the controlled acceptance rehearsal being assessed. The present observation is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Its governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The narrower applicable remedy is: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
C:Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone. This action was designed for the separate IS-IS Level 1 exit default case, not the controlled acceptance rehearsal being assessed. The present observation is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Its governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The narrower applicable remedy is: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
Question 527
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
- Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
- Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
- Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
Explanation
Correct Answer
D:Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state. In the controlled acceptance rehearsal, the reported evidence is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The intervention follows the governing fact that IS-IS relies on a unique system ID to identify LSP originators and topology nodes. Closure requires the corresponding specific confirmation: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
Incorrect Answers
A:Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information. This action was designed for the separate IS-IS LSP lifetime anomaly case, not the controlled acceptance rehearsal being assessed. The present observation is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Its governing mechanism is: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The narrower applicable remedy is: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
B:Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible. This action was designed for the separate IS-IS route export scope case, not the controlled acceptance rehearsal being assessed. The present observation is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Its governing mechanism is: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The narrower applicable remedy is: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
C:Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design. This action was designed for the separate IS-IS level capability mismatch case, not the controlled acceptance rehearsal being assessed. The present observation is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Its governing mechanism is: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The narrower applicable remedy is: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
Question 528
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
- Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
- Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
- Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
Explanation
Correct Answer
D:Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution. In the controlled acceptance rehearsal, the reported evidence 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. The intervention follows the governing fact that LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. Closure requires the corresponding specific confirmation: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
Incorrect Answers
A:Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. This action was designed for the separate RSVP link protection plan case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The narrower applicable remedy is: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
B:Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC. This action was designed for the separate Incoming label missing in LFIB case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The narrower applicable remedy is: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
C:Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers. This action was designed for the separate Segment routing SID advertisement case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The narrower applicable remedy is: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
Question 529
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
- Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
- Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
- Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
Explanation
Correct Answer
C:Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target. In the controlled acceptance rehearsal, the reported evidence 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. The intervention follows the governing fact that GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. Closure requires the corresponding specific confirmation: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
Incorrect Answers
A:Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy. This action was designed for the separate VRRP master priority failover case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The narrower applicable remedy is: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
B:Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health. This action was designed for the separate VRRP preemption oscillation case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The narrower applicable remedy is: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
D:Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response. This action was designed for the separate BFD detect timer too aggressive case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The narrower applicable remedy is: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
Question 530
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
- Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
- Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
- Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
Explanation
Correct Answer
B:Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection. In the controlled acceptance rehearsal, the reported evidence is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The intervention follows the governing fact that OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. Closure requires the corresponding specific confirmation: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
Incorrect Answers
A:Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions. This action was designed for the separate OSPF export policy omission case, not the controlled acceptance rehearsal being assessed. The present observation is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. Its governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The narrower applicable remedy is: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
C:Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state. This action was designed for the separate Duplicate OSPF router identifier case, not the controlled acceptance rehearsal being assessed. The present observation is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. Its governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The narrower applicable remedy is: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
D:Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement. This action was designed for the separate OSPF passive interface case, not the controlled acceptance rehearsal being assessed. The present observation is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. Its governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The narrower applicable remedy is: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests