Written Questions with Verified Answers (Correct Update)
Question 1: Network+ Guide to Networks (8th Ed.) - Chapter 8
Answer:
Question 2: What are some of the different reasons to use VLANs?
Answer: Reasons for using VLANs include: - You wish to isolate connections with heavy or
unpredictable traffic patterns, such as when separating heavy VoIP traffic from other network
activities. - You want to identify groups of devices whose data should be given priority handling, such
as executive client devices or an ICS (industrial control system) that manages a refrigeration system or
a gas pipeline. - You want to contain groups of devices that rely on legacy protocols incompatible
with the majority of the network's traffic, such as a legacy SCADA (supervisory control and data
acquisition) system monitoring an oil refinery. - You wish to separate groups of users who need
special or limited security or network functions, such as when setting up a guest network.
- You are configuring temporary networks, such as when making specific network resources available
to a short-term project team. - You intend to reduce the cost of networking equipment, such as when
upgrading a network design to include additional departments or new types of network traffic.
Question 3: What is the difference between a default VLAN and a native VLAN?
Answer: A default VLAN is typically preconfigured on a switch and initially includes all the switch's
ports. Other VLANs might be preconfigured as well, depending on the device and manufacturer. The
default VLAN cannot be renamed or deleted; however, ports in the default VLAN can be reassigned
to other VLANs. A native VLAN receives all untagged frames from untagged ports. By default, this is
the same as the default VLAN. However, this configuration poses a security risk when untagged
traffic is allowed to travel in a VLAN-managed network. To protect the network from unauthorized
traffic, the native VLAN should be changed to an unused VLAN so that untagged traffic essentially
runs into a dead-end. Each switch port can be configured for a different native VLAN. However,
switch ports on each end of a trunk should agree on the native VLAN assignment.
If the ports don't agree, this is called a native VLAN mismatch, or just VLAN mismatch, and will
result in a configuration error.
Question 4: How do unmanaged switches and managed switches differ from each other?
Answer: An unmanaged switch provides plug-and-play simplicity with minimal configuration options
and has no IP address assigned to it. Unmanaged switches are not very expensive, but their
capabilities are limited and they cannot support VLANs. Managed switches, on the other hand, can be
configured via a command-line interface or a web-based management GUI, and sometimes can be
configured in groups. Usually, they are also assigned IP addresses for the purpose of continued
management. VLANs can only be implemented through managed switches, whose ports can be
partitioned into groups.
Page 1
Question 1: Network+ Guide to Networks (8th Ed.) - Chapter 8
Answer:
Question 2: What are some of the different reasons to use VLANs?
Answer: Reasons for using VLANs include: - You wish to isolate connections with heavy or
unpredictable traffic patterns, such as when separating heavy VoIP traffic from other network
activities. - You want to identify groups of devices whose data should be given priority handling, such
as executive client devices or an ICS (industrial control system) that manages a refrigeration system or
a gas pipeline. - You want to contain groups of devices that rely on legacy protocols incompatible
with the majority of the network's traffic, such as a legacy SCADA (supervisory control and data
acquisition) system monitoring an oil refinery. - You wish to separate groups of users who need
special or limited security or network functions, such as when setting up a guest network.
- You are configuring temporary networks, such as when making specific network resources available
to a short-term project team. - You intend to reduce the cost of networking equipment, such as when
upgrading a network design to include additional departments or new types of network traffic.
Question 3: What is the difference between a default VLAN and a native VLAN?
Answer: A default VLAN is typically preconfigured on a switch and initially includes all the switch's
ports. Other VLANs might be preconfigured as well, depending on the device and manufacturer. The
default VLAN cannot be renamed or deleted; however, ports in the default VLAN can be reassigned
to other VLANs. A native VLAN receives all untagged frames from untagged ports. By default, this is
the same as the default VLAN. However, this configuration poses a security risk when untagged
traffic is allowed to travel in a VLAN-managed network. To protect the network from unauthorized
traffic, the native VLAN should be changed to an unused VLAN so that untagged traffic essentially
runs into a dead-end. Each switch port can be configured for a different native VLAN. However,
switch ports on each end of a trunk should agree on the native VLAN assignment.
If the ports don't agree, this is called a native VLAN mismatch, or just VLAN mismatch, and will
result in a configuration error.
Question 4: How do unmanaged switches and managed switches differ from each other?
Answer: An unmanaged switch provides plug-and-play simplicity with minimal configuration options
and has no IP address assigned to it. Unmanaged switches are not very expensive, but their
capabilities are limited and they cannot support VLANs. Managed switches, on the other hand, can be
configured via a command-line interface or a web-based management GUI, and sometimes can be
configured in groups. Usually, they are also assigned IP addresses for the purpose of continued
management. VLANs can only be implemented through managed switches, whose ports can be
partitioned into groups.
Page 1
