Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 141 discussion

The correct answer is C. The company can solve the problem by configuring scale-in protection for the instances during processing. This will ensure that the instances are not terminated while they are processing videos. This will prevent the messages from moving to the dead-letter queue and ensure that videos are processed properly. Option A is incorrect because turning on termination protection for the EC2 instances will not solve the problem as it will impact the ability of the Auto Scaling group to scale instances in and out based on the number of videos in the queue. Option B is incorrect because the company has specified a visibility timeout of 1 hour, which is enough time for the instances to process a video and there is no need to update the timeout to 3 hours. Option D is incorrect because the company has set the maxReceiveCount to 1 and changing it to 0 will not solve the problem. maxReceiveCount allowed range is 1 to 1000.

Refer https://aws.amazon.com/blogs/aws/new-instance-protection-for-auto-scaling/ From the above link, "an instance might be handling a long-running work task, perhaps pulled from an SQS queue. Protecting the instance from termination will avoid wasted work" - This is what the question is also alluding to. This is how one would make use of the functionality. You change the protection status of one or more instances by calling the SetInstanceProtection function. If you wanted to use this function to protect long-running, queue-driven worker processes from scale-in termination, you could set up your application as follows (this is pseudocode): while (true) { SetInstanceProtection(False); Work = GetNextWorkUnit(); SetInstanceProtection(True); ProcessWorkUnit(Work); SetInstanceProtection(False); }

The correct answer is C, because the problem is caused by EC2 instances being terminated by Auto Scaling while processing a message, before the message can be deleted from the SQS queue. This causes the message to reappear and immediately go to the dead-letter queue due to maxReceiveCount = 1. Applying scale-in protection during processing ensures the instance is not terminated mid-task, preventing message loss.

Correct is C: B. 3-hour visibility timeout Too long for 30-minute processing Could delay reprocessing of failed messages Doesn't address root cause C. Scale-in protection during processing Prevents instance termination while processing Allows message processing to complete Prevents message return to queue Stops premature scale-in ✓ CORRECT

B is correct; updating the visibility timeout to 3 hours (option B) is the most appropriate solution as it gives enough time for the messages to be processed without being prematurely marked as failures.

D is a typo

If Option D is a typo, then D

B. The best solution for this problem is to update the visibility timeout for the SQS queue to 3 hours. This is because when the visibility timeout is set to 1 hour, it means that if the EC2 instance doesn't process the message within an hour, it will be moved to the dead-letter queue. By increasing the visibility timeout to 3 hours, this should give the EC2 instance enough time to process the message before it gets moved to the dead-letter queue. Additionally, configuring scale-in protection for the EC2 instances during processing will help to ensure that the instances are not terminated while the messages are being processed.

Option D is a typo. I seen the same question in udemy but the Option D is 10

Option C is correct.

setting MaxReceiveCount to 0 doesn't make and send and it impossible, because messages would be send to DLQ without any attempt to consume them from source queue

checked 4 AI, C is definitely not the correct answer: Option C: Configuring scale-in protection for the instances during processing will not prevent messages from being moved to the dead-letter queue if they cannot be processed on the first attempt.

Going with C only because D has value of maxReceiveCount set to 0

I go with C

B. AWS "recommends setting your queue's visibility timeout to six times your function timeout" which makes 3 hours perfect. source: https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html

C more likely

I couldn't find any way to configure scale-in protection for the instances during processing except to do it manually, which is going to be an insane exercise. Eventually, that can be done by the application as part of the processing but I would then expect some more context in the answer.