AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company wants to provide data scientists with near real-time read-only access to the company's production Amazon RDS for PostgreSQL database. The database is currently configured as a Single-AZ database. The data scientists use complex queries that will not affect the production database. The company needs a solution that is highly available.
Which solution will meet these requirements MOST cost-effectively?
Other
Community
UAnonymous
A
Scale the existing production database in a maintenance window to provide enough power for the data scientists.
B
Change the setup from a Single-AZ to a Multi-AZ instance deployment with a larger secondary standby instance. Provide the data scientists access to the secondary instance.
C
Change the setup from a Single-AZ to a Multi-AZ instance deployment. Provide two additional read replicas for the data scientists.
D
Change the setup from a Single-AZ to a Multi-AZ cluster deployment with two readable standby instances. Provide read endpoints to the data scientists.
Explanation:
Explanation
Correct Answer: D
Why Option D is the most cost-effective solution:
-
Multi-AZ Cluster Deployment with Readable Standby Instances: This option provides the best balance of high availability, read scalability, and cost-effectiveness for PostgreSQL RDS.
-
Key Benefits:
- High Availability: Multi-AZ cluster deployment provides automatic failover capabilities across Availability Zones.
- Read Scalability: The two readable standby instances can handle read-only queries from data scientists without impacting the primary instance.
- Cost-Effective: Readable standby instances in a Multi-AZ cluster are more cost-effective than creating separate read replicas (Option C) because they serve dual purposes:
- They act as failover targets
- They handle read traffic
- Near Real-Time Access: The standby instances are synchronized with the primary instance, providing near real-time data access.
- No Production Impact: Data scientists' complex queries run on the standby instances, not affecting the production database performance.
Why Other Options Are Less Suitable:
-
Option A: Scaling the existing database doesn't provide high availability (still Single-AZ) and would impact production performance since data scientists' queries would run on the same instance.
-
Option B: While Multi-AZ provides high availability, using a larger secondary standby instance for read queries is less cost-effective than having multiple smaller readable standby instances. Also, the secondary in Multi-AZ instance deployment is not readable by default (only in Multi-AZ cluster deployment).
-
Option C: Creating two additional read replicas provides read scalability but is more expensive than Option D because:
- Read replicas are separate instances with their own costs
- Multi-AZ cluster with readable standbys provides both high availability AND read scalability in a more integrated, cost-effective package
AWS RDS PostgreSQL Considerations:
- Multi-AZ cluster deployment for PostgreSQL supports up to 2 readable standby instances
- These standby instances can be used for read-only queries
- The solution provides automatic failover with RPO (Recovery Point Objective) typically under 35 seconds
- Read endpoints can be configured to distribute read traffic across the standby instances
This solution meets all requirements: near real-time read-only access, high availability, no production impact, and cost-effectiveness.
Comments
Loading comments...