Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 195 discussion

C is correct. Step Scaling can solve the problem.

D is the correct answer. The key word here i sredesign the architecture . So why wouldn't i redesign in cloudfront

C is correct to me

Correct Answer - 'C' Step scaling applies “step adjustments” which means you can set multiple actions to vary the scaling depending on the size of the alarm breach. When you create a step scaling policy, you can also specify the number of seconds that it takes for a newly launched instance to warm up. Wrong Answer: Create a CloudFront distribution and set the EC2 instance as the origin is incorrect because this approach only resolves the traffic latency. Take note that the requirement in the scenario is to resolve the timeout issue and not the traffic latency.

C is the answer

C is the answer

I would go for D. The point of focus here is "Custom Application" takes 1 minute. Even though you manipulate the warm up of instance the application will still take 1 minute to boot. And in the choices we don't have something that talks about User Data or bootstrap.

C is correct to me. Warm-up value for Instances allows you to control the time until a newly launched instance can be part of an Auto Scaling group and will receive traffic. In this case, when EC2 will be part of an auto-scaling group, that will be ready to take traffic and users will not complain about timeout.

CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

C> Can solve slow start warm up issues only; while D> can solve both load balancing and slow start with ALB

D. Configure Amazon CloudFront to use an Application Load Balancer as the origin.

Can't be C as it is not a re-designed architecture, just a tweak of the existing. Also, it won't fix the timeouts. D is a redesigned architecture and the load balancer will reduce timeouts

redesign the architecture to better RESPOND to changing traffic Answer: C.

The aswer is C.

I would take C https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html#as-step-scaling-warmup: "If you are creating a step policy, you can specify the number of seconds that it takes for a newly launched instance to warm up. Until its specified warm-up time has expired, an instance is not counted toward the aggregated metrics of the Auto Scaling group. Using the example in the Step Adjustments section, suppose that the metric gets to 60, and then it gets to 62 while the new instance is still warming up. The current capacity is still 10 instances, so 1 instance is added (10 percent of 10 instances). However, the desired capacity of the group is already 11 instances, so the scaling policy does not increase the desired capacity further. If the metric gets to 70 while the new instance is still warming up, we should add 3 instances (30 percent of 10 instances). However, the desired capacity of the group is already 11, so we add only 2 instances, for a new desired capacity of 13 instances"

C. takes 1 minute to initiate upon boot up. Instance warm up can help to prevent from taking a EC2 instance metric as scaling criteria while it is still booting up. you can specify the number of seconds that it takes for a newly launched instance to warm up. Until its specified warm-up time has expired, an instance is not counted toward the aggregated metrics of the Auto Scaling group

C for sure. In step scaling there is no waiting period or cooldown period so it can adjust to alarms at any time.