Question 350
During production incident triage, 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. An engineer suggests the shortcut: "Remove the LAN from every OSPF configuration to stop the Hellos." Which critique explains the specific risk of that shortcut?
- BGP keepalive changes do not resolve an OSPF interface timer mismatch.
- Removing the interface entirely can also remove the necessary prefix advertisement.
- SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility.
- A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.
Explanation
Correct Answer
B:Removing the interface entirely can also remove the necessary prefix advertisement. In this live production incident the shortcut was explicitly proposed as: Remove the LAN from every OSPF configuration to stop the Hellos. It fails to resolve the underlying problem that Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. A sound alternative is the targeted engineering action: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
Incorrect Answers
A:BGP keepalive changes do not resolve an OSPF interface timer mismatch. That critique concerns a shortcut from the unrelated OSPF hello dead timer mismatch case. The shortcut actually proposed in this live production incident is: Remove the LAN from every OSPF configuration to stop the Hellos. It should be rejected for the narrower reason that Removing the interface entirely can also remove the necessary prefix advertisement. This distinction matters because Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
C:SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. That critique concerns a shortcut from the unrelated DR priority zero misconception case. The shortcut actually proposed in this live production incident is: Remove the LAN from every OSPF configuration to stop the Hellos. It should be rejected for the narrower reason that Removing the interface entirely can also remove the necessary prefix advertisement. This distinction matters because Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
D:A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. That critique concerns a shortcut from the unrelated OSPF LSDB discrepancy case. The shortcut actually proposed in this live production incident is: Remove the LAN from every OSPF configuration to stop the Hellos. It should be rejected for the narrower reason that Removing the interface entirely can also remove the necessary prefix advertisement. This distinction matters because Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
Question 351
During production incident triage, 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. An engineer suggests the shortcut: "Raise IPv4 local preference but do not configure IPv6 BGP family." Which critique explains the specific risk of that shortcut?
- IPv4 routing entries cannot replace the missing IPv6 prefix advertisements.
- IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path.
- IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement.
- Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery.
Explanation
Correct Answer
C:IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. In this live production incident the shortcut was explicitly proposed as: Raise IPv4 local preference but do not configure IPv6 BGP family. It fails to resolve the underlying problem that BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. A sound alternative is the targeted engineering action: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.
Incorrect Answers
A:IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. That critique concerns a shortcut from the unrelated IS-IS IPv6 reachability TLVs case. The shortcut actually proposed in this live production incident is: Raise IPv4 local preference but do not configure IPv6 BGP family. It should be rejected for the narrower reason that IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. This distinction matters because BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
B:IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. That critique concerns a shortcut from the unrelated IPv6 over IPv4 transit tunnel case. The shortcut actually proposed in this live production incident is: Raise IPv4 local preference but do not configure IPv6 BGP family. It should be rejected for the narrower reason that IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. This distinction matters because BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
D:Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery. That critique concerns a shortcut from the unrelated ICMPv6 packet-too-big handling case. The shortcut actually proposed in this live production incident is: Raise IPv4 local preference but do not configure IPv6 BGP family. It should be rejected for the narrower reason that IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. This distinction matters because BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
Question 352
During production incident triage, engineers observe: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. An engineer suggests the shortcut: "Increase application payload size while ignoring the tunnel-header overhead." Which critique explains the specific risk of that shortcut?
- Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path.
- Larger packets increase the encapsulation MTU violation and do not solve delivery.
- Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon.
- Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer.
Explanation
Correct Answer
B:Larger packets increase the encapsulation MTU violation and do not solve delivery. In this live production incident the shortcut was explicitly proposed as: Increase application payload size while ignoring the tunnel-header overhead. It fails to resolve the underlying problem that GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. A sound alternative is the targeted engineering action: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
Incorrect Answers
A:Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. That critique concerns a shortcut from the unrelated GRE tunnel endpoint mismatch case. The shortcut actually proposed in this live production incident is: Increase application payload size while ignoring the tunnel-header overhead. It should be rejected for the narrower reason that Larger packets increase the encapsulation MTU violation and do not solve delivery. This distinction matters because GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
C:Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. That critique concerns a shortcut from the unrelated GRE underlay recursive loss case. The shortcut actually proposed in this live production incident is: Increase application payload size while ignoring the tunnel-header overhead. It should be rejected for the narrower reason that Larger packets increase the encapsulation MTU violation and do not solve delivery. This distinction matters because GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
D:Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. That critique concerns a shortcut from the unrelated GRE confidentiality misconception case. The shortcut actually proposed in this live production incident is: Increase application payload size while ignoring the tunnel-header overhead. It should be rejected for the narrower reason that Larger packets increase the encapsulation MTU violation and do not solve delivery. This distinction matters because GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
Question 353
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. An engineer suggests the shortcut: "Set identical router IDs on all peers to force the lowest MED to win." Which critique explains the specific risk of that shortcut?
- Local preference governs route choice and does not change TCP source address or peer reachability.
- ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing.
- Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy.
- Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks.
Explanation
Correct Answer
C:Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. In this live production incident the shortcut was explicitly proposed as: Set identical router IDs on all peers to force the lowest MED to win. It fails to resolve the underlying problem that BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. A sound alternative is the targeted engineering action: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
Incorrect Answers
A:Local preference governs route choice and does not change TCP source address or peer reachability. That critique concerns a shortcut from the unrelated IBGP loopback source resolution case. The shortcut actually proposed in this live production incident is: Set identical router IDs on all peers to force the lowest MED to win. It should be rejected for the narrower reason that Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. This distinction matters because BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
B:ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. That critique concerns a shortcut from the unrelated EBGP multihop peering case. The shortcut actually proposed in this live production incident is: Set identical router IDs on all peers to force the lowest MED to win. It should be rejected for the narrower reason that Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. This distinction matters because BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
D:Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks. That critique concerns a shortcut from the unrelated BGP export policy omission case. The shortcut actually proposed in this live production incident is: Set identical router IDs on all peers to force the lowest MED to win. It should be rejected for the narrower reason that Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. This distinction matters because BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
Question 354
During production incident triage, engineers observe: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. An engineer suggests the shortcut: "Increase interface descriptions on both links until they look symmetric." Which critique explains the specific risk of that shortcut?
- Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.
- Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk.
- Hostname changes do not import a route between separate routing information bases.
- Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility.
Explanation
Correct Answer
D:Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. In this live production incident the shortcut was explicitly proposed as: Increase interface descriptions on both links until they look symmetric. It fails to resolve the underlying problem that ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. A sound alternative is the targeted engineering action: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
Incorrect Answers
A:Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. That critique concerns a shortcut from the unrelated Administrative preference overrides static case. The shortcut actually proposed in this live production incident is: Increase interface descriptions on both links until they look symmetric. It should be rejected for the narrower reason that Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. This distinction matters because ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
B:Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. That critique concerns a shortcut from the unrelated Martian-address acceptance case. The shortcut actually proposed in this live production incident is: Increase interface descriptions on both links until they look symmetric. It should be rejected for the narrower reason that Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. This distinction matters because ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
C:Hostname changes do not import a route between separate routing information bases. That critique concerns a shortcut from the unrelated RIB group forwarding copy case. The shortcut actually proposed in this live production incident is: Increase interface descriptions on both links until they look symmetric. It should be rejected for the narrower reason that Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. This distinction matters because ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
Question 355
During production incident triage, engineers observe: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. An engineer suggests the shortcut: "Add a permanent static route for every intermittent IS-IS destination." Which critique explains the specific risk of that shortcut?
- Changing interface labels cannot repair conflicting protocol system identities.
- Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
- OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
- Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes.
Explanation
Correct Answer
D:Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. In this live production incident the shortcut was explicitly proposed as: Add a permanent static route for every intermittent IS-IS destination. It fails to resolve the underlying problem that IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. A sound alternative is the targeted engineering action: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
Incorrect Answers
A:Changing interface labels cannot repair conflicting protocol system identities. That critique concerns a shortcut from the unrelated Duplicate IS-IS system ID case. The shortcut actually proposed in this live production incident is: Add a permanent static route for every intermittent IS-IS destination. It should be rejected for the narrower reason that Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. This distinction matters because IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
B:Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. That critique concerns a shortcut from the unrelated IS-IS narrow metric ceiling case. The shortcut actually proposed in this live production incident is: Add a permanent static route for every intermittent IS-IS destination. It should be rejected for the narrower reason that Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. This distinction matters because IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
C:OSPF election settings are unrelated to IS-IS DIS selection on the LAN. That critique concerns a shortcut from the unrelated IS-IS DIS election surprise case. The shortcut actually proposed in this live production incident is: Add a permanent static route for every intermittent IS-IS destination. It should be rejected for the narrower reason that Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. This distinction matters because IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
Question 356
During production incident triage, engineers observe: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. An engineer suggests the shortcut: "Repeatedly clear the OSPF process without fixing the MTU mismatch." Which critique explains the specific risk of that shortcut?
- BGP keepalive changes do not resolve an OSPF interface timer mismatch.
- A process reset can temporarily restart negotiation but leaves the same incompatibility in place.
- A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.
- Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.
Explanation
Correct Answer
B:A process reset can temporarily restart negotiation but leaves the same incompatibility in place. In this live production incident the shortcut was explicitly proposed as: Repeatedly clear the OSPF process without fixing the MTU mismatch. It fails to resolve the underlying problem that OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. A sound alternative is the targeted engineering action: Correct the actual transport MTU mismatch across the link, then validate database description exchange.
Incorrect Answers
A:BGP keepalive changes do not resolve an OSPF interface timer mismatch. That critique concerns a shortcut from the unrelated OSPF hello dead timer mismatch case. The shortcut actually proposed in this live production incident is: Repeatedly clear the OSPF process without fixing the MTU mismatch. It should be rejected for the narrower reason that A process reset can temporarily restart negotiation but leaves the same incompatibility in place. This distinction matters because OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
C:A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. That critique concerns a shortcut from the unrelated OSPF LSDB discrepancy case. The shortcut actually proposed in this live production incident is: Repeatedly clear the OSPF process without fixing the MTU mismatch. It should be rejected for the narrower reason that A process reset can temporarily restart negotiation but leaves the same incompatibility in place. This distinction matters because OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
D:Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. That critique concerns a shortcut from the unrelated OSPF authentication key mismatch case. The shortcut actually proposed in this live production incident is: Repeatedly clear the OSPF process without fixing the MTU mismatch. It should be rejected for the narrower reason that A process reset can temporarily restart negotiation but leaves the same incompatibility in place. This distinction matters because OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
Question 357
During production incident triage, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. An engineer suggests the shortcut: "Change OSPF DR priority to manipulate BGP AS-path selection." Which critique explains the specific risk of that shortcut?
- Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable.
- Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session.
- OSPF LAN DR election settings do not modify the BGP path attributes being compared.
- ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing.
Explanation
Correct Answer
C:OSPF LAN DR election settings do not modify the BGP path attributes being compared. In this live production incident the shortcut was explicitly proposed as: Change OSPF DR priority to manipulate BGP AS-path selection. It fails to resolve the underlying problem that When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. A sound alternative is the targeted engineering action: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
Incorrect Answers
A:Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. That critique concerns a shortcut from the unrelated BGP peer autonomous system mismatch case. The shortcut actually proposed in this live production incident is: Change OSPF DR priority to manipulate BGP AS-path selection. It should be rejected for the narrower reason that OSPF LAN DR election settings do not modify the BGP path attributes being compared. This distinction matters because When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
B:Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. That critique concerns a shortcut from the unrelated BGP TCP transport blocked case. The shortcut actually proposed in this live production incident is: Change OSPF DR priority to manipulate BGP AS-path selection. It should be rejected for the narrower reason that OSPF LAN DR election settings do not modify the BGP path attributes being compared. This distinction matters because When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
D:ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. That critique concerns a shortcut from the unrelated EBGP multihop peering case. The shortcut actually proposed in this live production incident is: Change OSPF DR priority to manipulate BGP AS-path selection. It should be rejected for the narrower reason that OSPF LAN DR election settings do not modify the BGP path attributes being compared. This distinction matters because When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
Question 358
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. An engineer suggests the shortcut: "Use the GRE tunnel itself as the only path to reach its outer destination." Which critique explains the specific risk of that shortcut?
- Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer.
- Larger packets increase the encapsulation MTU violation and do not solve delivery.
- Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon.
- Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path.
Explanation
Correct Answer
C:Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. In this live production incident the shortcut was explicitly proposed as: Use the GRE tunnel itself as the only path to reach its outer destination. It fails to resolve the underlying problem that GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. A sound alternative is the targeted engineering action: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
Incorrect Answers
A:Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. That critique concerns a shortcut from the unrelated GRE confidentiality misconception case. The shortcut actually proposed in this live production incident is: Use the GRE tunnel itself as the only path to reach its outer destination. It should be rejected for the narrower reason that Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. This distinction matters because GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
B:Larger packets increase the encapsulation MTU violation and do not solve delivery. That critique concerns a shortcut from the unrelated GRE encapsulation MTU overhead case. The shortcut actually proposed in this live production incident is: Use the GRE tunnel itself as the only path to reach its outer destination. It should be rejected for the narrower reason that Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. This distinction matters because GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
D:Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. That critique concerns a shortcut from the unrelated GRE tunnel endpoint mismatch case. The shortcut actually proposed in this live production incident is: Use the GRE tunnel itself as the only path to reach its outer destination. It should be rejected for the narrower reason that Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. This distinction matters because GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
Question 359
During production incident triage, engineers observe: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. An engineer suggests the shortcut: "Add a static default route in every tenant to conceal the leaked routes." Which critique explains the specific risk of that shortcut?
- Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
- More defaults can increase unintended connectivity without removing unauthorized route imports.
- Hostname changes do not import a route between separate routing information bases.
- Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.
Explanation
Correct Answer
B:More defaults can increase unintended connectivity without removing unauthorized route imports. In this live production incident the shortcut was explicitly proposed as: Add a static default route in every tenant to conceal the leaked routes. It fails to resolve the underlying problem that Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. A sound alternative is the targeted engineering action: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
Incorrect Answers
A:Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. That critique concerns a shortcut from the unrelated Static backup blackhole case. The shortcut actually proposed in this live production incident is: Add a static default route in every tenant to conceal the leaked routes. It should be rejected for the narrower reason that More defaults can increase unintended connectivity without removing unauthorized route imports. This distinction matters because Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
C:Hostname changes do not import a route between separate routing information bases. That critique concerns a shortcut from the unrelated RIB group forwarding copy case. The shortcut actually proposed in this live production incident is: Add a static default route in every tenant to conceal the leaked routes. It should be rejected for the narrower reason that More defaults can increase unintended connectivity without removing unauthorized route imports. This distinction matters because Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
D:Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. That critique concerns a shortcut from the unrelated Administrative preference overrides static case. The shortcut actually proposed in this live production incident is: Add a static default route in every tenant to conceal the leaked routes. It should be rejected for the narrower reason that More defaults can increase unintended connectivity without removing unauthorized route imports. This distinction matters because Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
Question 360
During production incident triage, engineers observe: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. An engineer suggests the shortcut: "Enable only interface-level LAG protection and assume routing processes synchronize automatically." Which critique explains the specific risk of that shortcut?
- VLAN membership does not make incompatible LACP peers join a single forwarding aggregate.
- Logical link state does not certify available bandwidth after a partial member failure.
- LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.
- Routing metrics in OSPF do not directly determine VRRP primary election.
Explanation
Correct Answer
C:LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. In this live production incident the shortcut was explicitly proposed as: Enable only interface-level LAG protection and assume routing processes synchronize automatically. It fails to resolve the underlying problem that NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. A sound alternative is the targeted engineering action: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
Incorrect Answers
A:VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. That critique concerns a shortcut from the unrelated LACP partner mismatch case. The shortcut actually proposed in this live production incident is: Enable only interface-level LAG protection and assume routing processes synchronize automatically. It should be rejected for the narrower reason that LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. This distinction matters because NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
B:Logical link state does not certify available bandwidth after a partial member failure. That critique concerns a shortcut from the unrelated LAG member imbalance after failure case. The shortcut actually proposed in this live production incident is: Enable only interface-level LAG protection and assume routing processes synchronize automatically. It should be rejected for the narrower reason that LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. This distinction matters because NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
D:Routing metrics in OSPF do not directly determine VRRP primary election. That critique concerns a shortcut from the unrelated VRRP master priority failover case. The shortcut actually proposed in this live production incident is: Enable only interface-level LAG protection and assume routing processes synchronize automatically. It should be rejected for the narrower reason that LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. This distinction matters because NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests