Question 800
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
- Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
- Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
- With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
Explanation
Correct Answer
C:Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables. This tests the actual condition identified in the controlled acceptance rehearsal: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. It is meaningful because Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
Incorrect Answers
A:The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems. This measurement may prove the unrelated Equal-cost multipath eligibility condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. A relevant acceptance result here is: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
B:Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded. This measurement may prove the unrelated Per-flow hash expectation condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. A relevant acceptance result here is: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
D:With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate. This measurement may prove the unrelated Static backup blackhole condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. A relevant acceptance result here is: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
Question 801
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. An engineer suggests the shortcut: "Set identical router IDs on all peers to force the lowest MED to win." Which critique explains the specific risk of that shortcut?
- 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.
- Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI.
Explanation
Correct Answer
A:Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Set identical router IDs on all peers to force the lowest MED to win. It fails to resolve the underlying problem that BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. A sound alternative is the targeted engineering action: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
Incorrect Answers
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: Set identical router IDs on all peers to force the lowest MED to win. It should be rejected for the narrower reason that Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. This distinction matters because BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
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: Set identical router IDs on all peers to force the lowest MED to win. It should be rejected for the narrower reason that Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. This distinction matters because BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
D: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: Set identical router IDs on all peers to force the lowest MED to win. It should be rejected for the narrower reason that Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. This distinction matters because BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
Question 802
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. An engineer suggests the shortcut: "Increase application payload size while ignoring the tunnel-header overhead." Which critique explains the specific risk of that shortcut?
- Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer.
- Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path.
- Larger packets increase the encapsulation MTU violation and do not solve delivery.
- Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon.
Explanation
Correct Answer
C:Larger packets increase the encapsulation MTU violation and do not solve delivery. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase application payload size while ignoring the tunnel-header overhead. It fails to resolve the underlying problem that GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. A sound alternative is the targeted engineering action: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
Incorrect Answers
A:Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. That critique concerns a shortcut from the unrelated GRE confidentiality misconception case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase application payload size while ignoring the tunnel-header overhead. It should be rejected for the narrower reason that Larger packets increase the encapsulation MTU violation and do not solve delivery. This distinction matters because GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
B:Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. That critique concerns a shortcut from the unrelated GRE tunnel endpoint mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase application payload size while ignoring the tunnel-header overhead. It should be rejected for the narrower reason that Larger packets increase the encapsulation MTU violation and do not solve delivery. This distinction matters because GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
D:Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. That critique concerns a shortcut from the unrelated GRE underlay recursive loss case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase application payload size while ignoring the tunnel-header overhead. It should be rejected for the narrower reason that Larger packets increase the encapsulation MTU violation and do not solve delivery. This distinction matters because GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
Question 803
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. An engineer suggests the shortcut: "Disable every MPLS label exchange just because one label was popped near the egress." 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.
- Packet size settings cannot create capacity for an RSVP admission request.
- Suppressing alarms cannot provide a precomputed alternate label-switched route.
- BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP.
Explanation
Correct Answer
A:PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Disable every MPLS label exchange just because one label was popped near the egress. It fails to resolve the underlying problem that Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. A sound alternative is the targeted engineering action: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
Incorrect Answers
B: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: Disable every MPLS label exchange just because one label was popped near the egress. It should be rejected for the narrower reason that PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. This distinction matters because Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
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: Disable every MPLS label exchange just because one label was popped near the egress. It should be rejected for the narrower reason that PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. This distinction matters because Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
D:BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. That critique concerns a shortcut from the unrelated LDP tunneled over RSVP case. The shortcut actually proposed in this controlled acceptance rehearsal is: Disable every MPLS label exchange just because one label was popped near the egress. It should be rejected for the narrower reason that PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. This distinction matters because Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
Question 804
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. An engineer suggests the shortcut: "Pin a static route to the stale next hop and ignore the LSDB discrepancy." Which critique explains the specific risk of that shortcut?
- A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.
- Blindly redistributing external information conflicts with the intended stub-area containment model.
- DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link.
- A process reset can temporarily restart negotiation but leaves the same incompatibility in place.
Explanation
Correct Answer
A:A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Pin a static route to the stale next hop and ignore the LSDB discrepancy. It fails to resolve the underlying problem that Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. A sound alternative is the targeted engineering action: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
Incorrect Answers
B:Blindly redistributing external information conflicts with the intended stub-area containment model. That critique concerns a shortcut from the unrelated Stub area external LSA expectation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Pin a static route to the stale next hop and ignore the LSDB discrepancy. It should be rejected for the narrower reason that A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. This distinction matters because Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
C:DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. That critique concerns a shortcut from the unrelated Point-to-point OSPF network type case. The shortcut actually proposed in this controlled acceptance rehearsal is: Pin a static route to the stale next hop and ignore the LSDB discrepancy. It should be rejected for the narrower reason that A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. This distinction matters because Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
D:A process reset can temporarily restart negotiation but leaves the same incompatibility in place. That critique concerns a shortcut from the unrelated OSPF MTU ExStart stall case. The shortcut actually proposed in this controlled acceptance rehearsal is: Pin a static route to the stale next hop and ignore the LSDB discrepancy. It should be rejected for the narrower reason that A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. This distinction matters because Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
Question 805
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. An engineer suggests the shortcut: "Announce only an IPv6 static route without providing a working cross-underlay tunnel." Which critique explains the specific risk of that shortcut?
- IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement.
- IPv4 routing entries cannot replace the missing IPv6 prefix advertisements.
- IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path.
- Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery.
Explanation
Correct Answer
C:IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Announce only an IPv6 static route without providing a working cross-underlay tunnel. It fails to resolve the underlying problem that An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. A sound alternative is the targeted engineering action: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
Incorrect Answers
A:IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. That critique concerns a shortcut from the unrelated IPv6 BGP NLRI family omitted case. The shortcut actually proposed in this controlled acceptance rehearsal is: Announce only an IPv6 static route without providing a working cross-underlay tunnel. It should be rejected for the narrower reason that IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. This distinction matters because An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
B: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 controlled acceptance rehearsal is: Announce only an IPv6 static route without providing a working cross-underlay tunnel. It should be rejected for the narrower reason that IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. This distinction matters because An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
D:Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery. That critique concerns a shortcut from the unrelated ICMPv6 packet-too-big handling case. The shortcut actually proposed in this controlled acceptance rehearsal is: Announce only an IPv6 static route without providing a working cross-underlay tunnel. It should be rejected for the narrower reason that IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. This distinction matters because An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
Question 806
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles.
- OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election.
- MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election.
- Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm.
Explanation
Correct Answer
A:Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles. In this controlled acceptance rehearsal 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
B:OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. That critique concerns a shortcut from the unrelated Root bridge election priority case. The shortcut actually proposed in this controlled acceptance rehearsal 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: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 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: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 controlled acceptance rehearsal 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 807
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. An engineer suggests the shortcut: "Repeatedly clear the OSPF process without fixing the MTU mismatch." Which critique explains the specific risk of that shortcut?
- Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.
- A process reset can temporarily restart negotiation but leaves the same incompatibility in place.
- Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks.
- Blanket redistribution can expose management and unrelated customer networks and create routing instability.
Explanation
Correct Answer
B:A process reset can temporarily restart negotiation but leaves the same incompatibility in place. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Repeatedly clear the OSPF process without fixing the MTU mismatch. It fails to resolve the underlying problem that OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. A sound alternative is the targeted engineering action: Correct the actual transport MTU mismatch across the link, then validate database description exchange.
Incorrect Answers
A:Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. That critique concerns a shortcut from the unrelated OSPF authentication key mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Repeatedly clear the OSPF process without fixing the MTU mismatch. It should be rejected for the narrower reason that A process reset can temporarily restart negotiation but leaves the same incompatibility in place. This distinction matters because OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
C:Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. That critique concerns a shortcut from the unrelated OSPF backbone connectivity case. The shortcut actually proposed in this controlled acceptance rehearsal is: Repeatedly clear the OSPF process without fixing the MTU mismatch. It should be rejected for the narrower reason that A process reset can temporarily restart negotiation but leaves the same incompatibility in place. This distinction matters because OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
D: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: Repeatedly clear the OSPF process without fixing the MTU mismatch. It should be rejected for the narrower reason that A process reset can temporarily restart negotiation but leaves the same incompatibility in place. This distinction matters because OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
Question 808
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. An engineer suggests the shortcut: "Raise the MAC aging timer while leaving both conflicting attachments active." Which critique explains the specific risk of that shortcut?
- 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.
- Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership.
- An aging change cannot prevent contradictory source-MAC observations on multiple ports.
Explanation
Correct Answer
D:An aging change cannot prevent contradictory source-MAC observations on multiple ports. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Raise the MAC aging timer while leaving both conflicting attachments active. It fails to resolve the underlying problem that Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. A sound alternative is the targeted engineering action: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
Incorrect Answers
A: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: Raise the MAC aging timer while leaving both conflicting attachments active. It should be rejected for the narrower reason that An aging change cannot prevent contradictory source-MAC observations on multiple ports. This distinction matters because Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
B: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 controlled acceptance rehearsal is: Raise the MAC aging timer while leaving both conflicting attachments active. It should be rejected for the narrower reason that An aging change cannot prevent contradictory source-MAC observations on multiple ports. This distinction matters because Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
C:Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. That critique concerns a shortcut from the unrelated Trunk allowed VLAN omission case. The shortcut actually proposed in this controlled acceptance rehearsal is: Raise the MAC aging timer while leaving both conflicting attachments active. It should be rejected for the narrower reason that An aging change cannot prevent contradictory source-MAC observations on multiple ports. This distinction matters because Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
Question 809
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. An engineer suggests the shortcut: "Disable all spanning-tree processing on the edge network to stop the BPDU alerts." Which critique explains the specific risk of that shortcut?
- Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles.
- 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.
- Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm.
Explanation
Correct Answer
C:Removing STP protection can permit the unauthorized bridge to create a forwarding loop. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Disable all spanning-tree processing on the edge network to stop the BPDU alerts. It fails to resolve the underlying problem that Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. A sound alternative is the targeted engineering action: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
Incorrect Answers
A: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: Disable all spanning-tree processing on the edge network to stop the BPDU alerts. It should be rejected for the narrower reason that Removing STP protection can permit the unauthorized bridge to create a forwarding loop. This distinction matters because Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
B: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: Disable all spanning-tree processing on the edge network to stop the BPDU alerts. It should be rejected for the narrower reason that Removing STP protection can permit the unauthorized bridge to create a forwarding loop. This distinction matters because Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
D: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 controlled acceptance rehearsal is: Disable all spanning-tree processing on the edge network to stop the BPDU alerts. It should be rejected for the narrower reason that Removing STP protection can permit the unauthorized bridge to create a forwarding loop. This distinction matters because Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
Question 810
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. An engineer suggests the shortcut: "Change the route description and leave the unresolved next hop unchanged." Which critique explains the specific risk of that shortcut?
- More routes in the original table do not implement selective forwarding through a different routing table.
- A text description has no effect on recursive route resolution and cannot install a usable forwarding entry.
- Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
- Hostname changes do not import a route between separate routing information bases.
Explanation
Correct Answer
B:A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Change the route description and leave the unresolved next hop unchanged. It fails to resolve the underlying problem that A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. A sound alternative is the targeted engineering action: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
Incorrect Answers
A:More routes in the original table do not implement selective forwarding through a different routing table. That critique concerns a shortcut from the unrelated Filter-based forwarding classification case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
C: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: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
D: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: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests