JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
Two redundant campus uplinks participate in VSTP but the traffic for a specific VLAN takes the uplink intentionally reserved for another segment. If the team bypasses or fails to implement the targeted correction (Tune the VSTP root bridge priority for that individual VLAN and review path cost.), which direct operational risk or residual exposure is MOST relevant?
Changing only global RSTP priority may not steer the intended per-VLAN topology. This is the consequence linked to the observed situation: Two redundant campus uplinks participate in VSTP but the traffic for a specific VLAN takes the uplink intentionally reserved for another segment. It is prevented by: Tune the VSTP root bridge priority for that individual VLAN and review path cost. The underlying reason is: Independent VSTP instances can use distinct roots and forwarding trees per VLAN.
An unintended root can place blocked ports and transit load on the wrong uplinks. This risk belongs to a different operational problem: A newly introduced switch becomes the unwanted MSTP root because its bridge priority is lower than the designated distribution pair. The stated condition instead exposes this direct risk: Changing only global RSTP priority may not steer the intended per-VLAN topology. The appropriate mitigation is: Tune the VSTP root bridge priority for that individual VLAN and review path cost.
Forcing all parallel bridging links to forward can create broadcast storms and MAC flapping. This risk belongs to a different operational problem: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The stated condition instead exposes this direct risk: Changing only global RSTP priority may not steer the intended per-VLAN topology. The appropriate mitigation is: Tune the VSTP root bridge priority for that individual VLAN and review path cost.
Enabling MVRP on access-only ports does not provide the intended trunk registration process. This risk belongs to a different operational problem: MVRP is enabled between two switches but a new VLAN is advertised only on an access port that is not a trunk member. The stated condition instead exposes this direct risk: Changing only global RSTP priority may not steer the intended per-VLAN topology. The appropriate mitigation is: Tune the VSTP root bridge priority for that individual VLAN and review path cost.
An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. Which targeted engineering change is MOST directly justified by the observed evidence?
Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port. This change specifically addresses the reported evidence: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The relevant protocol mechanism is: Edge-port designation avoids normal network-bridge convergence assumptions for host ports. A decisive acceptance test would be: The workstation port enters forwarding promptly without creating transit-device bridging loops.
Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance. This is a valid solution to a different Junos situation: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. It does not directly correct the specific failure evidence here: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The required targeted change is: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port.
Inspect Ethernet MAC learning/move logs and spanning-tree port changes on the implicated VLANs. This is a valid solution to a different Junos situation: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. It does not directly correct the specific failure evidence here: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The required targeted change is: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port.
Authorize the needed VLAN on the correct supported trunk without opening unrelated VLANs. This is a valid solution to a different Junos situation: A VLAN should cross an EX access-to-distribution trunk but remains absent from forwarding because it was not allowed on the uplink. It does not directly correct the specific failure evidence here: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The required targeted change is: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port.
An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The proposed correction is: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port. Which observation MOST directly confirms this fault is resolved?
The workstation port enters forwarding promptly without creating transit-device bridging loops. This is the direct acceptance evidence for the observed failure: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The mechanism being validated is: Edge-port designation avoids normal network-bridge convergence assumptions for host ports.
The alternate port shows a deliberate discarding role while the active tree remains connected. That would validate a different condition: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The decisive check for the current issue is: The workstation port enters forwarding promptly without creating transit-device bridging loops.
MAC move activity stops after the loop path is eliminated and the STP topology stabilizes. That would validate a different condition: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The decisive check for the current issue is: The workstation port enters forwarding promptly without creating transit-device bridging loops.
The trunk carries tagged frames for that VLAN and local MAC learning resumes. That would validate a different condition: A VLAN should cross an EX access-to-distribution trunk but remains absent from forwarding because it was not allowed on the uplink. The decisive check for the current issue is: The workstation port enters forwarding promptly without creating transit-device bridging loops.
A Junos engineer proposes this response: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port. The situation is: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. Which technical principle BEST justifies the response?
Edge-port designation avoids normal network-bridge convergence assumptions for host ports. This is the controlling mechanism in the specific case: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. It predicts the acceptance result: The workstation port enters forwarding promptly without creating transit-device bridging loops.
Spanning tree blocks redundant Layer 2 paths to avoid forwarding loops. This principle explains a separate situation: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. For this issue the relevant mechanism is: Edge-port designation avoids normal network-bridge convergence assumptions for host ports.
Rapid source-MAC moves among ports can indicate an unstable bridged topology. This principle explains a separate situation: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. For this issue the relevant mechanism is: Edge-port designation avoids normal network-bridge convergence assumptions for host ports.
An Ethernet trunk forwards only VLAN memberships configured or registered as eligible. This principle explains a separate situation: A VLAN should cross an EX access-to-distribution trunk but remains absent from forwarding because it was not allowed on the uplink. For this issue the relevant mechanism is: Edge-port designation avoids normal network-bridge convergence assumptions for host ports.
An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. If the team bypasses or fails to implement the targeted correction (Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port.), which direct operational risk or residual exposure is MOST relevant?
Marking actual switch-to-switch links as edge can weaken topology change safeguards. This is the consequence linked to the observed situation: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. It is prevented by: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port. The underlying reason is: Edge-port designation avoids normal network-bridge convergence assumptions for host ports.
Forcing all parallel bridging links to forward can create broadcast storms and MAC flapping. This risk belongs to a different operational problem: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The stated condition instead exposes this direct risk: Marking actual switch-to-switch links as edge can weaken topology change safeguards. The appropriate mitigation is: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port.
Adding more VLAN trunks before eliminating a loop may amplify a broadcast storm. This risk belongs to a different operational problem: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The stated condition instead exposes this direct risk: Marking actual switch-to-switch links as edge can weaken topology change safeguards. The appropriate mitigation is: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port.
Opening every VLAN to fix one missing membership expands an unnecessary Layer 2 failure domain. This risk belongs to a different operational problem: A VLAN should cross an EX access-to-distribution trunk but remains absent from forwarding because it was not allowed on the uplink. The stated condition instead exposes this direct risk: Marking actual switch-to-switch links as edge can weaken topology change safeguards. The appropriate mitigation is: Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port.
A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. Which targeted engineering change is MOST directly justified by the observed evidence?
Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance. This change specifically addresses the reported evidence: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The relevant protocol mechanism is: Spanning tree blocks redundant Layer 2 paths to avoid forwarding loops. A decisive acceptance test would be: The alternate port shows a deliberate discarding role while the active tree remains connected.
Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port. This is a valid solution to a different Junos situation: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. It does not directly correct the specific failure evidence here: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The required targeted change is: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance.
Inspect Ethernet MAC learning/move logs and spanning-tree port changes on the implicated VLANs. This is a valid solution to a different Junos situation: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. It does not directly correct the specific failure evidence here: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The required targeted change is: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance.
Reconfigure the gateway attachment as the intended promiscuous or primary-facing connection. This is a valid solution to a different Junos situation: A private-VLAN deployment places the default-gateway interface on an isolated host port and no tenants can reach it. It does not directly correct the specific failure evidence here: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The required targeted change is: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance.
A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The proposed correction is: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance. Which observation MOST directly confirms this fault is resolved?
The alternate port shows a deliberate discarding role while the active tree remains connected. This is the direct acceptance evidence for the observed failure: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The mechanism being validated is: Spanning tree blocks redundant Layer 2 paths to avoid forwarding loops.
The workstation port enters forwarding promptly without creating transit-device bridging loops. That would validate a different condition: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The decisive check for the current issue is: The alternate port shows a deliberate discarding role while the active tree remains connected.
MAC move activity stops after the loop path is eliminated and the STP topology stabilizes. That would validate a different condition: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The decisive check for the current issue is: The alternate port shows a deliberate discarding role while the active tree remains connected.
The customer receives a frame with the expected original inner VLAN tag and no provider S-VLAN tag. That would validate a different condition: A double-tagged customer Ethernet frame arrives at the far edge of a Q-in-Q service with its provider tag still attached. The decisive check for the current issue is: The alternate port shows a deliberate discarding role while the active tree remains connected.
A Junos engineer proposes this response: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance. The situation is: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. Which technical principle BEST justifies the response?
Spanning tree blocks redundant Layer 2 paths to avoid forwarding loops. This is the controlling mechanism in the specific case: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. It predicts the acceptance result: The alternate port shows a deliberate discarding role while the active tree remains connected.
Edge-port designation avoids normal network-bridge convergence assumptions for host ports. This principle explains a separate situation: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. For this issue the relevant mechanism is: Spanning tree blocks redundant Layer 2 paths to avoid forwarding loops.
Rapid source-MAC moves among ports can indicate an unstable bridged topology. This principle explains a separate situation: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. For this issue the relevant mechanism is: Spanning tree blocks redundant Layer 2 paths to avoid forwarding loops.
Private VLAN promiscuous ports connect shared services to otherwise restricted secondary ports. This principle explains a separate situation: A private-VLAN deployment places the default-gateway interface on an isolated host port and no tenants can reach it. For this issue the relevant mechanism is: Spanning tree blocks redundant Layer 2 paths to avoid forwarding loops.
A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. If the team bypasses or fails to implement the targeted correction (Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance.), which direct operational risk or residual exposure is MOST relevant?
Forcing all parallel bridging links to forward can create broadcast storms and MAC flapping. This is the consequence linked to the observed situation: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. It is prevented by: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance. The underlying reason is: Spanning tree blocks redundant Layer 2 paths to avoid forwarding loops.
Marking actual switch-to-switch links as edge can weaken topology change safeguards. This risk belongs to a different operational problem: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The stated condition instead exposes this direct risk: Forcing all parallel bridging links to forward can create broadcast storms and MAC flapping. The appropriate mitigation is: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance.
Adding more VLAN trunks before eliminating a loop may amplify a broadcast storm. This risk belongs to a different operational problem: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The stated condition instead exposes this direct risk: Forcing all parallel bridging links to forward can create broadcast storms and MAC flapping. The appropriate mitigation is: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance.
A gateway connected as an isolated host cannot serve the intended restricted segment properly. This risk belongs to a different operational problem: A private-VLAN deployment places the default-gateway interface on an isolated host port and no tenants can reach it. The stated condition instead exposes this direct risk: Forcing all parallel bridging links to forward can create broadcast storms and MAC flapping. The appropriate mitigation is: Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance.
A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. Which targeted engineering change is MOST directly justified by the observed evidence?
Inspect Ethernet MAC learning/move logs and spanning-tree port changes on the implicated VLANs. This change specifically addresses the reported evidence: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The relevant protocol mechanism is: Rapid source-MAC moves among ports can indicate an unstable bridged topology. A decisive acceptance test would be: MAC move activity stops after the loop path is eliminated and the STP topology stabilizes.
Inspect the port's selected STP role, root cost and designated bridge information for its VLAN/instance. This is a valid solution to a different Junos situation: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. It does not directly correct the specific failure evidence here: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The required targeted change is: Inspect Ethernet MAC learning/move logs and spanning-tree port changes on the implicated VLANs.
Apply the supported spanning-tree edge-port role only on the true endpoint-facing access port. This is a valid solution to a different Junos situation: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. It does not directly correct the specific failure evidence here: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The required targeted change is: Inspect Ethernet MAC learning/move logs and spanning-tree port changes on the implicated VLANs.
Restore a coherent STP or aggregated-link design instead of forwarding two independent looped bridges. This is a valid solution to a different Junos situation: A switched campus has more than one active uplink and staff remove STP protection to recover bandwidth after a topology change. It does not directly correct the specific failure evidence here: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The required targeted change is: Inspect Ethernet MAC learning/move logs and spanning-tree port changes on the implicated VLANs.
A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The proposed correction is: Inspect Ethernet MAC learning/move logs and spanning-tree port changes on the implicated VLANs. Which observation MOST directly confirms this fault is resolved?
MAC move activity stops after the loop path is eliminated and the STP topology stabilizes. This is the direct acceptance evidence for the observed failure: A campus switch has high MAC move counts during bursts and the upstream team suspects a Layer 2 loop rather than a routing failure. The mechanism being validated is: Rapid source-MAC moves among ports can indicate an unstable bridged topology.
The alternate port shows a deliberate discarding role while the active tree remains connected. That would validate a different condition: A redundant L2 link is unexpectedly blocked and engineers believe it indicates a physical error rather than spanning-tree loop prevention. The decisive check for the current issue is: MAC move activity stops after the loop path is eliminated and the STP topology stabilizes.
The workstation port enters forwarding promptly without creating transit-device bridging loops. That would validate a different condition: An edge desk port is treated as a transit switch link and waits for STP convergence every time a workstation reconnects. The decisive check for the current issue is: MAC move activity stops after the loop path is eliminated and the STP topology stabilizes.
The topology forwards without duplicate broadcast replication or unstable MAC tables. That would validate a different condition: A switched campus has more than one active uplink and staff remove STP protection to recover bandwidth after a topology change. The decisive check for the current issue is: MAC move activity stops after the loop path is eliminated and the STP topology stabilizes.
Please check your mailbox for a message from support@examlabs.com and follow the directions.