Question 830
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- 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.
- LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.
Explanation
Correct Answer
D:LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. In this controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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.
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 controlled acceptance rehearsal 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 831
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. An engineer suggests the shortcut: "Add more IPv4 routes without enabling IPv6 IS-IS reachability." Which critique explains the specific risk of that shortcut?
- IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path.
- IPv4 routing entries cannot replace the missing IPv6 prefix advertisements.
- Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery.
- Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency.
Explanation
Correct Answer
B:IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add more IPv4 routes without enabling IPv6 IS-IS reachability. It fails to resolve the underlying problem that IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. A sound alternative is the targeted engineering action: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
Incorrect Answers
A: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 controlled acceptance rehearsal is: Add more IPv4 routes without enabling IPv6 IS-IS reachability. It should be rejected for the narrower reason that IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. This distinction matters because IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
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 controlled acceptance rehearsal is: Add more IPv4 routes without enabling IPv6 IS-IS reachability. It should be rejected for the narrower reason that IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. This distinction matters because IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
D:Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. That critique concerns a shortcut from the unrelated OSPFv3 neighbor uses link-local case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add more IPv4 routes without enabling IPv6 IS-IS reachability. It should be rejected for the narrower reason that IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. This distinction matters because IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
Question 832
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. An engineer suggests the shortcut: "Add an extra IPv4 secondary address as a substitute for ISO interface support." Which critique explains the specific risk of that shortcut?
- Changing interface labels cannot repair conflicting protocol system identities.
- Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.
- Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
- Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy.
Explanation
Correct Answer
B:Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add an extra IPv4 secondary address as a substitute for ISO interface support. It fails to resolve the underlying problem that Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. A sound alternative is the targeted engineering action: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
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 controlled acceptance rehearsal is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
C: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 controlled acceptance rehearsal is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
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 controlled acceptance rehearsal is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
Question 833
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Routing metrics in OSPF do not directly determine VRRP primary election.
- 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.
- LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.
Explanation
Correct Answer
A:Routing metrics in OSPF do not directly determine VRRP primary election. In this controlled acceptance rehearsal 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
B: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 controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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:LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. That critique concerns a shortcut from the unrelated NSR backup routing synchronization case. The shortcut actually proposed in this controlled acceptance rehearsal 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.
Question 834
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. An engineer suggests the shortcut: "Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming." Which critique explains the specific risk of that shortcut?
- Additional network-layer routes cannot substitute for the required LDP session transport.
- IP addressing does not repair the label operation needed at a transit LSR.
- PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
- One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP.
Explanation
Correct Answer
D:One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming. It fails to resolve the underlying problem that RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. A sound alternative is the targeted engineering action: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
Incorrect Answers
A:Additional network-layer routes cannot substitute for the required LDP session transport. That critique concerns a shortcut from the unrelated LDP TCP 646 establishment case. The shortcut actually proposed in this controlled acceptance rehearsal is: Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming. It should be rejected for the narrower reason that One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. This distinction matters because RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
B:IP addressing does not repair the label operation needed at a transit LSR. That critique concerns a shortcut from the unrelated Incoming label missing in LFIB case. The shortcut actually proposed in this controlled acceptance rehearsal is: Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming. It should be rejected for the narrower reason that One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. This distinction matters because RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
C:PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. That critique concerns a shortcut from the unrelated Penultimate hop popping case. The shortcut actually proposed in this controlled acceptance rehearsal is: Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming. It should be rejected for the narrower reason that One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. This distinction matters because RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
Question 835
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. An engineer suggests the shortcut: "Add a plain IPv4 static route and assume the labeled data path now exists." Which critique explains the specific risk of that shortcut?
- Packet size settings cannot create capacity for an RSVP admission request.
- IP reachability alone does not create MPLS label switching capability on a disabled interface.
- Suppressing alarms cannot provide a precomputed alternate label-switched route.
- One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP.
Explanation
Correct Answer
B:IP reachability alone does not create MPLS label switching capability on a disabled interface. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add a plain IPv4 static route and assume the labeled data path now exists. It fails to resolve the underlying problem that MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. A sound alternative is the targeted engineering action: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
Incorrect Answers
A:Packet size settings cannot create capacity for an RSVP admission request. That critique concerns a shortcut from the unrelated RSVP reservable bandwidth shortage case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add a plain IPv4 static route and assume the labeled data path now exists. It should be rejected for the narrower reason that IP reachability alone does not create MPLS label switching capability on a disabled interface. This distinction matters because MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
C:Suppressing alarms cannot provide a precomputed alternate label-switched route. That critique concerns a shortcut from the unrelated RSVP link protection plan case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add a plain IPv4 static route and assume the labeled data path now exists. It should be rejected for the narrower reason that IP reachability alone does not create MPLS label switching capability on a disabled interface. This distinction matters because MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
D:One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. That critique concerns a shortcut from the unrelated RSVP LSP directionality case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add a plain IPv4 static route and assume the labeled data path now exists. It should be rejected for the narrower reason that IP reachability alone does not create MPLS label switching capability on a disabled interface. This distinction matters because MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
Question 836
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. An engineer suggests the shortcut: "Flood every core prefix as a static route into each Level 1 edge." Which critique explains the specific risk of that shortcut?
- Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy.
- 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.
- Premature transit eligibility can blackhole traffic while the node has incomplete routing state.
Explanation
Correct Answer
A:Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Flood every core prefix as a static route into each Level 1 edge. It fails to resolve the underlying problem that Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. A sound alternative is the targeted engineering action: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
Incorrect Answers
B: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 controlled acceptance rehearsal is: Flood every core prefix as a static route into each Level 1 edge. It should be rejected for the narrower reason that Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. This distinction matters because Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
C:Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. That critique concerns a shortcut from the unrelated IS-IS LSP lifetime anomaly case. The shortcut actually proposed in this controlled acceptance rehearsal is: Flood every core prefix as a static route into each Level 1 edge. It should be rejected for the narrower reason that Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. This distinction matters because Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
D:Premature transit eligibility can blackhole traffic while the node has incomplete routing state. That critique concerns a shortcut from the unrelated IS-IS overload-state recovery case. The shortcut actually proposed in this controlled acceptance rehearsal is: Flood every core prefix as a static route into each Level 1 edge. It should be rejected for the narrower reason that Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. This distinction matters because Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
Question 837
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. An engineer suggests the shortcut: "Change only VLAN interface descriptions without fixing the region mapping." Which critique explains the specific risk of that shortcut?
- MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election.
- 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.
- Descriptions do not participate in MSTP region identification or instance mapping.
Explanation
Correct Answer
D:Descriptions do not participate in MSTP region identification or instance mapping. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Change only VLAN interface descriptions without fixing the region mapping. It fails to resolve the underlying problem that MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. A sound alternative is the targeted engineering action: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
Incorrect Answers
A: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 controlled acceptance rehearsal is: Change only VLAN interface descriptions without fixing the region mapping. It should be rejected for the narrower reason that Descriptions do not participate in MSTP region identification or instance mapping. This distinction matters because MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
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 controlled acceptance rehearsal is: Change only VLAN interface descriptions without fixing the region mapping. It should be rejected for the narrower reason that Descriptions do not participate in MSTP region identification or instance mapping. This distinction matters because MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
C: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 controlled acceptance rehearsal is: Change only VLAN interface descriptions without fixing the region mapping. It should be rejected for the narrower reason that Descriptions do not participate in MSTP region identification or instance mapping. This distinction matters because MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
Question 838
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. An engineer suggests the shortcut: "Disable all MAC learning on the switch to eliminate the observed flood." Which critique explains the specific risk of that shortcut?
- Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.
- Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved.
- Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic.
- IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong.
Explanation
Correct Answer
A:Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Disable all MAC learning on the switch to eliminate the observed flood. It fails to resolve the underlying problem that A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. A sound alternative is the targeted engineering action: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
Incorrect Answers
B: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 controlled acceptance rehearsal is: Disable all MAC learning on the switch to eliminate the observed flood. It should be rejected for the narrower reason that Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. This distinction matters because A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
C:Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic. That critique concerns a shortcut from the unrelated Provider VLAN customer isolation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Disable all MAC learning on the switch to eliminate the observed flood. It should be rejected for the narrower reason that Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. This distinction matters because A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
D: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 controlled acceptance rehearsal is: Disable all MAC learning on the switch to eliminate the observed flood. It should be rejected for the narrower reason that Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. This distinction matters because A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
Question 839
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. An engineer suggests the shortcut: "Set the minimum possible BFD interval everywhere regardless of platform capacity." Which critique explains the specific risk of that shortcut?
- Aggressive preemption repeats the same transient blackhole while the upstream path remains unready.
- A gateway-election priority has no role in preserving the chassis routing protocol state across RE change.
- LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.
- Unreasonably small intervals can cause false liveness failures and repeated routing churn.
Explanation
Correct Answer
D:Unreasonably small intervals can cause false liveness failures and repeated routing churn. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Set the minimum possible BFD interval everywhere regardless of platform capacity. It fails to resolve the underlying problem that BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. A sound alternative is the targeted engineering action: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
Incorrect Answers
A: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 controlled acceptance rehearsal is: Set the minimum possible BFD interval everywhere regardless of platform capacity. It should be rejected for the narrower reason that Unreasonably small intervals can cause false liveness failures and repeated routing churn. This distinction matters because BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
B: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 controlled acceptance rehearsal is: Set the minimum possible BFD interval everywhere regardless of platform capacity. It should be rejected for the narrower reason that Unreasonably small intervals can cause false liveness failures and repeated routing churn. This distinction matters because BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
C:LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. That critique concerns a shortcut from the unrelated NSR backup routing synchronization case. The shortcut actually proposed in this controlled acceptance rehearsal is: Set the minimum possible BFD interval everywhere regardless of platform capacity. It should be rejected for the narrower reason that Unreasonably small intervals can cause false liveness failures and repeated routing churn. This distinction matters because BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
Question 840
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
- 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.
- Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
Explanation
Correct Answer
D:Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. In this controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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.
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 controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests