Soru

Zorluk: OrtaImproving Database and Caching Efficiency

A SaaS-based marketing automation platform stores tenant campaign configurations in a single-instance Amazon RDS for PostgreSQL database. During peak campaign execution windows, read query volume increases significantly, causing the database CPU utilization to exceed 90% and campaign delivery latencies to rise. The Solutions Architect must implement a caching solution to reduce the database load. The cached configuration data must survive cache node failures without causing a cache miss storm on the database, and the cache layer must support automatic failover. Which of the following caching strategies should the Solutions Architect implement to meet these requirements?

  1. Deploy an Amazon ElastiCache for Redis cluster in a Multi-AZ replication group with automatic failover enabled, and configure the application to read from the cache before querying the database.Cevap
  2. B
    Deploy an Amazon ElastiCache for Memcached cluster across multiple Availability Zones, and configure the application to cache campaign configurations to distribute the read load.
  3. C
    Modify the RDS for PostgreSQL database to a Multi-AZ deployment, and configure the application to route marketing campaign read queries to the standby database instance.
  4. D
    Create an Amazon Aurora PostgreSQL Global Database secondary cluster in another AWS Region, and configure the application to route read queries to the secondary region to distribute the query load.

Cevap

Deploy an Amazon ElastiCache for Redis cluster in a Multi-AZ replication group with automatic failover enabled, and configure the application to read from the cache before querying the database.
The correct solution uses Amazon ElastiCache for Redis with Multi-AZ replication. This pattern offloads read queries from the backend database, handles failover automatically to prevent cache stampedes, and ensures cache availability.

Adım Adım Çözüm

1
Analyze performance metrics to identify database CPU bottleneck.
Determine that the database is read-heavy on campaign configuration data.
Validates the need for caching rather than write-scaling options.
2
Evaluate caching requirements for high availability and automatic failover.
Establish that the cache must survive node outages without cache stampedes.
Filters out caching engines that lack replication and failover support.
3
Select the appropriate Amazon ElastiCache engine.
ElastiCache for Redis is selected over Memcached.
Redis supports Multi-AZ replication and automatic failover, whereas Memcached is a simple, non-replicated partitioning engine.

Anahtar Kavram

Improving database efficiency by using an ElastiCache Redis cluster with Multi-AZ replication for resilient caching.
Bu soruyu puanla