A vSphere 6 High Availability cluster has been configured with default settings. Four virtual machines in the cluster have been configured with these priorities:
Prod-DB. High
Prod-Email: High
Prod-VC. Medium
Dev-VDI: Low
How many VM Overrides would need to be defined at the cluster level to meet the restart priorities?
A.
1
B.
2
C.
3
D.
4
Explanation:
Explanation/Reference:
C
http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.avail.doc/GUID-FA8B166D-A5F5-47D3-840E-68996507A95B.html
VM Restart Priority
The values for this setting are Disabled, Low, Medium (the default), and High
0
0
I have to agree with Alex, even though every dump has this answer. No idea what (if any) the logic behind 2 would be.
0
0
Agree:
C – 3 changes from default of Medium
1) Prod-DB high>med
2) prod-email hi>md
3) Dev-VDI: low>md
1
0
Correct C – because we need to ensure the 2 Highs are started before the rest of the VMs. Default value is Medium.
You can set a VM’s restart priority to one of the following:
High: VMs with a high priority are restarted first.
Medium: This is the default setting.
Low: VMs with a low priority are restarted last.
Use Cluster Setting: VMs are restarted based on the setting defined at the cluster level defined in the window shown in the figure below.
Disabled: The VM does not power on.
The priority should be set based on the importance of the VMs. In other words, you might want to restart domain controllers and not restart print servers. The higher priority virtual machines are restarted first. VMs that can tolerate remaining powered off in the event of an emergency should be configured to remain powered off to conserve resources.
0
0
You could always approach this question as having a database server, email server, vcenter server, and a Dev VDI server. Perhaps the VCenter server would be the only one that might need to come up first and the answer might be one. No reason that the Dev-VDI server would need to be prioritized to come up first.
0
0
Another confusing dump answer that make no sense and no way of finding out why?
0
0
2 makes sense because we want all the Production VMs to start at the same time – so we lower 2x High to Medium and it is done.
0
0
Where does it say anything about wanting to start Production VMs at the same time? The question specifies the power on priority for all four VMs. The cluster is set at default which means all VMs are set to Medium. There are three VMs listed which are not set to Medium. I’d say that makes the answer C
0
0
The correct answer is A
We’re dealing with applications which have a dependency on a database. We can only assume that the Prod-DB presented is being used for one or all of the other applications. At least two of the remaining vm’s are prefixed with Prod-. In keeping with this line of thought, the DB has to come up first and all other application restarts become secondary. This would mean that an override would need to be set on Prod-Email specifically to ensure the DB comes up first.
Once the DB is up and running correctly any of the other vm’s could establish a connection and begin operating properly
0
0
The correct answer is B.
Since Medium is the restart priorities of default it is no necessary regard therefore are only 2 the Prod-DB/Prod-Email (High) and Dev-VDI (Low) the priorities from overrides.
Below a valid guide-:
http://geek-university.com/vmware-esxi/vm-overrides/
0
0
The reason why 2 is the correct answer is:
When you create a VM override in the Vsphere Web Client you can select multiple VMs in a single rule.
IMHO
0
0
agreed both ‘Highs’ can be in one override:
http://geek-university.com/vmware-esxi/vm-overrides/
0
0
Yes you can but when you open that configuration it shows as 2 rules (if you select 2 VM’s). So in my opinion the correct answer is 3.
0
0
I personally was not sure of the answer to this question, but after reading this article I’m inclined to agree with those who say B-2.
As always, please judge for yourselves and comment if you agree/disagree.
http://blog.ukotic.net/2013/05/26/vm-overrides-and-vcenter/
1
0
I’d go with 3. Yes you can define multiple to do high but it still counts as 2.
I think some people arguing what is more important between servers are missing the point.
Basically your baseline is medium. How many changes do you need to fit the requirements asked.
2 high and 1 low.
Maybe that’s my answer because I just used the Levenshtein Distance formula in a powershell script.
Basically it returns the “distance” between two strings. It means how many changes you need to do for one string to match another and helps determine ones that are close.
In the case of this question, we need to do 3 changes to match the given info.
https://en.wikipedia.org/wiki/Levenshtein_distance
0
0
100% agree.
It’s funny how people sometimes are willing to bend their logic to justify any known answer, which they would never come up with if they didn’t know it !
I guess if the “correct” answer was marked as 6 (six) overrides, there would be folks who for sure had an explanation for that 😉
0
0
I would go for B-2
1. add 2 x high VMs
2. add 1 x los VM
0
0
I would go with 3 overrides
Just because you can set 2 High overrides at the same time does not mean that the two overrides count as a single override.
once set the you still have 3 overrides!
1 high
2 high
3 low
0
0
The question could be understand in many way but I will agree on option B: 2.
Why? because I understand the question, how many changes I need to do (per each VM not all together) to meet the requirements.
So the answer is two. Why?
Because in HA enabled cluster, we need to change two VM Overrides settings per each VM: Automation level (from whatever is set to disabled) and VM restart priority (from whatever is set to desired one).
0
0
I am torn between 2 and 3, and let me explain why:
For answer B) 2
When you actually look at the question, it does not ask you how many rules do you need in order to satisfy the restart priority. It asks you how many VM overrides need to be defined. Technically, we can create 2 overrides for 3 VMs. 1 is for the group of two (Prod-DB and Prod-Email) set to high, that is one override for two VMs. The other override is for Dev-VDI and set to Low.
If you want to look at this question literally, 2 is the answer because we configured two overrides for 3 VMs that affects all 4 in the question.
However, for answer C) 3:
If you want to look at this question technically, yes we do need 3 overrides. Adding in both Prod machines at the same time and configuring them both still creates 2 priority rules. It does not group them together. Adding in multiple VMs to a VM Override window just lets you configure a bunch at the same time that all require the same priority and other settings. BUT, you can still go back to the rules once they are all created and individually edit the machines priority and it will not affect the ones you initially created it with. This proves my point that they are NOT grouped together.
So, in essence, I still dont know what the fuck the answer is because I cant figure out I should take this question literally, or technically.
I just hope I dont get this question come this Friday.
Good luck.
0
0