We thoroughly check each answer to a question to provide you with the most correct answers. Found a mistake? Let us know about it through the REPORT button at the bottom of the page.
All Physical OS’s
Currently, all of your testing virtual machines are connected to the production network through the hypervisor’s network interface.
However, you are concerned that the latest application you are working on could adversely impact other network hosts if errors exist in the code.
To prevent this, you decide to isolate the virtual machines from the production network. However, they still need to be able to communicate directly with each other. What should you do?
Create a new virtual switch configured for host-only (internal) networking.
Connect the virtual network interfaces in the virtual machines to the virtual switch.
Flexability – Moving virtual machines between hypervisor hosts.
Testing – Verifying that security controls are working as designed.
Server consolidation – Performing a physical-to-virtual migration (P2V)
Sandboxing – Isolating a virtual machine from the physical network.
To keep this from happening again, you decide to test all updates on a virtual machine before allowing them to be installed on production workstations.
Currently, none of your testing virtual machines have a network connection. However, they need to be able to connect to the update servers at Microsoft to download and install updates.What should you do?
-Create a new virtual switch configured for bridged (external) networking
-Connect the virtual network interfaces in the virtual machines to the virtual switch
What should you do?
Multiple virtual nics can be added to a virtual machine
virtual nics need the appropriate driver installed to function.