Question 610At fictional Crestland Networks 153, a regional service-provider network, during a two-site transit migration, operations observes: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. Why is this particular correction the best fit for the stated defect? BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. Root protection maintains root placement by preventing an untrusted port from becoming an upstream root path. RSTP edge-port behavior is intended for ports without downstream bridge participation. Filter-based forwarding selects a routing lookup context based on packet classification. ExplanationCorrect Answer C:RSTP edge-port behavior is intended for ports without downstream bridge participation. Remove inappropriate edge-port assumptions and verify RSTP role transitions. The interswitch link uses normal RSTP role and state handling during topology tests. Incorrect Answers A:BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. It addresses a different problem: A subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. Here, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. B:Root protection maintains root placement by preventing an untrusted port from becoming an upstream root path. This could matter when a customer-facing bridge advertises a superior root and takes over the provider STP topology. In this case, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. D:Filter-based forwarding selects a routing lookup context based on packet classification. This is applicable when a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup; the present condition is that a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.
Question 611At fictional Crestland Networks 153, a regional service-provider network, during a two-site transit migration, operations observes: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. What direct observation would prove the corrective action worked? An injected test BPDU triggers the documented protection while legitimate access ports behave normally. The interswitch link uses normal RSTP role and state handling during topology tests. A superior BPDU on the customer link is blocked from changing the intended root. The service route is visible on remote devices while unrelated prefixes remain suppressed. ExplanationCorrect Answer B:The interswitch link uses normal RSTP role and state handling during topology tests. RSTP edge-port behavior is intended for ports without downstream bridge participation. Remove inappropriate edge-port assumptions and verify RSTP role transitions. Incorrect Answers A:An injected test BPDU triggers the documented protection while legitimate access ports behave normally. That option concerns a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. The problem here is different: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. C:A superior BPDU on the customer link is blocked from changing the intended root. This could matter when a customer-facing bridge advertises a superior root and takes over the provider STP topology. In this case, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. D:The service route is visible on remote devices while unrelated prefixes remain suppressed. That could help when a customer service route never reaches another IS-IS area because the required export policy omits it; here, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.
Question 612At fictional Crestland Networks 153, a regional service-provider network, during a two-site transit migration, operations observes: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. Which failure consequence follows most closely from ignoring this issue? Customer equipment captures the root role and disrupts forwarding. A routine template update makes the provider bridge vulnerable to a customer-induced loop. An unnoticed bridging loop can trigger widespread broadcast storms. Services remain blackholed despite a received BGP update. ExplanationCorrect Answer C:An unnoticed bridging loop can trigger widespread broadcast storms. RSTP edge-port behavior is intended for ports without downstream bridge participation. Remove inappropriate edge-port assumptions and verify RSTP role transitions. Incorrect Answers A:Customer equipment captures the root role and disrupts forwarding. The choice would be appropriate if a customer-facing bridge advertises a superior root and takes over the provider STP topology. Here, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. B:A routine template update makes the provider bridge vulnerable to a customer-induced loop. That option concerns a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. The problem here is different: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. D:Services remain blackholed despite a received BGP update. This could matter when an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. In this case, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.
Question 613In a separate fictional JNCIS-SP lab review for Silverlake Routing 154, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. What intervention most directly restores the intended routing or switching behavior? Remove inappropriate edge-port assumptions and verify RSTP role transitions. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. Restore the documented protection features and run controlled BPDU and failover tests. Apply the agreed route-limit safeguard and validate alerts and peer handling at controlled thresholds. ExplanationCorrect Answer A:Remove inappropriate edge-port assumptions and verify RSTP role transitions. The interswitch link uses normal RSTP role and state handling during topology tests. RSTP edge-port behavior is intended for ports without downstream bridge participation. Incorrect Answers B:Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. The choice would be appropriate if a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. Here, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. C:Restore the documented protection features and run controlled BPDU and failover tests. That option concerns a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. The problem here is different: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. D:Apply the agreed route-limit safeguard and validate alerts and peer handling at controlled thresholds. It addresses a different problem: A misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale. Here, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.
Question 614In a separate fictional JNCIS-SP lab review for Silverlake Routing 154, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. Which networking principle explains why the proposed correction is appropriate? Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs. RSTP edge-port behavior is intended for ports without downstream bridge participation. Physical link-up does not imply permission to forward under spanning-tree loop prevention. OSPF peers must satisfy the configured authentication requirements to participate. ExplanationCorrect Answer B:RSTP edge-port behavior is intended for ports without downstream bridge participation. The interswitch link uses normal RSTP role and state handling during topology tests. Remove inappropriate edge-port assumptions and verify RSTP role transitions. Incorrect Answers A:Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs. That relates to circumstances in which a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge. Here the problem is that a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. C:Physical link-up does not imply permission to forward under spanning-tree loop prevention. The choice would be appropriate if a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. Here, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. D:OSPF peers must satisfy the configured authentication requirements to participate. That option concerns a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree. The problem here is different: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.
Question 615In a separate fictional JNCIS-SP lab review for Silverlake Routing 154, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. Which validation result would confirm the design is now functioning? The interswitch link uses normal RSTP role and state handling during topology tests. A superior BPDU on the customer link is blocked from changing the intended root. The alternate link takes the intended forwarding role within the accepted recovery target. MAC entries stabilize on the intended interface after repairing the bridge path. ExplanationCorrect Answer A:The interswitch link uses normal RSTP role and state handling during topology tests. Remove inappropriate edge-port assumptions and verify RSTP role transitions. RSTP edge-port behavior is intended for ports without downstream bridge participation. Incorrect Answers B:A superior BPDU on the customer link is blocked from changing the intended root. That relates to circumstances in which a customer-facing bridge advertises a superior root and takes over the provider STP topology. Here the problem is that a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. C:The alternate link takes the intended forwarding role within the accepted recovery target. This addresses a situation in which a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior; however, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. D:MAC entries stabilize on the intended interface after repairing the bridge path. The choice would be appropriate if a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. Here, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.
Question 616In a separate fictional JNCIS-SP lab review for Silverlake Routing 154, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. What likely service impact does this condition create? An unnoticed bridging loop can trigger widespread broadcast storms. Customer equipment captures the root role and disrupts forwarding. A routine template update makes the provider bridge vulnerable to a customer-induced loop. Outbound traffic takes an expensive or congested transit link. ExplanationCorrect Answer A:An unnoticed bridging loop can trigger widespread broadcast storms. Remove inappropriate edge-port assumptions and verify RSTP role transitions. RSTP edge-port behavior is intended for ports without downstream bridge participation. Incorrect Answers B:Customer equipment captures the root role and disrupts forwarding. It is useful for situations where a customer-facing bridge advertises a superior root and takes over the provider STP topology; the reported fault, though, is that a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. C:A routine template update makes the provider bridge vulnerable to a customer-induced loop. That relates to circumstances in which a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. Here the problem is that a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. D:Outbound traffic takes an expensive or congested transit link. This addresses a situation in which a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset; however, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.
Question 617At fictional Seabrook Metro 155, a regional service-provider network, during a preproduction design validation, operations observes: A subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. Which configuration or operational correction most directly addresses this failure? Apply the approved BPDU protection policy to the access edge and test the violation response. Restore the documented protection features and run controlled BPDU and failover tests. Use root protection on designated protected links and verify superior BPDU handling. Use the approved source address and confirm matching outer-packet forwarding and policy. ExplanationCorrect Answer A:Apply the approved BPDU protection policy to the access edge and test the violation response. BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. An injected test BPDU triggers the documented protection while legitimate access ports behave normally. Incorrect Answers B:Restore the documented protection features and run controlled BPDU and failover tests. This relates to a case where a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards; the current situation is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. C:Use root protection on designated protected links and verify superior BPDU handling. It is useful for situations where a customer-facing bridge advertises a superior root and takes over the provider STP topology; the reported fault, though, is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. D:Use the approved source address and confirm matching outer-packet forwarding and policy. That relates to circumstances in which a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. Here the problem is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only.
Question 618At fictional Seabrook Metro 155, a regional service-provider network, during a preproduction design validation, operations observes: A subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. Which Junos forwarding or control-plane rule applies to this case? BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. RSTP edge-port behavior is intended for ports without downstream bridge participation. The IS-IS overload indication can discourage transit use during control-plane recovery. ExplanationCorrect Answer A:BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. Apply the approved BPDU protection policy to the access edge and test the violation response. An injected test BPDU triggers the documented protection while legitimate access ports behave normally. Incorrect Answers B:Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. This could help if a low-capacity access switch becomes STP root after a new bridge priority setting, but not when a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. C:RSTP edge-port behavior is intended for ports without downstream bridge participation. This relates to a case where a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior; the current situation is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. D:The IS-IS overload indication can discourage transit use during control-plane recovery. It is useful for situations where a newly rebooted core router attracts transit traffic while its forwarding state is still being restored; the reported fault, though, is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only.
Question 619At fictional Seabrook Metro 155, a regional service-provider network, during a preproduction design validation, operations observes: A subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. What operational evidence best establishes successful remediation? The affected switches show the same region digest and expected per-instance port roles. The port's intentional blocking reason and root path are verified in control-plane output. Both endpoints reach the expected adjacency state and share matching area membership. An injected test BPDU triggers the documented protection while legitimate access ports behave normally. ExplanationCorrect Answer D:An injected test BPDU triggers the documented protection while legitimate access ports behave normally. BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. Apply the approved BPDU protection policy to the access edge and test the violation response. Incorrect Answers A:The affected switches show the same region digest and expected per-instance port roles. This is applicable when two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior; the present condition is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. B:The port's intentional blocking reason and root path are verified in control-plane output. It is relevant if a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics, but the reported issue is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. C:Both endpoints reach the expected adjacency state and share matching area membership. This could help if two provider routers on a point-to-point circuit cannot form an OSPF adjacency because their interfaces use different area IDs, but not when a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only.
Question 620At fictional Seabrook Metro 155, a regional service-provider network, during a preproduction design validation, operations observes: A subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. Which operational harm would persist without the intended correction? An unnoticed bridging loop can trigger widespread broadcast storms. Customer equipment captures the root role and disrupts forwarding. MPLS traffic remains broken despite restored IGP neighbors. Customer switching devices can influence provider spanning-tree topology. ExplanationCorrect Answer D:Customer switching devices can influence provider spanning-tree topology. BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. Apply the approved BPDU protection policy to the access edge and test the violation response. Incorrect Answers A:An unnoticed bridging loop can trigger widespread broadcast storms. That could help when a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior; here, a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. B:Customer equipment captures the root role and disrupts forwarding. This is applicable when a customer-facing bridge advertises a superior root and takes over the provider STP topology; the present condition is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. C:MPLS traffic remains broken despite restored IGP neighbors. It is relevant if after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device, but the reported issue is that a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only.