Question 880
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- 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.
- Removing the interface entirely can also remove the necessary prefix advertisement.
- Router-ID identity is not an OSPF path-cost control knob.
Explanation
Correct Answer
B:Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. In this controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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:Removing the interface entirely can also remove the necessary prefix advertisement. That critique concerns a shortcut from the unrelated OSPF passive interface case. The shortcut actually proposed in this controlled acceptance rehearsal 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.
D:Router-ID identity is not an OSPF path-cost control knob. That critique concerns a shortcut from the unrelated OSPF metric path preference case. The shortcut actually proposed in this controlled acceptance rehearsal 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 881
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. An engineer suggests the shortcut: "Reduce Ethernet MTU on the provider uplink to influence BPDU root election." 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.
- 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.
Explanation
Correct Answer
A:MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Reduce Ethernet MTU on the provider uplink to influence BPDU root election. It fails to resolve the underlying problem that Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. A sound alternative is the targeted engineering action: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
Incorrect Answers
B: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 controlled acceptance rehearsal is: Reduce Ethernet MTU on the provider uplink to influence BPDU root election. It should be rejected for the narrower reason that MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. This distinction matters because Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
C:Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles. That critique concerns a shortcut from the unrelated Per-VLAN spanning-tree path case. The shortcut actually proposed in this controlled acceptance rehearsal is: Reduce Ethernet MTU on the provider uplink to influence BPDU root election. It should be rejected for the narrower reason that MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. This distinction matters because Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
D: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: Reduce Ethernet MTU on the provider uplink to influence BPDU root election. It should be rejected for the narrower reason that MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. This distinction matters because Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
Question 882
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. An engineer suggests the shortcut: "Advertise an extra IGP prefix while leaving TCP 646 blocked." Which critique explains the specific risk of that shortcut?
- PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
- IP TTL does not control implicit-null versus explicit-null label disposition.
- Additional network-layer routes cannot substitute for the required LDP session transport.
- Packet size settings cannot create capacity for an RSVP admission request.
Explanation
Correct Answer
C:Additional network-layer routes cannot substitute for the required LDP session transport. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Advertise an extra IGP prefix while leaving TCP 646 blocked. It fails to resolve the underlying problem that LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. A sound alternative is the targeted engineering action: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
Incorrect Answers
A: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: Advertise an extra IGP prefix while leaving TCP 646 blocked. It should be rejected for the narrower reason that Additional network-layer routes cannot substitute for the required LDP session transport. This distinction matters because LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
B:IP TTL does not control implicit-null versus explicit-null label disposition. That critique concerns a shortcut from the unrelated Explicit-null forwarding case. The shortcut actually proposed in this controlled acceptance rehearsal is: Advertise an extra IGP prefix while leaving TCP 646 blocked. It should be rejected for the narrower reason that Additional network-layer routes cannot substitute for the required LDP session transport. This distinction matters because LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
D: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: Advertise an extra IGP prefix while leaving TCP 646 blocked. It should be rejected for the narrower reason that Additional network-layer routes cannot substitute for the required LDP session transport. This distinction matters because LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
Question 883
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- 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.
- Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
- 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 controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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 884
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. An engineer suggests the shortcut: "Increase BGP keepalive frequency while no contributor route exists." Which critique explains the specific risk of that shortcut?
- BGP timers do not create the aggregate's necessary routing-table contribution.
- Changing accounting counters does not change first-match classification or forwarding decisions.
- 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.
Explanation
Correct Answer
A:BGP timers do not create the aggregate's necessary routing-table contribution. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase BGP keepalive frequency while no contributor route exists. It fails to resolve the underlying problem that A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. A sound alternative is the targeted engineering action: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
Incorrect Answers
B:Changing accounting counters does not change first-match classification or forwarding decisions. That critique concerns a shortcut from the unrelated Filter policy overmatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase BGP keepalive frequency while no contributor route exists. It should be rejected for the narrower reason that BGP timers do not create the aggregate's necessary routing-table contribution. This distinction matters because A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
C: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 controlled acceptance rehearsal is: Increase BGP keepalive frequency while no contributor route exists. It should be rejected for the narrower reason that BGP timers do not create the aggregate's necessary routing-table contribution. This distinction matters because A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
D:Presence in a control-plane view does not prove active route selection or packet forwarding installation. That critique concerns a shortcut from the unrelated Inactive route versus forwarding entry case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase BGP keepalive frequency while no contributor route exists. It should be rejected for the narrower reason that BGP timers do not create the aggregate's necessary routing-table contribution. This distinction matters because A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
Question 885
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. An engineer suggests the shortcut: "Assume every routing neighbor automatically supports graceful restart with no negotiation." Which critique explains the specific risk of that shortcut?
- Routing metrics in OSPF do not directly determine VRRP primary election.
- Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations.
- 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.
Explanation
Correct Answer
B:Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Assume every routing neighbor automatically supports graceful restart with no negotiation. It fails to resolve the underlying problem that Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. A sound alternative is the targeted engineering action: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.
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: Assume every routing neighbor automatically supports graceful restart with no negotiation. It should be rejected for the narrower reason that Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. This distinction matters because Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
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 controlled acceptance rehearsal is: Assume every routing neighbor automatically supports graceful restart with no negotiation. It should be rejected for the narrower reason that Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. This distinction matters because Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
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 controlled acceptance rehearsal is: Assume every routing neighbor automatically supports graceful restart with no negotiation. It should be rejected for the narrower reason that Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. This distinction matters because Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
Question 886
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. An engineer suggests the shortcut: "Enable arbitrary per-packet splitting on the production service without checking reordering risk." Which critique explains the specific risk of that shortcut?
- Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
- An unconditional default masks missing prerequisites and may direct traffic into an unintended path.
- 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.
Explanation
Correct Answer
A:Forcing packets of one flow onto different paths can reorder packets and harm transport performance. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Enable arbitrary per-packet splitting on the production service without checking reordering risk. It fails to resolve the underlying problem that Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. A sound alternative is the targeted engineering action: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
Incorrect Answers
B: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 controlled acceptance rehearsal is: Enable arbitrary per-packet splitting on the production service without checking reordering risk. It should be rejected for the narrower reason that Forcing packets of one flow onto different paths can reorder packets and harm transport performance. This distinction matters because Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
C: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: Enable arbitrary per-packet splitting on the production service without checking reordering risk. It should be rejected for the narrower reason that Forcing packets of one flow onto different paths can reorder packets and harm transport performance. This distinction matters because Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
D: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: Enable arbitrary per-packet splitting on the production service without checking reordering risk. It should be rejected for the narrower reason that Forcing packets of one flow onto different paths can reorder packets and harm transport performance. This distinction matters because Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
Question 887
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. An engineer suggests the shortcut: "Change OSPF DR priority to manipulate BGP AS-path selection." Which critique explains the specific risk of that shortcut?
- ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing.
- Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
- OSPF LAN DR election settings do not modify the BGP path attributes being compared.
- Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI.
Explanation
Correct Answer
C:OSPF LAN DR election settings do not modify the BGP path attributes being compared. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Change OSPF DR priority to manipulate BGP AS-path selection. It fails to resolve the underlying problem that When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. A sound alternative is the targeted engineering action: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
Incorrect Answers
A:ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. That critique concerns a shortcut from the unrelated EBGP multihop peering case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change OSPF DR priority to manipulate BGP AS-path selection. It should be rejected for the narrower reason that OSPF LAN DR election settings do not modify the BGP path attributes being compared. This distinction matters because When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
B: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 controlled acceptance rehearsal is: Change OSPF DR priority to manipulate BGP AS-path selection. It should be rejected for the narrower reason that OSPF LAN DR election settings do not modify the BGP path attributes being compared. This distinction matters because When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
D:Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. That critique concerns a shortcut from the unrelated BGP IPv6 family inactive case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change OSPF DR priority to manipulate BGP AS-path selection. It should be rejected for the narrower reason that OSPF LAN DR election settings do not modify the BGP path attributes being compared. This distinction matters because When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
Question 888
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. An engineer suggests the shortcut: "Disable all IS-IS authentication in the area to bypass the mismatched key." Which critique explains the specific risk of that shortcut?
- OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
- 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.
Explanation
Correct Answer
B:Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Disable all IS-IS authentication in the area to bypass the mismatched key. It fails to resolve the underlying problem that When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. A sound alternative is the targeted engineering action: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
Incorrect Answers
A: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: Disable all IS-IS authentication in the area to bypass the mismatched key. It should be rejected for the narrower reason that Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. This distinction matters because When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
C: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 controlled acceptance rehearsal is: Disable all IS-IS authentication in the area to bypass the mismatched key. It should be rejected for the narrower reason that Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. This distinction matters because When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
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: Disable all IS-IS authentication in the area to bypass the mismatched key. It should be rejected for the narrower reason that Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. This distinction matters because When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
Question 889
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. An engineer suggests the shortcut: "Turn every trunk into an unrestricted all-VLAN connection." 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.
- Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership.
- Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames.
Explanation
Correct Answer
C:Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Turn every trunk into an unrestricted all-VLAN connection. It fails to resolve the underlying problem that A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. A sound alternative is the targeted engineering action: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
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 controlled acceptance rehearsal is: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
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 controlled acceptance rehearsal is: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
D:Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames. That critique concerns a shortcut from the unrelated Access VLAN membership case. The shortcut actually proposed in this controlled acceptance rehearsal is: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
Question 890
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.
- Presence in a control-plane view does not prove active route selection or packet forwarding installation.
- Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility.
- An unconditional default masks missing prerequisites and may direct traffic into an unintended path.
Explanation
Correct Answer
B:Presence in a control-plane view does not prove active route selection or packet forwarding installation. In this controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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.
C:Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. That critique concerns a shortcut from the unrelated Equal-cost multipath eligibility case. The shortcut actually proposed in this controlled acceptance rehearsal 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: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 controlled acceptance rehearsal 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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests