Question 510
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
- Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
- Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
- Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
Explanation
Correct Answer
A:Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. In the controlled acceptance rehearsal, the reported evidence is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The intervention follows the governing fact that Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. Closure requires the corresponding specific confirmation: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
Incorrect Answers
B:Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. This action was designed for the separate Equal-cost multipath eligibility case, not the controlled acceptance rehearsal being assessed. The present observation is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
C:Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change. This action was designed for the separate Per-flow hash expectation case, not the controlled acceptance rehearsal being assessed. The present observation is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
D:Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. This action was designed for the separate Static backup blackhole case, not the controlled acceptance rehearsal being assessed. The present observation is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
Question 511
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
- Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
- Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
Explanation
Correct Answer
D:Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. In the controlled acceptance rehearsal, the reported evidence is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The intervention follows the governing fact that IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. Closure requires the corresponding specific confirmation: The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
Incorrect Answers
A:Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. This action was designed for the separate IS-IS ISO family missing case, not the controlled acceptance rehearsal being assessed. The present observation is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Its governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The narrower applicable remedy is: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
B: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 designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Its governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The narrower applicable remedy is: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
C:Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the controlled acceptance rehearsal being assessed. The present observation is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Its governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The narrower applicable remedy is: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
Question 512
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
- Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
- Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.
- Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
Explanation
Correct Answer
D:Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. In the controlled acceptance rehearsal, the reported evidence 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. The intervention follows the governing fact that BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. Closure requires the corresponding specific confirmation: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
Incorrect Answers
A:Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. This action was designed for the separate BGP AS-path comparison case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The narrower applicable remedy is: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
B: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: 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. Its governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The narrower applicable remedy is: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
C:Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy. This action was designed for the separate BGP peer flap from mismatched hold timers case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The narrower applicable remedy is: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
Question 513
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
- Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
- Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
- Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
Explanation
Correct Answer
D:Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table. In the controlled acceptance rehearsal, the reported evidence is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The intervention follows the governing fact that Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. Closure requires the corresponding specific confirmation: The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
Incorrect Answers
A:Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. This action was designed for the separate Static backup blackhole case, not the controlled acceptance rehearsal being assessed. The present observation is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Its governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The narrower applicable remedy is: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
B:Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. This action was designed for the separate Filter policy overmatch case, not the controlled acceptance rehearsal being assessed. The present observation is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Its governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The narrower applicable remedy is: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
C:Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation. This action was designed for the separate Routing instance cross-leak case, not the controlled acceptance rehearsal being assessed. The present observation is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Its governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The narrower applicable remedy is: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
Question 514
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
- Move the access port to the approved VLAN and verify logical interface membership and learning.
- Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
- Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
Explanation
Correct Answer
B:Move the access port to the approved VLAN and verify logical interface membership and learning. In the controlled acceptance rehearsal, the reported evidence 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. The intervention follows the governing fact that An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. Closure requires the corresponding specific confirmation: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
Incorrect Answers
A:Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership. This action was designed for the separate Virtual switch instance membership case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The narrower applicable remedy is: Move the access port to the approved VLAN and verify logical interface membership and learning.
C:Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design. This action was designed for the separate MAC move instability case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The narrower applicable remedy is: Move the access port to the approved VLAN and verify logical interface membership and learning.
D:Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end. This action was designed for the separate Trunk allowed VLAN omission case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The narrower applicable remedy is: Move the access port to the approved VLAN and verify logical interface membership and learning.
Question 515
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. 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.
- Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
- Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
- Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.
Explanation
Correct Answer
B:Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members. In the controlled acceptance rehearsal, the reported evidence is: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. The intervention follows the governing fact that MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. Closure requires the corresponding specific confirmation: Both switches report the same region digest and expected instance-specific spanning-tree paths.
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: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. Its governing mechanism is: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. The narrower applicable remedy is: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
C:Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support. This action was designed for the separate Loop protection after BPDU loss case, not the controlled acceptance rehearsal being assessed. The present observation is: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. Its governing mechanism is: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. The narrower applicable remedy is: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
D:Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy. This action was designed for the separate Root bridge election priority case, not the controlled acceptance rehearsal being assessed. The present observation is: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. Its governing mechanism is: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. The narrower applicable remedy is: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
Question 516
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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.
- Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
- Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
- Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
Explanation
Correct Answer
D:Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN. In the controlled acceptance rehearsal, the reported evidence 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. The intervention follows the governing fact that VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. Closure requires the corresponding specific confirmation: Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
Incorrect Answers
A:Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy. This action was designed for the separate Root bridge election priority case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The narrower applicable remedy is: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
B: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: 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. Its governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The narrower applicable remedy is: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
C:Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition. This action was designed for the separate RSTP alternate port activation case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The narrower applicable remedy is: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
Question 517
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
- Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
- Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
- Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
Explanation
Correct Answer
A:Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange. In the controlled acceptance rehearsal, the reported evidence is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The intervention follows the governing fact that OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. Closure requires the corresponding specific confirmation: Both peers reach Full adjacency in the same area and the intended routes are learned.
Incorrect Answers
B: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: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. Its governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The narrower applicable remedy is: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
C: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: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. Its governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The narrower applicable remedy is: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
D:Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection. This action was designed for the separate OSPF metric path preference case, not the controlled acceptance rehearsal being assessed. The present observation is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. Its governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The narrower applicable remedy is: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
Question 518
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
- Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
- Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
- Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
Explanation
Correct Answer
B:Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate. In the controlled acceptance rehearsal, the reported evidence is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The intervention follows the governing fact that Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. Closure requires the corresponding specific confirmation: The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.
Incorrect Answers
A:Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. This action was designed for the separate BGP AS-path comparison case, not the controlled acceptance rehearsal being assessed. The present observation is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Its governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The narrower applicable remedy is: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
C:Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters. This action was designed for the separate BGP peer autonomous system mismatch case, not the controlled acceptance rehearsal being assessed. The present observation is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Its governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The narrower applicable remedy is: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
D: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 router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Its governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The narrower applicable remedy is: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
Question 519
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
- Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
- Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
Explanation
Correct Answer
A:Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs. In the controlled acceptance rehearsal, the reported evidence is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The intervention follows the governing fact that When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. Closure requires the corresponding specific confirmation: Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.
Incorrect Answers
B:Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the controlled acceptance rehearsal being assessed. The present observation is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Its governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The narrower applicable remedy is: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
C: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 participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Its governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The narrower applicable remedy is: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
D:Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established. This action was designed for the separate IS-IS overload-state recovery case, not the controlled acceptance rehearsal being assessed. The present observation is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Its governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The narrower applicable remedy is: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests