During metric analysis, your team has determined that the company’s website is experiencing response times during
peak hours that are higher than anticipated. You currently rely on Auto Scaling to make sure that you are scaling your
environment during peak windows. How can you improve your Auto Scaling policy to reduce this high response time?
Choose 2 answers.
A.
Push custom metrics to CloudWatch to monitor your CPU and network bandwidth from your servers, which will allow your Auto Scaling
policy to have better fine-grain insight.
B.
Increase your Auto Scaling group’s number of max servers.
C.
Create a script that runs and monitors your servers; when it detects an anomaly in load, it posts to an Amazon SNS topic that triggers
Elastic Load Balancing to add more servers to the load balancer.
D.
Push custom metrics to CloudWatch for your application that include more detailed information about your web application, such as
how many requests it is handling and how many are waiting to be processed.
E.
Update the CloudWatch metric used for your Auto Scaling policy, and enable sub-minute granularity to allow auto scaling to trigger
faster.
I think B & C.
A: not necessary. It handles by Cloudwatch default
D: not mention to action for resolving issue
E: it only improves the at step trigger ASG more quickly
B and D are working in tandem since the ultimate solution is to increase server instances but how many exactly better balance the needs and costs, choice B gives the solution. AWS questions are not like Azure that gives hints as choices following step one and step two, or both choices work for the same problem. This question I think talks about step one and step two. I believe that the answer is B & D.
I meant, “…to increase a number of server instances…” and D gives the solution (analyzing of requests and responses).
B,D
B & D
Definitely not C because its Auto scale group not ELB which adds more servers.
BD
DE
BD
I thik B and E are correct！Because E can help respond to the traffic change more quickly and the response time will be less.
E mentions about “…trigger faster.” Currently, AWS talks about triggering earlier, not triggering faster, to match the timing since any instance launched by AutoScaling needs time to fully boot up to its normal condition responding to web requests, for example. So E does not make sense here.
B & D
Explanation :
Auto scaling is already being used to the problem might be ‘Less number of instance assigned to Auto scaling group’ so B is a good option.
The other thing we can do is , monitoring the requests being processed so the other option is D.
B&D,
E Sounds good to me but in the question is nothing about fast scale
B&D.
C is wrong.SNS topic can not trigger ELB
B,D