Examkin

Question

Difficulty: MediumDatabase and Storage Strategy

An enterprise is designing a containerized web application on AWS that will be deployed using Amazon ECS across multiple Availability Zones. The application needs to dynamically process files and requires a shared, POSIX-compliant file system with sub-millisecond latencies for random read/write operations. Additionally, the application metadata must be stored in a relational database that handles high-volume OLTP workloads and supports automatic horizontal read scaling to accommodate traffic bursts. The architecture must achieve a Recovery Time Objective (RTO) of less than 30 minutes and a Recovery Point Objective (RPO) of less than 5 minutes.

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

  1. Use Amazon FSx for NetApp ONTAP to provide the POSIX-compliant shared file system with sub-millisecond latency.Answer
  2. Use Amazon Aurora PostgreSQL with Auto Scaling for Aurora Replicas to scale read capacity.Answer
  3. C
    Use Amazon RDS for PostgreSQL in a Multi-AZ deployment and configure the application to direct read traffic to the standby instance during traffic spikes.
  4. D
    Use Amazon EFS in General Purpose mode with daily backups to satisfy the disaster recovery objectives.
  5. E
    Use Amazon S3 with cross-account replication enabled and an AWS-managed KMS key (aws/s3) to store the shared files and delegate cross-account access.

Answer

Use Amazon FSx for NetApp ONTAP to provide the POSIX-compliant shared file system with sub-millisecond latency, and use Amazon Aurora PostgreSQL with Auto Scaling for Aurora Replicas to scale read capacity.
The correct options are using Amazon FSx for NetApp ONTAP for the shared file system and Amazon Aurora PostgreSQL with auto-scaling replicas. FSx for NetApp ONTAP delivers sub-millisecond latencies and is POSIX-compliant, satisfying the performance and compatibility requirements. Amazon Aurora PostgreSQL with Auto Scaling for Aurora Replicas scales read capacity horizontally in response to traffic demands and natively supports the required low RPO/RTO metrics.

Step-by-Step Solution

1
Evaluate the file storage options against performance and protocol constraints.
Amazon FSx for NetApp ONTAP is selected because it is POSIX-compliant and supports sub-millisecond read/write latencies. Amazon EFS does not consistently meet the sub-millisecond requirement, and Amazon S3 is object storage, not a POSIX file system.
To satisfy the performance and file system constraints of the media application.
2
Evaluate the database and read-scaling requirements.
Amazon Aurora PostgreSQL with Auto Scaling for Aurora Replicas is chosen. Amazon RDS Multi-AZ standby instances cannot serve read requests.
To dynamically scale read operations during traffic bursts for the OLTP metadata database.
3
Verify RTO and RPO objectives for the chosen components.
Both Amazon FSx for NetApp ONTAP and Amazon Aurora PostgreSQL support multi-AZ replication, automated snapshots, and rapid failover mechanisms that easily meet the 30-minute RTO and 5-minute RPO.
To ensure compliance with the disaster recovery requirements.

Key Concept

Selecting high-performance shared file storage and auto-scaling relational database strategies while meeting RTO/RPO limits.
Estimated Time:2m 30s
Rate this question

Topics

Database and Storage Strategy

More questions from this topic