Question

Difficulty: MediumDatabase and Storage Strategy

A media production company is building a document collaboration platform that manages transactional metadata (OLTP workload) and shared creative files (File storage workload). The file system must scale to handle millions of small, frequently accessed media assets while maintaining POSIX compliance, and must be replicated to a secondary AWS region with a Recovery Point Objective (RPO) of less than 15 minutes. Additionally, the metadata database must support high-performance transactional updates in the primary region, while providing read capabilities in the secondary region for reporting queries with replication latency under 1 second. Which two strategies should the solutions architect select to meet these requirements?

  1. Deploy Amazon EFS file systems in both the primary and secondary regions, and configure Amazon EFS Replication to copy data to the destination file system.Answer
  2. Provision an Amazon Aurora Global Database with the primary database cluster in the primary region and a secondary database cluster in the backup region to serve reporting queries.Answer
  3. C
    Deploy Amazon EFS in the primary region and create a scheduled AWS Backup job to replicate backups to a backup vault in the secondary region every 12 hours.
  4. D
    Configure an Amazon RDS for PostgreSQL database with a Multi-AZ deployment, and configure the standby DB instance in the secondary Availability Zone to serve read traffic for reporting queries.
  5. E
    Deploy Amazon ElastiCache for Memcached with multi-AZ replication enabled across both regions to cache database query results and media asset metadata.

Answer

The solutions architect should deploy Amazon EFS file systems in both regions with EFS Replication configured, and provision an Amazon Aurora Global Database with a secondary read cluster in the backup region.
To satisfy the POSIX-compliant file storage requirement with an RPO of less than 15 minutes, the architecture must use Amazon Elastic File System (EFS) with Amazon EFS Replication. EFS Replication replicates file system data to another AWS Region continuously with an RPO of minutes. To support transactional OLTP metadata with secondary region reads and sub-second latency, Amazon Aurora Global Database is the ideal choice. Aurora Global Database uses dedicated storage replication to duplicate data to secondary regions with a latency of less than 1 second, and the secondary cluster can actively serve read queries.

Step-by-Step Solution

1
Analyze the file storage requirements: POSIX compliance, millions of files, and a cross-region RPO of less than 15 minutes.
Determine that Amazon EFS provides POSIX compliance and scales to millions of files, and EFS Replication satisfies the RPO requirement since it operates continuously and typically replicates data in minutes.
Standard backup mechanisms like AWS Backup scheduled at 12-hour intervals cannot meet the strict 15-minute RPO target.
2
Analyze the database requirements: high-performance OLTP transactional updates, secondary region reads, and replication lag under 1 second.
Identify Amazon Aurora Global Database as the correct solution because it utilizes storage-based replication to replicate data to secondary regions with a typical latency of less than 1 second.
Amazon RDS Multi-AZ standby instances are passive and cannot accept read connections, and ElastiCache for Memcached lacks the required replication and persistence capabilities.

Key Concept

Selecting multi-region storage and database replication strategies to meet POSIX compliance, RPO, and read performance targets.
Estimated Time:2m 0s
Rate this question