Examkin

Design Resilient Architectures

382 questions

All types382Multiple choice195Multiple select187
Question 161Question →

A mobile gaming company uses Amazon CloudFront to deliver static game patch files to global users. The patch files are primarily served from an Application Load Balancer (ALB) backed by Amazon EC2 instances. To improve availability, the company has uploaded a backup copy of the patch files to an Amazon S3 bucket. The solutions architect must configure CloudFront to automatically serve files from the S3 bucket if the ALB is unavailable or returns 502 or 504 error codes.

Which two actions should the solutions architect take to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create an origin group in the CloudFront distribution containing the Application Load Balancer as the primary origin and the Amazon S3 bucket as the secondary origin.; Configure the failover criteria in the CloudFront origin group to trigger on HTTP status codes 502 and 504.

Answer

Create an origin group in the CloudFront distribution containing the Application Load Balancer as the primary origin and the Amazon S3 bucket as the secondary origin, and configure the failover criteria in the CloudFront origin group to trigger on HTTP status codes 502 and 504.
The correct solution involves creating a CloudFront origin group with the Application Load Balancer as the primary origin and the S3 bucket as the secondary origin. The failover criteria in the group must be configured to trigger on HTTP status codes 502 and 504. When CloudFront receives a 502 or 504 response from the ALB, it will transparently fail over to the S3 bucket to retrieve the content.

Step-by-Step Solution

1
Identify the primary and secondary origins for the content delivery path.
The Application Load Balancer is identified as the primary origin, and the Amazon S3 bucket containing the backup files is identified as the secondary origin.
Establishing the roles of each origin is necessary before configuring failover mechanics.
2
Group the origins in the CloudFront distribution settings.
An origin group is created containing both the Application Load Balancer (primary) and the Amazon S3 bucket (secondary).
CloudFront requires origins to be grouped together to enable automatic failover behavior.
3
Specify the status codes that should trigger failover.
The failover criteria are configured to include 502 and 504 HTTP status codes.
This ensures that when the ALB returns these gateway errors, CloudFront redirects the request to the S3 bucket.

Key Concept

CloudFront Origin Failover using Origin Groups allows automatic redirection of client requests to a backup origin when the primary origin is unreachable or returns specified HTTP error status codes.
Question 162Question →

A solutions architect needs to configure an Amazon RDS for MySQL database to support high availability within a single AWS Region. The configuration must provide automatic failover to a standby instance in a different Availability Zone in the event of an infrastructure failure. Which database configuration will meet these requirements with the least administrative effort?

Show answer & explanation

Answer: Configure an Amazon RDS Multi-AZ DB instance deployment.

Answer

Configure an Amazon RDS Multi-AZ DB instance deployment.
Deploying the database as an Amazon RDS Multi-AZ DB instance deployment automatically provisions and maintains a synchronous standby replica in a different Availability Zone. If the primary instance fails, Amazon RDS automatically performs a failover to the standby with zero administrative intervention and minimal downtime.

Step-by-Step Solution

1
Identify the primary goal of establishing database high availability and automatic failover within a single AWS Region with minimum administrative effort.
Determined that the database requires a configuration that synchronously replicates data to another Availability Zone and automatically redirects application traffic during a failure.
This establishes the baseline requirements to evaluate the available Amazon RDS deployment models.
2
Evaluate the capabilities of Amazon RDS Multi-AZ deployments.
Confirmed that Amazon RDS Multi-AZ automatically provisions a synchronous standby replica in a different Availability Zone and performs automatic failover during outages.
This directly aligns with the goal of high availability and automatic failover without manual intervention.
3
Compare the correct solution against alternatives like read replicas, DNS routing policies, and cross-region warm standbys.
Identified that the alternatives either require manual failover processes or are designed for different use cases like read scaling and regional disaster recovery.
This confirms that only the Multi-AZ deployment configuration satisfies all stated requirements with the least administrative effort.

Key Concept

Amazon RDS Multi-AZ deployments provide high availability, data redundancy, and automatic failover support within a single AWS Region.
Estimated Time:45s
Question 163Question →

An e-commerce corporation is upgrading the disaster recovery capabilities of its transaction ledger and media catalog storage on AWS. The architecture is primarily based in the `us-east-1` Region and must support failover to the `us-west-2` Region. The media catalog contains millions of image files that require a Recovery Point Objective (RPO) of 1515 minutes and a Recovery Time Objective (RTO) of 1515 minutes. The transaction ledger demands persistent shared file storage that spans multiple Availability Zones in both Regions with minimal recovery time. Which two storage configurations will meet these durability and disaster recovery requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Store the media catalog files in an Amazon S3 bucket in `us-east-1` and configure Amazon S3 Cross-Region Replication (CRR) to `us-west-2` with S3 Replication Time Control (RTC) enabled.; Deploy Amazon Elastic File System (Amazon EFS) in `us-east-1` using the Standard storage class to span multiple Availability Zones, and configure Amazon EFS Replication to asynchronously replicate data to a destination EFS file system in `us-west-2`.

Answer

The correct configurations involve storing the media catalog files in an Amazon S3 bucket with Cross-Region Replication (CRR) and Replication Time Control (RTC) enabled to guarantee replication within fifteen minutes, and using Amazon Elastic File System (Amazon EFS) with EFS Replication to provide highly available, multi-AZ shared storage replicated across regions.
The correct configurations involve storing the media catalog files in an Amazon S3 bucket with Cross-Region Replication (CRR) and Replication Time Control (RTC) enabled to guarantee replication within 1515 minutes, and using Amazon Elastic File System (Amazon EFS) with EFS Replication to provide highly available, multi-AZ shared storage replicated across regions.

Step-by-Step Solution

1
Analyze the RTO and RPO requirements for both storage types.
Identify that the media catalog requires an RTO of 1515 minutes and RPO of 1515 minutes, while the transaction ledger requires multi-AZ persistence and replication to the secondary region with minimal RTO.
Ensures the selected solutions meet the quantitative operational thresholds.
2
Evaluate options for replicating the S3-based media catalog.
Select S3 Cross-Region Replication (CRR) with Replication Time Control (RTC) enabled, which guarantees 99.99%99.99\% of objects replicate within 1515 minutes.
Standard S3 replication is asynchronous without a guaranteed SLA, but RTC ensures the 1515-minute RPO is met.
3
Evaluate options for the shared file storage ledger.
Select Amazon EFS with Standard storage class (spans multiple AZs) combined with Amazon EFS Replication to copy data across Regions.
EFS Replication provides automated cross-region replication for shared file systems, matching the high availability and multi-region resilience requirements.

Key Concept

Designing highly available, multi-AZ and multi-region storage systems using S3 replication configurations and EFS replication schemas to meet low RTO and RPO targets.
Estimated Time:2m 0s
Question 164Question →

A financial transaction processing platform is migrating its relational database to AWS. The platform requires a highly resilient database architecture deployed across two AWS Regions: us-east-1 (Primary) and us-west-2 (Secondary). The architecture must meet the following constraints:

1. Intra-region failover must be automatic, with a Recovery Time Objective (RTO) of less than 3030 seconds and a Recovery Point Objective (RPO) of 00.
2. Cross-region disaster recovery must have an RPO of less than 22 seconds and an RTO of less than 55 minutes.
3. The database must dynamically scale read capacity independently in both regions to handle seasonal traffic spikes without manual intervention.
4. During normal operations, the application in the secondary region must be able to issue read and write requests locally, with write requests forwarded to the primary region without needing complex application-side write-routing logic.

Which database configuration meets these requirements with the least operational complexity?

Show answer & explanation

Answer: Deploy an Amazon Aurora Global Database with PostgreSQL compatibility. Configure the primary DB cluster in us-east-1 as a Multi-AZ deployment. Deploy a secondary DB cluster in us-west-2 and enable Aurora Auto Scaling for its reader instances. Enable write forwarding on the secondary DB cluster, allowing application clients in us-west-2 to write directly to the local reader endpoint, which forwards the writes to the primary cluster in us-east-1.

Answer

Deploy an Amazon Aurora Global Database with PostgreSQL compatibility. Configure the primary DB cluster in us-east-1 as a Multi-AZ deployment. Deploy a secondary DB cluster in us-west-2 and enable Aurora Auto Scaling for its reader instances. Enable write forwarding on the secondary DB cluster, allowing application clients in us-west-2 to write directly to the local reader endpoint, which forwards the writes to the primary cluster in us-east-1.
The configuration utilizing Amazon Aurora Global Database satisfies all constraints. The local Multi-AZ cluster deployment meets the intra-region RTO/RPO requirements. Aurora Global Database's storage-level replication delivers a cross-region RPO of less than 22 seconds (typically under 11 second) and can be promoted to a primary cluster in under 55 minutes. Additionally, write forwarding on the secondary cluster allows the secondary region application to send reads and writes to its local endpoint, simplifying write routing, while Aurora Auto Scaling dynamically manages read replica capacity.

Step-by-Step Solution

1
Evaluate intra-region resiliency requirements.
Amazon Aurora DB clusters with Multi-AZ deployments replication model satisfies the local RPO of 00 and RTO of under 3030 seconds via automated failover of the writer instance.
Aurora storage is replicated across three Availability Zones within a region, ensuring zero data loss and rapid automated failover.
2
Evaluate cross-region disaster recovery replication lag.
Amazon Aurora Global Database uses dedicated storage-level physical replication to secondary regions, achieving replication lag of under 11 second.
Physical replication bypasses the SQL execution engine, which is much faster than logical database replication or snapshot-based restoration.
3
Assess write routing and read capacity requirements in the secondary region.
Enable write forwarding on the secondary Aurora DB cluster and configure Aurora Auto Scaling for the readers.
Write forwarding routes write requests transparently to the primary region cluster while keeping reads local. Aurora Auto Scaling adjusts read replicas dynamically based on demand.

Key Concept

Amazon Aurora Global Database architecture, cross-region replication mechanics, and write forwarding capabilities.
Question 165Question →

An enterprise is deploying a critical SQL-based retail application across two AWS Regions: eu-west-1 as the primary region and us-east-1 as the disaster recovery region. The application requires a database that can handle heavy read traffic locally in both regions. For disaster recovery, the solutions architect must design a database tier that achieves a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 5 minutes.

Which combination of actions must the solutions architect take to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy an Amazon Aurora Global Database with the primary database cluster in eu-west-1 and a secondary database cluster in us-east-1.; Promote the secondary database cluster in us-east-1 to take over as the primary cluster in the event of a regional outage in eu-west-1.

Answer

Deploy an Amazon Aurora Global Database with the primary DB cluster in eu-west-1 and a secondary DB cluster in us-east-1, and promote the secondary cluster to primary in the event of an outage.
Deploying Amazon Aurora Global Database provides storage-level replication across AWS Regions with replication latency under 1 second, meeting the Recovery Point Objective (RPO) requirement. Promoting the secondary cluster in the event of a primary region outage can be completed in less than 1 minute, which aligns with the Recovery Time Objective (RTO) requirement of under 5 minutes while allowing local read scaling in the secondary region.

Step-by-Step Solution

1
Select a multi-region database solution that supports SQL and storage-level replication.
Choose Amazon Aurora Global Database to achieve low-latency asynchronous replication across regions.
Aurora Global Database replicates data to secondary regions with a latency of less than 1 second, meeting the RPO requirement of < 1 second.
2
Enable read scaling in the secondary region.
The secondary cluster in us-east-1 is active and can serve read-only queries locally to users in that region.
This offloads read traffic from the primary region and improves local application performance.
3
Establish a disaster recovery promotion procedure.
Promoting the secondary cluster to primary read-write capability takes less than 1 minute.
This promotion meets the RTO requirement of under 5 minutes during a regional outage.

Key Concept

Amazon Aurora Global Database provides cross-region disaster recovery and read scaling by utilizing storage-based replication with latency under 1 second and promotion capabilities under 1 minute.
Estimated Time:2m 0s
Question 166Question →

A company runs a critical transactional workload on a single-instance Amazon RDS for MySQL database in a single Availability Zone. The database tier must be redesigned to survive an Availability Zone outage with a Recovery Point Objective (RPO) of zero (no data loss) and a Recovery Time Objective (RTO) of less than 2 minutes. Which configuration will meet these requirements with the least administrative effort?

Show answer & explanation

Answer: Modify the Amazon RDS for MySQL database instance to a Multi-AZ DB instance deployment.

Answer

Modify the Amazon RDS for MySQL database instance to a Multi-AZ DB instance deployment.
Modifying the DB instance to a Multi-AZ deployment is correct because Amazon RDS automatically provisions and maintains a synchronous standby replica in a different Availability Zone. Updates are synchronously committed to both the primary and standby databases, achieving an RPO of zero. In the event of an AZ outage, RDS automatically handles failover to the standby instance, typically completing in under 2 minutes (meeting the RTO requirement) without manual intervention.

Step-by-Step Solution

1
Analyze recovery requirements.
Determined that RPO = 0 requires synchronous data replication, and RTO < 2 minutes requires automated failover.
Asynchronous replication mechanisms cannot guarantee zero data loss, and manual failover procedures take too long.
2
Evaluate Amazon RDS deployment options.
Amazon RDS Multi-AZ deployments provide synchronous replication to a standby instance in a second Availability Zone and support automatic DNS failover.
This matches all recovery parameters with no manual intervention required during an outage.

Key Concept

Amazon RDS Multi-AZ Deployment
Question 167Question →

A global retail company is deploying a transactional microservice across two AWS Regions: us-east-1 and eu-west-1. The service requires active-active database access, allowing users in both regions to perform low-latency reads and writes locally. The architecture must achieve a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 5 seconds. The database must automatically handle multi-region replication and conflict resolution. Which two configurations should a solutions architect select to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create an Amazon DynamoDB table in us-east-1 and configure it as a global table by adding the eu-west-1 Region.; Configure the microservice instances in each region to read and write to their local regional Amazon DynamoDB endpoint.

Answer

Create an Amazon DynamoDB table in us-east-1 and configure it as a global table by adding the eu-west-1 Region, and configure the microservice instances in each region to read and write to their local regional Amazon DynamoDB endpoint.
To satisfy the requirements of active-active multi-region writes, sub-second RPO, and sub-5-second RTO, Amazon DynamoDB Global Tables is the optimal choice. It provides multi-region, multi-active replication where writes to any region are propagated to other regions within a second. By pointing the local microservices to their local DynamoDB endpoints, the application achieves low-latency local reads and writes, and if a region fails, traffic can be instantly rerouted to the other region's local endpoint, meeting the strict RTO constraint.

Step-by-Step Solution

1
Analyze the application requirements.
Identify that the system demands active-active local multi-region writes, RPO < 1 second, RTO < 5 seconds, and automatic conflict resolution.
This rules out traditional relational databases like RDS or Aurora that operate with a single primary writer and secondary read-only replicas.
2
Select a multi-region active-active database technology.
Amazon DynamoDB Global Tables provides fully managed active-active replication with automatic conflict resolution (last-writer-wins) and sub-second replication latency (RPO < 1s).
DynamoDB Global Tables replicates data across regions in near real-time, matching the sub-second replication requirement.
3
Configure application routing and local access.
Directing applications to their local regional endpoints ensures low-latency reads and writes, and enables automatic failover to the other region's endpoint in less than 5 seconds (RTO).
This fully addresses the active-active performance and resiliency constraints.

Key Concept

Multi-region active-active database architectures with low RTO/RPO using DynamoDB Global Tables
Question 168Question →

A healthcare provider is designing a resilient, highly available architecture on AWS for its critical patient imaging system. The system consists of: (1) A database layer that requires automated, immediate failover with zero data loss in the event of an Availability Zone outage. (2) A shared file storage system to host active image files that must be concurrently read and written by multiple Amazon EC2 instances across three Availability Zones. (3) An archiving solution for older images that requires retrieval in under 10 minutes for emergency cases. Which combination of storage and database configurations will meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure the database using Amazon RDS Multi-AZ DB clusters to provide automatic failover and synchronous replication across Availability Zones.; Use Amazon EFS as the shared file system for active image files, and archive historical images in Amazon S3 Glacier Flexible Retrieval using Expedited retrievals.

Answer

Configure the database using Amazon RDS Multi-AZ DB clusters to provide automatic failover and synchronous replication across Availability Zones, and use Amazon EFS as the shared file system for active image files while archiving historical images in Amazon S3 Glacier Flexible Retrieval using Expedited retrievals.
Deploying the database using Amazon RDS Multi-AZ DB clusters provides high availability, synchronous replication, and automated failover across multiple Availability Zones, which addresses the zero data loss and automated failover requirement. Utilizing Amazon EFS as a shared file system allows multiple EC2 instances to concurrently read and write files with high availability across three Availability Zones. Furthermore, archiving historical images in Amazon S3 Glacier Flexible Retrieval and using Expedited retrievals allows the company to meet the RTO requirement of under 10 minutes, as Expedited retrievals make data available within 1 to 5 minutes.

Step-by-Step Solution

1
Analyze the database resilience requirements: automated, immediate failover with zero data loss in the event of an AZ outage.
Identify Amazon RDS Multi-AZ DB clusters or standard Multi-AZ deployments as the correct choice since they support synchronous replication and automated failover.
To ensure high availability and prevent data loss during an AZ outage.
2
Analyze the shared storage requirements: active image files must be concurrently read/written by multiple EC2 instances across three AZs.
Identify Amazon EFS (Elastic File System) as the correct shared file system since it natively supports multi-AZ concurrent access.
EBS volumes cannot be mounted concurrently across multiple AZs under these constraints.
3
Analyze the archive retrieval requirements: historical images must be retrieved in under 10 minutes.
Select S3 Glacier Flexible Retrieval using Expedited retrievals, which completes in 1-5 minutes.
Standard retrievals take 3-5 hours, which violates the RTO target.

Key Concept

Designing resilient storage and database architectures involves matching application workloads with the correct storage service (e.g., EFS for concurrent multi-AZ file access) and retrieval configuration (e.g., Expedited retrievals for tight RTOs), while using Multi-AZ replication to ensure database resilience.
Estimated Time:2m 0s
Question 169Question →

An enterprise organization is migrating a high-volume PostgreSQL database to AWS. The application demands a multi-region disaster recovery architecture that can survive a complete AWS Region outage. The business specifies a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 2 minutes. Additionally, read requests from users in the recovery region must be served locally with sub-second latency to optimize user experience. Which combination of actions should a solutions architect recommend to satisfy these resilience and performance criteria? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create an Amazon Aurora PostgreSQL Global Database with the primary cluster located in the primary region and a secondary cluster in the recovery region.; In the event of a primary region outage, initiate a managed failover of the Aurora Global Database to promote the secondary cluster to primary.

Answer

Deploying an Amazon Aurora PostgreSQL Global Database and using managed failover during a regional outage satisfies the strict recovery and latency requirements.
Deploying an Amazon Aurora PostgreSQL Global Database ensures storage-level replication to the secondary region with lag typically below 1 second, which satisfies the sub-second RPO. The secondary cluster allows read requests in the backup region to be served locally with sub-second latency. In the event of a regional failure, initiating a managed failover promotes the secondary cluster to primary, maintaining the global database layout and meeting the RTO of under 2 minutes.

Step-by-Step Solution

1
Analyze recovery objectives and read latency constraints.
Identified RPO < 1 second, RTO < 2 minutes, and local read scaling in the recovery region.
This establishes the architectural boundary and eliminates low-performance backup or standard asynchronous replication models.
2
Evaluate database engine replication capabilities.
Amazon Aurora Global Database provides storage-level replication with lag under 1 second, supporting local read replicas in the secondary region.
Standard RDS replication has higher latency overhead and does not support native cross-region failover automation.
3
Identify failover mechanism to meet target RTO.
Managed failover of Aurora Global Database automates the promotion of the secondary cluster with minimal disruption.
Manual promotion of replicas takes longer and breaks the global database replication topology.

Key Concept

High availability and disaster recovery design using Amazon Aurora Global Databases.
Question 170Question →

A logistics company is designing the database architecture for a global fleet tracking system. The system uses a PostgreSQL database located in the eu-west-1 Region, with a disaster recovery (DR) target in the ap-southeast-1 Region. The system has a strict Recovery Time Objective (RTO) of under 5 minutes and a Recovery Point Objective (RPO) of under 1 minute. Local regional offices in the Asia-Pacific region must also run read-only telemetry reports with low latency, without affecting write performance in Europe.

Which database configuration will meet these requirements with the minimum operational complexity?

Show answer & explanation

Answer: Configure an Amazon Aurora PostgreSQL Global Database with the primary cluster in the eu-west-1 Region and a secondary cluster in the ap-southeast-1 Region. Use the secondary cluster's local endpoints for the Asia-Pacific telemetry reports, and perform a managed failover to promote the secondary cluster if the primary region fails.

Answer

Configure an Amazon Aurora PostgreSQL Global Database with the primary cluster in the eu-west-1 Region and a secondary cluster in the ap-southeast-1 Region. Use the secondary cluster's local endpoints for the Asia-Pacific telemetry reports, and perform a managed failover to promote the secondary cluster if the primary region fails.
The configuration utilizing Amazon Aurora Global Database is correct because it uses storage-level replication to achieve cross-region replication lag of less than 1 second, fulfilling the 1-minute RPO requirement. Furthermore, it supports managed failover, which promotes the secondary region to primary in less than a minute, meeting the 5-minute RTO. The local cluster in ap-southeast-1 provides local read endpoints for reporting workloads, keeping read latencies low and isolating reporting performance from primary write workloads.

Step-by-Step Solution

1
Analyze the disaster recovery constraints (RTO < 5 minutes, RPO < 1 minute).
Identify that the solution must support sub-minute replication lag (for RPO) and rapid failover (for RTO) across AWS Regions.
This rules out snapshot-based recovery (which has RTO in hours and RPO determined by snapshot intervals) and standard RDS replica promotion (which is manual and slow).
2
Analyze the read scalability and latency requirements (local Asia-Pacific reports with low latency, no impact on write performance).
Determine that a local read replica or secondary read-only database cluster must be placed in ap-southeast-1.
Routing read queries across regions from ap-southeast-1 to eu-west-1 would introduce unacceptable network latency.
3
Evaluate Amazon Aurora Global Database capabilities against the requirements.
Aurora Global Database replicates data storage-to-storage with a typical lag of under 1 second (meeting the RPO of < 1 minute) and supports managed failover with RTO of under 1 minute.
Aurora Global Database is the native AWS feature designed exactly for multi-region resilience and local read scaling under strict RTO/RPO limits.

Key Concept

Amazon Aurora Global Database provides storage-based cross-region replication for low-latency local reads, sub-minute replication lag, and rapid managed regional failover to meet strict RTO/RPO requirements.
Estimated Time:3m 0s
Question 171Question →

A company is hosting a web application on multiple Amazon EC2 instances distributed across different Availability Zones. The application requires a highly available, shared file storage system where all EC2 instances can concurrently read and write uploaded user media files. Which storage solution should a solutions architect recommend to meet these requirements?

Show answer & explanation

Answer: Amazon Elastic File System (Amazon EFS)

Answer

Amazon Elastic File System (Amazon EFS)
Amazon Elastic File System (Amazon EFS) provides serverless, highly available, and resilient network file storage that can be concurrently mounted by EC2 instances across multiple Availability Zones via standard NFSv4 protocols.

Step-by-Step Solution

1
Analyze the storage requirements of the application.
The application needs shared file-level storage (not block or database) that supports concurrent read/write operations from multiple EC2 instances across multiple Availability Zones.
Identifying the data access pattern (concurrent file access) and geographic requirement (multi-AZ) helps narrow down the service options.
2
Compare the capabilities of available AWS storage services against these requirements.
Amazon Elastic File System (Amazon EFS) is built for POSIX-compliant shared file access across multiple Availability Zones concurrently, while EBS is block storage, S3 Glacier is for archives, and RDS is for structured relational data.
Choosing the service that matches both the concurrent file sharing model and the high availability needs is required for a resilient architecture.

Key Concept

Selecting highly available shared file storage for concurrent multi-instance access across multiple Availability Zones
Estimated Time:45s
Question 172Question →

A logistics company is migrating its core shipment tracking system to AWS. The application uses a PostgreSQL database and must be resilient to a complete AWS Region outage. The solutions architect must design a disaster recovery (DR) strategy with a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 10 seconds. Which configuration meets these requirements with the least operational overhead?

Show answer & explanation

Answer: Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in the active Region and a secondary cluster in the recovery Region, using cross-Region replication.

Answer

Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in the active Region and a secondary cluster in the recovery Region, using cross-Region replication.
The correct configuration uses Amazon Aurora Global Databases, which feature built-in, storage-based replication across AWS Regions. It achieves an RPO of less than 10 seconds because replication lag is typically less than one second. The secondary cluster can be promoted to a primary cluster with full read/write capabilities in less than 15 minutes, satisfying the RTO requirement with minimal operational overhead.

Step-by-Step Solution

1
Analyze RTO and RPO requirements.
RTO must be under 15 minutes, and RPO must be under 10 seconds. This demands a warm standby or active-passive cross-region database replication mechanism with sub-second replication lag.
Traditional backup and restore methods take too long to restore (exceeding RTO) and have data loss intervals larger than 10 seconds (exceeding RPO).
2
Evaluate cross-region capabilities of Amazon RDS vs. Amazon Aurora.
Amazon Aurora Global Database replicates data at the storage layer with typical latency of less than one second, allowing an RPO of under 10 seconds. It also supports quick promotion of secondary clusters (RTO under 15 minutes).
Amazon RDS for PostgreSQL cross-region replicas use logical/physical replication at the engine level, which incurs more overhead, and promotion requires custom orchestration.
3
Select the option that minimizes operational overhead.
Amazon Aurora Global Database is fully managed and requires no custom scripting to handle replication and failover promotion.
Using Aurora Global Database is the most native and reliable way to meet both strict RTO/RPO limits and minimize management complexity.

Key Concept

Disaster recovery replication and failover constraints for managed relational databases on AWS
Question 173Question →

A clinical diagnostics company operates a containerized genomic analysis pipeline on Amazon Elastic Kubernetes Service (Amazon EKS) in the `eu-west-1` Region. The pipeline requires a shared, POSIX-compliant file storage layer that provides latencies of less than 11 millisecond for active DNA sequence processing, supports concurrent read/write access from hundreds of active pods across 33 Availability Zones, and guarantees a Recovery Point Objective (RPO) of 00 and a Recovery Time Objective (RTO) of near 00 in the event of an Availability Zone outage. For compliance, a copy of the processed genomic datasets must be archived in the `eu-central-1` Region with an RPO of less than 1515 minutes. If a disaster occurs in the primary Region, the archived datasets must be accessible in `eu-central-1` within a recovery RTO of 55 minutes. Which combination of storage configurations will meet these resilience and recovery requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure an Amazon Elastic File System (Amazon EFS) using the Regional (Standard) storage class in the primary Region.; Configure Amazon EFS Replication to asynchronously copy the file system to a destination EFS file system in the secondary Region.

Answer

Configure an Amazon Elastic File System (Amazon EFS) using the Regional (Standard) storage class in the primary Region, and configure Amazon EFS Replication to asynchronously copy the file system to a destination EFS file system in the secondary Region.
To build a highly available and resilient shared file system that supports POSIX-compliant operations with sub-millisecond latencies across multiple Availability Zones, the Regional (Standard) storage class of Amazon EFS must be used. To replicate this shared file system to a secondary Region while satisfying an RPO of under 1515 minutes and a recovery RTO of under 55 minutes, Amazon EFS Replication is the native feature that continuously synchronizes data and keeps the destination file system mount-ready.

Step-by-Step Solution

1
Evaluate the primary storage requirements for POSIX compliance, sub-millisecond latencies, and Multi-AZ concurrency.
Identify that Amazon EFS Regional (Standard) storage class is required to allow hundreds of pods to read/write concurrently across 33 Availability Zones.
EFS provides native POSIX-compliant shared file storage with automatic failover and replication across multiple Availability Zones in a Region, ensuring an RPO of 00 and near-zero RTO.
2
Determine the optimal cross-region replication method that satisfies the 1515-minute RPO and 55-minute recovery RTO.
Select Amazon EFS Replication to copy data to a destination EFS file system in the secondary Region.
EFS Replication is a fully managed, native feature that replicates changes asynchronously within minutes (meeting the 1515-minute RPO) and keeps the destination file system ready to mount immediately (meeting the 55-minute recovery RTO).

Key Concept

Amazon EFS Regional storage provides automatic Multi-AZ failover with zero data loss, while Amazon EFS Replication enables managed, low-latency cross-region disaster recovery.
Estimated Time:3m 0s
Question 174Question →

A company runs an application with a database backend on an Amazon RDS for PostgreSQL DB instance. The solutions architect must configure the database to achieve high availability with automatic failover (Recovery Time Objective under 2 minutes) in the event of an Availability Zone outage. Additionally, the application requires read scaling to handle reporting queries during peak hours without impacting the performance of the write database. Which two database configurations should the solutions architect choose to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy the RDS PostgreSQL DB instance as a Multi-AZ deployment.; Create one or more RDS Read Replicas to offload reporting queries.

Answer

Deploying the Amazon RDS PostgreSQL DB instance in a Multi-AZ configuration to support automatic failover and creating one or more RDS Read Replicas to handle reporting read queries.
To satisfy both requirements, the solutions architect must configure a Multi-AZ deployment to handle high availability and automatic failover in under 2 minutes, and create read replicas to handle the reporting read workload.

Step-by-Step Solution

1
Address the high availability and quick failover constraint.
An Amazon RDS Multi-AZ deployment is selected because it replicates data synchronously to a standby instance in a different Availability Zone and performs automatic failover when the primary instance fails.
This configuration provides an RTO of under 2 minutes without administrative intervention.
2
Address the read scaling performance constraint.
RDS Read Replicas are selected to host reporting queries.
By redirecting read traffic to the read replicas, the primary database's performance is preserved for write operations.

Key Concept

Configuring Amazon RDS for high availability using Multi-AZ deployments, and scaling read workloads separately using Read Replicas.
Question 175Question →

A financial auditing firm must store historical transaction logs. The logs require 99.999999999% durability and must be highly resilient across multiple Availability Zones. The recovery time objective (RTO) for retrieving these logs is less than 10 minutes when an audit request is received. The solution must be highly cost-effective. Which two AWS storage configurations will meet these requirements? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Store the logs in Amazon S3 Glacier Instant Retrieval to get millisecond retrieval times and multi-AZ durability.; Store the logs in Amazon S3 Standard-Infrequent Access (S3 Standard-IA) to ensure immediate retrieval and multi-AZ resilience.

Answer

Storing the logs in Amazon S3 Glacier Instant Retrieval and storing the logs in Amazon S3 Standard-Infrequent Access (S3 Standard-IA).
Storing logs in S3 Glacier Instant Retrieval and S3 Standard-IA are the correct options because both storage classes provide 99.999999999% durability across multiple Availability Zones, support millisecond retrieval times (well within the 10-minute RTO), and represent cost-optimized tiers for infrequently accessed log files.

Step-by-Step Solution

1
Identify the durability and resilience requirements.
The logs require 99.999999999% durability and must be highly resilient across multiple Availability Zones. This rules out single-AZ storage classes like S3 One Zone-IA.
This establishes the baseline requirements for multi-AZ availability and durability.
2
Evaluate the recovery time objective (RTO).
The RTO is under 10 minutes, meaning standard or bulk retrieval options in Glacier (which take hours) are unacceptable.
This rules out Glacier Flexible Retrieval standard options which take hours, requiring millisecond or expedited access.
3
Compare the eligible S3 storage tiers and configurations.
S3 Glacier Instant Retrieval and S3 Standard-IA both meet the multi-AZ resilience, high durability, and millisecond retrieval requirements while offering lower storage costs compared to S3 Standard.
Selecting the two configurations that align with all metrics while remaining cost-optimized.

Key Concept

Selecting highly available, resilient, and cost-effective storage options that meet strict RTO constraints.
Question 176Question →

A financial services company is hosting a transaction auditing application on Amazon EC2 instances distributed across three Availability Zones in a single AWS Region. The application requires a shared file system that can be accessed concurrently by all EC2 instances to read and write active audit files. The storage solution must be highly resilient within the Region. Additionally, the company requires a disaster recovery (DR) architecture for this shared storage in a secondary Region with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 30 minutes. Which combination of storage configurations will meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Use Amazon Elastic File System (Amazon EFS) with the Regional storage class to provide shared file storage within the primary Region.; Configure Amazon EFS Replication to replicate the shared file system to a secondary AWS Region to meet the disaster recovery requirements.

Answer

Use Amazon Elastic File System (Amazon EFS) with the Regional storage class, and configure Amazon EFS Replication to replicate the shared file system to a secondary AWS Region.
Using Amazon EFS with the Regional storage class ensures that files are stored redundantly across multiple Availability Zones, offering high resilience and allowing all EC2 instances to read and write concurrently. Setting up Amazon EFS Replication replicates data to a secondary Region automatically, meeting the 15-minute RPO and allowing access within the 30-minute RTO.

Step-by-Step Solution

1
Determine the shared storage requirements within the primary Region.
Identify that the EC2 instances are distributed across three Availability Zones and require simultaneous read/write access to the same file system, directing the choice to Amazon EFS with the Regional storage class.
Amazon EFS Regional storage class provides concurrent access from multiple AZs and replicates data across them for high resilience.
2
Address the disaster recovery constraints for the secondary Region.
Evaluate replication mechanisms to achieve a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 30 minutes, selecting Amazon EFS Replication.
Amazon EFS Replication continuously replicates file system changes to a secondary Region automatically, maintaining low latency synchronization to support quick failover.

Key Concept

Designing highly available and resilient shared storage architectures using Amazon EFS Regional storage and cross-Region replication.
Question 177Question →

A financial services firm is deploying a web-based client portal. The portal uses an Amazon RDS DB instance to store transaction records. The database must remain highly available during a database instance failure or an Availability Zone outage, with automatic failover to a standby instance without manual intervention. Which Amazon RDS configuration should a solutions architect recommend to meet these requirements?

Show answer & explanation

Answer: Configure the Amazon RDS DB instance to use a Multi-AZ deployment.

Answer

Configure the Amazon RDS DB instance to use a Multi-AZ deployment.
Configuring the Amazon RDS DB instance to use a Multi-AZ deployment is the standard method for achieving high availability on AWS. It replicates data synchronously to a standby instance in a different Availability Zone and automatically updates DNS records to point to the standby during a failure, ensuring automatic failover with no manual intervention.

Step-by-Step Solution

1
Identify the high availability and automatic failover requirements.
The solution must handle an Availability Zone or instance failure automatically without manual intervention.
This establishes the need for a synchronous database configuration that supports automatic failover.
2
Evaluate the capabilities of Amazon RDS Multi-AZ deployments.
RDS Multi-AZ creates a synchronous standby replica in a separate Availability Zone and handles automatic failover if the primary fails.
This matches all stated requirements for resilience and automation.
3
Exclude options that do not support automatic failover or high availability.
Read replicas require manual promotion, pilot light is a disaster recovery pattern with high recovery time, and Route 53 latency routing does not replicate database state.
These alternatives fail to meet either the high availability or the zero-manual-intervention constraints.

Key Concept

Amazon RDS Multi-AZ deployments provide automatic failover and synchronous replication for high availability across different Availability Zones.
Estimated Time:1m 0s
Question 178Question →

An enterprise inventory management application uses Amazon Aurora PostgreSQL as its database engine. The application has strict resiliency requirements: it must achieve high availability within the primary AWS Region with a recovery time objective (RTO) of less than 30 seconds and a recovery point objective (RPO) of zero. Furthermore, for disaster recovery, the database must be replicated to a secondary AWS Region with an RPO of less than 5 seconds and an RTO of less than 15 minutes.

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

Select all that apply

Show answer & explanation

Answer: Configure the database as an Amazon Aurora DB cluster in the primary region with one or more Aurora Replicas in different Availability Zones.; Use Amazon Aurora Global Databases to replicate the database cluster to the secondary AWS Region.

Answer

To meet the requirements, configure the database as an Amazon Aurora DB cluster in the primary region with one or more Aurora Replicas in different Availability Zones, and use Amazon Aurora Global Databases to replicate the database cluster to the secondary region.
To achieve high availability with an RTO under 30 seconds and RPO of zero in the primary region, deploying an Amazon Aurora DB cluster with one or more Aurora Replicas across different Availability Zones is required. Failover to an Aurora Replica typically completes in less than 30 seconds, and because all instances share the same virtual storage volume, no data is lost. For disaster recovery to a secondary region with an RPO under 5 seconds and RTO under 15 minutes, using Amazon Aurora Global Databases is the appropriate choice. It uses dedicated storage replication with lag typically under 1 second and can be promoted to a primary cluster in minutes.

Step-by-Step Solution

1
Analyze primary region high availability requirements.
Identify that the primary region requires an RTO of less than 30 seconds and an RPO of zero.
An Amazon Aurora DB cluster with one or more replicas across different Availability Zones provides automatic failover in less than 30 seconds with zero data loss, satisfying the primary region HA constraints.
2
Analyze cross-region disaster recovery requirements.
Identify that the secondary region requires an RPO of less than 5 seconds and an RTO of less than 15 minutes.
Amazon Aurora Global Databases use storage-based physical replication that replicates data in less than 1 second (RPO under 5 seconds) and supports fast failover/promotion of the secondary cluster in less than 1 minute (RTO under 15 minutes).

Key Concept

Amazon Aurora high availability configurations and disaster recovery options using Global Databases.
Question 179Question →

An IoT-connected vehicle telemetry platform processes real-time diagnostics data using Amazon EC2 instances distributed across three Availability Zones. The application requires a shared file storage layer that supports POSIX-compliant file operations, concurrent access from all EC2 instances, and sub-millisecond latencies. Additionally, the business requires a disaster recovery (DR) solution in a secondary AWS Region with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 5 minutes. Which combination of storage 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 using the Standard storage class and configure mount targets in each Availability Zone.; Configure Amazon EFS Replication to replicate the file system to a destination Amazon EFS file system in the secondary AWS Region.

Answer

Creating an Amazon EFS file system with the Standard storage class across multiple Availability Zones combined with Amazon EFS Replication to a secondary AWS Region.
The combination of deploying Amazon EFS with the Standard storage class and configuring EFS Replication meets all requirements. Amazon EFS provides the necessary POSIX compliance and allows concurrent access from EC2 instances in multiple Availability Zones. Configuring EFS Replication to a secondary region replicates data within minutes, fulfilling the 15-minute RPO, and the destination file system is instantly mountable, satisfying the 5-minute RTO.

Step-by-Step Solution

1
Select a shared file system that supports POSIX compliance and concurrent access across multiple Availability Zones.
Choose Amazon Elastic File System (Amazon EFS) with the Standard storage class.
Amazon EFS Standard is designed for Multi-AZ deployments and supports concurrent access from EC2 instances across multiple Availability Zones with low latency, unlike EBS volumes which are locked to a single AZ.
2
Choose a replication mechanism that achieves a low Recovery Point Objective (RPO) and Recovery Time Objective (RTO) in a secondary AWS Region.
Enable Amazon EFS Replication to a destination file system in the secondary AWS Region.
Amazon EFS Replication replicates data asynchronously to a secondary region, achieving an RPO of minutes and an RTO of minutes since the destination file system is already active and ready to mount.

Key Concept

Multi-AZ shared file storage with low latency combined with sub-minute regional replication.
Question 180Question →

A digital marketing agency runs a media processing application on Amazon EC2 instances distributed across multiple Availability Zones in the us-east-1 Region. The application requires a shared file storage solution that offers at least 99.99%99.99\% availability and high durability for active assets. Additionally, the architecture must support a Recovery Time Objective (RTO) of near-zero minutes and a Recovery Point Objective (RPO) of 00 for all active editing sessions. The storage must allow simultaneous read and write access from all EC2 instances across the Availability Zones. Which storage solution should a solutions architect recommend to meet these requirements?

Show answer & explanation

Answer: Configure an Amazon EFS file system using the Standard storage class to mount across all EC2 instances.

Answer

Configure an Amazon EFS file system using the Standard storage class to mount across all EC2 instances.
Amazon EFS is a fully managed, shared file system designed to be highly resilient and available across multiple Availability Zones. The Standard storage class replicates data across multiple AZs in a Region, ensuring high durability, 99.99%99.99\% availability, and immediate, concurrent read/write access. This fulfills the near-zero RTO and RPO requirements for active media editing sessions.

Step-by-Step Solution

1
Identify the storage access requirements for the application.
The application requires shared file storage that allows simultaneous read/write access from multiple EC2 instances distributed across different Availability Zones.
This rules out standard Amazon EBS volumes, which are restricted to a single Availability Zone and do not support multi-instance mounting across AZ boundaries.
2
Evaluate the recovery objectives (RTO and RPO) and availability targets.
The solution must deliver at least 99.99%99.99\% availability, a near-zero RTO, and an RPO of 00.
Amazon EFS Standard synchronously replicates data across multiple Availability Zones, ensuring high resilience, instant failover, and zero data loss in the event of an AZ disruption.
3
Select the correct service class and eliminate sub-optimal storage classes.
Amazon EFS Standard is selected, as archive solutions like Amazon S3 Glacier introduce retrieval latency that violates the near-zero RTO.
EFS Standard satisfies all constraints of shared access, high durability, high availability, and instant availability of data.

Key Concept

Amazon EFS provides highly available, multi-AZ elastic file storage that supports concurrent read/write operations from multiple EC2 instances, meeting strict recovery objectives (RTO/RPO) for shared active file systems.
PreviousPage 9 / 20Next