Network Access

When a Cisco switch is powered on for the first time with factory default settings, all switch ports are assigned to VLAN 1 by default. This is a fundamental concept in Cisco switching.

VLAN 1 serves multiple important functions:
- It is the default VLAN for all switch ports
- It is the default native VLAN for trunk links
- It carries control plane traffic like CDP, VTP, and STP by default
- It cannot be deleted or removed from the switch

This default configuration allows the switch to be operational immediately upon power-up, with all ports able to communicate with each other within VLAN 1.

Why the other answers are incorrect:

VLAN 0 does not exist as a valid VLAN identifier in Cisco switches. VLAN IDs range from 1 to 4094, and VLAN 0 is not used for any purpose, including management or initial configuration.

VLAN 1002 is indeed a reserved VLAN, but it is used for FDDI-default compatibility in older Token Ring and FDDI networks. It is not the default VLAN for switch ports and is rarely used in modern networks.

VLAN 1005 is also a reserved VLAN for Token Ring-default (TRNET-default) compatibility. Like VLAN 1002, it exists for legacy protocol support but is not the default VLAN assignment for switch ports when the switch is first powered on.

The primary purpose of a trunk link in a multi-switch VLAN environment is to carry traffic from multiple VLANs between switches using frame tagging.

A trunk link is a special type of port configuration that allows multiple VLANs to traverse a single physical connection between switches. This is accomplished through frame tagging, where each frame is marked with a VLAN identifier (typically using IEEE 802.1Q standard). When a frame enters a trunk port, it is tagged with its VLAN ID, transmitted across the trunk, and then the receiving switch can identify which VLAN the frame belongs to and forward it appropriately.

This approach is efficient because:
- It eliminates the need for multiple physical connections between switches (one for each VLAN)
- It conserves switch ports and cabling infrastructure
- It allows scalability as new VLANs can be added without requiring new physical connections
- Frame tagging ensures that VLAN separation and security are maintained across the trunk

Why the other answers are incorrect:

The option suggesting separate physical connections for each VLAN describes an inefficient and impractical approach that defeats the purpose of trunking. This would require a dedicated cable for each VLAN, which is wasteful and doesn't scale well.

The option about providing dedicated bandwidth for a single VLAN misunderstands the fundamental concept of trunking. Trunk links are specifically designed to carry MULTIPLE VLANs, not a single VLAN. An access port, not a trunk port, would be used for single VLAN traffic.

The option mentioning port aggregation and load balancing confuses trunk links with EtherChannel/Link Aggregation. While these technologies can work together, port aggregation is about combining multiple physical links for increased bandwidth and redundancy, whereas trunking is specifically about carrying multiple VLAN traffic using frame tagging. These are distinct concepts with different purposes.

The primary security difference between SSH and Telnet is that SSH encrypts all transmitted data including authentication credentials, while Telnet transmits all data in plaintext format.

SSH (Secure Shell) was specifically designed to address the security vulnerabilities of Telnet. SSH provides end-to-end encryption for the entire communication session, which includes:
- Authentication credentials (usernames and passwords)
- All commands entered by the user
- All data responses from the server
- The entire session from start to finish

This comprehensive encryption protects against eavesdropping, man-in-the-middle attacks, and credential theft. SSH uses TCP port 22 by default.

Telnet, on the other hand, transmits everything in cleartext (plaintext), making it extremely vulnerable to packet sniffing and interception attacks. Anyone monitoring network traffic can easily capture usernames, passwords, and all session data. Telnet uses TCP port 23 by default.

Why the other answers are incorrect:

The second option reverses the port numbers - SSH uses port 22, not port 23, and Telnet uses port 23, not port 22. Additionally, Telnet does not have encryption enabled at all.

The third option incorrectly states that SSH only encrypts the initial authentication and username, while suggesting Telnet encrypts session data after login. This is completely backwards - SSH encrypts everything, while Telnet encrypts nothing.

The fourth option incorrectly suggests that Telnet encrypts authentication credentials. Telnet provides no encryption whatsoever - neither for authentication credentials nor for any other data transmitted during the session.