Question 180
During production incident triage, engineers observe: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.
- OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
- OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
- OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.
Explanation
Correct Answer
C:OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. This principle directly explains the live production incident: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The aligned engineering response is: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover. The result should be established through: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
Incorrect Answers
A:OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. That explanation applies to the different Stub area external LSA expectation scenario rather than this live production incident. The current fault evidence is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The controlling mechanism is instead: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The correct response would be: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
B:OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. That explanation applies to the different DR priority zero misconception scenario rather than this live production incident. The current fault evidence is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The controlling mechanism is instead: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The correct response would be: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
D:OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. That explanation applies to the different Point-to-point OSPF network type scenario rather than this live production incident. The current fault evidence is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The controlling mechanism is instead: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The correct response would be: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
Question 181
During production incident triage, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
- Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
- When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
- BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.
Explanation
Correct Answer
A:BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. This principle directly explains the live production incident: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The aligned engineering response is: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters. The result should be established through: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
Incorrect Answers
B:Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. That explanation applies to the different BGP local preference egress scenario rather than this live production incident. The current fault evidence is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The controlling mechanism is instead: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The correct response would be: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
C:When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. That explanation applies to the different BGP AS-path comparison scenario rather than this live production incident. The current fault evidence is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The controlling mechanism is instead: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The correct response would be: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
D:BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. That explanation applies to the different BGP import policy leak scenario rather than this live production incident. The current fault evidence is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The controlling mechanism is instead: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The correct response would be: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
Question 182
During production incident triage, engineers observe: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
- A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
- A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
- Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
Explanation
Correct Answer
A:Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. This principle directly explains the live production incident: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The aligned engineering response is: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change. The result should be established through: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
Incorrect Answers
B:A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. That explanation applies to the different Recursive next-hop resolution scenario rather than this live production incident. The current fault evidence is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The controlling mechanism is instead: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The correct response would be: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
C:A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. That explanation applies to the different Aggregate route contribution scenario rather than this live production incident. The current fault evidence is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The controlling mechanism is instead: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The correct response would be: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
D:Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. That explanation applies to the different Generated default route prerequisite scenario rather than this live production incident. The current fault evidence is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The controlling mechanism is instead: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The correct response would be: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
Question 183
During production incident triage, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
- MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
- LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
- LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.
Explanation
Correct Answer
A:RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. This principle directly explains the live production incident: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The aligned engineering response is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. The result should be established through: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
Incorrect Answers
B:MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. That explanation applies to the different MPLS interface not enabled scenario rather than this live production incident. The current fault evidence is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The controlling mechanism is instead: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The correct response would be: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
C:LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. That explanation applies to the different LDP TCP 646 establishment scenario rather than this live production incident. The current fault evidence is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The controlling mechanism is instead: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The correct response would be: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
D:LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. That explanation applies to the different Missing LDP FEC label mapping scenario rather than this live production incident. The current fault evidence is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The controlling mechanism is instead: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The correct response would be: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
Question 184
During production incident triage, engineers observe: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
- VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
- LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
- BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
Explanation
Correct Answer
C:LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. This principle directly explains the live production incident: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The aligned engineering response is: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation. The result should be established through: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
Incorrect Answers
A:VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. That explanation applies to the different VRRP master priority failover scenario rather than this live production incident. The current fault evidence is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The controlling mechanism is instead: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The correct response would be: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
B:VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. That explanation applies to the different VRRP preemption oscillation scenario rather than this live production incident. The current fault evidence is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The controlling mechanism is instead: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The correct response would be: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
D:BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. That explanation applies to the different BFD detect timer too aggressive scenario rather than this live production incident. The current fault evidence is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The controlling mechanism is instead: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The correct response would be: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
Question 185
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
- BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
- Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
- BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.
Explanation
Correct Answer
C:Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. This principle directly explains the live production incident: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The aligned engineering response is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. The result should be established through: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
Incorrect Answers
A:BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. That explanation applies to the different BGP peer autonomous system mismatch scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The correct response would be: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
B:BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. That explanation applies to the different BGP export policy omission scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The correct response would be: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
D:BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. That explanation applies to the different BGP import policy leak scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The correct response would be: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
Question 186
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
- Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
- MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
- VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
Explanation
Correct Answer
A:Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. This principle directly explains the live production incident: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The aligned engineering response is: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment. The result should be established through: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.
Incorrect Answers
B:Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. That explanation applies to the different Root bridge election priority scenario rather than this live production incident. The current fault evidence is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The controlling mechanism is instead: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The correct response would be: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
C:MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. That explanation applies to the different MSTP region mismatch scenario rather than this live production incident. The current fault evidence is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The controlling mechanism is instead: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The correct response would be: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
D:VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. That explanation applies to the different Per-VLAN spanning-tree path scenario rather than this live production incident. The current fault evidence is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The controlling mechanism is instead: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The correct response would be: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
Question 187
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.
- GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
- GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
- GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
Explanation
Correct Answer
B:GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. This principle directly explains the live production incident: 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 aligned engineering response is: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. The result should be established through: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.
Incorrect Answers
A:GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. That explanation applies to the different GRE tunnel endpoint mismatch scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The correct response would be: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
C:GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. That explanation applies to the different GRE underlay recursive loss scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The correct response would be: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
D:GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. That explanation applies to the different GRE confidentiality misconception scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The correct response would be: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
Question 188
During production incident triage, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
- An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
- An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
- IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.
Explanation
Correct Answer
B:An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. This principle directly explains the live production incident: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The aligned engineering response is: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable. The result should be established through: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
Incorrect Answers
A:IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. That explanation applies to the different IS-IS IPv6 reachability TLVs scenario rather than this live production incident. The current fault evidence is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The controlling mechanism is instead: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The correct response would be: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
C:An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. That explanation applies to the different IPv6 over IPv4 transit tunnel scenario rather than this live production incident. The current fault evidence is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The controlling mechanism is instead: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The correct response would be: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
D:IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. That explanation applies to the different ICMPv6 packet-too-big handling scenario rather than this live production incident. The current fault evidence is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The controlling mechanism is instead: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The correct response would be: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
Question 189
During production incident triage, 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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
- Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
- OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
- External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
Explanation
Correct Answer
C:OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. This principle directly explains the live production incident: 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 aligned engineering response is: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange. The result should be established through: Both peers reach Full adjacency in the same area and the intended routes are learned.
Incorrect Answers
A:OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. That explanation applies to the different DR priority zero misconception scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The correct response would be: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
B:Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. That explanation applies to the different OSPF LSDB discrepancy scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The correct response would be: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
D:External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. That explanation applies to the different OSPF export policy omission scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The correct response would be: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
Question 190
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
- A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
- NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
- VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
Explanation
Correct Answer
C:NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. This principle directly explains the live production incident: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The aligned engineering response is: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover. The result should be established through: The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.
Incorrect Answers
A:LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. That explanation applies to the different LACP partner mismatch scenario rather than this live production incident. The current fault evidence is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
B:A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. That explanation applies to the different LAG member imbalance after failure scenario rather than this live production incident. The current fault evidence is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
D:VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. That explanation applies to the different VRRP master priority failover scenario rather than this live production incident. The current fault evidence is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests