Discuss Amazon DOP-C02 Exam Topic 5 Question 44

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.

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.

Get Premium DOP-C02 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

31 comments · newest first

Venita 11 months ago

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

Lenna 11 months ago

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

Ettie 11 months ago

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

Olive 11 months ago

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

Solange 12 months ago

Option A seems solid for minimizing downtime.

Adelina 12 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.

Merrilee 1 year 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.

Jamie 1 year ago

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

An 1 year ago

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

Arlette 1 year 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.

Josue 1 year 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.

Paola 1 year 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.

Frankie 1 year 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.

Junita 1 year 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!

Adaline 1 year ago

↳ replying to Junita

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

Christiane 1 year ago

↳ replying to Junita

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

Marvel 1 year ago

↳ replying to Junita

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

Elke 1 year ago

↳ replying to Junita

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.

Alpha 1 year ago

Hold up, are we sure this isn't just a trick question to see if we're paying attention? I'm going with Option B, just to be safe.

Bette 2 years ago

I'm not sure, but I think turning on the Multi-AZ option could also help with availability during maintenance.

Irving 2 years ago

I agree with Wendell. Adding a reader instance and updating the application seems like the best approach.

Leonora 2 years ago

Option D is like the Swiss Army Knife of solutions - it has everything! Custom endpoints and Multi-AZ? Sign me up!

Emilio 1 year ago

↳ replying to Leonora

User 2: Yeah, I agree. Having custom endpoints and Multi-AZ is a solid plan.

Dominga 1 year ago

↳ replying to Leonora

User 1: Option D sounds like the best choice. It covers all the bases.

Tyra 2 years ago

I'm not sure about this 'custom ANY endpoint' thing. Sounds a bit sketchy to me. I'll stick with Option C and the tried-and-true Multi-AZ approach.

Albina 2 years ago

Option A is the way to go! Adding a reader instance ensures high availability during the maintenance window.

Erick 1 year ago

↳ replying to Albina

D: Multi-AZ option might be useful, but I think Option A covers the requirements efficiently.

Tammara 1 year ago

↳ replying to Albina

C: The reader endpoint for reads is also important to consider for minimal interruption.

Jennie 1 year ago

↳ replying to Albina

B: I agree, updating the application to use the cluster endpoint for write operations is key.

Ronny 1 year ago

↳ replying to Albina

A: Option A is definitely the best choice. Adding a reader instance will help maintain availability.

Wendell 2 years ago

I think the answer is A.

Amazon DOP-C02 Exam - Topic 5 Question 44 Discussion