Answer: B 

Explanation: Hyper-V Network Virtrtualization runs multiple virtual networks on a physical network. And each virtual network operates as if it is running as a physical network. The The Set-NetAdaptercmdlet sets the basic properties of a network adapter such as virtual LAN (VLAN) identifier (ID) and MAC address. Thus if you add the binding parameter to the command then you will be able to install the Windows Network Virtualization Filter Driver. Step one:Enable Windows Network Virtualization (WNV). This is a binding that is applied to the NIC that you External Virtual Switch is bound to. This can be a physical NIC, it can be an LBFO NIC team. Either way, it is the network adapter that your External Virtual Switch uses to exit the server.This also means that if you have multiple virtual networks or multiple interfaces that you can pick and choose and it is not some global setting.If you have one External Virtual Switch this is fairly easy: $vSwitch = Get-VMSwitch -SwitchType External# Check if Network Virtualization is bound# This could be done by checking for the binding and seeing if it is enabledForEach-Object -InputObject $vSwitch {if ((Get-NetAdapterBinding -ComponentID "ms_netwnv" -InterfaceDescription $_.NetAdapterInterfaceDescription).Enabled -eq $false){ # Lets enable itEnable-NetAdapterBinding -InterfaceDescription $_.NetAdapterInterfaceDescription -ComponentID "ms_netwnv"}} 

Answer: D 

Explanation: 

Storage Pools use unallocated space thus you need to delete Volume E. 

References: 

http://technet.microsoft.com/en-us/library/ff399688.aspx 

Answer: A 

Explanation: 

Explanation IPAM ASM Administrators IPAM ASM Administrators is a local security group on an IPAM server that is created when you install the IPAM feature. Members of this group have all the privileges of the IPAM Users security group, and can perform IP address space tasks in addition to IPAM common management tasks. Note: When you install IPAM Server, the following local role-based IPAM security groups are created: IPAM Users IPAM MSM Administrators IPAM ASM Administrators IPAM IP Audit Administrators IPAM Administrators Incorrect: not B: Too much privileges. IPAM Administrators IPAM Administrators is a local security group on an IPAM server that is created when you install the IPAM feature. Members of this group have privileges to view all IPAM data and perform all IPAM tasks. 

Answer: J 

Explanation: 

The preferred owner in a 2 server cluster will always be the active node unless it is down. http:// www.sqlservercentral.com/Forums/Topic1174454-146-1.aspx#bm1174835 Difference between possible owners and preferred owners Possible owners are defined at the resource level and dictate which nodes in the Windows cluster are able to service this resource For instance, you have a 3 node cluster with Node A, Node B and Node C. You have a clustered disk resource "MyClusteredDisk", if you remove Node C from the possible owners of the clustered disk resource "MyClusteredDisk" then this disk will never be failed over to Node C. Preferred owners are defined at the resource group level and define the preferred node ownership within the Windows cluster For instance, you have a 3 node cluster with Node A, Node B and Node C. You have a cluster resource group "MyClusteredGroup" which contains various disk, IP, network name and service resources. Nodes A, B and C are all possible owners but Node B is set as the preferred owner and is currently the active node. The resource group fails over to Node C as Node B stops responding on the Public network due to a failed NIC. In the Resource group properties on the failback tab you have this set to immediate. You fix the NIC issue on Node B and bring it back up on the network. The resource group currently active on Node C will without warning immediately attempt to failback to Node B. Not a good idea if this is a Production SQL Server instance, so use caution when configuring preferred owners and failback http://support.microsoft.com/kb/299631/en-us Failover behavior on clusters of three or more nodes This article documents the logic by which groups fail from one node to another when there are 3 or more cluster node members. The movement of a group can be caused by an administrator who manually moves a group or by a node or resource failure. Where the group moves depends on how the move is initiated and whether the Preferred Owner list is set. 

Answer: C 

Explanation: 

http://blogs.technet.com/b/meamcs/archive/2012/05/28/hyper-v-resource-metering-in-windows-server-2012-server-8-beta.aspx Hyper-V Resource Metering in Windows Server 2012 R2 "Server 8 Beta" IT organizations need tools to charge back business units that they support while providing the business units with the right amount of resources to match their needs. For hosting providers, it is equally important to issue chargebacks based on the amount of usage by each customer. To implement advanced billing strategies that measure both the assigned capacity of a resource and its actual usage, earlier versions of Hyper-V required users to develop their own chargeback solutions that polled and aggregated performance counters. 

These solutions could be expensive to develop and sometimes led to loss of historical data. To assist with more accurate, streamlined chargebacks while protecting historical information, Hyper-V in Windows Server 2012 R2 "Server 8 Beta" introduces Resource Metering, a feature that allows customers to create cost-effective, usage-based billing solutions. With this feature, service providers can choose the best billing strategy for their business model, and independent software vendors can develop more reliable, end-to-end chargeback solutions on top of Hyper-V. Metrics collected for each virtual machine § Average CPU usage, measured in megahertz over a period of time. § Average physical memory usage, measured in megabytes. § Minimum memory usage (lowest amount of physical memory). § Maximum memory usage (highest amount of physical memory). § Maximum amount of disk space allocated to a virtual machine. § Total incoming network traffic, measured in megabytes, for a virtual network adapter. § Total outgoing network traffic, measured in megabytes, for a virtual network adapter To enable Hyper-V resource metering on hyper-v host HV01 run the following PowerShell commands: Get-VM -ComputerName HV01 | Enable-VMResourceMetering By default the collection interval for Hyper-v metering data is one hour to change this interval the following PowerShell command can be used "value used in the command below is one minute": Set-vmhost computername HV01 ResourceMeteringSaveInterval 00:01:00 To get all VMs metering data run the following PowerShell command: Get-VM -ComputerName HV01 | Measure-VM To get a particular VM "test01" metering data run the following PowerShell command: Get-VM -ComputerName HV01 -Name "test01" | Measure-VM 

Answer:  

Answer: H 

Explanation: 

http://technet.microsoft.com/en-us/library/ee461032.aspx 

Answer:  

Answer: C,D 

159. Your network contains a single Active Directory domain named contoso.com. All domain controllers run Windows Server 2012 R2. 

The domain contains 400 desktop computers that run Windows 8 and 200 desktop computers that run Windows XP Service Pack 3 (SP3). 

All new desktop computers that are added to the domain run Windows 8. All of the desktop computers are located in an organizational unit (OU) named OU1. 

You create a Group Policy object (GPO) named GPO1. GPO1 contains startup script settings. You link GPO1to OU1. You need to ensure that GPO1 is Applied only to computers that run Windows XP SP3. 

What should you do? 

A. Modify the Security settings of OU1. 

B. Run the Set-GPInheritancecmdlet and specify the -target parameter. 

C. Create and link a WMI filter to GPO1. 

D. Run the Set-GPLinkcmdlet and specify the -target parameter. 

Answer: C 

Explanation: 

Windows Remote Management allows you to manage and execute programs remotely References: Exam Ref 70-410: Installing and Configuring Windows Server 2012: Objective 4.3: Deploy and Configure the DNS service, Chapter 4 Deploying and Configuring core network services, p. 246 http://technet.microsoft.com/en-us/library/dd349801(v=ws.10).aspx