A cloud administrator would like the VMware Cloud on AWS cluster to automatically scale-out and scale-In based on resource demand. Which two Elastic DRS policies can be configured to meet this…

Question

Options

• AElastic DRS Baseline policy
• BOptimize for Best Performance policy
• COptimize for Lowest Cost policy
• DCustom Elastic DRS policy
• EOptimize for Rapid Scale-Out policy

• B
  86% (19)
• D
  9% (2)
• E
  5% (1)

Explanation

Optimize for Best Performance (B) and Optimize for Lowest Cost (C) are the two built-in Elastic DRS policies that automatically trigger both scale-out (adding hosts) and scale-in (removing hosts) based on actual resource demand - Best Performance scales out proactively to preserve headroom, while Lowest Cost scales in aggressively to minimize spend, both reacting dynamically to workload changes.

Why the distractors are wrong:

• A (Elastic DRS Baseline policy) - This is not a real, named Elastic DRS policy in VMware Cloud on AWS; it's a fabricated distractor.
• D (Custom Elastic DRS policy) - While custom policies exist, they require manual threshold configuration and are not a standard preset that meets the requirement out of the box.
• E (Optimize for Rapid Scale-Out) - As the name suggests, this policy is designed for fast, aggressive scale-out in burst scenarios; it does not emphasize bidirectional (scale-out and scale-in) automation.

Memory tip: Think "Best Performance = Both directions for speed, Cheapest Cost = Cuts hosts to save money" - both dynamically balance the cluster, just with different priorities. If the answer involves automatic bidirectional scaling, look for the two policies that each represent opposite optimization goals (performance vs. cost).

No community discussion yet for this question.