Examkin

Soru

Zorluk: OrtaDatabase and Storage Strategy

A company is designing a new multi-tenant online booking platform that requires a highly available database to handle a read-heavy OLTP workload. The database must automatically fail over to a standby instance in another Availability Zone during an outage to minimize downtime. Additionally, the platform must handle heavy read traffic for reporting dashboards with minimal latency without impacting the performance of the write operations. Which database configuration best meets these requirements?

  1. A
    Deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration. Route write operations to the primary endpoint and configure the application to query the passive standby database instance in the secondary Availability Zone to handle reporting reads.
  2. B
    Deploy a single-AZ Amazon RDS for PostgreSQL database instance. Implement a cron job to take manual database snapshots every hour and restore them to a secondary instance in a separate Availability Zone to serve read traffic and act as a standby.
  3. Deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration, and create one or more RDS Read Replicas in different Availability Zones. Route write operations to the primary endpoint and read-heavy reporting queries to the Read Replica endpoints.Cevap
  4. D
    Deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration encrypted with the default AWS-managed KMS key (aws/rds). Grant the reporting team's AWS account access to query the standby instance directly by updating the KMS key policy.

Cevap

Deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration for high availability and automatic failover, and deploy one or more RDS Read Replicas to serve the read-heavy reporting queries.
Deploying Amazon RDS for PostgreSQL in a Multi-AZ configuration ensures high availability and automatic failover by maintaining a synchronous standby instance in a different Availability Zone. Creating RDS Read Replicas allows read-heavy queries to be offloaded to read-only endpoints, improving overall performance and keeping the primary instance dedicated to write operations.

Adım Adım Çözüm

1
Analyze high availability and failover requirements.
Amazon RDS Multi-AZ deployment is selected to provide synchronous replication to a standby instance and automatic failover capabilities.
The system must minimize downtime and automatically fail over to another Availability Zone in the event of an outage.
2
Analyze the read scalability and latency requirements.
RDS Read Replicas are chosen to scale read capacity horizontally across Availability Zones.
Routing read traffic to Read Replicas offloads the primary database instance, maintaining write performance and reducing read latency.
3
Evaluate the architectural constraints of standby instances and KMS key sharing.
Rule out options that attempt to query the passive standby instance directly or use AWS-managed keys for cross-account resource sharing.
RDS standby instances in Multi-AZ are passive and inaccessible, and AWS-managed KMS keys do not support key policy modifications for cross-account access.

Anahtar Kavram

RDS Multi-AZ vs Read Replicas and cross-account access limitations
Bu soruyu puanla

Konular

Database and Storage Strategy

Bu konudan daha fazla soru