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

C is correct. You want to scale this application based on # of messages in SQS.

C correct. The metric you need to monitor is ApproximateNumberOfMessages

Selected Answer: C

CCCCCCCCCC

Agreed with C

- C - A and B are wrong. Launch configurations are not recommended. Launch templates are preferred - D is wrong. SNS is for sending notifications

"loosely connected" indicates SQS 'tasks' indicates ECS cluster (further 'state is not maintained' indicated ECS) SNS will publish a job received to multiple subscribers,we dont want same job to go to multiple instances for processing So A and D are out 'number of jobs to be handled dictating the number of applciation nodes added or removed'-->has to do autoscaling based on no of items not network

What is the difference between "hold the jobs" vs "send the jobs"?

CORRECT: "Create an Amazon SQS queue to hold the jobs that needs to be processed. Create an Amazon EC2 Auto Scaling group for the compute application. Set the scaling policy for the Auto Scaling group to add and remove nodes based on the number of items in the SQS queue" is the correct answer. Explanation: In this case we need to find a durable and loosely coupled solution for storing jobs. Amazon SQS is ideal for this use case and can be configured to use dynamic scaling based on the number of jobs waiting in the queue.To configure this scaling you can use the backlog per instance metric with the target value being the acceptable backlog per instance to maintain. You can calculate these numbers as follows: Backlog per instance: To calculate your backlog per instance, start with the ApproximateNumberOfMessages queue attribute to determine the length of the SQS queue

C is correct

C vs D (SQS vs SNS) It's a standard practice to scale based on SQS length and not based on SNS's NumberOfMessagesPublished. Thus, I would go for C.

loosely coupled -> SQS, based on number of jobs -> number of item in SQS queue

C correct. the autoscale should be based on number of items in SQS queue not network usage.

C for correct SQS helps design a loosely coupled architecture with an ability to store the message durably. Auto Scaling Group with target scaling policy based on the number of items in SQS would help scale the application nodes as per the demand.

C for sure

it's C

Ans = C