hardmultiple choiceObjective-mapped

Exhibit

Aurora cluster summary:
- 1 writer instance: db.r6g.large
- 2 reader instances: db.r6g.large
- Writer CPU avg: 82% / p95 91%
- Reader CPU avg: 18% / p95 26%
- Database connections: 480 total, all established to the cluster writer endpoint
- Query sample: 72% SELECT, 22% INSERT/UPDATE, 6% administrative queries

Based on the exhibit, an application runs on Amazon Aurora MySQL. The writer instance is frequently near 85% CPU while the reader instance is under 20% CPU. Application traces show that most of the database traffic is read-only SELECT queries, but the code currently sends all queries to the writer endpoint. What should the solutions architect recommend to improve performance with the smallest functional change?

Question 1hardmultiple choice
Full question →

Based on the exhibit, an application runs on Amazon Aurora MySQL. The writer instance is frequently near 85% CPU while the reader instance is under 20% CPU. Application traces show that most of the database traffic is read-only SELECT queries, but the code currently sends all queries to the writer endpoint. What should the solutions architect recommend to improve performance with the smallest functional change?

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

Increase the writer instance size and keep all traffic on the writer endpoint.

A larger writer can postpone saturation, but it wastes available read capacity and does not fix the traffic split problem.

B

Best answer

Point read-only database traffic to the Aurora reader endpoint and keep writes on the writer endpoint.

This directly uses the cluster’s read scale-out capability. The reader endpoint distributes read traffic across replicas, reducing load on the writer and increasing read throughput without changing schema or database engine.

C

Distractor review

Convert the cluster to a Multi-AZ RDS PostgreSQL deployment to get automatic failover and better read performance.

This changes both the engine and architecture, and it is not the lowest-impact way to improve read throughput for Aurora MySQL.

D

Distractor review

Enable cross-Region read replicas so SELECT queries are routed to a remote Region for improved performance.

Cross-Region replication helps disaster recovery and regional locality, but it adds latency and operational complexity rather than solving local writer saturation.

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: Point read-only database traffic to the Aurora reader endpoint and keep writes on the writer endpoint. — The exhibit shows a classic read/write split problem: the writer is busy, but the reader instances are underutilized. Aurora is designed to scale reads by directing read-only connections to the reader endpoint, which load-balances across reader instances. That improves throughput immediately, keeps writes on the writer, and requires the smallest functional change because the application only needs to route SELECT traffic appropriately. Upsizing the writer can help temporarily, but it ignores idle reader capacity and is less efficient. Switching engines to PostgreSQL is a major redesign, not a tuning change. Cross-Region replicas are for DR and geographic distribution, not local performance improvements, and they would usually add latency for application reads.

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.