2V0-16.25 · Question #36
An administrator has been tasked to share resources in the cluster between the Quality Assurance (QA) Department and Marketing Department. The following information has been provided: - In the case…
The correct answer is B. Set RP-QA to Fixed and RP-MKT to Scalable. Option B correctly satisfies both requirements by using complementary share types: Fixed shares for RP-QA guarantee it a consistent, predictable resource allocation that won't be squeezed during contention, while Scalable shares for RP-MKT allow Marketing's effective share…
Question
An administrator has been tasked to share resources in the cluster between the Quality Assurance (QA) Department and Marketing Department. The following information has been provided:
- In the case of contention, the QA Department must not lose any
performance.
- When the QA Department is not using all of its allocated resources,
the Marketing Department requires the ability to consume them.
- The administrator has set up resource pools for the QA Department
(RP-QA) and Marketing Department (RP-MKT). How should the resource shares be configured for each pool?
Options
- ASet both Resource Pools to Fixed.
- BSet RP-QA to Fixed and RP-MKT to Scalable.
- CSet RP-QA to Scalable and RP-MKT to Fixed.
- DIt is not possible to satisfy the requirements of both departments.
How the community answered
(29 responses)- A14% (4)
- B76% (22)
- C7% (2)
- D3% (1)
Explanation
Option B correctly satisfies both requirements by using complementary share types: Fixed shares for RP-QA guarantee it a consistent, predictable resource allocation that won't be squeezed during contention, while Scalable shares for RP-MKT allow Marketing's effective share count to grow proportionally as VMs are added, enabling it to absorb QA's idle capacity without a manual reconfiguration.
Why the distractors fail:
- A (both Fixed): Marketing cannot dynamically expand to consume QA's unused resources; both pools simply hold static allocations.
- C (RP-QA Scalable, RP-MKT Fixed): This reverses the logic - QA's shares would fluctuate with VM count, undermining its contention protection, while Marketing gets a rigid ceiling.
- D: The requirements are fully achievable; D is a distractor for anyone who misreads the share type behaviors.
Memory tip: Think "QA = Quality is Fixed, never negotiated; Marketing = Scalable, always hustling for more." Fixed locks in priority; Scalable unlocks growth.
Topics
Community Discussion
No community discussion yet for this question.