Amazon DOP-C02 Exam - Topic 5 Question 44 Discussion

Actual exam question for Amazon's DOP-C02 exam

Question #: 44
Topic #: 5

A company is using an Amazon Aurora cluster as the data store for its application. The Aurora cluster is configured with a single DB instance. The application performs read and write operations on the database by using the cluster's instance endpoint.

The company has scheduled an update to be applied to the cluster during an upcoming maintenance window. The cluster must remain available with the least possible interruption during the maintenance window.

What should a DevOps engineer do to meet these requirements?

AAdd a reader instance to the Aurora cluster. Update the application to use the Aurora cluster endpoint for write operations. Update the Aurora cluster's reader endpoint for reads.

BAdd a reader instance to the Aurora cluster. Create a custom ANY endpoint for the cluster. Update the application to use the Aurora cluster's custom ANY endpoint for read and write operations.

CTurn on the Multi-AZ option on the Aurora cluster. Update the application to use the Aurora cluster endpoint for write operations. Update the Aurora cluster's reader endpoint for reads.

DTurn on the Multi-AZ option on the Aurora cluster. Create a custom ANY endpoint for the cluster. Update the application to use the Aurora cluster's custom ANY endpoint for read and write operations.

Show Suggested Answer

Suggested Answer: D

Step 2: Using an SQS Dead-Letter Queue (DLQ) Configuring a dead-letter queue (DLQ) for SQS will ensure that messages with invalid data, or those that cannot be processed successfully, are moved to the DLQ. This prevents such messages from clogging the queue and allows the system to focus on processing valid messages.

Action: Configure an SQS dead-letter queue for the main queue.

Why: A DLQ helps isolate problematic messages, preventing them from continuously reappearing in the queue and causing processing delays for valid messages.

Step 3: Maintaining the Lambda Function's Batch Size Keeping the current batch size allows the Lambda function to continue processing multiple messages at once. By addressing the failed items separately, there's no need to increase or reduce the batch size.

Action: Maintain the Lambda function's current batch size.

Why: Changing the batch size is unnecessary if the invalid messages are properly handled by reporting failed items and using a DLQ.

This corresponds to Option D: Keep the Lambda function's batch size the same. Configure the Lambda function to report failed batch items. Configure an SQS dead-letter queue.

by Rossana at Feb 11, 2025, 01:31 PM

Limited Time Offer

25%

Off

Get Premium DOP-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Venita

4 months ago

Not sure about D, sounds complicated for a simple update.

upvoted 0 times

...

Lenna

4 months ago

I agree, A is the way to go for this scenario.

upvoted 0 times

...

Ettie

4 months ago

Wait, does turning on Multi-AZ really help that much?

upvoted 0 times

...

Olive

4 months ago

I think B is better for flexibility with read/write.

upvoted 0 times

...

Solange

5 months ago

Option A seems solid for minimizing downtime.

upvoted 0 times

...

Adelina

5 months ago

I’m a bit confused about the difference between the cluster endpoint and the reader endpoint. I hope I can remember which one to use for writes during maintenance.

upvoted 0 times

...

Merrilee

5 months ago

I practiced a similar question where we had to choose between endpoints. I feel like the custom ANY endpoint could be a good choice for both reads and writes.

upvoted 0 times

...

Jamie

5 months ago

I think using the Multi-AZ option could help with availability during maintenance, but I can't recall if that alone is enough.

upvoted 0 times

...

An

5 months ago

I remember something about adding a reader instance to improve availability, but I'm not sure if that's the best option here.

upvoted 0 times

...

Arlette

5 months ago

I'm leaning towards option D. Turning on Multi-AZ and using a custom ANY endpoint sounds like the most robust solution to ensure continuous availability during the maintenance window.

upvoted 0 times

...

Josue

5 months ago

Okay, I've got a strategy. I'll go with option A - add a reader instance and update the app to use the reader endpoint for reads. That way, the main writer instance can be updated without impacting the application's availability.

upvoted 0 times

...

Paola

5 months ago

Hmm, I'm a bit confused. Adding a reader instance seems like a good idea, but I'm not sure about the custom ANY endpoint. I'll need to review the Aurora documentation to understand that option better.

upvoted 0 times

...

Frankie

6 months ago

This seems like a straightforward question about maintaining availability during a maintenance window. I think the key is to leverage the Aurora cluster's reader and writer capabilities.

upvoted 0 times

...

Junita

11 months ago

I heard the maintenance window is scheduled during rush hour traffic. Good luck to the DevOps engineer trying to keep that cluster up and running!

upvoted 0 times

Adaline

9 months ago

D: Adding a custom ANY endpoint for the cluster might be a good solution too. It's important to minimize interruption during the update.

upvoted 0 times

...

Christiane

9 months ago

C: Turning on the Multi-AZ option on the Aurora cluster could also help keep it available during the maintenance window.

upvoted 0 times

...

Marvel

10 months ago

B: Yeah, that sounds like a good idea. They could also update the Aurora cluster's reader endpoint for reads.

upvoted 0 times

...

Elke

10 months ago

A: I think the DevOps engineer should add a reader instance to the Aurora cluster and update the application to use the Aurora cluster endpoint for write operations.

upvoted 0 times

...