Matt, the IT Manager, wants to create a new network available to virtual servers on the same hypervisor, and does not want this network to be routable to the firewall. How could this BEST be accomplished?
A.
Create a VLAN without a default gateway.
B.
Remove the network from the routing table.
C.
Create a virtual switch.
D.
Commission a stand-alone switch.
A really seems correct here but the answer is C because ‘a virtual switch is a software program that allows one virtual machine (VM) to communicate with another.’
0
0
This is another example of very vague and confusing questions in this exam. We have a ridiculous situation asking for an absurd requirement achieved through bizarre solutions.
• I need to create a NEW network (subnet?)
• For ALREADY EXISTENT virtual servers (in different subnets in the same network?)
• On the same hypervisor.
• I do not want this network to be routable to the firewall. (I.e. I do not want it to leave the LAN and access the WAN.
• So it is assumed by inference that the “new network” is for LAN related routing only.
• The main thing to remember is that we are talking about Hyper-V VIRTUALIZATION. (Not VMware)
SCENARIO:
Let me first create a scenario that fits the above criteria:
(1) I want to spin up a VM, and have 2 (virtual) network adapters on it.
(2) For one of those network adapters, I want connection to the standard network, routable to the firewall, thus with access to the WAN\
(3) However, for the 2nd network adapter, I want it to be connected to a different switch that a SAN is connected to. This is not to be connected to the WAN, but just to the LAN the SAN is connected to.
That to my mind provides some clarification as to what is to be achieved in here.
We want the existent servers to be connected to two networks. One pointing to the WAN and the other to the LAN.
(1) Before we proceed, let’s remove the blatantly daft answer out of the way, namely: “D. Commission a stand-alone switch.” I do not need an expensive physical device in order to achieve virtualization when a virtual device will do at absolutely no cost
(2) Secondly, let’s remove a ridiculous answer namely “B. Remove the network from the routing table.” A routing table contains information about the topology of the network immediately around it. Removing the network from it would prevent the virtual servers from connecting to the network, and would prevent the network from “routing”. Might as well not have created the new a network at all.
So it is a tossup between A & C.
Typically; in a “real” network, “A. Create a VLAN without a default gateway” would achieve what is required. Yet, for all the existent server to talk to each other using a VLAN without a gateway, they must by necessity be all found inside the same VLAN. So this also eliminates A.
So all we are left with is “C: Create a virtual switch”
We can configure Hyper-V for multiple subnets with only one NIC for example. This is achieved by:
1) Open the Hyper-V Manager
2) Click on the “Virtual Switch Manager” on the actions pane
3) Creating a New Virtual Switch with no Default Gateway configured.
• A Hyper-V Virtual Switch implements policy enforcement for security, isolation, and service levels.
• I can have the Servers connected to an existent Hyper-V Virtual Switch connected to the WAN
• I can also have the servers connected to the newly created Hyper-V Virtual Switch connected to the LAN
1
0