An application is deployed on Amazon EC2 instances that run in an Auto Scaling group. The Auto Scaling group configuration uses only one type of instance. CPU and memory utilization metrics show that the instances are underutilized. A solutions architect needs to implement a solution to permanently reduce the EC2 cost and increase the utilization. Which solution will meet these requirements with the LEAST number of configuration changes in the future?
Select an option, then click Submit answer.
Reference / correct answer:
Use the information about the application's CPU and memory utilization to specify CPU and memory requirements in a new revision of the Auto Scaling group's launch template. Remove the current instance type from the configuration.
Most accepted answer: C. Use the information about the application's CPU and memory utilization to specify CPU and memory requirements in a new revision of the Auto Scaling group's launch template. Remove the current instance type from the configuration.
Community votes: A=2, B=6, C=6
Selected Answer: C It's C. You change the instance type/size in the launch template not the ASG. ASG can change the min/max size, not instance type. upvoted 16 times titi_r 2 years, 3 months ago I’ve tested it myself in the AWS Console – correct answer is “B”. To change the instance type you have 3 options, and all of them require modifying the ASG’s config: 1. Create a new revision of the current launch template, then change the ASG config to use it. 2. Create a new launch template, then change the ASG config to use it. 3. Use the option “Override launch template” in the ASG config. If you only create a new revision of the launch template, the ASG will continue to use the old revision. The state that you cannot change the instance type from the ASG config is NOT true and anybody can verify it in the AWS Console. upvoted 7 times helloworldabc 1 year, 11 months ago just C upvoted 1 times ... ...
I’ve tested it myself in the AWS Console – correct answer is “B”. To change the instance type you have 3 options, and all of them require modifying the ASG’s config: 1. Create a new revision of the current launch template, then change the ASG config to use it. 2. Create a new launch template, then change the ASG config to use it. 3. Use the option “Override launch template” in the ASG config. If you only create a new revision of the launch template, the ASG will continue to use the old revision. The state that you cannot change the instance type from the ASG config is NOT true and anybody can verify it in the AWS Console. upvoted 7 times helloworldabc 1 year, 11 months ago just C upvoted 1 times ...
just C upvoted 1 times
Selected Answer: B The answer used to be C, but now it's B. But not for the reasons others here have mentioned. The question states that "The Auto Scaling group configuration uses only one type of instance". This implies the ASG config has implemented instance overrides, which - you guessed it - overrides the instance type that's specified in the launch template. You could cut new versions of launch templates until you're blue in the face, it wont make a lick of difference if the ASG config is overriding the instance type. And because ASGs can be modified, I reckon that puts a nail in C's coffin, making B the new correct answer. I think this is the first question (out of 400+) where the moderator-selected solution was correct and the community-voted solution was incorrect. upvoted 8 times fartosh 2 years, 2 months ago I believe "The Auto Scaling group configuration uses only one type of instance." is just a badly phrased sentence and the question designer only meant that instances running under AutoScaling Group are of one instance type. I understand the sentence as a suggestion to improve the state by specifying multiple types instead. Apart from the wording, there's nothing wrong with answer C. It lets you stop worrying about the future instance generations, too, compared to B where you have to modify the instance type whenever a new generation is released. Also, as specific instance types can be temporarily unavailable (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/troubleshooting-launch.html#troubleshooting-launch-capacity), C can smoothly use another available instance automatically. upvoted 2 times ...
I believe "The Auto Scaling group configuration uses only one type of instance." is just a badly phrased sentence and the question designer only meant that instances running under AutoScaling Group are of one instance type. I understand the sentence as a suggestion to improve the state by specifying multiple types instead. Apart from the wording, there's nothing wrong with answer C. It lets you stop worrying about the future instance generations, too, compared to B where you have to modify the instance type whenever a new generation is released. Also, as specific instance types can be temporarily unavailable (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/troubleshooting-launch.html#troubleshooting-launch-capacity), C can smoothly use another available instance automatically. upvoted 2 times
