Your application's Auto Scaling Group scales up too quickly, too much, and stays scaled when traffic decreases. What should you do to fix this?
A) Set a longer cooldown period on the Group, so the system stops overshooting the target capacity. The issue is that the scaling system does not allow enough time for new instances to begin servicing requests before measuring aggregate load again.
B) Calculate the bottleneck or constraint on the compute layer, then select that as the new metric, and set the metric thresholds to the bounding values that begin to affect response latency.
C) Raise the CloudWatch Alarms threshold associated with your autoscaling group, so the scaling takes more of an increase in demand before beginning.
D) Use larger instances instead of many smaller ones, so the Group stops scaling out so much and wasting resources as the OS level, since the OS uses a higher proportion of resources on smaller instances.
Correct Answer:
Verified
Q571: Your application stores sensitive information on an
Q572: There is a very serious outage at
Q573: You currently have the following setup in
Q574: When writing plays, tasks and playbooks, Ansible
Q575: What option below is the geographic limit
Q577: Due to compliance regulations, management has asked
Q578: Your serverless architecture using AWS API Gateway,
Q579: When running a playbook on a remote
Q580: A startup company is developing a web
Q581: A company uses federated access for its
Unlock this Answer For Free Now!
View this answer and more for free by performing one of the following actions
Scan the QR code to install the App and get 2 free unlocks
Unlock quizzes for free by uploading documents