Design Resilient Architectures

382 questions

All types382 Multiple choice195 Multiple select187

A solutions architect is configuring an active-passive disaster recovery (DR) strategy for a simple web application using Amazon Route 53. The primary endpoint is located in the us-east-1 Region, and the secondary backup endpoint is located in the us-west-2 Region. Which two configurations are required to set up this active-passive failover? (Select TWO.)

Select all that apply

Create a primary failover record pointing to the primary endpoint in us-east-1 and associate a Route 53 health check with it

Create a secondary failover record pointing to the secondary endpoint in us-west-2

Create latency routing records pointing to both endpoints to handle failover based on the lowest network latency

Associate a Route 53 health check directly with an RDS read replica in the secondary Region to automatically promote it to primary

Configure the secondary failover record with an automated action to boot and scale up the backup EC2 instances upon failover detection

Show answer & explanation

Answer: Create a primary failover record pointing to the primary endpoint in us-east-1 and associate a Route 53 health check with it; Create a secondary failover record pointing to the secondary endpoint in us-west-2

Answer

To configure Route 53 active-passive failover, you must create a primary failover record pointing to the primary endpoint in us-east-1 and associate a Route 53 health check with it, and also create a secondary failover record pointing to the secondary endpoint in us-west-2.

For an active-passive failover configuration, a primary failover record pointing to the primary endpoint must be created and linked to a Route 53 health check. This health check monitors the primary site. A secondary failover record pointing to the standby endpoint must also be configured. When the health check determines the primary site is down, Route 53 stops sending traffic to the primary record and starts resolving queries to the secondary record.

Step-by-Step Solution

Identify the primary active endpoint and the backup standby endpoint for the disaster recovery strategy.

The primary active endpoint is in us-east-1, and the secondary standby endpoint is in us-west-2.

This establishes the active-passive relationship where all normal traffic goes to us-east-1, and traffic only switches to us-west-2 during a disaster.

Create and configure a primary failover record in Route 53.

A record pointing to the us-east-1 endpoint with its routing policy set to Failover and failover type set to Primary, associated with a Route 53 health check.

Route 53 needs a health check associated with the primary record to monitor its availability and determine when to trigger failover.

Create and configure a secondary failover record in Route 53.

A record pointing to the us-west-2 endpoint with its routing policy set to Failover and failover type set to Secondary.

This record serves as the backup target. Route 53 only resolves queries to this record when the primary endpoint is determined to be unhealthy.

Key Concept

Route 53 Failover Routing Policy (Active-Passive)

Estimated Time:1m 0s

Question 202Question →

An enterprise document management SaaS provider stores customer contract PDFs in an Amazon S3 bucket. The business requirements specify that:

- Files must be highly available and resilient against a single Availability Zone (AZ) failure, with a Recovery Time Objective (RTO) of less than $1$ minute.
- Any files deleted or modified must be recoverable immediately.
- For disaster recovery, a copy of the contracts must be replicated to a secondary AWS Region with an RTO of less than $15$ minutes and a Recovery Point Objective (RPO) of less than $15$ minutes.
- Contracts are highly active for the first $45$ days and must be transitioned to a cheaper storage class afterward, while remaining instantly accessible.

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

Select all that apply

Enable Amazon S3 Versioning on the bucket and configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to the secondary Region.

Configure an S3 Lifecycle policy to transition objects from Amazon S3 Standard to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after

45

days.

Configure an S3 Lifecycle policy to transition objects to Amazon S3 Glacier Flexible Retrieval after

45

days, using Standard retrievals to meet recovery objectives in the secondary Region.

Provision Amazon EBS volumes attached to EC2 instances using Multi-Attach, and configure secondary Region replication using automated hourly EBS snapshots.

Deploy Amazon RDS read replicas in the secondary Region to replicate storage blocks synchronously and manage failover coordinates.

Show answer & explanation

Answer: Enable Amazon S3 Versioning on the bucket and configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to the secondary Region.; Configure an S3 Lifecycle policy to transition objects from Amazon S3 Standard to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after $45$ days.

Answer

Enable Amazon S3 Versioning on the bucket, configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to the secondary Region, and configure an S3 Lifecycle policy to transition objects from Amazon S3 Standard to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after 45 days.

The solution requires a combination of Amazon S3 Versioning, S3 Cross-Region Replication (CRR) with Replication Time Control (S3 RTC), and S3 Standard-IA lifecycle transition. S3 Versioning ensures that any overwrite or deletion can be immediately rolled back, fulfilling the immediate recovery requirement. S3 RTC guarantees that 99.9% of new uploads are replicated to the secondary Region within 15 minutes, satisfying the disaster recovery RPO and RTO. Transitioning objects to S3 Standard-IA after 45 days is optimal because S3 Standard-IA stores data redundantly across multiple Availability Zones (maintaining high availability and sub-minute RTO) and supports millisecond retrieval times (instant access) while saving cost.

Step-by-Step Solution

Select a mechanism for immediate file recovery.

Amazon S3 Versioning is enabled to store multiple versions of objects, allowing instant recovery of deleted or overwritten documents.

This directly satisfies the requirement that deleted or modified files must be recoverable immediately.

Select a replication mechanism that meets the disaster recovery constraints.

Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) is selected.

S3 RTC guarantees replication of 99.9% of objects within 15 minutes, fulfilling the secondary Region's RPO/RTO constraints of under 15 minutes.

Determine the appropriate cost-effective storage tier transition.

A lifecycle policy transitions files to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after 45 days.

S3 Standard-IA maintains multi-AZ resilience and provides millisecond (instantaneous) retrieval times, keeping files available under the 1-minute RTO, while reducing cost after the active 45-day period.

Key Concept

Designing a resilient, multi-AZ and multi-region storage architecture using Amazon S3 features including versioning, lifecycle transitions to Standard-IA, and Replication Time Control (S3 RTC).

Question 203Question →

A multinational e-commerce company serves a dynamic product recommendation API to users globally. The API is hosted on Application Load Balancers (ALBs) in two AWS Regions: a primary region in eu-west-1 and a secondary standby region in us-east-1. The company uses an Amazon CloudFront distribution to cache recommendation payloads at edge locations. To ensure high availability, the company needs to configure automated failover to the secondary region's ALB only if the primary ALB returns HTTP 502 (Bad Gateway) or HTTP 503 (Service Unavailable) status codes. The solution must minimize operational complexity, maintain edge caching benefits, and avoid client-side DNS propagation delays. Which architecture should a solutions architect recommend to meet these requirements?

Configure a CloudFront Origin Group containing the primary ALB as the primary origin and the secondary ALB as the failover origin, setting the failover criteria to include HTTP 502 and 503 status codes.

Configure an Amazon Route 53 latency routing policy with health checks to resolve the API domain name to either the primary or secondary ALB directly, bypassing CloudFront caching.

Associate an AWS WAF Web ACL with the CloudFront distribution, and configure a custom rule to intercept HTTP 502 and 503 responses from the primary ALB and rewrite the origin request header to the secondary ALB.

Configure the CloudFront distribution behavior to set the minimum, maximum, and default TTL values to zero, and configure CloudFront custom error pages for HTTP 502 and 503 responses to redirect to the secondary ALB.

Show answer & explanation

Answer: Configure a CloudFront Origin Group containing the primary ALB as the primary origin and the secondary ALB as the failover origin, setting the failover criteria to include HTTP 502 and 503 status codes.

Answer

The correct solution uses an Amazon CloudFront Origin Group containing the primary ALB as the primary origin and the secondary ALB as the failover origin, configured to trigger failover on 502 and 503 status codes. This ensures that CloudFront automatically and transparently redirects requests to the secondary region if the primary region encounters server issues, maintaining edge caching for successful requests and avoiding DNS-based failover delays.

Step-by-Step Solution

Analyze the requirements for low-latency delivery, high availability, edge caching preservation, and failover based on backend HTTP 502/503 status codes.

The solution must leverage CloudFront to maintain edge caching and fail over to a backup ALB without relying on DNS-based redirection, which introduces propagation delays.

This establishes the architectural boundary where caching must remain active at the edge, and failover must occur dynamically at the CDN layer.

Evaluate Amazon CloudFront Origin Groups as the native mechanism for origin failover.

An Origin Group allows grouping a primary origin (primary ALB) and a secondary origin (secondary ALB), with automated failover triggered when the primary origin returns specific HTTP status codes.

This directly meets the failover criteria (HTTP 502 and 503) with minimal operational overhead and near-instant failover.

Assess and eliminate alternative solutions such as Route 53 routing, AWS WAF, and TTL reduction.

Route 53 bypasses CloudFront caching; AWS WAF cannot route origins; TTL reduction to zero disables edge caching completely.

This confirms that only the Origin Group option achieves all design constraints (resiliency, performance, and low operational complexity).

Key Concept

Implementing Amazon CloudFront Origin Groups for automated origin-level failover of dynamic HTTP endpoints.

Question 204Question →

A company is building an online auction application where users submit bids in real time. The backend database experiences write performance issues during high-traffic spikes at the end of auctions. To ensure fairness, the bids must be processed in the exact order they are received by the application. A solutions architect needs to design a decoupled architecture that buffers incoming bids and processes them sequentially. Which solution meets these requirements with the least operational overhead?

Send the incoming bids to an Amazon SQS Standard queue and configure the backend service to consume and process the messages sequentially.

Write the incoming bids directly to an Amazon RDS Read Replica to buffer the write traffic before replicating the data to the primary database.

Send the incoming bids to an Amazon SQS FIFO queue and configure the backend service to consume and process the messages sequentially.

Configure a continuous, long-running AWS Lambda function to poll the application servers and write the bids directly to the primary database.

Show answer & explanation

Answer: Send the incoming bids to an Amazon SQS FIFO queue and configure the backend service to consume and process the messages sequentially.

Answer

Send the incoming bids to an Amazon SQS FIFO queue and configure the backend service to consume and process the messages sequentially.

The correct solution uses an Amazon SQS FIFO queue to buffer incoming write requests (bids) and ensure they are processed in the exact order they are received. SQS FIFO queues guarantee first-in, first-out delivery and exactly-once processing, which is required for determining the auction winner fairly, while decoupling the frontend from the database to handle traffic spikes.

Step-by-Step Solution

Identify the key requirements from the scenario.

The solution must decouple the application from the database, handle write spikes, and process bids in the exact order they are received.

This establishes the constraints that any valid architecture must satisfy.

Evaluate the messaging service that provides decoupling and order preservation.

Amazon SQS FIFO (First-In-First-Out) queues guarantee that messages are processed in the exact order they are sent, while also providing a buffer to decouple the frontend from the backend database.

Standard queues do not guarantee ordering, making FIFO the correct choice for ordering requirements.

Eliminate options that do not support writes or decouple the architecture effectively.

RDS Read Replicas cannot accept writes, and a continuous Lambda function violates serverless design principles and fails to provide reliable buffer-based decoupling.

This confirms that the SQS FIFO queue is the only solution that meets all constraints with minimal operational overhead.

Key Concept

Decoupling with ordered messaging using Amazon SQS FIFO queues

Question 205Question →

An e-commerce company is migrating its primary transactional database to Amazon RDS for MySQL. The database design must meet the following operational requirements:

* Within the primary AWS Region, the database must support automatic failover with a Recovery Time Objective (RTO) of less than $40$ seconds.
* The architecture must allow read workloads to scale horizontally across multiple Availability Zones in the primary Region without querying the primary writer instance.
* For disaster recovery, the database must support cross-Region replication to a secondary Region with a Recovery Point Objective (RPO) of less than $15$ minutes.

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

Deploy an Amazon RDS Multi-AZ DB cluster containing one primary writer and two readable standby instances across three Availability Zones. Configure an asynchronous cross-Region read replica in the secondary Region.

Deploy an Amazon RDS Multi-AZ DB instance containing one primary writer and one non-readable standby instance. Create two read replicas in the primary Region for read scaling, and create a cross-Region read replica. Configure Amazon Route 53 latency-based routing to automatically redirect write traffic to the read replicas if the primary writer fails.

Deploy an Amazon RDS Single-AZ DB instance with two read replicas in the primary Region and one cross-Region read replica in the secondary Region. Configure Route 53 failover routing with active-passive health checks to automatically promote a primary Region read replica to master if the Single-AZ instance fails.

Deploy an Amazon RDS Multi-AZ DB instance in the primary Region. Configure AWS Backup to perform cross-Region replication of the database snapshots to the secondary Region every

12

hours. Restore the database from the copied snapshot in the secondary Region during a disaster recovery scenario.

Show answer & explanation

Answer: Deploy an Amazon RDS Multi-AZ DB cluster containing one primary writer and two readable standby instances across three Availability Zones. Configure an asynchronous cross-Region read replica in the secondary Region.

Answer

The configuration utilizing an Amazon RDS Multi-AZ DB cluster satisfies all operational requirements. It provides a primary writer and two readable standby instances across three Availability Zones. Failover in a Multi-AZ DB cluster is typically completed in under

35

seconds (meeting the

40

-second RTO limit). Additionally, because both standby instances are readable, the application can scale read workloads without querying the primary writer. A cross-Region read replica provides asynchronous, near-real-time replication, meeting the RPO of less than

15

minutes.

Step-by-Step Solution

Analyze the local high availability and RTO requirement.

An RTO of less than

40

seconds rules out standard RDS Multi-AZ DB instances (which take

60

120

seconds to failover) and Single-AZ instances. An RDS Multi-AZ DB cluster uses semi-synchronous replication with a failover time of under

35

seconds, meeting the target.

Determining the correct local deployment configuration is critical to meeting the low RTO threshold.

Evaluate the read-scaling requirement in the primary Region.

Standard RDS Multi-AZ DB instances have a passive, non-readable standby. An RDS Multi-AZ DB cluster features two readable standby instances that can serve read traffic directly, reducing operational complexity compared to provisioning separate read replicas.

Identifying the scaling capabilities of readable standby instances versus passive standby instances ensures read requirements are met efficiently.

Evaluate the cross-Region disaster recovery and RPO requirement.

An RPO of less than

15

minutes requires continuous or near-continuous replication. An asynchronous cross-Region read replica continuously replicates data from the primary cluster, providing a low RPO (usually seconds). Replicating snapshots every

12

hours fails this RPO.

Verifying the replication mechanism ensures the RPO constraint is satisfied.

Key Concept

Selecting between Amazon RDS Multi-AZ DB instances, Multi-AZ DB clusters, and cross-Region read replicas to satisfy strict RTO, RPO, and read scaling requirements.

Estimated Time:2m 30s

Question 206Question →

A geographic information system (GIS) platform processes real-time satellite imagery using a fleet of Amazon EC2 instances launched in an Auto Scaling group across multiple Availability Zones. The instances require a highly available, shared file system that supports simultaneous read and write access with sub-millisecond latencies to coordinate mapping files. Additionally, the raw images must be backed up to a secondary AWS Region to comply with disaster recovery policies. The system must achieve a Recovery Point Objective (RPO) of $15$ minutes and a Recovery Time Objective (RTO) of $10$ minutes.

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

Select all that apply

Configure an Amazon Elastic File System (Amazon EFS) file system to store the active mapping files, and mount it on the EC2 instances in each Availability Zone.

Store the raw images in an Amazon S3 bucket, and configure Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to the secondary Region.

Attach an Amazon Elastic Block Store (Amazon EBS) gp3 volume with Multi-Attach enabled to the EC2 instances across the Availability Zones to serve as the shared file system.

Store the raw images in an Amazon S3 bucket, and configure an S3 Lifecycle policy to transition the backup data to S3 Glacier Flexible Retrieval in the secondary Region.

Deploy a secondary Amazon RDS database instance in the secondary Region as a read replica, and configure it as the primary failover target for raw image storage.

Show answer & explanation

Answer: Configure an Amazon Elastic File System (Amazon EFS) file system to store the active mapping files, and mount it on the EC2 instances in each Availability Zone.; Store the raw images in an Amazon S3 bucket, and configure Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to the secondary Region.

Answer

Configuring an Amazon EFS file system to store active mapping files and storing raw images in an Amazon S3 bucket with Cross-Region Replication (CRR) and S3 Replication Time Control (S3 RTC) enabled.

The correct configurations combine Amazon EFS and Amazon S3 with Cross-Region Replication (CRR) and S3 Replication Time Control (S3 RTC). Amazon EFS provides a serverless, highly available shared network file system that supports concurrent read and write access for EC2 instances across multiple Availability Zones with sub-millisecond latencies. Amazon S3 CRR with S3 RTC enabled replicates

99\%

of objects to a secondary AWS Region within

15

minutes, fulfilling the

15

-minute RPO. Because the replicated files are immediately readable in the destination bucket, the solution also easily meets the

10

-minute RTO.

Step-by-Step Solution

Analyze the active shared file system requirements.

The file system must be accessible concurrently by multiple EC2 instances across different Availability Zones with low latency.

This identifies Amazon EFS as the correct solution because it is designed for multi-AZ, concurrent file system access, whereas EBS volumes are generally restricted to a single Availability Zone.

Analyze the disaster recovery replication requirements for raw images.

The backup must have an RPO of

15

minutes and an RTO of

10

minutes.

This establishes that replication must happen in near real-time and retrieval must be immediate.

Evaluate S3 Replication Time Control (S3 RTC) against the RPO.

S3 RTC guarantees replication of

99\%

of objects within

15

minutes, satisfying the RPO.

Standard Cross-Region Replication does not guarantee a replication window, making S3 RTC necessary to meet the strict SLA.

Evaluate the retrieval speed of the replica for the RTO.

Since S3 replicated data is immediately accessible as standard object storage in the destination Region, it satisfies the

10

-minute RTO.

This rules out S3 Glacier classes which introduce retrieval delays exceeding the RTO.

Key Concept

Designing highly available, multi-AZ shared file systems and cross-region replication configurations with tight RPO and RTO SLA bounds.

Estimated Time:2m 0s

Question 207Question →

An online education company stores popular static media assets, such as course images and stylesheets, in an Amazon S3 bucket. During peak enrollment periods, the S3 bucket experiences performance degradation due to high request volumes from global users. The company wants to reduce latency for users, protect the S3 bucket from overloading, and minimize operational complexity. Which configuration should the solutions architect choose?

Configure an Amazon CloudFront distribution with the Amazon S3 bucket as the origin, caching the static assets at edge locations with default Time to Live (TTL) settings.

Create an Amazon CloudFront distribution with the Amazon S3 bucket as the origin, and set the default Time to Live (TTL) to zero to ensure content is always fetched from the source.

Configure Amazon Route 53 with a latency-based routing policy to resolve the website's domain name directly to the S3 bucket endpoint.

Deploy AWS Shield Advanced directly on the S3 bucket to inspect Layer 7 web traffic and prevent request spikes from degrading performance.

Show answer & explanation

Answer: Configure an Amazon CloudFront distribution with the Amazon S3 bucket as the origin, caching the static assets at edge locations with default Time to Live (TTL) settings.

Answer

Configure an Amazon CloudFront distribution with the Amazon S3 bucket as the origin, caching the static assets at edge locations with default Time to Live (TTL) settings.

Configuring Amazon CloudFront with the S3 bucket as the origin allows CloudFront to cache static assets (like images and stylesheets) at global edge locations. This reduces latency for users worldwide by serving content from the nearest edge location and protects the origin S3 bucket from high request volumes by serving cached copies, thereby increasing resiliency and reliability.

Step-by-Step Solution

Identify the primary requirements: reduce latency for global users accessing static S3 assets and protect the origin bucket from request overload.

A caching mechanism at edge locations is needed to serve content closer to users and offload traffic from the S3 bucket.

Serving cached static content at edge locations reduces network round-trip time and prevents origin degradation.

Evaluate the capabilities of Amazon CloudFront.

Amazon CloudFront is a content delivery network that caches files at edge locations when non-zero TTL settings are active.

CloudFront acts as an edge caching layer that directly solves latency issues and shields the origin S3 bucket from high request volumes.

Compare CloudFront options against Route 53 and AWS Shield alternatives.

CloudFront with default TTL settings meets the requirement, whereas setting TTL to zero disables caching. Route 53 latency routing and AWS Shield do not cache content.

This step eliminates incorrect architectures that fail to provide edge caching.

Key Concept

Edge caching with Amazon CloudFront

Question 208Question →

A software-as-a-service (SaaS) company is building a real-time collaborative whiteboarding application. The application requires a database to store user session states across two AWS Regions: $us-west-2$ and $eu-central-1$ . The architecture must support active-active writes in both Regions to ensure sub-millisecond write latencies for local users. The database must automatically replicate data bi-directionally with a Recovery Point Objective (RPO) of less than $1$ second and a recovery time objective (RTO) of near zero during a regional outage. Which combination of configurations must a solutions architect implement to achieve this resilient database architecture? (Select TWO.)

Select all that apply

Create a primary Amazon DynamoDB table in one Region and enable DynamoDB Streams with the "New and Old Images" setting.

Add a replica table in the secondary AWS Region to convert the existing table into a DynamoDB global table.

Configure an Amazon Aurora Global Database and route write requests to the local reader endpoints in both Regions.

Deploy an Amazon RDS for PostgreSQL database with a cross-Region read replica and implement Route 53 latency-based routing to distribute writes across both databases.

Use Amazon Route 53 latency routing policies to direct database traffic to independent, single-AZ RDS instances deployed in both Regions.

Show answer & explanation

Answer: Create a primary Amazon DynamoDB table in one Region and enable DynamoDB Streams with the "New and Old Images" setting.; Add a replica table in the secondary AWS Region to convert the existing table into a DynamoDB global table.

Answer

The correct configurations are enabling DynamoDB Streams with New and Old Images on the primary table and adding a replica table in the secondary Region.

To achieve an active-active, multi-region architecture with sub-second bi-directional replication and sub-millisecond write latencies, Amazon DynamoDB global tables should be used. The solutions architect must first enable DynamoDB Streams with New and Old Images on the primary table, then add the replica table in the secondary Region.

Step-by-Step Solution

Analyze the requirements for active-active multi-region write access, sub-millisecond latency, and low RTO/RPO.

Identify that a multi-region active-active database engine is required, which rules out Amazon RDS and standard Amazon Aurora configurations since they use active-passive write architectures.

This narrows down the database solution to Amazon DynamoDB global tables, which natively support active-active configurations across multiple Regions.

Identify the prerequisite configurations to deploy Amazon DynamoDB global tables.

DynamoDB Streams with the New and Old Images setting must be enabled on the primary table before replica tables can be added.

DynamoDB uses the stream to track and replicate data changes across Regions to maintain consistency.

Select the configuration step that completes the creation of the global table.

Add a replica table in the secondary Region (eu-central-1).

This establishes bi-directional replication between the two Regions, allowing local reads and writes.

Key Concept

Amazon DynamoDB global tables provide a fully managed, multi-region, active-active database solution that replicates data with low latency, meeting high availability and resilient disaster recovery requirements.

Question 209Question →

A global logistics company has deployed a fleet-tracking application that ingests real-time telemetry data from vehicle sensors using a proprietary TCP-based protocol. The backend application is hosted on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB) in a primary AWS Region. The company requires a highly resilient architecture that minimizes latency for global clients, prevents packet loss over the public internet, and automatically fails over to a secondary Region in the event of an outage. Which architecture should a solutions architect recommend to meet these requirements?

Create an Amazon CloudFront distribution with the ALBs configured in an origin group for failover. Set the caching behavior to forward all headers and query parameters, and set the default Time to Live (TTL) to zero.

Create an AWS Global Accelerator accelerator, and associate the ALBs in both the primary and secondary Regions as endpoints. Configure the vehicle sensors to send telemetry data to the static IP addresses provided by the accelerator.

Configure Amazon Route 53 with latency-based routing and health checks pointing to the ALBs in both Regions, allowing client sensors to establish direct TCP connections over the public internet to the closest regional endpoint.

Deploy an AWS WAF Web ACL associated with AWS Shield Advanced at the edge, and configure it to route incoming TCP traffic from the sensors directly to the ALBs in both Regions using IP-based rules.

Show answer & explanation

Answer: Create an AWS Global Accelerator accelerator, and associate the ALBs in both the primary and secondary Regions as endpoints. Configure the vehicle sensors to send telemetry data to the static IP addresses provided by the accelerator.

Answer

Create an AWS Global Accelerator accelerator, associate the Application Load Balancers in both Regions as endpoints, and configure the vehicle sensors to send telemetry data to the accelerator's static IP addresses.

AWS Global Accelerator is the correct solution because it supports TCP and UDP protocols, routes traffic over the congestion-free AWS global network to minimize latency and packet loss, and provides automatic regional failover via health checks. Additionally, it offers static Anycast IP addresses, eliminating issues associated with DNS caching.

Step-by-Step Solution

Analyze the application protocol and requirements.

Identify that the application uses a proprietary TCP-based protocol (non-HTTP/HTTPS) and requires low latency, prevention of packet loss, and multi-region failover.

This determines which edge service is capable of routing the traffic, as Amazon CloudFront and AWS WAF only support HTTP/HTTPS, whereas AWS Global Accelerator supports TCP/UDP.

Evaluate AWS Global Accelerator as a routing solution.

AWS Global Accelerator provides two static Anycast IP addresses that route traffic over the AWS global private network to the nearest regional endpoint.

Routing traffic over the AWS global backbone reduces network hops, minimizes latency, prevents packet loss over the public internet, and avoids DNS caching issues during failover.

Configure endpoint groups and health checks.

Associate the Application Load Balancers (ALBs) from both the primary and secondary Regions as endpoints within the accelerator.

Global Accelerator monitors endpoint health and automatically routes client traffic to the secondary Region in the event of an outage in the primary Region.

Key Concept

AWS Global Accelerator vs. Amazon CloudFront for non-HTTP protocols and multi-region resiliency.

Estimated Time:2m 30s

Question 210Question →

A company hosts its primary web application behind an Application Load Balancer (ALB) in the us-east-1 Region. The company wants to set up a simple disaster recovery strategy where public DNS traffic is automatically redirected to a static error page hosted on an Amazon S3 bucket in the us-west-2 Region if the primary application becomes unavailable. Which Amazon Route 53 routing configuration should a solutions architect implement to meet these requirements?

Configure Route 53 failover routing. Create a primary failover record pointing to the ALB with health checks enabled, and a secondary failover record pointing to the S3 bucket endpoint.

Configure Route 53 latency routing records pointing to both the ALB and the S3 bucket endpoint, relying on Route 53 to automatically route all traffic to the S3 bucket during a primary region outage.

Configure a Route 53 database failover policy that monitors the application's RDS read replica in us-west-2 and automatically redirects all client web traffic to that replica when the primary database fails.

Configure Route 53 with a pilot light routing record that keeps the S3 bucket endpoint inactive and scale-up the bucket's resources only after a CloudWatch alarm triggers a failover event.

Show answer & explanation

Answer: Configure Route 53 failover routing. Create a primary failover record pointing to the ALB with health checks enabled, and a secondary failover record pointing to the S3 bucket endpoint.

Answer

Configure Route 53 failover routing by creating a primary failover record pointing to the ALB with health checks enabled, and a secondary failover record pointing to the S3 bucket endpoint.

The correct answer correctly identifies that a failover routing policy should be used for active-passive disaster recovery. By setting the Application Load Balancer as the primary endpoint and enabling health checks, Route 53 will route traffic to the primary endpoint as long as it is healthy. If the health checks fail, Route 53 automatically redirects incoming DNS queries to the secondary endpoint, which is the Amazon S3 static website.

Step-by-Step Solution

Define the primary and secondary roles for the endpoints.

The Application Load Balancer (ALB) is designated as the primary active resource, and the Amazon S3 bucket static website endpoint is designated as the secondary passive resource.

This establishes the active-passive disaster recovery structure required by the business goal.

Associate health checks with the primary record.

Route 53 monitors the health of the primary ALB.

Route 53 requires health check status to determine when to trigger a failover from the primary resource to the secondary resource.

Configure the routing policy in Route 53.

Create a primary failover alias record pointing to the ALB and a secondary failover alias record pointing to the S3 status/error page.

Failover routing directs traffic to the primary resource when healthy and automatically switches to the secondary resource when the primary fails health checks.

Key Concept

Amazon Route 53 DNS Failover with Active-Passive Architecture

Question 211Question →

A company runs a logistics and package tracking application on AWS that uses an Amazon RDS for PostgreSQL database. The database must be configured to survive a single Availability Zone (AZ) failure within the Region. The solution must support automatic failover with a Recovery Time Objective (RTO) of less than $2$ minutes and a Recovery Point Objective (RPO) of $0$ (no data loss). Additionally, the company needs to scale read performance for historical tracking queries without affecting the write performance of the primary database. Which configuration will meet these requirements?

Deploy two independent Single-AZ DB instances in different Availability Zones, and configure Amazon Route 53 with a latency routing policy and health checks to automatically route read and write requests to the healthiest instance.

Deploy the database as a Single-AZ DB instance, create an asynchronous Read Replica in a different Availability Zone, and configure the application to manually promote the Read Replica if the primary instance fails.

Deploy the database as an Amazon RDS Multi-AZ DB instance, create one or more Read Replicas in different Availability Zones, and route application read traffic to the replica endpoints.

Deploy the database as a Single-AZ DB instance, and configure a disaster recovery strategy to restore the database from daily automated snapshots to a new instance in a different Availability Zone during a failure event.

Show answer & explanation

Answer: Deploy the database as an Amazon RDS Multi-AZ DB instance, create one or more Read Replicas in different Availability Zones, and route application read traffic to the replica endpoints.

Answer

Deploy the database as an Amazon RDS Multi-AZ DB instance, create one or more Read Replicas in different Availability Zones, and route application read traffic to the replica endpoints.

Deploying the database as an Amazon RDS Multi-AZ DB instance provides synchronous replication to a standby instance in a different Availability Zone, guaranteeing a Recovery Point Objective (RPO) of

0

(no data loss). In the event of an infrastructure failure, Amazon RDS automatically performs a failover to the standby instance, typically in under

60

120

seconds, which satisfies the Recovery Time Objective (RTO) of less than

2

minutes. To scale read performance without impacting the primary writer, one or more Read Replicas can be deployed to handle read-only queries.

Step-by-Step Solution

Select Amazon RDS Multi-AZ DB instance deployment.

Enables synchronous replication to a standby replica in a second Availability Zone.

Synchronous replication guarantees that write operations are committed to both zones before succeeding, satisfying the RPO of

0

(no data loss).

Rely on RDS automatic failover mechanism.

Database failover to the standby instance occurs automatically within

60

120

seconds during an outage.

Automatic failover satisfies the RTO requirement of less than

2

minutes without manual intervention.

Create one or more RDS Read Replicas in different Availability Zones.

Provides dedicated read endpoints for the application to query historical tracking data.

Offloads read-intensive queries from the primary database instance to keep write performance optimal.

Key Concept

High Availability and Read Scaling with Amazon RDS Multi-AZ and Read Replicas

Estimated Time:2m 0s

Question 212Question →

A company wants to distribute static media assets to global users with low latency. The assets are currently stored in a primary Amazon S3 bucket. The company also wants to ensure high availability by automatically serving content from a backup S3 bucket in a different region if the primary bucket is unavailable. Which combination of actions should a solutions architect take to meet these requirements? (Select TWO.)

Select all that apply

Create an Amazon CloudFront distribution and define an origin group with the primary S3 bucket as the primary origin and the backup S3 bucket as the secondary origin.

Configure origin failover within the CloudFront origin group to route requests to the backup S3 bucket when the primary S3 bucket returns specific HTTP error status codes.

Configure Amazon Route 53 with a latency routing policy to route traffic directly to the nearest S3 bucket.

Deploy AWS WAF to monitor the health of the primary S3 bucket and automatically redirect requests to the backup bucket when errors are detected.

Set the CloudFront Cache-Control max-age header and default Time to Live (TTL) value to zero for all behaviors to force direct client access to the S3 buckets.

Show answer & explanation

Answer: Create an Amazon CloudFront distribution and define an origin group with the primary S3 bucket as the primary origin and the backup S3 bucket as the secondary origin.; Configure origin failover within the CloudFront origin group to route requests to the backup S3 bucket when the primary S3 bucket returns specific HTTP error status codes.

Answer

Create an Amazon CloudFront distribution and define an origin group with the primary S3 bucket as the primary origin and the backup S3 bucket as the secondary origin. Additionally, configure origin failover within the CloudFront origin group to route requests to the backup S3 bucket when the primary S3 bucket returns specific HTTP error status codes.

To achieve both low latency and high availability for static assets, Amazon CloudFront is the recommended solution. By caching assets at global edge locations, CloudFront reduces the latency for end users. To ensure high availability and automatic failover, CloudFront support for origin groups allows configuring a primary and secondary origin. When origin failover is enabled, CloudFront automatically routes requests to the secondary origin (the backup S3 bucket) if the primary origin (the primary S3 bucket) returns configured error codes (such as 500, 502, 503, or 504).

Step-by-Step Solution

Set up a content delivery network to reduce latency for global users by caching content at edge locations close to them.

An Amazon CloudFront distribution is deployed with caching behaviors configured for the static assets.

CloudFront caches content at edge locations, significantly reducing latency compared to direct S3 access.

Establish origin-level resiliency to protect against S3 bucket unavailability or service issues.

An origin group is configured in CloudFront, containing the primary S3 bucket as the primary origin and the backup S3 bucket as the secondary origin.

An origin group allows the mapping of multiple origins to a single distribution behavior for failover purposes.

Configure the automatic transition rules between the primary and secondary origins.

Origin failover is enabled with criteria pointing to specific 5xx HTTP error status codes.

This guarantees that if the primary S3 bucket is unavailable and returns an error code, CloudFront automatically routes the request to the backup S3 bucket without any operational overhead.

Key Concept

CloudFront Origin Groups and Origin Failover

Question 213Question →

A company runs a high-performance web service deployed across two AWS Regions: us-east-1 and eu-west-1. The company wants to route users to the closest Region to minimize latency, but must automatically stop routing traffic to a Region if its endpoint fails. The solutions architect needs to configure Amazon Route 53 to meet these requirements.

Which combination of Route 53 configurations should the solutions architect implement? (Select TWO.)

Select all that apply

Create latency-based routing records in Route 53 that point to the endpoints in each Region.

Associate a Route 53 health check with each latency record to monitor endpoint availability.

Create failover routing records in Route 53 and set one Region as primary and the other as secondary.

Configure geolocation routing records to automatically route based on the lowest network latency.

Configure Amazon RDS read replicas in the secondary Region to automatically update the DNS records during a failover event.

Show answer & explanation

Answer: Create latency-based routing records in Route 53 that point to the endpoints in each Region.; Associate a Route 53 health check with each latency record to monitor endpoint availability.

Answer

To achieve low latency and high availability, create latency-based routing records in Route 53 for both Regions and associate each record with a Route 53 health check.

To route users to the closest Region to minimize latency, latency-based routing must be used. To ensure that traffic is not routed to an unhealthy Region, Route 53 health checks must be associated with the routing records so that Route 53 can automatically perform DNS failover when an endpoint becomes unhealthy.

Step-by-Step Solution

Select the appropriate routing policy for minimizing user latency.

Create Route 53 latency-based routing records pointing to endpoints in both us-east-1 and eu-west-1.

Latency-based routing measures round-trip time from the user to the AWS Regions and routes traffic to the Region with the lowest latency.

Configure health checks to ensure high availability.

Associate a Route 53 health check with each latency record.

If an endpoint in one Region fails, Route 53 detects the failure via the health check and stops returning that record, routing traffic to the healthy Region instead.

Key Concept

Active-active multi-region high availability with Route 53 latency routing and health checks

Question 214Question →

A maritime logistics enterprise is designing a highly resilient storage architecture for its shipping manifest processing platform. The platform must store PDF manifest files that are frequently accessed by multiple applications during the first 30 days. To comply with international shipping regulations, these manifests must be kept for 5 years and must be retrievable within 5 minutes in the event of an audit. The solution must support a multi-region disaster recovery strategy with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 30 minutes. Which storage design meets these requirements?

Store the manifests in Amazon S3 Standard. Configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled. Create an S3 Lifecycle policy to transition the manifest objects to Amazon S3 Glacier Flexible Retrieval after 30 days, using Expedited retrievals for audit requests.

Store the manifests in Amazon S3 Standard. Configure standard S3 Cross-Region Replication (CRR) to replicate objects to the secondary region. Create an S3 Lifecycle policy to transition the manifest objects to Amazon S3 Glacier Flexible Retrieval after 30 days, using Standard retrievals for audit requests.

Store the manifests in an Amazon RDS database. Set up cross-region RDS Read Replicas as the primary disaster recovery failover mechanism to meet the RPO and RTO requirements, storing historical documents directly within database tables.

Store the manifests on Amazon EFS file systems. Configure cross-region replication for the EFS file systems. Implement a Pilot Light disaster recovery strategy where recovery EC2 instances in the secondary region are kept shut down, relying on manual scripts to mount the replicated EFS file system during a failover event.

Show answer & explanation

Answer: Store the manifests in Amazon S3 Standard. Configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled. Create an S3 Lifecycle policy to transition the manifest objects to Amazon S3 Glacier Flexible Retrieval after 30 days, using Expedited retrievals for audit requests.

Answer

Store the manifests in Amazon S3 Standard, configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled, and use an S3 Lifecycle policy to transition objects to Amazon S3 Glacier Flexible Retrieval after 30 days with Expedited retrievals for audits.

The correct solution uses Amazon S3 Standard combined with Cross-Region Replication (CRR) and S3 Replication Time Control (S3 RTC). S3 RTC guarantees that 99% of objects replicate within 15 minutes, directly fulfilling the 15-minute RPO. For the 5-year retention requirement, an S3 Lifecycle policy automates the transition to S3 Glacier Flexible Retrieval after 30 days. To meet the 5-minute audit retrieval requirement, Expedited retrievals are used, which typically complete within 1 to 5 minutes.

Step-by-Step Solution

Select the correct replication mechanism to meet the Recovery Point Objective (RPO) constraint.

Amazon S3 Replication Time Control (S3 RTC) replicates 99% of objects within 15 minutes, satisfying the 15-minute RPO.

Standard Cross-Region Replication (CRR) does not provide a replication time guarantee, meaning replication could take longer than the 15-minute RPO threshold.

Choose the appropriate archival storage tier that satisfies the retrieval speed requirement.

Amazon S3 Glacier Flexible Retrieval with Expedited retrievals provides access to archives within 1 to 5 minutes.

Standard retrievals from Glacier take 3 to 5 hours, which violates the audit retrieval requirement of less than 5 minutes.

Integrate S3 Lifecycle rules to automate cost-efficient and resilient transition.

Create an S3 Lifecycle policy to transition objects from S3 Standard to S3 Glacier Flexible Retrieval after 30 days.

This automates the lifecycle transition, ensuring compliance while optimizing storage costs for the 5-year retention period.

Key Concept

Designing a resilient, multi-region object storage system using S3 Replication Time Control (S3 RTC) and S3 Glacier Expedited retrievals to satisfy strict RPO, RTO, and archival recovery metrics.

Estimated Time:1m 30s

Question 215Question →

A company hosts its primary web application on EC2 instances behind an Application Load Balancer (ALB). To ensure business continuity during an outage, the company configures a static "under maintenance" page in an Amazon S3 bucket. A solutions architect must configure Amazon Route 53 to automatically direct all user traffic to the S3 bucket if the ALB becomes unhealthy. Which Route 53 routing configuration should the solutions architect implement to meet these requirements?

Create a Route 53 failover routing policy. Configure a primary alias record pointing to the ALB with target health evaluation enabled, and a secondary alias record pointing to the S3 bucket.

Create a Route 53 latency routing policy. Configure one record pointing to the ALB and another record pointing to the S3 bucket, allowing Route 53 to route traffic to the resource with the lowest network latency.

Create a Route 53 failover routing policy. Configure a primary record pointing to the application's primary database instance and a secondary record pointing to an RDS read replica for database failover.

Create a Route 53 weighted routing policy. Assign a weight of

100

to the ALB and a weight of

0

to the S3 bucket, then manually update the weights during an outage to achieve warm standby recovery.

Show answer & explanation

Answer: Create a Route 53 failover routing policy. Configure a primary alias record pointing to the ALB with target health evaluation enabled, and a secondary alias record pointing to the S3 bucket.

Answer

Create a Route 53 failover routing policy. Configure a primary alias record pointing to the ALB with target health evaluation enabled, and a secondary alias record pointing to the S3 bucket.

The correct option is the one that recommends configuring a Route 53 failover routing policy with a primary alias record pointing to the ALB (health evaluation enabled) and a secondary alias record pointing to the S3 bucket. Failover routing allows Route 53 to route traffic to the primary resource when it is healthy, and switch to the secondary resource when the primary is unhealthy. Setting 'Evaluate Target Health' to Yes on the alias record enables Route 53 to automatically check the health of the ALB.

Step-by-Step Solution

Identify the high availability pattern required.

The requirement is active-passive disaster recovery where traffic automatically fails over from a primary application load balancer to a backup static S3 bucket.

This establishes that the Route 53 failover routing policy is the correct choice.

Configure the primary endpoint routing and health checks.

Configure a primary failover record as an Alias record pointing to the ALB with 'Evaluate Target Health' enabled.

Evaluating target health ensures that Route 53 automatically monitors the health of the ALB without needing a custom Route 53 health check.

Configure the secondary endpoint routing.

Configure a secondary failover record pointing to the S3 static website endpoint.

This provides the failover destination where Route 53 will route traffic when the primary endpoint is determined to be unhealthy.

Key Concept

Route 53 active-passive failover routing policy dynamically routes traffic to a secondary standby endpoint when the primary endpoint becomes unhealthy, determined via target health evaluation.

Question 216Question →

A company hosts a critical web application on Amazon EC2 instances behind an Application Load Balancer (ALB) in the us-west-2 Region. The application queries a Multi-AZ Amazon RDS DB instance. The company wants to implement an active-passive disaster recovery (DR) strategy with a Recovery Time Objective (RTO) of under 2 minutes. The passive site consists of a static maintenance website hosted in an Amazon S3 bucket in the us-east-1 Region. The system must automatically redirect users to the maintenance page if the primary application servers or the database fail. Which configuration should a solutions architect implement to meet these requirements?

Configure an HTTPS Route 53 health check to monitor a custom application endpoint that verifies database connectivity. Create a primary Failover Alias A record pointing to the ALB, associate it with the health check, and set Evaluate Target Health to Yes. Create a secondary Failover Alias A record pointing to the S3 static website endpoint.

Configure a Route 53 Latency routing policy with Alias records pointing to both the ALB in us-west-2 and the S3 website endpoint in us-east-1. Enable Evaluate Target Health on both records so that Route 53 automatically redirects users to the S3 bucket if the ALB's latency increases due to a database outage.

Configure a primary Failover Alias record pointing to the ALB. For the database tier, create a Route 53 CNAME record pointing to the primary RDS database endpoint, and a secondary CNAME record pointing to an RDS Read Replica in us-east-1 with Evaluate Target Health enabled, expecting Route 53 to promote the read replica if the primary database fails.

Configure a primary Failover CNAME record pointing to the ALB's DNS name and enable Evaluate Target Health. In the secondary region, keep the backup web servers stopped to minimize running costs as a Pilot Light environment, and configure Route 53 to automatically start the EC2 instances during failover to meet the 2-minute RTO.

Show answer & explanation

Answer: Configure an HTTPS Route 53 health check to monitor a custom application endpoint that verifies database connectivity. Create a primary Failover Alias A record pointing to the ALB, associate it with the health check, and set Evaluate Target Health to Yes. Create a secondary Failover Alias A record pointing to the S3 static website endpoint.

Answer

The correct configuration uses an HTTPS health check pointing to a custom endpoint on the application that actively verifies connection to the database. This deep health check ensures that database-level issues trigger a failover. By using an Alias A record for the primary ALB with Failover routing and Evaluate Target Health set to Yes, Route 53 can evaluate both the ALB health and the associated custom health check. Setting up the secondary Failover Alias record pointing to the S3 website endpoint ensures that Route 53 immediately routes traffic to the static maintenance page upon detecting primary failure, meeting the tight RTO requirement.

Step-by-Step Solution

Set up a deep health check endpoint on the web application.

An endpoint (such as /health) is created that checks connection to the Amazon RDS database and returns an HTTP 200 OK status only when the web servers and database are functional.

Standard ALB health checks only evaluate the ALB or the web servers, not downstream dependencies like the database. A deep health check ensures database failures trigger a failover.

Create a Route 53 health check.

A Route 53 HTTP/HTTPS health check is created pointing to the domain and the custom deep health endpoint, checking it at regular intervals.

This health check will report unhealthy if either the application servers or the database fails, providing the trigger for Route 53 to swap DNS targets.

Create the primary Route 53 Failover record.

An Alias A record pointing to the ALB is created with the Failover routing policy, associated with the Route 53 health check, and 'Evaluate Target Health' set to Yes.

Alias records allow the 'Evaluate Target Health' option to be set to Yes, which integrates the load balancer's health status with Route 53's routing decision.

Create the secondary Route 53 Failover record.

An Alias A record pointing to the S3 static website endpoint is created with the Failover routing policy.

When the primary record is determined to be unhealthy, Route 53 automatically fails over to the secondary record, pointing users to the maintenance page.

Key Concept

Active-passive DNS failover in Route 53 requires Alias records to support Evaluate Target Health, deep health checks to monitor backend dependencies, and a secondary resource that is immediately ready to serve traffic.

Question 217Question →

An organization is designing a highly resilient, low-latency API gateway endpoint for a global mobile application. The backend microservices are deployed on Amazon ECS behind Application Load Balancers (ALBs) in the `us-east-1` and `eu-west-1` regions. The business requires that users are routed to the closest region under normal operating conditions. If the ECS tasks in a region fail, Route 53 must automatically route traffic away from that region. Additionally, the failover mechanism must verify that the API returns a specific JSON status payload containing \"status\": \"healthy\", which is returned by a deep health check endpoint. Which two configurations should a solutions architect implement to meet these requirements? (Select two.)

Select all that apply

Create Route 53 HTTPS health checks with string matching configured to verify the string \"status\": \"healthy\" is present, ensuring the health check endpoint returns this payload within the first

5{}120

bytes of the response.

Create Latency alias records in Route 53 pointing to the Application Load Balancer in each region, set Evaluate Target Health to Yes, and associate each record with the corresponding custom HTTPS health check.

Create Latency CNAME records pointing to each region's ALB DNS name, enable Evaluate Target Health on these records, and associate them with the custom HTTPS health checks.

Configure Failover routing records for each region, and configure the Route 53 health checks to monitor the database tier and automatically trigger an Amazon RDS read replica promotion in the event of an outage.

Configure a warm standby disaster recovery policy using Failover routing records, and configure a custom health check with a

300

-second evaluation interval to prevent premature failover while the secondary region ECS tasks scale up.

Show answer & explanation

Answer: Create Route 53 HTTPS health checks with string matching configured to verify the string \"status\": \"healthy\" is present, ensuring the health check endpoint returns this payload within the first $5{}120$ bytes of the response.; Create Latency alias records in Route 53 pointing to the Application Load Balancer in each region, set Evaluate Target Health to Yes, and associate each record with the corresponding custom HTTPS health check.

Answer

The correct configurations are to create Route 53 HTTPS health checks with string matching for the specific JSON payload within the first

5{}120

bytes, and to create Latency alias records pointing to each Application Load Balancer with Evaluate Target Health set to Yes, associated with the health checks.

The solution requires latency-based routing to ensure users are directed to the closest region under normal conditions. This is achieved by creating Latency alias records in Route 53 pointing to the Application Load Balancers (ALBs) in both regions. Setting 'Evaluate Target Health' to Yes ensures Route 53 automatically evaluates the health of the ALB and its targets. Furthermore, to verify the specific JSON response payload, a custom HTTPS health check with string matching must be associated with the records. Because Route 53 string matching only evaluates the first

5{}120

bytes of a response body, the API status endpoint must return the required payload within this limit.

Step-by-Step Solution

Configure a custom Route 53 HTTPS health check with string matching.

A custom health check is created that monitors the deep health check endpoint and searches for the string \"status\": \"healthy\" within the first

5{}120

bytes of the response body.

Route 53 string matching health checks are limited to searching the first

5{}120

bytes of the response body, which matches the business requirement to verify the status payload.

Configure active-active latency-based routing with alias records and target health evaluation.

Latency alias records are created pointing to each regional Application Load Balancer with Evaluate Target Health set to Yes and associated with the custom health checks.

Alias records are required to use the Evaluate Target Health feature. Latency routing directs traffic to the closest region, and setting Evaluate Target Health to Yes ensures Route 53 shifts traffic away if the health check fails.

Key Concept

To implement active-active latency routing with deep health checking in Route 53, you must use Latency alias records (not CNAMEs) to support 'Evaluate Target Health', and configure custom HTTPS health checks with string matching that respects the

5{}120

-byte payload limit.

Question 218Question →

A retail company runs a production transaction-processing application on an Amazon RDS for MySQL DB instance. The database must be highly resilient to Availability Zone outages with a Recovery Time Objective (RTO) of less than 120 seconds. Additionally, the application requires read scaling to handle heavy reporting queries during business hours without impacting write operations on the primary database instance.

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

Select all that apply

Deploy the Amazon RDS DB instance in a Multi-AZ deployment.

Create Amazon RDS Read Replicas and direct read traffic to the read replica endpoints.

Deploy the Amazon RDS DB instance in a Multi-AZ deployment and configure the application to route read queries to the standby database instance.

Deploy a single-AZ DB instance and configure the application to automatically promote a Read Replica to primary during a primary database outage.

Deploy the database in a single-AZ configuration and set up an Amazon Route 53 latency routing policy with health checks to automatically fail over database write traffic to a Read Replica.

Show answer & explanation

Answer: Deploy the Amazon RDS DB instance in a Multi-AZ deployment.; Create Amazon RDS Read Replicas and direct read traffic to the read replica endpoints.

Answer

Deploy the database in a Multi-AZ configuration to achieve high availability and low RTO, and create RDS Read Replicas to scale read performance.

To meet the requirements, the database must support automatic failover for high availability and read scaling. A Multi-AZ deployment creates a primary DB instance and a synchronous standby replica in a different Availability Zone. If the primary instance fails, RDS automatically performs a failover to the standby, achieving a low RTO. To scale read queries without affecting the primary write performance, creating RDS Read Replicas and directing reporting traffic to the read replica endpoints is the correct approach.

Step-by-Step Solution

Identify high availability and RTO requirements.

Determine that a Multi-AZ deployment is required to provide synchronous replication and automatic failover in under 120 seconds.

A single-AZ DB instance with read replicas does not support automatic, low-RTO failover.

Identify read scaling requirements.

Determine that RDS Read Replicas are needed to handle reporting queries and offload read traffic from the primary database.

The standby DB instance in a Multi-AZ DB instance configuration is passive and cannot serve read traffic.

Select the correct combination of configurations.

Combine a Multi-AZ deployment for failover/HA with one or more Read Replicas for read scaling.

This satisfies both the HA/failover RTO requirements and the read scalability constraints.

Key Concept

Distinguishing between RDS Multi-AZ deployments for high availability/failover and RDS Read Replicas for scaling read operations.

Question 219Question →

A company wants to configure an active-passive disaster recovery strategy for its web portal. The primary website is hosted behind an Application Load Balancer (ALB) in the us-east-1 Region. If the ALB becomes unhealthy, all traffic must be redirected automatically to a backup static maintenance site hosted on an Amazon S3 website endpoint in the us-west-2 Region. Which configurations must the Solutions Architect implement in Amazon Route 53 to achieve this behavior? (Select TWO.)

Select all that apply

Create an Alias A record for the portal domain pointing to the Application Load Balancer, configure it with a Failover routing policy as the Primary record, and enable Evaluate Target Health.

Create an Alias A record for the portal domain pointing to the Amazon S3 website endpoint, and configure it with a Failover routing policy as the Secondary record.

Create a standard CNAME record for the portal domain pointing to the Application Load Balancer DNS name, configure it with a Failover routing policy, and enable Evaluate Target Health.

Create Latency routing records for both the Application Load Balancer and the S3 website endpoint to automatically reroute traffic during latency spikes.

Create a secondary DNS record pointing directly to an Amazon RDS Read Replica in us-west-2 to enable automated database failover.

Show answer & explanation

Answer: Create an Alias A record for the portal domain pointing to the Application Load Balancer, configure it with a Failover routing policy as the Primary record, and enable Evaluate Target Health.; Create an Alias A record for the portal domain pointing to the Amazon S3 website endpoint, and configure it with a Failover routing policy as the Secondary record.

Answer

Configure a primary Route 53 Alias A record pointing to the Application Load Balancer with a Failover policy and 'Evaluate Target Health' enabled, and configure a secondary Route 53 Alias A record pointing to the Amazon S3 website endpoint with a Failover policy.

To set up active-passive failover to a static website on Amazon S3, you must use Route 53 Failover routing. The primary record must point to the Application Load Balancer using an Alias A record with 'Evaluate Target Health' enabled so that Route 53 can detect load balancer unhealthiness. The secondary record must be an Alias A record pointing to the S3 bucket website endpoint configured as a secondary failover target.

Step-by-Step Solution

Configure the primary DNS entry using an Alias record.

An A record with an Alias to the ALB is created.

Alias records are required to map the zone apex or domain name directly to AWS resources like ALBs and enable Route 53's 'Evaluate Target Health' feature.

Set up health check monitoring for the primary record by enabling Evaluate Target Health.

Route 53 automatically tracks the health of the ALB and its targets.

Enabling 'Evaluate Target Health' allows Route 53 to inherit the health status of the ALB without needing a custom Route 53 health check configuration.

Configure the secondary DNS entry using an Alias record pointing to the S3 bucket website endpoint.

A secondary A record with Failover routing is established.

This record serves as the passive target, which Route 53 will resolve only when the primary target is marked unhealthy.

Key Concept

Route 53 DNS Failover allows solutions architects to implement active-passive architectures using primary and secondary records. It requires Alias records to leverage target health evaluation for AWS resources.

Question 220Question →

A fintech enterprise hosts a containerized loan processing platform on Amazon ECS across three Availability Zones. The platform generates and modifies loan agreements that must be concurrently accessible by multiple containers in an active-active configuration. The platform's disaster recovery SLA requires a Recovery Point Objective (RPO) of $4$ hours and a Recovery Time Objective (RTO) of $1$ hour. The storage solution must be highly resilient, durable, and support automatic failover across all three Availability Zones. Which combination of storage and backup configurations should a solutions architect implement to meet these requirements? (Select TWO.)

Select all that apply

Configure an Amazon EFS file system using the Regional storage class, and mount it on the Amazon ECS tasks across all three Availability Zones.

Create an AWS Backup plan with a backup rule that runs every

4

hours, backing up the filesystem to a backup vault.

Provision Amazon EBS volumes with Multi-Attach enabled and mount the volumes to the ECS tasks across all three Availability Zones.

Archive the agreements to Amazon S3 Glacier Flexible Retrieval and use Standard retrieval to recover the data in the event of storage failure.

Deploy a Pilot Light environment in a secondary AWS Region with active, scaled-down ECS tasks running continuously to ensure near-zero recovery time for the shared storage during failover.

Show answer & explanation

Answer: Configure an Amazon EFS file system using the Regional storage class, and mount it on the Amazon ECS tasks across all three Availability Zones.; Create an AWS Backup plan with a backup rule that runs every $4$ hours, backing up the filesystem to a backup vault.

Answer

The correct configurations are mounting a Regional Amazon EFS file system on the ECS tasks and implementing an AWS Backup plan with a

4

-hour schedule.

Mounting a Regional Amazon EFS file system provides concurrent, active-active file access across multiple Availability Zones, ensuring high availability and durability. Setting up AWS Backup to run every

4

hours ensures that recovery points are created frequently enough to satisfy the

4

-hour RPO, and restores from AWS Backup can be completed well within the

1

-hour RTO.

Step-by-Step Solution

Analyze shared storage and concurrency requirements across multiple Availability Zones.

Amazon EFS is selected because it supports active-active concurrent file access across multiple AZs, unlike Amazon EBS which is restricted to a single AZ or lacks multi-mount capabilities across AZs.

This establishes the high availability foundation required by the containerized ECS application.

Evaluate the RPO requirement of

4

hours.

AWS Backup is configured to take backups of the EFS filesystem every

4

hours.

This guarantees that the maximum data loss in a disaster scenario will not exceed the

4

-hour threshold.

Evaluate the RTO requirement of

1

hour.

Confirming EFS restores via AWS Backup are fast enough to meet the

1

-hour window, while rejecting Glacier Standard retrieval which takes

3

5

hours.

This ensures the recovery time remains within the SLA limits.

Key Concept

Designing highly available, multi-AZ shared file systems using Amazon EFS coupled with AWS Backup to meet specific RPO and RTO compliance metrics.

PreviousPage 11 / 20Next

Design Resilient Architectures

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept