5V0-35.21 · Question #85
A system administrator has been assigned a task to create a capacity policy with the following requirements: - ESXi clusters under custom group "Database Servers" requires a CPU allocation model…
The correct answer is B. Create a new policy "Database Servers", and then inherit it from Base Settings. C. Edit the new policy under section Groups and Objects, and then select Custom Group "Database F. Edit the new policy under section Capacity, filter object type by Cluster Compute Resource, and. Creating a new policy that inherits from Base Settings (B) is correct because the existing default policy already has a 4:1 overcommit ratio - inheriting from it would carry that setting over, requiring extra steps to undo. Starting from Base Settings gives a clean foundation…
Question
A system administrator has been assigned a task to create a capacity policy with the following requirements:
- ESXi clusters under custom group "Database Servers" requires a CPU
allocation model with overcommit ratio of 2:1 All ESXi clusters in the environment at the moment has been assigned with capacity policy for CPU allocation model with overcommit ratio of 4:1. Which three actions should be performed to ensure that the above capacity policy is correctly applied? (Choose three.)
Options
- AEdit the new policy under section Capacity, filter object type by custom group "Database Servers",
- BCreate a new policy "Database Servers", and then inherit it from Base Settings.
- CEdit the new policy under section Groups and Objects, and then select Custom Group "Database
- DCreate a new policy "Database Servers", and then inherit it from the current default policy.
- EEdit the new policy under section Groups and Objects, and then select object type "Cluster
- FEdit the new policy under section Capacity, filter object type by Cluster Compute Resource, and
How the community answered
(24 responses)- A4% (1)
- B75% (18)
- D17% (4)
- E4% (1)
Explanation
Creating a new policy that inherits from Base Settings (B) is correct because the existing default policy already has a 4:1 overcommit ratio - inheriting from it would carry that setting over, requiring extra steps to undo. Starting from Base Settings gives a clean foundation for the 2:1 configuration. Next, you must associate the policy to the target scope by going to Groups and Objects and selecting the Custom Group "Database Servers" (C) - this is how vROps knows which objects the policy governs. Finally, you configure the actual CPU overcommit ratio by going to Capacity, filtering by object type "Cluster Compute Resource," and setting 2:1 (F) - the Capacity section works at the object-type level, not the group level.
Why the distractors fail:
- A is wrong because the Capacity section filters by object type (e.g., Cluster Compute Resource), not by custom group - you can't select "Database Servers" there.
- D is wrong because inheriting from the current default policy drags in the 4:1 ratio you're trying to override, making inheritance from Base Settings the cleaner choice.
- E is wrong because in Groups and Objects you assign the custom group, not the object type - selecting "Cluster Compute Resource" there doesn't scope the policy to "Database Servers."
Memory tip: Think "B-C-F = Base → Connect → Fix" - Base the new policy on clean settings, Connect it to the custom group, then Fix the capacity ratio on the right object type.
Topics
Community Discussion
No community discussion yet for this question.