Tüm alıştırma soruları

1964 soru

Soru 941Soru

A digital publishing company hosts a content delivery and document archiving platform on AWS. The application runs on Amazon ECS tasks on AWS Fargate behind an Application Load Balancer (ALB) in a single AWS Region. The document metadata is stored in an Amazon Aurora PostgreSQL Serverless v2 database cluster. Files are uploaded directly to an Amazon S3 bucket.

Currently, the company's disaster recovery (DR) strategy relies on daily automated Aurora snapshots copied to a second region and cross-region S3 replication. The company wants to improve its reliability and disaster recovery posture to achieve a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 55 minutes in a secondary region.

Which two actions should a solutions architect take to meet these requirements with the least operational overhead?

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

Cevabı ve açıklamayı göster

Cevap: Convert the existing Amazon Aurora PostgreSQL database cluster into an Aurora Global Database by adding a secondary DB cluster in the secondary AWS Region.; Deploy the Amazon ECS tasks and the Application Load Balancer in the secondary AWS Region, and configure Amazon Route 53 Application Recovery Controller (ARC) routing control to manage traffic failover.

Cevap

Convert the database to an Aurora Global Database and deploy the application in the secondary region using Route 53 Application Recovery Controller (ARC) for failover routing.
To meet the 5-minute RPO, a live replication strategy is required. Converting the Aurora database to an Aurora Global Database ensures data is replicated across regions in near-real-time. To meet the 15-minute RTO, deploying the ECS tasks and ALB in the secondary region and using Amazon Route 53 Application Recovery Controller (ARC) routing control allows fast, deterministic failover of application traffic.

Adım Adım Çözüm

1
Address the 5-minute RPO database requirement by setting up real-time cross-region replication.
Converting the database cluster to an Aurora Global Database and adding a secondary cluster in the secondary region ensures sub-second replication latency.
This guarantees that database state is kept up to date within seconds, satisfying the 5-minute RPO with minimal administrative effort.
2
Address the 15-minute RTO traffic and compute failover requirements.
ECS tasks and an ALB are provisioned in the secondary region, and Route 53 Application Recovery Controller (ARC) routing controls are configured to direct traffic.
This allows deterministic, fast traffic redirection during a disaster, fulfilling the RTO requirement.

Anahtar Kavram

Selecting and configuring AWS multi-region disaster recovery mechanisms to achieve low RTO and RPO targets while ensuring proper cross-region resource connectivity and traffic control.
Soru 942Soru

A digital sports media company is preparing for a live-streamed championship event that is expected to attract millions of concurrent viewers within a 55-minute window. The application runs on Amazon EC2 instances in an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The application reads and writes user profile and viewing state data to an Amazon Aurora PostgreSQL DB cluster consisting of one writer instance in Availability Zone (AZ) A and one reader instance in AZ B.

During load testing, the following performance issues are observed:
- A sudden, massive flood of requests at the start of the event causes the ALB to drop connections and return HTTP 503 (Service Unavailable) errors before the ASG or ALB can scale out.
- The reporting and leaderboard dashboard queries, which are read-heavy, cause significant CPU utilization spikes on the primary writer instance because the application is currently configured to connect to the DB cluster endpoint for all operations.

Which combination of architectural modifications will optimize the compute and storage layers to handle the event's performance requirements?

Cevabı ve açıklamayı göster

Cevap: Submit a support ticket to AWS to pre-warm the Application Load Balancer based on the expected traffic profile. Update the dashboard application configuration to use the reader endpoint of the Aurora DB cluster to distribute the read queries across the available Aurora Replicas.

Cevap

Submit a support ticket to AWS to pre-warm the Application Load Balancer based on the expected traffic profile. Update the dashboard application configuration to use the reader endpoint of the Aurora DB cluster to distribute the read queries across the available Aurora Replicas.
The correct option addresses both the network/compute bottleneck at the ingress layer and the database compute bottleneck. Requesting AWS to pre-warm the ALB ensures the load balancer can handle millions of concurrent connections immediately. Utilizing the Aurora reader endpoint ensures that read queries are routed to the Aurora reader replica rather than the writer, relieving CPU strain on the database cluster's primary node.

Adım Adım Çözüm

1
Analyze the load profile and ALB scaling capabilities.
Identify that the expected traffic spike is instantaneous (55-minute window), meaning standard ALB scaling will be too slow, resulting in dropped requests.
ALBs scale in response to traffic over time; sudden, massive surges require pre-warming by AWS Support to pre-provision capacity.
2
Address the write instance CPU utilization bottleneck.
Observe that write and read workloads are sharing the same primary instance, leading to resource contention.
Separating read queries from write queries is a standard pattern to optimize database compute resource usage.
3
Redirect read queries using the Aurora reader endpoint.
Configure the read-heavy reporting application to connect to the cluster reader endpoint instead of the primary writer cluster endpoint.
The reader endpoint automatically load-balances connection requests across all available Aurora Replicas, offloading read operations from the writer instance.

Anahtar Kavram

Optimizing compute and storage performance by combining ELB pre-warming for sudden peak workloads and Aurora reader endpoints for database read scaling.
Soru 943Soru

A financial services company hosts a latency-sensitive trading application on AWS. The architecture consists of a client-facing VPC in the us-east-1 Region, a client-facing VPC in the us-west-2 Region, and a shared services VPC in us-east-1. Currently, all three VPCs are interconnected using an AWS Transit Gateway. The application developers are reporting two major issues: high network latency during database synchronization between the us-east-1 client VPC and the us-east-1 shared services VPC, and host name resolution failures when the us-west-2 application attempts to access endpoints in the shared services Private Hosted Zone (PHZ). Which two actions should a solutions architect recommend to optimize network performance, reduce latency, and resolve the DNS issues? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Establish a direct VPC Peering connection between the us-east-1 client-facing VPC and the us-east-1 shared services VPC.; Associate the Route 53 Private Hosted Zone from the shared services account with both client-facing VPCs.

Cevap

Establish a direct VPC Peering connection between the us-east-1 client-facing VPC and the us-east-1 shared services VPC, and associate the Route 53 Private Hosted Zone from the shared services account with both client-facing VPCs.
Establishing a direct VPC Peering connection between the us-east-1 client VPC and the us-east-1 shared services VPC optimizes network performance by offering the lowest latency and highest bandwidth path without Transit Gateway processing overhead. Associating the Route 53 Private Hosted Zone with the client-facing VPCs in both regions allows local DNS resolution of private endpoints across accounts.

Adım Adım Çözüm

1
Analyze regional latency constraints.
Identify that the us-east-1 client-facing VPC and us-east-1 shared services VPC are in the same region, meaning they can benefit from direct VPC Peering to eliminate the latency added by Transit Gateway processing.
VPC Peering does not have intermediate device hops, offering lower latency for intra-region traffic compared to Transit Gateway.
2
Resolve DNS failures for cross-account and cross-region endpoints.
Associate the Route 53 Private Hosted Zone (PHZ) created in the shared services account with the client-facing VPCs in both us-east-1 and us-west-2.
A Private Hosted Zone must be explicitly associated with any VPC that requires resolution of its records, even across accounts and regions.

Anahtar Kavram

Bypassing intermediate transit hops via VPC Peering for lowest latency, and cross-account/cross-region Private Hosted Zone association.
Soru 944Soru

An enterprise is designing a new multi-account AWS architecture. The design includes two spoke VPCs (`vpc-app-a` and `vpc-app-b`) in the `us-east-1` Region, each with subnets across two Availability Zones (`us-east-1a` and `us-east-1b`). The enterprise also has an egress VPC (`vpc-egress`) in `us-east-1` to centralize internet-bound traffic, and an on-premises datacenter connected via AWS Direct Connect (DX). A Private Hosted Zone (PHZ) named `corp.internal` is hosted in a central networking account.

The architecture must meet the following requirements:
1. Spoke VPCs must be able to communicate with each other and with the on-premises datacenter.
2. All outbound internet traffic from the spoke VPCs must route through `vpc-egress` in a highly available manner that survives an Availability Zone outage.
3. Resources within the spoke VPCs must resolve DNS queries for the `corp.internal` domain.

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

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

Cevabı ve açıklamayı göster

Cevap: Authorize and associate the `corp.internal` Private Hosted Zone in the central networking account with `vpc-app-a` and `vpc-app-b` using the AWS CLI or Route 53 API, and ensure that the VPCs have `enableDnsHostnames` and `enableDnsSupport` set to true.; Deploy an AWS Transit Gateway and attach both spoke VPCs and `vpc-egress`. Create a NAT Gateway in each Availability Zone of `vpc-egress`. Configure the spoke VPC route tables to route all outbound internet traffic (0.0.0.0/00.0.0.0/0) to the Transit Gateway, and configure the Transit Gateway route tables to route egress traffic to the `vpc-egress` attachments.

Cevap

To meet all requirements, the Solutions Architect must deploy an AWS Transit Gateway and associate the Private Hosted Zone with the spoke VPCs, while ensuring NAT Gateways are deployed in multiple Availability Zones within the egress VPC.
Associating the Private Hosted Zone with the spoke VPCs enables cross-account DNS resolution for internal resources, provided DNS hostnames and DNS support are enabled on those VPCs. Deploying Transit Gateway enables transitive routing between the spokes and to the egress VPC, and deploying NAT Gateways in multiple Availability Zones within the egress VPC ensures that outbound traffic routes remain resilient to Availability Zone failures.

Adım Adım Çözüm

1
Design the routing architecture using AWS Transit Gateway to attach the spoke VPCs and the egress VPC, which allows VPC-to-VPC transitive communication and outbound routing to the egress VPC.
Transitive routing path established across all accounts and VPCs.
Direct Connect Gateway alone does not support transitive routing between attached VPCs.
2
Deploy NAT Gateways in multiple Availability Zones (both us-east-1a and us-east-1b) in the egress VPC.
Outbound internet traffic paths are made redundant across AZs.
Avoids introducing a single point of failure for internet egress traffic.
3
Perform cross-account Private Hosted Zone association by authorizing the association of the domain in the central networking account and associating it with the spoke VPCs.
The spoke VPCs can successfully resolve the private domain queries internally.
Private Hosted Zones must be explicitly associated with a VPC to allow local resolution.

Anahtar Kavram

Multi-account hybrid routing and cross-account Private Hosted Zone DNS resolution with highly available egress design.
Soru 945Soru

A technology company is designing a new multi-VPC environment in the us-east-1 Region. The architecture consists of a Shared Services VPC and three spoke VPCs (Prod-VPC, Stage-VPC, and Dev-VPC). All spoke VPCs must be able to communicate with the Shared Services VPC, but the spoke VPCs must be completely isolated from one another. Additionally, resources in all spoke VPCs must resolve private DNS records for services hosted in the Shared Services VPC. Which of the following networking designs satisfies these requirements while minimizing administrative overhead?

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway with two Transit Gateway route tables. Associate the spoke VPCs with the first route table, routing traffic only to the Shared Services VPC. Associate the Shared Services VPC with the second route table, routing traffic to all spoke VPCs. Create a Route 53 Private Hosted Zone in the Shared Services VPC, and associate the zone with the Shared Services VPC and all three spoke VPCs.

Cevap

Deploy an AWS Transit Gateway with two Transit Gateway route tables. Associate the spoke VPCs with the first route table, routing traffic only to the Shared Services VPC. Associate the Shared Services VPC with the second route table, routing traffic to all spoke VPCs. Create a Route 53 Private Hosted Zone in the Shared Services VPC, and associate the zone with the Shared Services VPC and all three spoke VPCs.
The correct design uses AWS Transit Gateway with two separate route tables to enforce traffic isolation. Spoke VPCs are associated with a route table that only has a route to the Shared Services VPC, preventing them from routing traffic to each other. The Shared Services VPC is associated with a route table that has routes to all spokes, allowing bidirectional communication with them. Furthermore, associating the Route 53 Private Hosted Zone with all four VPCs ensures that private DNS queries from the spoke VPCs can be resolved correctly.

Adım Adım Çözüm

1
Define the routing architecture using AWS Transit Gateway to establish hub-and-spoke connectivity.
Deploy an AWS Transit Gateway and attach the Shared Services VPC and the three spoke VPCs.
Transit Gateway acts as a central cloud router to connect VPCs at scale.
2
Configure Transit Gateway route tables to isolate the spokes while allowing access to Shared Services.
Create two Transit Gateway route tables. Associate spoke VPCs with a route table that has a route pointing only to the Shared Services VPC. Associate the Shared Services VPC with a route table that has routes to all spoke VPCs.
This implements spoke isolation (preventing spoke-to-spoke traffic) while maintaining connectivity to the Shared Services VPC.
3
Configure DNS resolution for private resources.
Create a Route 53 Private Hosted Zone in the Shared Services VPC and associate it with the Shared Services VPC, Prod-VPC, Stage-VPC, and Dev-VPC.
This allows resources in all VPCs to resolve the private DNS names of the services hosted in the Shared Services VPC.

Anahtar Kavram

Multi-VPC isolation using Transit Gateway route tables and DNS resolution using Route 53 Private Hosted Zone associations.
Tahmini Süre:2m 0s
Soru 946Soru

A financial services firm runs a core banking microservice platform across two AWS accounts in an AWS Organization: Account A hosts the Production environment in the eu-west-1 Region, and Account B hosts the Disaster Recovery (DR) environment in the eu-central-1 Region. The application tier runs on Amazon ECS tasks on AWS Fargate in private subnets, resolving local services using a Route 53 Private Hosted Zone (PHZ) (service.internal) hosted in Account A. Database access is managed via an Amazon Aurora PostgreSQL Global Database, with the primary cluster in Account A and the secondary cluster in Account B. Currently, outbound internet access for the ECS tasks in both regions is routed through a single NAT Gateway located in a single public subnet within each region's VPC. The firm wants to enhance the architecture to achieve a recovery time objective (RTO) of under 15 minutes and a recovery point objective (RPO) of under 1 minute during a regional outage. Which TWO actions should the Solutions Architect implement to enhance reliability and automate disaster recovery failover?

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

Cevabı ve açıklamayı göster

Cevap: Authorize the association of the Route 53 Private Hosted Zone in Account A with the VPC in Account B using the AWS CLI or SDK, and then associate the VPC in Account B. Configure a Route 53 failover routing policy for the private database DNS record, linked to Route 53 health checks that monitor regional database health via CloudWatch alarms.; Deploy NAT Gateways in multiple Availability Zones within both the primary and recovery VPCs, and update the private subnet route tables in each Availability Zone to route outbound internet traffic through the NAT Gateway in the same Availability Zone.

Cevap

Authorize and associate the Private Hosted Zone in the primary account with the recovery VPC, utilizing CloudWatch alarms for Route 53 private failover routing, and deploy redundant NAT Gateways per Availability Zone to remove single points of failure.
To successfully failover the DNS record of private resources such as Aurora database endpoints across accounts and regions, the Private Hosted Zone in the primary account must be authorized and associated with the recovery VPC in the destination account. Since Route 53 health checks cannot directly probe internal, private IP addresses within a VPC, they must be associated with CloudWatch alarms that monitor regional database metrics. Furthermore, ensuring that outbound internet routing is redundant across all Availability Zones by using a dedicated NAT Gateway per zone ensures high availability for the ECS tasks and any egress communications during a failover event.

Adım Adım Çözüm

1
Establish cross-account VPC association for the Route 53 Private Hosted Zone (PHZ) from Account A to Account B.
Allows Fargate tasks in the recovery VPC in Account B to query the shared service.internal namespace locally.
VPC association authorization must be created in Account A and accepted in Account B using the AWS CLI or SDK to resolve internal records across accounts.
2
Link Route 53 health checks to CloudWatch alarms monitoring regional database availability.
Enables DNS failover fail-over for private records inside a VPC that cannot be reached directly by public Route 53 endpoints.
Since Aurora private IP addresses are unreachable from the public Route 53 edge health checkers, a CloudWatch alarm acts as the status intermediary.
3
Deploy multiple NAT Gateways (one per Availability Zone) in the public subnets of both VPCs, and configure private subnet route tables to use the NAT Gateway in their respective Availability Zone.
Eliminates single points of failure for outbound traffic routing to external systems or cross-region replication endpoints.
A single NAT Gateway per VPC creates a vulnerability where an Availability Zone outage could disrupt egress traffic for all other zones.

Anahtar Kavram

Disaster recovery failover automation and egress reliability in multi-account, multi-region hybrid DNS architectures
Soru 947Soru

A financial services company runs a high-frequency trading application on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The instances process incoming transactions and write detailed raw execution logs to attached 500 GiB Amazon EBS gp3 volumes (with default configurations of 3,000 IOPS and 125 MB/s throughput) before archiving the logs to Amazon S3. Transactional state is maintained in an Amazon Aurora MySQL DB cluster.

During weekly scheduled flash trading events, the company experiences the following performance issues:
- The ALB immediately drops a significant percentage of incoming requests, returning HTTP 503 (Service Unavailable) errors, because traffic surges from 2,000 requests/second to 150,000 requests/second within 30 seconds.
- The EC2 instances experience severe write latency and high disk queue length as the log writing throughput surges to 450 MB/s with 9,500 IOPS during peak trade processing.

Which of the following actions should the Solutions Architect recommend to resolve these performance bottlenecks? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Request AWS Support to pre-warm the Application Load Balancer with the expected peak request rate and rate of increase before the scheduled events.; Modify the EBS gp3 volumes to provision 10,000 IOPS and 500 MB/s throughput to accommodate the peak log ingestion rate.

Cevap

To resolve the performance bottlenecks, the Solutions Architect should recommend requesting AWS Support to pre-warm the Application Load Balancer and modifying the EBS gp3 volumes to provision 10,000 IOPS and 500 MB/s throughput.
The correct solution addresses the network bottleneck by pre-warming the ALB to handle the sudden 150,000 requests/second spike, and resolves the storage bottleneck by provisioning sufficient IOPS (10,000) and throughput (500 MB/s) on the EBS gp3 volumes to handle the 9,500 IOPS and 450 MB/s logging workload.

Adım Adım Çözüm

1
Analyze the Application Load Balancer HTTP 503 errors caused by the flash traffic spike (2,000 to 150,000 requests/second).
Identify that the ALB cannot scale dynamically fast enough for instantaneous surges, leading to dropped requests.
Establishing that standard ALB auto-scaling is too gradual and requires pre-warming by AWS Support.
2
Analyze the EC2 EBS storage bottleneck during peak log writes (9,500 IOPS and 450 MB/s).
Determine that the default gp3 configurations (3,000 IOPS, 125 MB/s) are throttling the application write throughput.
Determining that configuring the gp3 volumes to provision 10,000 IOPS and 500 MB/s satisfies the performance requirements in a cost-effective manner.
3
Evaluate the proposed DB and Auto Scaling group adjustments.
Eliminate RDS Multi-AZ migration and aggressive cooldown reductions as viable solutions.
Ensuring that the final configuration avoids passive standby architectures and Auto Scaling group thrashing.

Anahtar Kavram

Optimizing EBS storage throughput/IOPS and scaling load balancers for rapid traffic spikes
Soru 948Soru

A company runs a genomic data processing application on Amazon EC2 instances in an Auto Scaling group. The instances process large datasets downloaded from Amazon S3. The input files are written to 200 GiB Amazon EBS gp3 volumes configured with default IOPS and throughput (3,000 IOPS and 125 MiB/s). During peak processing, CloudWatch metrics show that the EBS volumes are constantly throttled at the 125 MiB/s throughput limit, causing high CPU wait times. Additionally, when the queue size increases, the Auto Scaling group launches new instances. However, because it takes 10 minutes to bootstrap the instances (downloading software and reference databases), the scaling metric remains high, causing the Auto Scaling group to continuously launch unnecessary instances during this startup period. Which two actions should the solutions architect take to resolve these performance and scaling issues?

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

Cevabı ve açıklamayı göster

Cevap: Increase the throughput of the gp3 EBS volumes to 500 MiB/s to eliminate the storage I/O bottleneck.; Create a custom AMI containing the pre-installed software and reference databases, and configure the scaling policy's warm-up timer to match the remaining initialization time.

Cevap

Increase the throughput of the gp3 EBS volumes to 500 MiB/s to eliminate the storage I/O bottleneck, and create a custom AMI containing the pre-installed software and reference databases, while configuring the scaling policy's warm-up timer to match the remaining initialization time.
The correct options identify that gp3 volumes support independent throughput tuning up to 1,000 MiB/s, which resolves the disk bottleneck. Furthermore, reducing EC2 bootstrapping duration by baking software into a custom AMI, and setting a proper warm-up period in the Auto Scaling group scaling policy, prevents the group from over-provisioning instances before they are fully online.

Adım Adım Çözüm

1
Analyze the storage bottleneck.
The gp3 EBS volumes are limited to the default 125 MiB/s throughput. This can be resolved by increasing the throughput parameter of the gp3 volume up to 1,000 MiB/s.
Since the CPU cores are waiting on storage I/O, increasing EBS throughput to 500 MiB/s will allow faster read/write operations and eliminate the CPU wait times.
2
Analyze the scaling bottleneck.
Bootstrapping takes 10 minutes, which is longer than the scaling evaluation window, leading to over-provisioning.
By creating a custom AMI with the required dependencies pre-installed, we significantly reduce the startup time. Combining this with a scale-out warm-up period ensures the Auto Scaling group does not launch duplicate instances while the active ones are warming up.

Anahtar Kavram

Optimizing compute scaling dynamics and storage performance by tuning EBS throughput and reducing EC2 instance bootstrap times.
Soru 949Soru

An enterprise runs a critical medical imaging application across multiple AWS accounts in an AWS Organization. The core database is an Amazon Aurora MySQL global database, with the primary cluster in us-east-1 and a secondary cluster in us-west-2. The application layer runs on Amazon Elastic Container Service (Amazon ECS) tasks on AWS Fargate behind Application Load Balancers (ALBs) in both regions. The application's DNS domain, imaging.internal.example.com, is hosted in a Route 53 private hosted zone (PHZ) in a shared services account. The PHZ is associated with the application VPCs in both regions. A Solutions Architect needs to enhance the disaster recovery (DR) capability to achieve a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 2 minutes. The failover process must be fully automated, including the routing of internal traffic to the active region during an outage in us-east-1. Which combination of actions should the Solutions Architect take to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure a Route 53 health check that monitors a CloudWatch alarm tracking the HealthyHostCount metric of the primary Application Load Balancer. In the private hosted zone, configure failover routing records for the application domain, associating the primary record with this health check.; Configure an Amazon EventBridge rule in the primary region to trigger when the CloudWatch alarm monitoring the Application Load Balancer health transitions to the ALARM state. Target an AWS Lambda function that invokes the RDS failover-global-cluster API to promote the secondary database cluster.

Cevap

The correct actions are to configure a Route 53 health check that monitors a CloudWatch alarm tracking the HealthyHostCount metric of the primary Application Load Balancer, and to configure an Amazon EventBridge rule that triggers an AWS Lambda function to promote the secondary database cluster using the failover-global-cluster API call.
The correct options implement a fully automated active-passive failover. In a private hosted zone, standard Route 53 health checks cannot directly probe internal resources; instead, a CloudWatch alarm based on ALB health is monitored by Route 53. To fail over the database, an EventBridge rule catches the alarm state transition and triggers a Lambda function to promote the secondary Aurora cluster using the RDS failover-global-cluster API.

Adım Adım Çözüm

1
Address private network routing failover by creating a CloudWatch alarm that tracks the HealthyHostCount metric of the primary ALB.
A metric-based trigger is established in the primary region to detect application layer failure.
Route 53 cannot probe private IP addresses directly from its public health checkers, so monitoring a CloudWatch alarm is required for Route 53 Private Hosted Zone failover.
2
Configure a Route 53 health check linked to the CloudWatch alarm, and create primary/secondary failover records in the private hosted zone.
Internal DNS queries resolve to the secondary ALB if the primary ALB becomes unhealthy.
This automates traffic redirection to the secondary region within minutes, contributing to the sub-15-minute RTO goal.
3
Configure an EventBridge rule that listens to the state change of the primary ALB CloudWatch alarm and triggers an AWS Lambda function.
An automated failover script is invoked upon detecting a primary region outage.
Automating the database promotion is necessary to achieve near-zero RPO and low RTO without manual intervention.
4
Use the AWS SDK inside the Lambda function to execute the failover-global-cluster API against the Aurora Global Database.
The secondary cluster is promoted to a standalone primary cluster.
Aurora Global Database replication has an RPO of less than 1 second, and promoting the secondary cluster takes less than a few minutes, satisfying the DR objectives.

Anahtar Kavram

Multi-region disaster recovery automation using Route 53 private hosted zones and Aurora Global Database failover mechanisms.
Soru 950Soru

A software company hosts a latency-sensitive API in the us-east-1 Region behind an Application Load Balancer (ALB). Users in Europe are experiencing high latency and frequent connection timeouts due to unpredictable routing and packet loss over the public internet. Which of the following solutions should the solutions architect implement to optimize network performance and reduce latency for these global users?

Cevabı ve açıklamayı göster

Cevap: Deploy AWS Global Accelerator in front of the Application Load Balancer to ingest user traffic at edge locations nearest to the users and route it over the AWS global network.

Cevap

Deploy AWS Global Accelerator in front of the Application Load Balancer to ingest user traffic at edge locations nearest to the users and route it over the AWS global network.
Deploying AWS Global Accelerator is the most effective solution because it provides two static IP addresses that utilize Anycast routing to ingest TCP traffic at the nearest AWS edge location. From the edge, the traffic is routed over the congestion-free AWS global network to the Application Load Balancer in us-east-1, significantly reducing latency and connection timeouts.

Adım Adım Çözüm

1
Analyze the source of the network issue.
The latency and packet loss are caused by routing over the public internet across a large geographic distance (Europe to us-east-1).
Identifying the root cause ensures we target network path optimization rather than regional load capacity.
2
Evaluate AWS services designed for global network optimization.
AWS Global Accelerator provides static IP addresses that act as entry points to the AWS global network close to the users.
Routing traffic over the private AWS backbone minimizes public internet hops, reducing latency and packet loss.
3
Select the optimal configuration to attach the accelerator to the API endpoint.
Associate the Application Load Balancer as an endpoint for the AWS Global Accelerator listener.
This setup allows Global Accelerator to receive TCP/UDP traffic at the edge and route it directly to the ALB.

Anahtar Kavram

AWS Global Accelerator optimizes network paths by routing user traffic through the AWS private network backbone, bypassing the public internet to reduce latency.
Soru 951Soru

An enterprise is running a web application on a fleet of Amazon EC2 instances. The application writes transaction logs to a local file at /var/log/app/production.log. These logs are rotated daily, renamed with a timestamp suffix, and compressed. The solutions architect needs to design a solution that continuously collects these logs, monitors them in real-time for specific error patterns, and archives them to a centralized Amazon S3 bucket in a security account. Which combination of steps should the solutions architect recommend to meet these requirements with the least administrative overhead? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Install the Unified CloudWatch Agent on the EC2 instances, and configure the agent configuration file with /var/log/app/production.log* in the file_path parameter under the logs section.; Create an Amazon Kinesis Data Firehose delivery stream in the application account to deliver logs to the S3 bucket in the security account, and configure a CloudWatch Logs subscription filter to forward the logs to the delivery stream.

Cevap

Configure the Unified CloudWatch Agent with the wildcard pattern /var/log/app/production.log* in the file_path parameter, and stream the logs using a CloudWatch Logs subscription filter to an Amazon Kinesis Data Firehose delivery stream targeting the centralized S3 bucket.
To continuously collect logs and monitor them in real-time, the solutions architect must configure the CloudWatch Agent to capture rotated files and establish a real-time streaming pipeline. Using the wildcard pattern /var/log/app/production.log* in the agent configuration ensures that both the active log file and rotated files are monitored. Utilizing a CloudWatch Logs subscription filter to stream logs to an Amazon Kinesis Data Firehose delivery stream enables real-time cross-account transmission to the centralized Amazon S3 bucket.

Adım Adım Çözüm

1
Configure the CloudWatch agent on the EC2 instances to track the log files using a wildcard suffix.
The agent monitors both /var/log/app/production.log and any rotated files like /var/log/app/production.log.2026-07-16.
Without the wildcard suffix, the agent ceases tracking logs after rotation occurs.
2
Create an Amazon Kinesis Data Firehose delivery stream that points to the centralized S3 bucket in the security account.
A delivery stream is prepared to ingest real-time log data and upload it to the cross-account destination.
Firehose handles cross-account delivery, buffering, and compression with minimal management overhead.
3
Apply a subscription filter to the CloudWatch Logs log group to route logs to the Kinesis Data Firehose delivery stream.
Logs are streamed in real-time as they are ingested by CloudWatch Logs.
This enables both real-time monitoring within CloudWatch Logs (metric filters) and automated archiving to the central bucket.

Anahtar Kavram

Configuring the Unified CloudWatch Agent with wildcard file paths for rotated logs, and streaming logs cross-account using CloudWatch Logs subscription filters and Kinesis Data Firehose.
Soru 952Soru

A media streaming platform runs its transaction processing workload on a fleet of Amazon EC2 instances managed by an Auto Scaling group across multiple AWS accounts in an organization. The application outputs transactional logs to `/var/log/checkout/transaction.log`. These logs are rotated hourly and renamed using the pattern `/var/log/checkout/transaction-YYYY-MM-DD-hh.log`. A Solutions Architect must design a solution to centralize these logs into a dedicated Amazon S3 bucket within a security account. The solution must ensure that log rotation does not interrupt log collection or result in duplicate log entries, and must enforce strict cross-account security controls. Which two of the following actions should the Solutions Architect perform to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the log files collector in the Amazon CloudWatch agent configuration on the EC2 instances to monitor `/var/log/checkout/transaction*.log`, allowing the agent to track file state and process both current and rotated logs without data loss.; In the security account, configure a CloudWatch Logs destination mapping to an Amazon Kinesis Data Firehose delivery stream that targets the central S3 bucket. Apply an access policy to the destination that trusts the member accounts, restricted by the `aws:PrincipalOrgID` condition key.

Cevap

Configuring the log files collector in the CloudWatch agent to monitor with wildcards, and establishing a centralized CloudWatch Logs destination in the security account linked to Kinesis Data Firehose.
To monitor rotated log files without data loss, the CloudWatch agent must be configured with a wildcard pattern so that it tracks the file descriptor even after rotation and renaming. To centralize logs across accounts, CloudWatch Logs subscription filters must route logs to a centralized CloudWatch Logs destination in the security account, which then feeds into Kinesis Data Firehose to write to S3. Restricting this destination using the organization's ID ensures only authorized member accounts can deliver logs.

Adım Adım Çözüm

1
Configure the CloudWatch Agent with wildcards.
The agent tracks file state and handles rotated log files without loss or duplication.
The wildcard pattern ensures renamed log files are continuously processed.
2
Set up a cross-account CloudWatch Logs destination in the central security account.
Member accounts can safely route subscription streams.
CloudWatch Logs subscription filters cannot write directly to cross-account S3 buckets and must target a destination.
3
Apply security policies with organizational restrictions.
The destination policy allows the organization to write to Firehose/S3 while blocking unauthorized access.
Secures log ingestion from only within the organization.

Anahtar Kavram

Centralized, secure cross-account logging with support for log rotation mechanisms.
Soru 953Soru

A government organization is launching a public service portal to process sensitive citizen applications. The architecture uses AWS Organizations and separates workloads into different accounts. A processing application runs on Amazon ECS tasks using AWS Fargate within a processing account (111122223333111122223333). The application must stream and archive finalized application data to an Amazon S3 bucket named `citizen-applications-archive` located in a centralized compliance account (444455556666444455556666). The security architecture must enforce the following security controls: (1) All archived data must be encrypted at rest using a Customer Managed Key (CMK) owned by the compliance account (444455556666444455556666). (2) The ECS tasks in the processing account must be write-only; they must be able to upload archives but must be strictly prevented from decrypting or deleting any archived objects once written. (3) IAM administrators within the processing account (111122223333111122223333) must not be able to bypass the encryption requirements or upload unencrypted data. Which combination of actions must a Solutions Architect perform to design a compliant solution? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: In the compliance account (444455556666444455556666), configure the key policy of the Customer Managed Key (CMK) to grant the ECS task role in the processing account (111122223333111122223333) permissions to perform `kms:GenerateDataKey` and `kms:DescribeKey` actions. In the processing account, attach an IAM policy to the ECS task role that allows these same actions on the CMK.; Attach a Service Control Policy (SCP) to the Organizational Unit (OU) containing the processing account (111122223333111122223333) that denies `s3:PutObject` actions on the target bucket unless the request headers enforce server-side encryption with AWS KMS (`x-amz-server-side-encryption` is set to `aws:kms`) and specify the CMK ARN in the compliance account as the key ID.

Cevap

Configuring the Customer Managed Key policy and the workload's IAM policy to grant `kms:GenerateDataKey` and `kms:DescribeKey` permissions, and attaching an SCP to the processing account's OU to enforce the specific CMK via S3 upload headers.
To write objects to an S3 bucket in a different account using cross-account KMS encryption, the writing principal must have permissions to generate a data key from the destination account's key. This requires configuring the key policy of the Customer Managed Key (CMK) in the compliance account to allow the ECS task role in the processing account to perform `kms:GenerateDataKey` and `kms:DescribeKey`, along with a corresponding IAM policy attached to the ECS task role in the processing account. Furthermore, to prevent local IAM administrators in the processing account from bypassing the compliance controls or uploading unencrypted data, a Service Control Policy (SCP) must be attached to the Organizational Unit (OU) of the processing account. This SCP blocks any `s3:PutObject` actions unless the request headers require server-side encryption with AWS KMS using the specific CMK ARN.

Adım Adım Çözüm

1
Configure the key policy for the Customer Managed Key (CMK) in the compliance account (444455556666444455556666) to allow cross-account operations.
The key policy explicitly permits the ECS task role principal in the processing account (111122223333111122223333) to execute `kms:GenerateDataKey` and `kms:DescribeKey` actions.
Because the KMS key is in a different account than the principal performing the encryption, the resource policy must explicitly delegate trust to the external principal.
2
Grant the ECS task role the necessary KMS and S3 permissions via an IAM policy in the processing account (111122223333111122223333).
The ECS task role is granted `kms:GenerateDataKey` and `kms:DescribeKey` permissions on the compliance account's CMK, and `s3:PutObject` on the destination S3 bucket.
Cross-account access requires explicit permission settings on both sides: the resource policy (KMS key policy) and the user identity policy (IAM policy).
3
Implement write-only controls on the destination S3 bucket in the compliance account (444455556666444455556666).
The S3 bucket policy permits `s3:PutObject` for the processing account's ECS task role, while withholding `s3:GetObject` and `s3:DeleteObject` permissions.
This guarantees that the application can upload the archives but cannot read, decrypt, or delete any data once written.
4
Establish an organization-level Service Control Policy (SCP) to prevent policy evasion by administrators in the processing account.
An SCP attached to the processing account's OU denies `s3:PutObject` calls to the telemetry bucket unless the request uses KMS encryption and specifies the target CMK ARN.
Because local IAM administrators in the workload account can modify IAM configurations, an SCP is required to restrict their ability to upload unencrypted objects or use unauthorized KMS keys.

Anahtar Kavram

Cross-account S3 uploads using a Customer Managed Key (CMK) under organization-level compliance controls.
Soru 954Soru

A financial services firm runs an online transaction processing (OLTP) application using a single Amazon RDS PostgreSQL Multi-AZ DB instance. During peak hours, read-heavy reporting queries cause CPU utilization on the primary instance to reach 100%, degrading write transactions. Which solution should a solutions architect implement to optimize performance and scale read capacity?

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon RDS PostgreSQL Read Replicas and configure the application to route reporting queries to the read replica endpoints.

Cevap

Deploy Amazon RDS PostgreSQL Read Replicas and configure the application to route reporting queries to the read replica endpoints.
Deploying Amazon RDS PostgreSQL Read Replicas is the correct solution. Read replicas are dedicated active instances that replicate data asynchronously from the primary writer. By routing reporting queries to these endpoints, the CPU load on the primary writer is reduced, resolving the performance degradation.

Adım Adım Çözüm

1
Identify the performance bottleneck on the primary DB instance.
The bottleneck is CPU starvation on the primary DB instance caused by read-heavy reporting queries.
Before recommending a scaling action, we must determine if the workload consists of reads or writes.
2
Evaluate the capabilities of the current RDS Multi-AZ deployment.
The standby DB instance is strictly passive and cannot be used for query routing.
Understanding the limits of Multi-AZ prevents incorrect routing architectures.
3
Select the correct AWS compute/storage optimization feature for RDS read capacity.
Amazon RDS Read Replicas provide horizontal scaling of read operations.
Deploying read replicas offloads query executions from the primary node and restores transaction performance.

Anahtar Kavram

Amazon RDS Read Replicas vs Multi-AZ Standby capabilities
Tahmini Süre:45s
Soru 955Soru

A company is designing a new environment on AWS with a single VPC named `Production-VPC` (CIDR: 10.0.0.0/1610.0.0.0/16) to host a web application. The architecture is deployed across two Availability Zones, `us-west-2a` and `us-west-2b`. The public subnets `Public-Subnet-A` (10.0.1.0/2410.0.1.0/24) and `Public-Subnet-B` (10.0.2.0/2410.0.2.0/24) host Application Load Balancers. The application instances are running in the private subnets `Private-Subnet-A` (10.0.10.0/2410.0.10.0/24) and `Private-Subnet-B` (10.0.20.0/2410.0.20.0/24). The instances in the private subnets must be able to securely download software patches from the internet. The design must ensure that an outage of a single Availability Zone does not disrupt outbound internet connectivity for the resources in the remaining active Availability Zone. Which configuration should the solutions architect implement to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy one NAT Gateway in `Public-Subnet-A` and another NAT Gateway in `Public-Subnet-B`. Configure the route table for `Private-Subnet-A` to route outbound traffic (0.0.0.0/00.0.0.0/0) to the NAT Gateway in `Public-Subnet-A`, and configure the route table for `Private-Subnet-B` to route outbound traffic to the NAT Gateway in `Public-Subnet-B`.

Cevap

Deploy one NAT Gateway in each public subnet, and configure the route tables of the corresponding private subnets to route outbound internet traffic to the local NAT Gateway in the same Availability Zone.
The correct configuration is to deploy a dedicated NAT Gateway in the public subnet of each Availability Zone and route outbound traffic from each private subnet to the NAT Gateway in its respective zone. This design ensures that if one Availability Zone experiences an outage, the NAT Gateway in the other zone remains functional, preventing a complete loss of egress connectivity for the remaining healthy zone.

Adım Adım Çözüm

1
Identify the high availability and fault-domain isolation requirement for outbound internet access.
Realize that outbound traffic from private subnets requires NAT Gateways, and relying on a single NAT Gateway introduces an Availability Zone dependency.
Each Availability Zone should operate independently to ensure that a failure in one zone does not affect resources in the other.
2
Select a design that places a NAT Gateway in each Availability Zone's public subnet.
A NAT Gateway is deployed in `Public-Subnet-A` and another in `Public-Subnet-B`.
This establishes redundant egress paths that are physically located in separate physical infrastructure zones.
3
Configure the VPC route tables to align with local Availability Zone routing.
The route table for `Private-Subnet-A` points to the NAT Gateway in `Public-Subnet-A`, and the route table for `Private-Subnet-B` points to the NAT Gateway in `Public-Subnet-B`.
This ensures that traffic does not cross Availability Zones for internet egress under normal operating conditions, isolating the failure domain.

Anahtar Kavram

NAT Gateway redundancy across multiple Availability Zones to ensure highly available internet egress.
Tahmini Süre:1m 0s
Soru 956Soru

A company hosts a public-facing application across two AWS Regions in an active-passive disaster recovery configuration. The primary region (us-east-1) and the secondary region (us-west-2) each have an Application Load Balancer (ALB) that routes traffic to Amazon EC2 instances. The company wants to configure Amazon Route 53 to automatically redirect client traffic to the secondary region if the primary region's application becomes unhealthy.

Which configuration should the solutions architect implement to achieve automatic failover to the secondary region?

Cevabı ve açıklamayı göster

Cevap: Create failover routing records in a Route 53 public hosted zone. Configure the primary record to point to the primary ALB with 'Evaluate Target Health' set to Yes and associate it with a health check that monitors the application's status. Configure the secondary record to point to the secondary ALB.

Cevap

Create failover routing records in a Route 53 public hosted zone, setting 'Evaluate Target Health' to Yes and associating the primary record with an application health check.
The correct configuration uses Route 53 public hosted zones with failover routing records. By setting 'Evaluate Target Health' to Yes and associating the primary record with an application health check, Route 53 can monitor the endpoint's health and failover to the secondary record when the primary endpoint is degraded.

Adım Adım Çözüm

1
Identify the routing policy required for active-passive disaster recovery.
Route 53 failover routing is chosen to direct traffic to a secondary region only when the primary region is unhealthy.
Active-passive failover aligns with the goal of automatic redirecting of traffic upon failure of the primary application.
2
Evaluate the hosted zone type needed for public client traffic.
A public hosted zone is required.
Private hosted zones are only resolvable within VPCs and do not support public internet clients.
3
Determine the health monitoring mechanism for the primary endpoint.
Associate the primary record with a Route 53 health check and enable 'Evaluate Target Health'.
This allows Route 53 to actively monitor the primary ALB and trigger failover when it detects unhealthy target resources.

Anahtar Kavram

Active-Passive Disaster Recovery Failover with Route 53
Tahmini Süre:1m 0s
Soru 957Soru

An enterprise runs a critical web application on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB) in the us-east-1 Region. The database tier uses an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. The company wants to improve their disaster recovery (DR) strategy to achieve a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. The company deploys a standby application tier in us-west-2. During a recent database outage in us-east-1, the application instances remained healthy but could not connect to the database. Because Route 53 was configured to only monitor the ALB endpoint health, DNS failover to us-west-2 did not trigger. Which architectural modification will meet these requirements and automate failover during database degradation?

Cevabı ve açıklamayı göster

Cevap: Implement an application-level health check endpoint (such as `/health`) on the Amazon EC2 instances that queries the Aurora database. Configure a Route 53 active-passive failover routing policy with a Route 53 health check monitoring the primary ALB pointing to the health check endpoint. Create an Amazon CloudWatch Alarm for the health check failure to trigger an AWS Lambda function that invokes the global database failover API to promote the secondary cluster in the recovery Region.

Cevap

Implement an application-level health check endpoint that queries the database, associate it with a Route 53 active-passive failover policy, and trigger an AWS Lambda function via CloudWatch Alarms to perform Aurora global database failover.
The correct answer combines an application-level health check that queries the database with a Route 53 health check. This setup allows Route 53 to detect database connectivity failures and automatically redirect traffic. Additionally, an AWS Lambda function triggered by CloudWatch Alarms automates the Aurora Global Database managed failover, ensuring the secondary database is promoted within the 15-minute RTO and 1-minute RPO boundaries.

Adım Adım Çözüm

1
Expose an application-level health check endpoint (e.g., `/health`) on the EC2 instances that verifies connectivity to the database.
The Application Load Balancer can evaluate the health of the target group based on database connectivity.
To ensure that database degradation propagates to the load balancer and Route 53, rather than only testing HTTP web server responsiveness.
2
Configure a Route 53 health check to monitor the primary Application Load Balancer endpoint targeting the `/health` path, and link it to the Route 53 primary failover record.
Route 53 will automatically fail over DNS routing to the standby region if the primary region's database connectivity is lost.
Route 53 active-passive failover requires an associated health check to dynamically redirect user traffic.
3
Create a CloudWatch Alarm on the Route 53 health check state and configure it to trigger an AWS Lambda function.
The Lambda function is executed automatically upon health check failure.
To automate the failover process of the database tier without manual intervention.
4
Program the Lambda function to invoke the AWS API to perform a managed failover of the Aurora Global Database to the recovery region.
The secondary Aurora cluster in the recovery region is promoted to primary, and the original primary cluster is demoted to secondary.
To achieve the 15-minute RTO and 1-minute RPO by promoting the active replication target without data loss.

Anahtar Kavram

Multi-region automated failover combining Route 53 active-passive failover routing, application-level health checks, and automated Aurora Global Database failover.
Tahmini Süre:2m 0s
Soru 958Soru

An enterprise uses AWS Organizations to manage multiple AWS accounts. The security team needs to improve the security posture of an existing architecture. Specifically, they must address two security findings:

1. Sensitive compliance logs stored in a central Amazon S3 bucket are currently encrypted using the default AWS-managed KMS key (`aws/s3`), which prevents other accounts from decrypting the logs during audits.
2. Developers in member accounts can still configure Amazon S3 buckets to be publicly accessible, violating company policy.

Which two actions should a solutions architect take to resolve these security findings? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Create a customer managed key (CMK) in AWS Key Management Service (AWS KMS) within the central account, update its key policy to allow cross-account access, and use it to encrypt the S3 bucket.; Configure a Service Control Policy (SCP) that denies public S3 bucket access capabilities, such as configuring public bucket policies or public access blocks, and attach it to the member accounts' Organizational Units (OUs).

Cevap

The solutions architect should create a customer managed KMS key in the central account with a key policy configured for cross-account access, and configure a Service Control Policy to deny S3 public access settings on the member accounts' Organizational Units.
Creating a customer managed KMS key allows editing the key policy to grant cross-account decryption access. Attaching an SCP that denies S3 public access block changes effectively prevents developers in member accounts from bypassing security configurations.

Adım Adım Çözüm

1
Analyze the KMS key restriction.
Realize that default AWS-managed keys cannot be shared cross-account because their key policies are unmodifiable.
This establishes the need for a customer managed key.
2
Analyze the restriction on S3 public access.
Realize that Service Control Policies can block actions like configuring public access blocks globally across member OUs.
This enforces organizational compliance rules.
3
Verify correct permissions mechanics for SCPs.
Ensure SCPs are used as guardrails (denying actions) rather than trying to grant positive permissions directly.
SCPs can only restrict permissions, not grant them.

Anahtar Kavram

Cross-account KMS sharing and enforcing resource access boundaries with Service Control Policies.
Soru 959Soru

An enterprise runs a critical containerized business API across two AWS accounts in an AWS Organization. The production environment is deployed in Account A within a VPC in the us-west-2 Region. The API runs on Amazon ECS tasks on AWS Fargate behind an Application Load Balancer (ALB). The data layer uses an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-west-2 (Account A) and a secondary cluster in us-east-1 (Account B). A Route 53 Private Hosted Zone (PHZ) for api.internal is hosted in Account A and associated with the production VPC to allow internal services to resolve the backend API. The enterprise wants to establish a disaster recovery (DR) environment in us-east-1 (Account B) using a warm standby pattern to achieve an RTO of less than 15 minutes and an RPO of less than 1 minute. The DR environment must also run on ECS Fargate behind an ALB. The Fargate tasks in the DR environment require highly reliable outbound internet access to communicate with third-party payment gateways. Additionally, internal microservices in the DR environment must be able to resolve api.internal to the local DR load balancer during a failover. Which solution meets these requirements while adhering to AWS high availability and disaster recovery best practices?

Cevabı ve açıklamayı göster

Cevap: Promote the Aurora secondary cluster in us-east-1 to primary. Associate the Account A Private Hosted Zone for api.internal with Account B's VPC in us-east-1 using cross-account authorization and association. In Account B, configure a local ALB, create a Route 53 failover record for api.internal pointing to the local ALB, and associate it with a Route 53 health check based on a CloudWatch metric alarm that monitors ALB target health. Deploy NAT Gateways in each Availability Zone of Account B's VPC in us-east-1 to provide redundant outbound connectivity.

Cevap

Promote the Aurora secondary cluster in us-east-1 to primary. Associate the Account A Private Hosted Zone for api.internal with Account B's VPC in us-east-1 using cross-account authorization and association. In Account B, configure a local ALB, create a Route 53 failover record for api.internal pointing to the local ALB, and associate it with a Route 53 health check based on a CloudWatch metric alarm that monitors ALB target health. Deploy NAT Gateways in each Availability Zone of Account B's VPC in us-east-1 to provide redundant outbound connectivity.
The correct solution involves promoting the secondary Aurora cluster to primary, which meets the low RTO/RPO requirements. Since Private Hosted Zones (PHZs) are not automatically shared across accounts, a cross-account VPC association must be authorized and associated. To ensure automatic failover, the Route 53 failover record must be associated with health checks (e.g., via CloudWatch alarms for internal ALBs). Finally, NAT Gateways must be deployed in each Availability Zone to maintain outbound network reliability and prevent a single point of failure.

Adım Adım Çözüm

1
Promote the Aurora secondary cluster in the secondary region to act as the primary database, satisfying the low RTO and RPO objectives.
The database tier is failed over with near-zero data loss.
Aurora Global Database allows fast database failover to a secondary region.
2
Use the AWS CLI or API to authorize cross-account association from Account A for the PHZ api.internal, and then associate it with the VPC in Account B.
Account B's VPC can resolve DNS queries for the api.internal hosted zone.
Private Hosted Zones must be explicitly associated cross-account to allow DNS resolution in another account's VPC.
3
Create a Route 53 failover record for api.internal in Account B pointing to the local ALB, and configure a health check using a CloudWatch metric alarm that tracks the ALB target health.
Route 53 will dynamically direct internal queries to the active load balancer based on health.
Route 53 failover records require an associated health check to perform automatic failover when endpoints degrade.
4
Deploy one NAT Gateway per Availability Zone in Account B's VPC and configure the route tables of each zone's private subnets to point to their respective local NAT Gateway.
Highly available outbound internet connectivity is established for Fargate tasks in the DR region.
Deploying a NAT Gateway in each Availability Zone removes single points of failure for outbound traffic.

Anahtar Kavram

Multi-region disaster recovery architecture requiring cross-account DNS hosted zone association, automatic DNS failover via health checks, and redundant outbound network gateways.
Tahmini Süre:3m 0s
Soru 960Soru

An enterprise runs a high-throughput, latency-sensitive SaaS platform across three AWS accounts in the useast1us-east-1 Region: a Production account, a Data Analytics account, and a Shared Services account. The Production VPC and Data Analytics VPC need to query a centralized, high-performance Amazon ElastiCache cluster hosted in the Shared Services VPC.

Currently, all VPCs are interconnected using an AWS Transit Gateway, but the application teams are reporting latency overhead and high network data processing costs. In addition, applications in the Production and Data Analytics VPCs are experiencing DNS resolution failures when attempting to resolve the cache cluster's domain name, which is managed via a Route 53 Private Hosted Zone (cache.internalcache.internal) created in the Shared Services account.

Which of the following actions should the Solutions Architect take to optimize network performance, minimize latency, and resolve the DNS issues? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Establish direct VPC Peering connections between the Shared Services VPC and the other two VPCs, and update the route tables to route traffic directly over the peered connections.; Authorize the Route 53 Private Hosted Zone association from the Shared Services account, and associate the private hosted zone with both the Production VPC and the Data Analytics VPC.

Cevap

To optimize network performance, minimize latency, and resolve the DNS issues, the Solutions Architect should establish direct VPC Peering connections between the Shared Services VPC and the other two VPCs, and authorize the association of the Route 53 Private Hosted Zone from the Shared Services account to associate it directly with both the Production VPC and the Data Analytics VPC.
Establishing direct VPC Peering connections provides the lowest latency and highest throughput without Transit Gateway hop overhead or processing fees. Authorizing and associating the Route 53 Private Hosted Zone across accounts allows native, local DNS resolution for the cache cluster without expensive and high-latency endpoints.

Adım Adım Çözüm

1
Replace the Transit Gateway routing path with direct VPC Peering connections between the Shared Services VPC and both the Production and Data Analytics VPCs, then update the VPC route tables.
Traffic between the application servers and the ElastiCache cluster bypasses the Transit Gateway, eliminating the extra gateway hop and Transit Gateway processing fees.
VPC Peering provides direct, unconstrained network pathways within the AWS global network, yielding the lowest possible latency and highest throughput.
2
Authorize the association of the Route 53 Private Hosted Zone in the Shared Services account with the Production VPC and Data Analytics VPC, and associate them.
The Route 53 Resolvers in the Production and Data Analytics VPCs can resolve queries for the caching domain directly and locally.
Direct Private Hosted Zone association resolves DNS queries natively within the VPCs, bypassing the cost, complexity, and latency of Resolver endpoints.

Anahtar Kavram

Optimizing multi-account network latency and DNS resolution using VPC Peering and cross-account Private Hosted Zone association.
Tahmini Süre:3m 0s
ÖncekiSayfa 48 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin