Design Resilient Architectures

382 soru

Tüm türler382 Çoktan seçmeli195 Çoklu seçim187

A company runs a global API platform across three AWS Regions: us-east-1, eu-west-1, and ap-southeast-2. Each region has an Application Load Balancer (ALB) routing traffic to Amazon EC2 instances. To optimize performance, the company uses Amazon Route 53 Latency routing with 'Evaluate Target Health' enabled on the alias records. During a disaster recovery test, the database in us-east-1 is powered down. The EC2 instances in us-east-1 remain running but return HTTP 500 Internal Server Error to all API clients because they cannot access the database. However, Route 53 continues to route client traffic to the us-east-1 ALB. Which configuration change will resolve this issue and ensure that Route 53 fails over to the next closest region?

Change the Route 53 routing policy to Failover routing, as Latency routing policies do not support health checks or Evaluate Target Health for automatic failover.

Scale up the EC2 instances in the standby regions to match the primary region's capacity, as Route 53 will not failover to a Pilot Light environment until target capacity is verified.

Configure the Application Load Balancer's target group health check to query a deep health check endpoint that validates database connectivity rather than a static resource.

Promote the database read replica in the standby region to primary, as Route 53 failover requires the database replication state to be synchronized before updating DNS records.

Cevabı ve açıklamayı göster

Cevap: Configure the Application Load Balancer's target group health check to query a deep health check endpoint that validates database connectivity rather than a static resource.

Cevap

Configure the Application Load Balancer's target group health check to query a deep health check endpoint that validates database connectivity rather than a static resource.

The correct answer is to configure the Application Load Balancer's target group health check to query a deep health check endpoint that validates database connectivity. When Route 53's Evaluate Target Health is enabled on an alias record pointing to an Application Load Balancer, Route 53 relies on the health status of the registered targets in the ALB's target groups. If the targets are configured to verify health using a static resource, they will continue to report as healthy even if the database is offline. By changing the health check path to a deep health check endpoint that verifies backend database connectivity, the targets will be marked unhealthy when the database fails, causing Route 53 to failover traffic to the next closest region.

Adım Adım Çözüm

Analyze the relationship between Route 53 'Evaluate Target Health' and the Application Load Balancer (ALB).

Identify that Route 53 determines the health of the ALB based on the health checks of its target group instances.

To find why Route 53 failed to detect the outage, we must trace how Route 53 gets health state data.

Evaluate the impact of the database outage on the existing target group health check configuration.

Determine that the targets are returning healthy status because the health check is hitting a static resource, ignoring the database status.

This explains why the EC2 instances are marked healthy by the ALB despite returning HTTP 500 to clients.

Formulate the correction to the target group health check.

Point the health check path to a deep health check endpoint that verifies database connection.

When the database goes down, this deep endpoint will return an unhealthy status, causing the target group to mark targets unhealthy, which prompts Route 53 to route traffic to the next closest region.

Anahtar Kavram

Route 53 routing policies evaluate target health based on the configured health checks of the target endpoint. For Application Load Balancers, this health state depends directly on the ALB target group's health checks. If target groups query a shallow endpoint (e.g. static file), Route 53 will remain unaware of database-level outages.

Soru 222Soru →

A financial services company is migrating its transactional application to AWS. The database tier will run on Amazon RDS for PostgreSQL. The company requires a database design that guarantees high availability within a single AWS Region. The design must provide an automatic failover time of less than 60 seconds (Recovery Time Objective) and zero data loss (Recovery Point Objective) during an Availability Zone outage. In addition, the database must support horizontal read scaling during peak hours. Which of the following database configurations meets these requirements?

Deploy a Single-AZ RDS PostgreSQL DB instance and create two Read Replicas in different Availability Zones, configuring the application to promote a Read Replica if the primary fails.

Deploy a Single-AZ RDS PostgreSQL DB instance and use AWS Backup to restore hourly snapshots to a new DB instance in a different Availability Zone during a failure.

Deploy an Amazon RDS Multi-AZ DB cluster with one writer DB instance and two readable standby DB instances across three Availability Zones.

Deploy two Single-AZ RDS PostgreSQL DB instances in different Availability Zones and configure Amazon Route 53 latency-based routing to distribute database write and read traffic.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon RDS Multi-AZ DB cluster with one writer DB instance and two readable standby DB instances across three Availability Zones.

Cevap

Deploy an Amazon RDS Multi-AZ DB cluster with one writer DB instance and two readable standby DB instances across three Availability Zones.

Deploying an Amazon RDS Multi-AZ DB cluster provides a high availability configuration with one primary (writer) DB instance and two readable standby DB instances across three Availability Zones. This deployment uses semi-synchronous replication to ensure zero data loss (RPO of 0) and supports automatic failover in under 35 seconds (meeting the RTO requirement). Furthermore, the readable standby instances allow horizontal scaling of read traffic through the reader endpoint.

Adım Adım Çözüm

Analyze the requirements for high availability, failover time (RTO < 60s), data loss (RPO = 0), and read scaling.

The solution must support automatic failover in less than 60 seconds, semi-synchronous replication to guarantee zero data loss during an AZ outage, and have readable standby or secondary instances.

This establishes the baseline criteria for filtering out non-compliant architectures.

Evaluate Amazon RDS Multi-AZ DB clusters against these criteria.

An RDS Multi-AZ DB cluster consists of one primary (writer) instance and two reader instances across three AZs. It uses semi-synchronous replication to achieve zero data loss (RPO = 0) and offers automatic failover in under 35 seconds, which meets the RTO < 60s constraint.

This confirms that the cluster deployment satisfies all high availability and replication requirements.

Evaluate read scaling capabilities of the selected architecture.

Because the standby instances in a Multi-AZ DB cluster are readable, they can actively serve read queries via the reader endpoint, addressing the read scaling constraint without requiring separate asynchronous replicas.

This guarantees that the design scales horizontally under peak workloads.

Anahtar Kavram

High Availability and Read Scaling in Amazon RDS Multi-AZ DB Clusters

Soru 223Soru →

A financial services enterprise runs a real-time transaction reconciliation application on Amazon EC2 instances distributed across three Availability Zones. The application requires concurrent read/write access to a shared storage repository with high durability ( $99.999999999\%$ ) and high availability ( $99.99\%$ ). The storage architecture must support a Recovery Point Objective (RPO) of zero and a Recovery Time Objective (RTO) of near-zero in the event of an Availability Zone outage, without requiring manual intervention. Which storage configuration best meets these requirements?

Amazon Elastic File System (Amazon EFS) using the Standard (Regional) storage class.

Amazon S3 Glacier Flexible Retrieval using Standard retrieval options for failover storage.

A Pilot Light disaster recovery configuration in a secondary Region with pre-warmed, scaled-down EC2 instances and EBS volumes.

Amazon Elastic Block Store (Amazon EBS) volumes attached to Amazon RDS DB instances, leveraging RDS Read Replicas for automatic write failover.

Cevabı ve açıklamayı göster

Cevap: Amazon Elastic File System (Amazon EFS) using the Standard (Regional) storage class.

Cevap

Amazon Elastic File System (Amazon EFS) using the Standard (Regional) storage class.

The correct answer is Amazon Elastic File System (Amazon EFS) using the Standard (Regional) storage class. EFS natively replicates data across multiple Availability Zones in an AWS Region, provides concurrent shared access to EC2 instances, and automatically handles AZ failures to meet near-zero RTO and zero RPO requirements.

Adım Adım Çözüm

Analyze the access pattern and durability requirements.

The application requires concurrent read/write access from EC2 instances in multiple Availability Zones, zero data loss (

RPO = 0

), and durability of

99.999999999\%

This filters out block storage (EBS) which cannot natively attach to multiple instances across AZs simultaneously.

Evaluate the recovery time requirements (RTO).

An AZ outage must be handled automatically without manual intervention, achieving a near-zero RTO.

This rules out S3 Glacier due to standard retrieval delays (3 to 5 hours) and Pilot Light disaster recovery configurations which require manual activation steps.

Assess the remaining storage configurations for multi-AZ failover capability.

Amazon EFS Regional storage class provides Multi-AZ durability, concurrent shared access, and native failover without manual intervention.

It meets both the high-availability metric (

99.99\%

) and the zero RPO/near-zero RTO targets.

Anahtar Kavram

Resilient and Highly Available Storage Infrastructure

Tahmini Süre:1m 30s

Soru 224Soru →

A global e-learning company hosts its interactive quiz application on Amazon EC2 instances behind an Application Load Balancer (ALB) in the us-east-1 Region. To ensure disaster recovery and high availability, the company has deployed a duplicate environment with an ALB in the eu-west-1 Region. The application requires low-latency delivery of dynamic content to global users and must automatically fail over to the secondary Region with minimal downtime if the primary Region experiences an outage. The solution must minimize operational complexity and avoid modifications to client-side DNS configurations. Which solution should the solutions architect implement to meet these requirements?

Configure an Amazon CloudFront distribution and define an origin group containing the us-east-1 ALB as the primary origin and the eu-west-1 ALB as the failover origin. Set failover criteria to include HTTP status codes 500, 502, 503, and 504.

Configure Amazon Route 53 with a latency routing policy pointing to both the us-east-1 ALB and the eu-west-1 ALB. Enable Route 53 health checks on both endpoints to automatically route traffic to the healthy Region during an outage.

Deploy AWS Global Accelerator to route traffic to both ALBs. Configure AWS WAF on the ALBs with a custom rule that blocks incoming traffic to the us-east-1 ALB when it becomes unhealthy, forcing the accelerator to route all requests to the eu-west-1 ALB.

Configure an Amazon CloudFront distribution with the us-east-1 ALB as the primary origin. Configure the cache behavior's default, minimum, and maximum TTL values to 0 seconds. Use Route 53 failover routing policy to update the origin DNS record to point to the eu-west-1 ALB during an outage.

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon CloudFront distribution and define an origin group containing the us-east-1 ALB as the primary origin and the eu-west-1 ALB as the failover origin. Set failover criteria to include HTTP status codes 500, 502, 503, and 504.

Cevap

Configure an Amazon CloudFront distribution with an origin group containing the primary ALB and the backup ALB, configuring failover for HTTP status codes 500, 502, 503, and 504.

The correct solution uses an Amazon CloudFront distribution configured with an Origin Group. This feature allows a primary origin (the Application Load Balancer in us-east-1) and a secondary origin (the Application Load Balancer in eu-west-1) to act in an active-passive setup. When the primary origin returns specific HTTP status codes (such as 500, 502, 503, or 504), CloudFront automatically retries the request against the secondary origin. This failover happens at the edge layer within seconds, preventing user downtime and bypassing client-side DNS caching limitations.

Adım Adım Çözüm

Identify the primary performance and resilience constraints.

The solution requires low-latency content delivery, automated active-passive regional failover, and minimal operational complexity without modifying client-side DNS settings.

This rules out basic Route 53 failover because client DNS caching (TTL) delays propagation, violating the minimal downtime constraint.

Evaluate Amazon CloudFront's native failover capabilities.

CloudFront supports Origin Groups, which allow designating a primary origin and a failover origin.

Edge-level failover avoids DNS propagation delays, routing requests directly to the backup region if the primary region's ALB fails.

Define the failover criteria.

Specify HTTP status codes (500, 502, 503, 504) that represent origin unavailability or server-side failure.

This guarantees that if the primary ALB or its backend EC2 instances fail, CloudFront immediately redirects the user request to the secondary ALB in eu-west-1.

Anahtar Kavram

CloudFront Origin Groups and Failover Configuration

Tahmini Süre:2m 30s

Soru 225Soru →

An enterprise application runs on Amazon EC2 instances and uses an Amazon RDS for PostgreSQL database. The database must be designed for high availability within a single AWS Region with a Recovery Time Objective (RTO) of under 60 seconds and a Recovery Point Objective (RPO) of zero. Additionally, the database must support scaling read traffic during peak monthly reporting periods without affecting write performance on the primary database instance. Which combination of database configurations should a solutions architect implement to meet these requirements? (Select TWO.)

Geçerli olan tümünü seçin

Deploy the RDS for PostgreSQL DB instance in a Multi-AZ configuration to enable synchronous replication and automatic failover.

Create RDS Read Replicas and configure the reporting application to use the read replica endpoints.

Configure an RDS Read Replica in another Availability Zone and manually promote it to primary during a database failover.

Deploy a single-AZ database instance and restore from Amazon S3 backups in a different Availability Zone during a failure.

Use Amazon Route 53 latency-based routing to distribute database write traffic between the primary DB instance and its read replicas.

Cevabı ve açıklamayı göster

Cevap: Deploy the RDS for PostgreSQL DB instance in a Multi-AZ configuration to enable synchronous replication and automatic failover.; Create RDS Read Replicas and configure the reporting application to use the read replica endpoints.

Cevap

To meet both the high availability and read-scaling requirements, the solutions architect should deploy the Amazon RDS database in a Multi-AZ configuration to enable automatic failover and synchronous replication (ensuring an RTO of under 60 seconds and an RPO of zero), and create RDS Read Replicas to offload read-heavy reporting queries from the primary instance.

Deploying Amazon RDS for PostgreSQL in a Multi-AZ configuration ensures that data is synchronously replicated to a standby instance in another Availability Zone, allowing for automatic failover without data loss (RPO = 0) in under 60 seconds (RTO < 60s). Creating RDS Read Replicas allows the application to route read-intensive reporting traffic to the replicas, successfully offloading the primary write-serving instance.

Adım Adım Çözüm

Analyze the high availability requirements (RTO under 60 seconds, RPO of zero).

Identify that synchronous replication and automatic failover are required, which matches the capabilities of RDS Multi-AZ deployments.

Single-AZ deployments with manual restores or asynchronous replication cannot meet the zero data loss (RPO = 0) and sub-minute recovery time (RTO < 60s) requirements.

Analyze the read scaling requirement (offloading peak monthly reporting traffic without affecting writes on the primary DB instance).

Identify that RDS Read Replicas must be deployed and configured as endpoints for the reporting application queries.

Read replicas utilize asynchronous replication to provide scalable read-only targets, preserving primary instance capacity for write operations.

Anahtar Kavram

Combining Amazon RDS Multi-AZ deployments for synchronous, zero-RPO high availability with Read Replicas for scalable, asynchronous read workloads.

Tahmini Süre:2m 0s

Soru 226Soru →

A logistics tracking company operates a fleet management system on AWS with a write-intensive workload. The backend database is an Amazon RDS for PostgreSQL DB instance. The architecture team wants to design a resilient database setup that survives an Availability Zone outage with a Recovery Time Objective (RTO) of under 2 minutes and a Recovery Point Objective (RPO) of 0 (no data loss). In addition, they must offload heavy read-only reporting queries from the primary database to ensure write operations are unaffected. Which database configuration should a solutions architect recommend?

Deploy a Single-AZ Amazon RDS for PostgreSQL DB instance, and create a Read Replica in a different Availability Zone. Configure the application to promote the Read Replica to primary in the event of an outage.

Deploy an Amazon RDS for PostgreSQL Multi-AZ DB instance deployment. Configure Amazon Route 53 latency routing to distribute the reporting read queries between the primary instance and the standby instance in the secondary Availability Zone.

Deploy an Amazon RDS for PostgreSQL Multi-AZ DB cluster with one primary writer instance and two readable standby DB instances.

Deploy a Single-AZ Amazon RDS for PostgreSQL DB instance. Configure AWS Database Migration Service (AWS DMS) to continuously replicate data to a warm standby instance in another Availability Zone, and use this instance for reporting queries.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon RDS for PostgreSQL Multi-AZ DB cluster with one primary writer instance and two readable standby DB instances.

Cevap

Deploy an Amazon RDS for PostgreSQL Multi-AZ DB cluster with one primary writer instance and two readable standby DB instances.

Deploying an Amazon RDS Multi-AZ DB cluster meets all requirements. It uses semi-synchronous replication to write data to two standby DB instances in different Availability Zones, guaranteeing a Recovery Point Objective (RPO) of 0. It also provides automatic failover in the event of an outage in less than 2 minutes (typically 35 to 75 seconds), meeting the Recovery Time Objective (RTO). Finally, because both standby instances are readable, they can serve read traffic to handle read scaling, eliminating the need to provision separate read replicas.

Adım Adım Çözüm

Analyze the recovery objectives (RTO < 2 minutes, RPO = 0) and scaling requirements (must scale read traffic).

Identify that the database configuration must support synchronous or semi-synchronous replication for RPO = 0, fast automated failover for RTO < 2 minutes, and active readable secondary nodes to scale reads.

This establishes the constraints that the chosen database solution must satisfy.

Evaluate Amazon RDS deployment options against these constraints.

A standard Multi-AZ DB instance deployment supports RPO = 0 and automatic failover, but its standby is passive and cannot serve reads. An RDS Multi-AZ DB cluster uses semi-synchronous replication (RPO = 0), performs automated failover in 35-75 seconds (RTO < 2 minutes), and contains two readable standby instances.

Comparing available RDS architectures helps select the one that meets both high availability and read scaling out-of-the-box.

Select the configuration that minimizes administrative overhead.

The Amazon RDS Multi-AZ DB cluster provides a single reader endpoint to load balance queries across the readable standbys without requiring manual setup of separate read replicas or promotion scripts.

Choosing the cluster option meets all performance and resiliency criteria with the least configuration effort.

Anahtar Kavram

Amazon RDS Multi-AZ DB clusters provide high availability, automatic failover, and read scaling by utilizing two readable standby DB instances across different Availability Zones.

Tahmini Süre:2m 0s

Soru 227Soru →

An enterprise is designing a highly available and resilient storage architecture for a containerized financial reporting application. The application runs on Amazon ECS tasks deployed across three Availability Zones in a single AWS Region. The tasks must concurrently read and write active ledger files and configuration files, requiring sub-millisecond access and strong resilience against Availability Zone failures. The architecture must achieve $99.99\%$ availability, protect against data loss with $99.999999999\%$ (11 9s) durability, and maintain read/write capability across the remaining zones with a Recovery Time Objective (RTO) of near-zero and a Recovery Point Objective (RPO) of zero in the event of a zone outage.

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

Geçerli olan tümünü seçin

Provision an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class, and mount it to the container tasks in all three Availability Zones.

Store the ledger and configuration files in an Amazon S3 bucket configured with the S3 Standard storage class, enabling S3 Versioning and using the AWS SDK for file operations.

Provision an Amazon EBS volume with Multi-Attach enabled, format it with a clustered file system, and mount it to the tasks across all three Availability Zones.

Store the active files in an Amazon S3 bucket using the S3 Glacier Flexible Retrieval storage class, and configure standard retrievals to fetch the files during container execution.

Deploy an Amazon RDS for PostgreSQL DB instance with a read replica in a second Availability Zone, and mount the replica as a shared block device to the tasks.

Cevabı ve açıklamayı göster

Cevap: Provision an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class, and mount it to the container tasks in all three Availability Zones.; Store the ledger and configuration files in an Amazon S3 bucket configured with the S3 Standard storage class, enabling S3 Versioning and using the AWS SDK for file operations.

Cevap

Deploying an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class, and storing files in an Amazon S3 bucket using the S3 Standard storage class with S3 Versioning enabled.

The correct storage configurations are deploying an Amazon Elastic File System (Amazon EFS) using EFS Standard storage, and using an Amazon S3 bucket with S3 Standard storage and Versioning enabled. Amazon EFS Standard provides a shared filesystem accessible concurrently across multiple Availability Zones with multi-AZ resilience, allowing ECS tasks to continue reading and writing during an AZ outage. Amazon S3 Standard provides

99.999999999\%

durability and replicates data across multiple Availability Zones within the region, ensuring zero data loss (RPO of zero) and near-zero RTO with proper versioning configuration.

Adım Adım Çözüm

Evaluate the storage sharing and access requirements.

The application requires concurrent read/write access to shared configuration and ledger files across Amazon ECS tasks located in different Availability Zones, needing sub-millisecond access and multi-AZ resilience.

This rules out single-AZ storage solutions and solutions that do not support concurrent multi-AZ access.

Analyze Multi-AZ storage options that support concurrent access.

Amazon EFS Standard provides a fully managed shared file system that is distributed across multiple Availability Zones. Amazon S3 Standard stores objects redundantly across multiple Availability Zones and provides high durability and immediate read/write access.

Both EFS Standard and S3 Standard offer multi-AZ replication, meeting the near-zero RTO and zero RPO requirements for zone-level resilience.

Examine and eliminate incorrect options based on technical limitations.

EBS Multi-Attach is restricted to a single Availability Zone. S3 Glacier Flexible Retrieval introduces significant retrieval delays. Amazon RDS is a relational database, not a mountable shared file system.

These limitations make the other options unsuitable for a resilient, shared, and low-latency storage solution.

Anahtar Kavram

Resilient multi-AZ shared storage services such as Amazon EFS and Amazon S3 Standard provide automatic replication across multiple Availability Zones, ensuring high availability and durability with near-zero recovery times in case of an AZ outage.

Tahmini Süre:2m 0s

Soru 228Soru →

A retail company runs a web application on AWS that uses an Amazon RDS for MySQL database. During peak shopping periods, the database experiences high volumes of read queries for generating inventory reports, which leads to performance degradation for transactional write operations. A solutions architect must redesign the database tier to be highly available within a single AWS Region with a recovery time objective (RTO) of less than 60 seconds. Additionally, the solution must offload the inventory reporting queries to scale read capacity independently.

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

Geçerli olan tümünü seçin

Deploy the RDS for MySQL database as a Multi-AZ DB instance deployment.

Create one or more RDS read replicas in different Availability Zones and update the reporting application to use the read replica endpoints.

Configure RDS read replicas as the failover target and use custom scripts to promote them to the primary database when the main instance is unavailable.

Deploy a warm standby RDS DB instance in a secondary AWS Region to handle automatic write failover during an Availability Zone outage.

Configure an Amazon Route 53 latency routing policy to distribute write requests directly to the read replicas during failover events.

Cevabı ve açıklamayı göster

Cevap: Deploy the RDS for MySQL database as a Multi-AZ DB instance deployment.; Create one or more RDS read replicas in different Availability Zones and update the reporting application to use the read replica endpoints.

Cevap

The solutions architect should deploy the database as an Amazon RDS Multi-AZ DB instance deployment to achieve automatic high availability and failover, and create RDS read replicas to offload inventory reporting queries.

To meet the low Recovery Time Objective (RTO) of less than 60 seconds within a single Region, the primary database must be configured with an Amazon RDS Multi-AZ DB instance deployment. This setup automatically replicates data synchronously to a standby instance in a different Availability Zone and performs automatic failover in the event of an outage. To scale read capacity independently and offload read-heavy reporting queries, the architect should deploy RDS read replicas and route read traffic to their endpoints, which prevents write operations on the primary DB instance from being degraded.

Adım Adım Çözüm

Analyze the high availability and recovery time objective (RTO) constraints.

An Amazon RDS Multi-AZ DB instance deployment provides automatic failover within a single Region, typically taking less than 60 seconds, meeting the RTO requirement.

Multi-AZ DB instances provide synchronous replication and automatic failover, which is required for high availability.

Analyze the read scaling requirements to offload analytics traffic from write operations.

Creating one or more RDS read replicas allows read-heavy queries to be routed to dedicated replica endpoints.

Read replicas utilize asynchronous replication to scale read workloads independently of the primary write database.

Evaluate and eliminate incorrect configurations that violate high availability or read scalability rules.

Discard manual failover configurations, multi-region database strategies that lack automatic failover, and options using read replicas as write targets.

These configurations violate regional high-availability constraints, Route 53 capabilities, and read-replica write limitations.

Anahtar Kavram

High availability via Multi-AZ deployments and read scaling via Read Replicas in Amazon RDS.

Tahmini Süre:2m 0s

Soru 229Soru →

A financial technology company is migrating its core transaction ledger application to Amazon Aurora PostgreSQL. The application requires high availability within a single AWS Region, with a Recovery Point Objective (RPO) of zero (no data loss) and a Recovery Time Objective (RTO) of less than 30 seconds. Additionally, the company needs to dynamically scale read operations during peak trading hours. Which database configuration best meets these requirements?

Deploy an Amazon Aurora PostgreSQL DB cluster with a primary writer instance and at least one Aurora Replica in a different Availability Zone, and configure the application to use the cluster endpoint and reader endpoint.

Deploy a single-node Amazon Aurora PostgreSQL DB cluster, and configure an Amazon RDS PostgreSQL Read Replica in a different Availability Zone to serve as the automatic failover target.

Deploy an Amazon Aurora PostgreSQL DB cluster in a Single-AZ configuration, and configure Amazon Route 53 latency routing to automatically redirect write traffic to a read replica during an outage.

Deploy a primary Amazon Aurora PostgreSQL DB instance, configure a standby instance in another Availability Zone, and implement a pilot light replication scheme to sync transaction logs every 10 minutes.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL DB cluster with a primary writer instance and at least one Aurora Replica in a different Availability Zone, and configure the application to use the cluster endpoint and reader endpoint.

Cevap

The correct configuration uses an Amazon Aurora PostgreSQL DB cluster with a primary writer instance and at least one Aurora Replica in a different Availability Zone. Amazon Aurora automatically replicates database storage across three Availability Zones within the region, ensuring an RPO of zero. If the primary instance fails, Aurora automatically fails over to the replica in another Availability Zone in less than 30 seconds (meeting the RTO requirement). The application can write to the cluster endpoint and scale read operations dynamically by using the reader endpoint.

Adım Adım Çözüm

Evaluate the RPO and RTO requirements to determine the storage and replication design.

Since RPO is zero, synchronous replication at the storage layer is required. Amazon Aurora automatically replicates data across three Availability Zones, ensuring zero data loss.

Asynchronous replication schemes or cross-region setups can introduce replication lag, resulting in an RPO greater than zero.

Evaluate the high availability and failover mechanism to meet the RTO requirement.

Deploying an Aurora Replica in a separate Availability Zone enables automatic failover in less than 30 seconds.

Manual intervention, external scripting (e.g., Lambda), or relying on read replicas for standard RDS failover increases failover times and fails the sub-30-second RTO constraint.

Address the read scaling requirement.

Direct read queries to the Aurora reader endpoint, which routes traffic across active replicas.

This offloads read traffic from the primary writer instance without impacting write performance.

Anahtar Kavram

Amazon Aurora high availability relies on multi-AZ storage replication and Aurora Replicas acting as failover targets with automated failover handling.

Soru 230Soru →

A medical imaging enterprise hosts a PACS (Picture Archiving and Communication System) on AWS. The application runs on a fleet of auto-scaled Amazon EC2 instances across multiple Availability Zones in the primary Region. The architecture requires:
- An Amazon RDS for PostgreSQL database hosting clinical transaction metadata.
- A shared storage layer containing raw DICOM image files (average size $12 \text{ MB}$ ) that must be read and written concurrently by the EC2 fleet.

The enterprise must design a disaster recovery (DR) architecture in a secondary AWS Region. The DR plan requires a Recovery Point Objective (RPO) of under $15 \text{ minutes}$ and a Recovery Time Objective (RTO) of under $10 \text{ minutes}$ for both the database and the image files.

Which architectural design meets these requirements while minimizing recovery time?

Deploy the primary database in a Multi-AZ configuration, and create a cross-Region read replica in the DR Region to be promoted upon failover. Store the DICOM images on a Regional Amazon Elastic File System (Amazon EFS) file system, and configure Amazon EFS Replication to replicate the file system to the DR Region. Deploy a Warm Standby environment in the DR Region with a pre-provisioned, scaled-down EC2 fleet.

Deploy the primary database in a Multi-AZ configuration, and create a cross-Region read replica in the DR Region. Store the DICOM images on a Regional Amazon EFS file system, and use an AWS Backup lifecycle policy to transition and replicate the EFS backups to an Amazon S3 Glacier Flexible Retrieval vault in the DR Region. Deploy a Warm Standby environment in the DR Region.

Deploy the primary database in a Multi-AZ configuration, and create a cross-Region read replica in the DR Region. Store the DICOM images on a Regional Amazon EFS file system, and configure Amazon EFS Replication to the DR Region. Deploy a Pilot Light environment in the DR Region with all EC2 application instances stopped, relying on automated scripts to start the instances immediately upon failover.

Deploy a Single-AZ primary database with a local read replica in a different Availability Zone configured as the primary automatic failover target. Store the DICOM images on Amazon EBS General Purpose SSD (gp3) volumes attached to the EC2 instances, and configure EBS snapshot replication to the DR Region. Deploy a Warm Standby environment in the DR Region.

Cevabı ve açıklamayı göster

Cevap: Deploy the primary database in a Multi-AZ configuration, and create a cross-Region read replica in the DR Region to be promoted upon failover. Store the DICOM images on a Regional Amazon Elastic File System (Amazon EFS) file system, and configure Amazon EFS Replication to replicate the file system to the DR Region. Deploy a Warm Standby environment in the DR Region with a pre-provisioned, scaled-down EC2 fleet.

Cevap

Deploy the primary database in a Multi-AZ configuration with a cross-Region read replica, store the diagnostic files on Regional Amazon EFS with cross-Region replication enabled, and deploy a Warm Standby environment in the secondary region.

The correct solution addresses high availability at the database layer (Multi-AZ) and provides cross-Region disaster recovery using RDS cross-Region Read Replicas. For storage, Regional Amazon EFS enables simultaneous read/write access across multiple Availability Zones, and EFS Replication fulfills the disaster recovery requirement asynchronously with a very low RPO. Deploying a Warm Standby (with pre-provisioned, scaled-down EC2 instances) ensures the systems can scale up to full production capacity within the

10 \text{ minute}

RTO.

Adım Adım Çözüm

Determine the shared storage requirements for concurrent access and high availability.

Amazon EFS Regional storage is selected because it allows concurrent read/write access from EC2 instances across multiple Availability Zones with sub-millisecond local latencies.

The EC2 application fleet must access the same files concurrently across different AZs, which is supported by EFS but not by EBS gp3 volumes.

Determine the replication strategy to achieve the

15 \text{ minute}

RPO in the DR Region.

Amazon EFS Replication is configured to replicate files asynchronously to the destination Region, and a cross-Region RDS Read Replica is created for the metadata database.

EFS Replication typically replicates changes within minutes, and cross-Region read replicas provide continuous asynchronous updates to the secondary database, satisfying the low RPO.

Select the appropriate disaster recovery environment strategy to meet the

10 \text{ minute}

RTO.

A Warm Standby strategy is implemented in the secondary Region, keeping a minimally scaled, running EC2 fleet ready to receive traffic.

A Warm Standby ensures that instances are already running and can be scaled out rapidly, meeting the sub-

10 \text{ minute}

RTO, whereas a Pilot Light setup with stopped instances would introduce startup delays that violate the RTO.

Anahtar Kavram

Designing a resilient and highly available multi-region architecture using Amazon EFS replication, Multi-AZ database configurations, and a Warm Standby DR strategy to meet strict RTO and RPO requirements.

Tahmini Süre:1m 30s

Soru 231Soru →

A logistics enterprise is migrating its central shipping tracking application to AWS. The application runs on Amazon ECS container instances distributed across three Availability Zones. The storage solution for the application must provide concurrent read/write POSIX-compliant file system access, offer sub-millisecond latency for active shipping manifests, and deliver 99.99% availability. Additionally, compliance mandates that the manifests must be replicated to a secondary AWS Region with a Recovery Point Objective (RPO) of 15 minutes. Which combination of storage configurations will meet these requirements? (Select TWO.)

Geçerli olan tümünü seçin

Deploy Amazon Elastic File System (Amazon EFS) with the Standard storage class to provide shared, multi-Availability Zone storage.

Configure Amazon EFS Replication to automatically replicate the file system to the secondary AWS Region.

Provision Amazon EBS gp3 volumes with Multi-Attach enabled, and mount them across all ECS container instances in the three Availability Zones.

Deploy Amazon EFS using the One Zone storage class and use AWS Backup to schedule replication to the secondary AWS Region.

Store the active manifests in an Amazon S3 bucket and configure an S3 Lifecycle policy to transition them to the S3 Glacier Instant Retrieval storage class in the secondary AWS Region.

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon Elastic File System (Amazon EFS) with the Standard storage class to provide shared, multi-Availability Zone storage.; Configure Amazon EFS Replication to automatically replicate the file system to the secondary AWS Region.

Cevap

Deploying Amazon EFS using the Standard storage class and configuring Amazon EFS Replication to the secondary AWS Region.

Deploying Amazon EFS using the Standard storage class provides a highly available, multi-AZ, POSIX-compliant shared file system supporting concurrent access from multiple ECS instances with sub-millisecond latency. Configuring Amazon EFS Replication automatically replicates the data to a destination region with a typical replication delay of minutes, meeting the 15-minute RPO requirement.

Adım Adım Çözüm

Analyze the file system and availability requirements.

Identify that the application requires concurrent, multi-AZ, POSIX-compliant access with sub-millisecond latency. Amazon EFS Standard meets this criteria.

EBS Multi-Attach cannot cross Availability Zones, and Amazon S3 does not natively support POSIX-compliant shared file mounting with concurrent read/writes.

Analyze the disaster recovery and RPO requirements.

Identify that the RPO requirement is 15 minutes, which requires a near real-time replication strategy. Amazon EFS Replication meets this requirement by automatically replicating changes within minutes.

Alternative backup tools like AWS Backup or manual snapshots do not support replication intervals that can guarantee a 15-minute RPO.

Anahtar Kavram

Amazon EFS replication provides cross-region replication for multi-AZ, POSIX-compliant shared file systems with low RPO targets.

Soru 232Soru →

A healthcare provider is deploying a critical patient scheduling web application on AWS that requires a highly resilient database tier. The database must support automatic failover with a Recovery Time Objective ( $RTO$ ) of less than 60 seconds and a Recovery Point Objective ( $RPO$ ) of $0$ (no data loss). Additionally, the application experiences read-heavy traffic spikes during morning scheduling hours that must be scaled efficiently.

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

Geçerli olan tümünü seçin

Deploy the database as an Amazon Aurora MySQL DB cluster with a primary DB instance and one or more Aurora Replicas in different Availability Zones.

Configure the application to connect to the database cluster's reader endpoint for read operations.

Deploy a single-instance Amazon RDS for MySQL database and configure an RDS Read Replica in a different Availability Zone to serve as the automatic failover target.

Set up an Amazon RDS for MySQL Multi-AZ DB instance deployment and configure the application to write to the secondary standby replica during peak hours to distribute write load.

Configure an Amazon Route 53 Latency routing policy to redirect database connection traffic to a backup database in a different AWS Region when the primary database is unhealthy.

Cevabı ve açıklamayı göster

Cevap: Deploy the database as an Amazon Aurora MySQL DB cluster with a primary DB instance and one or more Aurora Replicas in different Availability Zones.; Configure the application to connect to the database cluster's reader endpoint for read operations.

Cevap

Deploy the database as an Amazon Aurora MySQL DB cluster with a primary DB instance and one or more Aurora Replicas in different Availability Zones, and configure the application to connect to the database cluster's reader endpoint for read operations.

Deploying an Amazon Aurora cluster with Replicas in different Availability Zones provides automated failover within 30 seconds without data loss because of its shared virtual storage volume, meeting both RTO and RPO requirements. Utilizing the reader endpoint allows the application to balance read requests across the replicas, solving the read scaling requirement.

Adım Adım Çözüm

Evaluate the HA, RTO, and RPO requirements.

The requirement of automatic failover, RTO < 60s, and RPO = 0 points to Amazon Aurora's shared storage architecture with Aurora Replicas, which automatically handles failover in about 30 seconds with no data loss.

Standard RDS Multi-AZ DB instances provide HA but do not natively scale reads without adding separate Read Replicas, whereas Aurora integrates replica failover and cluster-wide read scalability out of the box.

Address the read scaling requirement.

Using the Aurora reader endpoint directs read traffic to the Aurora Replicas, offloading read-heavy queries from the primary writer instance.

This scales reads efficiently during morning traffic spikes without impacting write operations.

Analyze why other choices are incorrect.

Configurations relying on manual promotion of RDS Read Replicas or attempting to write directly to passive RDS standby replicas fail to meet high availability or operational guidelines.

RDS standby instances in a Multi-AZ deployment do not accept connections, and RDS Read Replicas are asynchronously replicated and cannot failover automatically.

Anahtar Kavram

High availability and read scaling in Amazon Aurora DB clusters

Soru 233Soru →

A healthcare organization manages an on-premises electronic health record (EHR) system that requires low-latency, local block storage access for active patient records. The organization needs to design a resilient hybrid storage and disaster recovery solution on AWS. The solution must support a Recovery Point Objective (RPO) of 1 hour and a Recovery Time Objective (RTO) of 2 hours. In the event of an on-premises virtualization failure, the organization must be able to restore the volumes in AWS and run the EHR application on Amazon EC2 instances. Which storage configuration will meet these requirements with the lowest latency for local operations?

Configure AWS Storage Gateway in Stored Volumes mode to store the primary dataset locally for low-latency access, while asynchronously backing up the data to Amazon S3 as Amazon EBS snapshots. Restore these snapshots to EBS volumes and attach them to EC2 instances during a disaster recovery event.

Configure AWS Storage Gateway in Tape Gateway mode to write the backup data to virtual tapes. Use lifecycle policies to transition these tapes to Amazon S3 Glacier Flexible Retrieval to minimize costs, and initiate standard retrievals to recover the tapes and restore them to EC2 during a disaster.

Configure AWS Storage Gateway in Stored Volumes mode. Implement a Pilot Light disaster recovery strategy by keeping a scaled-down fleet of EC2 instances running continuously in AWS, expecting that this configuration requires zero startup time or volume attachment steps during failover.

Configure AWS Storage Gateway in Cached Volumes mode. For the data tier, deploy Amazon RDS and configure an RDS Read Replica in the target AWS region as the primary automatic failover target to handle immediate write workloads without utilizing Multi-AZ deployments.

Cevabı ve açıklamayı göster

Cevap: Configure AWS Storage Gateway in Stored Volumes mode to store the primary dataset locally for low-latency access, while asynchronously backing up the data to Amazon S3 as Amazon EBS snapshots. Restore these snapshots to EBS volumes and attach them to EC2 instances during a disaster recovery event.

Cevap

The configuration utilizing AWS Storage Gateway in Stored Volumes mode satisfies all requirements. It ensures that the entire dataset is stored on-premises to provide low-latency access to the EHR system. Additionally, it asynchronously replicates data to Amazon S3 as EBS snapshots, satisfying the low RPO. During a disaster recovery event, these snapshots can be quickly restored to Amazon EBS volumes and attached to Amazon EC2 instances, allowing the EHR application to run on AWS within the 2-hour RTO.

Adım Adım Çözüm

Analyze on-premises latency and access requirements.

Since the application requires low-latency, local block storage access for the EHR system, Stored Volumes mode is preferred over Cached Volumes mode because it maintains the full primary copy of the data on-premises.

Stored Volumes mode ensures all active data is stored locally for immediate access, while Cached Volumes mode only stores frequently accessed data locally.

Evaluate backup and recovery mechanisms for meeting RTO and RPO.

Volume Gateway Stored Volumes asynchronously backs up data to Amazon S3 as incremental EBS snapshots, satisfying a low RPO.

EBS snapshots stored in Amazon S3 can be restored directly to EBS volumes in AWS within minutes, meeting the 2-hour RTO requirement.

Review the recovery procedure during disaster recovery on Amazon EC2.

In a disaster recovery event, create EBS volumes from the stored EBS snapshots and attach them to newly launched Amazon EC2 instances to resume EHR application operations.

This provides a clear path to run the EHR application in AWS using standard EC2 and EBS capabilities.

Anahtar Kavram

AWS Storage Gateway Volume Gateway (Stored Volumes) provides local low-latency access to the full volume dataset on-premises while maintaining point-in-time EBS snapshots in Amazon S3 for disaster recovery and EC2 restoration.

Alternatif Yöntem

An alternative hybrid solution would be using AWS Outposts to host the active patient records and application compute locally while utilizing AWS Backup to replicate EBS volumes directly to an AWS Region. However, this is significantly more expensive and complex than AWS Storage Gateway.

Tahmini Süre:2m 0s

Soru 234Soru →

An e-commerce company hosts its product catalog image library on an Amazon S3 bucket in the us-east-1 Region. These images must be delivered globally with the lowest possible latency. To ensure reliability, the company requires that if the primary S3 bucket in us-east-1 becomes unavailable or returns server errors, the architecture must automatically serve images from a replicated S3 bucket in the us-west-2 Region. The solution must minimize operational complexity.

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

Geçerli olan tümünü seçin

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

Enable origin failover for the CloudFront origin group and configure it to fail over to the secondary origin on specific HTTP status codes such as 500, 502, 503, and 504.

Configure an Amazon Route 53 latency routing policy with health checks to route user requests directly to the S3 bucket website endpoints.

Deploy AWS WAF to monitor the health of the primary S3 bucket and trigger an AWS Lambda function to update the CloudFront origin if an outage is detected.

Configure the CloudFront cache behavior with a Time to Live (TTL) of zero to force CloudFront to validate content availability with the primary bucket on every request.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon CloudFront distribution and define an origin group containing the primary S3 bucket as the primary origin and the secondary S3 bucket as the secondary origin.; Enable origin failover for the CloudFront origin group and configure it to fail over to the secondary origin on specific HTTP status codes such as 500, 502, 503, and 504.

Cevap

To meet the requirements, the solutions architect should create an Amazon CloudFront distribution with an origin group containing the primary S3 bucket as the primary origin and the secondary S3 bucket as the secondary origin. Additionally, they should enable origin failover in the origin group and configure it to fail over to the secondary origin on status codes such as 500, 502, 503, and 504.

The correct architecture uses Amazon CloudFront for low-latency edge caching of static images, coupled with CloudFront Origin Groups for high availability. By creating an origin group containing the primary S3 bucket and the secondary S3 bucket, and setting up failover on server error status codes (500, 502, 503, 504), CloudFront will automatically fall back to serving content from the secondary bucket in the event of an outage or error with the primary bucket. This is a native feature that minimizes operational complexity.

Adım Adım Çözüm

Configure content delivery to minimize latency.

Amazon CloudFront is deployed to cache the product catalog images at edge locations globally.

CloudFront caches static files close to users, fulfilling the requirement for lowest possible global latency.

Establish the secondary S3 bucket as a fallback origin.

An origin group is configured in CloudFront with the primary S3 bucket in us-east-1 as the primary origin and the replicated S3 bucket in us-west-2 as the secondary origin.

This establishes the logical mapping required for automatic origin-level failover.

Configure the failover threshold criteria.

Origin failover is enabled on the origin group, targeting HTTP status codes 500, 502, 503, and 504.

When CloudFront receives these server errors from the primary S3 bucket, it automatically routes the request to the secondary bucket, achieving high availability with zero manual intervention or custom code.

Anahtar Kavram

CloudFront Origin Groups and Origin Failover for static S3 assets

Soru 235Soru →

A company hosts a global media application that distributes static images from an Amazon S3 bucket. To minimize latency and protect the application from origin server failures, a solutions architect is implementing an Amazon CloudFront distribution. The architecture must automatically redirect traffic to a backup S3 bucket in a different AWS Region if the primary S3 bucket returns an HTTP 502 or 504 error. Which combination of actions should the solutions architect perform to meet these resiliency requirements? (Select TWO.)

Geçerli olan tümünü seçin

Create a CloudFront origin group containing both the primary and backup S3 buckets as origins, designating the primary bucket as primary.

Configure the CloudFront distribution's cache behavior to direct requests to the newly created origin group.

Configure an Amazon Route 53 failover routing policy that points to the primary and backup S3 bucket endpoints, and set the CloudFront origin to this Route 53 record.

Deploy an AWS WAF web ACL associated with the CloudFront distribution, and configure a custom rule to intercept 5xx errors and redirect requests to the backup S3 bucket.

Set the Minimum TTL, Default TTL, and Maximum TTL to 0 in the cache behavior settings to force CloudFront to query both S3 buckets simultaneously for each request.

Cevabı ve açıklamayı göster

Cevap: Create a CloudFront origin group containing both the primary and backup S3 buckets as origins, designating the primary bucket as primary.; Configure the CloudFront distribution's cache behavior to direct requests to the newly created origin group.

Cevap

Create a CloudFront origin group with the primary and backup S3 buckets, and configure the cache behavior to point to this origin group.

To set up automatic failover for static content distributed via CloudFront, you must create an origin group that contains a primary origin (the primary S3 bucket) and a secondary origin (the backup S3 bucket). You specify the failover criteria (e.g., HTTP 502 and 504 status codes) that trigger the failover. Finally, you configure the cache behavior to target the origin group so that requests are routed through this failover logic.

Adım Adım Çözüm

Define origins in the CloudFront distribution

Two distinct origins are created within the CloudFront configuration: one pointing to the primary S3 bucket and another pointing to the backup S3 bucket.

Before an origin group can be configured, the individual origin endpoints must exist in the distribution.

Create and configure an origin group

An origin group is established with the primary S3 bucket set as the primary origin and the backup S3 bucket set as the failover origin. The failover criteria are configured to trigger on HTTP 502 and 504 status codes.

This establishes the automatic failover relationship and defines which HTTP status codes from the primary origin will trigger a redirection to the backup origin.

Associate the origin group with the cache behavior

The cache behavior for the static images is updated to target the origin group instead of a single origin.

This ensures that incoming user requests are processed by the origin group, enabling the failover mechanism when errors occur.

Anahtar Kavram

CloudFront Origin Groups and Origin Failover

Soru 236Soru →

A logistics company is migrating its core order processing system to Amazon RDS. The database must be highly available across multiple Availability Zones with a Recovery Time Objective (RTO) of less than 2 minutes and a Recovery Point Objective (RPO) of 0 (no data loss). Additionally, the solutions architect must scale read performance horizontally to handle reporting queries without impacting write latency on the primary database instance.

Which combination of database configuration and application routing strategies will meet these requirements? (Select TWO.)

Geçerli olan tümünü seçin

Deploy the database as a standard Amazon RDS Multi-AZ DB instance deployment and route read queries to the standby instance.

Deploy the database as an Amazon RDS Multi-AZ DB cluster with one writer and two readable standby DB instances.

Deploy a single-AZ Amazon RDS DB instance and configure a cross-AZ Read Replica, using Amazon Route 53 to automatically promote the replica during an outage.

Configure the application to route write queries to the cluster endpoint and read queries to the reader endpoint of the DB cluster.

Use Amazon Route 53 latency-based routing to distribute database write traffic between the primary database instance and the read replica.

Cevabı ve açıklamayı göster

Cevap: Deploy the database as an Amazon RDS Multi-AZ DB cluster with one writer and two readable standby DB instances.; Configure the application to route write queries to the cluster endpoint and read queries to the reader endpoint of the DB cluster.

Cevap

Deploy the database as an Amazon RDS Multi-AZ DB cluster with one writer and two readable standby DB instances, and configure the application to route write queries to the cluster endpoint and read queries to the reader endpoint of the DB cluster.

Deploying an Amazon RDS Multi-AZ DB cluster provides a primary writer instance and two readable standby instances across three Availability Zones, ensuring automatic failover under 2 minutes and zero data loss (RPO of 0) via semi-synchronous replication. The application can scale reads horizontally by routing queries to the reader endpoint, which load-balances the traffic among the standby instances, while routing writes to the cluster endpoint.

Adım Adım Çözüm

Identify the high availability and zero data loss (RPO = 0) requirements during an Availability Zone outage.

Determine that standard single-instance or asynchronous replica configurations are insufficient, and a synchronous or semi-synchronous replication method (such as RDS Multi-AZ or Aurora) is required.

Multi-AZ deployments provide automatic failover and ensure data is replicated to another AZ before writes are committed, satisfying the RPO of 0 and RTO under 2 minutes.

Evaluate how to support horizontal read scaling alongside high availability in RDS.

Identify that a standard Multi-AZ DB instance has a passive standby that cannot be read from, whereas an RDS Multi-AZ DB cluster provides two readable standby instances.

Choosing the Multi-AZ DB cluster deployment enables both high availability and horizontal read scaling off the standby instances.

Determine the proper application routing mechanism to separate reads and writes in the cluster.

Route write operations to the cluster endpoint (pointing to the primary writer) and read operations to the reader endpoint (which load-balances reads to the standby instances).

This separation allows the application to scale reads horizontally without overloading the primary writer database instance.

Anahtar Kavram

Amazon RDS Multi-AZ DB cluster configurations for high availability and horizontal read scaling.

Soru 237Soru →

A company operates a globally distributed mobile gaming application. The gaming client communicates with a backend matchmaking and state service using a custom TCP-based protocol. The backend is currently hosted on Amazon ECS tasks behind an Application Load Balancer (ALB) in a single AWS Region. Users in distant regions are experiencing high latency and connection timeouts due to public internet routing inefficiencies. Additionally, client devices require a fixed set of IP addresses for security allowlisting in corporate firewalls. Which solution should a solutions architect recommend to resolve the latency issues while meeting the security requirements?

Configure AWS Global Accelerator in front of the ALB. Register the ALB as the endpoint group target. Update the client configuration to connect via the provided Anycast static IP addresses.

Configure an Amazon CloudFront distribution with the ALB as the origin. Route traffic through CloudFront using a custom Domain Name System (DNS) record, and enable Origin Shield.

Configure Amazon Route 53 with latency-based routing to resolve the application's domain name directly to the ALB. Apply AWS WAF to the ALB to accelerate TCP connections.

Deploy AWS WAF and enable AWS Shield Advanced directly on the ALB. Use the AWS Shield Anycast IPs to route global client traffic through the nearest AWS edge location.

Cevabı ve açıklamayı göster

Cevap: Configure AWS Global Accelerator in front of the ALB. Register the ALB as the endpoint group target. Update the client configuration to connect via the provided Anycast static IP addresses.

Cevap

Configure AWS Global Accelerator in front of the ALB. Register the ALB as the endpoint group target. Update the client configuration to connect via the provided Anycast static IP addresses.

AWS Global Accelerator is designed to optimize routing and improve availability for TCP and UDP traffic by onboarding traffic at the nearest AWS Edge Location and routing it over the congestion-free AWS global network. It also provides two static Anycast IP addresses, which satisfies the client firewall allowlisting requirement.

Adım Adım Çözüm

Analyze the protocol and client requirements.

The application uses a custom TCP-based protocol (non-HTTP/S) and requires static IP addresses on the client-side for firewall allowlisting.

This rules out Amazon CloudFront, which is restricted to HTTP/HTTPS traffic, and requires a service that can provide static Anycast IPs.

Evaluate network acceleration services.

AWS Global Accelerator supports non-HTTP TCP/UDP protocols, routes traffic over the AWS global network to reduce latency, and provides two static Anycast IP addresses.

This directly matches all requirements of the scenario, including latency reduction and fixed IP support.

Select the optimal architecture configuration.

Provision AWS Global Accelerator with the Application Load Balancer (ALB) as the endpoint target.

This setup allows clients to connect to the static Anycast IPs, routing their TCP packets over the optimized AWS global backbone to the ALB.

Anahtar Kavram

AWS Global Accelerator vs. Amazon CloudFront for non-HTTP/S TCP traffic

Tahmini Süre:1m 30s

Soru 238Soru →

A company hosts a public REST API for real-time weather telemetry data on Amazon ECS behind an Application Load Balancer (ALB) in the us-east-1 Region. The telemetry data is updated every 5 minutes. To support a global user base, the company needs to minimize latency, protect the ECS backend from traffic spikes, and ensure high availability by automatically routing traffic to a standby ECS deployment in the us-west-2 Region if the primary Region experiences an outage. Which architecture should a solutions architect recommend to meet these requirements with the LEAST operational overhead?

Configure an Amazon CloudFront distribution with an origin group. Set the us-east-1 ALB as the primary origin and the us-west-2 ALB as the failover origin. Configure a cache behavior with a TTL of 5 minutes.

Configure an Amazon CloudFront distribution with a single origin pointing to an Amazon Route 53 latency-based routing DNS record. Create Route 53 latency records with health checks pointing to the ALBs in both regions.

Configure an Amazon CloudFront distribution pointing to the us-east-1 ALB. Associate an AWS WAF web ACL with a custom rule that redirects traffic to the us-west-2 ALB when it detects HTTP 5xx errors from the primary ALB.

Configure an Amazon CloudFront distribution with an origin group containing the us-east-1 ALB as primary and the us-west-2 ALB as failover. Set the cache behavior Minimum TTL, Maximum TTL, and Default TTL to 0.

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon CloudFront distribution with an origin group. Set the us-east-1 ALB as the primary origin and the us-west-2 ALB as the failover origin. Configure a cache behavior with a TTL of 5 minutes.

Cevap

The correct configuration uses an Amazon CloudFront origin group with the primary Application Load Balancer as the primary origin and the standby Application Load Balancer as the failover origin. This native CloudFront feature allows for seamless, low-latency failover at the edge on specific HTTP status codes. Setting a 5-minute TTL optimizes performance for global users and shields the backend ECS containers from traffic spikes by caching the telemetry data.

Adım Adım Çözüm

Analyze caching requirements

Since telemetry data updates every 5 minutes, caching it for 5 minutes (300 seconds) at CloudFront edge locations will significantly reduce backend load and improve performance.

This satisfies the constraint of protecting the ECS backend from traffic spikes while serving low-latency data to global users.

Analyze regional resiliency requirements

Identify that CloudFront origin groups allow setting up active-passive failover with primary and standby ALBs across different regions.

This configuration automatically redirects client requests to the secondary origin if the primary origin returns specific HTTP 5xx error codes or connection timeouts, without relying on DNS propagation delays.

Evaluate and eliminate incorrect routing and firewall configurations

Eliminate solutions that rely on DNS-level failover for CloudFront origins (due to DNS caching) or misapply AWS WAF for traffic routing.

These alternatives either fail to provide rapid, reliable failover or use services outside their intended scope.

Anahtar Kavram

Amazon CloudFront Origin Groups and Edge Caching

Soru 239Soru →

A company is migrating a financial transaction application to AWS. The application database tier uses Amazon RDS for PostgreSQL. The database must be highly available with automatic failover to support a low recovery time objective (RTO) during an Availability Zone outage. Additionally, the application must offload read-intensive reporting queries from the primary database to prevent performance degradation on write operations.

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

Geçerli olan tümünü seçin

Configure a Multi-AZ DB instance deployment to achieve automatic failover across different Availability Zones.

Deploy RDS Read Replicas in different Availability Zones to handle the reporting query workload.

Configure Route 53 latency routing to automatically redirect write traffic to a read replica if the primary database becomes unavailable.

Use a read replica in a different Availability Zone as the primary automated failover target for the database tier.

Utilize a Pilot Light disaster recovery configuration in a second AWS region to achieve automatic database failover within seconds.

Cevabı ve açıklamayı göster

Cevap: Configure a Multi-AZ DB instance deployment to achieve automatic failover across different Availability Zones.; Deploy RDS Read Replicas in different Availability Zones to handle the reporting query workload.

Cevap

Deploying a Multi-AZ DB instance configuration to provide high availability and creating RDS Read Replicas to offload reporting workloads is the correct combination of configurations.

To meet the requirements, the solutions architect should deploy a Multi-AZ DB instance configuration and create RDS Read Replicas. A Multi-AZ DB instance deployment provides high availability and automatic failover by synchronously replicating data to a standby instance in a different Availability Zone. Read Replicas allow the database to offload read-intensive reporting workloads by asynchronously replicating data to one or more read-only instances, which prevents read queries from affecting the primary database's write performance.

Adım Adım Çözüm

Identify the high availability and failover requirements.

Determine that an Amazon RDS Multi-AZ DB instance deployment is needed to provide synchronous replication and automatic failover in the event of an Availability Zone outage.

Multi-AZ deployments provide built-in high availability and automatic failover for Amazon RDS databases.

Identify the read scaling and performance requirements.

Determine that one or more RDS Read Replicas must be created to handle read-heavy reporting queries.

Read replicas use asynchronous replication to offload read traffic from the primary DB instance, protecting write performance.

Eliminate options that use incorrect failover mechanisms or disaster recovery strategies.

Reject options proposing read replicas as automatic failover targets, Route 53 latency routing for database failover, or Pilot Light DR for high availability.

Read replicas do not support automatic HA failover, Route 53 latency routing does not manage RDS failover, and Pilot Light configurations have higher RTOs and are meant for disaster recovery, not HA.

Anahtar Kavram

Configuring Amazon RDS for high availability using Multi-AZ deployments and scaling read capacity using Read Replicas.

Soru 240Soru →

A media company is designing a globally distributed video-on-demand (VOD) streaming application. The application delivers HTTP Live Streaming (HLS) video files, which consist of static media segments stored in an Amazon S3 bucket. The company requires a highly resilient architecture that minimizes delivery latency for global viewers and automatically handles S3 origin failures. The solution must minimize operational overhead.

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

Geçerli olan tümünü seçin

Create an Amazon CloudFront origin group that contains the primary S3 bucket as the primary origin and a replicated secondary S3 bucket in another AWS Region as the failover origin.

Update the default cache behavior of the CloudFront distribution to target the origin group instead of individual S3 origins.

Configure an Amazon Route 53 latency-based routing policy to fail over traffic directly between the primary and secondary S3 bucket website endpoints.

Deploy AWS Global Accelerator in front of the S3 buckets to cache the video segments closer to the users and handle regional failover.

Associate an AWS WAF web ACL with the primary S3 bucket to monitor origin status codes and redirect requests to the secondary S3 bucket when HTTP 503 errors are detected.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon CloudFront origin group that contains the primary S3 bucket as the primary origin and a replicated secondary S3 bucket in another AWS Region as the failover origin.; Update the default cache behavior of the CloudFront distribution to target the origin group instead of individual S3 origins.

Cevap

Create an Amazon CloudFront origin group containing the primary S3 bucket and a replicated secondary S3 bucket as the failover origin, and configure the cache behavior to target this origin group.

To design a resilient edge caching architecture with minimal latency and low operational overhead, Amazon CloudFront must be used. By creating an origin group containing the primary S3 bucket and a secondary S3 bucket, CloudFront natively manages failover if the primary origin is unavailable. The cache behavior must target the origin group to direct incoming viewer requests to the correct group.

Adım Adım Çözüm

Analyze the requirements for global low-latency delivery and high origin availability of static assets.

Amazon CloudFront is identified as the optimal tool to cache static media segments at global edge locations to minimize latency.

Direct S3 endpoint access or network routing services do not provide caching capabilities.

Establish origin redundancy by replicating content to a secondary S3 bucket in another AWS Region.

A secondary S3 bucket is prepared to act as a fallback origin.

A secondary origin is required to enable failover capability.

Group the primary and secondary origins within CloudFront.

A CloudFront origin group is created with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin.

This enables native origin failover within CloudFront without adding custom application logic.

Configure the distribution's cache behavior to target the origin group.

The default cache behavior is updated to point to the origin group.

CloudFront cache behaviors must be explicitly pointed to the origin group to leverage failover routing.

Anahtar Kavram

CloudFront Origin Groups and Origin Failover

ÖncekiSayfa 12 / 20Sonraki

Design Resilient Architectures

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Alternatif Yöntem

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm