Question 610
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- 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.
- OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.
- 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 stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. This principle directly explains the controlled acceptance rehearsal: 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
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 controlled acceptance rehearsal. 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.
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 controlled acceptance rehearsal. 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: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 controlled acceptance rehearsal. 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 611
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.
- An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
- OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
- BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
Explanation
Correct Answer
D:BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. This principle directly explains the controlled acceptance rehearsal: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The aligned engineering response is: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops. The result should be established through: Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
Incorrect Answers
A: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 controlled acceptance rehearsal. The current fault evidence is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The controlling mechanism is instead: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The correct response would be: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.
B:An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. That explanation applies to the different IPv6 static link-local next hop scenario rather than this controlled acceptance rehearsal. The current fault evidence is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The controlling mechanism is instead: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The correct response would be: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.
C:OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. That explanation applies to the different OSPFv3 neighbor uses link-local scenario rather than this controlled acceptance rehearsal. The current fault evidence is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The controlling mechanism is instead: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The correct response would be: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.
Question 612
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- 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.
- VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
- Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
Explanation
Correct Answer
C:VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. This principle directly explains the controlled acceptance rehearsal: 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
A: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 controlled acceptance rehearsal. 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.
B: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 controlled acceptance rehearsal. 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:Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. That explanation applies to the different Graceful restart helper expectations scenario rather than this controlled acceptance rehearsal. 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 613
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- 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.
- Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
- Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
Explanation
Correct Answer
B: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 controlled acceptance rehearsal: 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: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 controlled acceptance rehearsal. 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:Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. That explanation applies to the different Provider VLAN customer isolation scenario rather than this controlled acceptance rehearsal. 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.
D:Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. That explanation applies to the different Flexible VLAN tagging logical units scenario rather than this controlled acceptance rehearsal. 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 614
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- 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.
- Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
- VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
Explanation
Correct Answer
A:A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. This principle directly explains the controlled acceptance rehearsal: 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
B: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 controlled acceptance rehearsal. 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:Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. That explanation applies to the different Graceful restart helper expectations scenario rather than this controlled acceptance rehearsal. 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: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 controlled acceptance rehearsal. 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 615
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. 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.
- 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.
- 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:BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. This principle directly explains the controlled acceptance rehearsal: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The aligned engineering response is: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response. The result should be established through: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
Incorrect Answers
A: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 controlled acceptance rehearsal. The current fault evidence is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The controlling mechanism is instead: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The correct response would be: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
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 controlled acceptance rehearsal. The current fault evidence is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The controlling mechanism is instead: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The correct response would be: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
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 controlled acceptance rehearsal. The current fault evidence is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The controlling mechanism is instead: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The correct response would be: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
Question 616
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
- Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
- VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
- GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
Explanation
Correct Answer
B: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 controlled acceptance rehearsal: 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: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 controlled acceptance rehearsal. 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.
C: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 controlled acceptance rehearsal. 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: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 controlled acceptance rehearsal. 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 617
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
- Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
- IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
- Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
Explanation
Correct Answer
A:An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. This principle directly explains the controlled acceptance rehearsal: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The aligned engineering response is: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established. The result should be established through: Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.
Incorrect Answers
B:Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. That explanation applies to the different IS-IS Level 1 exit default scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The controlling mechanism is instead: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The correct response would be: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
C:IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. That explanation applies to the different IS-IS LSP lifetime anomaly scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The controlling mechanism is instead: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The correct response would be: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
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 controlled acceptance rehearsal. The current fault evidence is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The controlling mechanism is instead: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The correct response would be: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
Question 618
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. 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.
- Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
- OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
- Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
Explanation
Correct Answer
D:Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. This principle directly explains the controlled acceptance rehearsal: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The aligned engineering response is: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement. The result should be established through: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
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 controlled acceptance rehearsal. The current fault evidence is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The controlling mechanism is instead: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The correct response would be: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
B: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 controlled acceptance rehearsal. The current fault evidence is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The controlling mechanism is instead: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The correct response would be: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
C:OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. That explanation applies to the different Duplicate OSPF router identifier scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The controlling mechanism is instead: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The correct response would be: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
Question 619
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
- 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.
- Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
- Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
Explanation
Correct Answer
A:For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. This principle directly explains the controlled acceptance rehearsal: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The aligned engineering response is: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. The result should be established through: The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
Incorrect Answers
B: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 controlled acceptance rehearsal. The current fault evidence is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The controlling mechanism is instead: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The correct response would be: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
C:Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. That explanation applies to the different Filter policy overmatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The controlling mechanism is instead: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The correct response would be: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
D: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 controlled acceptance rehearsal. The current fault evidence is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The controlling mechanism is instead: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The correct response would be: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
Question 620
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
- Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
- 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.
Explanation
Correct Answer
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. This principle directly explains the controlled acceptance rehearsal: 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
A: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 controlled acceptance rehearsal. 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.
B:Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. That explanation applies to the different Martian-address acceptance scenario rather than this controlled acceptance rehearsal. 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:Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. That explanation applies to the different RIB group forwarding copy scenario rather than this controlled acceptance rehearsal. 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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests