A biotechnology enterprise is designing a genomics research pipeline (File storage and OLT… — AWS Certified Solutions Architect - Professional

A biotechnology enterprise is designing a genomics research pipeline (File storage and OLTP workloads) that runs on Amazon EC2 instances across multiple Availability Zones in a single AWS Region. The pipeline has the following requirements:

- A shared file system that is POSIX-compliant, supports concurrent access from hundreds of EC2 instances, and scales throughput dynamically up to $3\text{ GB/s}$ during peak sequencing phases.
- A metadata database that must handle high-volume write and read queries with low latency.
- High availability with a Recovery Time Objective (RTO) of under $5\text{ minutes}$ and a Recovery Point Objective (RPO) of under $1\text{ minute}$ in the event of an Availability Zone outage.
- Securely share final sequencing output files, stored in Amazon S3, with a separate audit AWS account.

Which of the following database and storage strategies meets these requirements?

Deploy Amazon EFS with Elastic throughput for the shared file system. Deploy an Amazon Aurora PostgreSQL DB cluster with a writer instance and one or more Aurora Replicas across different Availability Zones, and configure Aurora Auto Scaling for the reader instances. Encrypt the S3 buckets for the sequencing output using an AWS KMS Customer Managed Key (CMK) and configure the key policy to allow access from the audit AWS account.Cevap
B
Deploy Amazon EFS with Elastic throughput for the shared file system. Deploy an Amazon RDS for PostgreSQL DB instance with a Multi-AZ deployment, and configure the application to route read queries to the standby replica to handle dynamic read scaling. Encrypt the S3 buckets using an AWS KMS Customer Managed Key (CMK) and configure the key policy to allow access from the audit AWS account.
C
Deploy Amazon EFS with Elastic throughput for the shared file system. Deploy an Amazon Aurora PostgreSQL DB cluster with a writer instance and one or more Aurora Replicas across different Availability Zones, and configure Aurora Auto Scaling for the reader instances. Encrypt the S3 buckets using the default AWS-managed KMS key (aws/s3) and configure the S3 bucket policy to grant read access to the audit AWS account.
D
Deploy Amazon EBS volumes with Multi-Attach enabled across the EC2 instances in different Availability Zones for the shared file system. Deploy an Amazon Aurora PostgreSQL DB cluster with a single writer instance, schedule daily DB snapshots, and copy them to the audit AWS account to satisfy disaster recovery and audit sharing requirements.

Cevap

Deploy Amazon EFS with Elastic throughput for the shared file system. Deploy an Amazon Aurora PostgreSQL DB cluster with a writer instance and Aurora Replicas across multiple Availability Zones with Auto Scaling. Use an AWS KMS Customer Managed Key (CMK) for cross-account S3 sharing.

The strategy using Amazon EFS with Elastic throughput satisfies the file storage requirements because it natively supports multi-AZ concurrent POSIX access and can scale throughput dynamically. Amazon Aurora PostgreSQL with Aurora Replicas and Auto Scaling provides high-performance reads and writes with failover times well under

5\text{ minutes}

and replication lag under

1\text{ minute}

. Finally, using a Customer Managed Key (CMK) allows updating the KMS key policy to permit the external audit account to decrypt objects, which is not possible with AWS-managed keys.

Adım Adım Çözüm

Select the appropriate shared storage service.

Amazon EFS with Elastic throughput is selected because it supports POSIX compliance, concurrent access from hundreds of EC2 instances across multiple Availability Zones, and scales dynamically to handle

3\text{ GB/s}

throughput.

Alternative storage options like EBS Multi-Attach are confined to a single Availability Zone and cannot support Multi-AZ high availability.

Determine the database configuration that meets the RTO/RPO constraints.

An Amazon Aurora DB cluster with a primary writer and one or more reader replicas is chosen.

Aurora failover takes less than

120\text{ seconds}

(meeting the RTO of

5\text{ minutes}

) and uses synchronous physical replication within the cluster storage volume with near-zero replica lag (meeting the RPO of

1\text{ minute}

). Standard RDS Multi-AZ standbys cannot serve read traffic to handle scale.

Configure encryption and cross-account access for the shared S3 bucket.

Use an AWS KMS Customer Managed Key (CMK) for encryption and modify its key policy to grant decrypt permissions to the external audit account.

The default AWS-managed KMS key (aws/s3) cannot be shared across accounts as its key policy is immutable.

Anahtar Kavram

Designing highly available, scalable database and shared storage architectures that support strict RTO/RPO targets and secure cross-account resource sharing.

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular

Bu konudan daha fazla soru