You have an application which consists of EC2 instances in an Auto Scaling group. Between a
particular time frame every day, there is an increase in traffic to your website. Hence users are
complaining of a poor response time on the application. You have configured your Auto Scaling
group to deploy one new EC2 instance when CPU utilization is greater than 60% for 2
consecutive periods of 5 minutes. What is the least cost-effective way to resolve this problem?
A. Decrease the consecutive number of collection periods
B. Increase the minimum number of instances in the Auto Scaling group
C. Decrease the collection period to ten minutes
D. Decrease the threshold CPU utilization percentage at which to deploy a new instance
If you increase the minimum number of instances, then they wil be running even though the
load is not high on the website. Hence you are incurring cost even though there is no need.
Al of the remaining options are possible options which can be used to increase the number of
instances on a high load.
For more information on On-demand scaling, please refer to the below link:
Note: The tricky part where the question is asking for 'least cost effective way". You got the
design consideration correctly but need to be careful on how the question is phrased.
You have decided that you need to change the instance type of your production instances which
are running as part of an AutoScaling group. The entire architecture is deployed using
CloudFormation Template. You currently have 4 instances in Production. You cannot have any
interruption in service and need to ensure 2 instances are always running during the update?
Which of the options below listed can be used for this?
The AWS::AutoScaling::AutoScalingGroup resource supports an UpdatePoIicy attribute. This is
used to define how an Auto Scalinggroup resource is updated when an update to the Cloud
Formation stack occurs. A common approach to updating an Auto Scaling group is to perform a
rolling update, which is done by specifying the AutoScalingRollingUpdate policy. This retains the
same Auto Scaling group and replaces old instances with new ones, according to the
parameters specified. For more information on Autoscaling updates, please refer to the below
You currently have the fol owing setup in AWS:
1)An Elastic Load Balancer