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.
Question 361
During production incident triage, engineers observe: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. An engineer suggests the shortcut: "Apply an export policy accepting every direct and static route." Which critique explains the specific risk of that shortcut?
- An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility.
- Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops.
- 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.
Explanation
Correct Answer
B:Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. In this live production incident the shortcut was explicitly proposed as: Apply an export policy accepting every direct and static route. It fails to resolve the underlying problem that IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. A sound alternative is the targeted engineering action: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
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: Apply an export policy accepting every direct and static route. It should be rejected for the narrower reason that Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. This distinction matters because IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
C: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: Apply an export policy accepting every direct and static route. It should be rejected for the narrower reason that Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. This distinction matters because IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
D: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: Apply an export policy accepting every direct and static route. It should be rejected for the narrower reason that Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. This distinction matters because IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
Question 362
During production incident triage, engineers observe: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. An engineer suggests the shortcut: "Change an IP route metric in a router to split Layer 2 STP paths." Which critique explains the specific risk of that shortcut?
- Removing STP protection can permit the unauthorized bridge to create a forwarding loop.
- Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles.
- Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link.
- OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election.
Explanation
Correct Answer
B:Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles. In this live production incident the shortcut was explicitly proposed as: Change an IP route metric in a router to split Layer 2 STP paths. It fails to resolve the underlying problem that VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. A sound alternative is the targeted engineering action: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
Incorrect Answers
A:Removing STP protection can permit the unauthorized bridge to create a forwarding loop. That critique concerns a shortcut from the unrelated Unexpected BPDU on edge port case. The shortcut actually proposed in this live production incident is: Change an IP route metric in a router to split Layer 2 STP paths. It should be rejected for the narrower reason that Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles. This distinction matters because VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
C:Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link. That critique concerns a shortcut from the unrelated Loop protection after BPDU loss case. The shortcut actually proposed in this live production incident is: Change an IP route metric in a router to split Layer 2 STP paths. It should be rejected for the narrower reason that Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles. This distinction matters because VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
D: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: Change an IP route metric in a router to split Layer 2 STP paths. It should be rejected for the narrower reason that Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles. This distinction matters because VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
Question 363
During production incident triage, engineers observe: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. An engineer suggests the shortcut: "Enable multipath forwarding in inet.0 without changing the peering transport assumptions." Which critique explains the specific risk of that shortcut?
- A higher preference cannot create a missing recursive path to a BGP next hop.
- ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing.
- 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.
Explanation
Correct Answer
B:ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. In this live production incident the shortcut was explicitly proposed as: Enable multipath forwarding in inet.0 without changing the peering transport assumptions. It fails to resolve the underlying problem that An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. A sound alternative is the targeted engineering action: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
Incorrect Answers
A:A higher preference cannot create a missing recursive path to a BGP next hop. That critique concerns a shortcut from the unrelated BGP next-hop inaccessible case. The shortcut actually proposed in this live production incident is: Enable multipath forwarding in inet.0 without changing the peering transport assumptions. It should be rejected for the narrower reason that ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. This distinction matters because An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
C: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: Enable multipath forwarding in inet.0 without changing the peering transport assumptions. It should be rejected for the narrower reason that ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. This distinction matters because An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
D: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: Enable multipath forwarding in inet.0 without changing the peering transport assumptions. It should be rejected for the narrower reason that ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. This distinction matters because An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
Question 364
During production incident triage, engineers observe: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. An engineer suggests the shortcut: "Modify only OSPFv2 hello timers and expect OSPFv3 to appear." Which critique explains the specific risk of that shortcut?
- Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency.
- IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path.
- Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery.
- IPv4 routing entries cannot replace the missing IPv6 prefix advertisements.
Explanation
Correct Answer
A:Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. In this live production incident the shortcut was explicitly proposed as: Modify only OSPFv2 hello timers and expect OSPFv3 to appear. It fails to resolve the underlying problem that OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. A sound alternative is the targeted engineering action: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
Incorrect Answers
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: Modify only OSPFv2 hello timers and expect OSPFv3 to appear. It should be rejected for the narrower reason that Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. This distinction matters because OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
C: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: Modify only OSPFv2 hello timers and expect OSPFv3 to appear. It should be rejected for the narrower reason that Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. This distinction matters because OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
D: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: Modify only OSPFv2 hello timers and expect OSPFv3 to appear. It should be rejected for the narrower reason that Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. This distinction matters because OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
Question 365
During production incident triage, engineers observe: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. An engineer suggests the shortcut: "Watch only local interface carrier and assume the remote service must be operational." Which critique explains the specific risk of that shortcut?
- BGP timers do not create the aggregate's necessary routing-table contribution.
- Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
- An unconditional default masks missing prerequisites and may direct traffic into an unintended path.
- Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
Explanation
Correct Answer
B:Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. In this live production incident the shortcut was explicitly proposed as: Watch only local interface carrier and assume the remote service must be operational. It fails to resolve the underlying problem that A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. A sound alternative is the targeted engineering action: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
Incorrect Answers
A:BGP timers do not create the aggregate's necessary routing-table contribution. That critique concerns a shortcut from the unrelated Aggregate route contribution case. The shortcut actually proposed in this live production incident is: Watch only local interface carrier and assume the remote service must be operational. It should be rejected for the narrower reason that Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. This distinction matters because A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.
C:An unconditional default masks missing prerequisites and may direct traffic into an unintended path. That critique concerns a shortcut from the unrelated Generated default route prerequisite case. The shortcut actually proposed in this live production incident is: Watch only local interface carrier and assume the remote service must be operational. It should be rejected for the narrower reason that Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. This distinction matters because A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.
D: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: Watch only local interface carrier and assume the remote service must be operational. It should be rejected for the narrower reason that Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. This distinction matters because A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.
Question 366
During production incident triage, engineers observe: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. An engineer suggests the shortcut: "Treat a route's mere appearance in a protocol database as evidence of successful forwarding." Which critique explains the specific risk of that shortcut?
- Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
- Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
- Presence in a control-plane view does not prove active route selection or packet forwarding installation.
- Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.
Explanation
Correct Answer
C:Presence in a control-plane view does not prove active route selection or packet forwarding installation. In this live production incident the shortcut was explicitly proposed as: Treat a route's mere appearance in a protocol database as evidence of successful forwarding. It fails to resolve the underlying problem that Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. A sound alternative is the targeted engineering action: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.
Incorrect Answers
A: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: Treat a route's mere appearance in a protocol database as evidence of successful forwarding. It should be rejected for the narrower reason that Presence in a control-plane view does not prove active route selection or packet forwarding installation. This distinction matters because Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.
B: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: Treat a route's mere appearance in a protocol database as evidence of successful forwarding. It should be rejected for the narrower reason that Presence in a control-plane view does not prove active route selection or packet forwarding installation. This distinction matters because Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.
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: Treat a route's mere appearance in a protocol database as evidence of successful forwarding. It should be rejected for the narrower reason that Presence in a control-plane view does not prove active route selection or packet forwarding installation. This distinction matters because Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.
Question 367
During production incident triage, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. An engineer suggests the shortcut: "Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag." Which critique explains the specific risk of that shortcut?
- MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding.
- Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.
- A duplicate name does not move frames into the intended instance and can increase configuration confusion.
- Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved.
Explanation
Correct Answer
D:Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. In this live production incident the shortcut was explicitly proposed as: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It fails to resolve the underlying problem that Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. A sound alternative is the targeted engineering action: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.
Incorrect Answers
A:MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. That critique concerns a shortcut from the unrelated IRB routed gateway missing case. The shortcut actually proposed in this live production incident is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
B:Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. That critique concerns a shortcut from the unrelated Unknown unicast flooding behavior case. The shortcut actually proposed in this live production incident is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
C:A duplicate name does not move frames into the intended instance and can increase configuration confusion. That critique concerns a shortcut from the unrelated Virtual switch instance membership case. The shortcut actually proposed in this live production incident is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
Question 368
During production incident triage, engineers observe: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. An engineer suggests the shortcut: "Increase OSPF router ID on the core switch to influence the STP root." Which critique explains the specific risk of that shortcut?
- Removing STP protection can permit the unauthorized bridge to create a forwarding loop.
- Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link.
- Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm.
- OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election.
Explanation
Correct Answer
D:OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. In this live production incident the shortcut was explicitly proposed as: Increase OSPF router ID on the core switch to influence the STP root. It fails to resolve the underlying problem that Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. A sound alternative is the targeted engineering action: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.
Incorrect Answers
A:Removing STP protection can permit the unauthorized bridge to create a forwarding loop. That critique concerns a shortcut from the unrelated Unexpected BPDU on edge port case. The shortcut actually proposed in this live production incident is: Increase OSPF router ID on the core switch to influence the STP root. It should be rejected for the narrower reason that OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. This distinction matters because Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
B:Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link. That critique concerns a shortcut from the unrelated Loop protection after BPDU loss case. The shortcut actually proposed in this live production incident is: Increase OSPF router ID on the core switch to influence the STP root. It should be rejected for the narrower reason that OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. This distinction matters because Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
C:Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm. That critique concerns a shortcut from the unrelated RSTP alternate port activation case. The shortcut actually proposed in this live production incident is: Increase OSPF router ID on the core switch to influence the STP root. It should be rejected for the narrower reason that OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. This distinction matters because Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
Question 369
During production incident triage, 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. An engineer suggests the shortcut: "Clear overload immediately at boot before route and forwarding synchronization." Which critique explains the specific risk of that shortcut?
- Broad deactivation removes protections and can expose the link-state domain to untrusted control packets.
- Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops.
- Premature transit eligibility can blackhole traffic while the node has incomplete routing state.
- Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy.
Explanation
Correct Answer
C:Premature transit eligibility can blackhole traffic while the node has incomplete routing state. In this live production incident the shortcut was explicitly proposed as: Clear overload immediately at boot before route and forwarding synchronization. It fails to resolve the underlying problem that An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. A sound alternative is the targeted engineering action: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
Incorrect Answers
A:Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. That critique concerns a shortcut from the unrelated IS-IS authentication mismatch case. The shortcut actually proposed in this live production incident is: Clear overload immediately at boot before route and forwarding synchronization. It should be rejected for the narrower reason that Premature transit eligibility can blackhole traffic while the node has incomplete routing state. This distinction matters because An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
B:Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. That critique concerns a shortcut from the unrelated IS-IS route export scope case. The shortcut actually proposed in this live production incident is: Clear overload immediately at boot before route and forwarding synchronization. It should be rejected for the narrower reason that Premature transit eligibility can blackhole traffic while the node has incomplete routing state. This distinction matters because An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
D:Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. That critique concerns a shortcut from the unrelated IS-IS Level 1 exit default case. The shortcut actually proposed in this live production incident is: Clear overload immediately at boot before route and forwarding synchronization. It should be rejected for the narrower reason that Premature transit eligibility can blackhole traffic while the node has incomplete routing state. This distinction matters because An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
Question 370
During production incident triage, engineers observe: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. An engineer suggests the shortcut: "Change OSPF cost only while ignoring VRRP priority and virtual-router state." 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.
- Logical link state does not certify available bandwidth after a partial member failure.
- Unreasonably small intervals can cause false liveness failures and repeated routing churn.
Explanation
Correct Answer
B:Routing metrics in OSPF do not directly determine VRRP primary election. In this live production incident the shortcut was explicitly proposed as: Change OSPF cost only while ignoring VRRP priority and virtual-router state. It fails to resolve the underlying problem that VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. A sound alternative is the targeted engineering action: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
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: Change OSPF cost only while ignoring VRRP priority and virtual-router state. It should be rejected for the narrower reason that Routing metrics in OSPF do not directly determine VRRP primary election. This distinction matters because VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
C: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: Change OSPF cost only while ignoring VRRP priority and virtual-router state. It should be rejected for the narrower reason that Routing metrics in OSPF do not directly determine VRRP primary election. This distinction matters because VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
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: Change OSPF cost only while ignoring VRRP priority and virtual-router state. It should be rejected for the narrower reason that Routing metrics in OSPF do not directly determine VRRP primary election. This distinction matters because VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests