mediummultiple choiceObjective-mapped

Which command places a switch interface into trunking mode directly instead of relying on negotiation?

Question 1mediummultiple choice
Full question →

Which command places a switch interface into trunking mode directly instead of relying on negotiation?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

switchport mode trunk

This is correct because it directly forces the interface into trunk mode.

B

Distractor review

switchport access vlan 10

This is wrong because it assigns an access VLAN and does not place the interface into trunking mode.

C

Distractor review

switchport mode dynamic auto

This is wrong because dynamic auto relies on negotiation and does not directly force trunking.

D

Distractor review

spanning-tree portfast

This is wrong because PortFast is an STP feature for edge ports, not a trunk-mode command.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A frequent exam trap is selecting the dynamic trunking commands like `switchport mode dynamic auto` as the correct way to enable trunking. These modes depend on Dynamic Trunking Protocol negotiation and do not guarantee the interface will become a trunk port. If the neighboring device does not actively negotiate trunking, the port may remain in access mode, causing VLAN traffic to be dropped or misrouted. This subtlety often confuses candidates who overlook the difference between forced trunk mode and negotiation-based trunking.

Technical deep dive

How to think about this question

In Cisco switching, trunk ports carry traffic for multiple VLANs between switches or other network devices. The command `switchport mode trunk` explicitly configures an interface to operate as a trunk port, bypassing any negotiation protocols like Dynamic Trunking Protocol (DTP). This direct configuration ensures the interface immediately tags frames with VLAN identifiers and forwards traffic for all allowed VLANs, which is essential for VLAN segmentation and inter-switch communication. Cisco switches support several trunking modes, including dynamic auto, dynamic desirable, trunk, and access. The `switchport mode trunk` command forces the interface into trunk mode without waiting for negotiation, making the administrative intent explicit and preventing ambiguity. In contrast, dynamic auto mode places the port in a passive state, waiting for the other side to initiate trunking, which can lead to inconsistent or unexpected trunk formation. A common exam trap is confusing dynamic trunking modes with forced trunk mode. Candidates often mistake `switchport mode dynamic auto` as enabling trunking directly, but it actually relies on negotiation and may result in an access port if the other side does not initiate trunking. Understanding this distinction is critical for both exam success and real-world network stability, as forced trunking avoids negotiation failures and ensures consistent VLAN tagging across links.

KKey Concepts to Remember

  • The `switchport mode trunk` command directly forces a switch interface to operate as a trunk port, carrying multiple VLANs without negotiation.
  • Dynamic trunking modes like `dynamic auto` rely on DTP negotiation and may not activate trunking if the neighbor does not initiate it.
  • Trunk ports tag Ethernet frames with VLAN identifiers to segregate traffic across a shared physical link between switches.
  • Access ports carry traffic for a single VLAN and do not tag frames, making `switchport access vlan` incompatible with trunking.
  • Spanning Tree Protocol features like PortFast do not influence trunking behavior and serve different purposes related to loop prevention.
  • Explicitly configuring trunk mode avoids negotiation failures and ensures consistent VLAN traffic forwarding in Cisco networks.
  • Dynamic Trunking Protocol (DTP) automates trunk negotiation but can introduce ambiguity and is often disabled in secure environments.
  • Understanding the difference between forced trunk mode and negotiation-based trunking is critical for CCNA exam success and network reliability.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related 200-301 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this 200-301 question test?

The `switchport mode trunk` command directly forces a switch interface to operate as a trunk port, carrying multiple VLANs without negotiation.

What is the correct answer to this question?

The correct answer is: switchport mode trunk — The direct command is `switchport mode trunk`. In plain language, this tells the switch to behave as a trunk port rather than waiting to negotiate that role through DTP. That makes the administrative intent clear and avoids ambiguity. In many production environments, explicit configuration is preferred because it is easier to understand and troubleshoot than relying on negotiation behavior. This is a core CCNA switching idea because trunks and access ports serve very different purposes. The wrong answers either describe negotiation states or commands that relate to other aspects of VLAN behavior. The best answer is the one that directly forces the interface into trunk mode instead of merely suggesting or passively waiting for trunking.

What should I do if I get this 200-301 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.