Design Resilient Architectures

382 soru

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

A logistics company is designing an automated warehouse inventory synchronization system. When items are scanned at receiving stations, inventory update events are generated. These events must be delivered to three separate systems: a centralized inventory database, a third-party vendor replenishment system, and a real-time shipping analytics dashboard. The centralized inventory database must process the events in the exact chronological order they were generated to avoid reconciliation errors, whereas the other systems can process events in any order. If any downstream system is unavailable, it must not impact the others, and the failed events must be retried automatically. Which solution meets these requirements with the least operational overhead?

Publish the inventory update events to an Amazon SNS FIFO topic. Subscribe three Amazon SQS FIFO queues to the SNS FIFO topic, with each queue consuming messages for one of the downstream systems.

Publish the inventory update events to a standard Amazon SNS topic. Subscribe three standard Amazon SQS queues to the SNS topic, with each queue consuming messages for one of the downstream systems.

Publish the inventory update events to a single Amazon SQS FIFO queue. Configure the centralized inventory database, vendor replenishment system, and shipping analytics dashboard to poll this queue and delete messages after processing.

Publish the inventory update events to an Amazon Kinesis data stream. Provision a single shard and configure the three downstream systems to consume the events from the stream using the Kinesis Client Library (KCL).

Cevabı ve açıklamayı göster

Cevap: Publish the inventory update events to an Amazon SNS FIFO topic. Subscribe three Amazon SQS FIFO queues to the SNS FIFO topic, with each queue consuming messages for one of the downstream systems.

Cevap

Publish the inventory update events to an Amazon SNS FIFO topic and subscribe three Amazon SQS FIFO queues to it, with each queue consuming messages for one of the downstream systems.

The correct solution leverages the fan-out pattern with ordering. By publishing events to an Amazon SNS FIFO topic, the message order is preserved. Subscribing three Amazon SQS FIFO queues (one for each downstream system) ensures that each system gets its own independent copy of every event, ensuring fault isolation and automatic retries. The SQS FIFO queue bound to the inventory database guarantees that the events are processed in the exact order they were scanned, preventing race conditions or incorrect state calculations.

Adım Adım Çözüm

Select a message fan-out service to deliver events to multiple downstream systems.

Amazon SNS is chosen because it natively supports publishing messages to multiple subscribers (fan-out pattern).

The requirement states that events must be delivered to three separate systems independently.

Ensure strict ordering guarantees for the centralized inventory database.

Use Amazon SNS FIFO and Amazon SQS FIFO queues.

Standard SQS/SNS do not guarantee ordering. SQS FIFO queues guarantee chronological order processing, and they can only subscribe to SNS FIFO topics.

Decouple downstream processing to ensure isolation and retries.

Create a separate SQS FIFO queue for each of the three downstream systems.

If any downstream system fails, its dedicated SQS queue will hold the messages for retry without affecting the other systems' queues.

Anahtar Kavram

Decoupling message fan-out with strict ordering guarantees using Amazon SNS FIFO and Amazon SQS FIFO queues.

Soru 102Soru →

A company is deploying a global gaming application that requires a multi-region, active-active database configuration. The database must allow users in both North America and Europe to perform local read and write operations with sub-millisecond latency. The data must be replicated bi-directionally across regions with a Recovery Point Objective (RPO) of less than 1 second. Which two database configuration steps should the solutions architect perform to meet these requirements?

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

Create an Amazon DynamoDB table and enable DynamoDB Streams with the "New and old images" view type.

Add the replica region to the DynamoDB table to automatically establish a DynamoDB global table.

Deploy an Amazon RDS PostgreSQL DB instance in Multi-AZ mode and configure cross-region read replicas to accept local write operations in both regions.

Configure Route 53 latency-based routing to direct write requests to the nearest database endpoint and automatically synchronize writes across regions.

Deploy a warm standby database replica in the secondary region and set up a pilot light replication model to handle active-active traffic.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon DynamoDB table and enable DynamoDB Streams with the "New and old images" view type.; Add the replica region to the DynamoDB table to automatically establish a DynamoDB global table.

Cevap

To meet the requirements of active-active writes, low latency, and sub-second replication across multiple regions, you must configure Amazon DynamoDB global tables. This is achieved by creating a DynamoDB table, enabling DynamoDB Streams with the new and old images view type, and then adding the target replica region to the table configuration.

Establishing a global, active-active database configuration with sub-millisecond latency requires Amazon DynamoDB global tables. To configure global tables, a solutions architect must enable DynamoDB Streams with the new and old images view type on the source table and then add the replica regions. This configures managed bi-directional replication, allowing local reads and writes in all replica regions.

Adım Adım Çözüm

Identify the active-active multi-region database requirement.

Amazon DynamoDB global tables is identified as the appropriate service to support active-active writes and reads in multiple regions with sub-millisecond latencies.

Relational databases like RDS do not support multi-region active-active write configurations natively, whereas DynamoDB global tables provide fully managed, multi-region replication with local read/write performance.

Configure the prerequisites for DynamoDB global tables.

Enable DynamoDB Streams on the primary table with the view type set to new and old images.

DynamoDB global tables rely on DynamoDB Streams to track and propagate changes across region replicas.

Add replica regions to the table configuration.

Add the desired AWS region as a replica in the table's global tables settings.

This establishes the bi-directional replication between the selected regions to complete the global tables setup.

Anahtar Kavram

Amazon DynamoDB Global Tables

Soru 103Soru →

An enterprise is migrating a critical SQL-based inventory application to AWS. The database must be highly available within a single AWS Region. The architecture must achieve a Recovery Time Objective (RTO) of less than 30 seconds and a Recovery Point Objective (RPO) of zero (no data loss) during an Availability Zone outage. Additionally, the application experiences sudden spikes in read traffic that must be scaled independently without affecting the primary write database. Which two database configurations or actions should a solutions architect recommend to satisfy these requirements? (Select TWO.)

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

Deploy an Amazon Aurora PostgreSQL DB cluster with a primary DB instance and at least one Aurora Replica in a different Availability Zone.

Configure the application's read operations to use the DB cluster reader endpoint.

Create a single-instance Amazon RDS PostgreSQL DB instance and set up an RDS Read Replica in a different Availability Zone to serve as the automatic failover target.

Configure an Amazon RDS PostgreSQL Multi-AZ DB instance and use Amazon Route 53 latency-based routing to distribute read queries to the standby database instance.

Set up an Amazon RDS PostgreSQL DB instance in one Availability Zone and configure AWS Database Migration Service (AWS DMS) to sync data to a scaled-down warm standby instance in another Availability Zone.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL DB cluster with a primary DB instance and at least one Aurora Replica in a different Availability Zone.; Configure the application's read operations to use the DB cluster reader endpoint.

Cevap

Deploying an Amazon Aurora PostgreSQL DB cluster with a primary DB instance and at least one Aurora Replica in a different Availability Zone, and configuring the application's read operations to use the DB cluster reader endpoint.

Deploying an Amazon Aurora PostgreSQL DB cluster with a replica in another Availability Zone ensures automatic failover in less than 30 seconds with zero data loss, satisfying both the RTO and RPO requirements. Directing read traffic to the Aurora reader endpoint allows read queries to be load-balanced across replicas, scaling the read workload independently of the primary write instance.

Adım Adım Çözüm

Evaluate the HA failover time (RTO) and data loss (RPO) requirements.

Identify that a database configuration with automatic failover under 30 seconds and synchronous replication (RPO of 0) is necessary. Amazon Aurora PostgreSQL with an Aurora Replica fits this requirement.

Amazon Aurora automates failover to a replica within 30 seconds, and its shared storage architecture replicates writes synchronously across three Availability Zones to prevent data loss.

Address the requirement to scale read traffic independently without impacting write operations.

Determine that read operations should be routed away from the primary writer instance using a read-scaling mechanism. In Aurora, this is handled by connecting to the reader endpoint.

The Aurora reader endpoint automatically load balances read-only connections among available Aurora Replicas, isolating read-heavy spikes from the primary writer instance.

Eliminate options that fail to meet high availability, replication, or read-scaling constraints.

Exclude configurations using RDS Read Replicas for primary failover (requires manual intervention), RDS standby instances for read traffic (standbys are passive), or AWS DMS to a warm standby (asynchronous replication with higher RTO).

These configurations violate basic AWS RDS/Aurora architectural constraints regarding read routing, synchronous replication, and automated failover capabilities.

Anahtar Kavram

Amazon Aurora high availability architecture relies on synchronous storage replication across multiple Availability Zones, automated failover to Aurora Replicas within 30 seconds, and endpoint management (writer and reader endpoints) to decouple read and write traffic.

Soru 104Soru →

An energy utility provider runs a smart grid monitoring application on Amazon EC2 instances in an Auto Scaling group across multiple Availability Zones in the us-east-1 Region. The application requires a shared, POSIX-compliant file system to store active telemetry logs. Additionally, raw historical log files must be archived to a highly durable object store.

The provider wants to establish a disaster recovery (DR) architecture in the us-west-2 Region with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 15 minutes for both active logs and historical archives. Historical archives must be accessible within minutes during a DR event.

Which two configurations should the solutions architect implement to meet these requirements?

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

Configure Amazon EFS replication to automatically replicate the shared file system from us-east-1 to us-west-2.

Store raw historical logs in an Amazon S3 bucket in us-east-1, and configure Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to a destination bucket in us-west-2.

Store raw historical logs in Amazon S3, and configure a replication rule to copy the objects to a destination bucket in us-west-2 with the S3 Glacier Flexible Retrieval storage class.

Migrate the shared telemetry logs to an Amazon RDS Multi-AZ DB instance in us-east-1, and configure a cross-region Read Replica in us-west-2 to act as the automated, zero-administrative failover endpoint.

Implement a Pilot Light disaster recovery strategy by creating daily Amazon Machine Images (AMIs) of the EC2 instances and daily backups of the shared storage, copying them to us-west-2, and restoring them during a failover event.

Cevabı ve açıklamayı göster

Cevap: Configure Amazon EFS replication to automatically replicate the shared file system from us-east-1 to us-west-2.; Store raw historical logs in an Amazon S3 bucket in us-east-1, and configure Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to a destination bucket in us-west-2.

Cevap

Configure Amazon EFS replication to automatically replicate the shared file system from us-east-1 to us-west-2, and store raw historical logs in an Amazon S3 bucket in us-east-1, configuring Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to a destination bucket in us-west-2.

To satisfy a POSIX-compliant shared file system requirement with a 15-minute RTO and RPO in a secondary region, Amazon EFS replication is the correct choice because it automatically and continuously replicates changes to the destination region within minutes. To satisfy the raw historical logs archiving requirement with a 15-minute RPO, Amazon S3 Cross-Region Replication with S3 Replication Time Control (S3 RTC) is the correct choice because it provides a service level agreement (SLA) to replicate 99.9% of objects within 15 minutes, and storing them in standard S3 buckets ensures they are immediately accessible during a failover event.

Adım Adım Çözüm

Analyze the file system requirement and RTO/RPO limits.

The application requires a POSIX-compliant shared file system. Amazon EFS provides this capability for EC2 instances. To meet the 15-minute RTO and RPO in the us-west-2 DR region, Amazon EFS replication is required as it replicates data within minutes.

Identify the primary storage service that supports shared POSIX access and cross-region replication within minutes.

Analyze the historical log archiving requirement and RTO/RPO limits.

Historical logs must be stored in a highly durable object store (Amazon S3). To meet the 15-minute RPO, S3 Cross-Region Replication (CRR) with Replication Time Control (S3 RTC) must be configured, which guarantees replication of 99.9% of objects within 15 minutes. To meet the 15-minute RTO, the target storage class must allow rapid access (milliseconds/minutes).

Identify the object storage replication and retrieval configuration that satisfies the RTO and RPO criteria.

Evaluate and eliminate incorrect architectures.

Using S3 Glacier Flexible Retrieval for replicated archives introduces retrieval delays of 3-5 hours, violating the RTO. Daily backups (Pilot Light) violate the 15-minute RPO. Relying on RDS Read Replicas does not solve the shared file system requirement and lacks automated cross-region failover.

Ensure all other options are eliminated based on AWS service limitations and scenario constraints.

Anahtar Kavram

Designing highly available, multi-region storage systems using EFS Replication and S3 Replication Time Control (RTC) to meet strict RTO and RPO requirements.

Soru 105Soru →

A financial services company is deploying a critical online transaction processing (OLTP) application on AWS that requires a multi-region database architecture. The primary database cluster will be hosted in `us-east-1`, and the disaster recovery (DR) cluster will be located in `us-west-2`. The architecture must achieve a Recovery Point Objective (RPO) of less than $1$ second and a Recovery Time Objective (RTO) of less than $1$ minute. The database tier must support scaling read traffic in the secondary region while keeping the write path resilient to regional failures. Which two database configurations or actions should a solutions architect recommend to meet these requirements? (Select TWO.)

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

Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2.

Configure Aurora Auto Scaling for the reader instances in the us-west-2 secondary cluster to handle fluctuating read query workloads.

Provision an Amazon RDS for PostgreSQL DB instance with Multi-AZ enabled in us-east-1 and set up a cross-region read replica in us-west-2 to act as the primary failover target.

Use Amazon Route 53 latency-based routing to distribute database write and read requests directly between the database endpoints in both regions.

Configure a Pilot Light disaster recovery strategy by scheduling hourly database snapshots in us-east-1 and copying them to us-west-2 to restore on demand.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2.; Configure Aurora Auto Scaling for the reader instances in the us-west-2 secondary cluster to handle fluctuating read query workloads.

Cevap

To meet the requirements, the solutions architect should deploy an Amazon Aurora PostgreSQL Global Database across the primary and secondary regions, and configure Aurora Auto Scaling for the reader instances in the secondary region cluster.

Deploying an Amazon Aurora PostgreSQL Global Database ensures storage-level replication lag remains under

1

second, fulfilling the low RPO limit. If a regional outage occurs, the secondary cluster in the recovery region can be promoted to primary in under

1

minute, satisfying the RTO limit. Furthermore, configuring Aurora Auto Scaling on the reader instances in the secondary region allows the secondary cluster to handle dynamic read request volumes independently of the primary write path.

Adım Adım Çözüm

Select a multi-region database engine that supports low-latency replication.

Amazon Aurora Global Database provides storage-level asynchronous replication across AWS regions with typical latencies of less than

1

second.

This satisfies the strict RPO requirement of less than

1

second.

Ensure the disaster recovery failover capability fits the target recovery window.

Aurora Global Database secondary clusters can be promoted to a standalone primary cluster with full read-write capabilities in less than

1

minute.

This allows the database to meet the RTO requirement of less than

1

minute.

Configure scaling for the read workload in the secondary region.

Enable Aurora Auto Scaling on reader instances in the secondary region cluster.

This allows the reader endpoints to dynamically scale out or scale in based on query volume without affecting the primary cluster.

Anahtar Kavram

Resilient Database Configurations and High Availability

Soru 106Soru →

A healthcare software provider is deploying a web application on AWS that uses an Amazon Aurora PostgreSQL database. The application has strict compliance requirements:

1. High availability within the primary region (us-east-1) with a Recovery Time Objective (RTO) of less than $30$ seconds and a Recovery Point Objective (RPO) of $0$ (no data loss).
2. A cross-region disaster recovery (DR) site in us-west-2 with an RTO of less than $15$ minutes and an RPO of less than $5$ minutes. The DR region must also support low-latency read operations during normal business hours to serve local reports.

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

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

Deploy an Amazon Aurora PostgreSQL DB cluster in the primary region with one or more Aurora Replicas placed in different Availability Zones.

Create an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, and use the secondary cluster to serve local read traffic.

Deploy a single-instance Amazon RDS for PostgreSQL database in us-east-1 and configure a cross-region read replica in us-west-2 to automatically perform failover for the primary region.

Set up a Pilot Light disaster recovery strategy in us-west-2 by deploying an idle, single-node PostgreSQL database on an Amazon EC2 instance that is shut down and only started and synchronized daily from Amazon S3 database backups.

Configure an Amazon Route 53 Latency routing policy with health checks to automatically route database connection traffic between the database in us-east-1 and the database in us-west-2.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL DB cluster in the primary region with one or more Aurora Replicas placed in different Availability Zones.; Create an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, and use the secondary cluster to serve local read traffic.

Cevap

Deploying an Amazon Aurora PostgreSQL DB cluster with replicas in different Availability Zones in the primary region, and creating an Amazon Aurora Global Database with a secondary cluster in the disaster recovery region.

Deploying an Amazon Aurora cluster with replicas across different Availability Zones guarantees high availability and automatic failover (RTO < 30 seconds) with zero data loss (RPO = 0) because Aurora replicates storage synchronously across three Availability Zones. Adding an Aurora Global Database to replicate asynchronously to us-west-2 provides an RPO of less than 1 second and can be promoted to primary in less than a minute, meeting the DR RTO/RPO requirements while allowing the secondary cluster to serve local read operations.

Adım Adım Çözüm

Evaluate the high availability requirement in the primary region (us-east-1).

Identify that an Amazon Aurora DB cluster with replicas in different Availability Zones provides automatic failover (RTO < 30 seconds) and synchronous replication across storage nodes (RPO of 0).

This configuration ensures that if the primary instance fails, a replica in another Availability Zone is promoted automatically with no data loss.

Evaluate the cross-region disaster recovery (DR) and read scaling requirements in us-west-2.

Identify that Amazon Aurora Global Databases replicate data asynchronously to a secondary region with an RPO of less than 1 second and an RTO of less than 1 minute when managed failover is used, while also allowing the secondary cluster to serve read traffic.

This satisfies the cross-region RTO (< 15 minutes) and RPO (< 5 minutes) limits and offloads reporting read traffic.

Eliminate configurations that do not support automatic failover or fail to meet the recovery objectives.

Reject using RDS read replicas for primary failover, setting up an EC2-based Pilot Light strategy with daily backups, and using Route 53 Latency routing for database failover.

These alternatives either lack automatic failover capabilities, exhibit recovery times and data loss exceeding the thresholds, or misapply DNS routing policies to database replication.

Anahtar Kavram

Amazon Aurora Multi-AZ and Global Databases provide high availability and cross-region disaster recovery by separating compute and storage replication layers.

Soru 107Soru →

A financial technology company is deploying a global transactional platform across two AWS Regions: us-east-1 (primary) and us-west-2 (secondary). The application requires a relational database backend that can survive a complete regional outage with a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 1 minute. Read operations must be served locally in both regions to minimize latency, while write operations must be routed appropriately to avoid data divergence. Which combination of actions should a solutions architect take to meet these requirements? (Select TWO.)

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

Deploy an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, and enable write forwarding on the secondary cluster.

In the event of a primary regional outage, initiate a managed failover of the Aurora Global Database to promote the secondary DB cluster in us-west-2 to primary.

Configure an Amazon RDS for PostgreSQL database in us-east-1 with a cross-region read replica in us-west-2, and configure Route 53 failover routing to promote the replica.

Set up Route 53 Latency routing with active-active failover to route database write traffic directly to both database clusters simultaneously in both regions.

Deploy the database as an Amazon RDS for PostgreSQL Multi-AZ DB cluster in us-east-1 and use AWS Database Migration Service (DMS) to replicate data to us-west-2.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, and enable write forwarding on the secondary cluster.; In the event of a primary regional outage, initiate a managed failover of the Aurora Global Database to promote the secondary DB cluster in us-west-2 to primary.

Cevap

Deploy an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, and enable write forwarding on the secondary cluster. Also, in the event of a primary regional outage, initiate a managed failover of the Aurora Global Database to promote the secondary DB cluster in us-west-2 to primary.

Deploying an Amazon Aurora Global Database with write forwarding enabled ensures low-latency reads in both regions and coordinates writes to the primary cluster. During a regional outage, initiating a managed failover promotes the secondary cluster to primary with zero data loss, achieving an RPO of less than 1 second and an RTO of less than 1 minute.

Adım Adım Çözüm

Select a multi-region relational database engine that supports cross-region replication latency under 1 second.

Amazon Aurora Global Database is chosen because its physical replication lag is typically under 1 second.

This satisfies the Recovery Point Objective (RPO) requirement of less than 1 second.

Enable write forwarding on the secondary Aurora cluster.

Applications in the secondary region can read locally and send writes to the local cluster, which are forwarded to the primary region.

This allows reads to be served locally with low latency while avoiding split-brain data divergence.

Define the disaster recovery failover mechanism.

Managed failover is configured to promote the secondary cluster to primary during a disaster.

Aurora Global Database managed failover completes in less than 1 minute (meeting the RTO requirement of less than 1 minute) and guarantees zero data loss.

Anahtar Kavram

Amazon Aurora Global Database managed failover and write forwarding support cross-region high availability with RTO < 1 minute and RPO < 1 second.

Tahmini Süre:3m 0s

Soru 108Soru →

A health insurance provider is migrating its transactional claims processing application to AWS. The application database requires a MySQL-compatible relational engine. The solutions architect must design a highly resilient database architecture that spans two AWS Regions in an active-passive setup. The design must achieve a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 1 minute for a regional disaster. Furthermore, the database must support automatic failover in the primary region within 60 seconds if an Availability Zone fails.

Which configuration meets these requirements with the least operational complexity?

Deploy an Amazon Aurora MySQL Multi-AZ cluster in the primary region, and configure an Amazon Aurora Global Database with a secondary cluster in the secondary region.

Deploy an Amazon RDS for MySQL Multi-AZ DB instance in the primary region, and configure a cross-region read replica in the secondary region to act as the primary failover target using custom failover scripts.

Deploy a single Amazon RDS for MySQL DB instance in the primary region, and configure AWS Backup to take hourly database snapshots, copying them to the secondary region to restore a new DB instance during a disaster.

Deploy two independent Amazon RDS for MySQL Multi-AZ DB instances, one in the primary region and one in the secondary region, and use an Amazon Route 53 latency routing policy to synchronize data write operations between them.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora MySQL Multi-AZ cluster in the primary region, and configure an Amazon Aurora Global Database with a secondary cluster in the secondary region.

Cevap

Deploying an Amazon Aurora MySQL Multi-AZ cluster in the primary region and using Amazon Aurora Global Database to create a secondary cluster in the secondary region meets all constraints with the lowest operational overhead. Aurora Multi-AZ clusters use shared storage and automatically fail over to a reader instance in another Availability Zone within 30 seconds, satisfying the local high availability requirements. For disaster recovery, Aurora Global Databases use storage-based, physical replication that operates asynchronously but has latency typically under 1 second (satisfying the Recovery Point Objective of less than 1 minute). In a disaster event, the secondary cluster can be promoted to a standalone primary cluster with read-write capabilities in under 10 minutes (satisfying the Recovery Time Objective of less than 15 minutes). This setup is managed natively by AWS, minimizing operational complexity.

Adım Adım Çözüm

Analyze the database engine and high availability (HA) constraints in the primary region.

The application requires a MySQL-compatible database that must survive an Availability Zone outage and fail over within 60 seconds.

This helps eliminate options that do not support rapid local auto-failover, such as Single-AZ deployments.

Evaluate the disaster recovery (DR) constraints for the secondary region.

The DR solution requires an RPO of less than 1 minute and an RTO of less than 15 minutes.

The RPO constraint requires near-real-time cross-region data replication, while the RTO constraint requires a fast, automated or highly streamlined database promotion process.

Compare the candidate architectures against AWS managed replication capabilities and operational complexity.

Amazon Aurora Global Database replicates storage blocks across regions in under 1 second (RPO < 1 second) and supports promotion in under 10 minutes (RTO < 15 minutes), meeting all criteria natively.

Choosing the architecture with the lowest operational overhead ensures compliance with the requirement of least operational complexity.

Anahtar Kavram

Amazon Aurora Global Database provides low-latency cross-region storage replication (RPO < 1 second) and fast managed failover/promotion (RTO < 10 minutes) for multi-region resilience, while Aurora Multi-AZ clusters handle rapid, automated local failovers (RTO < 30 seconds).

Soru 109Soru →

A digital marketing agency maintains an on-premises file server containing active design assets and historical archives. The agency requires a hybrid storage solution that provides low-latency local read/write access to active assets while ensuring that all files are stored with high durability in the cloud. If the local data center suffers a catastrophic power failure, the agency must be able to resume file access for its designers within a Recovery Time Objective (RTO) of $15$ minutes, using either a secondary office or AWS-based compute instances. Which storage configuration meets these requirements?

Deploy an AWS Storage Gateway (Volume Gateway) in stored volume mode on-premises. Configure the gateway to backup point-in-time snapshots to Amazon S3 Glacier Flexible Retrieval, and retrieve them using Standard retrieval to construct new volumes at the secondary office.

Provision an Amazon EBS gp3 volume and enable EBS Multi-Attach to share the block storage concurrently between the on-premises servers and AWS EC2 instances, while relying on Amazon RDS read replicas to manage the failover process.

Deploy an AWS Storage Gateway (Amazon S3 File Gateway) on-premises, and configure the local file server to mount the NFS file share backed by an Amazon S3 bucket. If the primary on-premises site fails, deploy a new S3 File Gateway virtual machine (VM) at the secondary office or on an Amazon EC2 instance, and associate it with the existing S3 bucket.

Deploy an Amazon EFS file system using One Zone storage to host the design assets. Configure a Pilot Light disaster recovery strategy where the standby EFS file system in a secondary Availability Zone is kept inactive and only provisioned when a failover occurs.

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Storage Gateway (Amazon S3 File Gateway) on-premises, and configure the local file server to mount the NFS file share backed by an Amazon S3 bucket. If the primary on-premises site fails, deploy a new S3 File Gateway virtual machine (VM) at the secondary office or on an Amazon EC2 instance, and associate it with the existing S3 bucket.

Cevap

Deploying an AWS Storage Gateway (Amazon S3 File Gateway) on-premises allows designers to access files locally via NFS with low latency, while the master copy is stored in Amazon S3. In the event of a disaster, a new gateway VM can be quickly created on-premises at a secondary office or as an Amazon EC2 instance and pointed to the same S3 bucket. This restores file sharing capabilities in minutes, satisfying the

15

-minute Recovery Time Objective (RTO).

Adım Adım Çözüm

Analyze the requirements for a hybrid storage solution that offers local caching and high cloud durability.

Identify that AWS Storage Gateway (Amazon S3 File Gateway) fits this scenario by caching active data locally while storing the primary copy in Amazon S3.

S3 File Gateway provides NFS/SMB access to objects in S3 with a local cache for low-latency read/write operations.

Evaluate the disaster recovery failover strategy against the

15

-minute Recovery Time Objective (RTO).

Determine that recreating the gateway virtual machine (VM) and pointing it to the existing Amazon S3 bucket allows immediate retrieval of file metadata and data access.

Since the file data is preserved in the S3 bucket, a new gateway can be quickly provisioned on-premises or on an EC2 instance without waiting for lengthy data restores.

Anahtar Kavram

AWS Storage Gateway (S3 File Gateway) hybrid storage and disaster recovery failover mechanics.

Tahmini Süre:2m 0s

Soru 110Soru →

An enterprise is designing a disaster recovery (DR) architecture for a critical web application. The primary infrastructure is located in the us-east-1 Region, consisting of an Application Load Balancer (ALB) and an Amazon Aurora PostgreSQL Global Database. The passive DR site is in the eu-west-1 Region, using a Pilot Light strategy where application servers are scaled to zero to minimize costs, and an Aurora read replica is maintained for data replication.

The Solutions Architect must configure Amazon Route 53 to implement automatic failover. Under normal operations, all client traffic must be routed to us-east-1. If the primary region's compute resources or database fail, Route 53 must redirect all traffic to eu-west-1. The architect must ensure that traffic is not routed to eu-west-1 before the pilot light resources are scaled up, and Route 53 does not route traffic to both regions simultaneously.

Which TWO configurations should the Solutions Architect implement to meet these requirements?

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

Configure a Route 53 primary failover record pointing to the us-east-1 ALB with Evaluate Target Health set to Yes. Configure a secondary failover record pointing to the eu-west-1 ALB with Evaluate Target Health set to No.

Create a Route 53 metric-based health check linked to a CloudWatch alarm that monitors Aurora database health and database connection failures in us-east-1, and associate this health check with the primary Route 53 record.

Configure Route 53 Latency routing records for both us-east-1 and eu-west-1, associating each record with a standard Route 53 HTTP health check to ensure failover to the healthy region.

Set the Route 53 Failover routing policy directly on the Amazon Aurora database cluster endpoints to automate the promotion of the Aurora read replica in eu-west-1 during a failover.

Configure both primary and secondary Route 53 failover records with Evaluate Target Health set to Yes, relying on the eu-west-1 ALB target group health checks to trigger EC2 Auto Scaling policies when DNS queries begin failing over.

Cevabı ve açıklamayı göster

Cevap: Configure a Route 53 primary failover record pointing to the us-east-1 ALB with Evaluate Target Health set to Yes. Configure a secondary failover record pointing to the eu-west-1 ALB with Evaluate Target Health set to No.; Create a Route 53 metric-based health check linked to a CloudWatch alarm that monitors Aurora database health and database connection failures in us-east-1, and associate this health check with the primary Route 53 record.

Cevap

Configure the primary failover record pointing to the primary ALB with Evaluate Target Health set to Yes while setting Evaluate Target Health to No on the secondary failover record, and create a Route 53 metric-based health check linked to a CloudWatch alarm monitoring database health.

The correct configurations ensure robust active-passive DNS failover. First, the primary failover record must point to the primary ALB with target health evaluation enabled, while the secondary failover record pointing to the standby ALB must have target health evaluation disabled (set to No). This is because the standby region uses a Pilot Light DR pattern where application servers are scaled to zero. A target-health-check enabled secondary record would be seen as unhealthy by Route 53 due to zero healthy registered targets, causing Route 53 to route to both endpoints if the primary fails. Second, Route 53 health checks can be linked to CloudWatch alarms. Because standard ALB health checks do not monitor database status, creating a metric-based health check linked to a CloudWatch alarm that tracks database connectivity and write availability ensures Route 53 will fail over if the primary database cluster becomes unavailable.

Adım Adım Çözüm

Determine the correct Route 53 routing policy for an active-passive disaster recovery configuration.

Identify that a Failover routing policy must be used to ensure all traffic goes to the primary region (us-east-1) under normal conditions, and is redirected to the secondary region (eu-west-1) only during an outage.

Active-passive failover requires directing all traffic to the active site, unlike active-active policies such as Latency routing.

Analyze target health evaluation settings for both the primary and secondary ALB endpoints when using a Pilot Light strategy.

Primary failover record points to the primary ALB with Evaluate Target Health set to Yes. Secondary failover record points to the secondary ALB with Evaluate Target Health set to No.

Because the secondary region runs in a Pilot Light state with compute instances scaled to zero, the secondary ALB has no healthy targets and would fail health checks. Setting Evaluate Target Health to Yes on the secondary would cause Route 53 to see both regions as unhealthy and route traffic to both. Setting it to No ensures Route 53 always treats the secondary as healthy when the primary fails.

Integrate database health checks into Route 53 routing decisions.

Configure a CloudWatch alarm monitoring Aurora database health metrics (such as connection count or write availability) and link a Route 53 metric-based health check to this alarm, associating it with the primary failover record.

Standard Route 53 health checks and ALB target group health checks only evaluate compute target health, not database availability. A metric-based health check ensures Route 53 triggers a failover if the database layer fails while the web servers remain running.

Anahtar Kavram

Configuring Route 53 active-passive DNS failover in a Pilot Light DR scenario requires coordinating compute scaling states with Route 53's health evaluation mechanisms (Evaluate Target Health) and using CloudWatch alarm-based health checks to incorporate backend database health into the DNS failover decision.

Soru 111Soru →

A financial technology company is deploying a transaction processing system on AWS. The application uses an Amazon RDS for PostgreSQL database. To meet regulatory compliance, the database architecture must achieve a Recovery Point Objective (RPO) of zero (no data loss) and a Recovery Time Objective (RTO) of less than 35 seconds for any single Availability Zone failure within the primary AWS Region. The application also requires local read scaling within the primary Region to handle reporting queries without affecting write transaction throughput. Which database configuration satisfies these resilience and scalability requirements with the lowest RTO?

Deploy a Single-AZ DB instance with two Read Replicas in different Availability Zones, and configure an AWS Lambda function to promote a Read Replica to primary if the main instance fails.

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

Deploy two independent Single-AZ DB instances in different Availability Zones, configure bidirectional database replication, and use an Amazon Route 53 latency routing policy with health checks to route traffic.

Deploy a standard Amazon RDS Multi-AZ DB instance with a standby in a second Availability Zone, and configure a cross-Region Read Replica to handle local reporting queries.

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 across three Availability Zones.

Cevap

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

Deploying an Amazon RDS Multi-AZ DB cluster satisfies all constraints. It uses semi-synchronous replication to guarantee an RPO of zero (no data loss) if at least one standby acknowledges the write. Its architecture enables automatic failovers that typically complete in under 35 seconds, meeting the strict RTO target. Furthermore, it allows read traffic to be routed to the two standby DB instances, providing native local read scaling within the primary Region.

Adım Adım Çözüm

Analyze the RPO requirement.

An RPO of zero requires synchronous or semi-synchronous database replication so that no acknowledged transactions are lost during an Availability Zone failure.

Asynchronous replication mechanisms, such as standard RDS Read Replicas, can lead to data loss during failover and do not guarantee an RPO of zero.

Analyze the RTO requirement.

An RTO of less than 35 seconds requires an automated failover mechanism that promotes a backup instance immediately without manual intervention or script execution delays.

Standard Multi-AZ DB instance deployments typically failover in 60 to 120 seconds, which is too slow. Multi-AZ DB clusters feature transaction-routing mechanisms that achieve failovers in under 35 seconds.

Evaluate the read scalability requirement.

The configuration must support readable standby instances or replicas within the same Region to offload reporting queries.

A Multi-AZ DB cluster allows the two standby instances to serve read traffic, satisfying local read scaling natively, whereas standard Multi-AZ DB instances do not allow reading from the standby.

Anahtar Kavram

Amazon RDS Multi-AZ DB Cluster Deployments vs Multi-AZ DB Instance Deployments

Soru 112Soru →

A financial technology enterprise is designing the storage architecture for its transactional auditing application. The application processes high-volume trade ledgers that must be stored with high availability and durability. The company requires that all ingested ledger files be replicated across two AWS Regions to support a disaster recovery strategy with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 5 minutes. Additionally, older historical ledger archives must be stored cost-effectively for 7 years; these archives are rarely accessed, but when an audit occurs, the data must be fully retrievable within a strict RTO of 2 hours.

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

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

Configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled on the S3 buckets hosting the ledger files.

Transition the historical ledger archives to Amazon S3 Glacier Flexible Retrieval and utilize Expedited retrievals when accessing the data for audits.

Transition the historical ledger archives to Amazon S3 Glacier Deep Archive and utilize Standard retrievals when accessing the data for audits.

Store the ledger files in an Amazon RDS DB instance and create a cross-region Read Replica to achieve automatic cross-region failover within the 5-minute RTO.

Configure an AWS Storage Gateway Tape Gateway in a Pilot Light disaster recovery model to restore the active ledger files to the secondary Region.

Cevabı ve açıklamayı göster

Cevap: Configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled on the S3 buckets hosting the ledger files.; Transition the historical ledger archives to Amazon S3 Glacier Flexible Retrieval and utilize Expedited retrievals when accessing the data for audits.

Cevap

The correct configurations are configuring Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled on the primary bucket, and transitioning historical archives to Amazon S3 Glacier Flexible Retrieval with Expedited retrievals used during audits.

To achieve an RPO of 15 minutes for object replication between two AWS Regions, enabling Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) is necessary because S3 RTC provides a service level agreement (SLA) to replicate 99.9% of objects within 15 minutes. To retrieve archived files within a 2-hour RTO during audits, the data must be stored in a class that supports fast retrieval. Amazon S3 Glacier Flexible Retrieval supports Expedited retrievals, which complete within 1-5 minutes, fitting the 2-hour window.

Adım Adım Çözüm

Identify the replication RPO and RTO for active files.

The active ledger files must be replicated to a second region with an RPO of 15 minutes and an RTO of 5 minutes.

This establishes the performance boundaries for the replication technology selection.

Evaluate replication features for Amazon S3.

Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) replicates 99.9% of objects within 15 minutes.

S3 RTC provides the necessary SLA to meet the strict 15-minute RPO, and replication keeps the data available in the secondary region for immediate retrieval.

Analyze the retrieval RTO for historical archives.

Historical archives must be stored cost-effectively for 7 years and retrieved within a 2-hour window during audit events.

This defines the latency limits of the cold storage classes and retrieval tier.

Compare Glacier storage classes and retrieval options.

Amazon S3 Glacier Flexible Retrieval with Expedited retrievals restores data in 1 to 5 minutes.

Standard retrieval from Glacier takes 3 to 5 hours, and standard retrieval from Glacier Deep Archive takes 12 hours, meaning only Expedited retrieval meets the 2-hour RTO constraint.

Anahtar Kavram

Implementing resilient and highly available multi-region storage systems using S3 replication controls and optimizing lifecycle transitions based on recovery time objectives (RTO).

Tahmini Süre:2m 30s

Soru 113Soru →

An enterprise retail company wants to deploy a multi-region, active-active database configuration for its online shopping cart application. The database needs to support write operations in both the us-east-1 and us-west-2 Regions with sub-second replication latency. The solution must achieve a Recovery Point Objective (RPO) of under 1 second and a Recovery Time Objective (RTO) of near-zero in the event of a regional outage. The database must automatically handle replication and conflict resolution based on a last-writer-wins rule. Which two actions should a solutions architect take to configure the database to meet these resilience requirements? (Select two.)

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

Enable Amazon DynamoDB Streams on the primary table in us-east-1 and set the stream view type to NEW_AND_OLD_IMAGES.

Add a replica of the table in us-west-2 to the DynamoDB table configuration to establish a global table.

Set up Amazon Route 53 Latency routing with active-passive failover checks to route database write queries, relying on DNS routing to manage write replication.

Deploy an Amazon RDS for PostgreSQL database in us-east-1 and configure a cross-region read replica in us-west-2, promoting the replica manually during a regional failover.

Configure an Amazon Aurora PostgreSQL Global Database and write a custom AWS Lambda script to execute a manual database failover using a pilot light disaster recovery strategy.

Cevabı ve açıklamayı göster

Cevap: Enable Amazon DynamoDB Streams on the primary table in us-east-1 and set the stream view type to NEW_AND_OLD_IMAGES.; Add a replica of the table in us-west-2 to the DynamoDB table configuration to establish a global table.

Cevap

The correct options are to enable Amazon DynamoDB Streams with the stream view type set to NEW_AND_OLD_IMAGES, and to add a replica of the table in the us-west-2 Region to establish a global table.

To support active-active writes in both us-east-1 and us-west-2 with an RPO of under 1 second and automatic conflict resolution, Amazon DynamoDB Global Tables is the ideal solution. Configuring a global table requires enabling DynamoDB Streams on the source table with the stream view type set to NEW_AND_OLD_IMAGES, and then adding the replica region to create the multi-region configuration.

Adım Adım Çözüm

Enable DynamoDB Streams with NEW_AND_OLD_IMAGES on the existing DynamoDB table in the primary region.

Creates a stream that captures all modifications (insert, update, delete) to the table data, which DynamoDB uses to replicate changes.

DynamoDB Streams is a mandatory prerequisite for setting up DynamoDB Global Tables.

Add the target replica region (us-west-2) to the DynamoDB table configuration.

Creates an identical table in the secondary region and enables bi-directional active-active replication between the regions.

This establishes a DynamoDB Global Table, which natively replicates updates with sub-second latency and automatically handles conflict resolution.

Anahtar Kavram

Amazon DynamoDB Global Tables provides a fully managed, multi-region, active-active database replication solution. To configure it, you must enable DynamoDB Streams with the NEW_AND_OLD_IMAGES view type on the source table and add replica regions to the table configuration.

Soru 114Soru →

A company hosts a dynamic web application on Amazon EC2 instances behind an Application Load Balancer (ALB) in the us-east-1 Region. The company wants to improve the application's performance for global users by caching static content. Additionally, they need to ensure high availability by serving a static maintenance page from an Amazon S3 bucket in the us-west-2 Region if the ALB returns HTTP 502 or 504 errors. The solution must minimize latency for global users, automate the failover process, and minimize operational complexity. Which configuration should a solutions architect implement to meet these requirements?

Configure an Amazon Route 53 latency routing policy with health checks pointing to both the ALB in us-east-1 and the S3 bucket in us-west-2 to distribute traffic and fail over during outages.

Create an Amazon CloudFront distribution with the ALB as the origin. Configure an AWS WAF web ACL with custom rules to inspect response codes and redirect client requests to the S3 bucket when the ALB returns 502 or 504 status codes.

Create an Amazon CloudFront distribution. Configure an Origin Group containing the ALB as the primary origin and the S3 bucket as the secondary origin. Set the failover criteria to include status codes 502 and 504.

Create an Amazon CloudFront distribution with the ALB as the origin. Configure the Cache Behavior with a Minimum TTL and Default TTL of 0 seconds for all paths, and write a custom Lambda@Edge function to intercept origin response errors and redirect users to the S3 bucket.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon CloudFront distribution. Configure an Origin Group containing the ALB as the primary origin and the S3 bucket as the secondary origin. Set the failover criteria to include status codes 502 and 504.

Cevap

The correct answer is to create an Amazon CloudFront distribution and configure an Origin Group containing the ALB as the primary origin and the S3 bucket as the secondary origin, setting the failover criteria to include status codes 502 and 504.

The correct answer is to configure an Amazon CloudFront distribution with an Origin Group. CloudFront Origin Groups allow you to specify a primary origin and a secondary failover origin. When the primary origin returns specific HTTP status codes such as 502 or 504, CloudFront automatically routes traffic to the secondary origin (the S3 bucket) to serve the static maintenance page. This solution provides edge caching to reduce latency globally, implements automatic failover, and has low operational complexity.

Adım Adım Çözüm

Analyze the requirements for edge caching, latency reduction, and automatic failover.

Identify that Amazon CloudFront is the best service to reduce global latency through edge caching, and that failover must handle 502 and 504 error codes from the Application Load Balancer.

CloudFront caches content at edge locations globally, reducing latency, and native failover is required to handle origin errors.

Evaluate native high-availability features of Amazon CloudFront.

Determine that CloudFront Origin Groups allow setting up a primary origin (ALB) and a secondary origin (S3 bucket) with failover criteria for specific HTTP status codes.

Using native CloudFront Origin Groups eliminates the need for complex DNS-level failover or custom Lambda@Edge code, reducing operational complexity.

Select the correct configuration that combines caching and resilient origin failover.

Create an Origin Group with the primary origin pointing to the ALB and the secondary origin pointing to the S3 bucket, configuring failover for 502 and 504 status codes.

This configuration meets the performance requirements by caching content at the edge and satisfies the resiliency requirements by automatically serving a static maintenance page if the ALB is unhealthy.

Anahtar Kavram

Edge caching and resilient origin failover using Amazon CloudFront Origin Groups

Tahmini Süre:2m 0s

Soru 115Soru →

An enterprise healthcare organization is designing a highly resilient storage and database architecture for its Picture Archiving and Communication System (PACS) imaging application. The system consists of a metadata catalog stored in Amazon RDS for PostgreSQL and raw DICOM medical images stored as objects. The disaster recovery (DR) strategy requires a Recovery Time Objective (RTO) of $15$ minutes and a Recovery Point Objective (RPO) of $15$ minutes across a secondary AWS Region. The primary region deployment must be highly available with $99.99\%$ availability and $99.999999999\%$ durability for the raw images. Additionally, radiologists at local clinics require low-latency local access to the most recently acquired medical images. Which architecture meets these requirements with the lowest operational overhead?

Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to a destination bucket in the secondary region. Deploy the RDS PostgreSQL database in a Multi-AZ configuration in the primary region, and configure a cross-region read replica in the secondary region.

Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure an S3 Lifecycle policy to transition objects immediately to the S3 Glacier Flexible Retrieval storage class in the secondary region. Deploy the RDS PostgreSQL database in a Multi-AZ configuration in the primary region, and configure a cross-region read replica in the secondary region.

Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure S3 CRR with S3 RTC enabled to the secondary region. Implement a Pilot Light disaster recovery strategy in the secondary region by using AWS Backup to copy database backups across regions, restoring the RDS PostgreSQL database from these backups only after a regional disaster is declared.

Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure S3 CRR with S3 RTC enabled to the secondary region. Deploy the RDS PostgreSQL database in a Single-AZ configuration in the primary region, and set up a cross-region read replica in the secondary region with Route 53 configured to automatically route write traffic directly to the replica if the primary instance fails.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to a destination bucket in the secondary region. Deploy the RDS PostgreSQL database in a Multi-AZ configuration in the primary region, and configure a cross-region read replica in the secondary region.

Cevap

Deploy an Amazon S3 File Gateway at the local clinics, store raw images in Amazon S3 in the primary region with S3 Cross-Region Replication (CRR) and S3 Replication Time Control (S3 RTC) enabled to the secondary region, and deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration in the primary region with a cross-region read replica in the secondary region.

The correct architecture uses Amazon S3 File Gateway to cache images locally for radiologists, satisfying the low-latency local access requirement. Amazon S3 Standard provides

99.99\%

availability and

99.999999999\%

durability. To meet the

15

-minute RPO and RTO for the objects, S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) is used, which guarantees that

99.9\%

of objects replicate within

15

minutes. For the database, RDS Multi-AZ provides high availability within the primary region, and a cross-region read replica provides continuous replication to the secondary region, allowing manual promotion within the

15

-minute RTO during a disaster.

Adım Adım Çözüm

Address the local access requirement by placing an Amazon S3 File Gateway on-premises at the local clinics to cache recently accessed DICOM images.

Radiologists receive low-latency local access to the most recently generated images.

S3 File Gateway provides a local cache for file-based access to objects stored directly in Amazon S3.

Address S3 data replication durability and RPO requirements by enabling S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC).

S3 objects are replicated to the secondary region with a SLA-backed

15

-minute replication time, meeting the

15

-minute RPO.

S3 RTC ensures

99.9\%

of objects are replicated within

15

minutes and provides CloudWatch metrics to monitor replication lag.

Address database high availability and disaster recovery requirements by configuring Amazon RDS for PostgreSQL in a Multi-AZ deployment in the primary region and setting up a cross-region read replica in the secondary region.

Synchronous replication across AZs provides local high availability, and asynchronous replication to the secondary region read replica satisfies the cross-region DR RPO.

Multi-AZ configuration handles local zone failures automatically, while the cross-region read replica allows quick manual promotion within the

15

-minute RTO during a regional disaster.

Anahtar Kavram

Designing highly resilient hybrid storage and database architectures using S3 Replication Time Control (RTC) and RDS cross-region replication to satisfy strict RTO and RPO objectives.

Tahmini Süre:2m 30s

Soru 116Soru →

A global financial technology enterprise is migrating its transaction auditing system to AWS. The system must run across two AWS Regions: us-east-1 as the primary region and us-west-2 as the disaster recovery region. The database layer must support high-performance local read operations in both regions while routing all write operations to us-east-1. The disaster recovery requirements dictate a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 1 minute. Which database configuration best meets these requirements with the least operational complexity?

Configure an Amazon RDS for PostgreSQL DB instance in us-east-1 with a cross-region read replica in us-west-2, and configure Amazon Route 53 to automatically promote the replica to primary if the primary region fails.

Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Aurora physical replication to maintain synchronization.

Provision an Amazon RDS for PostgreSQL Multi-AZ DB instance in us-east-1 and a stopped pilot light DB instance in us-west-2, automating the startup and transaction log restoration from Amazon S3 upon failover.

Set up Amazon RDS for PostgreSQL Multi-AZ deployments in both us-east-1 and us-west-2, and use Amazon Route 53 latency-based routing with active health checks to synchronize write transactions across both regions.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Aurora physical replication to maintain synchronization.

Cevap

Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Aurora physical replication to maintain synchronization.

Deploying an Amazon Aurora PostgreSQL Global Database is the most resilient design for these requirements. It replicates data across regions at the storage tier using physical replication, keeping replica lag under 1 second to meet the RPO requirement. In a failover scenario, the secondary cluster can be promoted to primary in under 1 minute to meet the RTO requirement, while natively supporting high-performance local reads in both regions.

Adım Adım Çözüm

Analyze RPO, RTO, and multi-region read/write requirements.

Identify that the system needs storage-level cross-region replication with lag under 1 second and regional recovery orchestration under 1 minute.

Narrow down database architectures to those capable of meeting the strict high-availability and disaster recovery thresholds.

Evaluate the replication mechanics of Amazon Aurora Global Databases.

Confirm that Aurora physical replication operates at the storage layer with typical lag of less than 1 second (satisfying the RPO) and can be promoted to primary in under 1 minute (satisfying the RTO).

Ensure the selected configuration natively aligns with the target metrics.

Assess and eliminate alternative configurations that introduce lag, manual steps, or incorrect routing.

Identify that RDS read replica promotion is manual, pilot light startup is too slow, and Route 53 cannot replicate transactional writes.

Eliminate distractors that fail to meet either the performance or recovery requirements.

Anahtar Kavram

Using Amazon Aurora Global Databases to achieve multi-region read scaling, sub-second RPO storage-level replication, and sub-minute RTO failover capabilities.

Tahmini Süre:2m 30s

Soru 117Soru →

A financial services firm hosts a global portfolio analytics application on AWS. The application consists of a dynamic transaction API hosted on Application Load Balancers (ALBs) in two AWS Regions: eu-west-1 (primary) and ap-southeast-1 (standby). Additionally, the application generates static PDF reports that are stored in Amazon S3 buckets in both regions. The firm requires a resilient routing and edge caching strategy that minimizes latency for global users, guarantees automatic failover to the standby region for both dynamic APIs and static reports, and keeps operational overhead to a minimum.

Which TWO actions should a solutions architect take to meet these requirements?

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

Configure a CloudFront Origin Group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin. Create a cache behavior for /reports/* that routes requests to this Origin Group.

Configure a CloudFront Origin Group with the primary ALB as the primary origin and the secondary ALB as the failover origin. Create a default cache behavior (*) routing to this Origin Group, and attach the Managed-CachingDisabled cache policy.

Configure Route 53 Latency Routing to route dynamic traffic directly to the two regional ALBs, bypassing CloudFront to ensure the lowest latency and automatic DNS failover for APIs without edge network routing.

Attach an AWS WAF Web ACL to the CloudFront distribution and configure a custom rule that intercepts 502 Bad Gateway responses from the primary ALB to redirect the request to the secondary ALB.

Create a single CloudFront cache behavior for all paths (*) pointing to a combined ALB and S3 origin, and set the default, minimum, and maximum Time to Live (TTL) values to zero to guarantee dynamic requests are not cached.

Cevabı ve açıklamayı göster

Cevap: Configure a CloudFront Origin Group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin. Create a cache behavior for /reports/* that routes requests to this Origin Group.; Configure a CloudFront Origin Group with the primary ALB as the primary origin and the secondary ALB as the failover origin. Create a default cache behavior (*) routing to this Origin Group, and attach the Managed-CachingDisabled cache policy.

Cevap

To meet the requirements, the solutions architect should configure a CloudFront Origin Group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin with a cache behavior for static reports, and configure a separate CloudFront Origin Group for the ALB origins with a default cache behavior using a disabled caching policy.

The correct implementation requires establishing separate CloudFront Origin Groups for S3 and ALB endpoints. For the static reports path, a dedicated cache behavior directs traffic to the S3 Origin Group, ensuring low-latency delivery of cached reports and automatic standby-bucket failover. For the dynamic transaction path, a default cache behavior points to the ALB Origin Group with the Managed-CachingDisabled policy. This ensures transaction requests bypass the edge cache but benefit from edge routing failover and optimized network pathing.

Adım Adım Çözüm

Separate the static assets (/reports/*) from the dynamic transactions (*) in the CloudFront cache behavior settings.

Two distinct paths are configured to handle caching properties independently.

Static content should be cached at edge locations to minimize latency, while dynamic content must bypass the cache to ensure real-time query results.

Group the primary and standby S3 buckets into a CloudFront Origin Group.

High availability is configured for the static assets layer at the edge.

If the primary S3 bucket fails, CloudFront automatically routes requests to the failover bucket in the standby region.

Group the primary and standby ALBs into a second CloudFront Origin Group.

Edge-level failover is configured for the dynamic application layer.

This guarantees dynamic API requests failover automatically with minimal delay, leveraging the AWS global network for optimized latency.

Apply a CachingDisabled policy to the default cache behavior routing to the ALB Origin Group.

Dynamic content bypasses edge caching while maintaining routing resilience.

This prevents transactional payloads from being cached while still using CloudFront's persistent connections and Origin Group failover capabilities.

Anahtar Kavram

CloudFront Origin Groups and Path-Based Caching Profiles

Tahmini Süre:2m 0s

Soru 118Soru →

A financial services company is launching a global trading dashboard. The application consists of dynamic JSON APIs hosted on Amazon ECS containers behind an Application Load Balancer (ALB) in the us-east-1 Region, and static web assets stored in an Amazon S3 bucket in the same Region. For disaster recovery and high availability, the company has deployed a replica of the ECS application and a replicated S3 bucket in the us-west-2 Region. The company wants to minimize latency for global users and ensure that both static and dynamic requests automatically fail over to the secondary Region with minimal downtime if the primary Region becomes unavailable.

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

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

Configure an Amazon CloudFront distribution with two origin groups: one containing the primary and secondary S3 buckets, and another containing the primary and secondary ALBs, with failover criteria set for 5xx status codes.

Create two cache behaviors in the CloudFront distribution: one for static paths routing to the S3 origin group with caching enabled, and another for dynamic API paths routing to the ALB origin group with caching disabled (TTL set to 0).

Configure Amazon Route 53 latency-based routing policies pointing directly to the ALBs in both regions, and enable Route 53 health checks to route dynamic API requests during a regional outage.

Deploy AWS Global Accelerator to route dynamic API traffic to the ALB endpoints, and configure Route 53 with failover routing to switch CloudFront static traffic to the backup S3 bucket.

Create a single CloudFront origin group that combines both the primary ALB and the primary S3 bucket, and configure an AWS WAF rule to redirect traffic to the secondary Region.

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon CloudFront distribution with two origin groups: one containing the primary and secondary S3 buckets, and another containing the primary and secondary ALBs, with failover criteria set for 5xx status codes.; Create two cache behaviors in the CloudFront distribution: one for static paths routing to the S3 origin group with caching enabled, and another for dynamic API paths routing to the ALB origin group with caching disabled (TTL set to 0).

Cevap

The correct configurations are to set up an Amazon CloudFront distribution with two distinct origin groups (one for S3 buckets and one for Application Load Balancers) and configure two cache behaviors to route static traffic with caching enabled and dynamic API traffic with caching disabled (TTL set to 0) to their respective origin groups.

To achieve both sub-second global latency and high availability with fast failover, the solutions architect should use Amazon CloudFront with origin groups. By configuring separate origin groups for S3 and ALB origins, CloudFront can monitor the primary origin and instantly switch to the secondary origin if a 5xx error status code is returned. Creating separate cache behaviors ensures that static content is cached for performance, while dynamic API calls bypass caching (using a TTL of 0) but still benefit from edge optimizations and origin-level failover.

Adım Adım Çözüm

Analyze the requirements for latency minimization and regional failover for both static and dynamic contents.

Identify that CloudFront is required to minimize latency globally and that both static (S3) and dynamic (ALB) resources exist in two regions (primary us-east-1 and secondary us-west-2).

This establishes the scope of the solution which must handle two distinct traffic types and regional disaster recovery.

Select the appropriate failover mechanism at the edge layer.

Create two CloudFront origin groups (one for the S3 buckets and one for the ALBs) with us-east-1 as the primary origin and us-west-2 as the failover origin based on 5xx status codes.

CloudFront origin groups provide rapid, CDN-level failover without relying on DNS TTL propagation, meeting the minimal downtime requirement.

Configure caching behaviors for the static and dynamic paths.

Create a static cache behavior pointing to the S3 origin group with caching enabled, and a dynamic cache behavior pointing to the ALB origin group with TTL set to 0 to bypass caching.

This optimizes delivery by caching static assets at edge locations while ensuring dynamic API requests are always forwarded to the backend containers.

Anahtar Kavram

Amazon CloudFront Origin Groups and Cache Behaviors

Soru 119Soru →

A media streaming company is launching an on-demand video platform on AWS. The application database workload is highly unpredictable, experiencing sudden surges of read and write queries during popular content releases, followed by extended periods of low activity. The company requires a database design that supports high availability within a single AWS Region with a Recovery Time Objective (RTO) of less than 30 seconds and a Recovery Point Objective (RPO) of 0 (no data loss) during an Availability Zone outage. Additionally, the database must dynamically scale compute capacity up and down to match workload demands without manual intervention or connection disruption, while allowing read workloads to scale independently. Which database configuration will meet these requirements?

Deploy an Amazon Aurora PostgreSQL Serverless v2 DB cluster with a writer instance and a reader instance in different Availability Zones, and configure the application to use the cluster endpoint for writes and the reader endpoint for reads.

Deploy an Amazon RDS for PostgreSQL DB instance in a single Availability Zone, and configure a Read Replica in a different Availability Zone. Configure the application to direct writes to the primary instance, and design a custom failover script to promote the Read Replica during an outage.

Deploy a single-AZ Amazon Aurora DB cluster, and set up a separate standby Aurora DB cluster in another Availability Zone. Configure Amazon Route 53 latency routing to automatically failover and route database writes between the two clusters during an outage.

Deploy an Amazon RDS for PostgreSQL DB instance in a Multi-AZ deployment. Set up a second RDS DB instance as a scaled-down warm standby in a different AWS Region, and configure the application to failover to the regional standby within 30 seconds.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL Serverless v2 DB cluster with a writer instance and a reader instance in different Availability Zones, and configure the application to use the cluster endpoint for writes and the reader endpoint for reads.

Cevap

The correct configuration utilizes Amazon Aurora Serverless v2 in a Multi-AZ deployment with both a writer and a reader instance. Aurora Serverless v2 automatically scales compute capacity up and down based on application demand without causing connection disruption. By having a reader instance in a separate Availability Zone, Aurora can automatically fail over to the reader in less than 30 seconds (meeting the RTO constraint). Because both instances share the same distributed Aurora storage volume across multiple Availability Zones, no data loss occurs during a failover (meeting the RPO of 0). The reader endpoint allows the application to route read queries to the reader instance, scaling read capacity independently.

Adım Adım Çözüm

Identify the RTO, RPO, and compute scaling constraints from the scenario.

The solution requires high availability with RTO < 30 seconds, RPO = 0 (no data loss) in a single Region, dynamic compute scaling without connection drops, and read scaling.

Understanding these metrics eliminates disaster recovery options (which have RPO > 0 due to asynchronous cross-region replication) and standard RDS scaling options (which require downtime to change instance classes).

Evaluate the replication and failover mechanisms of the database engines.

Amazon Aurora replicates data across three Availability Zones using a shared storage volume, ensuring RPO = 0. Failover to an Aurora replica takes less than 30 seconds.

This guarantees the required HA and recovery objectives are met automatically during an Availability Zone outage.

Determine the scaling mechanism that prevents connection disruptions.

Amazon Aurora Serverless v2 scales compute capacity dynamically in place, preventing connection drops during workload spikes.

This satisfies the requirement for seamless scaling under unpredictable workloads.

Anahtar Kavram

Amazon Aurora Serverless v2 Multi-AZ deployments with reader instances provide high availability (RTO < 30 seconds), zero data loss (RPO = 0), and instant compute scaling without connection disruption.

Tahmini Süre:2m 0s

Soru 120Soru →

A media distribution company serves static high-resolution graphics and dynamic personalized recommendations from a web application. The static assets are stored in an Amazon S3 bucket in the us-east-1 Region, with a cross-region replication bucket in the us-west-2 Region. The dynamic recommendations are generated by an Application Load Balancer (ALB) in us-east-1. The company wants to implement a solution that reduces latency for global users and provides automatic failover for the static assets if the primary S3 bucket becomes unavailable. Which two actions should a solutions architect take to meet these requirements?

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

Create an Amazon CloudFront distribution. Configure an origin group with the S3 bucket in us-east-1 as the primary origin and the S3 bucket in us-west-2 as the secondary origin. Point the static cache behavior to this origin group.

Configure the CloudFront distribution to use the ALB in us-east-1 as the origin for dynamic requests, and configure the dynamic cache behavior to forward cookies, headers, and query strings to the origin.

Configure a Route 53 latency routing policy with health checks to route static asset requests directly to either S3 bucket.

Configure the CloudFront cache behavior for static assets with a default Time to Live (TTL) of 0 seconds.

Configure AWS WAF on the Application Load Balancer to inspect requests and dynamically redirect users to the backup S3 bucket when the primary bucket is offline.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon CloudFront distribution. Configure an origin group with the S3 bucket in us-east-1 as the primary origin and the S3 bucket in us-west-2 as the secondary origin. Point the static cache behavior to this origin group.; Configure the CloudFront distribution to use the ALB in us-east-1 as the origin for dynamic requests, and configure the dynamic cache behavior to forward cookies, headers, and query strings to the origin.

Cevap

To meet the requirements, the solutions architect should create an Amazon CloudFront distribution, configure an origin group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the backup origin, and route the static cache behavior to this group. Additionally, the ALB should be configured as a CloudFront origin for dynamic requests, with the dynamic cache behavior forwarding headers, cookies, and query strings to the origin.

The correct actions involve configuring CloudFront with an origin group for the static assets, and setting up the ALB as an origin with a dynamic cache behavior that forwards necessary user context. CloudFront origin groups provide automatic failover for static content by switching to the backup S3 bucket in us-west-2 if the primary bucket in us-east-1 is down or returns errors. Forwarding cookies, headers, and query strings to the ALB ensures dynamic recommendations are processed correctly while using CloudFront's optimized network path to reduce latency.

Adım Adım Çözüm

Analyze the requirements for latency reduction and resiliency.

Identify that CloudFront is the appropriate service for global edge caching of static content and optimized routing of dynamic content.

CloudFront reduces latency by caching static assets at edge locations and routing dynamic traffic over the AWS global network.

Configure automatic failover for the static S3 origins.

Create a CloudFront origin group containing the us-east-1 S3 bucket as primary and the us-west-2 S3 bucket as secondary.

CloudFront origin groups automatically route requests to the secondary origin if the primary origin is unavailable or returns error status codes.

Configure dynamic request handling.

Add the ALB as an origin and configure a separate cache behavior for dynamic paths to bypass caching by forwarding query strings, cookies, and headers.

This allows personalized recommendation requests to reach the ALB directly while benefiting from CloudFront's optimized network routing.

Anahtar Kavram

Leveraging Amazon CloudFront origin groups for static asset failover and optimizing dynamic API performance by routing Application Load Balancer traffic through the edge network.

Tahmini Süre:2m 0s

ÖncekiSayfa 6 / 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

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