Examkin

Soru

Zorluk: OrtaDatabase and Storage Strategy

A solutions architect is designing a storage and database architecture for a new financial auditing application (OLTP workload). The application will run in a primary AWS account and must access audit logs and transaction history stored in an Amazon S3 bucket in a centralized security account. The architecture must satisfy the following requirements:

1. The transaction ledger database requires a highly available, MySQL-compatible relational database with a recovery point objective (RPO) of 0 and a recovery time objective (RTO) of less than 60 seconds. High read throughput must be supported by dynamically scaling read capacity during end-of-month reporting.
2. The audit logs in S3 must be encrypted at rest, and the primary account's application role must be able to read and write to the central S3 bucket.
3. A low-latency session caching layer must support replication across multiple Availability Zones to prevent session loss if a primary cache node fails.

Which of the following database, caching, and storage designs meets these requirements?

  1. A
    Configure Amazon Aurora MySQL with a Multi-AZ deployment and Aurora Replica Auto Scaling for the database. Encrypt the central S3 bucket using a Customer Managed Key (CMK) in AWS KMS, and configure the key policy and S3 bucket policy to allow the primary account's IAM role access. Deploy Amazon ElastiCache for Memcached with multi-AZ replication nodes to handle the session caching layer.
  2. B
    Configure Amazon Aurora MySQL with a Multi-AZ deployment and Aurora Replica Auto Scaling for the database. Encrypt the central S3 bucket using the AWS-managed KMS key for S3 (aws/s3), and configure the S3 bucket policy in the security account to delegate access to the primary account's IAM role. Deploy Amazon ElastiCache for Redis with Multi-AZ enabled to handle the session caching layer.
  3. Configure Amazon Aurora MySQL with a Multi-AZ deployment and Aurora Replica Auto Scaling for the database. Encrypt the central S3 bucket using a Customer Managed Key (CMK) in AWS KMS, and configure both the KMS key policy and the S3 bucket policy to grant cross-account permissions to the primary account's IAM role. Deploy Amazon ElastiCache for Redis with Multi-AZ enabled to handle the session caching layer.Cevap
  4. D
    Configure Amazon RDS for MySQL with a Multi-AZ deployment, and configure auto-scaling to direct reporting query traffic to the standby instance during periods of high read demand. Encrypt the central S3 bucket using a Customer Managed Key (CMK) in AWS KMS, and configure both the KMS key policy and the S3 bucket policy to grant cross-account permissions to the primary account's IAM role. Deploy Amazon ElastiCache for Redis with Multi-AZ enabled to handle the session caching layer.

Cevap

The correct design configures Amazon Aurora MySQL with Aurora Replica Auto Scaling, encrypts the S3 bucket using a Customer Managed Key (CMK) with appropriate cross-account permissions, and deploys Amazon ElastiCache for Redis with Multi-AZ.
The correct design uses Amazon Aurora MySQL because its Multi-AZ architecture supports rapid failover (RTO < 60s) with zero data loss (RPO = 0), and Aurora Auto Scaling dynamically scales read replicas to handle reporting loads. For cross-account access to encrypted S3 buckets, a Customer Managed Key (CMK) is required because AWS-managed keys (like aws/s3) cannot be shared across accounts via key policies. Amazon ElastiCache for Redis supports replication and automatic failover across Availability Zones, which prevents session loss upon node failure.

Adım Adım Çözüm

1
Evaluate database requirements for MySQL compatibility, RPO of 0, RTO under 60 seconds, and dynamic read scaling.
Amazon Aurora MySQL with Multi-AZ and Aurora Replica Auto Scaling is selected.
Aurora's active-active storage layer replication enables rapid failover under 60 seconds with no data loss, and read replicas can auto-scale horizontally to offload reporting queries.
2
Determine the encryption and cross-account access mechanism for the S3 bucket.
Select a Customer Managed Key (CMK) in AWS KMS and configure a cross-account key policy.
AWS-managed keys (like aws/s3) do not support policy modification and cannot be shared across accounts. A CMK allows explicitly granting decrypt/encrypt permissions to the primary account.
3
Select the session caching layer that supports low latency and multi-AZ replication.
Amazon ElastiCache for Redis with Multi-AZ is selected.
ElastiCache for Redis supports replication, data persistence, and automatic failover across Availability Zones to prevent session loss, whereas Memcached does not support replication.

Anahtar Kavram

Selecting and integrating appropriate AWS database, cache, and storage services under strict high-availability, scaling, and cross-account security constraints.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Database and Storage Strategy

Bu konudan daha fazla soru