1V0-604 · Question #41
Which two statements accurately describe a virtual distributed switch? (Choose two.)
The correct answer is C. Virtual distributed switch can be configured with network configurations that span across all D. Virtual distributed switch functions as a single network switch across all associated hosts. 51/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc%2Fcli_manage_networks.11.2.html
Question
Which two statements accurately describe a virtual distributed switch? (Choose two.)
Options
- AVirtual distributed switch manages virtual machine traffic, while a virtual standard switch is
- BVirtual distributed switch only forwards traffic between virtual machines and external networks.
- CVirtual distributed switch can be configured with network configurations that span across all
- DVirtual distributed switch functions as a single network switch across all associated hosts.
How the community answered
(27 responses)- A7% (2)
- B19% (5)
- C74% (20)
Explanation
51/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc%2Fcli_manage_networks.11.2.html
Topics
Community Discussion
4C and D are your correct picks here. A distributed switch presents itself as one logical switch spanning every host attached to it, and that single logical fabric is exactly what lets you push consistent port group configs, policies, and uplink settings across all those hosts from one place in vCenter, no per-host babysitting required.
Nailed it, and the sticky hook I paste in my notes is ONE UMBRELLA over all your hosts, because the vDS canopy gives you that single-pane control, but do not forget the umbrella only opens when vCenter is available, so flag that dependency before exam day or it will bite you on a scenario question.
Think of the vDS like one giant invisible umbrella stretched over your entire datacenter, every host standing under it sharing the same rain, while a standard switch is more like each host carrying its own little pocket umbrella. That single-umbrella image is exactly why D lands, the vDS acts as one logical switch across all associated hosts instead of making you configure each host separately. C follows naturally from that because when your config lives at the datacenter level, it spans all the hosts automatically, so you set a VLAN or a traffic shaping policy once and it just flows everywhere. My hook is SPAN and ONE: the vDS SPANs the datacenter and acts as ONE switch, C and D. Here is my genuine question for you though: when you picture the vDS managing port groups centrally, do you feel clear on where the actual packet forwarding still happens physically, meaning does the vDS do the switching work itself on some central box, or does each host's kernel still do the local forwarding? That distinction might trip you up on a trickier version of this question.
Our group landed on C and D pretty quickly once someone pointed out that the whole point of a vDS is centralized management, so the configuration spans hosts and the switch itself looks like one logical switch to all the associated hosts rather than separate per-host switches like a vSS. Does anyone have a clear way to explain why B trips people up, since a vDS does handle external traffic too, or is it just the word "only" that makes it wrong?