Cloud · Flashcard
Reporting queries are saturating an RDS primary in a Multi-AZ instance deployment. What actually helps?
- AA read replica, which the reporting workload can be pointed at directly
- BPromoting the Multi-AZ standby, which is idle and can serve the reports
- CA second Multi-AZ standby in another Availability Zone to share the load
- DEnabling automatic backups, which offloads read traffic to the snapshot
Why this is the answer
In a Multi-AZ instance deployment the standby exists purely for failover and serves no traffic, so adding availability does nothing for a read bottleneck. A read replica is a separately addressable instance kept up to date asynchronously, and pointing reporting at it takes that load off the primary. Promoting the standby would break the failover pair, and backups are not a read path. (Note the contrast with a Multi-AZ DB cluster deployment, whose two reader instances are readable by design.)
Official docsMore AWS Solutions Architect Associate (SAA-C03) flashcards
- Private-subnet instances must reach S3 without traversing the internet, at the lowest cost. Which endpoint type?
- Instances pull terabytes per month from S3 through a NAT gateway. What removes most of that charge?
- A three-tier web application runs in one Availability Zone. The business needs it to survive the loss of a zone, the reporting queries are saturating the database, and the budget will not stretch to a second Region. What is the smallest set of changes that meets all three?