Question 40
During production incident triage, 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?
- Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
- Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.
- Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
- Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
Explanation
Correct Answer
A:Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. In the live production incident, 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
B:Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it. This action was designed for the separate BGP next-hop inaccessible case, not the live production incident 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: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 live production incident 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.
D: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 live production incident 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 41
During production incident triage, engineers observe: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
- Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
- Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
- Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
Explanation
Correct Answer
D:Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover. In the live production incident, the reported evidence is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The intervention follows the governing fact that NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. Closure requires the corresponding specific confirmation: The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.
Incorrect Answers
A:Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation. This action was designed for the separate LACP partner mismatch case, not the live production incident being assessed. The present observation is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. Its governing mechanism is: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The narrower applicable remedy is: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
B:Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity. This action was designed for the separate LAG member imbalance after failure case, not the live production incident being assessed. The present observation is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. Its governing mechanism is: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The narrower applicable remedy is: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
C: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 live production incident being assessed. The present observation is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. Its governing mechanism is: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The narrower applicable remedy is: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
Question 42
During production incident triage, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. 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.
- Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
- Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
Explanation
Correct Answer
C:Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design. In the live production incident, the reported evidence is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The intervention follows the governing fact that An IS-IS adjacency needs compatible protocol levels as well as link reachability. Closure requires the corresponding specific confirmation: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
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 live production incident being assessed. The present observation is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. Its governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The narrower applicable remedy is: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
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 live production incident being assessed. The present observation is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. Its governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The narrower applicable remedy is: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
D: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 live production incident being assessed. The present observation is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. Its governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The narrower applicable remedy is: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
Question 43
During production incident triage, engineers observe: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
- Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
- Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
- Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
Explanation
Correct Answer
D:Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy. In the live production incident, the reported evidence is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The intervention follows the governing fact that VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. Closure requires the corresponding specific confirmation: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
Incorrect Answers
A:Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation. This action was designed for the separate LACP partner mismatch case, not the live production incident being assessed. The present observation is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. Its governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. The narrower applicable remedy is: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
B:Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity. This action was designed for the separate LAG member imbalance after failure case, not the live production incident being assessed. The present observation is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. Its governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. The narrower applicable remedy is: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
C: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 live production incident being assessed. The present observation is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. Its governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. The narrower applicable remedy is: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
Question 44
During production incident triage, engineers observe: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
- Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
- Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
- Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
Explanation
Correct Answer
D:Set the correct point-to-point OSPF interface type where supported and aligned at both ends. In the live production incident, the reported evidence is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The intervention follows the governing fact that OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. Closure requires the corresponding specific confirmation: Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.
Incorrect Answers
A:Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF. This action was designed for the separate OSPF LSDB discrepancy case, not the live production incident being assessed. The present observation is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. Its governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The narrower applicable remedy is: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
B:Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover. This action was designed for the separate OSPF authentication key mismatch case, not the live production incident being assessed. The present observation is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. Its governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The narrower applicable remedy is: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
C:Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries. This action was designed for the separate OSPF backbone connectivity case, not the live production incident being assessed. The present observation is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. Its governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The narrower applicable remedy is: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
Question 45
During production incident triage, engineers observe: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
- Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
- Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
Explanation
Correct Answer
A:Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. In the live production incident, the reported evidence is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The intervention follows the governing fact that LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. Closure requires the corresponding specific confirmation: An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
Incorrect Answers
B:Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path. This action was designed for the separate MPLS interface not enabled case, not the live production incident being assessed. The present observation is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. Its governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The narrower applicable remedy is: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
C: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 live production incident being assessed. The present observation is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. Its governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The narrower applicable remedy is: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
D:Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the live production incident being assessed. The present observation is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. Its governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The narrower applicable remedy is: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
Question 46
During production incident triage, engineers observe: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
- Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
- Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
- Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
Explanation
Correct Answer
C:Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design. In the live production incident, the reported evidence is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The intervention follows the governing fact that OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. Closure requires the corresponding specific confirmation: An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
Incorrect Answers
A: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 live production incident being assessed. The present observation is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. Its governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The narrower applicable remedy is: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
B:Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange. This action was designed for the separate OSPF area ID mismatch case, not the live production incident being assessed. The present observation is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. Its governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The narrower applicable remedy is: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
D:Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub. This action was designed for the separate Stub area external LSA expectation case, not the live production incident being assessed. The present observation is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. Its governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The narrower applicable remedy is: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
Question 47
During production incident triage, engineers observe: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
- Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
- Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
- Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
Explanation
Correct Answer
A:Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries. In the live production incident, the reported evidence is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The intervention follows the governing fact that Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. Closure requires the corresponding specific confirmation: ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.
Incorrect Answers
B: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 live production incident being assessed. The present observation is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. Its governing mechanism is: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The narrower applicable remedy is: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
C:Set the correct point-to-point OSPF interface type where supported and aligned at both ends. This action was designed for the separate Point-to-point OSPF network type case, not the live production incident being assessed. The present observation is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. Its governing mechanism is: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The narrower applicable remedy is: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
D:Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover. This action was designed for the separate OSPF authentication key mismatch case, not the live production incident being assessed. The present observation is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. Its governing mechanism is: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The narrower applicable remedy is: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
Question 48
During production incident triage, 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?
- Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.
- Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
- 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.
Explanation
Correct Answer
B:Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. In the live production incident, 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:Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it. This action was designed for the separate BGP next-hop inaccessible case, not the live production incident 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: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 live production incident 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.
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 live production incident 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 49
During production incident triage, engineers observe: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
- 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.
- Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
Explanation
Correct Answer
A:Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag. In the live production incident, the reported evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The intervention follows the governing fact that Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. Closure requires the corresponding specific confirmation: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
Incorrect Answers
B: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 live production incident being assessed. The present observation is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Its governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The narrower applicable remedy is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
C: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 live production incident being assessed. The present observation is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Its governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The narrower applicable remedy is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
D:Align intended native VLAN handling on both ends or require explicit tagging according to the approved design. This action was designed for the separate Native VLAN mismatch case, not the live production incident being assessed. The present observation is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Its governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The narrower applicable remedy is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
Question 50
During production incident triage, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
- Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
- Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.
- Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
Explanation
Correct Answer
A:Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. In the live production incident, the reported evidence is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The intervention follows the governing fact that Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. Closure requires the corresponding specific confirmation: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
Incorrect Answers
B: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 live production incident being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
C:Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes. This action was designed for the separate BGP export policy omission case, not the live production incident being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
D: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 live production incident being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests