Question 310
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. An engineer suggests the shortcut: "Keep legacy narrow metrics but set a higher impossible value in planning documents." Which critique explains the specific risk of that shortcut?
- An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility.
- Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
- Route preference affects installation of received routes, not which IS-IS levels can form an adjacency.
- Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.
Explanation
Correct Answer
B:Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. In this live production incident the shortcut was explicitly proposed as: Keep legacy narrow metrics but set a higher impossible value in planning documents. It fails to resolve the underlying problem that IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. A sound alternative is the targeted engineering action: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
Incorrect Answers
A:An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. That critique concerns a shortcut from the unrelated IS-IS level-one area mismatch case. The shortcut actually proposed in this live production incident is: Keep legacy narrow metrics but set a higher impossible value in planning documents. It should be rejected for the narrower reason that Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. This distinction matters because IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
C:Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. That critique concerns a shortcut from the unrelated IS-IS level capability mismatch case. The shortcut actually proposed in this live production incident is: Keep legacy narrow metrics but set a higher impossible value in planning documents. It should be rejected for the narrower reason that Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. This distinction matters because IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
D:Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. That critique concerns a shortcut from the unrelated IS-IS ISO family missing case. The shortcut actually proposed in this live production incident is: Keep legacy narrow metrics but set a higher impossible value in planning documents. It should be rejected for the narrower reason that Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. This distinction matters because IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
Question 311
During production incident triage, engineers observe: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. An engineer suggests the shortcut: "Only change the OSPF reference bandwidth on one router." Which critique explains the specific risk of that shortcut?
- 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.
- Blanket redistribution can expose management and unrelated customer networks and create routing instability.
- Reference bandwidth affects metric calculation, not the area ID carried in Hello packets.
Explanation
Correct Answer
D:Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. In this live production incident the shortcut was explicitly proposed as: Only change the OSPF reference bandwidth on one router. It fails to resolve the underlying problem that OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. A sound alternative is the targeted engineering action: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
Incorrect Answers
A: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: Only change the OSPF reference bandwidth on one router. It should be rejected for the narrower reason that Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. This distinction matters because OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
B: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: Only change the OSPF reference bandwidth on one router. It should be rejected for the narrower reason that Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. This distinction matters because OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
C:Blanket redistribution can expose management and unrelated customer networks and create routing instability. That critique concerns a shortcut from the unrelated OSPF export policy omission case. The shortcut actually proposed in this live production incident is: Only change the OSPF reference bandwidth on one router. It should be rejected for the narrower reason that Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. This distinction matters because OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
Question 312
During production incident triage, engineers observe: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. An engineer suggests the shortcut: "Increase the BGP keepalive rate and assume the route will be forwarded." Which critique explains the specific risk of that shortcut?
- Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session.
- Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
- Session liveness timers do not change IBGP route propagation rules.
- OSPF LAN DR election settings do not modify the BGP path attributes being compared.
Explanation
Correct Answer
C:Session liveness timers do not change IBGP route propagation rules. In this live production incident the shortcut was explicitly proposed as: Increase the BGP keepalive rate and assume the route will be forwarded. It fails to resolve the underlying problem that Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. A sound alternative is the targeted engineering action: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
Incorrect Answers
A: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: Increase the BGP keepalive rate and assume the route will be forwarded. It should be rejected for the narrower reason that Session liveness timers do not change IBGP route propagation rules. This distinction matters because Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
B:Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. That critique concerns a shortcut from the unrelated BGP import policy leak case. The shortcut actually proposed in this live production incident is: Increase the BGP keepalive rate and assume the route will be forwarded. It should be rejected for the narrower reason that Session liveness timers do not change IBGP route propagation rules. This distinction matters because Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
D:OSPF LAN DR election settings do not modify the BGP path attributes being compared. That critique concerns a shortcut from the unrelated BGP AS-path comparison case. The shortcut actually proposed in this live production incident is: Increase the BGP keepalive rate and assume the route will be forwarded. It should be rejected for the narrower reason that Session liveness timers do not change IBGP route propagation rules. This distinction matters because Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
Question 313
During production incident triage, engineers observe: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. An engineer suggests the shortcut: "Force an unrelated VLAN trunk membership without fixing the LACP mismatch." Which critique explains the specific risk of that shortcut?
- VLAN membership does not make incompatible LACP peers join a single forwarding aggregate.
- Routing metrics in OSPF do not directly determine VRRP primary election.
- Aggressive preemption repeats the same transient blackhole while the upstream path remains unready.
- Unreasonably small intervals can cause false liveness failures and repeated routing churn.
Explanation
Correct Answer
A:VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. In this live production incident the shortcut was explicitly proposed as: Force an unrelated VLAN trunk membership without fixing the LACP mismatch. It fails to resolve the underlying problem that LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. A sound alternative is the targeted engineering action: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
Incorrect Answers
B: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: Force an unrelated VLAN trunk membership without fixing the LACP mismatch. It should be rejected for the narrower reason that VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. This distinction matters because LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
C:Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. That critique concerns a shortcut from the unrelated VRRP preemption oscillation case. The shortcut actually proposed in this live production incident is: Force an unrelated VLAN trunk membership without fixing the LACP mismatch. It should be rejected for the narrower reason that VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. This distinction matters because LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
D:Unreasonably small intervals can cause false liveness failures and repeated routing churn. That critique concerns a shortcut from the unrelated BFD detect timer too aggressive case. The shortcut actually proposed in this live production incident is: Force an unrelated VLAN trunk membership without fixing the LACP mismatch. It should be rejected for the narrower reason that VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. This distinction matters because LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
Question 314
During production incident triage, engineers observe: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. An engineer suggests the shortcut: "Disable the session's logs and assume the missing errors mean the timer problem disappeared." Which critique explains the specific risk of that shortcut?
- MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS.
- OSPF LAN DR election settings do not modify the BGP path attributes being compared.
- Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy.
- Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers.
Explanation
Correct Answer
D:Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers. In this live production incident the shortcut was explicitly proposed as: Disable the session's logs and assume the missing errors mean the timer problem disappeared. It fails to resolve the underlying problem that BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. A sound alternative is the targeted engineering action: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.
Incorrect Answers
A:MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. That critique concerns a shortcut from the unrelated BGP local preference egress case. The shortcut actually proposed in this live production incident is: Disable the session's logs and assume the missing errors mean the timer problem disappeared. It should be rejected for the narrower reason that Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers. This distinction matters because BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
B:OSPF LAN DR election settings do not modify the BGP path attributes being compared. That critique concerns a shortcut from the unrelated BGP AS-path comparison case. The shortcut actually proposed in this live production incident is: Disable the session's logs and assume the missing errors mean the timer problem disappeared. It should be rejected for the narrower reason that Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers. This distinction matters because BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
C:Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. That critique concerns a shortcut from the unrelated BGP MED comparison scope case. The shortcut actually proposed in this live production incident is: Disable the session's logs and assume the missing errors mean the timer problem disappeared. It should be rejected for the narrower reason that Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers. This distinction matters because BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
Question 315
During production incident triage, engineers observe: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. An engineer suggests the shortcut: "Force all redundant ports into permanent forwarding state." Which critique explains the specific risk of that shortcut?
- Descriptions do not participate in MSTP region identification or instance mapping.
- OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election.
- Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm.
- MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election.
Explanation
Correct Answer
C:Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm. In this live production incident the shortcut was explicitly proposed as: Force all redundant ports into permanent forwarding state. It fails to resolve the underlying problem that RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. A sound alternative is the targeted engineering action: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
Incorrect Answers
A:Descriptions do not participate in MSTP region identification or instance mapping. That critique concerns a shortcut from the unrelated MSTP region mismatch case. The shortcut actually proposed in this live production incident is: Force all redundant ports into permanent forwarding state. It should be rejected for the narrower reason that Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm. This distinction matters because RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
B:OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. That critique concerns a shortcut from the unrelated Root bridge election priority case. The shortcut actually proposed in this live production incident is: Force all redundant ports into permanent forwarding state. It should be rejected for the narrower reason that Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm. This distinction matters because RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
D:MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. That critique concerns a shortcut from the unrelated Root protection against rogue core case. The shortcut actually proposed in this live production incident is: Force all redundant ports into permanent forwarding state. It should be rejected for the narrower reason that Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm. This distinction matters because RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
Question 316
During production incident triage, engineers observe: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. An engineer suggests the shortcut: "Increase MAC learning timeout and assume routing between VLANs will start." Which critique explains the specific risk of that shortcut?
- MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding.
- An aging change cannot prevent contradictory source-MAC observations on multiple ports.
- IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong.
- Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved.
Explanation
Correct Answer
A:MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. In this live production incident the shortcut was explicitly proposed as: Increase MAC learning timeout and assume routing between VLANs will start. It fails to resolve the underlying problem that An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. A sound alternative is the targeted engineering action: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.
Incorrect Answers
B:An aging change cannot prevent contradictory source-MAC observations on multiple ports. That critique concerns a shortcut from the unrelated MAC move instability case. The shortcut actually proposed in this live production incident is: Increase MAC learning timeout and assume routing between VLANs will start. It should be rejected for the narrower reason that MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. This distinction matters because An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
C:IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. That critique concerns a shortcut from the unrelated Flexible VLAN tagging logical units case. The shortcut actually proposed in this live production incident is: Increase MAC learning timeout and assume routing between VLANs will start. It should be rejected for the narrower reason that MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. This distinction matters because An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
D:Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. That critique concerns a shortcut from the unrelated Q-in-Q outer tag mismatch case. The shortcut actually proposed in this live production incident is: Increase MAC learning timeout and assume routing between VLANs will start. It should be rejected for the narrower reason that MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. This distinction matters because An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
Question 317
During production incident triage, engineers observe: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. An engineer suggests the shortcut: "Change only the BGP local preference while keeping the incorrect source." Which critique explains the specific risk of that shortcut?
- 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.
- Local preference governs route choice and does not change TCP source address or peer reachability.
- Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
Explanation
Correct Answer
C:Local preference governs route choice and does not change TCP source address or peer reachability. In this live production incident the shortcut was explicitly proposed as: Change only the BGP local preference while keeping the incorrect source. It fails to resolve the underlying problem that IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. A sound alternative is the targeted engineering action: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
Incorrect Answers
A:Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. That critique concerns a shortcut from the unrelated BGP MED comparison scope case. The shortcut actually proposed in this live production incident is: Change only the BGP local preference while keeping the incorrect source. It should be rejected for the narrower reason that Local preference governs route choice and does not change TCP source address or peer reachability. This distinction matters because IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.
B: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: Change only the BGP local preference while keeping the incorrect source. It should be rejected for the narrower reason that Local preference governs route choice and does not change TCP source address or peer reachability. This distinction matters because IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.
D:Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. That critique concerns a shortcut from the unrelated BGP import policy leak case. The shortcut actually proposed in this live production incident is: Change only the BGP local preference while keeping the incorrect source. It should be rejected for the narrower reason that Local preference governs route choice and does not change TCP source address or peer reachability. This distinction matters because IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.
Question 318
During production incident triage, engineers observe: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. An engineer suggests the shortcut: "Force rapid repeated role changes without checking upstream readiness." Which critique explains the specific risk of that shortcut?
- VLAN membership does not make incompatible LACP peers join a single forwarding aggregate.
- Aggressive preemption repeats the same transient blackhole while the upstream path remains unready.
- Unreasonably small intervals can cause false liveness failures and repeated routing churn.
- A gateway-election priority has no role in preserving the chassis routing protocol state across RE change.
Explanation
Correct Answer
B:Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. In this live production incident the shortcut was explicitly proposed as: Force rapid repeated role changes without checking upstream readiness. It fails to resolve the underlying problem that VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. A sound alternative is the targeted engineering action: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
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: Force rapid repeated role changes without checking upstream readiness. It should be rejected for the narrower reason that Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. This distinction matters because VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
C:Unreasonably small intervals can cause false liveness failures and repeated routing churn. That critique concerns a shortcut from the unrelated BFD detect timer too aggressive case. The shortcut actually proposed in this live production incident is: Force rapid repeated role changes without checking upstream readiness. It should be rejected for the narrower reason that Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. This distinction matters because VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
D:A gateway-election priority has no role in preserving the chassis routing protocol state across RE change. That critique concerns a shortcut from the unrelated GRES forwarding versus routing continuity case. The shortcut actually proposed in this live production incident is: Force rapid repeated role changes without checking upstream readiness. It should be rejected for the narrower reason that Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. This distinction matters because VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
Question 319
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. An engineer suggests the shortcut: "Force external LSAs into the stub by indiscriminate route export." Which critique explains the specific risk of that shortcut?
- BGP keepalive changes do not resolve an OSPF interface timer mismatch.
- Blindly redistributing external information conflicts with the intended stub-area containment model.
- 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:Blindly redistributing external information conflicts with the intended stub-area containment model. In this live production incident the shortcut was explicitly proposed as: Force external LSAs into the stub by indiscriminate route export. It fails to resolve the underlying problem that OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. A sound alternative is the targeted engineering action: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
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: Force external LSAs into the stub by indiscriminate route export. It should be rejected for the narrower reason that Blindly redistributing external information conflicts with the intended stub-area containment model. This distinction matters because OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.
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: Force external LSAs into the stub by indiscriminate route export. It should be rejected for the narrower reason that Blindly redistributing external information conflicts with the intended stub-area containment model. This distinction matters because OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.
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: Force external LSAs into the stub by indiscriminate route export. It should be rejected for the narrower reason that Blindly redistributing external information conflicts with the intended stub-area containment model. This distinction matters because OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.
Question 320
During production incident triage, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. An engineer suggests the shortcut: "Change the route description and leave the unresolved next hop unchanged." Which critique explains the specific risk of that shortcut?
- Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
- A text description has no effect on recursive route resolution and cannot install a usable forwarding entry.
- Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
- More routes in the original table do not implement selective forwarding through a different routing table.
Explanation
Correct Answer
B:A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. In this live production incident the shortcut was explicitly proposed as: Change the route description and leave the unresolved next hop unchanged. It fails to resolve the underlying problem that A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. A sound alternative is the targeted engineering action: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
Incorrect Answers
A:Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. That critique concerns a shortcut from the unrelated Aggregate rejection behavior case. The shortcut actually proposed in this live production incident is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
C:Forcing packets of one flow onto different paths can reorder packets and harm transport performance. That critique concerns a shortcut from the unrelated Per-flow hash expectation case. The shortcut actually proposed in this live production incident is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
D:More routes in the original table do not implement selective forwarding through a different routing table. That critique concerns a shortcut from the unrelated Filter-based forwarding classification case. The shortcut actually proposed in this live production incident is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests