Tüm alıştırma soruları

1964 soru

Soru 201Soru

A financial services company is designing a disaster recovery (DR) solution for a critical transaction processing application. The primary infrastructure is deployed in the `us-east-1` Region, using Amazon EC2 instances in private subnets across three Availability Zones (AZs) and an Amazon Aurora PostgreSQL database. The application must remain highly available within the primary Region and resilient to regional failures. The DR solution in the `us-west-2` Region must achieve a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. The company wants to minimize ongoing running costs for the DR environment.

Which of the following architectures meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy a NAT Gateway in each public subnet in the primary Region. Set up an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary read-only cluster in `us-west-2`. Deploy a scaled-down Auto Scaling group of EC2 instances behind an Application Load Balancer (ALB) in `us-west-2`. Configure Route 53 Failover routing records with health checks, directing traffic to the primary ALB under normal conditions and to the secondary ALB during a failover.

Cevap

The correct architecture deploys a NAT Gateway per Availability Zone in the primary Region for high availability, sets up Amazon Aurora Global Database for sub-minute RPO cross-region replication, runs a scaled-down Auto Scaling group in the secondary Region to minimize costs, and routes traffic via Route 53 Failover routing records with health checks.
The correct architecture uses redundant NAT Gateways (one per Availability Zone) in the primary Region to ensure that a single AZ failure does not disrupt outbound internet access for the EC2 instances in private subnets. To satisfy the low RTO of 15 minutes and RPO of 1 minute, Amazon Aurora Global Database is used to continuously replicate data from the primary to the secondary Region with typical replication latency of under one second. Deploying a scaled-down Auto Scaling group in the secondary Region represents a Warm Standby disaster recovery strategy, which minimizes ongoing compute costs while allowing rapid scale-up. Route 53 Failover routing automatically shifts public traffic to the secondary Application Load Balancer if the primary Region endpoints become unhealthy.

Adım Adım Çözüm

1
Evaluate high availability requirements in the primary Region.
Identify that outbound internet traffic from private subnets requires a NAT Gateway. Deploying a NAT Gateway in each Availability Zone eliminates the single point of failure.
Ensures that an outage in one Availability Zone does not impact outbound traffic in other Availability Zones.
2
Evaluate RPO and RTO requirements for the disaster recovery Region.
Select Amazon Aurora Global Database to achieve cross-region replication latency of under 1 second, meeting the 1-minute RPO.
Snapshot-based backup replication cannot meet sub-minute RPO requirements.
3
Address cost minimization for the DR environment.
Propose a Warm Standby setup with a scaled-down Auto Scaling group of EC2 instances in the secondary Region.
Allows the instances to be provisioned and scale up rapidly upon promotion, keeping active compute costs low during normal operations.
4
Configure DNS routing for global failover.
Implement Route 53 Failover routing records associated with application health checks.
Ensures automated or rapid manual redirection of public traffic to the secondary ALB when the primary Region endpoints fail.

Anahtar Kavram

High Availability and Disaster Recovery Design
Tahmini Süre:2m 0s
Soru 202Soru

A software-as-a-service (SaaS) company is designing a highly available, multi-region web application on AWS with a primary deployment in us-east-1 and a disaster recovery (DR) site in us-west-2. The application relies on an Amazon Aurora MySQL database and must communicate with external payment APIs. The business requirements specify a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 22 minutes. The design must ensure high availability within each Region and minimize single points of failure. Which two actions should a solutions architect take to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Create an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, utilizing storage-based physical replication.; Deploy a NAT Gateway in each Availability Zone's public subnet within both Regions, and configure the route tables of the private subnets in each Availability Zone to route outbound traffic through their respective local NAT Gateway.

Cevap

Create an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, and deploy a NAT Gateway in each Availability Zone's public subnet within both Regions, configuring the private route tables accordingly.
Implementing an Amazon Aurora Global Database meets the RPO of 22 minutes because its storage-based cross-region replication lag is typically under a second, and a failover can be completed quickly to meet the RTO. Deploying a NAT Gateway in each public subnet per Availability Zone ensures outbound high availability, preventing a single Availability Zone outage from dropping all outbound connections.

Adım Adım Çözüm

1
Evaluate the database tier against the RTO of 1515 minutes and RPO of 22 minutes.
Identify that cross-region storage replication via Amazon Aurora Global Database is required to keep replication lag under a second, meeting the RPO, and allowing rapid failover within the RTO.
Traditional snapshot copies or standard backup restorations take too long and result in too much data loss to satisfy the RTO and RPO requirements.
2
Design the outbound connectivity architecture for external API access.
Deploy a NAT Gateway in each Availability Zone's public subnet and point local private subnets to their respective zone's gateway.
A single NAT Gateway per Region creates a single point of failure. Redundant NAT Gateways ensure high availability in the event of an Availability Zone outage.

Anahtar Kavram

Designing multi-region disaster recovery using Amazon Aurora Global Database while ensuring local Availability Zone redundancy for network address translation.
Soru 203Soru

A digital publishing company is designing a disaster recovery (DR) architecture for its high-traffic content management application. The primary database is an Amazon RDS for PostgreSQL instance. The application tier runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The business requirements specify a Recovery Time Objective (RTO) of less than 1515 minutes and a Recovery Point Objective (RPO) of less than 55 minutes. Additionally, the secondary database must be capable of serving read-only search queries to local users in the secondary region during normal operations to offload read traffic. The solution must also support internal service discovery using a Route 53 Private Hosted Zone (PHZ). Which two actions should the solutions architect take to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Create a cross-region read replica of the RDS for PostgreSQL instance in the secondary region. Configure the local search application in the secondary region to query this replica for read-only traffic, and promote it to a standalone primary instance during a failover.; Configure Amazon Route 53 with a Failover routing policy. Point the primary record to the primary ALB and the secondary record to an ALB in the secondary region, where an Auto Scaling group is pre-deployed with a minimum capacity of 11 instance to process local read-only traffic.

Cevap

Create a cross-region read replica of the RDS for PostgreSQL instance, and configure Amazon Route 53 with a Failover routing policy pointing to a pre-deployed standby ALB with an Auto Scaling group in the secondary region.
The correct solution uses an Amazon RDS cross-region read replica, which provides asynchronous database replication with low lag (meeting the 55-minute RPO) and supports active read queries from local applications. For the application tier, configuring Route 53 Failover routing health-checked against the primary ALB allows automated traffic redirection to the secondary region. Pre-deploying the Auto Scaling group with a minimum capacity of 11 instance ensures the standby resources are online to serve local search queries and can scale out immediately during failover, satisfying the 1515-minute RTO constraint.

Adım Adım Çözüm

1
Establish database replication to satisfy RPO and read-only traffic requirements.
A cross-region Amazon RDS Read Replica is created in the secondary region, which replicates data asynchronously under 55 minutes and can be queried directly.
RDS Read Replicas support cross-region asynchronous replication with low lag and support active read workloads, satisfying both the RPO and the local query requirement.
2
Configure public routing and compute resources for disaster recovery.
Route 53 Failover routing redirects traffic to the secondary ALB, where an Auto Scaling group with a minimum capacity of 11 instance is pre-deployed.
A warm standby configuration with a scaled-down application tier ensures the secondary site is online to serve local read-only traffic and can quickly scale out to meet the 1515-minute RTO during failover.
3
Ensure internal DNS resolution is functional across regions.
The Route 53 Private Hosted Zone created in the primary VPC is associated with the secondary VPC.
Private Hosted Zones must be explicitly associated with each VPC that needs to resolve its records, as network connectivity alone does not enable DNS resolution.

Anahtar Kavram

Designing a multi-region active-passive disaster recovery architecture using RDS cross-region read replicas and Route 53 failover routing policies, while ensuring proper VPC DNS association and multi-AZ NAT redundancy.
Soru 204Soru

A global automotive manufacturer is designing a new critical parts tracking system on AWS. The application will be deployed across two AWS Regions: us-east-1 as the primary active region and us-west-2 for disaster recovery. The business requires a Recovery Time Objective (RTO) of 10 minutes and a Recovery Point Objective (RPO) of 5 minutes. The database tier must support cross-region replication, and the network design must ensure outbound internet connectivity remains highly available even if an entire Availability Zone experiences an outage. External client traffic must automatically fail over to the secondary region if the primary region's endpoints become degraded. Which architecture meets these requirements while minimizing cost and operational complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy Application Load Balancers (ALBs) in both regions behind Amazon Route 53 failover routing records with active health checks. Deploy NAT Gateways in each Availability Zone within the private subnets of both regions' VPCs.

Cevap

Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy Application Load Balancers (ALBs) in both regions behind Amazon Route 53 failover routing records with active health checks. Deploy NAT Gateways in each Availability Zone within the private subnets of both regions' VPCs.
The correct solution uses Amazon Aurora Global Database, which offers a typical replication latency of less than one second, easily satisfying the 5-minute RPO requirement, and can be promoted to a standalone read-write cluster in under a minute to satisfy the 10-minute RTO. Route 53 failover routing automatically redirects traffic to the secondary region's Application Load Balancer when health checks fail. Outbound internet redundancy is preserved by deploying NAT Gateways in each Availability Zone, preventing outbound connection failures if a single Availability Zone goes offline.

Adım Adım Çözüm

1
Evaluate the database tier requirements against the target RTO (10 minutes) and RPO (5 minutes).
An Amazon Aurora Global Database is selected because it replicates data across regions in under 1 second (meeting the 5-minute RPO) and can be promoted to a primary cluster in under 1 minute (meeting the 10-minute RTO).
Standard cross-region replication or backup-and-restore patterns do not reliably guarantee the tight RTO and RPO limits under load.
2
Assess regional routing failover and health checking requirements.
Configure Amazon Route 53 failover routing records pointing to Application Load Balancers in both regions, backed by active health checks.
This configuration automatically detects primary region endpoint degradation and diverts traffic to the secondary region without manual intervention.
3
Design outbound NAT connectivity to ensure no single point of failure during an Availability Zone outage.
Deploy NAT Gateways in each Availability Zone within the private subnets of the VPCs.
Deploying a NAT Gateway in each Availability Zone ensures that if one AZ fails, resources in the remaining AZs can still access the internet through their respective local gateways.

Anahtar Kavram

Multi-region disaster recovery design using Amazon Aurora Global Database, Route 53 failover routing, and redundant NAT Gateways to satisfy stringent RTO/RPO and high availability requirements.
Soru 205Soru

A municipal smart-grid utility provider is launching a new smart-meter data ingestion system on AWS. The system's primary workload runs in the us-east-1 Region, and the company requires a disaster recovery (DR) solution in the us-west-2 Region. The application requires outbound internet access from its private subnets to register meters. The database tier uses Amazon Aurora PostgreSQL. The business requires a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. Which design meets these objectives with the lowest cost and operational complexity while maintaining high availability in the primary region?

Cevabı ve açıklamayı göster

Cevap: Configure Amazon Aurora Global Database to replicate data from us-east-1 to us-west-2. Deploy the application servers in both Regions using Auto Scaling groups, keeping the us-west-2 group scaled to a minimum capacity of one instance as a warm standby. Deploy a NAT Gateway in each Availability Zone within us-east-1 for outbound internet access. Configure Amazon Route 53 with a failover routing policy and health checks to route traffic to the secondary Region if the primary Region becomes unhealthy.

Cevap

Configure Amazon Aurora Global Database for database replication, run the secondary application tier in a warm standby state with a minimum capacity of one instance, deploy redundant NAT Gateways across Availability Zones in the primary region, and use Route 53 failover routing policy with health checks.
The correct option satisfies the 5-minute RPO using Amazon Aurora Global Database, which offers sub-second cross-region replication. It satisfies the 15-minute RTO by utilizing a warm standby strategy with at least one active instance in the secondary region's Auto Scaling group, allowing the application tier to scale up rapidly during failover. By placing NAT Gateways in each Availability Zone of the primary region, it avoids a single point of failure for outbound traffic. Using Route 53 failover routing policy allows the system to automatically redirect DNS requests to the secondary region if the primary region's ALB health checks fail.

Adım Adım Çözüm

1
Analyze RTO and RPO requirements.
Identify that the 5-minute RPO rules out backup/restore methods with longer intervals, and the 15-minute RTO requires pre-existing database replication (like Aurora Global Database) and a fast application recovery strategy (like Warm Standby).
This establishes the baseline DR strategy that can meet the recovery objectives.
2
Evaluate high availability requirements for the primary region.
Determine that outbound internet connectivity must be highly available, requiring redundant NAT Gateways across multiple Availability Zones in the primary region.
A single NAT Gateway creates a single point of failure, violating high availability principles.
3
Select the correct database and routing configuration.
Choose Aurora Global Database for sub-second cross-region replication, and Route 53 with failover routing policies linked to health checks to manage external traffic redirection.
This ensures the database meets the RPO and DNS failover is automated and reliable.

Anahtar Kavram

High Availability and Disaster Recovery Design
Tahmini Süre:2m 0s
Soru 206Soru

A retail company manages a multi-account AWS environment with ten spoke VPCs connected to a central AWS Transit Gateway in the us-east-1 Region. The VPCs are split into six Production spoke VPCs and four Development spoke VPCs. The company's security policy requires that Production VPCs must be able to communicate with each other, and Development VPCs must be able to communicate with each other. However, any traffic between Production and Development VPCs must be completely blocked. Additionally, all ten spoke VPCs must have access to a Shared Services VPC that hosts centralized security monitoring and scanning tools. Which two Transit Gateway routing configurations should the Solutions Architect implement 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: Create three separate Transit Gateway route tables: one for Production VPCs, one for Development VPCs, and one for the Shared Services VPC. Associate the Production spoke VPC attachments with the Production route table, and the Development spoke VPC attachments with the Development route table.; Associate the Shared Services VPC attachment with the Shared Services route table. Propagate the Shared Services VPC attachment to both the Production and Development route tables, and propagate all Production and Development VPC attachments to the Shared Services route table.

Cevap

Create three separate Transit Gateway route tables for Production, Development, and Shared Services. Associate the spoke VPCs with their respective environment route tables, and associate the Shared Services VPC with its own route table. Propagate the Shared Services VPC attachment to both the Production and Development route tables, and propagate all spoke VPC attachments to the Shared Services route table.
To achieve isolation between Production and Development VPCs while allowing both to communicate with a Shared Services VPC, three Transit Gateway route tables must be utilized. Associating the Production spoke VPCs with a Production route table and Development spoke VPCs with a Development route table prevents them from routing traffic to each other because neither route table contains routes to the other's CIDR blocks. Propagating the Shared Services VPC attachment to both the Production and Development route tables allows the spoke VPCs to find a route to Shared Services. Finally, propagating all spoke VPC attachments to the Shared Services route table allows the Shared Services VPC to route return traffic back to the appropriate spoke VPCs.

Adım Adım Çözüm

1
Determine the boundary requirements for network traffic.
Production and Development spoke VPCs must be isolated from one another, but both groups must communicate within their own environment and access the Shared Services VPC.
This establishes the routing isolation domains required on the AWS Transit Gateway.
2
Define route table associations.
Three Transit Gateway route tables are created. Production VPC attachments associate with the Production route table, Development VPC attachments associate with the Development route table, and the Shared Services VPC attachment associates with the Shared Services route table.
VPC associations dictate which route table is used for traffic originating from that VPC.
3
Define route propagations.
Propagate Production attachments to the Production route table, and Development attachments to the Development route table. Propagate the Shared Services attachment to both Production and Development route tables. Propagate all spoke attachments to the Shared Services route table.
Propagations dynamically populate route tables. This allows internal environment communication, access to the Shared Services VPC, and correct return routing from the Shared Services VPC while keeping Production and Development isolated.

Anahtar Kavram

AWS Transit Gateway Route Table Associations and Propagations for Network Isolation
Tahmini Süre:2m 0s
Soru 207Soru

A retail company is launching a new serverless microservice using AWS Lambda and Amazon API Gateway. To minimize deployment risk for new updates, a solutions architect must design a deployment strategy that routes 10%10\% of API traffic to the new version of the Lambda function. The strategy must monitor the deployment for a period of 1515 minutes using Amazon CloudWatch alarms, and automatically roll back to the previous version within seconds if errors are detected. If no errors are detected, the remaining traffic must be routed to the new version. Which deployment strategy and configuration meets these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Deploy the updates using AWS CodeDeploy with the CodeDeployDefault.LambdaCanary10Percent15Minutes deployment configuration, and configure CloudWatch alarms to monitor Lambda execution errors for automatic rollback.

Cevap

Deploy the updates using AWS CodeDeploy with the CodeDeployDefault.LambdaCanary10Percent15Minutes deployment configuration, and configure CloudWatch alarms to monitor Lambda execution errors for automatic rollback.
The correct option is to use AWS CodeDeploy with the canary configuration because it natively implements the two-phase traffic-shifting pattern. It routes 10%10\% of traffic to the new version of the Lambda function (via alias weights), monitors for 1515 minutes, and uses CloudWatch alarms to perform a rapid rollback if errors are detected. This is a fully managed, configuration-driven approach with the lowest operational complexity.

Adım Adım Çözüm

1
Identify the traffic-shifting pattern requirements.
The requirement specifies routing 10%10\% of traffic to the new version initially, holding it for 1515 minutes, and then promoting the rest. This represents a canary deployment pattern, not a linear pattern.
Choosing the correct deployment pattern (canary vs. linear) ensures that the traffic shifting matches the business requirements.
2
Select the appropriate pre-defined AWS CodeDeploy deployment configuration.
The pre-defined configuration `CodeDeployDefault.LambdaCanary10Percent15Minutes` maps directly to the requirement of routing 10%10\% of traffic to the new Lambda version for 1515 minutes.
Using a native CodeDeploy configuration minimizes custom development and operational overhead.
3
Configure the automated rollback mechanism.
Associate CloudWatch alarms monitoring Lambda execution errors with the CodeDeploy deployment group.
If the alarm is triggered during the 1515-minute canary period, CodeDeploy immediately shifts 100%100\% of traffic back to the original stable version, satisfying the rollback requirement within seconds.

Anahtar Kavram

AWS CodeDeploy Canary Deployments for Lambda
Soru 208Soru

A company needs to migrate 500 TB500\text{ TB} of historical data from an on-premises NFS file system to Amazon S3. The initial migration must be completed within 30 days. After the initial migration, the company needs to replicate daily incremental updates of approximately 50 GB50\text{ GB} from the same NFS file system to Amazon S3. The company has a dedicated 100 Mbps100\text{ Mbps} internet connection available for this migration. Security policies require that all data at rest in Amazon S3 be encrypted using a Customer Managed Key (CMK) in AWS KMS, and the migration process must minimize administrative overhead. Which two actions should a Solutions Architect recommend to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Order multiple AWS Snowball Edge Storage Optimized devices, copy the initial 500 TB500\text{ TB} dataset locally to the devices, and ship them to AWS to import the data into the Amazon S3 bucket.; Deploy an AWS DataSync agent on-premises, configure the source location as the NFS file system and the destination location as the Amazon S3 bucket, and schedule a daily task to replicate the 50 GB50\text{ GB} incremental updates.

Cevap

Order multiple AWS Snowball Edge Storage Optimized devices to import the initial 500 TB dataset into the Amazon S3 bucket, and deploy an AWS DataSync agent on-premises to sync the daily 50 GB incremental updates to Amazon S3.
Using multiple AWS Snowball Edge Storage Optimized devices for the initial transfer is correct because copying the data locally and shipping it physically bypasses the 100 Mbps network constraint, which would otherwise take over a year. Deploying AWS DataSync on-premises is correct because it provides an automated, managed mechanism to sync the daily 50 GB updates over the network link in about 1 hour with minimal administration.

Adım Adım Çözüm

1
Calculate the transfer duration for the initial 500 TB dataset over the 100 Mbps network connection.
Transferring 500 TB at 100 Mbps takes approximately 463 days (500×1012 bytes×8 bits/byte/108 bps=4×107 seconds500 \times 10^{12} \text{ bytes} \times 8 \text{ bits/byte} / 10^8 \text{ bps} = 4 \times 10^7 \text{ seconds}), which is far greater than the 30-day requirement. Therefore, an offline physical transfer (Snowball Edge) is required.
To determine whether the network bandwidth can support the initial migration within the specified timeline.
2
Calculate the transfer duration for the daily 50 GB incremental updates over the 100 Mbps network connection.
Transferring 50 GB at 100 Mbps takes approximately 1.1 hours (50×109 bytes×8 bits/byte/108 bps=4000 seconds50 \times 10^9 \text{ bytes} \times 8 \text{ bits/byte} / 10^8 \text{ bps} = 4000 \text{ seconds}), which easily fits into a daily maintenance window.
To determine whether the daily updates can be replicated over the network.
3
Select the correct AWS services that automate network replication and satisfy key-management compliance.
AWS DataSync is selected for the daily replication because it natively handles incremental synchronization with minimal administrative overhead. A Customer Managed Key (CMK) is required because AWS Snowball Edge import jobs cannot use AWS-managed keys.
To align the migration strategy with compliance and overhead minimization requirements.

Anahtar Kavram

Selecting data transfer strategies requires balancing network bandwidth constraints against data volume and timelines (the online vs. offline decision matrix). For initial bulk migrations where network transfer time exceeds the timeline, offline shipping with AWS Snowball Edge is required. For ongoing incremental updates that fit within the available network capacity, automated replication via AWS DataSync minimizes operational overhead. Additionally, AWS Snowball Edge require Customer Managed KMS keys (CMKs) rather than AWS-managed keys to allow custom policy delegation.
Soru 209Soru

A metropolitan transit authority is launching a digital boarding verification system across its entire rail network. The system processes QR code passenger scans from 300,000300,000 active turnstiles. During morning rush hour, boarding verification requests surge from a baseline of 2,0002,000 requests per second to a peak of 120,000120,000 requests per second within 45 seconds45\text{ seconds}. The system must validate passenger ticket balances, update transit logs, and return boarding decisions with sub-millisecond database read response times to prevent passenger queues.

Which architecture scales to meet this sudden workload surge while maintaining performance and operational efficiency?

Cevabı ve açıklamayı göster

Cevap: Deploy a Network Load Balancer (NLB) to distribute the verification requests to an Amazon ECS service running on AWS Fargate. Store ticket and balance information in an Amazon Aurora PostgreSQL DB cluster. Configure Aurora Auto Scaling to dynamically scale the number of Aurora Replicas, and route the boarding validation read queries to the DB cluster's reader endpoint.

Cevap

Deploy a Network Load Balancer (NLB) to distribute the verification requests to an Amazon ECS service running on AWS Fargate. Store ticket and balance information in an Amazon Aurora PostgreSQL DB cluster. Configure Aurora Auto Scaling to dynamically scale the number of Aurora Replicas, and route the boarding validation read queries to the DB cluster's reader endpoint.
The correct architecture uses a Network Load Balancer (NLB) to handle the sudden, extreme traffic spike without requiring pre-warming, routing requests to Amazon ECS tasks. On the database tier, it stores data in Amazon Aurora PostgreSQL and uses Aurora Auto Scaling to dynamically provision read replicas, routing read traffic to the reader endpoint. This scales the read workload efficiently while maintaining low latency.

Adım Adım Çözüm

1
Analyze load balancer scaling requirements.
Identify that the system must scale from a baseline of 2,0002,000 requests per second to 120,000120,000 requests per second in 45 seconds45\text{ seconds}.
An Application Load Balancer (ALB) cannot scale this fast natively without pre-warming, leading to dropped requests. A Network Load Balancer (NLB) is required to handle sudden, extreme traffic spikes.
2
Evaluate database horizontal scaling limitations for RDS.
Determine that Amazon RDS Multi-AZ deployments use a passive standby instance.
The standby instance in an RDS Multi-AZ configuration only serves as a failover target and does not accept read connections, making it unable to scale query throughput.
3
Evaluate Amazon Aurora read scaling mechanisms.
Leverage Amazon Aurora Auto Scaling with Aurora Replicas.
Amazon Aurora can dynamically add replicas to handle spikes in read queries, and routes traffic through the reader endpoint, solving the database read bottleneck.

Anahtar Kavram

Handling sudden traffic bursts at the entry tier using Network Load Balancers (NLB) and scaling the database read capacity using Amazon Aurora Replicas behind a reader endpoint.
Tahmini Süre:3m 0s
Soru 210Soru

A global logistics and fleet tracking platform is designing a new multi-region disaster recovery (DR) and high availability architecture for its core routing and dispatch system. The application is deployed across eu-west-1 (Primary) and eu-central-1 (Secondary). The business requires a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 1 minute.

The application layer consists of containerized microservices running on Amazon ECS on Fargate in private subnets. These microservices must make outbound API calls to external traffic mapping services, which must remain highly available even if an entire Availability Zone (AZ) in the active region experiences an outage. The database layer uses Amazon Aurora PostgreSQL. For internal service discovery, the microservices use a Route 53 Private Hosted Zone.

Which of the following architectures meets these requirements with the lowest operational complexity?

Cevabı ve açıklamayı göster

Cevap: Configure Amazon Aurora Global Database with the primary cluster in eu-west-1 and a secondary cluster in eu-central-1. Deploy the ECS tasks across three Availability Zones in both regions, and deploy a NAT Gateway in each Availability Zone of the VPCs. Configure Route 53 with Failover routing policies, creating a primary record pointing to the Application Load Balancer (ALB) in eu-west-1 and a secondary record pointing to the ALB in eu-central-1, both associated with Route 53 active application health checks. Associate the Route 53 Private Hosted Zone with the VPCs in both regions.

Cevap

Configure Amazon Aurora Global Database across the primary and secondary regions, deploy a NAT Gateway in each Availability Zone for private subnet outbound connectivity, use Route 53 Failover routing policies with active health checks to manage region failover, and associate the Route 53 Private Hosted Zone with the VPCs in both regions.
The correct architecture leverages Amazon Aurora Global Database for sub-second cross-region replication, complying with the RPO of under 1 minute. Redundant NAT Gateways across all Availability Zones ensure outbound connectivity survives a single zone outage. Route 53 active health checks combined with Failover routing records automatically redirect traffic during an outage, meeting the RTO of under 15 minutes. Associating the Private Hosted Zone with both VPCs ensures service discovery remains functional in both regions.

Adım Adım Çözüm

1
Select a database replication mechanism that meets the RPO.
Amazon Aurora Global Database provides typical replication latency of less than 1 second, meeting the RPO of less than 1 minute.
Standard snapshot replication or cross-region backups are insufficient to meet an RPO under 1 minute.
2
Design highly available outbound network paths for the application tier.
Deploying a NAT Gateway in each Availability Zone ensures that ECS Fargate tasks in remaining zones retain outbound internet access if one zone fails.
A single NAT Gateway creates a single point of failure for outbound traffic across all Availability Zones.
3
Configure internal DNS resolution for the multi-region environment.
Associate the Route 53 Private Hosted Zone with both the primary and secondary VPCs.
If the Private Hosted Zone is not associated with the secondary VPC, the application will experience internal resolution failures during DR failover.
4
Implement automatic external client redirection.
Configure Route 53 Failover routing records for the primary and secondary Application Load Balancers with health checks.
Failover routing automatically shifts public traffic when health checks fail, keeping the recovery process within the 15-minute RTO.

Anahtar Kavram

Multi-region high availability and disaster recovery design using Route 53, Aurora Global Database, redundant NAT Gateways, and cross-VPC Private Hosted Zone associations.
Soru 211Soru

A company is designing a high-throughput event processing platform to ingest JSON telemetry logs from 50,00050,000 IoT devices. The platform must support two primary requirements:

1. Low-latency, single-digit millisecond writes to ingest telemetry logs, which must be stored for real-time dashboarding. The telemetry data must automatically expire after 3030 days to minimize storage costs.
2. An audit compliance mandate requires raw logs to be archived for 77 years. These archives must be queryable via standard SQL on-demand, without provisioning permanent database compute resources.

Which two database and storage strategies will satisfy these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Use Amazon DynamoDB to ingest and store the active telemetry logs, and enable Time to Live (TTL) to automatically delete items older than 3030 days.; Use Amazon S3 to store the raw logs, configure an S3 Lifecycle policy to transition the logs to Amazon S3 Glacier Flexible Retrieval after 3030 days, and query the archived logs on-demand using Amazon Athena.

Cevap

Use Amazon DynamoDB to ingest and store active logs with Time to Live (TTL) enabled, and use Amazon S3 to archive raw logs with an S3 Lifecycle policy transitioning them to Amazon S3 Glacier Flexible Retrieval while querying them via Amazon Athena.
The correct strategy uses Amazon DynamoDB to handle the high-write, low-latency telemetry ingestion, utilizing Time to Live (TTL) to automatically expire data after 3030 days at no extra cost. For long-term archiving, Amazon S3 coupled with a Lifecycle policy to transition logs to S3 Glacier Flexible Retrieval offers the most cost-effective solution, while Amazon Athena allows serverless, on-demand SQL queries without the need for active database compute resources.

Adım Adım Çözüm

1
Evaluate the requirements for active telemetry storage.
The active store must handle high-throughput, low-latency writes and automatically delete items after 3030 days.
Amazon DynamoDB is selected because it scales horizontally to support high write throughput with single-digit millisecond latency, and offers built-in TTL to automatically expire data at no additional cost.
2
Evaluate the requirements for long-term archiving and auditing.
Raw logs must be stored cost-effectively for 77 years and remain queryable via SQL on-demand without provisioning server resources.
Amazon S3 combined with S3 Lifecycle policies allows archiving raw logs to a cold storage class like S3 Glacier Flexible Retrieval, reducing cost. Amazon Athena provides a serverless SQL query capability directly over the archived data.
3
Analyze and eliminate incorrect options based on AWS service features.
Identify flaws: Aurora reader scaling does not help write workloads; AWS-managed KMS key policies cannot be modified for cross-account access; ElastiCache for Memcached does not support replication or durability.
Eliminating options that introduce single points of failure, administrative limitations, or incorrect engine behaviors ensures the design is both viable and optimal.

Anahtar Kavram

Selecting and integrating optimal database and storage services based on performance, cost-effective archiving, and query requirements.
Soru 212Soru

A global meteorological agency operates a severe weather monitoring platform that ingests telemetry from 5 million5\text{ million} active IoT weather sensors. Under normal conditions, each sensor transmits data every 15 minutes15\text{ minutes}. However, during sudden severe weather events, up to 1.5 million1.5\text{ million} sensors in the affected regions immediately transition to high-frequency reporting, transmitting data every 2 seconds2\text{ seconds}. The platform’s ingestion layer uses stateless web servers hosted on Amazon ECS tasks using the AWS Fargate launch type, positioned behind an Application Load Balancer (ALB). The persistence layer is an Amazon Aurora PostgreSQL DB cluster. During simulations of a sudden localized storm, the platform experiences severe request drops at the ingestion layer, and read latency for the real-time public dashboard increases exponentially. Which architectural strategy will optimize performance and ensure scalability during these unpredictable spikes?

Cevabı ve açıklamayı göster

Cevap: Replace the ALB with a Network Load Balancer (NLB) to handle the instantaneous surge of TCP connections without pre-warming. Deploy an Amazon ElastiCache for Redis cluster with Multi-AZ replication to cache dashboard query results. Configure Aurora Auto Scaling to dynamically provision Aurora Replicas to offload read queries from the primary DB instance.

Cevap

Replace the ALB with a Network Load Balancer (NLB) to handle the instantaneous surge of TCP connections without pre-warming. Deploy an Amazon ElastiCache for Redis cluster with Multi-AZ replication to cache dashboard query results. Configure Aurora Auto Scaling to dynamically provision Aurora Replicas to offload read queries from the primary DB instance.
The correct answer replaces the ALB with an NLB, which scales instantly to handle millions of requests without pre-warming. It offloads read-heavy queries by utilizing ElastiCache for Redis for caching, and uses Aurora Auto Scaling to add replicas dynamically for handling residual read queries. This represents the most performant, scalable, and resilient architecture under AWS best practices.

Adım Adım Çözüm

1
Evaluate the ingestion layer load balancer options for handling sudden, unpredictable flash traffic spikes.
Identify that an Application Load Balancer (ALB) requires time to scale out or requires manual pre-warming, which is unviable for unpredictable severe weather events. A Network Load Balancer (NLB) is designed to handle sudden spikes of millions of requests per second instantly without pre-warming.
Solves the request drops at the ingestion layer due to load balancer scaling limitations.
2
Design the caching tier to offload read traffic from the primary database cluster.
Choose Amazon ElastiCache for Redis due to its support for multi-AZ replication, persistence, and complex data structures, which are critical for maintaining high availability of the live dashboard.
Reduces read queries reaching the database, keeping DB CPU usage low during high-frequency telemetry reports.
3
Address residual read scaling at the database layer.
Configure Aurora Auto Scaling to add reader replicas dynamically, which can scale up to 15 replicas to handle remaining read traffic, while ensuring the primary writer is reserved for telemetry writes.
Provides horizontal read scaling for database query spikes that bypass the caching layer.

Anahtar Kavram

Handling unpredictable flash traffic spikes requires using Network Load Balancers (NLBs) to avoid pre-warming delays, caching read-heavy workloads with ElastiCache for Redis, and leveraging Aurora Replicas with appropriate Auto Scaling configurations rather than relying on passive standby instances.
Soru 213Soru

A retail enterprise manages 150150 member accounts within an organization in AWS Organizations. The security team requires that all VPC Flow Logs from all VPCs in all member accounts be centralized into a single Amazon S3 bucket located in a dedicated Logging account. To comply with security policies, all logs must be encrypted at rest using a customer managed KMS key, and the data transfer must not utilize intermediate CloudWatch log groups in the member accounts. Which configuration should the Solutions Architect implement in the central Logging account to enable successful delivery of the VPC Flow Logs?

Cevabı ve açıklamayı göster

Cevap: Configure the S3 bucket policy to grant s3:PutObject and s3:GetBucketAcl permissions to the S3 Log Delivery service principal (delivery.logs.amazonaws.com). Configure the KMS key policy of the customer managed key to grant kms:GenerateDataKey* and kms:Decrypt permissions to the same service principal.

Cevap

Configure the S3 bucket policy to grant s3:PutObject and s3:GetBucketAcl permissions to the S3 Log Delivery service principal (delivery.logs.amazonaws.com). Configure the KMS key policy of the customer managed key to grant kms:GenerateDataKey* and kms:Decrypt permissions to the same service principal.
The correct configuration grants bucket access and KMS key access directly to the S3 Log Delivery service principal (delivery.logs.amazonaws.com). Since VPC Flow Logs bypass CloudWatch and write directly to S3, the delivery service acts as the writer. Since the destination bucket is in a different account, a customer managed KMS key is required because AWS-managed keys (like aws/s3) do not allow modification of their key policies to trust external service principals or accounts.

Adım Adım Çözüm

1
Determine the service principal responsible for log delivery.
The service principal is identified as delivery.logs.amazonaws.com.
VPC Flow Logs delivered directly to S3 are written by the S3 Log Delivery service principal rather than the member accounts' IAM roles.
2
Configure the resource-based policy on the target S3 bucket.
The S3 bucket policy permits s3:PutObject and s3:GetBucketAcl for delivery.logs.amazonaws.com.
The service principal must have permission to verify bucket ownership and write flow log objects.
3
Configure permissions for bucket encryption.
A customer managed KMS key is selected, and its key policy is updated to grant kms:GenerateDataKey* and kms:Decrypt to delivery.logs.amazonaws.com.
AWS-managed KMS keys (like aws/s3) cannot be shared across accounts. A customer managed key allows the key policy to be customized to permit the Log Delivery service principal to generate data keys and decrypt them for log writes.

Anahtar Kavram

Cross-account VPC Flow Logs centralization with custom KMS encryption
Soru 214Soru

A financial services company is designing a hybrid network connectivity architecture to connect its on-premises data center to its AWS environment. The AWS environment consists of a Production VPC in us-east-1 and a Development VPC in us-west-2, both attached to a central AWS Transit Gateway. The primary path must use an AWS Direct Connect connection with 1 Gbps1\text{ Gbps} bandwidth, and an IPsec VPN over the public internet must serve as a backup path. Both paths connect to the same AWS Transit Gateway. The company wants to ensure that the IPsec VPN is used only if the Direct Connect connection fails, without requiring manual administrative intervention during failover. Which configuration will achieve this routing behavior automatically?

Cevabı ve açıklamayı göster

Cevap: Configure BGP on both the Direct Connect virtual interface and the VPN connection to advertise the same on-premises prefixes. The Transit Gateway will automatically prefer the Direct Connect Gateway path over the VPN path due to the default AWS route source evaluation order.

Cevap

Configure BGP on both the Direct Connect virtual interface and the VPN connection to advertise the same on-premises prefixes. The Transit Gateway will automatically prefer the Direct Connect Gateway path over the VPN path due to the default AWS route source evaluation order.
When a Transit Gateway receives identical prefixes from both a Direct Connect Gateway and an IPsec VPN connection, AWS evaluates the route source. In the route evaluation order, Transit Gateway automatically prioritizes Direct Connect Gateway attachments over VPN attachments for identical CIDR blocks. By advertising the same prefixes over both BGP sessions, failover occurs dynamically and automatically without manual intervention or static routing conflicts.

Adım Adım Çözüm

1
Establish BGP sessions over both the Direct Connect connection and the IPsec VPN connection to the Transit Gateway.
On-premises routes are dynamically propagated to the Transit Gateway.
Dynamic routing using BGP allows the Transit Gateway to automatically detect path availability and perform failover.
2
Advertise identical prefixes from the on-premises router over both paths.
The Transit Gateway receives the same routing destinations from both attachments.
Advertising identical prefixes allows the Transit Gateway to evaluate and compare the two paths using its default route preference logic.
3
Rely on the AWS Transit Gateway route selection algorithm to determine the primary path.
Traffic defaults to the Direct Connect Gateway attachment and falls back to the VPN attachment upon failure.
For identical prefix lengths, Transit Gateway prioritizes Direct Connect Gateway routes over VPN routes by default.

Anahtar Kavram

AWS Transit Gateway route evaluation order and source preference for hybrid connectivity.
Soru 215Soru

A healthcare provider is designing a new telemedicine consultation platform. The platform runs on Amazon EC2 instances in private subnets across two Availability Zones in the us-east-1 (Primary) Region and needs a disaster recovery (DR) solution in the us-west-2 (Secondary) Region. The backend database is an Amazon RDS for PostgreSQL instance. The platform must meet a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. To control costs, active application servers must not run in the recovery region during normal operations. Additionally, the platform must automatically route user traffic to the secondary region during a disaster, and outbound connectivity from the EC2 instances to external pharmacy APIs must be highly available and redundant within each region. Which architecture should a Solutions Architect design to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Create an RDS PostgreSQL cross-region read replica in us-west-2. Deploy a NAT Gateway in each Availability Zone in both regions. Use a Route 53 Private Hosted Zone for internal database endpoint resolution and associate it with the VPCs in both regions. Configure a Route 53 Failover routing policy with health checks pointing to the primary Application Load Balancer. Keep the secondary Auto Scaling group at a desired capacity of 0, scaling it up and promoting the database replica during a failover.

Cevap

The correct architecture uses an Amazon RDS cross-region read replica, redundant NAT Gateways in each Availability Zone, a Route 53 Private Hosted Zone associated with both VPCs, a Route 53 Failover routing policy, and a secondary Auto Scaling group with a capacity of 0.
The correct architecture leverages an Amazon RDS cross-region read replica to meet the 5-minute RPO requirement via low-latency asynchronous replication. By keeping the secondary Auto Scaling group's desired capacity at 0, compute costs are minimized during normal operations. Deploying NAT Gateways in every Availability Zone within both regions prevents a single point of failure for outbound connections to external APIs. Associating the Route 53 Private Hosted Zone with both the primary and secondary VPCs ensures that the application servers in the recovery region can resolve the database endpoint upon failover. Finally, a Route 53 Failover routing policy dynamically redirects client traffic based on health check results.

Adım Adım Çözüm

1
Evaluate the replication strategy for the Amazon RDS for PostgreSQL database to meet the 5-minute RPO constraint.
Determine that an RDS cross-region read replica is required, as snapshot-based backups are too infrequent.
Cross-region read replicas provide near-continuous asynchronous replication, keeping data lag well under 5 minutes.
2
Design the compute layer for the secondary region to satisfy the cost-minimization constraint while meeting the 15-minute RTO.
Configure an Auto Scaling group in the secondary region with a desired capacity of 0, to be scaled up to active instances only during failover.
This avoids ongoing EC2 costs in the secondary region, and scaling up takes only a few minutes, fitting within the 15-minute RTO.
3
Verify networking and DNS requirements for outbound connectivity and database resolution in the secondary region.
Deploy NAT Gateways in each Availability Zone of both regions, and associate the Route 53 Private Hosted Zone for the database endpoint with both the primary and secondary VPCs.
A single NAT Gateway per region is a single point of failure. The database Private Hosted Zone must be associated with the recovery VPC to allow the scaled-up EC2 instances to resolve the database's endpoint.

Anahtar Kavram

Multi-region disaster recovery design balancing RTO/RPO requirements, cost optimization, local NAT redundancy, and Route 53 DNS routing/private hosted zone associations.
Tahmini Süre:2m 0s
Soru 216Soru

A logistics company is designing a new real-time package delivery tracking system. During peak holiday seasons, query traffic for package status is expected to spike instantly from 2,0002,000 requests per second to 250,000250,000 requests per second. The system must also ingest 50,00050,000 GPS coordinate updates per second from delivery vehicles. The tracking status queries require a latency of less than 5 milliseconds5\text{ milliseconds}. Which architecture meets these performance and scalability requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Deploy a Network Load Balancer (NLB) to handle the GPS ingestion, routing to an Amazon Elastic Container Service (ECS) cluster. Store the package tracking status in Amazon ElastiCache for Redis with replication, and serve status queries from the Redis read replicas.

Cevap

Deploy a Network Load Balancer (NLB) to handle the GPS ingestion, routing to an Amazon Elastic Container Service (ECS) cluster. Store the package tracking status in Amazon ElastiCache for Redis with replication, and serve status queries from the Redis read replicas.
The correct architecture uses a Network Load Balancer (NLB), which is optimized for ultra-low latency and handles sudden, volatile traffic spikes of millions of requests per second without pre-warming. For storage, Amazon ElastiCache for Redis with replication is chosen because it easily meets the sub-5ms read latency requirement and supports replication groups, allowing reads to scale horizontally on replicas while the primary node handles the 50,00050,000 writes per second GPS ingestion rate.

Adım Adım Çözüm

1
Select the appropriate load balancer for volatile and sudden traffic spikes.
Choose a Network Load Balancer (NLB) because it can scale to millions of requests per second instantly without requiring pre-warming, unlike an Application Load Balancer (ALB).
The scenario describes a flash spike from 2,0002,000 to 250,000250,000 requests per second, which would overwhelm a standard ALB before it could auto-scale.
2
Select the database/caching tier that meets the sub-5ms read latency constraint and handles high write volumes.
Choose Amazon ElastiCache for Redis with replication.
Redis provides sub-millisecond latencies. By deploying a replication group, we can offload read queries to read replicas while reserving the primary node for the 50,00050,000 writes per second.
3
Evaluate the capabilities of alternative configurations against replication and scaling constraints.
Rule out Memcached (no replication support) and RDS Multi-AZ standby (cannot serve read traffic).
Memcached is multi-threaded but lacks replication, meaning it cannot scale reads via dedicated read replicas. An RDS standby database in a standard Multi-AZ configuration is strictly passive and cannot be queried.

Anahtar Kavram

Selecting load balancing and caching tiers capable of handling sudden, high-velocity traffic spikes and scaling read capacity horizontally.
Tahmini Süre:2m 0s
Soru 217Soru

A financial services company is designing a hybrid network architecture for its multi-account environment on AWS. The environment contains 3535 spoke VPCs in a single AWS Region: 1515 Production VPCs and 2020 Development VPCs. The company's on-premises infrastructure consists of a corporate headquarters connected via AWS Direct Connect and a backup recovery center connected via an IPsec VPN.

The network design must satisfy the following requirements:
- All spoke VPCs must have bi-directional connectivity with the corporate headquarters and the recovery center.
- Production VPCs must be able to communicate with each other.
- Development VPCs must be completely isolated from each other and from the Production VPCs.
- Administrative overhead for routing configuration must be minimized.

Which network architecture and routing configuration should the solutions architect implement?

Cevabı ve açıklamayı göster

Cevap: Create an AWS Transit Gateway. Create three Transit Gateway route tables: Production, Development, and Hybrid. Associate the Production VPC attachments with the Production route table, and enable route propagation from the Production VPCs, the Direct Connect gateway, and the VPN. Associate the Development VPC attachments with the Development route table, and enable route propagation only from the Direct Connect gateway and the VPN. Associate the Direct Connect gateway and VPN attachments with the Hybrid route table, and enable route propagation from all Production and Development VPCs.

Cevap

Create an AWS Transit Gateway with three separate route tables (Production, Development, and Hybrid) to separate routing domains, thereby ensuring proper network isolation and hybrid connectivity.
The correct configuration uses an AWS Transit Gateway with three separate route tables to isolate traffic domains. The Production route table enables local VPC-to-VPC communication and hybrid routing. The Development route table does not propagate the Development VPCs, which prevents them from routing traffic to each other. The Hybrid route table propagates all VPCs to allow return traffic from the on-premises networks back to all spoke VPCs.

Adım Adım Çözüm

1
Identify the connectivity and isolation requirements for the spoke VPCs and on-premises endpoints.
There are 1515 Production VPCs that need inter-communication and hybrid access, 2020 Development VPCs that need hybrid access but absolute isolation from each other and from Production, and corporate/recovery networks that need access to all VPCs.
Understanding the required traffic paths is necessary to design the routing domains.
2
Evaluate scale limitations of Direct Connect Gateway and VPC peering.
Direct Connect Gateway only supports up to 1010 Virtual Private Gateway associations, and full-mesh VPC peering for 1515 Production VPCs requires 105105 peering connections, making both options unsuitable.
This rules out direct Direct Connect Gateway association and manual VPC peering at this scale.
3
Design Transit Gateway route tables for spoke isolation and hybrid routing.
Create three route tables: Production (associated with Production VPCs, propagating Production and hybrid paths), Development (associated with Development VPCs, propagating only hybrid paths to prevent spoke-to-spoke routing), and Hybrid (associated with hybrid connections, propagating all spoke VPCs so the hybrid network can route replies back).
This utilizes Transit Gateway route domain separation to meet the isolation and connectivity requirements with minimal administrative overhead.

Anahtar Kavram

AWS Transit Gateway route domain separation using multiple route tables to enforce traffic isolation in a multi-account spoke VPC architecture.
Soru 218Soru

A real-estate Multiple Listing Service (MLS) provider is modernizing its legacy property listing management system by migrating to a serverless architecture on AWS. The application uses Amazon API Gateway and AWS Lambda, and must securely access an Amazon RDS PostgreSQL database located in a private subnet. The application experiences highly variable traffic with sudden, massive spikes during peak hours. The solution must ensure high availability, prevent database connection exhaustion, protect other critical functions in the AWS account from throttling, and support secure cross-account credentials access.

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

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

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon RDS Proxy in the private subnets across multiple Availability Zones to manage the database connection pool, and configure the Lambda functions to connect to the RDS Proxy endpoint.; Configure reserved concurrency on the Lambda functions processing listing updates to protect the regional concurrency pool of the AWS account from exhaustion.

Cevap

Deploy Amazon RDS Proxy in multiple Availability Zones and configure reserved concurrency on the Lambda functions.
To ensure database stability and high availability during traffic spikes, deploying Amazon RDS Proxy across multiple Availability Zones manages the connection pool effectively. To protect other critical functions in the AWS account from throttling, setting reserved concurrency on the listing update functions limits their resource consumption. Together, these two actions address database scaling limits and prevent account-wide resource starvation.

Adım Adım Çözüm

1
Evaluate connection pool management and database protection.
Identify that Amazon RDS Proxy manages PostgreSQL connection pools to prevent exhaustion during rapid scaling of serverless functions.
Lambda functions scale rapidly in response to spikes, which can quickly exceed the database's max_connections limit.
2
Address high availability and redundancy requirements.
Ensure RDS Proxy is configured in multiple subnets/Availability Zones, and reject options proposing a single NAT Gateway.
A single NAT Gateway creates a single point of failure, violating the high availability requirement.
3
Evaluate account-wide concurrency limits.
Identify that configuring reserved concurrency prevents a single bursty function from consuming the entire account's regional concurrency pool.
Without reserved concurrency limits, traffic spikes could exhaust the concurrency pool and throttle other critical operations in the account.
4
Evaluate cross-account authentication security.
Determine that a customer managed KMS key is required for cross-account Secrets Manager access.
AWS managed KMS keys do not support policy modification and cannot be shared across accounts.

Anahtar Kavram

Modernizing legacy workloads using Lambda and API Gateway requires securing database connections, configuring concurrency limits to prevent account-wide starvation, and ensuring high availability across network and encryption configurations.
Soru 219Soru

An energy trading enterprise runs its core transaction processing platform on Amazon ECS tasks within a Production account (Account 111111111111). The enterprise is designing a compliance archiving architecture where transaction logs must be written directly from the ECS tasks to an Amazon S3 bucket located in a dedicated Audit account (Account 222222222222).

The security requirements are as follows:
- Cryptographic control over the logs must remain within the Production account.
- The logs must be encrypted at rest when stored in the S3 bucket.
- The Audit account users must have the ability to read and decrypt these logs.
- The S3 Object Ownership must be configured so that the Audit account automatically owns all uploaded logs, and access control lists (ACLs) are disabled.
- The ECS task roles must be granted only the minimum required permissions.

Which configuration strategy meets these requirements while adhering to the principle of least privilege?

Cevabı ve açıklamayı göster

Cevap: In Account 111111111111, create a KMS customer managed key (CMK). Configure the CMK key policy to allow the Production ECS task role to perform kms:GenerateDataKey and kms:Decrypt, and allow Account 222222222222 to perform kms:Decrypt. In Account 222222222222, set S3 Object Ownership to Bucket Owner Enforced on the S3 bucket. Configure the S3 bucket policy to allow s3:PutObject permissions only to the Production ECS task role principal. Attach an IAM policy to the Production ECS task role that grants s3:PutObject on the Audit S3 bucket and kms:GenerateDataKey and kms:Decrypt on the Production CMK.

Cevap

The correct strategy is to create a customer managed key in the Production Account, configure its key policy to allow the Production ECS task role to use it and the Audit Account to decrypt with it. On the Audit S3 bucket, configure S3 Object Ownership to Bucket Owner Enforced, and set the S3 bucket policy to allow only the Production ECS task role to write objects. Finally, attach an IAM policy to the Production ECS task role that grants S3 write permissions and KMS access.
The correct strategy uses a Customer Managed Key (CMK) in the Production Account to keep cryptographic control there, while updating its key policy to delegate decrypt permissions to the Audit Account. By setting the S3 Object Ownership to Bucket Owner Enforced in the Audit Account, S3 automatically transfers ownership of the uploaded objects to the Audit Account and disables ACLs. The S3 bucket policy specifies the exact ECS task role principal, and a local IAM policy explicitly grants the ECS task role the required write and encryption permissions. This setup meets all compliance, ownership, and least privilege requirements.

Adım Adım Çözüm

1
Select a key type and location that allows cross-account policy modification to meet the encryption and compliance requirements.
Create a Customer Managed Key (CMK) in the Production Account (111111111111). AWS-managed keys (e.g., aws/s3) cannot be shared across accounts as their key policies are immutable.
Cryptographic control must remain with the Production Account, and the key policy must be modified to delegate decrypt permissions to the Audit Account.
2
Establish cross-account encryption and decryption rights in the KMS key policy.
The key policy in Account 111111111111 is configured to allow the Production ECS task role to use the key for encryption (GenerateDataKey, Decrypt) and allows Account 222222222222 to use the key for decryption (Decrypt).
This allows the Production ECS tasks to encrypt the transaction logs during upload, and allows the Audit Account to decrypt them when reading.
3
Ensure the Audit Account owns all uploaded files and disable Access Control Lists (ACLs) to simplify compliance management.
Set S3 Object Ownership to Bucket Owner Enforced on the Audit S3 bucket in Account 222222222222.
This automatically transfers ownership of all uploaded objects to the Audit Account and disables ACLs, ensuring the Audit Account can manage and read the logs.
4
Apply explicit write permissions on both the source IAM identity and the destination S3 bucket resource policy using the principle of least privilege.
The S3 bucket policy in Account 222222222222 is configured to permit the specific ECS task role ARN from Account 111111111111 to perform s3:PutObject. A local IAM policy is attached to the ECS task role in Account 111111111111 granting s3:PutObject on the Audit S3 bucket and kms:GenerateDataKey and kms:Decrypt on the Production CMK.
Cross-account access requires explicit permission in both the IAM policy of the caller and the resource-based policy of the target bucket. Restricting the bucket policy to the specific ECS task role (rather than using wildcard principals with organizational conditions) enforces least privilege.

Anahtar Kavram

Cross-Account S3 Access with KMS CMK Encryption and S3 Object Ownership
Soru 220Soru

An enterprise is designing a new multi-tenant financial transaction platform (OLTP workload). The platform requires a relational database that handles moderate write volumes and dynamically scales read capacity across 22 AWS Regions to support end-of-month reporting spikes. The solution must achieve a recovery time objective (RTO) of less than 11 hour and a recovery point objective (RPO) of less than 1515 minutes. Additionally, compliance regulations require database exports stored in Amazon S3 to be directly decryptable by a central security audit team operating in a separate AWS account. Which database and storage strategy meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora Global Database across both regions, and configure an Aurora Auto Scaling policy for reader instances in both the primary and secondary regions. Encrypt the database clusters using a Customer Managed Key (CMK) in AWS KMS, and configure the key policy to grant decrypt permissions to the external security audit account's IAM principal.

Cevap

Deploy an Amazon Aurora Global Database across both regions, configure an Aurora Auto Scaling policy for reader instances in both the primary and secondary regions, and encrypt the database clusters using a Customer Managed Key (CMK) in AWS KMS with cross-account permissions.
The correct strategy uses Amazon Aurora Global Database because it satisfies the multi-region read requirement, scales reader instances automatically using Aurora Auto Scaling, and achieves an RPO of less than 11 second and RTO of less than 11 minute. Additionally, using an AWS KMS Customer Managed Key (CMK) allows the policy to be modified to grant decrypt permissions to the security auditing account's IAM principal, enabling cross-account data decryption of database exports.

Adım Adım Çözüm

1
Select a multi-region database solution that meets low RTO/RPO targets.
Amazon Aurora Global Database provides sub-second replication latency across regions, easily satisfying the target RTO of less than 11 hour and RPO of less than 1515 minutes.
Standard backup and restore methods or slow snapshot copies cannot meet strict cross-region failover limits.
2
Configure horizontal scale-out of read replicas for seasonal spikes.
Configure Aurora Auto Scaling to dynamically provision and remove Aurora Replicas (reader instances) in both regions based on performance metrics.
This handles the end-of-month spikes without maintaining over-provisioned idle databases.
3
Implement a cross-account encryption strategy for database exports.
Use an AWS KMS Customer Managed Key (CMK) instead of an AWS-managed key, modifying its key policy to trust the security audit account's IAM principal for the kms:Decrypt action.
AWS-managed keys do not support policy modifications and cannot be shared across AWS accounts.

Anahtar Kavram

Designing a multi-region, scalable relational database strategy using Aurora Global Database and Customer Managed KMS Keys for secure cross-account auditing.
Tahmini Süre:2m 0s
ÖncekiSayfa 11 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin