Question 60
During production incident triage, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
- Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
- Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
- Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
Explanation
Correct Answer
D:Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. In the live production incident, the reported evidence is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The intervention follows the governing fact that An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. Closure requires the corresponding specific confirmation: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
Incorrect Answers
A:Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route. This action was designed for the separate Recursive next-hop resolution case, not the live production incident being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
B:Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. This action was designed for the separate Administrative preference overrides static case, not the live production incident being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
C:Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. This action was designed for the separate Generated default route prerequisite case, not the live production incident being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
Question 61
During production incident triage, 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?
- Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
- Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
- Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
- Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
Explanation
Correct Answer
A:Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members. In the live production incident, 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
B: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 live production incident 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: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 live production incident 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: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 live production incident 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 62
During production incident triage, engineers observe: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
- Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
- Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
- Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
Explanation
Correct Answer
C:Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. In the live production incident, the reported evidence is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The intervention follows the governing fact that GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. Closure requires the corresponding specific confirmation: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.
Incorrect Answers
A:Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. This action was designed for the separate GRE tunnel endpoint mismatch case, not the live production incident being assessed. The present observation is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Its governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The narrower applicable remedy is: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
B:Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. This action was designed for the separate GRE underlay recursive loss case, not the live production incident being assessed. The present observation is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Its governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The narrower applicable remedy is: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
D:Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. This action was designed for the separate GRE confidentiality misconception case, not the live production incident being assessed. The present observation is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Its governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The narrower applicable remedy is: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
Question 63
During production incident triage, engineers observe: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
- Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
- Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
- Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
Explanation
Correct Answer
A:Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. In the live production incident, the reported evidence is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. The intervention follows the governing fact that GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. Closure requires the corresponding specific confirmation: Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.
Incorrect Answers
B:Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. This action was designed for the separate GRE encapsulation MTU overhead case, not the live production incident being assessed. The present observation is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Its governing mechanism is: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The narrower applicable remedy is: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
C:Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. This action was designed for the separate GRE confidentiality misconception case, not the live production incident being assessed. The present observation is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Its governing mechanism is: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The narrower applicable remedy is: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
D:Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. This action was designed for the separate GRE underlay recursive loss case, not the live production incident being assessed. The present observation is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Its governing mechanism is: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The narrower applicable remedy is: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
Question 64
During production incident triage, 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?
- Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
- Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
- 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.
Explanation
Correct Answer
D:Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection. In the live production incident, 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:Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state. This action was designed for the separate OSPF hello dead timer mismatch case, not the live production incident 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.
B:Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design. This action was designed for the separate DR priority zero misconception case, not the live production incident 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: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 live production incident 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.
Question 65
During production incident triage, 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?
- Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
- Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
- Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
- Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
Explanation
Correct Answer
C:Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path. In the live production incident, 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:Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. This action was designed for the separate LDP TCP 646 establishment case, not the live production incident 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:Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling. This action was designed for the separate RSVP-TE constrained path missing case, not the live production incident 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.
D: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 live production incident 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 66
During production incident triage, engineers observe: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
- Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
- Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
- Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
Explanation
Correct Answer
D:Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path. In the live production incident, the reported evidence is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The intervention follows the governing fact that IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. Closure requires the corresponding specific confirmation: Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.
Incorrect Answers
A:Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity. This action was designed for the separate OSPFv3 neighbor uses link-local case, not the live production incident being assessed. The present observation is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. Its governing mechanism is: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The narrower applicable remedy is: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
B:Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. This action was designed for the separate IS-IS IPv6 reachability TLVs case, not the live production incident being assessed. The present observation is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. Its governing mechanism is: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The narrower applicable remedy is: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
C:Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel. This action was designed for the separate IPv6 over IPv4 transit tunnel case, not the live production incident being assessed. The present observation is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. Its governing mechanism is: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The narrower applicable remedy is: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
Question 67
During production incident triage, engineers observe: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. 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.
- Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
- Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
- Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
Explanation
Correct Answer
B:Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment. In the live production incident, the reported evidence is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The intervention follows the governing fact that Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. Closure requires the corresponding specific confirmation: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.
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 live production incident being assessed. The present observation is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Its governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The narrower applicable remedy is: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
C:Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members. This action was designed for the separate MSTP region mismatch case, not the live production incident being assessed. The present observation is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Its governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The narrower applicable remedy is: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
D: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 live production incident being assessed. The present observation is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Its governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The narrower applicable remedy is: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
Question 68
During production incident triage, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. 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.
- Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
- Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
Explanation
Correct Answer
B:Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. In the live production incident, the reported evidence is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The intervention follows the governing fact that IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. Closure requires the corresponding specific confirmation: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
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: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Its governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The narrower applicable remedy is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
C: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: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Its governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The narrower applicable remedy is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
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: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Its governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The narrower applicable remedy is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
Question 69
During production incident triage, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. 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.
- Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
- Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
- Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
Explanation
Correct Answer
B:Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state. In the live production incident, the reported evidence is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The intervention follows the governing fact that OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. Closure requires the corresponding specific confirmation: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
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: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Its governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The narrower applicable remedy is: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
C: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: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Its governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The narrower applicable remedy is: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
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 live production incident being assessed. The present observation is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Its governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The narrower applicable remedy is: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
Question 70
During production incident triage, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- 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.
- 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.
Explanation
Correct Answer
D:Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. In the live production incident, the reported evidence is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The intervention follows the governing fact that When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. Closure requires the corresponding specific confirmation: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
Incorrect Answers
A: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: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
B: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 live production incident being assessed. The present observation is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
C:Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. This action was designed for the separate EBGP multihop peering case, not the live production incident being assessed. The present observation is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests