File Info
| Exam | Installing and Configuring Windows Server 2012 |
| Number | 70-410 |
| File Name | Microsoft.70-410.Pass4Sure.2019-04-22.319q.tqb |
| Size | 11 MB |
| Posted | Apr 22, 2019 |
| Download | Microsoft.70-410.Pass4Sure.2019-04-22.319q.tqb |
How to open VCEX & EXAM Files?
Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.
Coupon: MASTEREXAM
With discount: 20%
Demo Questions
Question 1
You have a server named Server1 that runs Windows Server 2012 R2. Server1 has the Hyper-V server role installed.
An iSCSI SAN is available on the network.
Server1 hosts four virtual machines named VM1, VM2, VM3, and VM4.
You create a LUN on the SAN to host the virtual hard drive files for the virtual machines.
You need to create a 3-TB virtual hard disk for VM1 on the LUN. The solution must prevent VM1 from being paused if the LUN runs out of disk space.
Which type of virtual hard disk should you create on the LUN?
- Dynamically expanding VHDX
- Fixed-size VHDX
- Fixed-size VHD
- Dynamically expanding VHD
Correct answer: B
Explanation:
The virtual disk needs to be a VHDX file since it is going to be over 2TB in size and it must be fixed-size so that the space is already taken on the server (that way the server does not run out of space as the volume grows) even if the actual virtual disk does not yet hold that amount of data. The virtual disk needs to be a VHDX file since it is going to be over 2TB in size and it must be fixed-size so that the space is already taken on the server (that way the server does not run out of space as the volume grows) even if the actual virtual disk does not yet hold that amount of data.
Question 2
You have a Hyper-V host named Server1 that runs Windows Server 2012 R2. Server1 has the virtual switches listed in the following table.
You create a virtual machine named VM1. VM1 has two network adapters. One network adapter connects to vSwitch1. The other network adapter connects to vSwitch2.You configure NIC teaming on VM1.
You need to ensure that if a physical NIC fails on Server1, VM1 remains connected to the network.
What should you do on Server1?
- Run the Set-VmNetworkAdapter cmdlet.
- Add a new network adapter to VM1.
- Create a new virtual switch on Server 1.
- Modify the properties of vSwitch1 and vSwitch2.
Correct answer: A
Explanation:
The Set-VmNetworkAdapter cmdlet configures features of the virtual network adapter in a virtual machine or the management operating system. References: https://docs.microsoft.com/en-us/powershell/module/hyper-v/set-vmnetworkadapter?view=win10-ps The Set-VmNetworkAdapter cmdlet configures features of the virtual network adapter in a virtual machine or the management operating system.
References: https://docs.microsoft.com/en-us/powershell/module/hyper-v/set-vmnetworkadapter?view=win10-ps
Question 3
You have a server named Server1 that runs Windows Server 2012 R2. Server1 has the Hyper-V server role installed. Server1 is connected to two Fibre Channel SANs and is configured as shown in the following table.
You have a virtual machine named VM1.
You need to configure VM1 to connect to SAN1.
What should you do first?
- Add one HBA
- Create a Virtual Fibre Channel SAN.
- Create a Hyper-V virtual switch.
- Configure network adapter teaming.
Correct answer: B
Explanation:
You need your virtualized workloads to connect easily and reliably to your existing storage arrays. Windows Server 2012 provides Fibre Channel ports within the guest operating system, which allows you to connect to Fibre Channel directly from within virtual machines. This feature protects your investments in Fibre Channel, enables you to virtualize workloads that use direct access to Fibre Channel storage, allows you to cluster guest operating systems over Fibre Channel, and provides an important new storage option for servers hosted in your virtualization infrastructure. With this Hyper-V virtual Fibre Channel feature, you can connect to Fibre Channel storage from within a virtual machine. This allows you to use your existing Fibre Channel investments to support virtualized workloads. Support for Fibre Channel in Hyper-V guests also includes support for many related features, such as virtual SANs, live migration, and MPIO. You need your virtualized workloads to connect easily and reliably to your existing storage arrays.
Windows Server 2012 provides Fibre Channel ports within the guest operating system, which allows you to connect to Fibre Channel directly from within virtual machines. This feature protects your investments in Fibre Channel, enables you to virtualize workloads that use direct access to Fibre Channel storage, allows you to cluster guest operating systems over Fibre Channel, and provides an important new storage option for servers hosted in your virtualization infrastructure.
With this Hyper-V virtual Fibre Channel feature, you can connect to Fibre Channel storage from within a virtual machine. This allows you to use your existing Fibre Channel investments to support virtualized workloads.
Support for Fibre Channel in Hyper-V guests also includes support for many related features, such as virtual SANs, live migration, and MPIO.
