The instance removal strategy supported by the elastic scaling service AS, when the instance in the scaling group is upgraded to a new instance type, and the older instance can be gradually replaced…

Question

Options

• AAn instance created earlier
• BAn instance created earlier in a configuration created later
• CManually move the instance into the scaling group
• DInstances created later

• A
  72% (38)
• B
  8% (4)
• C
  4% (2)
• D
  17% (9)

Explanation

Option A ("an instance created earlier") is correct because when upgrading to a new instance type, the goal is to remove the oldest instances first so that scale-out events naturally create new instances using the updated configuration. This produces a gradual, rolling replacement without disrupting running workloads.

Option B is a distractor that sounds plausible but inverts the logic: targeting instances created early under a later configuration would remove instances that already reflect the upgrade, which is counterproductive. Option C describes a manual operational action, not a removal strategy at all, so it cannot be configured as an automatic policy. Option D removes the most recently created instances first, which would eliminate the newly provisioned instances of the desired type and preserve the old ones -- the opposite of the intended outcome.

Memory tip: Match the strategy name to your goal. You want to get rid of old instances, so pick the policy that targets old instances. "Created earlier" equals oldest, and oldest equals the ones you want gone.

No community discussion yet for this question.