A financial technology company operates a web application that stores active user session tokens and transaction history metadata in a single-instance Amazon RDS for MySQL database. During peak trading hours, read-heavy traffic to the database spikes, causing CPU utilization to reach 95% and leading to transaction delays. The session tokens must be highly available, replicated across Availability Zones, and persisted to prevent users from being logged out in the event of an outage. The Solutions Architect needs to improve database efficiency and reduce query latency. Which combination of actions should the Solutions Architect take to resolve the performance issues? (Select TWO.)
- Deploy Amazon ElastiCache for Redis with replication enabled to store session tokens.Answer
- Create Amazon RDS Read Replicas to offload read queries for transaction history metadata.Answer
- CDeploy Amazon ElastiCache for Memcached to store session tokens and enable multi-AZ replication.
- DEnable Multi-AZ on the RDS instance and configure the application to route read queries to the standby DB instance.
- EPurchase an EC2 Instance Savings Plan to optimize database costs while scaling operations.
Answer
Deploy Amazon ElastiCache for Redis with replication enabled to store session tokens, and create Amazon RDS Read Replicas to offload read queries for transaction history metadata.
The correct solution involves deploying ElastiCache for Redis with replication to handle persistent, highly available session data, and implementing RDS Read Replicas to handle the read-heavy queries for transaction history, directly mitigating the CPU bottleneck on the primary database.
Step-by-Step Solution
Key Concept
Improving database performance and efficiency involves offloading read operations via Read Replicas and shifting transient state storage to highly available in-memory caching solutions.