You need to ensure that all of the virtual machinesthat connect to Switch1 are isolated from the external network and can connect to each other only

Your network contains an Active Directory domain named contoso.com. The domain contains a member server
named Server1. Server1 runs Windows Server 2012 andhas the Hyper-V server role installed.
You create an external virtual switch named Switch1. Switch1 has the following configurations:
Connection type: External network
Single-root I/O visualization (SR-IOV): Enabled
Ten virtual machines connect to Switch1.
You need to ensure that all of the virtual machinesthat connect to Switch1 are isolated from the external
network and can connect to each other only. The solution must minimize network downtime for the virtual
machines.
What should you do?

Your network contains an Active Directory domain named contoso.com. The domain contains a member server
named Server1. Server1 runs Windows Server 2012 andhas the Hyper-V server role installed.
You create an external virtual switch named Switch1. Switch1 has the following configurations:
Connection type: External network
Single-root I/O visualization (SR-IOV): Enabled
Ten virtual machines connect to Switch1.
You need to ensure that all of the virtual machinesthat connect to Switch1 are isolated from the external
network and can connect to each other only. The solution must minimize network downtime for the virtual
machines.
What should you do?

A.
Change the Connection type of Switch1 to Internalnetwork.

B.
Change the Connection type of Switch1 to Private network.

C.
Remove Switch1 and recreate Switch1 as an internal network.

D.
Remove Switch1 and recreate Switch1 as a private network.



Leave a Reply 11

Your email address will not be published. Required fields are marked *


Green Hosting

Green Hosting

One of the possible answer is A

Found an explanation shows:
“You can change the connection type of a virtual switch from the virtual switch manager without having to remove it:”

Imi

Imi

The correct answer is D.

You cannot change the type of vswitch from external to private when SR-IOV is enabled at vswitch creation –> you need to recreate the vswitch

semevalavida

semevalavida

Correct Imi

Navin

Navin

Simplest way to understand it:

Private: VM to VM only
Internal: Host and VM
External: Host, VM and Internet.

polinoma

polinoma

Imi is right, I recreate the situation and you can’t change the connection type when the SR-IOV is enabled. You should recreate the virtual switch.

Correct answer D

Thank you

Baltej Gandhi

Baltej Gandhi

Did you try to disable the Single-root I/O visualization (SR-IOV) and then change the switch type.

TOn

TOn

Thanks guys
Many vce had anwer B, but D is right.

Jack

Jack

Answer is B.

You can change the connection type of a virtual switch from the virtual switch manager without having to remove it. A private virtual network is isolated from all external network traffic on the virtualization server, as well any network traffic between the management operating system and the external network. This type of network is useful when you need to create an isolated networking environment, such as an isolated test domain.

http://www.techrepublic.com/blog/windows-and-office/create-a-virtual-switch-in-windows-8-client-hyper-v/

http://www.eightforums.com/tutorials/19359-hyper-v-virtual-switch-manager.html

Mel

Mel

The Virtual Switch Manager console displays the following warning: “SR-IOV can only be configured when the virtual switch is created. An external virtual switch with SR-IOV enabled cannot be converted to an internal or private switch.”
The question states “You create an external virtual switch named Switch1. Switch1 has the following configurations: Connection type: External network, Single-root I/O visualization (SR-IOV): Enabled.
“You need to ensure that all of the virtual machines that connect to Switch1 are isolated from the external network and can connect to each other only.”
But the switch was created as “External network.” So it has to be re-created. Answer D.