Run heavy daily read-only analytics without stopping production writes.
Some replication lag is acceptable if the application's write performance remains protected.
Which configuration is most appropriate?
Send analytical reads to an RDS Read Replica so the primary handles transactional traffic.
Detailed explanation
Large scans can consume CPU and I/O needed by transactional writes.
Large scans can consume CPU and I/O needed by transactional writes.
A change stream does not provide a relational analytical query environment.
A change stream does not provide a relational analytical query environment.
Archive storage is not an immediate SQL replica of the RDS database.
Archive storage is not an immediate SQL replica of the RDS database.
A read replica isolates read load asynchronously while the primary continues serving writes.
A read replica isolates read load asynchronously while the primary continues serving writes.
Check official documentation
Compare the following points with the official documentation.
Amazon RDS Read Replica、非同期レプリケーション、昇格、制約の公式説明を確認する。
What to confirm
分析負荷分離と、ストリーム変更配信・アーカイブ保存を区別できる。
Key points
- Read Replica
- RDS
- Read scaling
- Asynchronous replication
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Workload isolation
Analytics scans should not compete with production writes for primary resources.
Freshness trade-off
Acceptable lag and consistency requirements determine whether a replica is suitable.