Question 670In a separate fictional JNCIS-SP lab review for Brightstone Backbone 168, a carrier-edge and core routing team, following a monitored network change window, engineers find: A link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. What technical principle underlies the right remedy? BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. Physical link-up does not imply permission to forward under spanning-tree loop prevention. RSTP can converge more quickly using its port-role handshake and state mechanisms. Routing filters must match the relevant address family and intended prefix semantics. ExplanationCorrect Answer B:Physical link-up does not imply permission to forward under spanning-tree loop prevention. The port's intentional blocking reason and root path are verified in control-plane output. Inspect spanning-tree port role, state, and received BPDU information before changing hardware. 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 link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. C:RSTP can converge more quickly using its port-role handshake and state mechanisms. That could help when a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior; here, a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. D:Routing filters must match the relevant address family and intended prefix semantics. This is applicable when a prefix-list filter written for IPv4 is applied conceptually to IPv6 routing, and all intended IPv6 routes vanish; the present condition is that a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics.
Question 671In a separate fictional JNCIS-SP lab review for Brightstone Backbone 168, a carrier-edge and core routing team, following a monitored network change window, engineers find: A link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. Which acceptance finding demonstrates the affected service has recovered? The port's intentional blocking reason and root path are verified in control-plane output. The intended distribution bridge is root and access ports show expected roles. Protection triggers on test violations and normal subscriber frames still forward. The chosen path follows documented selection policy with MED considered only where applicable. ExplanationCorrect Answer A:The port's intentional blocking reason and root path are verified in control-plane output. Inspect spanning-tree port role, state, and received BPDU information before changing hardware. Physical link-up does not imply permission to forward under spanning-tree loop prevention. Incorrect Answers B:The intended distribution bridge is root and access ports show expected roles. It addresses a different problem: A low-capacity access switch becomes STP root after a new bridge priority setting. Here, a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. C:Protection triggers on test violations and normal subscriber frames still forward. This could matter when a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. In this case, a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. D:The chosen path follows documented selection policy with MED considered only where applicable. That could help when a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems; here, a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics.
Question 672In a separate fictional JNCIS-SP lab review for Brightstone Backbone 168, a carrier-edge and core routing team, following a monitored network change window, engineers find: A link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. What is the direct residual network risk if the fault remains unresolved? Unnecessary physical changes introduce instability without fixing the actual topology constraint. Subscribers see extended connectivity interruptions after routine link changes. A redundant Layer 2 link becomes a forwarding loop and floods the provider network. Customers can inject unapproved Layer 2 traffic into the provider bridge. ExplanationCorrect Answer A:Unnecessary physical changes introduce instability without fixing the actual topology constraint. Inspect spanning-tree port role, state, and received BPDU information before changing hardware. Physical link-up does not imply permission to forward under spanning-tree loop prevention. Incorrect Answers B:Subscribers see extended connectivity interruptions after routine link changes. That option concerns a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. The problem here is different: A link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. C:A redundant Layer 2 link becomes a forwarding loop and floods the provider network. It addresses a different problem: A blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge. Here, a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. D:Customers can inject unapproved Layer 2 traffic into the provider bridge. This could matter when an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. In this case, a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics.
Question 673At fictional Eastbridge Networks 169, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. Which targeted remediation best fits the reported behavior? Remove inappropriate edge-port assumptions and verify RSTP role transitions. Inspect the relevant VSTP instance and set its intended per-VLAN root and port roles. Restore the documented protection features and run controlled BPDU and failover tests. Review negotiated hold time and keepalive settings alongside transport health, then correct the design. ExplanationCorrect Answer C:Restore the documented protection features and run controlled BPDU and failover tests. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. Protection triggers on test violations and normal subscriber frames still forward. Incorrect Answers A:Remove inappropriate edge-port assumptions and verify RSTP role transitions. This addresses a situation in which a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior; however, a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. B:Inspect the relevant VSTP instance and set its intended per-VLAN root and port roles. The choice would be appropriate if one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs. Here, a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. D:Review negotiated hold time and keepalive settings alongside transport health, then correct the design. It addresses a different problem: A neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. Here, a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.
Question 674At fictional Eastbridge Networks 169, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. Why is this particular correction the best fit for the stated defect? Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. RSTP can converge more quickly using its port-role handshake and state mechanisms. BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. IS-IS neighbors require compatible level participation to exchange link-state information. ExplanationCorrect Answer A:Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. Restore the documented protection features and run controlled BPDU and failover tests. Protection triggers on test violations and normal subscriber frames still forward. Incorrect Answers B:RSTP can converge more quickly using its port-role handshake and state mechanisms. 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 configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. C:BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. The choice would be appropriate if a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. Here, a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. D:IS-IS neighbors require compatible level participation to exchange link-state information. That option concerns two adjacent core routers cannot establish IS-IS because one is configured only for Level 1 and the other only for Level 2. The problem here is different: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.
Question 675At fictional Eastbridge Networks 169, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. What direct observation would prove the corrective action worked? The suspect port remains in the protected state until valid BPDU information returns. The affected VLAN has the desired root and its forwarding path recovers. Protection triggers on test violations and normal subscriber frames still forward. The route table and forwarding lookup show the expected metric-driven next hop. ExplanationCorrect Answer C:Protection triggers on test violations and normal subscriber frames still forward. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. Restore the documented protection features and run controlled BPDU and failover tests. Incorrect Answers A:The suspect port remains in the protected state until valid BPDU information returns. It is useful for situations where a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; the reported fault, though, is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. B:The affected VLAN has the desired root and its forwarding path recovers. That relates to circumstances in which one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs. Here the problem is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. D:The route table and forwarding lookup show the expected metric-driven next hop. The choice would be appropriate if the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. Here, a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.
Question 676At fictional Eastbridge Networks 169, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. Which failure consequence follows most closely from ignoring this issue? A VLAN takes an unintended blocked or looping path. One subscriber VLAN suffers an isolated Layer 2 outage while others appear normal. A routine template update makes the provider bridge vulnerable to a customer-induced loop. Packets cannot reach the intended next hop despite a syntactically valid address. ExplanationCorrect Answer C:A routine template update makes the provider bridge vulnerable to a customer-induced loop. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. Restore the documented protection features and run controlled BPDU and failover tests. Incorrect Answers A:A VLAN takes an unintended blocked or looping path. This relates to a case where two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior; the current situation is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. B:One subscriber VLAN suffers an isolated Layer 2 outage while others appear normal. It is useful for situations where one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs; the reported fault, though, is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. D:Packets cannot reach the intended next hop despite a syntactically valid address. This addresses a situation in which an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design; however, a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.
Question 677In a separate fictional JNCIS-SP lab review for Orchard Link 170, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. What intervention most directly restores the intended routing or switching behavior? Restore the documented protection features and run controlled BPDU and failover tests. Configure supported loop protection where appropriate and test loss-of-BPDU behavior. Inspect the relevant VSTP instance and set its intended per-VLAN root and port roles. Verify active next-hop resolution and transit forwarding after OSPF convergence. ExplanationCorrect Answer A:Restore the documented protection features and run controlled BPDU and failover tests. Protection triggers on test violations and normal subscriber frames still forward. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. Incorrect Answers B:Configure supported loop protection where appropriate and test loss-of-BPDU behavior. This relates to a case where a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; the current situation is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. C:Inspect the relevant VSTP instance and set its intended per-VLAN root and port roles. It is useful for situations where one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs; the reported fault, though, is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. D:Verify active next-hop resolution and transit forwarding after OSPF convergence. That relates to circumstances in which an engineer sees an OSPF route in the routing table and closes the incident without testing the egress path. Here the problem is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.
Question 678In a separate fictional JNCIS-SP lab review for Orchard Link 170, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. Which networking principle explains why the proposed correction is appropriate? Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. RSTP edge-port behavior is intended for ports without downstream bridge participation. GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. ExplanationCorrect Answer B:Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. Protection triggers on test violations and normal subscriber frames still forward. Restore the documented protection features and run controlled BPDU and failover tests. Incorrect Answers A:Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. It is relevant if a low-capacity access switch becomes STP root after a new bridge priority setting, but the reported issue is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. 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 configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. D:GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. It is useful for situations where a configured GRE tunnel stays unusable after the remote outer IP endpoint changes; the reported fault, though, is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.
Question 679In a separate fictional JNCIS-SP lab review for Orchard Link 170, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. Which validation result would confirm the design is now functioning? The affected VLAN has the desired root and its forwarding path recovers. Protection triggers on test violations and normal subscriber frames still forward. The interswitch link uses normal RSTP role and state handling during topology tests. The planned L1 adjacency forms and the corresponding area information is consistent. ExplanationCorrect Answer B:Protection triggers on test violations and normal subscriber frames still forward. Restore the documented protection features and run controlled BPDU and failover tests. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. Incorrect Answers A:The affected VLAN has the desired root and its forwarding path recovers. This is applicable when one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs; the present condition is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. C:The interswitch link uses normal RSTP role and state handling during topology tests. This could help if a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior, but not when a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. D:The planned L1 adjacency forms and the corresponding area information is consistent. This relates to a case where a Level 1 IS-IS adjacency fails between routers with different area addresses even though the physical link is up; the current situation is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.
Question 680In a separate fictional JNCIS-SP lab review for Orchard Link 170, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. What likely service impact does this condition create? A routine template update makes the provider bridge vulnerable to a customer-induced loop. Traffic traverses unsuitable links and topology changes become disruptive. Customer equipment captures the root role and disrupts forwarding. MPLS traffic cannot use the planned engineered transport path. ExplanationCorrect Answer A:A routine template update makes the provider bridge vulnerable to a customer-induced loop. Restore the documented protection features and run controlled BPDU and failover tests. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. Incorrect Answers B:Traffic traverses unsuitable links and topology changes become disruptive. This is applicable when a low-capacity access switch becomes STP root after a new bridge priority setting; the present condition is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. C:Customer equipment captures the root role and disrupts forwarding. It is relevant if a customer-facing bridge advertises a superior root and takes over the provider STP topology, but the reported issue is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. D:MPLS traffic cannot use the planned engineered transport path. This could help if an RSVP LSP stays down but engineers only examine the ingress router's IP default route, but not when a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.