Design Resilient Architectures

382 questions

Question 21Question

A company hosts its static website assets in an Amazon S3 bucket located in the us-east-1 Region. To ensure high availability and resiliency, the company replicates these assets to a secondary S3 bucket in the us-west-2 Region. A solutions architect needs to configure Amazon CloudFront to deliver these assets with low latency and automatically serve files from the backup S3 bucket if the primary S3 bucket returns an HTTP 503 Service Unavailable error. Which configuration should the solutions architect use to meet these requirements?

Show answer & explanation

Answer: Configure a CloudFront origin group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin, selecting the 503 status code in the failover criteria.

Answer

Configure a CloudFront origin group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin, selecting the 503 status code in the failover criteria.
Configuring a CloudFront origin group provides a native, seamless way to implement high availability for static content. By setting up an origin group with a primary S3 bucket and a failover S3 bucket, CloudFront automatically retries the request against the secondary origin when the primary origin returns specific HTTP status codes such as 503.

Step-by-Step Solution

1
Identify the primary requirement for origin failover and low-latency content delivery.
Amazon CloudFront is selected as the content delivery network (CDN) to cache content at edge locations.
CloudFront caches content globally to reduce latency for end users.
2
Configure high availability for the S3 origin within CloudFront.
Create a CloudFront origin group containing both S3 buckets as origins.
An origin group is the native CloudFront feature designed to handle failover between two origins.
3
Define failover conditions for the origin group.
Specify the 503 HTTP status code as a trigger to failover from the primary bucket to the secondary bucket.
This ensures that if the primary S3 bucket experiences issues and returns a 503 error, CloudFront automatically retrieves the requested asset from the backup bucket without impacting the client.

Key Concept

CloudFront Origin Groups and Origin Failover
Estimated Time:50s
Question 22Question

An international logistics provider runs a critical tracking application using Amazon RDS for PostgreSQL in the us-east-1 Region. The company requires a disaster recovery (DR) solution in the us-west-2 Region with a Recovery Point Objective (RPO) of less than 5 minutes and a Recovery Time Objective (RTO) of less than 15 minutes. Additionally, the secondary region must serve read-only reporting workloads during normal operations to offload the primary database. Which combination of actions will meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create a cross-region read replica of the primary database in the us-west-2 Region.; Promote the cross-region read replica to a standalone DB instance in the us-west-2 Region during a disaster recovery event, and update the application connection settings.

Answer

To meet the requirements, the company should create a cross-region read replica in the secondary region to handle reporting workloads and maintain low replication lag, and then promote that replica to a standalone DB instance during a DR event.
The correct actions are to create a cross-region read replica in the secondary region and to promote this replica to a standalone instance during a failover. The cross-region read replica satisfies the RPO of less than 5 minutes due to continuous asynchronous replication and allows read-only reporting queries to run in the secondary region. Promoting the read replica takes only a few minutes, which satisfies the 15-minute RTO.

Step-by-Step Solution

1
Select a replication method that meets the RPO and read workload requirements.
Creating an Amazon RDS cross-region read replica provides near-continuous asynchronous replication (meeting the 5-minute RPO) and can serve read-only reporting traffic during normal operations.
Asynchronous replication to a read replica offloads reads and replicates changes without synchronous write latency across regions.
2
Select a failover method that meets the 15-minute RTO requirement.
Promoting the read replica to a standalone instance takes only a few minutes.
Promoting an existing read replica is significantly faster than restoring from backups or setting up new instances, keeping RTO well under the 15-minute threshold.
3
Identify and eliminate options that are technically impossible or violate constraints.
Eliminated Multi-AZ spanning regions (not supported), Route 53 database promotion (DNS only), and 4-hour backup restore (violates RPO).
Multi-AZ is single-region, Route 53 cannot perform database operations, and snapshot restores from 4-hour intervals violate the RPO constraint.

Key Concept

Cross-Region Disaster Recovery using RDS Read Replicas
Question 23Question

A global agricultural logistics company is migrating its telemetry archiving system to AWS. The system must store critical supply chain data with an RPO of 1515 minutes and an RTO of 3030 minutes. The architecture must ensure the data is resilient to regional disasters and remains immediately readable from a secondary destination region for localized reporting. Which two configurations should the solutions architect combine to meet these resilience and recovery requirements?

Select all that apply

Show answer & explanation

Answer: Configure Amazon S3 Cross-Region Replication (CRR) to automatically copy telemetry data to a destination bucket in the secondary region.; Enable S3 Replication Time Control (RTC) on the replication rule configured for the telemetry data bucket.

Answer

To meet the requirements, the solutions architect should configure Amazon S3 Cross-Region Replication (CRR) to copy telemetry data to the destination bucket and enable S3 Replication Time Control (RTC) to ensure replication is completed within the 1515-minute RPO.
Configuring Amazon S3 Cross-Region Replication (CRR) copies objects to a secondary region automatically, keeping the data immediately readable. Enabling S3 Replication Time Control (RTC) enforces replication within 1515 minutes, satisfying the 1515-minute RPO requirement.

Step-by-Step Solution

1
Select the appropriate storage service for storing raw telemetry objects across regions.
Amazon S3 with Cross-Region Replication (CRR) is selected, ensuring durability and cross-region disaster recovery.
This establishes a replicated object repository that supports immediate, active read access in the destination region.
2
Configure Replication Time Control (RTC) on the S3 replication rule.
RTC guarantees that 99.99%99.99\% of objects replicate within 1515 minutes.
This configuration directly aligns with the strict RPO constraint of 1515 minutes.

Key Concept

Amazon S3 Cross-Region Replication with Replication Time Control (RTC) to guarantee strict RPO/RTO constraints.
Question 24Question

A digital ticketing platform plans to migrate its database to Amazon Aurora MySQL. The database must sustain high availability during an Availability Zone outage with a recovery time objective (RTO) of less than 60 seconds and zero data loss (recovery point objective or RPO of 0). In addition, the database must dynamically scale to support a large, unpredictable volume of read queries. Which two configurations should a solutions architect implement to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy the database as an Amazon Aurora cluster with a primary instance and one or more Aurora Replicas in different Availability Zones.; Configure the application to use the Aurora reader endpoint and enable Aurora Auto Scaling for the reader instances.

Answer

Deploy the database as an Amazon Aurora cluster with a primary instance and Aurora Replicas in different Availability Zones, and configure the application to use the Aurora reader endpoint while enabling Aurora Auto Scaling.
Deploying the database as a Multi-AZ Amazon Aurora cluster with replicas in multiple Availability Zones ensures that if the primary instance fails, Aurora automatically promotes a replica within 30 seconds with no data loss because all replicas share the cluster's distributed storage volume. Routing read traffic to the reader endpoint and enabling Aurora Auto Scaling ensures the database dynamically handles spikes in read queries by automatically scaling the number of read replicas.

Step-by-Step Solution

1
Analyze high availability (RTO/RPO) requirements.
Identified that RTO must be under 60 seconds and RPO must be 0 (no data loss) in case of an Availability Zone outage.
This necessitates automatic failover and synchronous-like storage replication within the region.
2
Evaluate the database deployment model.
Selecting a Multi-AZ cluster deployment with Aurora Replicas across different Availability Zones guarantees automatic failover and shared storage replication.
Aurora storage is automatically replicated across three Availability Zones. Failover to an Aurora Replica in another AZ takes less than 30 seconds.
3
Analyze the read scaling requirements.
Determined that read scaling must be dynamic and handled automatically.
By connecting the application to the reader endpoint and configuring Aurora Auto Scaling, instances are provisioned or terminated dynamically to handle load changes.

Key Concept

High Availability and Read Scaling in Amazon Aurora
Question 25Question

A healthcare software provider is deploying a critical patient portal application on AWS. The application database tier requires high availability within the primary Region (us-east-1) to survive the loss of an Availability Zone with a Recovery Time Objective (RTO) of under 60 seconds. Additionally, the provider requires a cross-region disaster recovery (DR) solution in the us-west-2 Region with a Recovery Point Objective (RPO) of under 1 minute and a Recovery Time Objective (RTO) of under 15 minutes. Which combination of database configurations will meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy an Amazon Aurora PostgreSQL DB cluster in us-east-1 with at least one Aurora Replica in a different Availability Zone.; Use Amazon Aurora Global Databases to replicate data from us-east-1 to a secondary Aurora DB cluster in us-west-2.

Answer

Deploy an Amazon Aurora PostgreSQL DB cluster in us-east-1 with at least one Aurora Replica in a different Availability Zone, and use Amazon Aurora Global Databases to replicate data from us-east-1 to a secondary Aurora DB cluster in us-west-2.
Deploying an Amazon Aurora DB cluster with an Aurora Replica in a different Availability Zone provides automatic failover in under 30 seconds, satisfying the regional high availability RTO requirement of under 60 seconds. Combining this with Amazon Aurora Global Databases allows storage-level, low-latency replication to a secondary Region with a lag of less than 1 second (satisfying the 1-minute RPO) and enabling promotion of the secondary cluster in less than 1 minute (satisfying the 15-minute RTO).

Step-by-Step Solution

1
Analyze the regional high availability constraint (RTO < 60 seconds in us-east-1).
Identify that a Multi-AZ deployment is required. An Amazon Aurora PostgreSQL DB cluster with at least one replica in a separate Availability Zone provides automatic failover in under 30 seconds, meeting the target.
Single-AZ deployments or manual replica promotions do not meet the low RTO requirement for regional Availability Zone failures.
2
Analyze the cross-region disaster recovery constraints (RPO < 1 minute, RTO < 15 minutes in us-west-2).
Select Amazon Aurora Global Databases, which use fast storage-level replication with lag under 1 second (meeting the RPO of under 1 minute) and support failover/promotion in minutes (meeting the RTO of under 15 minutes).
Daily snapshot replication (Pilot Light) results in an RPO of 24 hours, which violates the 1-minute RPO limit.

Key Concept

High availability and disaster recovery design using Amazon Aurora Multi-AZ and Aurora Global Databases
Estimated Time:2m 0s
Question 26Question

A maritime fleet management company is designing a high-availability telemetry processing system on AWS. The application runs on Amazon ECS containers across multiple Availability Zones in the primary region (`eu-west-1`). The containers require concurrent read/write access to a shared POSIX-compliant file system. The architecture must support a multi-region disaster recovery (DR) plan in `eu-central-1` with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 10 minutes. During failover, the file system in the recovery region must be immediately writable without latency or performance degradation. Which combination of configurations will meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create an Amazon Elastic File System (Amazon EFS) file system in `eu-west-1` using the Regional storage class, and configure Amazon EFS Replication to a destination file system in `eu-central-1`.; In the disaster recovery region (`eu-central-1`), configure the ECS task definitions to mount the replica EFS file system using its native mount target when initiating failover.

Answer

Deploying an Amazon EFS file system in the primary region with replication configured to the secondary region, and configuring the secondary region's ECS tasks to mount the replicated EFS file system.
Deploying Amazon EFS with native replication guarantees that files are automatically copied across regions with low latency, satisfying the 15-minute RPO. In the event of a failover, mounting the local replicated file system in the secondary region allows ECS containers to start up and begin executing operations instantly, comfortably staying within the 10-minute RTO.

Step-by-Step Solution

1
Determine the storage access requirement.
The application requires concurrent read/write POSIX-compliant access, which makes Amazon Elastic File System (EFS) the ideal choice over object storage or block storage.
Amazon EFS supports concurrent access from multiple container instances and complies with standard POSIX directory structures and permissions.
2
Assess replication and RPO compliance.
Enable Amazon EFS Replication from the primary region to the disaster recovery region.
EFS Replication transfers data asynchronously across regions and typically updates the replica within minutes, satisfying the 15-minute RPO.
3
Determine recovery procedures to meet the RTO.
Configure ECS container tasks in the secondary region to mount the replicated EFS file system.
When a failover occurs, the secondary EFS is immediately available for read and write operations. The ECS tasks can mount the local replica with minimal latency, ensuring the 10-minute RTO is met.

Key Concept

Multi-Region shared storage resilience utilizing Amazon EFS Replication to achieve low recovery metrics.
Question 27Question

A SaaS provider is migrating its core multi-tenant application to AWS and requires a PostgreSQL-compatible database. The database architecture must guarantee high availability within a single AWS Region, with a Recovery Time Objective (RTO) of less than 30 seconds and a Recovery Point Objective (RPO) of near zero (under 1 second). Which database configuration meets these requirements with the lowest operational overhead?

Show answer & explanation

Answer: Amazon Aurora PostgreSQL DB cluster with a Multi-AZ deployment containing a writer instance and a reader instance in a different Availability Zone

Answer

Amazon Aurora PostgreSQL DB cluster with a Multi-AZ deployment containing a writer instance and a reader instance in a different Availability Zone
The correct configuration is the Amazon Aurora PostgreSQL DB cluster with a Multi-AZ deployment. Amazon Aurora utilizes a shared storage volume replicated across three Availability Zones. If the primary instance fails, Aurora automatically promotes a reader instance (Aurora Replica) in another Availability Zone to primary. This failover process typically takes less than 30 seconds, satisfying the RTO. Because the storage volume is shared and updated synchronously, the RPO is near zero.

Step-by-Step Solution

1
Analyze RTO and RPO constraints.
The architecture requires an RTO of less than 30 seconds and an RPO of under 1 second (near zero).
This eliminates slow recovery mechanisms (such as snapshot restoration) and asynchronous replication strategies that depend on manual failover.
2
Compare RDS Multi-AZ DB instance failover time with the requirements.
Standard RDS Multi-AZ DB instance failover takes 60 to 120 seconds because it requires database recovery on the standby instance.
This failover duration exceeds the 30-second RTO threshold, eliminating standard RDS Multi-AZ options.
3
Evaluate Amazon Aurora Multi-AZ failover and replication capabilities.
Amazon Aurora automatically promotes an Aurora Replica in another Availability Zone in less than 30 seconds. The shared storage design ensures near-zero RPO without data loss.
Aurora meets both strict RTO and RPO limits out of the box with minimal operational management.

Key Concept

Amazon Aurora Multi-AZ failover and shared storage architecture
Estimated Time:1m 30s
Question 28Question

A media production company hosts a shared file repository on-premises for video editing. The company wants to migrate its storage to AWS to improve resiliency and high availability while maintaining low-latency access for on-premises editors. The design requirements include a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 10 minutes for accessing archived footage. Which of the following solutions should a solutions architect recommend?

Show answer & explanation

Answer: Deploy an Amazon S3 File Gateway on-premises. Configure it to write data to an Amazon S3 bucket, and use an S3 Lifecycle policy to transition archived data to Amazon S3 Glacier Instant Retrieval.

Answer

Deploying an Amazon S3 File Gateway on-premises, writing to an Amazon S3 bucket, and using an S3 Lifecycle policy to transition archived data to Amazon S3 Glacier Instant Retrieval.
The configuration using Amazon S3 File Gateway with S3 Glacier Instant Retrieval is correct because the gateway provides local caching for low-latency file access, while S3 Glacier Instant Retrieval provides millisecond retrieval times that comfortably satisfy the 10-minute RTO requirement.

Step-by-Step Solution

1
Analyze the storage latency and access protocol requirements.
The application requires NFS/SMB file protocols with low local latency, which points to Amazon S3 File Gateway.
File Gateway caches active data locally for low latency and translates file protocols to S3 API calls.
2
Evaluate the Recovery Time Objective (RTO) for archived data.
The RTO is 10 minutes, which requires a storage class with immediate or near-immediate retrieval capabilities.
Standard S3 Glacier classes have retrieval delays of hours, whereas S3 Glacier Instant Retrieval offers millisecond access.
3
Determine the lifecycle strategy to transition archived data.
Define an S3 Lifecycle policy to transition older files to S3 Glacier Instant Retrieval.
This satisfies the 10-minute RTO while optimizing storage costs.

Key Concept

Designing a hybrid file storage architecture with low-latency local access and immediate retrieval of archived data using S3 File Gateway and S3 Glacier Instant Retrieval.
Estimated Time:2m 0s
Question 29Question

A healthcare provider is deploying a critical patient record application using Amazon RDS for MySQL. The database tier must withstand an Availability Zone (AZ) failure with zero data loss (RPO=0RPO = 0) and support automatic failover in less than 45 seconds45\text{ seconds} (RTO<45 sRTO < 45\text{ s}). The application also requires horizontal scaling of read operations to prevent reporting dashboards from affecting the write performance of the primary database instance. Which database configuration meets these requirements with the least operational complexity?

Show answer & explanation

Answer: Deploy an RDS for MySQL Multi-AZ DB cluster. Configure the reporting dashboards to use the reader endpoint of the cluster.

Answer

Deploy an RDS for MySQL Multi-AZ DB cluster and configure the reporting dashboards to use the reader endpoint of the cluster.
Deploying an RDS for MySQL Multi-AZ DB cluster is correct because it uses synchronous replication across three Availability Zones to ensure zero data loss (RPO=0RPO = 0) and provides automatic failover in under 35 seconds (meeting the RTO<45 sRTO < 45\text{ s} requirement). Additionally, the cluster includes two readable standby instances that can be queried via the reader endpoint to scale reads without the operational complexity of provisioning separate read replicas.

Step-by-Step Solution

1
Analyze the high availability and failover constraints.
The requirements dictate zero data loss (RPO=0RPO = 0) and automatic failover in less than 45 seconds (RTO<45 sRTO < 45\text{ s}), which rules out asynchronous replication methods and standard Multi-AZ DB instances (which take 60–120 seconds).
Identifying the recovery metrics helps narrow the architecture options to synchronous cluster-based deployments.
2
Analyze the read scaling and complexity constraints.
The reporting dashboards require read scaling that does not impact write operations, with the least operational complexity.
This points to a configuration that natively supports readable standby instances without requiring separate read replicas to be provisioned and managed.
3
Select the optimal database deployment option.
An Amazon RDS Multi-AZ DB cluster provides one writer and two readable standby instances across three AZs with synchronous replication, automatic failover under 35 seconds, and a built-in reader endpoint.
This satisfies all RTO, RPO, read scaling, and low operational complexity requirements.

Key Concept

Amazon RDS Multi-AZ DB clusters provide synchronous replication across three Availability Zones with readable standby instances and rapid automatic failover (typically under 35 seconds), satisfying strict RPO, RTO, and read-scaling requirements simultaneously.
Question 30Question

A global legal technology platform hosts sensitive litigation documents consisting of scanned court files. The documents must be stored with 99.999999999%99.999999999\% (11 nines) of durability. The platform must maintain a disaster recovery plan across two AWS regions (primary and secondary) with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 15 minutes for its storage tier. The files are frequently accessed during the first 30 days of active litigation, after which access drops significantly; however, any document must remain retrievable within milliseconds when requested. Which storage architecture meets these requirements with the lowest operational overhead?

Show answer & explanation

Answer: Store the litigation documents in an Amazon S3 bucket in the primary region. Configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to replicate the documents to an S3 bucket in the secondary region. Apply an S3 Lifecycle policy to transition the documents to S3 Glacier Instant Retrieval after 30 days.

Answer

Store the litigation documents in an Amazon S3 bucket in the primary region. Configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to replicate the documents to an S3 bucket in the secondary region. Apply an S3 Lifecycle policy to transition the documents to S3 Glacier Instant Retrieval after 30 days.
The correct strategy uses S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) to replicate objects to a secondary region within 15 minutes, satisfying the 15-minute RPO. Transitioning the objects to S3 Glacier Instant Retrieval after 30 days reduces costs while maintaining millisecond retrieval speeds, satisfying the RTO and immediate access requirement when a case is reopened.

Step-by-Step Solution

1
Evaluate the durability and recovery point (RPO) constraints.
Amazon S3 provides 99.999999999%99.999999999\% (11 nines) of durability. To achieve a 15-minute RPO across regions, S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) must be used, which guarantees replication of 99.99% of objects within 15 minutes.
Standard CRR does not guarantee a replication completion time, which could violate the RPO during peak load, while S3 RTC provides a SLA-backed replication timeframe.
2
Evaluate the recovery time (RTO) and access latency constraints.
The documents must be retrievable in milliseconds. S3 Glacier Instant Retrieval meets this requirement, whereas standard Glacier storage classes introduce hours of retrieval latency.
Court discovery workflows require rapid, millisecond access even for archived files, making Glacier Instant Retrieval the only cost-effective archive class that meets the latency target.
3
Determine the optimal cost optimization strategy.
An S3 Lifecycle policy can transition objects from S3 Standard to S3 Glacier Instant Retrieval after 30 days.
This automatically reduces storage costs for historical litigation documents while preserving the ability to retrieve them in milliseconds when a case is reopened.

Key Concept

Designing a multi-region resilient storage architecture using Amazon S3 Cross-Region Replication with Replication Time Control (S3 RTC) and cost-optimizing with S3 Glacier Instant Retrieval for millisecond access latency.
Estimated Time:2m 0s
Question 31Question

A financial technology firm is deploying a transaction auditing application on Amazon EC2 instances distributed across two Availability Zones in the eu-west-1 Region. The application requires a shared, POSIX-compliant file system to store transaction journals. The architecture must survive the complete loss of an Availability Zone with zero data loss (RPO = 0) and continue serving requests without manual intervention. Additionally, the journals must be replicated to the eu-central-1 Region with a Recovery Point Objective (RPO) of less than 15 minutes and a Recovery Time Objective (RTO) of less than 10 minutes. Which storage design meets these requirements while minimizing operational overhead?

Show answer & explanation

Answer: Deploy Amazon EFS using the Regional storage class in the primary region. Configure Amazon EFS Replication to replicate the file system to a destination EFS file system in the secondary region. During a regional failover, delete the replication association on the destination file system and mount it to the standby EC2 instances.

Answer

Deploy Amazon EFS using the Regional storage class in the primary region, configure Amazon EFS Replication to the secondary region, and delete the replication association during a failover to make the destination file system writable.
The correct solution uses the Amazon EFS Regional storage class, which natively replicates data synchronously across multiple Availability Zones to ensure zero data loss during an AZ outage. To achieve cross-region disaster recovery, Amazon EFS Replication provides continuous asynchronous replication to a destination EFS file system in the secondary region. During a disaster recovery event, deleting the replication association changes the destination file system status from read-only to writeable, which can be accomplished in under a minute, meeting the 10-minute RTO.

Step-by-Step Solution

1
Select a storage service that supports POSIX compliance, shared concurrent access across multiple EC2 instances, and automatically replicates data across multiple Availability Zones within the primary region.
Amazon EFS Regional storage class is selected, as it satisfies POSIX compliance, multi-instance mounting, and achieves an RPO of 0 during Availability Zone outages through synchronous multi-AZ replication.
This satisfies the requirement for zero data loss and automated failover in the event of a single Availability Zone loss.
2
Determine the cross-region replication method to meet the RPO of less than 15 minutes.
Configure Amazon EFS Replication to replicate data asynchronously to a destination EFS file system in the eu-central-1 Region.
EFS Replication continuously copies changes to the destination region and typically completes replication in under 15 minutes, which satisfies the RPO requirement.
3
Identify the failover procedure that satisfies the RTO of less than 10 minutes.
In the event of a disaster, delete the replication association on the destination EFS file system to make it read-write, and mount it to the standby EC2 instances.
EFS replica file systems are read-only while replication is active. Deleting the replication association is a fast control-plane operation that makes the destination file system writable immediately, meeting the 10-minute RTO.

Key Concept

Amazon EFS Regional replication and cross-region replication failover behavior
Question 32Question

An international logistics company uses a critical PostgreSQL-compatible transactional database on AWS. The application demands high availability within its primary AWS Region (euwest1eu-west-1) with a Recovery Time Objective (RTO) of less than 60 seconds60\text{ seconds} and a Recovery Point Objective (RPO) of 00 (no data loss) in the event of an Availability Zone outage. Additionally, the company requires a cross-region disaster recovery (DR) architecture in eucentral1eu-central-1 that supports an RPO of less than 5 seconds5\text{ seconds} and an RTO of less than 15 minutes15\text{ minutes}. Which combination of database configurations will satisfy these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy an Amazon Aurora PostgreSQL DB cluster with the primary writer instance in one Availability Zone and a reader instance in a different Availability Zone within the primary Region.; Create an Amazon Aurora Global Database and add a secondary DB cluster in the disaster recovery Region.

Answer

Deploying an Amazon Aurora PostgreSQL DB cluster with writer and reader instances across different Availability Zones in the primary Region, and creating an Amazon Aurora Global Database with a secondary DB cluster in the disaster recovery Region.
The correct architecture combines an Amazon Aurora PostgreSQL DB cluster deployed across multiple Availability Zones in the primary Region (to achieve an RTO of less than 60 seconds and an RPO of 0 through automatic failover to a reader instance) with an Amazon Aurora Global Database secondary cluster (to achieve an RPO of less than 5 seconds and an RTO of less than 15 minutes through physical storage-level replication and managed failover).

Step-by-Step Solution

1
Analyze the high availability (HA) requirements in the primary Region.
The RTO must be less than 60 seconds and the RPO must be 0.
An Aurora DB cluster with a reader instance in a different Availability Zone supports automatic failover in less than 30 seconds with 0 data loss due to Aurora's shared storage architecture.
2
Analyze the cross-region disaster recovery (DR) requirements.
The RPO must be less than 5 seconds and the RTO must be less than 15 minutes.
Amazon Aurora Global Databases replicate data at the physical storage layer with typical replication lag under 1 second and support managed failovers in under 1 minute.
3
Evaluate the architectural options against these combined requirements.
Deploying Aurora Multi-AZ with a reader instance and configuring an Aurora Global Database secondary cluster satisfies all parameters, whereas backups, single-node configurations, and DNS-level routing do not meet the RTO/RPO limits or multi-region database capabilities.

Key Concept

High availability is achieved locally using Multi-AZ deployments with synchronous replication (or shared storage architectures), whereas cross-region disaster recovery with low RPO/RTO requires low-latency asynchronous physical replication such as Amazon Aurora Global Databases.
Question 33Question

A healthcare provider hosts a web application where medical imaging files must be stored. The storage solution must allow multiple web servers running on Amazon EC2 instances in different Availability Zones to read and write to the files simultaneously. In the event of an Availability Zone outage, the storage must remain available with a Recovery Time Objective (RTO) of zero. Which storage solution meets these requirements with the least configuration effort?

Show answer & explanation

Answer: Deploy an Amazon Elastic File System (Amazon EFS) file system with mount targets in each Availability Zone.

Answer

Deploy an Amazon Elastic File System (Amazon EFS) file system with mount targets in each Availability Zone.
Deploying an Amazon Elastic File System (Amazon EFS) is correct because it is a regional storage service that supports concurrent read/write access from EC2 instances in different Availability Zones. Because it replicates data across multiple Availability Zones, it offers native resilience and maintains availability with an RTO of zero if a single Availability Zone experiences an outage.

Step-by-Step Solution

1
Identify key requirements for file access and resiliency.
The requirements are simultaneous read/write access from multiple EC2 instances in different Availability Zones, and an RTO of zero during an AZ outage.
This determines that the target solution must support regional multi-AZ architectures and concurrent file-level access.
2
Evaluate the capabilities of the storage options.
Amazon EFS natively provides concurrent, POSIX-compliant file system access across multiple Availability Zones with built-in high availability.
Amazon EBS is restricted to a single Availability Zone, S3 Glacier introduces retrieval delays, and RDS is a structured database rather than a shared file system.

Key Concept

Amazon EFS provides highly available, regional shared file systems that support concurrent read and write access from EC2 instances in multiple Availability Zones.
Estimated Time:45s
Question 34Question

A pharmaceutical company is designing a disaster recovery architecture for its genomic drug simulation datasets. The active datasets are stored in Amazon S3 in the `us-east-1` Region and are critical to clinical trial validation. Compliance mandates that these datasets must be replicated to a secondary AWS Region (`us-west-2`). The solution must guarantee a Recovery Point Objective (RPO) of 15 minutes15\text{ minutes} and a Recovery Time Objective (RTO) of 30 minutes30\text{ minutes} for read access to the replicated datasets in `us-west-2`. The replication mechanism must be asynchronous to prevent any performance impact on the primary simulation engines in `us-east-1`. Which configuration will meet these storage requirements?

Show answer & explanation

Answer: Configure Amazon S3 Cross-Region Replication (CRR) from the source bucket in `us-east-1` to the destination bucket in `us-west-2`, and enable Amazon S3 Replication Time Control (S3 RTC) on the replication rule.

Answer

Configure Amazon S3 Cross-Region Replication (CRR) from the source bucket in `us-east-1` to the destination bucket in `us-west-2`, and enable Amazon S3 Replication Time Control (S3 RTC) on the replication rule.
Enabling Amazon S3 Replication Time Control (S3 RTC) on a Cross-Region Replication (CRR) rule ensures that 99.9%99.9\% of objects are replicated within 15 minutes15\text{ minutes}, directly satisfying the 1515-minute Recovery Point Objective (RPO). Since the replicated data is immediately accessible in the destination S3 bucket in the secondary region, it easily satisfies the 3030-minute Recovery Time Objective (RTO) for read access without affecting write performance at the source.

Step-by-Step Solution

1
Analyze the Recovery Point Objective (RPO) requirement.
The requirement is an RPO of 15 minutes15\text{ minutes}, which means replicated data must be at most 15 minutes15\text{ minutes} behind the primary storage.
To guarantee replication lag of under 15 minutes15\text{ minutes} with an AWS SLA, Amazon S3 Replication Time Control (S3 RTC) must be used, which replicates 99.9%99.9\% of objects within 15 minutes15\text{ minutes}.
2
Analyze the Recovery Time Objective (RTO) requirement.
The RTO is 30 minutes30\text{ minutes} for read access in the failover region.
Active replication to a standard S3 bucket allows immediate read access via S3 APIs, which fits well within the 3030-minute RTO. Glacier Flexible Retrieval with Standard retrieval is ruled out due to its 33-to-55-hour retrieval delay.
3
Evaluate administrative overhead and workload compatibility.
Amazon S3 object storage is optimal for raw simulation datasets, and native S3 CRR requires minimal operational management compared to custom sync scripts or relational databases.
Native replication features minimize custom scripts, reduce operational complexity, and avoid misusing relational database services for object storage workloads.

Key Concept

Replication Time Control (S3 RTC) guarantees replication within 15 minutes15\text{ minutes} to meet tight RPO/RTO parameters for object storage.
Estimated Time:2m 0s
Question 35Question

A company serves its global API through Amazon EC2 instances behind Application Load Balancers (ALBs) in the us-east-1 and eu-west-1 Regions. Currently, Route 53 is configured with latency-based routing to distribute traffic across these regions. The company wants to establish an active-passive disaster recovery (DR) plan. If the application endpoints in both primary regions fail their health checks, Route 53 must automatically redirect all user traffic to a static maintenance webpage hosted in an Amazon S3 bucket in us-west-2. The recovery time objective (RTO) is under 10 minutes. Which Route 53 routing configuration should a solutions architect implement to meet these requirements?

Show answer & explanation

Answer: Configure latency-based alias records for a subdomain pointing to the ALBs in us-east-1 and eu-west-1, with 'Evaluate Target Health' set to Yes on both. Create a primary failover alias record for the primary domain pointing to the subdomain with 'Evaluate Target Health' set to Yes, and a secondary failover alias record pointing to the S3 static website endpoint.

Answer

The correct configuration is to use nested Route 53 records where latency-based alias records for a subdomain point to the ALBs with 'Evaluate Target Health' set to Yes, combined with primary and secondary failover records at the apex domain level that propagate health check status.
The correct configuration uses nested records to combine active-active latency routing with active-passive failover routing. By pointing the primary failover alias record to the latency-based alias records, and enabling 'Evaluate Target Health' on both the parent failover record and the child latency records, Route 53 monitors the health of the ALBs. If the ALBs in both regions fail their health checks, Route 53 detects that the primary failover target is unhealthy and redirects traffic to the secondary failover record pointing to the S3 static website.

Step-by-Step Solution

1
Identify the hybrid routing requirement.
The configuration requires active-active routing (latency-based) between the two active regions under normal operation, combined with active-passive failover to a static website on Amazon S3 during an outage.
This establishes the need for nested records because a single Route 53 record name cannot support both latency-based and failover routing policies simultaneously.
2
Design the active-passive failover record pair.
Create a primary failover alias record at the domain apex pointing to a nested subdomain, and create a secondary failover alias record pointing to the S3 static website endpoint.
This structures the DNS records so that traffic fails over to the backup S3 bucket only when the primary target group is deemed completely unhealthy.
3
Configure the nested active-active latency records with health check propagation.
Create latency-based alias records for the subdomain pointing to the respective regional ALBs, and enable 'Evaluate Target Health' on both the parent failover record and the child latency records.
Enabling 'Evaluate Target Health' on the child latency records ensures Route 53 monitors ALB health. Enabling it on the parent failover record ensures Route 53 checks the health of the subdomain targets and fails over to S3 if all underlying ALBs are unhealthy.

Key Concept

Route 53 active-passive failover can be configured over active-active latency-based routing by using nested alias records and enabling 'Evaluate Target Health' to propagate health status up the DNS record chain.
Question 36Question

An energy utility company's smart grid platform processes real-time telemetry from millions of meters. The ingestion layer runs on a fleet of Amazon EC2 instances distributed across three Availability Zones. This tier requires a shared, highly available file storage layer that supports concurrent read/write access. Additionally, the company must retain raw data logs for 77 years to meet regulatory compliance, with an administrative requirement to retrieve any archived log within 1515 minutes.

Which combination of AWS storage configurations will meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class to mount on the EC2 instances.; Store compliance logs in Amazon S3 and implement an S3 Lifecycle policy to transition objects to Amazon S3 Glacier Instant Retrieval.

Answer

The correct configurations are to mount an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class on the EC2 instances, and to store compliance logs in Amazon S3 with an S3 Lifecycle policy transitioning them to Amazon S3 Glacier Instant Retrieval.
The correct configurations involve using Amazon Elastic File System (Amazon EFS) and Amazon S3 Glacier Instant Retrieval. Amazon EFS provides a serverless, fully managed, shared file system that can be accessed concurrently by EC2 instances across multiple Availability Zones, ensuring high availability and resilience. For the archiving requirement, storing logs in Amazon S3 and transitioning them to Amazon S3 Glacier Instant Retrieval ensures the logs are cost-effectively stored for 77 years while maintaining the ability to retrieve them in milliseconds, meeting the RTO of 1515 minutes.

Step-by-Step Solution

1
Analyze the file sharing requirement for the compute tier.
The EC2 fleet is distributed across three Availability Zones and requires concurrent read/write access to a shared file system.
This establishes that a regional shared file storage service like Amazon EFS is required, as standard EBS volumes cannot be shared across multiple Availability Zones.
2
Evaluate the compliance log retention and retrieval requirements.
Logs must be stored for 77 years with a retrieval time limit (RTO) of 1515 minutes.
This eliminates cold archive options like S3 Glacier Deep Archive standard retrievals, which take up to 1212 hours, and directs the solution toward S3 Glacier Instant Retrieval which offers millisecond access.
3
Verify service compatibility and limitations for the selected options.
Amazon EFS natively supports multi-AZ concurrent mounts. Amazon S3 Glacier Instant Retrieval satisfies both the long-term archiving requirement and the low RTO retrieval requirement.
This confirms that combining Amazon EFS and S3 Glacier Instant Retrieval provides a highly available, resilient, and compliant architecture.

Key Concept

Designing a resilient, multi-AZ shared file storage layer combined with a compliant, fast-retrieval archive solution.
Estimated Time:2m 0s
Question 37Question

An enterprise company hosts its customer portal under the domain name portal.finance.example.com. The primary infrastructure consists of an Application Load Balancer (ALB) and EC2 instances in the us-east-1 region. The company wants to set up an active-passive disaster recovery strategy. If the primary region goes offline or if the primary database loses connectivity, traffic must automatically redirect to an Amazon S3 bucket in the us-west-2 region hosting a static maintenance page. A custom health-check script on the EC2 instances monitors the database connection status. Which two configurations should the solutions architect implement to achieve this goal? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the us-east-1 ALB, set the routing category to Primary, enable Evaluate Target Health, and configure the ALB's target group health checks to monitor the custom health-check path.; Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the Amazon S3 static website endpoint in us-west-2, set the routing category to Secondary, and configure the S3 bucket name to exactly match portal.finance.example.com.

Answer

Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the us-east-1 ALB (Primary with Evaluate Target Health enabled and target group health checks pointing to the custom path) and configure a Route 53 Failover record as an Alias record pointing to the Amazon S3 static website endpoint in us-west-2 (Secondary with matching bucket name).
To implement active-passive failover, the architect should define a Route 53 Failover policy. The primary record is configured as an Alias record pointing to the Application Load Balancer (ALB) with 'Evaluate Target Health' enabled. This links Route 53's health decision to the ALB's target health status. The ALB's target group executes health checks against the custom script verifying database connectivity. The secondary record is also configured as a Failover Alias record pointing to the Amazon S3 static website endpoint. For Route 53 to resolve an Alias record directly to an S3 bucket, the S3 bucket name must match the domain name exactly.

Step-by-Step Solution

1
Analyze the active-passive failover requirement and identify the correct Route 53 routing policy.
Determine that a Route 53 Failover routing policy is required, featuring a primary record for normal operations and a secondary record for the maintenance page.
Failover routing is the native Route 53 policy designed specifically for active-passive disaster recovery configurations.
2
Evaluate the health-checking requirement involving the primary application and the backend database.
Identify that enabling 'Evaluate Target Health' on the primary Route 53 Alias record will delegate health evaluation to the ALB. The ALB's target group must be configured to check the custom script path that verifies database connectivity.
If target instances fail the ALB's health check due to database loss, the ALB is marked unhealthy, causing Route 53 to failover to the secondary target.
3
Establish the secondary record pointing to the static maintenance site.
Configure a secondary Failover Alias record pointing to the Amazon S3 static website endpoint. Ensure the S3 bucket name matches the domain name exactly.
Route 53 requires the S3 bucket name to match the record name (portal.finance.example.com) for Alias record resolution to work correctly.

Key Concept

Amazon Route 53 DNS Failover and health check configuration for active-passive disaster recovery architectures.
Question 38Question

A digital real estate enterprise operates a property document management portal on AWS. The portal hosts critical PDF appraisal reports and legal deeds that require 99.999999999%99.999999999\% (11 nines) of data durability. These documents are frequently accessed during the first 3030 days of a listing. After this period, they are rarely accessed, but agents must be able to retrieve them in real-time (latency under 11 second) during client meetings, establishing a Recovery Time Objective (RTO) of less than 1010 seconds. The architecture must remain highly available (99.9%99.9\% availability) and resilient to the loss of an entire AWS Availability Zone (AZ). Which storage strategy meets these requirements most cost-effectively?

Show answer & explanation

Answer: Store the files in Amazon S3 Standard. Use an S3 Lifecycle policy to transition the files to Amazon S3 Glacier Instant Retrieval after 3030 days.

Answer

Store the files in Amazon S3 Standard. Use an S3 Lifecycle policy to transition the files to Amazon S3 Glacier Instant Retrieval after 30 days.
Amazon S3 Glacier Instant Retrieval is designed for archiving data that is rarely accessed but requires millisecond retrieval times when requested. It provides the same 11 nines of durability and availability across multiple Availability Zones as S3 Standard, meeting all resilience and RTO constraints while optimizing costs.

Step-by-Step Solution

1
Analyze durability, availability, and recovery requirements.
The system requires 99.999999999%99.999999999\% durability, 99.9%99.9\% availability, multi-AZ resilience, and real-time retrieval (latency under 11 second) after 3030 days.
This establishes the constraints for choosing the appropriate storage tier.
2
Evaluate Amazon S3 storage classes against RTO requirements.
Amazon S3 Standard and Amazon S3 Glacier Instant Retrieval both offer 99.999999999%99.999999999\% durability and multi-AZ resilience. S3 Glacier Instant Retrieval provides retrieval in milliseconds, satisfying the RTO.
Standard Glacier classes like Glacier Flexible Retrieval take hours to retrieve data and cannot meet the real-time access requirement.
3
Compare cost-effectiveness.
S3 Glacier Instant Retrieval has a lower storage cost than S3 Standard, making it the most cost-effective choice for rarely accessed documents that require immediate access.
Using S3 Lifecycle policies to automate the transition minimizes costs without manual intervention.

Key Concept

Selecting resilient and cost-effective AWS storage classes based on RTO and retrieval latency requirements
Estimated Time:1m 30s
Question 39Question

A digital media agency is building a collaborative video editing platform on AWS. The editing application runs on a fleet of Amazon EC2 instances distributed across multiple Availability Zones in a single AWS Region. The instances require concurrent read and write access to a shared file workspace with sub-millisecond latencies. Additionally, the agency must archive completed video projects to minimize storage costs. In the event of a disaster, the archived files must be fully recoverable within a Recovery Time Objective (RTO) of 10 minutes. Which combination of storage solutions should a solutions architect recommend?

Show answer & explanation

Answer: Use Amazon EFS for the active collaborative workspace. Store the archived projects in Amazon S3 Glacier Flexible Retrieval and use Expedited retrievals during disaster recovery.

Answer

Use Amazon EFS for the active collaborative workspace. Store the archived projects in Amazon S3 Glacier Flexible Retrieval and use Expedited retrievals during disaster recovery.
Amazon EFS is a managed, shared file system that supports simultaneous read and write connections from multiple EC2 instances across multiple Availability Zones in a Region. It provides sub-millisecond latencies, which fits the active collaboration requirements. For the archival tier, Amazon S3 Glacier Flexible Retrieval using Expedited retrievals satisfies the 10-minute Recovery Time Objective (RTO) because it typically restores data within 1 to 5 minutes, while maintaining a lower storage cost relative to S3 Standard.

Step-by-Step Solution

1
Analyze the active workspace storage requirements.
Identify that the storage must support concurrent read/write access from EC2 instances across multiple Availability Zones with sub-millisecond latency. Amazon EFS is a native POSIX-compliant shared file system that meets these requirements.
EBS volumes cannot be attached across multiple Availability Zones, and EBS Multi-Attach is limited to a single Availability Zone and only supported on io1/io2 volumes, not gp3.
2
Evaluate the archive storage retrieval options against the disaster recovery requirements.
The target RTO is 10 minutes. S3 Glacier Flexible Retrieval with Expedited retrievals recovers data in 1 to 5 minutes, which falls within the 10-minute threshold. Standard retrievals for Glacier Flexible Retrieval (3-5 hours) and Glacier Deep Archive (12 hours) are too slow.
Choosing the correct Glacier retrieval tier is critical to meeting strict RTOs while minimizing long-term archival costs.
3
Assess the cost optimization constraints.
Verify that deleting objects early in S3 Standard-IA is cost-prohibitive due to the 30-day minimum billing charge. EFS for hot data and S3 Glacier Flexible Retrieval with Expedited retrievals for cold data represents the most cost-effective and resilient architecture.
Avoiding S3 IA minimum duration penalties helps satisfy the requirement to minimize storage costs.

Key Concept

Selecting highly available and resilient shared storage (Amazon EFS) combined with fast-recovery archival solutions (S3 Glacier with Expedited retrievals) to satisfy concurrent access, Multi-AZ availability, and tight RTO limits.
Estimated Time:1m 30s
Question 40Question

A telehealth provider runs a medical imaging and patient record application on AWS. The application tier runs on a fleet of Amazon EC2 instances distributed across multiple Availability Zones in a single AWS Region. The application requires a shared storage layer to host patient medical images. This storage layer must allow concurrent read and write access from all EC2 instances. The architecture must achieve high availability with a Recovery Point Objective (RPO) of 0 and a Recovery Time Objective (RTO) of less than 1 minute against an Availability Zone outage. For compliance, the images must also be replicated to a secondary AWS Region. In the event of a disaster in the primary Region, the secondary Region must be able to serve the images with a recovery time (RTO) of less than 5 minutes. Which two configurations should a solutions architect recommend to build a resilient storage solution? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Use an Amazon EFS file system configured with the EFS Regional storage class in the primary Region.; Configure Amazon EFS Replication to replicate the file system to a destination EFS file system in the secondary Region.

Answer

The correct configurations are to use an Amazon EFS file system with the EFS Regional storage class in the primary Region, and to configure Amazon EFS Replication to replicate the file system to a destination EFS file system in the secondary Region.
The correct options are to use an Amazon EFS file system with the Regional storage class and to configure Amazon EFS Replication. EFS Regional storage class stores data redundantly across multiple Availability Zones in a single Region, ensuring that even if one Availability Zone fails, the file system remains online with no data loss (RPO = 0, RTO < 1 minute) and allows concurrent access from all application instances. Amazon EFS Replication replicates data across AWS Regions continuously in near real-time, allowing the destination file system to be immediately writable during a failover with a recovery time of less than 5 minutes.

Step-by-Step Solution

1
Evaluate the requirement for shared, concurrent storage access across multiple Availability Zones in the primary Region.
Identify that Amazon EFS with the Regional storage class is designed for multi-AZ concurrent file access with high availability.
Amazon EFS Regional replicates data across multiple AZs and allows concurrent read/write from EC2 instances in different AZs, satisfying RPO=0 and low RTO.
2
Analyze the cross-Region disaster recovery requirements (RTO < 5 minutes).
Determine that Amazon EFS Replication continuously synchronizes EFS file systems across Regions with minimal latency.
EFS Replication provides a destination file system that is immediately ready during failover, satisfying the sub-5-minute RTO.
3
Examine the recovery time constraints of alternative storage tiers like S3 Glacier and EBS.
Eliminate options utilizing S3 Glacier Standard Retrieval due to hours-long retrieval delays, and eliminate EBS due to single-AZ limits and manual recovery times.
Meeting strict low RTO and RPO requirements necessitates active replication rather than slow restore processes or single-AZ block storage.

Key Concept

Implementing resilient, shared multi-AZ file storage using Amazon EFS with cross-Region replication to meet low RTO and RPO targets.
PreviousPage 2 / 20Next
Design Resilient Architectures Practice Questions — AWS Certified Solutions Architect - Associate — Page 2 | Examkin