Question 160
During production incident triage, engineers observe: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
- 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 encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.
Explanation
Correct Answer
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. This principle directly explains the live production incident: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The aligned engineering response is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. The result should be established through: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.
Incorrect Answers
A: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 interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
B:GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. That explanation applies to the different GRE encapsulation MTU overhead scenario rather than this live production incident. The current fault evidence is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
D: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 interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
Question 161
During production incident triage, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
- Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
- An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
- A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
Explanation
Correct Answer
D:A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. This principle directly explains the live production incident: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The aligned engineering response is: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end. The result should be established through: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
Incorrect Answers
A: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: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The controlling mechanism is instead: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The correct response would be: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
B: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: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The controlling mechanism is instead: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The correct response would be: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
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: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The controlling mechanism is instead: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The correct response would be: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
Question 162
During production incident triage, engineers observe: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.
- An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
- BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
- BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
Explanation
Correct Answer
C:BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. This principle directly explains the live production incident: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The aligned engineering response is: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design. The result should be established through: The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.
Incorrect Answers
A:IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. That explanation applies to the different IBGP loopback source resolution scenario rather than this live production incident. The current fault evidence is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The controlling mechanism is instead: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. The correct response would be: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
B:An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. That explanation applies to the different EBGP multihop peering scenario rather than this live production incident. The current fault evidence is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The controlling mechanism is instead: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. The correct response would be: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
D: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: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The controlling mechanism is instead: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. The correct response would be: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
Question 163
During production incident triage, engineers observe: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
- 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.
- IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
Explanation
Correct Answer
A:OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. This principle directly explains the live production incident: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The aligned engineering response is: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity. The result should be established through: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
Incorrect Answers
B: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: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The controlling mechanism is instead: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The correct response would be: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
C: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: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The controlling mechanism is instead: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The correct response would be: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
D: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: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The controlling mechanism is instead: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The correct response would be: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
Question 164
During production incident triage, engineers observe: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. 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.
- Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
- VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
Explanation
Correct Answer
C:Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. This principle directly explains the live production incident: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The aligned engineering response is: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable. The result should be established through: Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.
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 router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The controlling mechanism is instead: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. The correct response would be: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.
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 router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The controlling mechanism is instead: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. The correct response would be: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.
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 router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The controlling mechanism is instead: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. The correct response would be: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.
Question 165
During production incident triage, engineers observe: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. 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.
- A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
- GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
- NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
Explanation
Correct Answer
B:A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. This principle directly explains the live production incident: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. The aligned engineering response is: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity. The result should be established through: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
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: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. The controlling mechanism is instead: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. The correct response would be: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
C: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: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. The controlling mechanism is instead: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. The correct response would be: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
D:NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. That explanation applies to the different NSR backup routing synchronization scenario rather than this live production incident. The current fault evidence is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. The controlling mechanism is instead: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. The correct response would be: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
Question 166
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
- GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
- 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 encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.
Explanation
Correct Answer
D:GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. This principle directly explains the live production incident: 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 aligned engineering response is: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. The result should be established through: Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.
Incorrect Answers
A:GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. That explanation applies to the different GRE encapsulation MTU overhead scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The correct response would be: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
B: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: 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 controlling mechanism is instead: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The correct response would be: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
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: 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 controlling mechanism is instead: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The correct response would be: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
Question 167
During production incident triage, engineers observe: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. 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 adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
- 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.
Explanation
Correct Answer
A:OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. This principle directly explains the live production incident: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. The aligned engineering response is: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub. The result should be established through: Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
Incorrect Answers
B:OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. That explanation applies to the different OSPF hello dead timer mismatch scenario rather than this live production incident. The current fault evidence is: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. The controlling mechanism is instead: OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. The correct response would be: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
C: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: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. The controlling mechanism is instead: OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. The correct response would be: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
D: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: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. The controlling mechanism is instead: OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. The correct response would be: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
Question 168
During production incident triage, engineers observe: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. 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.
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
- Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
- A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
Explanation
Correct Answer
D:A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. This principle directly explains the live production incident: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The aligned engineering response is: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port. The result should be established through: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
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: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The controlling mechanism is instead: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. The correct response would be: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
B: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: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The controlling mechanism is instead: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. The correct response would be: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
C:Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. That explanation applies to the different Q-in-Q outer tag mismatch scenario rather than this live production incident. The current fault evidence is: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The controlling mechanism is instead: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. The correct response would be: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
Question 169
During production incident triage, engineers observe: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Which 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 TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
- An IS-IS adjacency needs compatible protocol levels as well as link reachability.
- Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
Explanation
Correct Answer
B:IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. This principle directly explains the live production incident: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The aligned engineering response is: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. The result should be established through: The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
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 designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The controlling mechanism is instead: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The correct response would be: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
C:An IS-IS adjacency needs compatible protocol levels as well as link reachability. That explanation applies to the different IS-IS level capability mismatch scenario rather than this live production incident. The current fault evidence is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The controlling mechanism is instead: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The correct response would be: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
D:Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. That explanation applies to the different IS-IS ISO family missing scenario rather than this live production incident. The current fault evidence is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The controlling mechanism is instead: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The correct response would be: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests