Examkin

Soru

Zorluk: OrtaImproving Database and Caching Efficiency

A real-estate listing portal uses an Amazon RDS for MySQL database to manage property listings and user-saved search preferences. During peak marketing campaigns, users experience high latency when searching for listings due to read-heavy query volumes. Furthermore, the user-saved search preference feature, which requires session state persistence and multi-AZ replication to prevent data loss, is causing write bottlenecks on the primary database instance. Which two actions should the Solutions Architect take to address these performance issues? (Select TWO.)

  1. Deploy an Amazon ElastiCache for Redis cluster with Multi-AZ enabled to store and replicate the user-saved search preferences.Cevap
  2. Create Amazon RDS Read Replicas and configure the application's search module to route read-heavy queries to the read replica endpoints.Cevap
  3. C
    Deploy an Amazon ElastiCache for Memcached cluster to store the user-saved search preferences and enable multi-AZ data replication.
  4. D
    Configure the existing primary Amazon RDS for MySQL database to use a Multi-AZ deployment, and configure the application to route read queries to the standby DB instance endpoint.
  5. E
    Deploy an Amazon ElastiCache for Memcached cluster with a cold standby node in another Availability Zone to store and secure the user-saved search preferences.

Cevap

Deploying an Amazon ElastiCache for Redis cluster with Multi-AZ enabled to store and replicate the user-saved search preferences, and creating Amazon RDS Read Replicas to offload read-heavy queries from the primary database instance.
The correct strategy involves deploying an Amazon ElastiCache for Redis cluster with Multi-AZ enabled and creating Amazon RDS Read Replicas. Using ElastiCache for Redis satisfies the requirement for session state persistence and multi-AZ replication for user-saved search preferences. Creating RDS Read Replicas offloads read-heavy queries from the primary database instance to reduce search latency.

Adım Adım Çözüm

1
Analyze the workload bottleneck and requirements.
Identify that property listing searches are read-heavy, while user-saved search preferences require replication, persistence, and generate write bottlenecks.
This helps determine the distinct caching and replication solutions required for the two different data types.
2
Evaluate the caching solution for the persistent session data.
Choose ElastiCache for Redis with Multi-AZ because it provides persistence, replication, and high availability, which ElastiCache for Memcached lacks.
Ensures that user-saved preferences are not lost during cache failures or failovers.
3
Offload read-heavy queries from the primary RDS database.
Implement RDS Read Replicas and point the search read traffic to the read replica endpoints.
Reduces CPU utilization on the primary RDS instance and resolves latency issues for users executing listing searches.

Anahtar Kavram

Selecting appropriate database caching and scaling technologies based on persistence and read/write requirements.
Tahmini Süre:2m 30s
Bu soruyu puanla

Konular

Improving Database and Caching Efficiency