Read-Heavy Relational Database with RDS Read Replicas
A company is designing a new application that requires a relational database with high read capacity. The application is read-heavy and requires low latency. Which database configuration should be used?
Quick Answer
The answer is Amazon RDS with read replicas. This configuration is correct because a read-heavy relational database with low latency requires offloading read traffic from the primary instance to multiple read replicas, which scale read capacity horizontally and reduce latency by distributing the load across synchronized copies of the data. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of when to scale reads versus writes—a common trap is choosing Amazon DynamoDB DAX or ElastiCache, but the question explicitly requires a relational database, so RDS read replicas are the only fit. A key memory tip: if the workload is read-heavy and relational, think "replicas for reads, Aurora for auto-scaling."
⚠ Common exam trap
Test-takers frequently confuse Multi-AZ deployments with read replicas, assuming Multi-AZ also improves read performance, but Multi-AZ only provides failover redundancy and does not offload read traffic.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Amazon RDS with read replicas
Amazon RDS with read replicas is the correct choice because the application is read-heavy and requires low latency. Read replicas offload read traffic from the primary database instance, scaling read capacity and reducing latency for read operations by distributing the load across multiple copies of the data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Amazon RDS with read replicas
Why this is correct
Read replicas scale read capacity.
- ✗
Amazon DynamoDB with DAX
Why it's wrong here
DynamoDB is NoSQL, not relational.
- ✗
Amazon RDS with Multi-AZ deployment
Why it's wrong here
Multi-AZ is for high availability, not read scaling.
- ✗
Amazon ElastiCache for Redis
Why it's wrong here
ElastiCache is a cache, not a relational database.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAP-C02 question from scratch — 1,660 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SAP-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is designing a new application that requires a relational database with automated backups and multi-AZ redundancy. The database workload is predictable with occasional read replicas for reporting. Which AWS service should be used?
medium- ✓ A.Amazon RDS
- B.Amazon Redshift
- C.Amazon DynamoDB
- D.Amazon ElastiCache
Why A: Amazon RDS is the correct choice because it provides managed relational databases (e.g., MySQL, PostgreSQL, Oracle, SQL Server) with built-in automated backups and Multi-AZ redundancy for high availability. The workload is predictable and requires occasional read replicas for reporting, both of which are natively supported by RDS without the need for complex configuration.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.