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 recently started using Amazon Aurora as the data store for its global ecommerce application. When large reports are run, developers report that the ecommerce application is performing poorly. After reviewing metrics in Amazon CloudWatch, a solutions architect finds that the ReadIOPS and CPUUtilization metrics are spiking when monthly reports run.
What is the MOST cost-effective solution?
Other
Community
UAnonymous
A
Migrate the monthly reporting to Amazon Redshift.
B
Migrate the monthly reporting to an Aurora Replica.
C
Migrate the Aurora database to a larger instance class.
D
Increase the Provisioned IOPS on the Aurora instance.
Explanation:
Explanation
Correct Answer: B - Migrate the monthly reporting to an Aurora Replica.
Why this is the most cost-effective solution:
-
Aurora Read Replicas are specifically designed to offload read traffic from the primary instance. Monthly reports are read-intensive operations that consume significant ReadIOPS and CPU resources.
-
Cost-effectiveness: Aurora Read Replicas are less expensive than scaling up the primary instance or migrating to a completely different service like Amazon Redshift. You only pay for the replica instance, which can handle the reporting workload without affecting the primary production database.
-
Performance isolation: By moving reporting queries to a replica, you prevent the read-intensive reporting workload from impacting the performance of the primary ecommerce application, which likely handles critical transactional operations.
-
No application changes required: The application can be configured to direct reporting queries to the replica endpoint while maintaining transactional operations on the primary instance.
Why other options are less cost-effective:
-
A. Migrate the monthly reporting to Amazon Redshift: While Redshift is excellent for analytics, this would require data migration, ETL processes, and additional service costs. It's overkill for monthly reporting and introduces unnecessary complexity and expense.
-
C. Migrate the Aurora database to a larger instance class: This would increase costs for the entire database 24/7, even though the reporting workload only occurs monthly. You'd be paying for unused capacity most of the time.
-
D. Increase the Provisioned IOPS on the Aurora instance: Aurora uses a distributed storage system where I/O is automatically scaled. Provisioned IOPS aren't directly configurable in the same way as RDS. Even if this were possible, it would increase ongoing costs without addressing the CPU utilization issue.
Key AWS Concepts:
- Aurora Read Replicas provide horizontal scaling for read workloads
- Replicas can be created in different regions for global applications
- Replicas can be promoted to standalone instances if needed
- This pattern follows the "read/write splitting" best practice for database performance optimization
Comments
Loading comments...