Examkin

Soru

Zorluk: OrtaDatabase and Storage Strategy

A company is designing a new financial reporting platform. The platform requires a database to handle a bursty OLTP transaction history workload with dynamic, auto-scaling read capability. For caching, the application requires sub-key eviction, persistence, and Multi-AZ replication. Finally, financial reports must be exported to an Amazon S3 bucket located in a separate, dedicated audit AWS account. These exports must be encrypted at rest using key material controlled by the company, and the audit account must have permissions to immediately read the files. Which two database and storage configurations should a Solutions Architect select to satisfy these requirements?

  1. Deploy an Amazon Aurora PostgreSQL DB cluster with Auto Scaling enabled for Aurora Replicas to handle read traffic spikes, and provision Amazon ElastiCache for Redis with Multi-AZ enabled for caching.Cevap
  2. Configure the S3 bucket to use server-side encryption with AWS KMS Customer Managed Keys (SSE-KMS), and configure cross-account access by updating both the S3 bucket policy and the KMS key policy in the primary account.Cevap
  3. C
    Deploy an Amazon RDS for PostgreSQL DB instance in a Multi-AZ deployment and configure the standby replica to serve read traffic during query bursts, alongside Amazon ElastiCache for Memcached.
  4. D
    Store the reporting exports in the audit S3 bucket encrypted with the AWS-managed KMS key for Amazon S3 (aws/s3), and configure cross-account access by modifying the default KMS policy to trust the audit account.
  5. E
    Deploy an Amazon Aurora PostgreSQL DB cluster with Multi-AZ, and configure Amazon ElastiCache for Memcached to provide persistent caching and sub-key eviction controls.

Cevap

Deploying an Amazon Aurora PostgreSQL DB cluster with Auto Scaling for Aurora Replicas alongside Amazon ElastiCache for Redis, and encrypting the S3 exports using Customer Managed Keys (CMKs) with appropriate cross-account policies.
The correct configurations involve using Amazon Aurora PostgreSQL because Aurora Replicas can serve reads and auto-scale dynamically, and Amazon ElastiCache for Redis because it satisfies the persistence and sub-key eviction requirements. For S3 encryption, using a Customer Managed Key (CMK) with SSE-KMS is necessary for cross-account S3 access because AWS-managed keys cannot be shared cross-account, and both S3 bucket policies and key policies must explicitly permit access.

Adım Adım Çözüm

1
Select the appropriate database and caching engines.
Amazon Aurora PostgreSQL with auto-scaled Aurora Replicas is selected for handling bursty OLTP read workloads. Amazon ElastiCache for Redis is selected to fulfill persistence, replication, and sub-key eviction requirements.
Aurora Replicas, unlike RDS Multi-AZ standby instances, can actively serve read traffic and auto-scale. Redis supports persistence and sub-key eviction, which Memcached does not.
2
Determine the S3 encryption and cross-account access mechanism.
An S3 bucket is configured with SSE-KMS using a Customer Managed Key (CMK), with policies updated to grant cross-account access.
AWS-managed KMS keys (like aws/s3) cannot be shared across accounts. A customer-managed CMK must be used, and its key policy along with the S3 bucket policy must allow access to the external audit account.

Anahtar Kavram

Selecting appropriate database replication and caching mechanisms, and configuring secure cross-account storage encryption.
Bu soruyu puanla

Konular

Database and Storage Strategy

Bu konudan daha fazla soru