Sure, E can work, but what does it do that a virtual switch cant? VMs can talk with no external switch involved.
with B, its possible with Nexus1000v, or CSR1000v
A.B for me.
But B is saying that the VM is acting as the virtual switch. The virtual switch is used to allow VMs to communicate with each other. It does not make sense to have a VM as a virtual switch. The question does not designate that traffic needs to stay within the hypervisor. It just states that the VMs happen to be in the same hypervisor. B is ruled out for me based on the VM acting as a virtual switch. VMs typically act as routers or provide other network services (i.e. firewall, IPS, DNS server, etc.), not switches.
A. Use a virtual switch provided by the hypervisor:
Hypervisors (like VMware ESXi, Hyper-V, etc.) include built-in virtual switches (vSwitches).
These vSwitches operate at Layer 2 and allow VMs on the same hypervisor to communicate with each other using MAC addresses, just like physical switches.
This is the most common and efficient way to provide Layer 2 connectivity between VMs on the same host.
E. Use a single trunk link to an external Layer 2 switch:
You can connect a vSwitch to a physical Layer 2 switch using a trunk link.
This allows VMs on the hypervisor to communicate with devices (physical or virtual) connected to the external switch, while still maintaining Layer 2 separation through VLANs.
The trunk link carries traffic for multiple VLANs, enabling controlled Layer 2 communication
page 12 from OCG:
"Thanks to the introduction of virtualization, some servers run a hypervisor for the operating system and contain a virtualized switch with different VLANs. These servers also provide connectivity via a trunk port".
A and B don't need additional hardware and cabling, the hypervisor can take care of both scenarios.
In a question related to virtualization *within the same hypervisor* why in the world would you go with E?
The two actions that provide controlled Layer 2 network connectivity between virtual machines running on the same hypervisor are:
A. Use a virtual switch provided by the hypervisor.
B. Use a virtual switch running as a separate virtual machine.
A and B are the correct answers.
VXLAN fabric, a single routed link to an external router on stick, and a single trunk link to an external Layer 2 switch are all network connectivity solutions, BUT THEY ARE NOT specifically designed for providing controlled Layer 2 network connectivity between virtual machines running on the same hypervisor.
This Question asks about the L2 connectivity.
If it's running on the same host( Not required for any L2 Interconnection between two Hypervisor)
Even if you are running Two Virtual machines with two Hypervisor, Still you required the L2 connection/trunk link to interconnect the two VirtualSwitch which are running on both hypervisor .
So I'm Going with A,E.
This section is not available anymore. Please use the main Exam Page.350-401 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Pb1805
Highly Voted 4 years, 2 months agodanny_f
2 years, 12 months agociscogear
3 years, 3 months agoBeehurls
1 year, 3 months agoxziomal9
Highly Voted 3 years, 7 months agoDoopfenel
Most Recent 1 month, 2 weeks agorocketplus
9 months ago[Removed]
11 months, 1 week agoKZM
1 year, 6 months agoKZM
1 year agoanaz691011
1 year, 8 months agoMaxwellJK
1 year, 9 months agoeww_cybr
1 year, 9 months ago[Removed]
1 year, 9 months agoBurik
1 year, 10 months agonet_eng10021
1 year, 11 months agoJackyChon
1 year, 11 months agoHarwinderSekhon
1 year, 12 months agoChiaretta
2 years agoNickplayany
2 years, 1 month agoalbertie
2 years, 1 month ago