You manage a Hyper-V 2012 cluster by using System Center Virtual Machine Manager 2012 SP1.
You need to ensure high availability for business-critical virtual machines (VMs) that host business-critical SQL server databases.
Solution: You create a custom placement rule and apply it to all business-critical VMs.
Does this meet the goal?
A.
Yes
B.
No
Explanation:
Need to Check
ATT: This question is one of a series of similar questions where only the “Solution” changes. the answer to this one appears to always be “No” unless the
Solution involves the following:
Adding the VMs to an “Availability Set.
Modifying the Preferred and Possible Owners.
Configuring Custom Placement Rules.”
The Following Settings all enable an aspect of Failover for Virtual Machines Running in a Cluster in VMM:
Availability Sets will make them highly avialable because VMM will keep each VM that is in the availability set on its own SEPERATE physical Host machine. This
is highly available because if one Host machine crashes, you will only lose one of the SQL servers at most.
Preferred and Possible Owner nodes set preferences for which cluster nodes each VM is allowed on (Possible Owners), and which nodes you would prefer each
VM to be on (Preferred Owners). During Dynamic Optimization, patching or cluster failover, your preferences will be taken into account and your specified target
nodes will be preferred. (This can be used in the same way as an Availability Set to keep the SQL servers off the same physical Host.Custom Placement Rules allow use to set which machine a VM must failover to, among other things. You can also adjust cost settings etc.
This series should always be NO, unless “you create an availability set and add each VM to the set”
I agree with this.
You manage a Hyper-V 2012 cluster by using System Center Virtual Machine Manager 2012 SP1. You need to ensure high availability for business-critical virtual machines (VMs) that host business-critical SQL Server databases.
Solution:
A: You configure preferred and possible owners for each business-critical VM
B: You set the memory-weight threshold value to High for each business-critical VM
C: You create an availability set and place each business-critical VM in the set
D: You create a custom placement rule and apply it to all business-critical VMs
Availability set can help with HA (like VMware DRS separation rules)
C: You create an availability set and place each business-critical VM in the set