Controlled Layer 2 Network Connectivity Between Virtual Machines on the Same Hypervisor

Implementing Controlled Layer 2 Network Connectivity

Question

Which two actions provide controlled Layer 2 network connectivity between virtual machines running on the same hypervisor? (Choose two.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

AD.

The correct answers are A and B.

A hypervisor is a software layer that allows multiple virtual machines (VMs) to run on the same physical server. In this scenario, the virtual machines are hosted on the same hypervisor, and we want to provide controlled Layer 2 network connectivity between them.

To achieve this, we can use a virtual switch provided by the hypervisor, which operates at Layer 2 of the OSI model and allows virtual machines to communicate with each other. The virtual switch is similar to a physical switch and provides features such as VLAN support, traffic shaping, and quality of service.

Using a virtual switch running as a separate virtual machine is also a viable option. In this case, the virtual switch is a dedicated VM that operates as a Layer 2 switch, providing connectivity between the other VMs hosted on the same hypervisor. This approach can provide additional features, such as the ability to run Layer 3 protocols, and can offer more control and flexibility over the network topology.

Option C, using a VXLAN fabric, is not necessary in this scenario. VXLAN is a network virtualization technology that encapsulates Layer 2 traffic in Layer 3 packets, allowing it to be transported over an IP network. While VXLAN can provide Layer 2 connectivity between virtual machines, it is typically used in larger-scale virtualized environments that span multiple physical hosts.

Option D, using a single routed link to an external router on a stick, would provide Layer 3 connectivity between the virtual machines, not Layer 2. This approach involves configuring a router interface with multiple subinterfaces, each corresponding to a different VLAN. While it can provide connectivity, it is not the best approach for a small-scale environment with a limited number of virtual machines.

Option E, using a single trunk link to an external Layer 2 switch, is also not necessary in this scenario. While it can provide connectivity between the virtual machines, it introduces additional complexity and requires an external Layer 2 switch. In a small-scale environment with a limited number of virtual machines, using a virtual switch provided by the hypervisor or a virtual switch running as a separate virtual machine is a simpler and more efficient approach.