Bird
0
0

Which JSON configuration correctly sets up a Dead Letter Queue for an AWS SQS queue with a maxReceiveCount of 5?

easy📝 Configuration Q3 of 15
AWS - SNS and SQS
Which JSON configuration correctly sets up a Dead Letter Queue for an AWS SQS queue with a maxReceiveCount of 5?
A{"DeadLetterConfig": {"targetArn": "arn:aws:sqs:region:account-id:DLQ", "maxRetries": 5}}
B{"RedrivePolicy": {"deadLetterTargetArn": "arn:aws:sqs:region:account-id:DLQ", "maxReceiveCount": 5}}
C{"RedrivePolicy": {"targetArn": "arn:aws:sqs:region:account-id:DLQ", "maxReceiveCount": 3}}
D{"DeadLetterQueue": {"arn": "arn:aws:sqs:region:account-id:DLQ", "maxReceiveCount": 5}}
Step-by-Step Solution
Solution:
  1. Step 1: Identify correct property names

    The correct property for configuring DLQ in SQS is RedrivePolicy with deadLetterTargetArn and maxReceiveCount.
  2. Step 2: Validate JSON structure

    {"RedrivePolicy": {"deadLetterTargetArn": "arn:aws:sqs:region:account-id:DLQ", "maxReceiveCount": 5}} correctly uses "RedrivePolicy" with "deadLetterTargetArn" and "maxReceiveCount" set to 5.
  3. Final Answer:

    {"RedrivePolicy": {"deadLetterTargetArn": "arn:aws:sqs:region:account-id:DLQ", "maxReceiveCount": 5}} is the correct JSON snippet.
  4. Quick Check:

    RedrivePolicy with deadLetterTargetArn and maxReceiveCount is required [OK]
Quick Trick: Use RedrivePolicy with deadLetterTargetArn and maxReceiveCount [OK]
Common Mistakes:
MISTAKES
  • Using incorrect property names like DeadLetterConfig
  • Setting maxReceiveCount to wrong values
  • Misnaming the ARN property

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes