hardmultiple choiceObjective-mapped

Exhibit

Aurora cluster configuration:
- 1 writer instance
- 1 reader instance
- Application JDBC string: jdbc:mysql://cluster-writer.endpoint.example.com:3306/orders

CloudWatch metrics (peak hour):
- DBWriterCPUUtilization: 84%
- DBReaderCPUUtilization: 17%
- DatabaseConnections: steady
- ReadLatency p95: 38 ms
- WriteLatency p95: 9 ms

Application trace sample:
SELECT order_id, status, total FROM orders WHERE customer_id=? ORDER BY created_at DESC LIMIT 20

Based on the exhibit, an Amazon Aurora MySQL application is read-heavy, but the database writer is nearing CPU limits while the reader instance is mostly idle. The application currently sends all queries to the writer endpoint. Which change should you make first to increase read throughput?

Question 1hardmultiple choice
Full question →

Based on the exhibit, an Amazon Aurora MySQL application is read-heavy, but the database writer is nearing CPU limits while the reader instance is mostly idle. The application currently sends all queries to the writer endpoint. Which change should you make first to increase read throughput?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Keep using the writer endpoint so Aurora can route the reads automatically.

The writer endpoint sends traffic to the writer instance, which is already the bottleneck. It does not offload read traffic to the idle reader and therefore does not improve throughput.

B

Best answer

Change the application to send read-only queries to the Aurora reader endpoint.

The reader endpoint is designed to distribute read traffic across Aurora replica instances. Moving SELECT-heavy traffic off the writer immediately reduces writer CPU pressure and increases total read throughput.

C

Distractor review

Convert the cluster to a single-AZ deployment so network hops are reduced.

Aurora is already a managed multi-AZ service, and reducing AZ diversity would hurt resilience without solving the read bottleneck. The problem is query routing, not inter-AZ overhead.

D

Distractor review

Add an Amazon DynamoDB Accelerator (DAX) cluster in front of Aurora.

DAX is for DynamoDB, not Aurora MySQL. It cannot accelerate SQL reads from Aurora or change how the application routes database queries.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Change the application to send read-only queries to the Aurora reader endpoint. — The application is sending SELECT queries to the Aurora writer endpoint, which forces read traffic onto the writer instance and leaves the reader underused. Redirecting read-only queries to the Aurora reader endpoint is the first and most effective change. This offloads the writer, lowers read latency, and uses the replica that is already available for read scaling. The exhibit clearly shows the writer is the constraint, not the reader pool. Using the writer endpoint preserves the current bottleneck. Making the cluster single-AZ would reduce availability and does nothing for read scaling. DAX only applies to DynamoDB and is unrelated to Aurora MySQL, so it cannot solve this problem.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.