Topic 06 Practice Test 2 covers 802.1Q Trunking and EtherChannel Troubleshooting for Cisco 350-401 ENCOR. For broader exam preparation, review the Cisco 350-401 ENCOR Exam Dumps. Every option includes focused technical reasoning explaining both the Cisco enterprise networking concept and its fit to the scenario.
Question 1
A troubleshooting ticket states that engineers must diagnose why a port remains access mode after an engineer assumed it would become a trunk automatically. Which action addresses the root requirement most directly? Choose ONE.
- STP on the port-channel
- static 802.1Q trunk mode
- PAgP desirable mode
- DTP dynamic desirable
Correct Answer(s)
B
Rationale
- STP on the port-channel provides spanning-tree control of the logical bundle, which belongs to STP and aggregation decisions. The stem instead requires engineers to diagnose why a port remains access mode after an engineer assumed it would become a trunk automatically. That result comes from static 802.1Q trunk mode; selecting STP on the port-channel would leave the tested condition unresolved.
- Static 802.1Q trunk mode provides an administratively forced trunk. That matches the requirement to diagnose why a port remains access mode after an engineer assumed it would become a trunk automatically. It directly controls the relevant trunk mode behavior, so the alternatives would change a different condition. This makes static 802.1Q trunk mode the direct fit for this case.
- PAgP desirable mode solves the wrong problem by producing active PAgP EtherChannel negotiation. It fits PAgP negotiation needs, but the tested task is to diagnose why a port remains access mode after an engineer assumed it would become a trunk automatically. That requirement maps directly to static 802.1Q trunk mode.
- DTP dynamic desirable is not an equivalent substitute because it creates active DTP trunk negotiation. That serves DTP negotiation needs, not the requirement to diagnose why a port remains access mode after an engineer assumed it would become a trunk automatically. static 802.1Q trunk mode acts on the condition described in the stem.
Question 2
While comparing the running configuration with the intended state, the team needs to explain why untagged frames are entering VLAN 99 on one switch but VLAN 1 on its trunk peer. Which choice is correct? Choose ONE.
- Layer 3 port-channel interface
- DTP dynamic auto
- PAgP auto mode
- matching native VLAN
Correct Answer(s)
D
Rationale
- Layer 3 port-channel interface is technically useful for a single routed logical interface over several links in Layer 3 aggregation work. The tested task is to explain why untagged frames are entering VLAN 99 on one switch but VLAN 1 on its trunk peer, however. That behavior is governed by matching native VLAN, making this option a distractor.
- DTP dynamic auto is related but operationally wrong because it yields passive DTP trunk negotiation. That supports DTP negotiation work. This case requires engineers to explain why untagged frames are entering VLAN 99 on one switch but VLAN 1 on its trunk peer, so matching native VLAN fits the stated condition.
- Do not select PAgP auto mode; its effect is passive PAgP EtherChannel participation, a valid PAgP negotiation function. The scenario requires engineers to explain why untagged frames are entering VLAN 99 on one switch but VLAN 1 on its trunk peer. That requirement maps to matching native VLAN, not to this alternative.
- The best answer is matching native VLAN, which supplies consistent handling of untagged frames. Because the requirement is to explain why untagged frames are entering VLAN 99 on one switch but VLAN 1 on its trunk peer, this option matches the trunk VLAN consistency decision and leaves adjacent functions untouched. This makes matching native VLAN the direct fit for this case.
Question 3
A change request will be accepted only if it can identify why hosts in VLAN 70 fail across a trunk even though VLAN 10 and VLAN 20 traverse normally. Which mechanism is the most appropriate? Choose ONE.
- allowed VLAN list
- switchport nonegotiate
- restore required VLAN on the trunk
- static EtherChannel on mode
Correct Answer(s)
A
Rationale
- Allowed VLAN list matches the desired state by providing forwarding of the required VLAN on the trunk. Since engineers must identify why hosts in VLAN 70 fail across a trunk even though VLAN 10 and VLAN 20 traverse normally, this selection acts on the relevant trunk VLAN filtering behavior and directly satisfies the requirement. This makes allowed VLAN list the direct fit for this case.
- Switchport nonegotiate would change a trunk that does not send DTP, which is appropriate in DTP suppression scenarios. The present stem asks engineers to identify why hosts in VLAN 70 fail across a trunk even though VLAN 10 and VLAN 20 traverse normally. That is why allowed VLAN list is the correct mechanism instead.
- Restore required VLAN on the trunk is not an equivalent substitute because it creates targeted restoration of the missing VLAN. That serves trunk VLAN filtering needs, not the requirement to identify why hosts in VLAN 70 fail across a trunk even though VLAN 10 and VLAN 20 traverse normally. allowed VLAN list acts on the condition described in the stem.
- Static EtherChannel on mode is a neighboring feature that yields a protocol-free static EtherChannel for static aggregation needs. This scenario requires the team to identify why hosts in VLAN 70 fail across a trunk even though VLAN 10 and VLAN 20 traverse normally. The required behavior belongs to allowed VLAN list, so this alternative is mismatched.
Question 4
During a maintenance window, the team must remediate two dynamic-auto switchports that never establish an 802.1Q trunk. Which option is the best fit for this exact constraint? Choose ONE.
- correct access VLAN assignment
- static 802.1Q trunk mode
- DTP dynamic desirable
- consistent EtherChannel member parameters
Correct Answer(s)
C
Rationale
- Correct access VLAN assignment should not be changed for this issue; it provides placement of an endpoint in the intended VLAN for access-port VLAN cases. The actual requirement is to remediate two dynamic-auto switchports that never establish an 802.1Q trunk, which is handled by DTP dynamic desirable.
- Static 802.1Q trunk mode is related but operationally wrong because it yields an administratively forced trunk. That supports trunk mode work. This case requires engineers to remediate two dynamic-auto switchports that never establish an 802.1Q trunk, so DTP dynamic desirable fits the stated condition.
- Choose DTP dynamic desirable. It creates active DTP trunk negotiation, while the stem requires engineers to remediate two dynamic-auto switchports that never establish an 802.1Q trunk. This directly satisfies the DTP negotiation condition and avoids changing a feature that is not implicated. This makes DTP dynamic desirable the direct fit for this case.
- Consistent EtherChannel member parameters does not resolve the requirement; it provides compatible member-link configuration for bundle consistency decisions. Because the stem requires engineers to remediate two dynamic-auto switchports that never establish an 802.1Q trunk, DTP dynamic desirable is the mechanism that should be selected.
Question 5
A troubleshooting ticket states that engineers must keep the local interface passive in DTP while still allowing a desirable neighbor to form the trunk. Which action addresses the root requirement most directly? Choose ONE.
- port-channel logical interface configuration
- matching native VLAN
- DTP dynamic auto
- LACP active mode
Correct Answer(s)
C
Rationale
- Port-channel logical interface configuration fails on scenario fit: it gives consistent aggregate-level configuration for port-channel configuration decisions. The evidence says engineers must keep the local interface passive in DTP while still allowing a desirable neighbor to form the trunk, and DTP dynamic auto is the option that provides the needed behavior.
- Matching native VLAN would change consistent handling of untagged frames, which is appropriate in trunk VLAN consistency scenarios. The present stem asks engineers to keep the local interface passive in DTP while still allowing a desirable neighbor to form the trunk. That is why DTP dynamic auto is the correct mechanism instead.
- DTP dynamic auto fits because it delivers passive DTP trunk negotiation. The scenario specifically asks engineers to keep the local interface passive in DTP while still allowing a desirable neighbor to form the trunk. This is the DTP negotiation control that changes the tested behavior directly. This makes DTP dynamic auto the direct fit for this case.
- LACP active mode would leave the key condition unchanged because it supplies active standards-based EtherChannel negotiation. That is useful for LACP negotiation tasks, while this scenario requires the team to keep the local interface passive in DTP while still allowing a desirable neighbor to form the trunk using DTP dynamic auto.
Question 6
While comparing the running configuration with the intended state, the team needs to remove unwanted DTP advertisements seen by a third-party device on an explicitly configured trunk. Which choice is correct? Choose ONE.
- show etherchannel summary
- switchport nonegotiate
- allowed VLAN list
- LACP passive mode
Correct Answer(s)
B
Rationale
- Show etherchannel summary targets direct EtherChannel membership verification, so it fits another EtherChannel verification condition. The question requires the team to remove unwanted DTP advertisements seen by a third-party device on an explicitly configured trunk. Since switchport nonegotiate produces the needed behavior, this choice would not fix the root requirement.
- For this case, switchport nonegotiate supplies a trunk that does not send DTP. The operational need is to remove unwanted DTP advertisements seen by a third-party device on an explicitly configured trunk. That correspondence makes it the correct DTP suppression mechanism for the scenario. This makes switchport nonegotiate the direct fit for this case.
- Allowed VLAN list should not be changed for this issue; it provides forwarding of the required VLAN on the trunk for trunk VLAN filtering cases. The actual requirement is to remove unwanted DTP advertisements seen by a third-party device on an explicitly configured trunk, which is handled by switchport nonegotiate.
- LACP passive mode controls passive standards-based EtherChannel participation and is useful for LACP negotiation work. This case requires the team to remove unwanted DTP advertisements seen by a third-party device on an explicitly configured trunk. Because switchport nonegotiate supplies that behavior, this option acts on the wrong requirement.
Question 7
A change request will be accepted only if it can correct a desk port that has link and DHCP but receives an address from the wrong user subnet. Which mechanism is the most appropriate? Choose ONE.
- correct access VLAN assignment
- DTP dynamic desirable
- PAgP desirable mode
- correct channel-group protocol pairing
Correct Answer(s)
A
Rationale
- Correct access VLAN assignment is the functional match: it provides placement of an endpoint in the intended VLAN. The question requires the network to correct a desk port that has link and DHCP but receives an address from the wrong user subnet. That makes this the relevant access-port VLAN choice for the stated evidence. This makes correct access VLAN assignment the direct fit for this case.
- DTP dynamic desirable would leave the key condition unchanged because it supplies active DTP trunk negotiation. That is useful for DTP negotiation tasks, while this scenario requires the team to correct a desk port that has link and DHCP but receives an address from the wrong user subnet using correct access VLAN assignment.
- PAgP desirable mode does not match the evidence because it provides active PAgP EtherChannel negotiation. That is a PAgP negotiation function, whereas the stem requires engineers to correct a desk port that has link and DHCP but receives an address from the wrong user subnet. correct access VLAN assignment is the option tied to that task.
- Correct channel-group protocol pairing has a different role: it supplies matching aggregation protocol behavior in protocol compatibility scenarios. The engineer must correct a desk port that has link and DHCP but receives an address from the wrong user subnet here. That makes correct access VLAN assignment the direct answer and this option unsuitable.
Question 8
During a maintenance window, the team must remediate an LACP passive/passive pair that leaves both physical links unbundled. Which option is the best fit for this exact constraint? Choose ONE.
- EtherChannel load-balancing method
- PAgP auto mode
- DTP dynamic auto
- LACP active mode
Correct Answer(s)
D
Rationale
- EtherChannel load-balancing method lacks the needed control effect; it provides a more suitable per-flow distribution key for load balancing situations. Here the team must remediate an LACP passive/passive pair that leaves both physical links unbundled, which LACP active mode enables directly.
- PAgP auto mode would be useful when passive PAgP EtherChannel participation is needed for PAgP negotiation work. This question instead asks the team to remediate an LACP passive/passive pair that leaves both physical links unbundled. The correct control is LACP active mode, so this alternative fails scenario fit.
- DTP dynamic auto controls passive DTP trunk negotiation and is useful for DTP negotiation work. This case requires the team to remediate an LACP passive/passive pair that leaves both physical links unbundled. Because LACP active mode supplies that behavior, this option acts on the wrong requirement.
- Use LACP active mode; its operational effect is active standards-based EtherChannel negotiation. The stated task is to remediate an LACP passive/passive pair that leaves both physical links unbundled. That mechanism addresses the LACP negotiation requirement without altering an unrelated control. This makes LACP active mode the direct fit for this case.
Question 9
A troubleshooting ticket states that engineers must keep one side non-initiating after the peer has been changed to LACP active and the bundle is forming. Which action addresses the root requirement most directly? Choose ONE.
- switchport nonegotiate
- static EtherChannel on mode
- LACP passive mode
- STP on the port-channel
Correct Answer(s)
C
Rationale
- Switchport nonegotiate does not match the evidence because it provides a trunk that does not send DTP. That is a DTP suppression function, whereas the stem requires engineers to keep one side non-initiating after the peer has been changed to LACP active and the bundle is forming. LACP passive mode is the option tied to that task.
- Static EtherChannel on mode would be an unnecessary change because it controls a protocol-free static EtherChannel. That is relevant to static aggregation requirements, while the current task is to keep one side non-initiating after the peer has been changed to LACP active and the bundle is forming using LACP passive mode.
- LACP passive mode is the precise choice because it yields passive standards-based EtherChannel participation. Here, the network must keep one side non-initiating after the peer has been changed to LACP active and the bundle is forming. The feature therefore resolves the tested LACP negotiation condition instead of a different issue. This makes LACP passive mode the direct fit for this case.
- STP on the port-channel is plausible because it delivers spanning-tree control of the logical bundle for STP and aggregation cases. Here the team must keep one side non-initiating after the peer has been changed to LACP active and the bundle is forming. LACP passive mode directly controls that state, while this option does not.
Question 10
While comparing the running configuration with the intended state, the team needs to fix a PAgP auto/auto pair where neither switch starts negotiation. Which choice is correct? Choose ONE.
- PAgP desirable mode
- correct access VLAN assignment
- consistent EtherChannel member parameters
- Layer 3 port-channel interface
Correct Answer(s)
A
Rationale
- Use PAgP desirable mode to obtain active PAgP EtherChannel negotiation. That is exactly what the team needs when it must fix a PAgP auto/auto pair where neither switch starts negotiation. The PAgP negotiation decision is therefore resolved by this mechanism, not the alternatives. This makes PAgP desirable mode the direct fit for this case.
- Correct access VLAN assignment would be useful when placement of an endpoint in the intended VLAN is needed for access-port VLAN work. This question instead asks the team to fix a PAgP auto/auto pair where neither switch starts negotiation. The correct control is PAgP desirable mode, so this alternative fails scenario fit.
- Consistent EtherChannel member parameters solves a different problem by providing compatible member-link configuration. That matters for bundle consistency decisions, but this case requires engineers to fix a PAgP auto/auto pair where neither switch starts negotiation. PAgP desirable mode matches the evidence more precisely.
- Layer 3 port-channel interface would affect a single routed logical interface over several links, a legitimate Layer 3 aggregation purpose. The stem instead depends on engineers being able to fix a PAgP auto/auto pair where neither switch starts negotiation. PAgP desirable mode provides that exact behavior, leaving this option operationally wrong.
Question 11
A change request will be accepted only if it can preserve a passive PAgP role after the peer is deliberately changed to desirable. Which mechanism is the most appropriate? Choose ONE.
- restore required VLAN on the trunk
- LACP active mode
- port-channel logical interface configuration
- PAgP auto mode
Correct Answer(s)
D
Rationale
- Restore required VLAN on the trunk is not selected because it governs targeted restoration of the missing VLAN. That function belongs to trunk VLAN filtering work. The required task is to preserve a passive PAgP role after the peer is deliberately changed to desirable, and that task is handled by PAgP auto mode.
- LACP active mode would be an unnecessary change because it controls active standards-based EtherChannel negotiation. That is relevant to LACP negotiation requirements, while the current task is to preserve a passive PAgP role after the peer is deliberately changed to desirable using PAgP auto mode.
- Port-channel logical interface configuration misses the controlling requirement because its result is consistent aggregate-level configuration. That fits port-channel configuration tasks. Here, the network needs engineers to preserve a passive PAgP role after the peer is deliberately changed to desirable, so PAgP auto mode is the relevant mechanism.
- PAgP auto mode is correct because it creates passive PAgP EtherChannel participation. In this scenario, engineers must preserve a passive PAgP role after the peer is deliberately changed to desirable. The option acts on the exact PAgP negotiation decision described in the stem. This makes PAgP auto mode the direct fit for this case.
Question 12
During a maintenance window, the team must explain why forcing mode on at only one end does not safely create a negotiated EtherChannel. Which option is the best fit for this exact constraint? Choose ONE.
- show etherchannel summary
- static EtherChannel on mode
- LACP passive mode
- static 802.1Q trunk mode
Correct Answer(s)
B
Rationale
- Show etherchannel summary solves the wrong problem by producing direct EtherChannel membership verification. It fits EtherChannel verification needs, but the tested task is to explain why forcing mode on at only one end does not safely create a negotiated EtherChannel. That requirement maps directly to static EtherChannel on mode.
- Select static EtherChannel on mode for a protocol-free static EtherChannel. The stem makes the requirement explicit: explain why forcing mode on at only one end does not safely create a negotiated EtherChannel. That result is governed by this static aggregation mechanism rather than by the neighboring options. This makes static EtherChannel on mode the direct fit for this case.
- LACP passive mode solves a different problem by providing passive standards-based EtherChannel participation. That matters for LACP negotiation decisions, but this case requires engineers to explain why forcing mode on at only one end does not safely create a negotiated EtherChannel. static EtherChannel on mode matches the evidence more precisely.
- Static 802.1Q trunk mode provides an administratively forced trunk, which belongs to trunk mode decisions. The stem instead requires engineers to explain why forcing mode on at only one end does not safely create a negotiated EtherChannel. That result comes from static EtherChannel on mode; selecting static 802.1Q trunk mode would leave the tested condition unresolved.
Question 13
A troubleshooting ticket states that engineers must identify why a new trunk member is marked incompatible after being added to an existing port-channel. Which action addresses the root requirement most directly? Choose ONE.
- consistent EtherChannel member parameters
- matching native VLAN
- correct channel-group protocol pairing
- PAgP desirable mode
Correct Answer(s)
A
Rationale
- Consistent EtherChannel member parameters is appropriate because the result is compatible member-link configuration. The scenario requires engineers to identify why a new trunk member is marked incompatible after being added to an existing port-channel. This feature controls that bundle consistency behavior specifically, so it is the best fit. This makes consistent EtherChannel member parameters the direct fit for this case.
- Matching native VLAN is technically useful for consistent handling of untagged frames in trunk VLAN consistency work. The tested task is to identify why a new trunk member is marked incompatible after being added to an existing port-channel, however. That behavior is governed by consistent EtherChannel member parameters, making this option a distractor.
- Do not select correct channel-group protocol pairing; its effect is matching aggregation protocol behavior, a valid protocol compatibility function. The scenario requires engineers to identify why a new trunk member is marked incompatible after being added to an existing port-channel. That requirement maps to consistent EtherChannel member parameters, not to this alternative.
- PAgP desirable mode misses the controlling requirement because its result is active PAgP EtherChannel negotiation. That fits PAgP negotiation tasks. Here, the network needs engineers to identify why a new trunk member is marked incompatible after being added to an existing port-channel, so consistent EtherChannel member parameters is the relevant mechanism.
Question 14
While comparing the running configuration with the intended state, the team needs to stop member-by-member changes from producing different trunk behavior inside one logical bundle. Which choice is correct? Choose ONE.
- allowed VLAN list
- PAgP auto mode
- EtherChannel load-balancing method
- port-channel logical interface configuration
Correct Answer(s)
D
Rationale
- Allowed VLAN list is not an equivalent substitute because it creates forwarding of the required VLAN on the trunk. That serves trunk VLAN filtering needs, not the requirement to stop member-by-member changes from producing different trunk behavior inside one logical bundle. port-channel logical interface configuration acts on the condition described in the stem.
- PAgP auto mode solves the wrong problem by producing passive PAgP EtherChannel participation. It fits PAgP negotiation needs, but the tested task is to stop member-by-member changes from producing different trunk behavior inside one logical bundle. That requirement maps directly to port-channel logical interface configuration.
- EtherChannel load-balancing method is a neighboring feature that yields a more suitable per-flow distribution key for load balancing needs. This scenario requires the team to stop member-by-member changes from producing different trunk behavior inside one logical bundle. The required behavior belongs to port-channel logical interface configuration, so this alternative is mismatched.
- Choose port-channel logical interface configuration because its result is consistent aggregate-level configuration. The stem requires the team to stop member-by-member changes from producing different trunk behavior inside one logical bundle. That is a direct port-channel configuration match, not merely a related feature. This makes port-channel logical interface configuration the direct fit for this case.
Question 15
A change request will be accepted only if it can determine from operational state whether links are bundled, individual, or suspended before changing configuration. Which mechanism is the most appropriate? Choose ONE.
- DTP dynamic desirable
- STP on the port-channel
- show etherchannel summary
- static EtherChannel on mode
Correct Answer(s)
C
Rationale
- DTP dynamic desirable is related but operationally wrong because it yields active DTP trunk negotiation. That supports DTP negotiation work. This case requires engineers to determine from operational state whether links are bundled, individual, or suspended before changing configuration, so show etherchannel summary fits the stated condition.
- STP on the port-channel does not resolve the requirement; it provides spanning-tree control of the logical bundle for STP and aggregation decisions. Because the stem requires engineers to determine from operational state whether links are bundled, individual, or suspended before changing configuration, show etherchannel summary is the mechanism that should be selected.
- Show etherchannel summary directly produces direct EtherChannel membership verification. That is relevant because the team needs to determine from operational state whether links are bundled, individual, or suspended before changing configuration. For this EtherChannel verification decision, the feature changes the condition identified by the evidence. This makes show etherchannel summary the direct fit for this case.
- Do not select static EtherChannel on mode; its effect is a protocol-free static EtherChannel, a valid static aggregation function. The scenario requires engineers to determine from operational state whether links are bundled, individual, or suspended before changing configuration. That requirement maps to show etherchannel summary, not to this alternative.
Question 16
During a maintenance window, the team must resolve a protocol mismatch where LACP PDUs arrive but the local channel-group is configured for PAgP. Which option is the best fit for this exact constraint? Choose ONE.
- DTP dynamic auto
- correct channel-group protocol pairing
- Layer 3 port-channel interface
- consistent EtherChannel member parameters
Correct Answer(s)
B
Rationale
- DTP dynamic auto would change passive DTP trunk negotiation, which is appropriate in DTP negotiation scenarios. The present stem asks engineers to resolve a protocol mismatch where LACP PDUs arrive but the local channel-group is configured for PAgP. That is why correct channel-group protocol pairing is the correct mechanism instead.
- The required mechanism is correct channel-group protocol pairing, which gives matching aggregation protocol behavior. The stem calls for the team to resolve a protocol mismatch where LACP PDUs arrive but the local channel-group is configured for PAgP. That makes this the direct protocol compatibility answer rather than an adjacent workaround. This makes correct channel-group protocol pairing the direct fit for this case.
- Layer 3 port-channel interface fails on scenario fit: it gives a single routed logical interface over several links for Layer 3 aggregation decisions. The evidence says engineers must resolve a protocol mismatch where LACP PDUs arrive but the local channel-group is configured for PAgP, and correct channel-group protocol pairing is the option that provides the needed behavior.
- Consistent EtherChannel member parameters is a neighboring feature that yields compatible member-link configuration for bundle consistency needs. This scenario requires the team to resolve a protocol mismatch where LACP PDUs arrive but the local channel-group is configured for PAgP. The required behavior belongs to correct channel-group protocol pairing, so this alternative is mismatched.
Question 17
A troubleshooting ticket states that engineers must address uneven member utilization when all links are healthy and a small number of long-lived flows dominate. Which action addresses the root requirement most directly? Choose ONE.
- port-channel logical interface configuration
- restore required VLAN on the trunk
- switchport nonegotiate
- EtherChannel load-balancing method
Correct Answer(s)
D
Rationale
- Port-channel logical interface configuration does not resolve the requirement; it provides consistent aggregate-level configuration for port-channel configuration decisions. Because the stem requires engineers to address uneven member utilization when all links are healthy and a small number of long-lived flows dominate, EtherChannel load-balancing method is the mechanism that should be selected.
- Restore required VLAN on the trunk targets targeted restoration of the missing VLAN, so it fits another trunk VLAN filtering condition. The question requires the team to address uneven member utilization when all links are healthy and a small number of long-lived flows dominate. Since EtherChannel load-balancing method produces the needed behavior, this choice would not fix the root requirement.
- Switchport nonegotiate should not be changed for this issue; it provides a trunk that does not send DTP for DTP suppression cases. The actual requirement is to address uneven member utilization when all links are healthy and a small number of long-lived flows dominate, which is handled by EtherChannel load-balancing method.
- EtherChannel load-balancing method provides a more suitable per-flow distribution key. That matches the requirement to address uneven member utilization when all links are healthy and a small number of long-lived flows dominate. It directly controls the relevant load balancing behavior, so the alternatives would change a different condition. This makes EtherChannel load-balancing method the direct fit for this case.
Question 18
While comparing the running configuration with the intended state, the team needs to explain why spanning tree shows one port-channel interface instead of separate forwarding decisions for bundled members. Which choice is correct? Choose ONE.
- STP on the port-channel
- static 802.1Q trunk mode
- correct access VLAN assignment
- show etherchannel summary
Correct Answer(s)
A
Rationale
- The best answer is STP on the port-channel, which supplies spanning-tree control of the logical bundle. Because the requirement is to explain why spanning tree shows one port-channel interface instead of separate forwarding decisions for bundled members, this option matches the STP and aggregation decision and leaves adjacent functions untouched. This makes STP on the port-channel the direct fit for this case.
- Static 802.1Q trunk mode has a different role: it supplies an administratively forced trunk in trunk mode scenarios. The engineer must explain why spanning tree shows one port-channel interface instead of separate forwarding decisions for bundled members here. That makes STP on the port-channel the direct answer and this option unsuitable.
- Correct access VLAN assignment would leave the key condition unchanged because it supplies placement of an endpoint in the intended VLAN. That is useful for access-port VLAN tasks, while this scenario requires the team to explain why spanning tree shows one port-channel interface instead of separate forwarding decisions for bundled members using STP on the port-channel.
- Show etherchannel summary fails on scenario fit: it gives direct EtherChannel membership verification for EtherChannel verification decisions. The evidence says engineers must explain why spanning tree shows one port-channel interface instead of separate forwarding decisions for bundled members, and STP on the port-channel is the option that provides the needed behavior.
Question 19
A change request will be accepted only if it can fix a routed bundle where an IP address was placed on one member while the port-channel should own Layer 3 state. Which mechanism is the most appropriate? Choose ONE.
- matching native VLAN
- LACP active mode
- Layer 3 port-channel interface
- correct channel-group protocol pairing
Correct Answer(s)
C
Rationale
- Matching native VLAN lacks the needed control effect; it provides consistent handling of untagged frames for trunk VLAN consistency situations. Here the team must fix a routed bundle where an IP address was placed on one member while the port-channel should own Layer 3 state, which Layer 3 port-channel interface enables directly.
- LACP active mode controls active standards-based EtherChannel negotiation and is useful for LACP negotiation work. This case requires the team to fix a routed bundle where an IP address was placed on one member while the port-channel should own Layer 3 state. Because Layer 3 port-channel interface supplies that behavior, this option acts on the wrong requirement.
- Layer 3 port-channel interface matches the desired state by providing a single routed logical interface over several links. Since engineers must fix a routed bundle where an IP address was placed on one member while the port-channel should own Layer 3 state, this selection acts on the relevant Layer 3 aggregation behavior and directly satisfies the requirement. This makes Layer 3 port-channel interface the direct fit for this case.
- Correct channel-group protocol pairing targets matching aggregation protocol behavior, so it fits another protocol compatibility condition. The question requires the team to fix a routed bundle where an IP address was placed on one member while the port-channel should own Layer 3 state. Since Layer 3 port-channel interface produces the needed behavior, this choice would not fix the root requirement.
Question 20
During a maintenance window, the team must repair a single missing service VLAN without resetting the EtherChannel or changing its native VLAN. Which option is the best fit for this exact constraint? Choose ONE.
- allowed VLAN list
- restore required VLAN on the trunk
- EtherChannel load-balancing method
- LACP passive mode
Correct Answer(s)
B
Rationale
- Allowed VLAN list is plausible because it delivers forwarding of the required VLAN on the trunk for trunk VLAN filtering cases. Here the team must repair a single missing service VLAN without resetting the EtherChannel or changing its native VLAN. restore required VLAN on the trunk directly controls that state, while this option does not.
- Choose restore required VLAN on the trunk. It creates targeted restoration of the missing VLAN, while the stem requires engineers to repair a single missing service VLAN without resetting the EtherChannel or changing its native VLAN. This directly satisfies the trunk VLAN filtering condition and avoids changing a feature that is not implicated. This makes restore required VLAN on the trunk the direct fit for this case.
- EtherChannel load-balancing method has a different role: it supplies a more suitable per-flow distribution key in load balancing scenarios. The engineer must repair a single missing service VLAN without resetting the EtherChannel or changing its native VLAN here. That makes restore required VLAN on the trunk the direct answer and this option unsuitable.
- LACP passive mode does not match the evidence because it provides passive standards-based EtherChannel participation. That is a LACP negotiation function, whereas the stem requires engineers to repair a single missing service VLAN without resetting the EtherChannel or changing its native VLAN. restore required VLAN on the trunk is the option tied to that task.