mediummulti selectObjective-mapped

A web application uses an Amazon Aurora DB cluster for a read-heavy workload. The team wants to increase read throughput without changing the database schema or rewriting application data access patterns. Which two changes should they make? Select two.

Question 1mediummulti select
Full question →

A web application uses an Amazon Aurora DB cluster for a read-heavy workload. The team wants to increase read throughput without changing the database schema or rewriting application data access patterns. Which two changes should they make? Select two.

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

Best answer

Add Aurora Replicas to scale out read traffic across multiple database instances.

Aurora Replicas are the primary horizontal scaling mechanism for read-heavy Aurora workloads. They add more database compute so the cluster can process more concurrent read queries.

B

Best answer

Send read queries to the Aurora reader endpoint so they are distributed across the replicas.

The reader endpoint automatically routes connections to Aurora Replicas, which lets the application use additional read capacity without hard-coding individual replica endpoints.

C

Distractor review

Point all queries to the writer endpoint so Aurora can balance reads and writes internally.

The writer endpoint is intended for writes and for transactional work that must go to the primary instance. Sending all reads there concentrates load on the primary and reduces the benefit of replicas.

D

Distractor review

Enable Multi-AZ standby for the cluster to increase the number of read-only connections.

Aurora Multi-AZ is about availability and failover, not extra read scaling. A standby or passive component does not provide the same read capacity as adding active replicas.

E

Distractor review

Move the database to a single larger instance class instead of adding replicas.

A larger instance may improve the performance of one node, but it does not provide the horizontal scaling needed for a read-heavy workload. The question asks for more read throughput without changing the application design, which is exactly what replicas and the reader endpoint provide.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Add Aurora Replicas to scale out read traffic across multiple database instances. — Aurora increases read throughput by adding Aurora Replicas and routing read-only traffic to the reader endpoint. The replicas provide additional compute capacity for queries, while the reader endpoint distributes connections across available replicas without requiring application code to know each instance address. That combination scales reads cleanly while preserving the existing schema and access patterns. Sending all traffic to the writer endpoint overloads the primary instance and defeats Aurora read scaling. Multi-AZ standby focuses on availability and recovery, not read capacity. A bigger single instance can help one node, but it is not a horizontal scaling strategy for a read-heavy cluster.

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.