Examkin

Question

Difficulty: MediumDatabase and Storage Strategy

An enterprise is designing the database and storage strategy for a new containerized web application deployed on AWS across multiple Availability Zones. The application has the following architecture requirements:

* A shared file storage system to store user-uploaded media files. The storage must support standard POSIX file system permissions and allow concurrent read and write access from Linux containers running in multiple Availability Zones.
* A database tier that handles high-volume OLTP transactions, scales read operations horizontally with minimum replication lag, and supports automatic failover with low RTO.

Which two database and storage configurations should the solutions architect choose to meet these requirements? (Select TWO.)

  1. Amazon Elastic File System (Amazon EFS) to provide shared, elastic file storage accessible concurrently by Linux containers across multiple Availability Zones.Answer
  2. Amazon Aurora MySQL with Auto Scaling for Aurora Replicas to scale read queries horizontally and provide low-latency failover.Answer
  3. C
    Amazon RDS Multi-AZ deployment configured to serve read queries directly from the secondary standby database instance to scale read capacity.
  4. D
    A multi-Region database setup utilizing a pilot light disaster recovery pattern to achieve near-zero Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for the database layer.
  5. E
    An Amazon EFS file system encrypted with the AWS-managed KMS key (aws/elasticfilesystem) to allow cross-account access via a modified key policy.

Answer

The correct configurations are using Amazon Elastic File System (Amazon EFS) to provide shared, POSIX-compliant file storage across multiple Availability Zones, and using Amazon Aurora MySQL with Auto Scaling for Aurora Replicas to scale read queries horizontally with low latency and support automatic failover.
The correct configurations are Amazon Elastic File System (Amazon EFS) and Amazon Aurora MySQL with Auto Scaling for Aurora Replicas. Amazon EFS natively supports the NFSv4 protocol and standard POSIX permissions, enabling concurrent read and write access for Linux containers across multiple Availability Zones. Amazon Aurora MySQL provides horizontal read scaling with low replication lag using Aurora Replicas and supports rapid automatic failover, meeting the database tier requirements.

Step-by-Step Solution

1
Identify the shared storage requirements.
Amazon EFS is selected because it supports the NFSv4 protocol, POSIX file permissions, and concurrent read/write access from Linux containers across multiple Availability Zones.
Linux containers require a shared filesystem that respects standard file permissions and allows simultaneous writes.
2
Evaluate the database tier requirements.
Amazon Aurora MySQL with Aurora Replicas and Auto Scaling is chosen.
Aurora Replicas provide horizontal read scaling with low replication lag (usually sub-100ms) and serve as rapid failover targets to minimize RTO.
3
Analyze and eliminate incorrect options.
RDS Multi-AZ standbys cannot serve read traffic; pilot light patterns do not achieve near-zero RTO/RPO; and AWS-managed KMS keys cannot be shared cross-account.
Ensures that constraints around read scaling, recovery objectives, and encryption key sharing are not violated.

Key Concept

Selecting appropriate AWS storage and database services based on protocol support (POSIX/NFS), read scaling capability, replication behavior, and access delegation constraints.
Rate this question

Topics

Database and Storage Strategy

More questions from this topic