You are the virtualization administrator for an organization. The organization uses all components of System
Center 2012 R2 in the production environment. A power supply in a Hyper-v host server fails. The host server
continues to run and host virtual machines in this degraded state.
You have the following requirements:
Move virtual machines from host servers that are running in a degraded state to another host server.
Prevent placement of new virtual machines on degraded host servers.
You need to configure the environment.
Which System Center feature should you implement?
A.
Dynamic Optimization
B.
Performance and Resource Optimization (PRO)
C.
Shared VHDX files
D.
Placement Rules
Why is this Answer B?
I think answer D: Placement Rule
B is correct. From technet:
” Alternatively, a customer might want to migrate virtual machines when a hardware failure is detected (for example, a fan failure). ”
http://technet.microsoft.com/en-us/library/cc917965.aspx
I think it’s A. Dynamic Optimization is new in VMM 2012 and appears more fully featured than PRO: http://blogs.technet.com/b/scvmm/archive/2013/02/11/managing-your-cluster-with-scvmm-2012-s-dynamic-optimization-do.aspx
dynamic optimization is a subset of PRO, however it is autonomous; no SCOM required.
DO cannot be trigered from a hardware failure; a SCOM management pack is needed for that, thus integration required between SCOM and VMM = PRO.
I think B is correct, too. Even though Operations Manager is not mentioned in the question.
From Pepper’s link:
“For many health monitoring requirements Operations Manager is still the right choice and custom management packs allow deep monitoring of a wide range of specific hardware or configurations. In the case of VMM’s load management however, DO is almost always the right tool for the job.”
I can’t find any information that DO monitors degraded states for power supply, for example. And the question is stressing the degraded state of the host, which is detected by PRO.
I think is A. DO is a newer and more advanced feature. Power Optimization is a part of Dynamic Optimization.
http://technet.microsoft.com/en-us/library/gg675109.aspx
Wrong. Power optimization in DO is a function to power off hosts that can be drained in offpeak hours.
PRO is the best answer.
I think the answer is A since:
In System Center 2012 – Virtual Machine Manager, Dynamic Optimization replaces the host load balancing that is performed for Performance and Resource Optimization (PRO) by the PRO CPU Utilization and PRO Memory Utilization monitors in System Center Virtual Machine Manager (VMM) 2008 R2.
In 2012 R2, DO is what PRO used to be.
i would go for PRO at the end after reading more.
Lets rule out the wrong answers:
A) WRONG. DO relies on user configured parameters for Memory and CPU resources and does not detect hardware failures. See bottom link.
C) WRONG. Shared VHDX files do not meet the requirements.
D) WRONG. Placement algorithm analyzes PERFORMANCE data for the workload of hosts, not host hardware. It does not consider the health of the host hardware when calculating host ratings to make/offer a placement decision. (http://technet.microsoft.com/en-us/library/jj860428.aspx)
Now on to why B is the correct answer. They key in this scenario is the org uses all components of SC 2012 R2 and the requirements are to prevent placement of new VMs on degraded hardware. SCOM can detect hardware failures and VMM can tie certain alerts (hardware failures) from SCOM to remediation actions (VM movement and placement) in VMM by utilizing PRO Tips.
…
http://technet.microsoft.com/en-us/library/jj126987.aspx
Lets rule out the wrong answers:
A) WRONG. DO relies on user configured parameters for Memory and CPU resources and does not detect hardware failures. See bottom link.
C) WRONG. Shared VHDX files do not meet the requirements.
D) WRONG. Placement algorithm analyzes PERFORMANCE data for the workload of hosts, not host hardware. It does not consider the health of the host hardware when calculating host ratings to make/offer a placement decision. (http://technet.microsoft.com/en-us/library/jj860428.aspx)
Now on to why B is the correct answer. They key in this scenario is the org uses all components of SC 2012 R2 and the requirements are to prevent placement of new VMs on degraded hardware. SCOM can detect hardware failures and VMM can tie certain alerts (hardware failures) from SCOM to remediation actions (VM movement and placement) in VMM by utilizing PRO Tips.
…
http://technet.microsoft.com/en-us/library/jj126987.aspx
B is the correct answer. They key in this scenario is the org uses all components of SC 2012 R2 and the requirements are to prevent placement of new VMs on degraded hardware. SCOM can detect hardware failures and VMM can tie certain alerts (hardware failures) from SCOM to remediation actions (VM movement and placement) in VMM by utilizing PRO Tips.
http://technet.microsoft.com/en-us/library/jj126987.aspx
B is the correct answer.
DO is only a subset and can only monitor memory, CPU and disk space. It doesn’t monitor Power.
PRO in SCOM monitors all aspects of likely scenarios.
Here is how to think about this:
PRO and Dynamic Optimization perform many of the same tasks. Half of a Microsoft test is marking the new features and making sure that Admins know what is contained in the new version vs. the old version.
Therefore and since Dynamic Optimization is new to 2012 the answer is probably Dynamic Optimization.
Also – as Power Optimization is a subset of Dynamic Optimization:
Power Optimization – as we dynamically optimize our VM and application placement, Power Optimization can be enabled as an added capability for Hyper-V virtualization hosts in clusters within our Private Cloud fabric. When System Center 2012 SP1 VMM finds that it can safely consolidate running VMs and applications on a smaller number of physical virtualization hosts, while still preserving enough spare capacity for high availability in the event of an unexpected host outage, Power Optimization can be leveraged to safely shutdown and power-off unneeded virtualization hosts during periods of low activity.
http://blogs.technet.com/b/keithmayer/archive/2013/04/17/guided-hands-on-lab-dynamic-optimization-and-power-optimization-for-an-elastic-private-cloud-fabric-build-your-private-cloud-in-a-month.aspx
I think PRO is a good candidate because:
“VMM only migrates highly available virtual machines that use shared storage. If a host cluster contains virtual machines that are not highly available, those virtual machines are not migrated during Dynamic Optimization.”
I think it would be Dynamic Optimization. Below would be my reference:
“In System Center 2012 – Virtual Machine Manager, Dynamic Optimization replaces the host load balancing that is performed for Performance and Resource Optimization (PRO) by the PRO CPU Utilization and PRO Memory Utilization monitors in System Center Virtual Machine Manager (VMM) 2008 R2.”
http://technet.microsoft.com/en-us/library/gg675109.aspx
Anyone who can tell us for sure if its A or B please?
The answer is A. The difference is between system 2008 and 2012, read this:
http://www.virtualizationadmin.com/blogs/lowe/news/virtual-machine-manager-2012-dynamic-optimization-an-introduction-219.html
“n Virtual Machine Manager 2008 R2, Microsoft leveraged the monitoring capabilities of Operations Manager with a feature called Performance and Resource Optimization (PRO). This feature would recommend workload migrations when resource constraint rule dictated and these migrations could be carried out with additional PRO rules with or without administrator intervention.
With VMM 2012, Microsoft has replaced the PRO feature with a new feature called Dynamic Optimization. The best part: Dynamic Optimization eliminates any reliance on Operations Manager. Although Operations Manager is a great product, as a requirement for PRO, it was just an implementation bottleneck.”
Answer B:
In this specific scenario the hardware monitoring is key.
See this blog: http://blogs.technet.com/b/scvmm/archive/2013/02/11/managing-your-cluster-with-scvmm-2012-s-dynamic-optimization-do.aspx
For many health monitoring requirements Operations Manager is still the right choice and custom management packs allow deep monitoring of a wide range of specific hardware or configurations. In the case of VMM’s load management however, DO is almost always the right tool for the job.
So use DO in most scenarios, but if hardware monitoring is coming in the picture, choose PRO.
A and C are NOT System Center features so you can rule tem out. D does not automatic move VM’s in case of a failure of one power supply because the system is still online. B is correct. SCOM (PRO) can detect hardware failures and report this to VMM which moves the VM’s