Question 170
During production incident triage, engineers observe: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
- Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
- Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
- A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.
Explanation
Correct Answer
C:Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. This principle directly explains the live production incident: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The aligned engineering response is: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table. The result should be established through: The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
Incorrect Answers
A:ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. That explanation applies to the different Equal-cost multipath eligibility scenario rather than this live production incident. The current fault evidence is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The controlling mechanism is instead: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The correct response would be: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
B:Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. That explanation applies to the different Per-flow hash expectation scenario rather than this live production incident. The current fault evidence is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The controlling mechanism is instead: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The correct response would be: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
D:A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. That explanation applies to the different Static backup blackhole scenario rather than this live production incident. The current fault evidence is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The controlling mechanism is instead: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The correct response would be: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
Question 171
During production incident triage, engineers observe: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- 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.
- GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
Explanation
Correct Answer
A:VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. This principle directly explains the live production incident: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The aligned engineering response is: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health. The result should be established through: Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
Incorrect Answers
B: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 recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The controlling mechanism is instead: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The correct response would be: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
C: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: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The controlling mechanism is instead: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The correct response would be: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
D:GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. That explanation applies to the different GRES forwarding versus routing continuity scenario rather than this live production incident. The current fault evidence is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The controlling mechanism is instead: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The correct response would be: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
Question 172
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
- A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
- Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
- Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
Explanation
Correct Answer
C:Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. This principle directly explains the live production incident: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The aligned engineering response is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag. The result should be established through: 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
A:An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. That explanation applies to the different IRB routed gateway missing scenario rather than this live production incident. The current fault evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
B:A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this live production incident. The current fault evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
D:Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. That explanation applies to the different Native VLAN mismatch scenario rather than this live production incident. The current fault evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
Question 173
During production incident triage, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
- A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
- Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
- Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.
Explanation
Correct Answer
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. This principle directly explains the live production incident: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The aligned engineering response is: 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. The result should be established through: The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.
Incorrect Answers
A:An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. That explanation applies to the different Aggregate rejection behavior scenario rather than this live production incident. The current fault evidence is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The controlling mechanism is instead: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The correct response would be: 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.
C:Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. That explanation applies to the different Per-flow hash expectation scenario rather than this live production incident. The current fault evidence is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The controlling mechanism is instead: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The correct response would be: 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.
D:Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. That explanation applies to the different Filter-based forwarding classification scenario rather than this live production incident. The current fault evidence is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The controlling mechanism is instead: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The correct response would be: 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.
Question 174
During production incident triage, engineers observe: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
- Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
- An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
- A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
Explanation
Correct Answer
A:Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. This principle directly explains the live production incident: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The aligned engineering response is: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design. The result should be established through: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
Incorrect Answers
B:Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. That explanation applies to the different Native VLAN mismatch scenario rather than this live production incident. The current fault evidence is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The controlling mechanism is instead: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The correct response would be: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
C:An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. That explanation applies to the different IRB routed gateway missing scenario rather than this live production incident. The current fault evidence is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The controlling mechanism is instead: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The correct response would be: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
D:A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this live production incident. The current fault evidence is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The controlling mechanism is instead: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The correct response would be: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
Question 175
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
- OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
- Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
- OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.
Explanation
Correct Answer
D:OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. This principle directly explains the live production incident: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The aligned engineering response is: Set the correct point-to-point OSPF interface type where supported and aligned at both ends. The result should be established through: Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.
Incorrect Answers
A: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 routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The controlling mechanism is instead: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The correct response would be: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
B:OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. That explanation applies to the different OSPF authentication key mismatch scenario rather than this live production incident. The current fault evidence is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The controlling mechanism is instead: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The correct response would be: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
C:Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. That explanation applies to the different OSPF backbone connectivity scenario rather than this live production incident. The current fault evidence is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The controlling mechanism is instead: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The correct response would be: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
Question 176
During production incident triage, engineers observe: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
- IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
- IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
- IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
Explanation
Correct Answer
D:IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. This principle directly explains the live production incident: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The aligned engineering response is: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible. The result should be established through: The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
Incorrect Answers
A:IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. That explanation applies to the different IS-IS level-one area mismatch scenario rather than this live production incident. The current fault evidence is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The controlling mechanism is instead: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The correct response would be: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
B:IS-IS relies on a unique system ID to identify LSP originators and topology nodes. That explanation applies to the different Duplicate IS-IS system ID scenario rather than this live production incident. The current fault evidence is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The controlling mechanism is instead: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The correct response would be: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
C:IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. That explanation applies to the different IS-IS narrow metric ceiling scenario rather than this live production incident. The current fault evidence is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The controlling mechanism is instead: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The correct response would be: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
Question 177
During production incident triage, engineers observe: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
- Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
- An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
Explanation
Correct Answer
B:Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. This principle directly explains the live production incident: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The aligned engineering response is: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design. The result should be established through: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
Incorrect Answers
A:Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. That explanation applies to the different MAC move instability scenario rather than this live production incident. The current fault evidence is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The controlling mechanism is instead: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The correct response would be: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
C:Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. That explanation applies to the different Virtual switch instance membership scenario rather than this live production incident. The current fault evidence is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The controlling mechanism is instead: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The correct response would be: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
D:An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. That explanation applies to the different Access VLAN membership scenario rather than this live production incident. The current fault evidence is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The controlling mechanism is instead: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The correct response would be: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
Question 178
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
- Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
- MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
- Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
Explanation
Correct Answer
C:MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. This principle directly explains the live production incident: 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 aligned engineering response is: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members. The result should be established through: Both switches report the same region digest and expected instance-specific spanning-tree paths.
Incorrect Answers
A:RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. That explanation applies to the different RSTP alternate port activation scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. The correct response would be: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
B:Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. That explanation applies to the different Unexpected BPDU on edge port scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. The correct response would be: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
D:Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. That explanation applies to the different Root protection against rogue core scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. The correct response would be: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
Question 179
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
- When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
- BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
- An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
Explanation
Correct Answer
D:An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. This principle directly explains the live production incident: 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 aligned engineering response is: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. The result should be established through: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
Incorrect Answers
A:BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. That explanation applies to the different BGP next-hop inaccessible scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The correct response would be: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
B: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: 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 controlling mechanism is instead: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The correct response would be: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
C:BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. That explanation applies to the different BGP MED comparison scope scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The correct response would be: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests