All practice questions

1964 questions

All types1,964 Multiple choice1,006 Multiple select931 Ordering27

A retail company, OmniStore, is setting up a centralized auditing pipeline. AWS CloudTrail logs from the main production account (Account A) must be delivered to a centralized Amazon S3 bucket located in the security operations account (Account B). The S3 bucket is encrypted using an AWS KMS Customer Managed Key (CMK) managed in Account B. The security architect must configure the access policies to allow CloudTrail to write the log files to Account B while enforcing least-privilege access. Which configuration strategy will allow CloudTrail to successfully deliver the logs to the encrypted S3 bucket in Account B?

Configure the S3 bucket policy in Account B to allow the CloudTrail service principal (cloudtrail.amazonaws.com) to perform the s3:PutObject and s3:GetBucketAcl actions. Configure the key policy of the CMK in Account B to allow the CloudTrail service principal to perform the kms:GenerateDataKey action, using policy conditions to restrict access to the ARN of the CloudTrail in Account A.

Configure the S3 bucket in Account B to use the default AWS-managed KMS key (aws/s3) for encryption. Configure the S3 bucket policy in Account B to allow the CloudTrail service principal (cloudtrail.amazonaws.com) to perform the s3:PutObject action.

Attach a Service Control Policy (SCP) to the organizational unit containing Account A that allows the kms:GenerateDataKey and s3:PutObject actions for the CloudTrail service principal. Omit updates to the KMS key policy and S3 bucket policy in Account B.

Configure the S3 bucket policy in Account B to allow the AWS account ID of Account A as the Principal for the s3:PutObject action, omitting the CloudTrail service principal (cloudtrail.amazonaws.com), and rely on Account A's local IAM policies to delegate write permissions to CloudTrail.

Show answer & explanation

Answer: Configure the S3 bucket policy in Account B to allow the CloudTrail service principal (cloudtrail.amazonaws.com) to perform the s3:PutObject and s3:GetBucketAcl actions. Configure the key policy of the CMK in Account B to allow the CloudTrail service principal to perform the kms:GenerateDataKey action, using policy conditions to restrict access to the ARN of the CloudTrail in Account A.

Answer

The correct configuration requires granting permissions directly to the CloudTrail service principal (cloudtrail.amazonaws.com) in both the S3 bucket policy and the KMS key policy in Account B. Because this is a cross-account scenario, the S3 bucket policy must allow the service principal to write objects (s3:PutObject) and read bucket ACLs (s3:GetBucketAcl), and the Customer Managed Key (CMK) policy must grant the service principal permission to generate data keys (kms:GenerateDataKey) to encrypt the logs. Adding conditions ensures only logs from the specific production CloudTrail are accepted.

Step-by-Step Solution

Analyze the IAM identities involved in writing CloudTrail logs.

Identify that the CloudTrail service writes logs using the service principal 'cloudtrail.amazonaws.com', not local IAM roles in the source account.

Permissions must be granted directly to the CloudTrail service principal rather than the source account ID.

Determine the S3 bucket policy requirements for cross-account log delivery.

Identify that the target S3 bucket policy in Account B must allow 's3:PutObject' and 's3:GetBucketAcl' for the service principal 'cloudtrail.amazonaws.com'.

Cross-account S3 writes require explicit resource-based policy allowance for the writing identity.

Evaluate the KMS encryption configuration for cross-account S3 delivery.

Confirm that an AWS Customer Managed Key (CMK) must be used, and its key policy must grant 'kms:GenerateDataKey' to the service principal 'cloudtrail.amazonaws.com'.

AWS-managed keys (aws/s3) do not support policy modification and cannot be shared across accounts.

Key Concept

Cross-account AWS CloudTrail log delivery using KMS Customer Managed Keys (CMKs)

Question 182Question →

An advertising technology company is deploying a real-time bidding analytics platform. The platform must process device telemetry and bid requests. The system handles a baseline load of $5,000$ requests per second, but during live sporting events, traffic instantly spikes to $150,000$ requests per second. The application is hosted on Amazon EC2 instances behind an Application Load Balancer (ALB). The backend is an Amazon RDS PostgreSQL database. During recent spikes, the platform experienced dropped requests at the load balancer level, and read query latency on the database spiked, causing performance degradation.

Which of the following combinations of actions should a Solutions Architect recommend to optimize the performance and scalability of the platform? (Select TWO.)

Select all that apply

Deploy a Network Load Balancer (NLB) in front of the EC2 instances to handle the sudden, massive spikes in traffic without the need for load balancer pre-warming.

Migrate the database to Amazon Aurora PostgreSQL, and configure Aurora Auto Scaling to dynamically scale Aurora Replicas based on reader CPU utilization.

Configure the existing RDS PostgreSQL Multi-AZ standby instance to serve read queries during peak traffic hours to reduce the load on the primary DB instance.

Rely on the Application Load Balancer's default auto-scaling capabilities to automatically scale out to handle the instant

30

-fold traffic spike.

Deploy an Amazon ElastiCache for Memcached cluster to cache common read queries, and configure multi-region replication to scale caching layer throughput.

Show answer & explanation

Answer: Deploy a Network Load Balancer (NLB) in front of the EC2 instances to handle the sudden, massive spikes in traffic without the need for load balancer pre-warming.; Migrate the database to Amazon Aurora PostgreSQL, and configure Aurora Auto Scaling to dynamically scale Aurora Replicas based on reader CPU utilization.

Answer

The correct actions are deploying a Network Load Balancer (NLB) to handle the instant, massive traffic spikes without requiring pre-warming, and migrating the database to Amazon Aurora PostgreSQL to utilize Aurora Auto Scaling for reader replicas.

To handle sudden, massive spikes in traffic that scale instantly, a Network Load Balancer (NLB) is highly suitable as it can handle millions of requests per second without requiring pre-warming. Additionally, migrating the backend database to Amazon Aurora PostgreSQL allows the use of Aurora Replicas and Aurora Auto Scaling, which can dynamically scale reader nodes to handle read query spikes, offloading traffic from the primary writer node.

Step-by-Step Solution

Analyze the load balancer scaling characteristics.

Determine that the Application Load Balancer cannot scale fast enough to absorb the instant

30

-fold increase from

5,000

150,000

requests per second, requiring a Network Load Balancer to handle the spike without pre-warming.

To prevent request drops during sudden spikes, the load balancing tier must be capable of handling rapid throughput changes instantly.

Evaluate database scaling patterns.

Identify that the primary PostgreSQL instance is saturated by read query spikes, and that standard RDS Multi-AZ standbys cannot serve read traffic.

To scale read operations, the architecture must implement a technology that supports dynamic horizontal scaling of read endpoints.

Select the optimal database and caching architecture.

Choose to migrate to Amazon Aurora PostgreSQL and configure Aurora Auto Scaling for reader replicas.

Aurora Auto Scaling dynamically adjusts reader replicas based on CPU demand, resolving the database read query latency issue.

Key Concept

Handling sudden, extreme traffic spikes at the load balancer and database layers using Network Load Balancers and Aurora Auto Scaling.

Estimated Time:2m 0s

Question 183Question →

A logistics company is designing a high-availability tracking and route optimization backend for a global maritime cargo fleet. The application runs on Amazon EC2 instances in private subnets across three Availability Zones in the `us-east-1` Region, with a replication target in `us-west-2` for disaster recovery. The database layer uses Amazon Aurora MySQL. The company has the following requirements:
- Maximum tolerable downtime (RTO) is 15 minutes.
- Maximum tolerable data loss (RPO) is 2 minutes.
- Outbound API calls from the EC2 instances to external weather services must remain highly available even if an Availability Zone fails, without routing traffic across Availability Zones.
- Global client requests must be routed to the closest Region to minimize latency, with automatic redirect to the surviving Region if a regional outage occurs.

Which of the following architectures meets these requirements while minimizing operational complexity and cost?

Deploy a Multi-AZ Amazon RDS MySQL DB instance in `us-east-1`, directing read-heavy application traffic to the standby replica to scale query performance. Deploy a cross-region read replica in `us-west-2` for disaster recovery. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the cross-region read replica to primary.

Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both Regions, deploy a single NAT Gateway in one Availability Zone to handle all outbound traffic from the private subnets across all zones. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the Aurora secondary database cluster to primary.

Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside, and update private subnet route tables to direct outbound traffic to the local NAT Gateway. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the Aurora secondary database cluster to primary.

Deploy an Amazon Aurora cluster in `us-east-1` and configure an AWS Backup plan to perform daily snapshots, copying them to `us-west-2`. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside, and update private subnet route tables. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, restore the database from the copied snapshot in `us-west-2`.

Show answer & explanation

Answer: Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside, and update private subnet route tables to direct outbound traffic to the local NAT Gateway. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the Aurora secondary database cluster to primary.

Answer

Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the Aurora secondary database cluster.

The correct architecture leverages Amazon Aurora Global Database to achieve cross-region replication lag of under 1 second, fulfilling the 2-minute RPO. Promoting the secondary cluster takes only a few minutes, meeting the 15-minute RTO. A NAT Gateway deployed in each Availability Zone ensures that a single zone failure does not disrupt outbound traffic from the remaining zones, avoiding cross-AZ charges. Finally, Route 53 Latency-based routing with health checks routes users to the lowest-latency Region and automatically reroutes them during a failure.

Step-by-Step Solution

Select the database replication strategy.

Amazon Aurora Global Database provides replication lag under 1 second and a promotion time under 15 minutes, fulfilling both the RPO of 2 minutes and RTO of 15 minutes.

Traditional backup restore methods take too long and result in high data loss, while cross-region RDS replica promotion is more complex and slow.

Configure highly available outbound NAT routing.

A NAT Gateway is deployed in each Availability Zone where the private subnets are located.

This setup prevents outbound traffic disruption if a single Availability Zone experiences an outage, and it prevents cross-AZ network traffic charges.

Set up Route 53 routing policies for latency and regional failover.

Latency-based routing records are configured pointing to each region's load balancer, with Route 53 health checks associated with each record.

This routes global client traffic to the nearest healthy Region to minimize latency, and automatically shifts traffic to the surviving Region if health checks fail.

Key Concept

Multi-region disaster recovery and high availability design combining low-latency global routing, cross-region database replication, and localized NAT gateway redundancy.

Question 184Question →

A digital advertising company is designing a real-time bidding platform. The application tier runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB) across multiple Availability Zones in a primary AWS Region. The database tier uses an Amazon Aurora PostgreSQL DB cluster. The company requires a multi-region disaster recovery (DR) strategy in a secondary AWS Region. The design must support a Recovery Time Objective (RTO) of less than $10$ minutes and a Recovery Point Objective (RPO) of less than $1$ minute while minimizing cost. Which architecture meets these requirements?

Deploy an Amazon Aurora Global Database with the primary cluster in the primary region and a secondary cluster in the secondary region. Deploy a minimum-capacity Auto Scaling group and an ALB in the secondary region. Configure Amazon Route 53 failover routing records pointing to the ALBs in both regions, and associate the primary record with a Route 53 health check that monitors the primary application endpoint.

Deploy an Amazon Aurora Global Database with the primary cluster in the primary region and a secondary cluster in the secondary region. Deploy a minimum-capacity Auto Scaling group and an ALB in the secondary region. Configure Amazon Route 53 failover routing records pointing to the ALBs in both regions, but do not associate the primary record with an application health check to avoid false failovers.

Configure daily Amazon Aurora database backups and copy the snapshots to the secondary region. Use an AWS CloudFormation template to deploy the ALB, Auto Scaling group, and Aurora PostgreSQL database in the secondary region only when a disaster is declared, and update Route 53 records manually.

Deploy an Amazon Aurora PostgreSQL DB cluster in Multi-AZ mode in the primary region. Create an Aurora Read Replica in the secondary region, and configure Aurora Auto Scaling on the secondary replica to automatically accept write traffic if the primary region fails. Configure Route 53 latency-based routing to distribute traffic between the regions.

Show answer & explanation

Answer: Deploy an Amazon Aurora Global Database with the primary cluster in the primary region and a secondary cluster in the secondary region. Deploy a minimum-capacity Auto Scaling group and an ALB in the secondary region. Configure Amazon Route 53 failover routing records pointing to the ALBs in both regions, and associate the primary record with a Route 53 health check that monitors the primary application endpoint.

Answer

Deploying an Amazon Aurora Global Database with a warm standby application tier in the secondary region, combined with Amazon Route 53 failover routing and health checks, meets both the RTO and RPO requirements at a lower cost than an active-active multi-region setup.

The correct answer proposes an Amazon Aurora Global Database for sub-second database replication, satisfying the RPO of less than

1

minute. By maintaining a minimum-capacity Auto Scaling group in the secondary region (Warm Standby), costs are minimized compared to active-active, while still allowing the application to scale up within the

10

-minute RTO. Route 53 failover routing with an associated health check ensures that traffic is automatically redirected to the secondary region if the primary region's application becomes degraded.

Step-by-Step Solution

Select a database replication technology that meets the RPO constraint.

Amazon Aurora Global Database provides sub-second replication latency to a secondary region, which satisfies the RPO of less than

1

minute.

Standard database snapshots or cross-region read replicas without proper failover mechanisms will not satisfy the strict recovery objectives.

Select a disaster recovery pattern for the application tier that meets the RTO constraint.

A warm standby pattern with a minimum-capacity Auto Scaling group in the secondary region allows for rapid scaling to handle production traffic within

10

minutes.

Rebuilding the infrastructure using CloudFormation from scratch takes too long and exceeds the

10

-minute RTO.

Configure DNS routing and health checks for automated failover.

Create Route 53 failover routing records and associate the primary record with a health check monitoring the primary application's availability.

Without Route 53 health checks, the DNS failover cannot be automated, leaving the system vulnerable to prolonged downtime during an outage.

Key Concept

Disaster Recovery Patterns and DNS Failover Design

Question 185Question →

A logistics enterprise is building a new supply-chain tracking platform. The architecture stores sensitive transaction logs in an Amazon S3 bucket within a dedicated Storage Account. An analytics application running on Amazon ECS tasks in a separate Processing Account needs to read and write objects in this S3 bucket. All data stored in the S3 bucket must be encrypted at rest using an AWS KMS key. The design must adhere to the principle of least privilege while enabling secure cross-account access. Which design strategy meets these requirements?

Encrypt the S3 bucket with a Customer Managed Key (CMK) in the Storage Account. Configure the CMK key policy to allow the Processing Account's ECS task role kms:Decrypt and kms:GenerateDataKey permissions. Update the S3 bucket policy to allow the ECS task role s3:GetObject and s3:PutObject permissions. Attach an IAM policy to the ECS task role in the Processing Account that allows S3 and KMS actions on these resources.

Encrypt the S3 bucket using the default AWS managed key (aws/s3). Configure the S3 bucket policy to allow the Processing Account's ECS task role s3:GetObject and s3:PutObject permissions. Attach an IAM policy to the ECS task role in the Processing Account that allows S3 and KMS actions on these resources.

Encrypt the S3 bucket with a Customer Managed Key (CMK) in the Storage Account. Apply a Service Control Policy (SCP) at the Organizational Unit level that grants the Processing Account's ECS task role access to the S3 bucket and the CMK. Avoid modifying the CMK key policy or the S3 bucket policy in the Storage Account.

Encrypt the S3 bucket with a Customer Managed Key (CMK) in the Storage Account. Configure the CMK key policy to allow the Processing Account's ECS task role kms:Decrypt and kms:GenerateDataKey permissions. Attach an IAM policy to the ECS task role in the Processing Account that allows S3 and KMS actions on the storage resources, omitting the S3 bucket policy to rely on IAM authority.

Show answer & explanation

Answer: Encrypt the S3 bucket with a Customer Managed Key (CMK) in the Storage Account. Configure the CMK key policy to allow the Processing Account's ECS task role kms:Decrypt and kms:GenerateDataKey permissions. Update the S3 bucket policy to allow the ECS task role s3:GetObject and s3:PutObject permissions. Attach an IAM policy to the ECS task role in the Processing Account that allows S3 and KMS actions on these resources.

Answer

The correct strategy uses a Customer Managed Key (CMK) because its key policy can be configured to delegate permissions to an external account. The security design correctly requires permissions on the S3 bucket policy (granting write/read), the KMS key policy (granting decrypt/generate data key), and the client-side IAM policy (granting the ECS task role access to the resources).

Step-by-Step Solution

Determine the type of KMS key to use.

Identify that a Customer Managed Key (CMK) is required.

AWS-managed keys (aws/s3) have read-only key policies that cannot be modified to allow cross-account access.

Establish trust on the S3 bucket.

Add an S3 bucket policy in the Storage Account allowing the ECS task role read and write access.

For cross-account access, the S3 bucket owner must explicitly grant access to the external principal.

Establish trust on the KMS key.

Add a statement in the CMK key policy in the Storage Account allowing the ECS task role kms:Decrypt and kms:GenerateDataKey.

The key policy must explicitly authorize the external role to perform cryptographic operations with the CMK.

Configure the local IAM permissions.

Attach an IAM policy to the ECS task role in the Processing Account allowing S3 operations on the bucket and KMS operations on the CMK.

The accessing account must grant its own principal permission to access the external resources.

Key Concept

Cross-account access to encrypted S3 resources requires coordination of the S3 bucket policy, the KMS key policy (which must be a Customer Managed Key), and the IAM policy of the calling principal.

Estimated Time:2m 0s

Question 186Question →

A company hosts a critical customer-facing web application on AWS Elastic Beanstalk. The application must maintain its full serving capacity at all times during updates to prevent any performance degradation. Additionally, the company's release policy requires testing the new version with a small fraction of live production traffic for a specific evaluation period, with an automated rollback if the new version displays health issues. Which Elastic Beanstalk deployment policy should the solutions architect recommend to meet these requirements?

Traffic splitting deployment

Immutable deployment

Rolling with additional batch deployment

Rolling deployment

Show answer & explanation

Answer: Traffic splitting deployment

Answer

Traffic splitting deployment

Traffic splitting deployment is the only policy in Elastic Beanstalk that satisfies both constraints. It launches a new set of instances alongside the old ones to maintain capacity and routes a specified percentage of incoming traffic to the new version for a trial period, rolling back automatically if issues arise.

Step-by-Step Solution

Analyze the capacity requirement during updates.

The requirement states that the application must maintain full serving capacity at all times, which rules out standard rolling deployments that take instances offline.

Standard rolling deployments degrade capacity during the update window, violating performance requirements.

Analyze the canary testing requirement.

The application needs to test the new version using a small fraction of live production traffic for a specified evaluation period before complete rollout.

This requires a deployment strategy that supports canary testing with real traffic rather than immediately routing all traffic to the new version.

Evaluate Elastic Beanstalk deployment policies against the constraints.

Traffic splitting deployment creates a parallel set of instances (maintaining capacity) and routes a configurable percentage of traffic for evaluation, automatically rolling back if metrics degrade. This satisfies both full capacity and canary testing constraints.

Only traffic splitting offers both full capacity preservation and customizable, time-bound traffic canary routing in Elastic Beanstalk.

Key Concept

AWS Elastic Beanstalk deployment strategies, specifically utilizing traffic splitting for zero-downtime, capacity-preserving canary updates.

Estimated Time:2m 0s

Question 187Question →

An enterprise is designing a multi-region disaster recovery (DR) architecture for a web-based learning management system. The primary workload runs in the us-east-1 Region, and the DR workload runs in the us-west-2 Region. The architecture must achieve a Recovery Point Objective (RPO) of 1 minute and a Recovery Time Objective (RTO) of 15 minutes. The database tier uses an Amazon Aurora PostgreSQL DB cluster. Which combination of actions should a Solutions Architect take to meet these requirements? (Select TWO.)

Select all that apply

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

Create Amazon Route 53 failover routing records with active-passive configuration, and associate them with health checks on the Application Load Balancers.

Implement Route 53 latency-based routing records to automatically direct client requests to the secondary region if the primary region's latency increases during an outage.

Configure synchronous database replication between us-east-1 and us-west-2 by deploying a single Aurora DB cluster spanning both Regions.

Deploy a single NAT Gateway in each Region's primary Availability Zone to route outbound internet traffic from the private subnets.

Configure Route 53 Private Hosted Zones and associate them only with the us-east-1 VPC, relying on Route 53 Resolver outbound endpoints for cross-region resolution.

Show answer & explanation

Answer: Establish an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2.; Create Amazon Route 53 failover routing records with active-passive configuration, and associate them with health checks on the Application Load Balancers.

Answer

Establish an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, and create Amazon Route 53 failover routing records with active-passive configuration associated with health checks on the Application Load Balancers.

To meet the RPO of 1 minute and RTO of 15 minutes, the database replication must be continuously active and low-latency, which is achieved by establishing an Amazon Aurora Global Database. To redirect user traffic during a regional outage, Route 53 failover routing records must be created in an active-passive configuration, which uses health checks to detect failure of the primary Application Load Balancer and dynamically direct requests to the secondary region.

Step-by-Step Solution

Determine database replication requirements to meet the 1-minute RPO.

Identify that Amazon Aurora Global Database uses fast asynchronous replication across Regions, keeping the RPO well under 1 minute.

Standard cross-region replication is required as Aurora clusters cannot span multiple Regions, and manual processes would violate the strict RPO.

Identify the routing mechanism for active-passive multi-region failover.

Select Amazon Route 53 failover routing policy configured with health checks on the Application Load Balancers.

This configuration ensures that traffic is automatically redirected to the healthy secondary region if the primary region's load balancer becomes unhealthy.

Verify high availability constraints within each region.

Ensure redundant NAT Gateways are deployed in each Availability Zone and Private Hosted Zones are associated with all VPCs.

This guarantees that local infrastructure failures do not prevent the DR region from operating successfully during a failover event.

Key Concept

Multi-region disaster recovery using Amazon Aurora Global Database and Route 53 active-passive failover routing.

Estimated Time:2m 0s

Question 188Question →

A gaming company is launching a multiplayer online game with a backend DRM and matchmaking platform. The licensing and matchmaking tiers run on Amazon EC2 instances behind Application Load Balancers (ALBs) in private subnets across two AWS Regions: us-east-1 (Primary) and us-west-2 (Secondary). The application must connect to external licensing verification servers on the public internet. The company has defined a Recovery Time Objective (RTO) of 10 minutes and a Recovery Point Objective (RPO) of 1 minute. The architecture must eliminate single points of failure for outbound communication and DNS resolution for internal microservices. Which combination of actions should the solutions architect take to meet these requirements? (Select TWO.)

Select all that apply

Configure Amazon Route 53 with Failover routing policy for the game's public endpoint, associating the primary record with the us-east-1 ALB and the secondary record with the us-west-2 ALB, with both records linked to Route 53 health checks that evaluate application status.

Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, and provision NAT Gateways in every Availability Zone containing active EC2 instances in both Regions.

Establish a database Warm Standby strategy where backups of an Amazon RDS for PostgreSQL DB instance are copied to Amazon S3 in us-west-2 hourly, and write an AWS Lambda function to spin up a new database instance from the backup during failover.

Deploy a single NAT Gateway in a single public subnet in us-east-1 and another in us-west-2, and update the route tables of all private subnets in each Region to route internet-bound traffic through their respective regional NAT Gateway to optimize cost.

Configure a Route 53 Private Hosted Zone (PHZ) in the primary AWS account to resolve internal microservice DNS names, and peer the VPCs using AWS Transit Gateway to automatically enable cross-VPC DNS resolution without associating the PHZ to the secondary VPC.

Provision an Amazon Aurora Multi-AZ DB cluster in us-east-1, and set up Aurora replica auto-scaling to automatically scale out database write nodes in us-west-2 based on CPU utilization to handle write requests during a regional outage.

Show answer & explanation

Answer: Configure Amazon Route 53 with Failover routing policy for the game's public endpoint, associating the primary record with the us-east-1 ALB and the secondary record with the us-west-2 ALB, with both records linked to Route 53 health checks that evaluate application status.; Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, and provision NAT Gateways in every Availability Zone containing active EC2 instances in both Regions.

Answer

The correct architecture uses Route 53 Failover routing with application health checks to direct traffic between the primary region and the warm standby region, while using Aurora Global Database to achieve cross-region storage replication under 1 second. High availability for outbound traffic is secured by deploying NAT Gateways in each Availability Zone containing EC2 instances.

Deploying Amazon Aurora Global Database replicates storage updates asynchronously with sub-second latency, ensuring that the 1-minute RPO is met. Routing traffic using Route 53 Failover policies associated with health checks enables automatic failover to the standby region in under 10 minutes, satisfying the RTO. Provisioning NAT Gateways in every Availability Zone containing EC2 instances removes any single point of failure for outbound traffic.

Step-by-Step Solution

Select the database replication strategy.

Amazon Aurora Global Database provides storage-level replication across AWS regions with sub-second replication lag, meeting the 1-minute RPO.

Traditional RDS backups to S3 are too slow to restore and exceed the RTO/RPO limits.

Select the DNS routing and health checking setup.

Amazon Route 53 Failover routing checks the health of the primary ALB and automatically redirects users to the warm standby secondary ALB in the event of an outage.

Automatic failover without human intervention is required to recover within the 10-minute RTO.

Ensure high availability of NAT and egress routes.

NAT Gateways must be placed in each Availability Zone to avoid single point of failure (SPOF) risks.

A single NAT Gateway per Region fails HA criteria if the zone containing the gateway goes offline.

Key Concept

High Availability and Disaster Recovery Design

Question 189Question →

A company is designing a new multi-region web application that processes package tracking requests. The application tier runs on Amazon EC2 instances in an Auto Scaling group across two Availability Zones behind an Application Load Balancer (ALB) in the primary region (us-east-1). The application tier requires outbound internet connectivity to query external APIs for customs clearance updates. For disaster recovery, the database tier uses Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in the recovery region (us-west-2). The disaster recovery solution must achieve a Recovery Time Objective (RTO) of less than 10 minutes, a Recovery Point Objective (RPO) of less than 1 minute, and minimize resource costs during normal operations. Additionally, the outbound connectivity in the primary region must not have a single point of failure. Which architecture configuration should a solutions architect select to meet these requirements?

Deploy a single NAT Gateway in one Availability Zone in the primary region, pointing the route tables of all private subnets across both Availability Zones to this NAT Gateway. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing a single scaled-down db.t3.medium reader instance. Use Route 53 Failover routing policies with health checks linked to the regional ALBs.

Deploy a NAT Gateway in each Availability Zone in the primary region, updating the route tables for each private subnet to point to its local NAT Gateway. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing a single scaled-down db.t3.medium reader instance. Use Route 53 Failover routing policies with health checks linked to the regional ALBs.

Deploy a NAT Gateway in each Availability Zone in the primary region, updating the route tables for each private subnet to point to its local NAT Gateway. Configure Amazon Aurora daily snapshot copies from us-east-1 to us-west-2, and restore the database to a new cluster in us-west-2 only during a disaster event. Use Route 53 Failover routing policies with health checks linked to the regional ALBs.

Deploy a NAT Gateway in each Availability Zone in the primary region, updating the route tables for each private subnet to point to its local NAT Gateway. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing a single scaled-down db.t3.medium reader instance. Create a Route 53 Private Hosted Zone for the database endpoint in the primary account's VPC but do not associate it with the recovery VPC. Use Route 53 Geolocation routing to route public web traffic.

Show answer & explanation

Answer: Deploy a NAT Gateway in each Availability Zone in the primary region, updating the route tables for each private subnet to point to its local NAT Gateway. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing a single scaled-down db.t3.medium reader instance. Use Route 53 Failover routing policies with health checks linked to the regional ALBs.

Answer

The correct architecture requires a NAT Gateway in each Availability Zone of the primary region to prevent outbound internet connectivity from becoming a single point of failure. It also requires Amazon Aurora Global Database to achieve the sub-minute RPO and sub-10-minute RTO, along with Route 53 Failover routing policies with health checks to automatically direct public traffic to the recovery region's Application Load Balancer in the event of a primary region outage.

Step-by-Step Solution

Analyze the outbound connectivity requirements for high availability in the primary region.

Identify that outbound NAT Gateway redundancy is required. A NAT Gateway must be placed in each Availability Zone, and private subnet route tables must be updated to route traffic through their local NAT Gateway.

Prevents a failure in one Availability Zone from interrupting the outbound API connectivity of instances in the remaining healthy Availability Zone.

Evaluate the database replication strategy against RTO and RPO limits.

Select Amazon Aurora Global Database over snapshot copies, configuring a single scaled-down reader instance in the secondary region to minimize costs.

Aurora Global Database replication lag is under 1 second, meeting the sub-minute RPO constraint, and failover takes less than a few minutes, meeting the 10-minute RTO constraint.

Determine the proper Route 53 DNS routing policy for the multi-region configuration.

Select Route 53 Failover routing with health checks targeted at regional Application Load Balancers.

Failover routing is designed specifically for active-passive disaster recovery, ensuring that traffic automatically routes to the secondary region if the primary region's endpoints fail health checks.

Key Concept

High Availability and Disaster Recovery Design

Question 190Question →

An international airline is designing a high-availability and disaster recovery architecture for its global crew scheduling and flight dispatching system. The system runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The primary workload is hosted in `us-east-1`, and the disaster recovery region is `us-west-2`. The airline has defined a Recovery Time Objective (RTO) of $10$ minutes and a Recovery Point Objective (RPO) of $1$ minute. The flight dispatchers are distributed globally, and their client connections must be routed to the region offering the lowest network latency. Furthermore, the application requires outbound internet access to retrieve real-time weather feeds from external aviation authorities, which must remain functional even if a single Availability Zone within either region suffers an outage. Which solution should a solutions architect recommend to meet these requirements?

Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both regions, deploy the EC2 instances across multiple Availability Zones with Route 53 latency-based routing records and health checks pointing to the regional ALBs. Run the application tier in `us-west-2` at minimum capacity and use an Auto Scaling group to scale it up during a failover. Configure NAT Gateways in each Availability Zone in both VPCs for outbound internet access.

Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both regions, deploy the EC2 instances across multiple Availability Zones with Route 53 latency-based routing records and health checks pointing to the regional ALBs. Run the application tier in `us-west-2` at minimum capacity and use an Auto Scaling group to scale it up during a failover. To optimize resource costs, deploy a single NAT Gateway in the public subnet of the first Availability Zone in each VPC to handle outbound internet access.

Deploy an Amazon Aurora PostgreSQL DB cluster in `us-east-1` and configure AWS Backup to take automated snapshots every hour, copying them to `us-west-2`. In both regions, deploy the EC2 instances across multiple Availability Zones with Route 53 latency-based routing records and health checks pointing to the regional ALBs. Run the application tier in `us-west-2` at minimum capacity and use an Auto Scaling group to scale it up during a failover. Configure NAT Gateways in each Availability Zone in both VPCs for outbound internet access.

Deploy a Multi-AZ Amazon RDS PostgreSQL DB instance in `us-east-1`. To handle local read requests and reduce database load during failover, configure the application servers in `us-west-2` to read directly from the passive RDS standby instance in the secondary Availability Zone. Deploy the EC2 instances across multiple Availability Zones with Route 53 latency-based routing records and health checks pointing to the regional ALBs. Configure NAT Gateways in each Availability Zone in both VPCs for outbound internet access.

Show answer & explanation

Answer: Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both regions, deploy the EC2 instances across multiple Availability Zones with Route 53 latency-based routing records and health checks pointing to the regional ALBs. Run the application tier in `us-west-2` at minimum capacity and use an Auto Scaling group to scale it up during a failover. Configure NAT Gateways in each Availability Zone in both VPCs for outbound internet access.

Answer

Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Route client connections using Route 53 latency-based routing records with health checks pointing to regional ALBs. Run the application tier in us-west-2 at minimum capacity and use an Auto Scaling group to scale it up during failover. Deploy NAT Gateways in each Availability Zone in both VPCs for redundant outbound internet access.

The correct solution addresses all architecture requirements. First, Amazon Aurora Global Database replicates data across regions in under

1

second, which easily satisfies the

1

-minute RPO. Second, Route 53 latency-based routing records with associated health checks ensure that clients are routed to the lowest-latency healthy endpoint, automatically failing over to the secondary region if the primary region goes down. Third, the application tier in the secondary region runs at a lower capacity to minimize idle costs and scales up using Auto Scaling during a failover to meet the

10

-minute RTO. Finally, deploying NAT Gateways in each Availability Zone of the subnets ensures that outbound connectivity remains operational even during an Availability Zone outage.

Step-by-Step Solution

Select a cross-region database replication mechanism that meets the RPO.

Amazon Aurora Global Database is chosen because it offers physical replication lag of less than

1

second across regions, satisfying the

1

-minute RPO constraint.

Standard backup/restore or read replica copying mechanisms cannot guarantee an RPO under

1

minute, and RDS Multi-AZ standby instances do not span regions.

Design the DNS routing policy to handle low-latency and automatic failover.

Amazon Route 53 latency-based routing is configured with health checks associated with the primary and secondary region Application Load Balancers.

This configuration routes users to the closest region under normal operations and automatically redirects traffic to the surviving region if a failure occurs, satisfying both low latency and the

10

-minute RTO.

Ensure outbound connectivity is highly available and resilient to AZ outages.

NAT Gateways are deployed in each Availability Zone in both regions where the application instances reside.

If a single NAT Gateway were shared across multiple Availability Zones in a VPC, the outage of the zone hosting that NAT Gateway would disrupt outbound connectivity for the entire region. Multi-AZ NAT Gateway deployment removes this single point of failure.

Key Concept

Multi-region disaster recovery design balancing RTO/RPO using Aurora Global Database, Route 53 latency routing with health checks, and AZ-redundant NAT Gateways.

Question 191Question →

A municipal agency is designing a cloud-native smart-grid telemetry ingestion system to monitor real-time energy distribution. The core application runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The application database is hosted on Amazon Aurora PostgreSQL. The architecture must be highly resilient across two AWS Regions to handle regional outages. The business requirements specify an active-passive disaster recovery strategy with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. Outbound internet traffic for the private EC2 instances must remain highly available during a local Availability Zone outage. Which two architectural configurations should the solutions architect implement to satisfy these requirements?

Select all that apply

Configure Amazon Route 53 with a failover routing policy, designating the primary region's Application Load Balancer as active and the secondary region's Application Load Balancer as passive, and associate active Route 53 health checks with both endpoints.

Create an Amazon Aurora Global Database with the primary database cluster in the active region and a secondary cluster in the passive region, and deploy a NAT Gateway in each Availability Zone utilized by the private EC2 instances in both regions.

Provision a single NAT Gateway in one public subnet for each region's VPC, configure the route tables in all private subnets to point outbound traffic to this single gateway, and configure Route 53 failover routing.

Enable Aurora replica auto scaling for read replicas deployed in the standby region to automatically promote a standby instance to a primary writer cluster during a regional failover event.

Configure AWS Backup to take hourly database snapshots and replicate them to the standby region, and set up Amazon Route 53 latency-based routing without active health checks.

Configure Route 53 Private Hosted Zones for public DNS resolution and associate the hosted zone only with the primary region's VPC, while deploying NAT Instances in each Availability Zone.

Show answer & explanation

Answer: Configure Amazon Route 53 with a failover routing policy, designating the primary region's Application Load Balancer as active and the secondary region's Application Load Balancer as passive, and associate active Route 53 health checks with both endpoints.; Create an Amazon Aurora Global Database with the primary database cluster in the active region and a secondary cluster in the passive region, and deploy a NAT Gateway in each Availability Zone utilized by the private EC2 instances in both regions.

Answer

The correct configurations are to deploy an Amazon Aurora Global Database with regional NAT Gateways in each Availability Zone, and to set up Route 53 failover routing with active health checks targeting the Application Load Balancers.

To meet the 1-minute RPO, a replication mechanism with very low latency is required. Amazon Aurora Global Database replication has typical latencies of under a second. To meet the 15-minute RTO, traffic redirection must be automated, which is achieved by using Route 53 failover routing with active health checks to monitor the Application Load Balancers. Finally, deploying a NAT Gateway in each Availability Zone utilized by the private EC2 instances ensures that outbound connectivity remains operational even during a single Availability Zone outage, preventing a single point of failure.

Step-by-Step Solution

Evaluate the database replication strategy to satisfy the 1-minute RPO.

Aurora Global Database replication latency is typically under 1 second, fulfilling the RPO constraint.

Standard multi-region database replication options like backup replication or manual promotion from read replicas cannot satisfy near-zero or sub-minute recovery point requirements.

Establish the multi-region traffic routing strategy for disaster recovery.

Route 53 active-passive failover routing with health checks monitors the primary ALB and automatically redirects DNS traffic during a regional outage, satisfying the 15-minute RTO.

Active health checks are necessary to trigger automated DNS failover without manual intervention.

Architect outbound internet access for private instances to survive a local zone outage.

Deploying a NAT Gateway in each Availability Zone utilized by the VPC resources provides zone-independent outbound routing.

A single NAT Gateway per VPC creates a single point of failure if its hosting Availability Zone goes down.

Key Concept

Disaster recovery planning with tight RTO/RPO requirements requires automated traffic routing failover and low-latency database replication, coupled with zone-redundant NAT architectures to prevent single points of failure.

Estimated Time:2m 0s

Question 192Question →

A SaaS company, 'MetricsFlow', is designing a multi-tenant analytics dashboard. The application running on Amazon EC2 instances in the Production Account (Account A) must read historical reporting logs stored in an Amazon S3 bucket within the Analytics Account (Account B). The S3 bucket is encrypted using an AWS KMS Customer Managed Key (CMK) created in Account B. The security team requires that all cross-account data access adheres to the principle of least privilege.

Which combination of actions must the solutions architect perform in the Analytics Account (Account B) to enable this access? (Select TWO.)

Select all that apply

Update the S3 bucket policy in Account B to grant the s3:GetObject permission to the ARN of the IAM role associated with the EC2 instances in Account A.

Update the KMS key policy of the CMK in Account B to grant the kms:Decrypt permission to the ARN of the IAM role associated with the EC2 instances in Account A.

Modify the S3 encryption configuration in Account B to use the default AWS-managed KMS key (aws/s3) and configure cross-account access using S3 Access Points.

Attach a Service Control Policy (SCP) to the organization root in Account B that explicitly allows the IAM role in Account A to assume key decryption permissions.

Configure a SAML 2.0 federated trust relationship directly within the S3 bucket policy to authorize and trust the EC2 instance profile from Account A.

Show answer & explanation

Answer: Update the S3 bucket policy in Account B to grant the s3:GetObject permission to the ARN of the IAM role associated with the EC2 instances in Account A.; Update the KMS key policy of the CMK in Account B to grant the kms:Decrypt permission to the ARN of the IAM role associated with the EC2 instances in Account A.

Answer

To securely enable cross-account access to encrypted S3 objects, the resource policies in the destination account must trust the IAM identity in the source account. This is accomplished by updating the S3 bucket policy to allow the read action, and updating the Customer Managed Key (CMK) policy to allow the decryption action for the source account's IAM role.

For cross-account access to S3 objects encrypted with a Customer Managed Key (CMK), the resource owner must update both the S3 bucket policy and the KMS key policy in the destination account to explicitly grant access to the IAM role in the source account. The bucket policy must grant read permissions, and the key policy must grant decrypt permissions.

Step-by-Step Solution

Identify the S3 permissions required for cross-account read access.

Determine that the S3 bucket policy in Account B must explicitly permit the IAM role in Account A to read objects.

By default, cross-account access requires explicit permission in the resource-based policy of the resource being accessed.

Identify the KMS permissions required for decryption.

Determine that the Customer Managed Key (CMK) policy in Account B must explicitly permit the IAM role in Account A to perform decryption.

When objects are encrypted with a Customer Managed Key, the reader must have permissions on both the S3 bucket and the key used for encryption.

Key Concept

Cross-account access to encrypted S3 resources requires resource-based policy delegation on both the S3 bucket and the KMS Customer Managed Key.

Estimated Time:1m 30s

Question 193Question →

A financial services company is designing a disaster recovery (DR) architecture for its critical transaction processing application. The application runs on Amazon Elastic Container Service (ECS) on AWS Fargate across two AWS Regions: us-east-1 (Primary) and us-west-2 (Secondary). The database layer uses Amazon Aurora PostgreSQL. The business requirements specify a Recovery Time Objective (RTO) of less than 5 minutes and a Recovery Point Objective (RPO) of less than 1 minute. Outbound transaction requests to external payment gateways must originate from a stable pool of static IP addresses. How should a solutions architect design the network and database layers to meet these requirements with high availability? (Select TWO.)

Select all that apply

Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Use Amazon Route 53 Application Recovery Controller (Route 53 ARC) routing controls to manage failover and route client traffic.

In both us-east-1 and us-west-2, deploy the ECS tasks across multiple Availability Zones (AZs). Deploy a dedicated NAT Gateway associated with an Elastic IP address in each AZ where tasks are deployed, and configure the private subnet route tables to use the local NAT Gateway in their respective AZ.

In both us-east-1 and us-west-2, deploy the ECS tasks across multiple Availability Zones (AZs). To minimize NAT Gateway and Elastic IP costs, deploy a single NAT Gateway in the primary AZ of each region, and configure the private subnet route tables in all AZs to point to that single NAT Gateway.

Use AWS Backup to take hourly snapshots of the Aurora database in us-east-1 and copy them to us-west-2. During a failover event, restore the database from the copied snapshot in us-west-2 and spin up the ECS tasks.

For internal service discovery across regions, create a Route 53 Private Hosted Zone (PHZ) in the primary account and associate it with the us-east-1 VPC. Rely on cross-region VPC peering to automatically resolve names in the us-west-2 VPC without associating the PHZ to it.

Show answer & explanation

Answer: Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Use Amazon Route 53 Application Recovery Controller (Route 53 ARC) routing controls to manage failover and route client traffic.; In both us-east-1 and us-west-2, deploy the ECS tasks across multiple Availability Zones (AZs). Deploy a dedicated NAT Gateway associated with an Elastic IP address in each AZ where tasks are deployed, and configure the private subnet route tables to use the local NAT Gateway in their respective AZ.

Answer

Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Route 53 ARC for failover. In both regions, deploy ECS tasks across multiple AZs using a dedicated NAT Gateway in each AZ to ensure multi-AZ redundancy and support the static IP requirement.

The correct options are the ones recommending Amazon Aurora Global Database combined with Route 53 Application Recovery Controller (Route 53 ARC) for fast, low-RPO/RTO database failover, and deploying a NAT Gateway in every Availability Zone in both regions. Aurora Global Database asynchronous replication keeps lag under a second, meeting the 1-minute RPO. Route 53 ARC routing controls allow failovers within minutes, meeting the 5-minute RTO. Deploying a NAT Gateway in each AZ ensures egress traffic has redundant paths and uses Elastic IP addresses to fulfill the static IP whitelisting requirement.

Step-by-Step Solution

Evaluate the database replication strategy to satisfy the RPO constraint of less than 1 minute.

Amazon Aurora Global Database provides sub-second cross-region replication, which easily satisfies the 1-minute RPO requirement, whereas snapshot backups fail this requirement.

Choosing the correct disaster recovery pattern is critical to meeting RTO and RPO requirements.

Determine the routing and failover orchestration mechanism to satisfy the RTO constraint of less than 5 minutes.

Using Route 53 Application Recovery Controller (Route 53 ARC) allows failover coordination and health monitoring, resulting in a database promotion and DNS change time of under 2 minutes, which is well within the 5-minute RTO.

Manual database restoration or poor DNS failover setups fail to meet the tight RTO.

Design the network egress configuration to provide static outbound IPs and ensure no single point of failure (SPOF) in the private subnets.

Deploying one NAT Gateway per Availability Zone ensures that if one zone fails, only the tasks in that zone are affected. Each NAT Gateway is assigned an Elastic IP, providing the required static IP pool for whitelisting.

Configuring private subnets in multiple AZs to use a single NAT Gateway introduces a single point of failure for internet access, violating high availability principles.

Key Concept

Designing multi-region disaster recovery for databases with sub-minute RPO using Amazon Aurora Global Databases, and ensuring high availability for outbound NAT traffic by avoiding cross-AZ dependencies and implementing redundant NAT Gateways.

Question 194Question →

A digital publishing firm, ChronicleGroup, is designing a new solution where an application running on Amazon ECS in a Production Account (Account A) must read editorial archives stored in an Amazon S3 bucket within a shared Archive Account (Account B). The objects in the S3 bucket are encrypted at rest. The application uses an IAM task execution role in Account A to access the resources. Which combination of configuration steps will allow the application in Account A to decrypt and retrieve the archives from the S3 bucket in Account B?

Use a Customer Managed Key (CMK) in Account B for S3 bucket encryption. Configure the CMK key policy in Account B to allow kms:Decrypt for Account A's IAM role. Configure the S3 bucket policy in Account B to grant read access to Account A's IAM role, and attach an IAM policy to Account A's role allowing S3 read and KMS decrypt permissions.

Use the AWS-managed KMS key (aws/s3) in Account B for S3 bucket encryption. Modify the S3 bucket policy in Account B to allow read access for Account A's IAM role, and attach an IAM policy to the role in Account A allowing s3:GetObject and kms:Decrypt actions.

Use a Customer Managed Key (CMK) in Account B for S3 bucket encryption. Attach a Service Control Policy (SCP) to the Organization Root that allows the IAM role in Account A to perform s3:GetObject and kms:Decrypt on Account B's resources, which grants permission to the role without modifying local IAM or KMS policies.

Use a Customer Managed Key (CMK) in Account B for S3 bucket encryption. Configure the S3 bucket policy and the CMK key policy in Account B to allow read and decrypt access to Account A's IAM role. No IAM policy configuration is required in Account A because the resource-based policies in Account B explicitly delegate access.

Show answer & explanation

Answer: Use a Customer Managed Key (CMK) in Account B for S3 bucket encryption. Configure the CMK key policy in Account B to allow kms:Decrypt for Account A's IAM role. Configure the S3 bucket policy in Account B to grant read access to Account A's IAM role, and attach an IAM policy to Account A's role allowing S3 read and KMS decrypt permissions.

Answer

Use a Customer Managed Key (CMK) in Account B for S3 bucket encryption, grant key decrypt permissions to Account A's IAM role in Account B's key policy, configure the S3 bucket policy in Account B to trust the role, and configure the IAM policy in Account A to permit accessing both resources.

The correct option outlines the necessary three-way handshake for cross-account S3 and KMS access: a Customer Managed Key (CMK) policy in the destination account, a bucket policy in the destination account, and an identity-based IAM policy in the source account.

Step-by-Step Solution

Select the correct key type for cross-account S3 encryption.

Identify that a Customer Managed Key (CMK) is required because AWS-managed keys (aws/s3) do not support cross-account resource sharing.

AWS-managed key policies cannot be altered to include external account principles.

Configure the resource policies in the destination account (Account B).

Update the S3 bucket policy and the Customer Managed Key policy to trust Account A's IAM task execution role.

Resource-based policies must allow external accounts or roles to access them.

Configure the identity policy in the source account (Account A).

Attach an IAM policy to Account A's IAM role allowing s3:GetObject and kms:Decrypt on Account B's bucket and CMK.

Cross-account access requires explicit permission in both the resource policies and the user/role identity policies.

Key Concept

Cross-account access to encrypted S3 resources requires a Customer Managed Key (CMK) with configurations in the IAM identity policy, S3 bucket policy, and KMS key policy.

Estimated Time:2m 0s

Question 195Question →

A fintech startup, PayFlow, is designing a new compliance reporting solution. An application running in a Production Account (Account A) stores transaction logs in an Amazon S3 bucket. The compliance audit team needs to run SQL queries on these logs using Amazon Athena from an Audit Account (Account B) via an IAM role named 'ComplianceAuditorRole'. The S3 bucket is encrypted using an AWS KMS Customer Managed Key (CMK) in Account A. The compliance team mandates that access must be restricted to the minimum necessary permissions and must enforce cross-account separation of duties. Which combination of actions is required to enable the 'ComplianceAuditorRole' in Account B to query the S3 bucket in Account A? (Select TWO.)

Select all that apply

Configure the KMS key policy of the Customer Managed Key (CMK) in Account A to allow the ComplianceAuditorRole in Account B to perform the kms:Decrypt and kms:DescribeKey actions.

Configure the S3 bucket policy in Account A to allow the ComplianceAuditorRole in Account B to perform the s3:GetObject and s3:ListBucket actions.

Configure the S3 bucket in Account A to use the default AWS-managed key (aws/s3) for encryption, and attach an IAM policy to the ComplianceAuditorRole in Account B that permits decryption of the aws/s3 key.

Attach a Service Control Policy (SCP) to the Organizational Unit containing Account B that explicitly allows the s3:GetObject action on the S3 bucket in Account A.

Configure the S3 bucket policy in Account A to grant access to the root user of Account B, specifying the AWS Organization ID as the Principal element.

Show answer & explanation

Answer: Configure the KMS key policy of the Customer Managed Key (CMK) in Account A to allow the ComplianceAuditorRole in Account B to perform the kms:Decrypt and kms:DescribeKey actions.; Configure the S3 bucket policy in Account A to allow the ComplianceAuditorRole in Account B to perform the s3:GetObject and s3:ListBucket actions.

Answer

To configure cross-account S3 bucket access encrypted with a Customer Managed Key (CMK), you must allow the external IAM role access in both the S3 bucket policy and the KMS CMK key policy in the source account, while also granting the permissions in the target account's IAM role.

To establish cross-account access to encrypted S3 resources, the source account (Account A) must delegate trust. This is accomplished by adding the external IAM role in Account B as an authorized principal in the S3 bucket policy for the S3 actions (s3:GetObject and s3:ListBucket) and in the KMS CMK key policy for the decryption actions (kms:Decrypt and kms:DescribeKey). The target account's IAM role must also have a policy allowing these actions.

Step-by-Step Solution

Grant cross-account access to the KMS CMK

The key policy of the CMK in Account A is updated to include the IAM role from Account B as a principal with permissions for kms:Decrypt and kms:DescribeKey.

AWS KMS Customer Managed Keys require explicit key policy delegation to allow decryption by cross-account principals, as AWS-managed keys cannot be shared.

Grant cross-account access to the S3 bucket

The S3 bucket policy in Account A is updated to grant s3:GetObject and s3:ListBucket permissions to the IAM role in Account B.

For cross-account S3 access, the resource-based policy must explicitly allow access to the external principal, in addition to the external principal's own IAM policy.

Key Concept

Cross-account access to encrypted S3 resources requires both resource policy delegation (S3 bucket policy and KMS key policy) in the source account and identity policy permissions in the destination account.

Estimated Time:2m 0s

Question 196Question →

A healthtech company is designing a multi-region disaster recovery (DR) architecture for a critical patient scheduling portal. The primary workload runs in the us-east-1 Region, and the secondary DR site is in the us-west-2 Region. The business requires a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. To minimize ongoing costs, application servers in the secondary region must not run during normal operations. The portal communicates with external medical insurance endpoints, and the architecture must ensure that an Availability Zone (AZ) outage in either region does not disrupt outbound connectivity. Which architecture meets these requirements?

Configure an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy the application tier on Amazon EC2 instances inside Auto Scaling groups across multiple Availability Zones in both regions, setting the desired capacity to zero in us-west-2. Set up Amazon Route 53 with a Failover routing policy and associate it with active application health checks targeting the Application Load Balancer in us-east-1. Deploy a NAT Gateway in each Availability Zone in both regions for outbound traffic routing.

Configure Amazon RDS for PostgreSQL in us-east-1 with cross-region read replication to us-west-2. Deploy the application tier on Amazon EC2 instances inside Auto Scaling groups across multiple Availability Zones in both regions, setting the desired capacity to zero in us-west-2. Set up Amazon Route 53 with a Latency routing policy to handle traffic distribution. Deploy a single NAT Gateway in the public subnet of a single Availability Zone in each region to route outbound traffic.

Configure Amazon Aurora PostgreSQL in us-east-1 and schedule hourly database snapshots copied to us-west-2. Deploy the application tier on Amazon EC2 instances inside Auto Scaling groups in both regions, setting the desired capacity to zero in us-west-2. Configure Amazon Route 53 with a Failover routing policy and active health checks targeting the primary Application Load Balancer. Deploy a NAT Gateway in each Availability Zone in both regions for outbound traffic routing.

Configure an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy the application tier on Amazon EC2 instances inside Auto Scaling groups across multiple Availability Zones in both regions, setting the desired capacity to zero in us-west-2. Set up Amazon Route 53 with a Weighted routing policy, setting the weight for us-east-1 to 100 and us-west-2 to 0. Deploy a NAT Gateway in each Availability Zone in both regions for outbound traffic routing.

Show answer & explanation

Answer: Configure an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy the application tier on Amazon EC2 instances inside Auto Scaling groups across multiple Availability Zones in both regions, setting the desired capacity to zero in us-west-2. Set up Amazon Route 53 with a Failover routing policy and associate it with active application health checks targeting the Application Load Balancer in us-east-1. Deploy a NAT Gateway in each Availability Zone in both regions for outbound traffic routing.

Answer

The architecture using an Amazon Aurora PostgreSQL Global Database, Auto Scaling groups with zero desired capacity in the disaster recovery region, Route 53 Failover routing with active health checks, and a NAT Gateway in each Availability Zone in both regions.

The correct architecture uses Amazon Aurora PostgreSQL Global Database, which replicates data within seconds to meet the 5-minute RPO. It configures Route 53 with a Failover routing policy associated with health checks, allowing DNS to fail over automatically to the secondary region within the 15-minute RTO. Cost is minimized by setting the Auto Scaling group capacity in the recovery region to zero, preventing charges for idle compute resources. Finally, deploying a NAT Gateway in each Availability Zone ensures that outbound connectivity to external endpoints is maintained even if one Availability Zone experiences an outage.

Step-by-Step Solution

Select the database replication method that meets the 5-minute RPO.

Amazon Aurora PostgreSQL Global Database provides typical cross-region replication latency of less than 1 second, easily meeting the 5-minute RPO, whereas hourly snapshots fail this requirement.

Choosing the correct replication mechanism guarantees that data loss stays within the business-defined RPO during a regional disaster.

Configure the DNS failover strategy for active-passive routing.

Amazon Route 53 Failover routing policy combined with health checks targeting the primary region Application Load Balancer (ALB) ensures automatic failover, whereas Weighted routing (100/0) or Latency routing does not provide automatic active-passive failover based on application health.

Automatic failover routing is required to meet the 15-minute RTO without manual intervention.

Ensure outbound connectivity resiliency against Availability Zone outages.

Deploying a NAT Gateway in each Availability Zone in both regions ensures that if one zone goes down, instances in the remaining zones can still route outbound traffic through their zone's NAT Gateway.

A single NAT Gateway per region represents a single point of failure that violates the high availability requirement for outbound traffic.

Key Concept

Multi-region active-passive (pilot light/warm standby) disaster recovery design using Amazon Aurora Global Database, Route 53 DNS Failover, and multi-AZ NAT Gateways.

Question 197Question →

A digital marketing agency is designing a disaster recovery (DR) architecture for its centralized digital asset management platform. The primary production environment runs in the us-east-1 Region, and the DR environment will be deployed in the us-west-2 Region. The architecture must support a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. The design must also minimize ongoing compute costs in the secondary Region during normal operations. The platform's database tier uses an Amazon Aurora PostgreSQL DB cluster.

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

Select all that apply

Configure Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2. In us-west-2, provision a single Aurora Replica of the same instance class as the primary writer to serve as the failover target.

Configure Route 53 with a Failover routing policy. Create a primary record pointing to the us-east-1 Application Load Balancer (ALB) and associate it with a Route 53 health check, and create a secondary record pointing to the us-west-2 ALB.

Configure Route 53 with a Latency routing policy. Associate health checks with the Application Load Balancers (ALBs) in both Regions to dynamically route users to the secondary Region if latency increases or an outage occurs.

Deploy a single NAT Gateway in us-east-1 within a single Availability Zone, and configure the route tables of private subnets in all Availability Zones to route outbound internet traffic through this NAT Gateway to reduce idle resource costs.

Configure Aurora Auto Scaling on the secondary DB cluster in us-west-2 with a target metric to dynamically upgrade the instance class of the standby database from a cost-optimized db.t3.medium to the primary instance class during a failover event.

Show answer & explanation

Answer: Configure Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2. In us-west-2, provision a single Aurora Replica of the same instance class as the primary writer to serve as the failover target.; Configure Route 53 with a Failover routing policy. Create a primary record pointing to the us-east-1 Application Load Balancer (ALB) and associate it with a Route 53 health check, and create a secondary record pointing to the us-west-2 ALB.

Answer

The combination of configuring Amazon Aurora Global Database with a standby replica of the same instance class in the secondary Region, and using Amazon Route 53 Failover routing policy with health checks to route traffic between the Regions.

Configuring Amazon Aurora Global Database provides cross-region replication with a typical replication lag of less than one second, which satisfies the 1-minute RPO. Provisioning a replica of the same instance class in the secondary Region ensures that when the cluster is promoted to primary, it can immediately handle the production load without performance degradation. For DNS routing, configuring a Route 53 Failover routing policy with health checks creates an active-passive setup. This directs all production traffic to the primary Region (us-east-1) under normal operations and automatically redirects users to the secondary Region (us-west-2) during an outage, meeting the 15-minute RTO while keeping the secondary Region's compute resources idle or scaled down.

Step-by-Step Solution

Analyze the database replication mechanism and instance configuration for disaster recovery.

Amazon Aurora Global Database provides sub-second cross-region replication, meeting the 1-minute RPO. The secondary Region's instance must be the same size as the primary to handle the write workload immediately upon failover, satisfying the 15-minute RTO.

Choosing the correct replication technology and sizing ensures database integrity and performance standards are met during failover.

Select the appropriate Route 53 routing policy for an active-passive disaster recovery configuration.

A Route 53 Failover routing policy is chosen, directing all traffic to us-east-1 under normal operations and failing over to us-west-2 when health checks fail.

This policy ensures that the secondary Region's compute resources remain idle/scaled down during normal operations, minimizing running compute costs.

Verify high availability constraints in the primary Region and check for scaling limitations.

Avoid single points of failure like a single NAT Gateway in the primary Region, and avoid invalid configurations like using Aurora Auto Scaling for vertical instance class upgrades.

This guarantees that the primary infrastructure is highly available and that the disaster recovery failover mechanism is technically viable.

Key Concept

Designing active-passive multi-region architectures with low RTO/RPO using Route 53 Failover routing and Aurora Global Database.

Question 198Question →

A financial technology company is designing a new multi-region disaster recovery and high availability architecture for its core payment reconciliation service. The application runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer, and utilizes an Amazon Aurora PostgreSQL database. The application must communicate with external payment gateways over the internet to perform verification. The business requirements specify a Recovery Time Objective (RTO) of 15 minutes, a Recovery Point Objective (RPO) of 2 minutes, and high availability within the primary region. Which of the following architectures meets these requirements with the lowest operational complexity?

Deploy the application in a primary AWS Region and a secondary AWS Region. Use Amazon Aurora Global Database to replicate data to the secondary region. In the primary region, deploy the EC2 instances across multiple Availability Zones, with a NAT Gateway in each Availability Zone. Configure Route 53 with Failover routing policies and active Application Load Balancer health checks to route public user traffic to the primary region.

Deploy the application in a primary AWS Region and a secondary AWS Region. Use Amazon Aurora Global Database to replicate data to the secondary region. In the primary region, deploy the EC2 instances across multiple Availability Zones, but route all outbound traffic through a single NAT Gateway in one Availability Zone to reduce costs. Configure Route 53 with Failover routing policies and active Application Load Balancer health checks.

Deploy the application in a primary AWS Region. Configure Amazon Aurora to automatically copy database snapshots to a secondary AWS Region every 4 hours. In the primary region, deploy the EC2 instances across multiple Availability Zones, with a NAT Gateway in each Availability Zone. Configure Route 53 with Failover routing to direct users to the primary region, and restore the database from the secondary region snapshot during a failover event.

Deploy the application in a primary AWS Region and a secondary AWS Region. Use Amazon Aurora Global Database to replicate data to the secondary region. In the primary region, deploy the EC2 instances across multiple Availability Zones, with a NAT Gateway in each Availability Zone. Configure Route 53 with a Private Hosted Zone to perform failover routing of public client requests to the secondary region during an outage.

Show answer & explanation

Answer: Deploy the application in a primary AWS Region and a secondary AWS Region. Use Amazon Aurora Global Database to replicate data to the secondary region. In the primary region, deploy the EC2 instances across multiple Availability Zones, with a NAT Gateway in each Availability Zone. Configure Route 53 with Failover routing policies and active Application Load Balancer health checks to route public user traffic to the primary region.

Answer

Deploy the application in primary and secondary regions, using Amazon Aurora Global Database for replication. Ensure outbound connectivity in the primary region is resilient by placing a NAT Gateway in each Availability Zone, and use Route 53 Failover routing with public Application Load Balancer health checks to handle region failover.

The configuration that deploys the application across two regions with Amazon Aurora Global Database satisfies the strict 2-minute RPO because Aurora Global Database replicates data in under a second. The 15-minute RTO is met via Route 53 Failover routing to direct public traffic to the primary region and fail over to the secondary region if a disaster occurs. Deploying a NAT Gateway in each Availability Zone ensures that outbound payment gateway communication remains highly available within the primary region.

Step-by-Step Solution

Determine the database replication strategy based on RPO and RTO constraints.

Aurora Global Database is selected because it replicates data cross-region asynchronously with typical latency of less than 1 second, meeting the 2-minute RPO, whereas snapshot-based solutions fail.

The 2-minute RPO cannot be satisfied by periodic snapshot backups, making continuous replication mandatory.

Evaluate the primary region's networking components for high availability.

NAT Gateways must be deployed in every Availability Zone containing application subnets.

Routing all subnets through a single NAT Gateway creates a single point of failure, violating the requirement for high availability in the primary region if that specific zone fails.

Select the appropriate Route 53 routing configuration for external clients.

Route 53 public failover routing policies linked to Application Load Balancer health checks are configured.

Private Hosted Zones only resolve DNS requests originating from inside the associated VPCs, meaning public clients require public hosted zone records for failover.

Key Concept

Disaster recovery architectures require aligning database replication (RPO), networking redundancy (HA), and public DNS routing (RTO) to eliminate single points of failure both within and across AWS regions.

Question 199Question →

A metropolitan transit authority is designing a new multi-region disaster recovery (DR) architecture for its public transit ticketing system. The primary production environment runs in the us-east-1 Region, and the secondary disaster recovery environment will be located in the us-west-2 Region. The application consists of a ticketing API hosted on Amazon EC2 instances inside private subnets behind an Application Load Balancer (ALB), and a backend database. The API needs to perform outbound calls to external payment gateways. Internal services resolve endpoints using a Route 53 Private Hosted Zone. The architecture must achieve a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes while minimizing cost during normal operations. Which of the following architectures meets these requirements?

Deploy the application on Amazon EC2 instances in an Auto Scaling group scaled to minimum capacity in us-west-2. Use Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy a NAT Gateway in each Availability Zone in both regions. Configure Amazon Route 53 Failover routing to direct public traffic to us-east-1, and associate the internal Route 53 Private Hosted Zone with the VPCs in both regions.

Deploy the application on Amazon EC2 instances in an Auto Scaling group scaled to minimum capacity in us-west-2. Use Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy a single NAT Gateway in the first Availability Zone of each region to reduce idle gateway costs. Configure Amazon Route 53 Failover routing to direct public traffic to us-east-1, and associate the internal Route 53 Private Hosted Zone with the VPCs in both regions.

Deploy the application on Amazon EC2 instances in an Auto Scaling group scaled to minimum capacity in us-west-2. Use Amazon RDS for PostgreSQL in us-east-1 with a cross-region Read Replica in us-west-2. Deploy a NAT Gateway in each Availability Zone in both regions. Configure Amazon Route 53 Latency-based routing to distribute traffic between regions, and manually promote the RDS replica during a disaster event.

Show answer & explanation

Answer: Deploy the application on Amazon EC2 instances in an Auto Scaling group scaled to minimum capacity in us-west-2. Use Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy a NAT Gateway in each Availability Zone in both regions. Configure Amazon Route 53 Failover routing to direct public traffic to us-east-1, and associate the internal Route 53 Private Hosted Zone with the VPCs in both regions.

Answer

The correct architecture uses Amazon Aurora Global Database to replicate data with sub-second latency, satisfying the 5-minute RPO. A Warm Standby deployment in the secondary region ensures the instances are online and ready to scale, which easily meets the 15-minute RTO. Redundant NAT Gateways in each Availability Zone eliminate single points of failure for outbound payment gateway traffic. Finally, Route 53 Failover routing automatically shifts traffic upon primary ALB failure, while the Private Hosted Zone association with both VPCs ensures that internal DNS resolution remains functional after failover.

Step-by-Step Solution

Select the appropriate database replication strategy to meet the RPO constraint.

Amazon Aurora Global Database provides replication lag of less than 1 second, meeting the 5-minute RPO requirement, and supports fast cross-region failover.

Standard RDS PostgreSQL cross-region replication is asynchronous and promotion is manual, which increases RTO and risk of data loss beyond 5 minutes.

Determine the application tier DR strategy to meet the 15-minute RTO at minimal cost.

A Warm Standby pattern using a scaled-down Auto Scaling group in the secondary region ensures instances are running and ready to scale out quickly upon failover, staying well within the 15-minute window while minimizing standby costs.

Cold standby deployment via CloudFormation takes too long to spin up resources, execute bootstrap scripts, and pass health checks, risking RTO violations.

Ensure NAT Gateway redundancy for payment gateway validation traffic.

Deploy one NAT Gateway per Availability Zone in each VPC.

A single NAT Gateway per VPC creates a single point of failure. If the Availability Zone containing the NAT Gateway goes down, all other private subnets lose egress connectivity.

Configure DNS routing and internal service resolution for multi-region failover.

Set up Route 53 Failover routing with active-passive configuration, and associate the Route 53 Private Hosted Zone with both the us-east-1 and us-west-2 VPCs.

Failover routing automatically shifts public traffic when health checks fail. Private Hosted Zones must be explicitly associated with the consumer VPC in the secondary region, as VPC peering does not forward Private Hosted Zone queries.

Key Concept

Multi-Region Active-Passive Disaster Recovery with Aurora Global Database and Route 53 Failover Routing

Estimated Time:2m 0s

Question 200Question →

A logistics company is designing a telemetry ingestion system for connected vehicles. The system must ingest real-time GPS data from vehicles globally. The primary workload runs in the us-east-1 Region, utilizing an Amazon ECS cluster running on AWS Fargate in private subnets, an Application Load Balancer (ALB), and a database layer. The architecture must be expanded to the us-west-2 Region to support a disaster recovery plan with an RTO of under 5 minutes and an RPO of under 1 minute. Active-active routing is preferred to minimize ingestion latency for vehicles on the West Coast. The company needs to minimize operational complexity while maintaining high availability, and the Fargate tasks require highly resilient outbound internet access in both regions to fetch firmware updates without a single point of failure. Which of the following actions should the Solutions Architect take to meet these requirements? (Select TWO.)

Select all that apply

Configure Amazon DynamoDB Global Tables to replicate database tables between the us-east-1 and us-west-2 regions.

Configure Route 53 latency-based routing policies with health checks to route telemetry traffic to the nearest region, and deploy a NAT Gateway in each Availability Zone in both regions.

Configure AWS Backup to perform hourly cross-region copying of Amazon DynamoDB backups from us-east-1 to us-west-2.

Deploy a single NAT Gateway in the primary Availability Zone of each region, and configure route tables in all other Availability Zones to point to this single NAT Gateway.

Deploy the database layer using Amazon Aurora PostgreSQL with active-active write replication, and configure Aurora Auto Scaling to dynamically adjust database replication lag.

Configure Route 53 with a Private Hosted Zone to resolve the public Application Load Balancer endpoints for telemetry client connections.

Show answer & explanation

Answer: Configure Amazon DynamoDB Global Tables to replicate database tables between the us-east-1 and us-west-2 regions.; Configure Route 53 latency-based routing policies with health checks to route telemetry traffic to the nearest region, and deploy a NAT Gateway in each Availability Zone in both regions.

Answer

Configure Amazon DynamoDB Global Tables to replicate database tables between the us-east-1 and us-west-2 regions, and configure Route 53 latency-based routing policies with health checks while deploying a NAT Gateway in each Availability Zone in both regions.

The correct answer combines Amazon DynamoDB Global Tables to achieve fully managed, active-active multi-region database replication with sub-second replication lag, thereby satisfying the strict RPO under 1 minute. It also uses Route 53 latency-based routing to ensure vehicles reach the closest region for minimum latency, coupled with a NAT Gateway per Availability Zone to prevent a single Availability Zone outage from breaking outbound internet access for ECS tasks.

Step-by-Step Solution

Select a multi-region active-active database replication strategy to satisfy the RPO constraint.

Amazon DynamoDB Global Tables replicate data across regions with sub-second replication latency, meeting the 1-minute RPO requirement without custom coding.

Traditional backup restore methods (hourly copying) exceed both the RPO and RTO requirements.

Design dynamic routing for active-active low-latency ingress client traffic.

Configure Route 53 latency-based routing policies with health checks to route telemetry traffic from vehicles to the nearest healthy regional Application Load Balancer.

This guarantees that vehicles connect to the closest region, reducing latency and facilitating automatic regional failover.

Ensure outbound connectivity redundancy in both regions for private subnet resources.

Deploy a NAT Gateway in each Availability Zone in public subnets of both regions, and update the private subnet route tables to reference their local NAT Gateway.

Sharing a single NAT Gateway across Availability Zones creates a single point of failure, violating the high availability and resiliency requirements.

Key Concept

Multi-region active-active design using Amazon DynamoDB Global Tables, combined with Route 53 latency-based routing and localized NAT Gateway redundancy for resilient ingress/egress patterns.

PreviousPage 10 / 99Next

All practice questions

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept