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?
- 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
- 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
- CDeploy 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.
- DImplement 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.
- EEncrypt 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.