You are responsible for your company’s large multi-tiered Windows-based web application running on Amazon EC2
instances situated behind a load balancer. While reviewing metrics, you’ve started noticing an upwards trend for slow
customer page load time. Your manager has asked you to come up with a solution to ensure that customer load time is
not affected by too many requests per second. Which technique would you use to solve this issue?
A.
Re-deploy your infrastructure using an AWS CloudFormation template.
Configure Elastic Load Balancing health checks to initiate a new AWS CloudFormation stack when health checks return failed.
B.
Re-deploy your infrastructure using an AWS CloudFormation template.
Spin up a second AWS CloudFormation stack.
Configure Elastic Load Balancing SpillOver functionality to spill over any slow connections to the second AWS CloudFormation stack.
C.
Re-deploy your infrastructure using AWS CloudFormation, Elastic Beanstalk, and Auto Scaling.
Set up your Auto Scaling group policies to scale based on the number of requests per second as well as the current customer load
time.
D.
Re-deploy your application using an Auto Scaling template.
Configure the Auto Scaling template to spin up a new Elastic Beanstalk application when the customer load time surpasses your
threshold.
C
C
C seams to be a reasonable choice
C
Absolutely C
C.
The problems belongs to Auto scaling so C is the best answer here.
C.
Key = scale based on the number of requests per second