New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon DOP-C02 Exam - Topic 4 Question 57 Discussion

Actual exam question for Amazon's DOP-C02 exam
Question #: 57
Topic #: 4
[All DOP-C02 Questions]

A DevOps team manages infrastructure for an application. The application uses long-running processes to process items from an Amazon Simple Queue Service (Amazon SQS) queue. The application is deployed to an Auto Scaling group.

The application recently experienced an issue where items were taking significantly longer to process. The queue exceeded the expected size, which prevented various business processes from functioning properly. The application records all logs to a third-party tool.

The team is currently subscribed to an Amazon Simple Notification Service (Amazon SNS) topic that the team uses for alerts. The team needs to be alerted if the queue exceeds the expected size.

Which solution will meet these requirements with the MOST operational efficiency?

Show Suggested Answer Hide Answer
Suggested Answer: B

Comprehensive and Detailed Explanation From Exact Extract:

The Amazon SQS service publishes several standard CloudWatch metrics by default, including ApproximateNumberOfMessagesVisible, which represents the number of messages available for retrieval from the queue (i.e., the number of messages waiting to be processed). This is the primary metric to monitor queue backlog and processing delays.

Using ApproximateNumberOfMessagesVisible to monitor the visible messages in the queue gives a direct and near real-time indication of processing delays or backlog.

CloudWatch metrics are automatically collected and available without the need to create custom metrics or Lambda functions, which increases operational efficiency by reducing complexity and maintenance overhead.

Setting a CloudWatch alarm on this metric with a static threshold and a reasonable evaluation period (such as 1 hour) is sufficient to alert the team when the queue grows beyond an expected size.

The alarm can be directly configured to send notifications to an existing SNS topic, maintaining seamless integration with the team's alerting mechanisms.

The ApproximateNumberOfMessagesDelayed metric refers to messages that are delayed and not available for processing yet due to delay settings, which is not the direct backlog that causes business process delays.

Options C and D introduce unnecessary complexity by requiring Lambda functions and custom metrics or scheduled invocations, which reduce operational efficiency compared to using built-in CloudWatch metrics and alarms.

Reference from AWS Official Documentation and Study Guide:

Amazon SQS Monitoring with CloudWatch Metrics:

'Amazon SQS automatically sends metrics to CloudWatch, including ApproximateNumberOfMessagesVisible, which shows the number of messages available for retrieval.'

(Source: Amazon SQS Monitoring - AWS Documentation)

Setting CloudWatch Alarms for SQS Queues:

'You can create CloudWatch alarms on SQS metrics such as ApproximateNumberOfMessagesVisible to receive notifications when the queue size exceeds a threshold.'

(Source: Amazon CloudWatch Alarms - AWS Documentation)

AWS DevOps Engineer Professional Exam Guide:

'Efficient alerting for queue backlogs should leverage native CloudWatch metrics to minimize operational overhead.'

(Source: Official AWS Certified DevOps Engineer Professional Study Guide)


Contribute your Thoughts:

0/2000 characters
Glory
3 days ago
Option D looks simpler, but Option C seems more robust and scalable.
upvoted 0 times
...
William
8 days ago
I agree, Option C covers all the requirements and provides a good monitoring solution.
upvoted 0 times
...
Latanya
13 days ago
Option C seems the most comprehensive and efficient solution.
upvoted 0 times
...
Mitzie
18 days ago
I recall that using Lambda functions can add complexity, but they might be necessary for more specific checks. I just hope it doesn't create too much overhead.
upvoted 0 times
...
Casey
23 days ago
I’m a bit confused about the difference between the static threshold and the custom metric approach. I wonder if the custom metric would provide more flexibility?
upvoted 0 times
...
Trevor
29 days ago
I think we practiced a similar question where we had to decide between using visible messages or delayed messages. I feel like the delayed messages might be more relevant here.
upvoted 0 times
...
Maddie
1 month ago
I remember we discussed how CloudWatch alarms can help monitor SQS metrics, but I'm not sure which metric to focus on for this scenario.
upvoted 0 times
...
Marge
1 month ago
Option A seems like a good starting point, but I'm not sure if the average of the ApproximateNumberOfMessagesDelayed metric is the best indicator of the queue size. I might want to explore the other options in more depth before making a decision.
upvoted 0 times
...
Cyndy
1 month ago
I'm leaning towards option B. Monitoring the sum of the ApproximateNumberOfMessagesVisible metric seems like a straightforward way to detect if the queue is exceeding the expected size. The static threshold alarm should be easy to set up and configure.
upvoted 0 times
...
Raina
2 months ago
Option C looks interesting, but creating a custom CloudWatch metric and setting up an EventBridge rule seems a bit more complex than the other options. I'm not sure if that's the most operationally efficient approach.
upvoted 0 times
...
Coleen
2 months ago
I'm a bit confused by the different metrics mentioned in the options. I'm not sure if I fully understand the differences between ApproximateNumberOfMessagesDelayed and ApproximateNumberOfMessagesVisible. I'll need to review those metrics more closely.
upvoted 0 times
...
Tess
2 months ago
I think option D might be the best approach here. The Lambda function can directly check the queue attribute and send a notification if it exceeds the expected size, which seems like the most efficient way to monitor the queue.
upvoted 0 times
...

Save Cancel