Courseiva
Switching and Network AccessmediumMultiple ChoiceObjective-mapped

CCNA Switching and Network Access Practice Question

A switch port connected to an end host should forward traffic for one VLAN only and should not negotiate trunking. Which configuration approach best fits that requirement?

⚠ Common exam trap

Avoid confusing trunking features with access port requirements. Remember, end devices typically connect via access ports.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Configure the interface with `switchport mode access`

The best approach is to configure the interface as an access port. In plain language, this tells the switch that the interface is for a normal endpoint and should belong to one VLAN rather than carry multiple VLANs like a trunk. It also avoids reliance on dynamic trunk negotiation, which is usually unnecessary and potentially confusing for a user-facing connection. This is a standard access-layer design principle. End hosts such as PCs and printers usually connect to access ports, not trunks. That is why the correct answer is the one centered on explicit access-port behavior.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Configure the interface with `switchport mode access`

    Why this is correct

    Configuring 'switchport mode access' forces the interface to operate in permanent access mode, disabling Dynamic Trunking Protocol (DTP) and ensuring the port carries untagged traffic for only one VLAN—usually VLAN 1 by default unless reassigned with 'switchport access vlan'. This deterministic, secure configuration is exactly what an end host expects, because most host NICs send untagged frames and rely on the switch to place them in the proper broadcast domain. It is the industry-standard best practice for connecting PCs, printers, and other typical end devices.

  • Configure the interface with `switchport mode trunk`

    Why it's wrong here

    A trunk port is designed to carry tagged frames for multiple VLANs simultaneously, typically between switches or to a router that supports 802.1Q tagging. An end host does not usually tag its traffic; if the switchport is set to trunk, the host's untagged frames would be placed in the native VLAN, potentially causing VLAN mismatch, broadcast isolation, and security issues. Therefore trunk mode is not appropriate for a simple end-host connection.

    When this WOULD be correct

    In a scenario where the question specifies that a switch port needs to support multiple VLANs for inter-VLAN routing or to connect to another switch that requires trunking, then `switchport mode trunk` would be the correct configuration.

  • Configure the interface with `switchport mode dynamic desirable`

    Why it's wrong here

    Dynamic desirable is a Dynamic Trunking Protocol (DTP) mode that actively tries to negotiate a trunk with the connected neighbor. Because an ordinary end host does not generate DTP frames, the port will either remain in access mode after a failed negotiation or, if the host is actually another switch, it could unexpectedly form a trunk, defeating security best practices. This non-deterministic negotiation-based behavior makes it unsuitable for a dedicated end-host port, which should be explicitly forced into access mode.

    When this WOULD be correct

    In a scenario where the question specifies that the switch port should support dynamic trunking negotiation to allow for flexibility in VLAN assignments, `switchport mode dynamic desirable` would be the correct answer. This would apply in environments where multiple VLANs are expected and trunking is acceptable.

  • Configure the interface with `no switchport`

    Why it's wrong here

    The 'no switchport' command on a multilayer switch converts the interface from a Layer 2 switching port into a routed port that operates at Layer 3, requiring an IP address to forward packets. This eliminates the ability to assign the port to a VLAN and disables normal Ethernet switching, which is not what an end host needs. The port would no longer bridge traffic as a standard access port, and the host would be unable to communicate on the VLAN unless the routed configuration is intentionally desired.

    When this WOULD be correct

    In a scenario where the question specifies that the switch port should be used for routing between different subnets without VLAN tagging, `no switchport` would be the correct configuration to enable Layer 3 routing functionality on that interface.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.

Configure the interface with `switchport mode access`Correct answer

Why this is correct

Configuring 'switchport mode access' forces the interface to operate in permanent access mode, disabling Dynamic Trunking Protocol (DTP) and ensuring the port carries untagged traffic for only one VLAN—usually VLAN 1 by default unless reassigned with 'switchport access vlan'. This deterministic, secure configuration is exactly what an end host expects, because most host NICs send untagged frames and rely on the switch to place them in the proper broadcast domain. It is the industry-standard best practice for connecting PCs, printers, and other typical end devices.

Configure the interface with `switchport mode trunk`Wrong answer — click to see why

Why this is wrong here

A trunk port is designed to carry traffic for multiple VLANs between switches, not for a single end host. Using switchport mode trunk on an access port would allow multiple VLANs and enable trunk negotiation, violating the requirement.

★ When this WOULD be the correct answer

In a scenario where the question specifies that a switch port needs to support multiple VLANs for inter-VLAN routing or to connect to another switch that requires trunking, then `switchport mode trunk` would be the correct configuration.

Why candidates choose this

Students may confuse trunking with the ability to carry VLAN traffic, but they might not realize that trunk ports are for inter-switch links, not end-host connections.

Configure the interface with `switchport mode dynamic desirable`Wrong answer — click to see why

Why this is wrong here

The dynamic desirable mode actively attempts to form a trunk with the connected device using DTP. This allows trunk negotiation, which contradicts the requirement to not negotiate trunking and to forward traffic for only one VLAN.

★ When this WOULD be the correct answer

In a scenario where the question specifies that the switch port should support dynamic trunking negotiation to allow for flexibility in VLAN assignments, `switchport mode dynamic desirable` would be the correct answer. This would apply in environments where multiple VLANs are expected and trunking is acceptable.

Why candidates choose this

Students might think 'dynamic' implies automatic configuration for a single VLAN, but dynamic desirable actually initiates trunk negotiation, making it unsuitable for an end host.

Configure the interface with `no switchport`Wrong answer — click to see why

Why this is wrong here

The no switchport command converts the Layer 2 switch port into a Layer 3 routed port, which does not operate as a switch port and cannot be assigned to a VLAN. This is used for routing between VLANs, not for connecting an end host to a single VLAN.

★ When this WOULD be the correct answer

In a scenario where the question specifies that the switch port should be used for routing between different subnets without VLAN tagging, `no switchport` would be the correct configuration to enable Layer 3 routing functionality on that interface.

Why candidates choose this

Students may think removing switchport functionality simplifies the port, but they overlook that it changes the port to a routed interface, which is not appropriate for a standard end-host connection.

Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Visual reference

Switch VLAN 10 Sales (192.168.10.0/24) PC-A PC-B VLAN 20 HR (192.168.20.0/24) PC-C PC-D Router VLANs isolate traffic — inter-VLAN routing requires a Layer 3 device

About these practice questions

This 200-301 question is part of Courseiva's 1,389-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.