You save $69.98
200-301 Premium Bundle
- Premium File 760 Questions & Answers
- Last Update: Nov 4, 2026
- Training Course 271 Lectures
- Study Guide 1969 Pages
You save $69.98
At a supply depot, the migration lead increased the LACP member count for port-channel 4 but observes one large TCP transfer not reaching total summed link rates. Which explanation is correct?
EtherChannel uses a load-balancing hash to select member links per flow/key, so many distinct flows can use aggregate capacity. One long flow often stays on one member to preserve ordering.
LACP aggregates interfaces into a logical forwarding channel; it is more than media testing.
Per-packet round-robin is not the standard Cisco LACP load-distribution guarantee and can reorder packets.
A single hashed flow is not generally able to consume all physical member links as one logical high-rate lane.
At a field-service firm, the infrastructure lead is configuring GigabitEthernet1/0/7 in a negotiated LACP EtherChannel 29; the far end uses LACP passive. Which local mode should be set?
Active initiates LACP negotiation for port-channel 29; it can form with a correctly configured active or passive peer if member parameters match.
Desirable belongs to PAgP, not IEEE LACP, and will not negotiate the LACP-only far end.
Mode on forces static aggregation without LACP negotiation; it is not the requested LACP dynamic negotiation.
Passive alone waits for the peer to initiate LACP; if both sides are passive, negotiation will not start.
An LACP EtherChannel forms correctly, yet `show spanning-tree vlan 20` lists Port-channel10 as an alternate/discarding port. What is the best interpretation?
Spanning tree treats a correctly bundled EtherChannel as one logical port and can select an alternate/discarding role. LACP membership and STP forwarding are separate decisions.
A logical Port-channel participates in STP. A blocked Port-channel does not prove LACP negotiation failure.
STP applies the selected logical-port role to the bundle; individual members do not independently circumvent a blocked channel.
Changing the aggregation negotiation method does not eliminate the Layer 2 topology loop or change STP's need to block a redundant path.
At a distribution center, the campus network lead sees member ports intermittently suspended from negotiated EtherChannel 10 after a template push. Which configuration practice should be checked first?
For a stable LACP EtherChannel 10, member interfaces must be compatible with the logical port-channel policy. Mismatched VLAN or physical parameters may suspend members.
An incompatible speed/duplex member typically cannot join the same working aggregate.
VLAN inconsistency between bundled Layer 2 members violates the expected common logical connection.
Native VLAN mismatches cause inconsistent untagged-frame classification across the bundle.
A switch reports `Po7(SU)` with members `Gi1/0/1(P)` and `Gi1/0/2(P)` in `show etherchannel summary`. What does the combined flag evidence establish?
`S` identifies Layer 2 operation, `U` in use, and `(P)` on each interface denotes bundled membership. The summary is a direct operational check, unlike a configuration line alone.
A routed port-channel uses a different Layer 3 indicator; `(P)` is not an administrative-down flag.
Both listed members show `(P)`, so the assertion that only one joined contradicts the current operational summary.
Suspended members show `(s)` and an unused bundle would not show the reported active `SU` state.
Two LACP members show `(P)` in `show etherchannel summary`, but workstations in VLAN 40 still cannot cross the port-channel while VLAN 20 succeeds. What operational evidence should be inspected next?
LACP proves link aggregation, not that every tagged VLAN is carried. `show interfaces trunk` for the logical bundle and VLAN state can reveal omitted VLAN 40.
LACP neighbor state addresses negotiation and aggregation; it does not guarantee trunk VLAN membership or forwarding availability.
The LACP system priority participates in aggregation identity/election and does not encode the trunk VLAN allowed list.
Load-sharing hashes select member links for flows; they do not configure or verify VLAN carriage on the logical trunk.
A port-channel has four 1-Gbps members. Telemetry shows four different TCP flows distributed across different members, but a single large TCP flow never exceeds roughly 1 Gbps. What explains this?
EtherChannel balances traffic using selected header fields. The total bundle capacity is available across eligible flows, not as a guaranteed 4-Gbps pipe for a single flow.
Deterministic hashing is used to avoid out-of-order delivery; it does not guarantee per-packet spreading for a given flow.
EtherChannel members generally require matching port properties; mismatches can prevent aggregation.
LACP does not change the physical member link speed; it coordinates aggregation and link eligibility.
At a bank branch, the campus network lead must identify the Rapid PVST+ root for VLAN 142; all listed switches are on the same Layer 2 topology and no superior external BPDU exists. Which switch wins?
SW-2 has bridge priority 0; root selection compares bridge ID priority first and MAC as tie-breaker. It wins because this is the lowest priority in the presented candidates.
SW-1 has bridge priority 20480; root selection compares bridge ID priority first and MAC as tie-breaker. The winning bridge has lower priority 0, so this cannot be root despite its MAC value.
SW-4 has bridge priority 24576; root selection compares bridge ID priority first and MAC as tie-breaker. The winning bridge has lower priority 0, so this cannot be root despite its MAC value.
SW-3 has bridge priority 16384; root selection compares bridge ID priority first and MAC as tie-breaker. The winning bridge has lower priority 0, so this cannot be root despite its MAC value.
At a customer support center, the security and networking lead examines four ports on a non-root Rapid PVST+ switch for VLAN 69. Their received BPDUs identify the same root bridge but yield different total path costs. Which port becomes the root port?
Root-port selection begins with the lowest accumulated path cost toward the root bridge. Gi1/0/1 has cost 12; it is preferred, assuming equal root IDs and no other superior tie-breakers.
Root-port selection begins with the lowest accumulated path cost toward the root bridge. Gi1/0/4 has cost 28; cost 12 is better than 28, so this path is not selected.
Root-port selection begins with the lowest accumulated path cost toward the root bridge. Gi1/0/2 has cost 16; cost 12 is better than 16, so this path is not selected.
Root-port selection begins with the lowest accumulated path cost toward the root bridge. Gi1/0/3 has cost 22; cost 12 is better than 22, so this path is not selected.
At a payment processor, the infrastructure lead connects normal user PCs on VLAN 156. The requirement is fast edge-port activation and automatic protection if someone attaches an unmanaged switch sending BPDUs. What should be used?
PortFast helps a verified endpoint-facing port transition to forwarding quickly, while BPDU guard can disable it if it unexpectedly receives BPDUs. This protects VLAN 156 against an unauthorized bridged switch.
Suppressing BPDUs on transit links can hide loops and compromise spanning-tree protection rather than safely enforcing the edge boundary.
PortFast should be used cautiously on true edge ports; an inter-switch trunk can form a loop and should not blindly be treated as an endpoint.
A typical laptop is not a managed bridge participating in STP root election; its fictional priority does not protect the access link.
At a media studio, a network operations engineer wants the authorized distribution pair to remain Rapid PVST+ root for VLAN 196 even if an access-layer switch advertises a superior bridge ID. Which safeguard fits?
Root guard keeps an unexpected superior BPDU from changing the intended root hierarchy on the protected designated segment. It can place the receiving port into root-inconsistent state.
BPDU guard is appropriate on endpoint edges, not every legitimate switch-to-switch link carrying BPDUs.
802.1Q VLAN tags do not stop Layer 2 loops within each VLAN.
PortFast bypasses some transition behavior on edge ports; core trunks should participate normally in STP.
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.