Soru

Zorluk: OrtaDatabase and Storage Strategy

A financial technology company is designing a new high-throughput transaction processing application. The solutions architect must design the database and storage tier to meet the following requirements:

* A relational database to store account balances. The database must automatically scale read capacity during high-traffic events, support automatic failover across multiple Availability Zones, and meet a near-zero RTO and RPO for regional disaster recovery.
* A shared file system to store application configuration files. The file system must be concurrently accessible by multiple Amazon EC2 instances across multiple Availability Zones.
* All data at rest must be encrypted, and the encryption keys must be managed in a way that allows cross-account access for the security auditing team.

Which two configurations should the solutions architect select to meet these requirements?

  1. Deploy an Amazon Aurora PostgreSQL DB cluster with Aurora Replicas, configure Aurora Auto Scaling to dynamically adjust read capacity, and set up an Aurora Global Database using a Customer Managed Key (CMK) for encryption.Cevap
  2. Create an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class and mount it on the Amazon EC2 instances in each Availability Zone.Cevap
  3. C
    Deploy an Amazon RDS for PostgreSQL DB instance with a Multi-AZ standby deployment, and route read queries to the standby instance to scale reads during traffic spikes.
  4. D
    Implement a Pilot Light disaster recovery strategy for the relational database by scheduling weekly database snapshots and copying them to a secondary Region to minimize costs.
  5. E
    Encrypt the database storage using the default AWS-managed KMS key (aws/rds) and modify its key policy to grant decrypt permissions to the security auditing account.

Cevap

Deploy an Amazon Aurora PostgreSQL DB cluster with Aurora Replicas, configure Aurora Auto Scaling, and set up an Aurora Global Database using a Customer Managed Key (CMK). Create an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class.
Deploying an Amazon Aurora PostgreSQL DB cluster with Aurora Replicas and Auto Scaling provides high availability and dynamic read scaling. Aurora Global Database ensures cross-region disaster recovery with near-zero RTO and RPO. Furthermore, using a Customer Managed Key (CMK) allows configuring key policies to share access across accounts. Amazon EFS provides a shared file system that can be mounted concurrently by EC2 instances across multiple Availability Zones, which matches the storage requirement for configuration files.

Adım Adım Çözüm

1
Select the database engine and scaling strategy.
Amazon Aurora PostgreSQL with Aurora Replicas and Auto Scaling is chosen to handle local read spikes and failover.
Amazon RDS Multi-AZ standby instances do not support read traffic, whereas Aurora Replicas can be dynamically scaled to handle read queries.
2
Select the disaster recovery and encryption method for the database.
Aurora Global Database with Customer Managed Key (CMK) encryption is selected.
Aurora Global Database meets the near-zero RTO/RPO requirements, and CMKs are required because default AWS-managed KMS keys cannot be shared with external accounts.
3
Select the shared storage class for the configuration files.
Amazon Elastic File System (Amazon EFS) with EFS Standard storage class is selected.
Amazon EFS natively supports concurrent read/write mounts from multiple EC2 instances across multiple Availability Zones, unlike EBS volumes which cannot span AZs for multi-attach.

Anahtar Kavram

Selecting database and storage solutions that satisfy performance (read scaling, concurrent multi-AZ access), security (cross-account KMS key sharing), and reliability (RTO/RPO) requirements.
Bu soruyu puanla