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 has a large dataset for its online advertising business stored in an Amazon RDS for MySQL DB instance in a single Availability Zone. The company wants business reporting queries to run without impacting the write operations to the production DB instance.
Which solution meets these requirements?
Other
Community
UAnonymous
A
Deploy RDS read replicas to process the business reporting queries.
B
Scale out the DB instance horizontally by placing it behind an Elastic Load Balancer.
C
Scale up the DB instance to a larger instance type to handle write operations and queries.
D
Deploy the DB instance in multiple Availability Zones to process the business reporting queries.
Explanation:
Explanation
Correct Answer: A
Amazon RDS Read Replicas are specifically designed to handle read-heavy workloads like business reporting queries without impacting the write operations on the primary database instance. Here's why:
Why Option A is Correct:
- Read/Write Separation: Read replicas allow you to offload read traffic from the primary database instance to one or more read-only copies.
- No Impact on Primary: Business reporting queries (which are typically read-only) can be directed to read replicas, leaving the primary instance free to handle write operations.
- Asynchronous Replication: Read replicas use asynchronous replication, so they don't affect the performance of the primary instance.
- Scalability: You can create multiple read replicas to handle increasing read traffic.
Why Other Options are Incorrect:
Option B: Placing an RDS instance behind an Elastic Load Balancer doesn't work because RDS instances are not designed to be load balanced in this way. ELB is for distributing traffic across multiple EC2 instances, not RDS instances.
Option C: Scaling up (vertical scaling) to a larger instance type might improve overall performance, but it doesn't separate read and write operations. Both read and write operations would still compete for resources on the same instance.
Option D: Deploying the DB instance in multiple Availability Zones (Multi-AZ) provides high availability and failover capability, but it doesn't separate read and write operations. Multi-AZ deployments maintain a synchronous standby replica in another AZ for failover purposes only, not for read scaling.
Best Practice Recommendation:
For this scenario, the company should:
- Create one or more RDS Read Replicas in the same or different regions
- Configure their business reporting application to connect to the read replica endpoint
- Monitor replication lag to ensure data consistency for reporting
- Consider using Amazon Aurora if they need even better read scaling capabilities (Aurora can support up to 15 read replicas with minimal replication lag)
Comments
Loading comments...