You save $69.98
A switch has two possible root paths for VLAN 144. Path A has total STP cost 8 and path B has cost 4. An engineer raises the interface cost of path B to 12 without modifying other costs. Which selection should be expected after convergence?
STP root-port selection prioritizes the lowest accumulated root path cost. After changing B to 12, A provides the lower-cost path to the same root.
STP recalculates its topology after relevant cost changes and does not lock a root port forever.
Normal STP selects one root port for each per-VLAN instance.
Interface path cost changes do not replace the bridge-ID election of the root bridge.
A downstream designated trunk port sees a new access switch advertising an unexpectedly superior root BPDU for VLAN 145. The campus design requires the current distribution switch to remain root without permanently shutting the link. Which STP guard is designed for this event?
Root guard prevents a designated port from accepting a superior root and transitioning toward that bridge; it can move the port to root-inconsistent until the superior BPDUs stop.
BPDU guard err-disables ports upon receiving BPDUs and is not the normal role-preserving choice on BPDU-speaking inter-switch trunks.
Loop guard handles missing expected BPDUs on non-designated ports, not active superior-root claims on a designated port.
PortFast does not prevent a neighboring switch from advertising a better root and is unsafe as a root-protection strategy here.
An operator uses the CLI `spanning-tree vlan 146 priority 4096` on a distribution switch. The change is accepted, but a neighbor still has VLAN 146 bridge priority 0. Which observation is correct?
Bridge-ID comparison prefers the lowest priority value; priority 0 beats 4096, so a local priority change is not proof that the switch became root.
Lower numeric STP bridge priority wins, and 0 is smaller than 4096.
A per-VLAN STP instance elects a single best root bridge ID.
An accepted bridge priority value changes root preference, not the existence of STP.
At a municipal utility, the branch support lead needs controller-managed access points to serve SSIDs while centralized policy lives on a wireless LAN controller. Which choice best addresses the stated requirement?
Lightweight APs are managed by a controller that defines WLAN settings and AP policy.
Autonomous APs manage much of their own configuration.
Hubs have no WLAN control plane.
DHCP address assignment alone does not prove controller association.
At a stadium, the branch support lead requires local wireless client switching even during loss of a central controller WAN path at a small remote branch. Which choice best addresses the stated requirement?
FlexConnect can locally switch client data at a branch under supported designs.
Monitor modes are not normal client access service.
Central switching cannot cross a failed WAN path.
Time service does not supply radio client access.
At a design agency, the infrastructure lead wants an AP to observe wireless security events without providing ordinary client access on that radio. Which choice best addresses the stated requirement?
Monitor APs scan RF channels for wireless events rather than serving normal data clients.
Routing passive-interface settings do not turn a router into an RF monitor.
NTP cannot replace radio scanning modes.
Monitor-only radios generally do not host normal client associations.
At a design agency, the on-call technician needs client association and ordinary wireless traffic forwarding on a radio managed by the WLC. Which choice best addresses the stated requirement?
Client-serving AP mode makes the AP available to stations on configured WLANs.
A backhaul-only bridge design does not automatically service WLAN clients.
Sniffer-only radios capture packets and are not normal client APs.
Monitor-only mode is primarily for capture/security observation and does not serve normal WLAN clients on that radio.
At a manufacturing plant, the campus network lead must plan centrally managed enterprise WLAN roaming across many overlapping AP cells. Which choice best addresses the stated requirement?
Consistent WLAN policy and RF planning enable clients to roam across cells subject to client behavior.
Different networks can interrupt intended seamless roaming.
DHCP lease handling is not the RF association/roaming control mechanism; controller and AP WLAN policy must be configured.
Removing authentication creates security risks and does not establish controlled roaming.
At an engineering company, a network operations engineer needs controller-managed access points to serve SSIDs while centralized policy lives on a wireless LAN controller. During review, someone proposes: "Use standalone autonomous APs with no WLC association and expect central WLC commands to configure them." Which technical explanation most directly shows why this proposal does not solve the requirement?
Autonomous APs manage much of their own configuration. The effective remedy is to deploy lightweight APs associated to the intended WLC.
DHCP address assignment alone does not prove controller association. It concerns a different proposed change, not the change being evaluated.
Hubs have no WLAN control plane. A true general network fact is not necessarily the direct diagnosis. The named change was use standalone autonomous aps with no wlc association and expect central wlc commands to configure them, whose relevant defect is that autonomous APs manage much of their own configuration.
Lightweight APs are managed by a controller that defines WLAN settings and AP policy. That distinction is technically relevant elsewhere, but it does not identify the failure of the proposed use standalone autonomous aps with no wlc association and expect central wlc commands to configure them. The actual issue is that autonomous APs manage much of their own configuration.
At an e-commerce platform, the infrastructure lead requires local wireless client switching even during loss of a central controller WAN path at a small remote branch. During review, someone proposes: "Require all client data to traverse a broken controller tunnel despite no WAN." Which technical explanation most directly shows why this proposal does not solve the requirement?
Central switching cannot cross a failed WAN path. The effective remedy is to evaluate FlexConnect local switching and survivability for supported APs.
Time service does not supply radio client access. It concerns a different proposed change, not the change being evaluated.
Monitor modes are not normal client access service. The statement addresses a different mechanism. Here the engineer specifically proposed require all client data to traverse a broken controller tunnel despite no wan; the decisive limitation is that central switching cannot cross a failed WAN path.
FlexConnect can locally switch client data at a branch under supported designs. This observation would apply to another device or feature, not the proposed require all client data to traverse a broken controller tunnel despite no wan. For this scenario, central switching cannot cross a failed WAN path is the direct cause.
At a field-service firm, the campus network lead wants an AP to observe wireless security events without providing ordinary client access on that radio. During review, someone proposes: "Put all user data on monitor-only radios." Which technical explanation most directly shows why this proposal does not solve the requirement?
Monitor-only radios generally do not host normal client associations. The effective remedy is to use an appropriate wireless monitor/sensor AP mode for air monitoring.
Routing passive-interface settings do not turn a router into an RF monitor. That distinction is technically relevant elsewhere, but it does not identify the failure of the proposed put all user data on monitor-only radios. The actual issue is that monitor-only radios generally do not host normal client associations.
Monitor APs scan RF channels for wireless events rather than serving normal data clients. The statement addresses a different mechanism. Here the engineer specifically proposed put all user data on monitor-only radios; the decisive limitation is that monitor-only radios generally do not host normal client associations.
NTP cannot replace radio scanning modes. It concerns a different proposed change, not the change being evaluated.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (760 Questions, Last Updated on Nov 4, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
