Examkin

Soru

Zorluk: OrtaResilient Database Configurations and High Availability

A retail company runs a web application on AWS that uses an Amazon RDS for MySQL database. During peak shopping periods, the database experiences high volumes of read queries for generating inventory reports, which leads to performance degradation for transactional write operations. A solutions architect must redesign the database tier to be highly available within a single AWS Region with a recovery time objective (RTO) of less than 60 seconds. Additionally, the solution must offload the inventory reporting queries to scale read capacity independently.

Which TWO configurations should the solutions architect implement to meet these requirements? (Select TWO.)

  1. Deploy the RDS for MySQL database as a Multi-AZ DB instance deployment.Cevap
  2. Create one or more RDS read replicas in different Availability Zones and update the reporting application to use the read replica endpoints.Cevap
  3. C
    Configure RDS read replicas as the failover target and use custom scripts to promote them to the primary database when the main instance is unavailable.
  4. D
    Deploy a warm standby RDS DB instance in a secondary AWS Region to handle automatic write failover during an Availability Zone outage.
  5. E
    Configure an Amazon Route 53 latency routing policy to distribute write requests directly to the read replicas during failover events.

Cevap

The solutions architect should deploy the database as an Amazon RDS Multi-AZ DB instance deployment to achieve automatic high availability and failover, and create RDS read replicas to offload inventory reporting queries.
To meet the low Recovery Time Objective (RTO) of less than 60 seconds within a single Region, the primary database must be configured with an Amazon RDS Multi-AZ DB instance deployment. This setup automatically replicates data synchronously to a standby instance in a different Availability Zone and performs automatic failover in the event of an outage. To scale read capacity independently and offload read-heavy reporting queries, the architect should deploy RDS read replicas and route read traffic to their endpoints, which prevents write operations on the primary DB instance from being degraded.

Adım Adım Çözüm

1
Analyze the high availability and recovery time objective (RTO) constraints.
An Amazon RDS Multi-AZ DB instance deployment provides automatic failover within a single Region, typically taking less than 60 seconds, meeting the RTO requirement.
Multi-AZ DB instances provide synchronous replication and automatic failover, which is required for high availability.
2
Analyze the read scaling requirements to offload analytics traffic from write operations.
Creating one or more RDS read replicas allows read-heavy queries to be routed to dedicated replica endpoints.
Read replicas utilize asynchronous replication to scale read workloads independently of the primary write database.
3
Evaluate and eliminate incorrect configurations that violate high availability or read scalability rules.
Discard manual failover configurations, multi-region database strategies that lack automatic failover, and options using read replicas as write targets.
These configurations violate regional high-availability constraints, Route 53 capabilities, and read-replica write limitations.

Anahtar Kavram

High availability via Multi-AZ deployments and read scaling via Read Replicas in Amazon RDS.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Resilient Database Configurations and High Availability

Bu konudan daha fazla soru