VTP modes and where VLAN changes are permitted In Cisco's VLAN Trunking Protocol (VTP), which switch mode specifically allows you to create, modify, and delete VLAN definitions that are then advertised to other switches in the same VTP domain?

Introduction / Context:
VTP is a Cisco protocol that distributes VLAN configuration information across switches in the same VTP domain, reducing administrative overhead. Understanding what you can and cannot do in each mode (server, client, transparent) is essential for proper VLAN management and change control within a campus network.

Given Data / Assumptions:

• VTP is enabled and switches share the same domain name.
• We need to know which mode permits making VLAN changes that will be propagated.
• Modes considered: server, client, transparent (STP is unrelated).

Concept / Approach:

In VTP server mode, you can add, delete, and rename VLANs; changes are advertised to other switches in the domain. In VTP client mode, the switch cannot create or delete VLANs; it only receives updates. In VTP transparent mode, the switch does not apply received updates to its VLAN database (it forwards them) but can manage VLANs locally (not distributed). Therefore, the mode that both allows changes and distributes them is server.

Step-by-Step Solution:

Verification / Alternative check:

Check the VTP status with show vtp status to confirm the mode and revision number. Only servers increment and propagate configuration revision numbers upon changes.

Why Other Options Are Wrong:

• Client: Cannot create or delete VLANs.
• Transparent: Local changes only; no propagation to the domain database.
• STP: Not a VTP mode; it is a separate protocol (Spanning Tree).
• Off: Not relevant to VTP operations in this context.

Common Pitfalls:

• Making changes in transparent mode expecting domain-wide propagation.
• Ignoring VTP revision numbers, which can overwrite domain VLANs if not managed carefully.

Final Answer:

Server