Soru

Zorluk: OrtaDatabase and Storage Strategy

A solutions architect is designing a new high-frequency transaction processing application that requires a relational database. The database must support an unpredictable read workload that surges during marketing campaigns, needing auto-scaling read capacity. Additionally, the system must achieve high availability with an automatic failover recovery time objective (RTO) of less than 30 seconds. Which database and storage strategy meets these requirements with the least operational overhead?

  1. Deploy an Amazon Aurora PostgreSQL DB cluster with a primary instance and an Aurora Replica in a different Availability Zone. Configure Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas based on CPU utilization.Cevap
  2. B
    Deploy an Amazon RDS for PostgreSQL DB instance with a Multi-AZ deployment. Configure the standby DB instance to serve read traffic during high CPU utilization, and enable RDS storage auto-scaling.
  3. C
    Deploy a Single-AZ Amazon RDS for PostgreSQL DB instance. Configure cross-Region read replicas, and implement a script that manually promotes a replica to primary and updates application connection strings when the primary instance fails.
  4. D
    Deploy an Amazon Aurora PostgreSQL DB cluster in a Multi-AZ configuration encrypted with the AWS-managed KMS key (aws/rds). Share the database snapshots with a separate security audit account by modifying the key policy of the AWS-managed KMS key to delegate cross-account access.

Cevap

Deploy an Amazon Aurora PostgreSQL DB cluster with a primary instance and an Aurora Replica in a different Availability Zone. Configure Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas based on CPU utilization.
The correct strategy uses Amazon Aurora PostgreSQL with an Aurora Replica in another Availability Zone. This architecture ensures high availability with automatic failover (typically completed within 30 seconds) and scales read operations dynamically using Aurora Auto Scaling based on target CPU utilization metrics.

Adım Adım Çözüm

1
Analyze high availability and failover requirements.
An RTO of less than 30 seconds requires an automated failover mechanism. Amazon Aurora DB clusters automatically fail over to an existing replica in a different Availability Zone within 30 seconds, whereas Amazon RDS Multi-AZ failovers can take 1-2 minutes.
Ensures the database strategy matches the strict RTO target.
2
Analyze read scaling requirements.
Unpredictable read workloads require horizontal read scaling. Aurora Replicas can handle read queries, and Aurora Auto Scaling dynamically provisions and terminates replicas based on CPU utilization target tracking.
Allows the architecture to handle surges in read traffic automatically.
3
Validate security and integration constraints.
The correct strategy must utilize Customer Managed Keys (CMKs) if cross-account sharing is needed, but for the basic setup, deploying Aurora with Aurora Auto Scaling is the only choice that satisfies both high availability failover and dynamic read scaling without custom scripting.
Confirms the operational feasibility and compliance of the chosen option.

Anahtar Kavram

Amazon Aurora provides rapid automated failover to replicas and supports dynamic horizontal scaling of read capacity via Aurora Auto Scaling, whereas standard RDS standby instances cannot serve read traffic.
Tahmini Süre:2m 0s
Bu soruyu puanla