Design Resilient Architectures

382 soru

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

A company hosts a stateful transaction processing application on Amazon EC2 instances behind an Application Load Balancer (ALB) in the us-east-1 Region. The company wants to set up an active-passive disaster recovery (DR) configuration using a secondary scaled-down environment behind an ALB in the eu-west-1 Region. The DR plan requires automatic failover to the secondary region if the primary region's application or its underlying database becomes unavailable. To avoid database write conflicts, the application in the secondary region must not receive traffic unless a failover is active. Which two configurations should a solutions architect implement to meet these requirements? (Select two.)

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

Configure Route 53 Failover routing alias records pointing to the ALB in each region, and set the Evaluate Target Health option to Yes on both records.

Configure the primary Application Load Balancer (ALB) target group health check to query a deep path (such as /health) that verifies database connectivity, so targets are marked unhealthy if the database is offline.

Configure Route 53 Latency routing records pointing to both the primary and secondary ALBs to automatically route traffic based on network latency, and rely on Route 53 to fail over to the standby region if the primary region goes offline.

Create standard CNAME records pointing to the primary and secondary ALB DNS names, and enable the Evaluate Target Health option on both records to allow Route 53 to monitor the load balancer health.

Configure Route 53 Failover routing policies to route database traffic directly to the RDS Read Replica in the secondary region by using Route 53 DNS records to handle automatic read-replica promotion and database write failover.

Cevabı ve açıklamayı göster

Cevap: Configure Route 53 Failover routing alias records pointing to the ALB in each region, and set the Evaluate Target Health option to Yes on both records.; Configure the primary Application Load Balancer (ALB) target group health check to query a deep path (such as /health) that verifies database connectivity, so targets are marked unhealthy if the database is offline.

Cevap

The correct configurations are to set up Route 53 Failover routing alias records with Evaluate Target Health enabled, and to implement a deep health check endpoint on the primary Application Load Balancer target group to verify database availability.

To implement a resilient active-passive configuration, the solutions architect should use Route 53 Failover routing records. These records must be configured as Alias records pointing to the respective Application Load Balancers (ALBs) to support the Evaluate Target Health feature. Additionally, because the database status dictates the availability of this stateful application, a deep health check endpoint (like /health) must be configured on the primary ALB's target group. This ensures that a database failure marks the targets and the load balancer as unhealthy, prompting Route 53 to trigger failover.

Adım Adım Çözüm

Determine the routing policy that meets the active-passive constraint.

Route 53 Failover routing policy is the correct choice, as it ensures traffic is directed to the primary region and only switches to the secondary region if the primary becomes unhealthy. Policies like Latency routing are active-active and do not satisfy this requirement.

Active-passive routing is required to prevent write conflicts on a stateful database.

Select the correct DNS record type to enable Route 53 health monitoring of AWS resources.

Route 53 Alias records must be used because they natively support the 'Evaluate Target Health' option, which queries the ALB health. Standard CNAME records do not support this feature.

Ensuring the correct record type is used is critical for integrating DNS routing with resource health status.

Determine how Route 53 will detect database-level failures.

Configure the ALB target group health check to hit a '/health' endpoint that runs a query against the database. When the database is offline, the EC2 targets fail the check, the ALB becomes unhealthy, and Route 53 detects this via the Evaluate Target Health setting.

Standard ALB target group checks only verify if the web server is listening, which would miss database outages.

Anahtar Kavram

Route 53 active-passive failover requires Failover routing alias records combined with deep application health checks on the load balancer's targets.

Tahmini Süre:2m 0s

Soru 42Soru →

A software-as-a-service (SaaS) company hosts its customer relationship management (CRM) application on AWS, utilizing an Amazon RDS for PostgreSQL DB instance for the transactional database. The company needs to design a database architecture that ensures high availability within the region to survive an Availability Zone (AZ) outage with a Recovery Time Objective (RTO) of less than 2 minutes and a Recovery Point Objective (RPO) of 0. Additionally, the database must be able to scale to handle a high volume of read-only reporting queries during business hours without impacting write performance. Which database configuration meets these requirements?

Configure the RDS DB instance as a Multi-AZ deployment, and create one or more RDS Read Replicas in different Availability Zones to handle the read-only reporting traffic.

Configure the RDS DB instance as a single-AZ deployment, create multiple Read Replicas in different Availability Zones, and configure the application to use the Read Replicas as automatic failover targets.

Configure the RDS DB instance as a Multi-AZ deployment, and use Amazon Route 53 latency routing to distribute read traffic between the active primary DB instance and the passive standby DB instance.

Configure the RDS DB instance as a Multi-AZ deployment, and implement a cross-region Pilot Light configuration to serve the reporting queries from a read-only standby instance in a secondary region.

Cevabı ve açıklamayı göster

Cevap: Configure the RDS DB instance as a Multi-AZ deployment, and create one or more RDS Read Replicas in different Availability Zones to handle the read-only reporting traffic.

Cevap

Configure the RDS DB instance as a Multi-AZ deployment, and create one or more RDS Read Replicas in different Availability Zones to handle the read-only reporting traffic.

The correct configuration uses RDS Multi-AZ to achieve high availability with synchronous replication to a standby instance in another AZ, enabling automatic failover with zero data loss (RPO of 0) and low downtime (RTO of less than 2 minutes). Creating Read Replicas offloads read traffic to separate endpoints, scaling read performance without affecting the primary writer instance.

Adım Adım Çözüm

Evaluate the high availability (HA) requirements.

To meet an RTO of less than 2 minutes and an RPO of 0 (no data loss) during an AZ outage, a Multi-AZ deployment is required because it uses synchronous replication to a standby instance in another AZ and performs automatic failover.

Single-AZ deployments or asynchronous read replicas cannot guarantee zero data loss or automatic failover within the required RTO.

Evaluate the read-scaling requirements.

To scale read-only reporting queries without affecting the primary writer instance, RDS Read Replicas must be deployed.

Read replicas utilize asynchronous replication to process read-only queries, freeing up resources on the primary DB instance.

Combine the HA and read-scaling configurations.

The final architecture requires a Multi-AZ deployment for HA and automatic failover, coupled with Read Replicas to offload read-only queries.

This combination successfully satisfies both resilience and performance scaling constraints.

Anahtar Kavram

Amazon RDS Multi-AZ deployments provide high availability and automatic failover, while Read Replicas provide horizontal scaling for read-heavy workloads.

Tahmini Süre:1m 30s

Soru 43Soru →

A technology company hosts a containerized catalog API on Amazon EC2 instances within a private subnet. The instances are managed by an Auto Scaling group and are registered with an Application Load Balancer (ALB) that resides in a public subnet. The API service runs on port 8080. The target group is configured to perform health checks on port 8080. The security group of the EC2 instances is configured to allow inbound traffic on port 8080 from the ALB's security group. To meet security requirements, a network administrator applied a custom Network ACL to the private subnet, adding an inbound rule that allows traffic on port 8080 from the ALB's subnet. However, the health checks are now failing, and the ALB reports all EC2 instances as unhealthy. Which action should the solutions architect take to resolve the health check failure?

Add an outbound rule to the private subnet's Network ACL to allow traffic to the ephemeral ports of the Application Load Balancer's subnet.

Add an outbound rule to the EC2 instances' Security Group to allow return traffic on ephemeral ports, because Security Groups are stateless and require explicit return rules.

Modify the target group health check configuration to use the default HTTP port 80 instead of port 8080, as Elastic Load Balancing health checks must query port 80 to bypass subnet-level restrictions.

Configure an Amazon Route 53 latency routing policy to route traffic directly to the private IP addresses of the EC2 instances to bypass the subnet's Network ACL.

Cevabı ve açıklamayı göster

Cevap: Add an outbound rule to the private subnet's Network ACL to allow traffic to the ephemeral ports of the Application Load Balancer's subnet.

Cevap

Add an outbound rule to the private subnet's Network ACL to allow traffic to the ephemeral ports of the Application Load Balancer's subnet.

The correct option is to add an outbound rule to the private subnet's Network ACL. Since Network ACLs are stateless, allowing inbound traffic on port 8080 is not sufficient; the return traffic from the EC2 instances (source port 8080) to the ALB (destination ephemeral ports 1024-65535) must be explicitly permitted by an outbound rule on the private subnet's Network ACL.

Adım Adım Çözüm

Analyze the network configuration of the Application Load Balancer (ALB) and EC2 instances.

The ALB is in a public subnet, and the EC2 instances are in a private subnet. The EC2 instances listen on port 8080, which is also the target group port and the health check port.

Understanding the traffic flow helps locate where the network packet is blocked.

Evaluate the stateful and stateless components in the communication path.

Security groups are stateful, so inbound traffic allowed on port 8080 will automatically allow outbound return traffic. Network ACLs are stateless, meaning both inbound and outbound traffic must be explicitly allowed.

Since a custom Network ACL was applied, both incoming requests and outgoing responses must have matching rules.

Determine the required outbound rule for the Network ACL.

The load balancer sends health check requests from ephemeral ports (1024-65535) to port 8080 on the instances. When the instances reply, the return traffic is sent from port 8080 back to the load balancer's ephemeral ports. Therefore, the private subnet's Network ACL needs an outbound rule allowing traffic to the ALB subnet on ephemeral ports.

This completes the stateless return path, allowing the health check to succeed.

Anahtar Kavram

Network ACLs are stateless firewall rules at the subnet level, meaning that return traffic must be explicitly allowed via outbound rules, whereas Security Groups are stateful and allow return traffic automatically.

Tahmini Süre:1m 30s

Soru 44Soru →

A retail company hosts a customer-facing e-commerce application on Amazon EC2 instances behind an Application Load Balancer (ALB) in the us-east-1 Region. For disaster recovery (DR), the company has deployed a scaled-down standby environment in the us-west-2 Region with a standby ALB. The company wants to implement an active-passive disaster recovery strategy where Route 53 automatically redirects all incoming traffic to the standby ALB in us-west-2 only if the application in us-east-1 is unhealthy. The target Recovery Time Objective (RTO) is less than 2 minutes. Which TWO configurations must the solutions architect implement to meet these requirements? (Select TWO.)

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

Create a Route 53 Failover Alias record for the primary ALB, setting the routing policy to Primary and Evaluate Target Health to Yes.

Create a Route 53 Failover Alias record for the standby ALB, setting the routing policy to Secondary and Evaluate Target Health to Yes.

Create Route 53 Latency routing records for both regional ALBs to automatically route user traffic based on the lowest network latency.

Configure the standby environment as a pilot light deployment with all EC2 instances stopped, and use Route 53 health checks to start the instances automatically during failover.

Configure a Route 53 health check to monitor the Amazon RDS read replica in the standby region and automatically promote it to primary when the primary database goes offline.

Cevabı ve açıklamayı göster

Cevap: Create a Route 53 Failover Alias record for the primary ALB, setting the routing policy to Primary and Evaluate Target Health to Yes.; Create a Route 53 Failover Alias record for the standby ALB, setting the routing policy to Secondary and Evaluate Target Health to Yes.

Cevap

Create a Route 53 Failover Alias record for the primary ALB, setting the routing policy to Primary and Evaluate Target Health to Yes; and create a Route 53 Failover Alias record for the standby ALB, setting the routing policy to Secondary and Evaluate Target Health to Yes.

To configure active-passive failover with Amazon Route 53, a solutions architect should create two failover records: one primary and one secondary. By using Alias records pointing to the Application Load Balancers (ALBs) and enabling the 'Evaluate Target Health' option, Route 53 automatically monitors the health of the targets in the target groups. If the targets behind the primary ALB fail their health checks, Route 53 will automatically stop routing traffic to the primary ALB and begin routing it to the secondary standby ALB, keeping failover time minimal and meeting the recovery time objective.

Adım Adım Çözüm

Analyze the disaster recovery requirement.

The requirements demand an active-passive cross-region failover strategy with an RTO of less than 2 minutes.

This establishes that we need a fast DNS-based failover mechanism using Route 53 and a warm standby environment that is ready to accept traffic immediately.

Select the appropriate routing policy.

Amazon Route 53 Failover routing policy is designed specifically for active-passive configurations.

Other routing policies like Latency routing are intended for active-active configurations rather than strict active-passive failover.

Configure health checks and target evaluation.

Configure Primary and Secondary Failover Alias records pointing to the respective ALBs with 'Evaluate Target Health' set to Yes.

Setting 'Evaluate Target Health' to Yes on the Alias records allows Route 53 to check the health of the backend EC2 targets behind the ALBs directly, enabling rapid failover within the RTO budget without requiring manually created external health checks.

Anahtar Kavram

Amazon Route 53 Active-Passive Failover Routing

Soru 45Soru →

A company hosts a web application on Amazon EC2 instances managed by an Auto Scaling group. The instances are registered as targets under an Application Load Balancer (ALB) that handles SSL termination. Users intermittently report receiving "502 Bad Gateway" errors when accessing the application. A solutions architect discovers that the ALB target group has marked several EC2 instances as unhealthy, but the Auto Scaling group still shows the instances as healthy and continues to route traffic to them. Which configuration change will ensure that the Auto Scaling group automatically terminates and replaces the unhealthy instances?

Update the Auto Scaling group's health check type configuration from EC2 to ELB.

Modify the target group configuration to perform health checks on the default port 80 instead of the application's traffic port.

Configure the private subnet's Network ACL to statefully allow outbound traffic from the ALB's security group to ensure the health checks succeed.

Implement an Amazon Route 53 latency routing policy with health checks to route client traffic to a secondary target group in a different Availability Zone.

Cevabı ve açıklamayı göster

Cevap: Update the Auto Scaling group's health check type configuration from EC2 to ELB.

Cevap

Update the Auto Scaling group's health check type configuration from EC2 to ELB.

The correct answer is to update the Auto Scaling group's health check type configuration from EC2 to ELB. By default, an Auto Scaling group only performs EC2 status checks (system and instance status checks). If the application server fails but the OS remains running, the Auto Scaling group will consider the instance healthy. Setting the health check type to ELB configures the Auto Scaling group to also check the health of the instances in the Application Load Balancer target group, causing it to automatically terminate and replace instances that fail the ALB health check.

Adım Adım Çözüm

Analyze the mismatch between the load balancer target group health status and the Auto Scaling group health status.

By default, an Auto Scaling group only monitors EC2 status checks (the health check type is set to EC2). It does not monitor the health of the application running behind the Application Load Balancer.

This explains why the Auto Scaling group considers the instances healthy even though the ALB target group has marked them as unhealthy due to application-level failures.

Identify the correct configuration update to bind the Auto Scaling group health checks to the load balancer target group health checks.

Changing the Auto Scaling group health check type to ELB ensures the Auto Scaling group monitors the target group's health checks.

This configuration allows the Auto Scaling group to detect when an instance fails the target group's application-level health check, prompting it to replace the instance.

Anahtar Kavram

Auto Scaling Group Health Checks (EC2 vs. ELB)

Tahmini Süre:1m 30s

Soru 46Soru →

An online ticketing platform serves event detail pages and seat map images to a global audience. The application runs on Amazon EC2 instances behind an Application Load Balancer (ALB) in the ap-southeast-1 Region. To reduce latency, the platform uses an Amazon CloudFront distribution. The company wants to implement a highly resilient architecture that automatically serves a static maintenance page from an Amazon S3 bucket in the us-west-2 Region if the ALB returns gateway errors (502, 503, or 504) during high-traffic events.

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

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

Create a CloudFront origin group with the ALB as the primary origin and the S3 bucket as the secondary origin.

Configure the origin group's failover criteria to include HTTP status codes 502, 503, and 504.

Use AWS WAF to inspect the ALB responses and redirect client requests to the S3 bucket if a gateway error code is detected.

Configure Amazon Route 53 with active-passive failover using a latency routing policy between the ALB and the S3 bucket.

Create a custom cache behavior for the distribution with the Minimum TTL, Maximum TTL, and Default TTL set to 0.

Cevabı ve açıklamayı göster

Cevap: Create a CloudFront origin group with the ALB as the primary origin and the S3 bucket as the secondary origin.; Configure the origin group's failover criteria to include HTTP status codes 502, 503, and 504.

Cevap

Create a CloudFront origin group with the ALB as the primary origin and the S3 bucket as the secondary origin, and configure the origin group's failover criteria to include HTTP status codes 502, 503, and 504.

To build a resilient edge architecture that handles backend failures automatically, a CloudFront origin group must be configured. Placing the Application Load Balancer as the primary origin and the Amazon S3 bucket as the secondary origin allows CloudFront to manage the traffic routing. Configuring the origin group's failover criteria to trigger on HTTP status codes 502, 503, and 504 ensures that CloudFront switches to the static maintenance page hosted on Amazon S3 without any user-perceived downtime or DNS propagation delay.

Adım Adım Çözüm

Configure the two distinct destinations as CloudFront origins.

The Application Load Balancer and the Amazon S3 bucket are defined as origins within the CloudFront distribution.

This registers the primary application stack and the backup static storage as valid backend targets.

Group the origins into an origin group.

An origin group is established with the ALB designated as the primary origin and the S3 bucket as the secondary origin.

An origin group is the CloudFront configuration wrapper required to enable origin-level resilience and automatic failover.

Define the origin failover criteria.

The origin group is configured to failover when the primary origin returns HTTP status codes 502, 503, or 504.

This tells CloudFront to automatically query the backup S3 bucket instead of the ALB when those gateway error codes are returned.

Anahtar Kavram

Amazon CloudFront Origin Groups and Origin Failover

Soru 47Soru →

A company runs a high-traffic e-commerce platform where a fleet of Amazon EC2 instances in an Auto Scaling group (ASG) serves traffic behind an Application Load Balancer (ALB). During a peak shopping event, several instances experience application-level crashes and stop responding to HTTP requests, but the EC2 status checks show the instances are healthy. The ALB marks the instances as unhealthy and stops sending them traffic, but the Auto Scaling group does not replace them. Which configuration change should the solutions architect make to ensure unhealthy instances are automatically replaced?

Update the Auto Scaling group health check type from EC2 to ELB.

Reconfigure the Application Load Balancer target group health check to query a default port such as port 80, regardless of the application's actual listening port.

Create stateless Network Access Control List (Network ACL) rules to monitor target instance health and terminate unresponsive instances.

Configure an Amazon Route 53 latency-based routing policy with target health evaluation to identify and terminate the failed instances.

Cevabı ve açıklamayı göster

Cevap: Update the Auto Scaling group health check type from EC2 to ELB.

Cevap

Update the Auto Scaling group health check type from EC2 to ELB.

By default, an Auto Scaling group (ASG) only monitors EC2 status checks. If an application crashes but the operating system and VM remain responsive, the EC2 status checks will pass, and the ASG will not replace the instance. Changing the health check type of the ASG to ELB allows the ASG to use the Application Load Balancer's target group health checks. When the ALB marks an instance as unhealthy, the ASG will automatically terminate and replace it.

Adım Adım Çözüm

Analyze the health check configuration of the Auto Scaling group (ASG) and the Application Load Balancer (ALB).

The ASG is currently using the default EC2 health check, which only monitors the hypervisor and OS-level status, while the ALB performs application-level HTTP health checks.

This explains why the ASG does not terminate the instances despite the ALB marking them as unhealthy.

Change the health check type of the ASG to ELB.

The ASG will now monitor both EC2 status checks and the ALB target group health checks.

To ensure that application-level failures detected by the ALB trigger instance replacement by the ASG.

Anahtar Kavram

Auto Scaling Group Health Check Type

Tahmini Süre:45s

Soru 48Soru →

A global e-learning company serves dynamic content to users worldwide. The application backend is deployed behind Application Load Balancers (ALBs) in both the eu-central-1 and ap-southeast-1 regions. The company wants to route users to the region that provides the lowest network latency. If one of the regions experiences an outage, Route 53 must automatically stop routing traffic to that region's ALB. The application uses the apex domain learn.example.com. Which configuration should the solutions architect implement to meet these requirements?

Create Latency Alias records for the apex domain pointing to the ALBs in each region, and set the 'Evaluate Target Health' parameter to 'No' to maximize DNS caching efficiency.

Create Latency Alias records for the apex domain. Configure the primary record to point to the eu-central-1 ALB, and configure the secondary record to point directly to the DNS endpoint of the Amazon RDS read replica in ap-southeast-1.

Create Latency Alias records for the apex domain pointing to the respective ALBs in each region, and set the 'Evaluate Target Health' parameter to 'Yes' on both records.

Create Failover records for the apex domain, pointing the primary record to the eu-central-1 ALB. Point the secondary record to a stopped EC2 instance in ap-southeast-1 that serves as a standby database, expecting Route 53 to automatically start the instance and route traffic during a failover.

Cevabı ve açıklamayı göster

Cevap: Create Latency Alias records for the apex domain pointing to the respective ALBs in each region, and set the 'Evaluate Target Health' parameter to 'Yes' on both records.

Cevap

Create Latency Alias records for the apex domain pointing to the respective ALBs in each region, and set the 'Evaluate Target Health' parameter to 'Yes' on both records.

The correct configuration utilizes Latency-based routing with Alias records pointing to the ALBs in each region. Because the zone apex domain (learn.example.com) is used, CNAME records are not permitted, necessitating Alias records. Setting 'Evaluate Target Health' to 'Yes' allows Route 53 to determine the health of the ALBs based on the underlying target group health checks, enabling automatic failover and routing redirection during a regional outage.

Adım Adım Çözüm

Determine the routing policy and record type required for the zone apex domain.

An Alias record must be used because DNS standards do not allow CNAME records at the zone apex (learn.example.com). To satisfy the requirement of routing to the lowest latency region, Latency-based routing must be used.

Alias records allow mapping the zone apex to AWS resources like ALBs, and Latency routing satisfies the performance requirement.

Configure health checks and automatic failover mechanism.

Enable the 'Evaluate Target Health' setting (set to Yes) on the Route 53 Latency Alias records pointing to the ALBs.

This allows Route 53 to inherit the health of the ALB (based on its target group health checks) to stop routing traffic to an unhealthy region automatically without needing a separate Route 53 health check.

Anahtar Kavram

Route 53 Latency Routing with Alias records and Target Health Evaluation

Soru 49Soru →

A medical research institute distributes large, static genomic data files that are updated weekly, and provides a search API for genomic metadata. The genomic files are stored in an Amazon S3 bucket, and the search API is hosted on Amazon EC2 instances behind an Application Load Balancer (ALB). During new publication releases, the institute experiences sudden spikes in global traffic. The institute needs a resilient architecture that minimizes load on both S3 and the ALB, reduces latency for researchers worldwide, and protects the search API from SQL injection attacks. Which architecture meets these requirements with the lowest latency and highest resiliency?

Configure Amazon Route 53 with latency-based routing policies to distribute traffic directly to the S3 bucket for static files and to the ALB for API requests. Associate an AWS WAF web ACL with the ALB to mitigate SQL injection attacks.

Create an Amazon CloudFront distribution with the S3 bucket and ALB configured as origins. Configure cache behaviors to cache static files and forward API requests. Enable AWS Shield Advanced on the CloudFront distribution to detect and block SQL injection attacks on the API.

Create an Amazon CloudFront distribution with the S3 bucket and ALB configured as origins. Configure two cache behaviors: one for static file paths with caching enabled, and one for API paths that forwards requests to the ALB. Associate an AWS WAF web ACL with the CloudFront distribution.

Create an Amazon CloudFront distribution with the S3 bucket and ALB configured as origins. Configure a cache behavior for the static files with Minimum TTL, Default TTL, and Maximum TTL set to 0 to ensure the weekly files are never stale. Associate an AWS WAF web ACL with the CloudFront distribution.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon CloudFront distribution with the S3 bucket and ALB configured as origins. Configure two cache behaviors: one for static file paths with caching enabled, and one for API paths that forwards requests to the ALB. Associate an AWS WAF web ACL with the CloudFront distribution.

Cevap

The correct solution uses Amazon CloudFront to cache static files from S3 at edge locations, significantly reducing global latency and origin S3 read load during traffic spikes. Dynamic API requests are routed through a separate CloudFront cache behavior to the ALB without caching. By attaching an AWS WAF web ACL to CloudFront, the API is protected against SQL injection attacks at the edge, before the traffic reaches the backend servers.

Adım Adım Çözüm

Analyze the static and dynamic requirements.

The static genomic data files stored in S3 can be cached at the edge, while the dynamic search API requests behind the ALB should be forwarded to the origin without caching.

Separating static and dynamic traffic allows for optimized caching rules and reduces load on the origin S3 bucket and ALB.

Configure Amazon CloudFront origins and cache behaviors.

Create a CloudFront distribution with the S3 bucket and ALB as origins. Create a behavior for `/static/*` that caches content, and a behavior for `/api/*` that forwards requests to the ALB origin with caching disabled.

CloudFront edge locations serve cached static content directly to users, minimizing latency and origin load, while acting as a reverse proxy for the API traffic.

Address the security requirement for the search API.

Associate an AWS WAF web ACL with the CloudFront distribution to inspect incoming requests for SQL injection signatures.

AWS WAF provides Layer 7 protection at the edge, blocking malicious requests before they reach the ALB or S3 origins.

Anahtar Kavram

Using Amazon CloudFront cache behaviors to segregate and optimize static caching and dynamic forwarding, combined with AWS WAF for Layer 7 edge security.

Tahmini Süre:2m 0s

Soru 50Soru →

A company operates a global shipment tracking API at api.shipments.example.com. The application is deployed in the eu-central-1 and ap-southeast-1 Regions behind an Application Load Balancer (ALB) in each Region. The company wants an active-active setup that routes users to the Region with the lowest network latency. If an ALB in one Region fails, Route 53 must automatically stop routing traffic to that Region. Which configuration meets these requirements with the lowest administrative complexity and cost?

Create Route 53 Latency CNAME records for api.shipments.example.com pointing to the ALB DNS names, and set Evaluate Target Health to Yes.

Create Route 53 Failover Alias records pointing to the ALBs, configuring eu-central-1 as primary and ap-southeast-1 as a pilot light secondary that only provisions compute resources after a failover event is detected.

Create Route 53 Latency Alias records for api.shipments.example.com pointing to the Application Load Balancer (ALB) in each Region, and set Evaluate Target Health to Yes.

Create Route 53 Latency Alias records pointing to the ALBs, and configure the DNS failover to route traffic directly to the Amazon RDS Read Replica in the secondary Region when the primary database becomes unhealthy.

Cevabı ve açıklamayı göster

Cevap: Create Route 53 Latency Alias records for api.shipments.example.com pointing to the Application Load Balancer (ALB) in each Region, and set Evaluate Target Health to Yes.

Cevap

Create Route 53 Latency Alias records for api.shipments.example.com pointing to the Application Load Balancer (ALB) in each Region, and set Evaluate Target Health to Yes.

The correct configuration uses Route 53 Latency Alias records pointing to the Application Load Balancers with Evaluate Target Health set to Yes. This fulfills the active-active requirement by routing users to the Region with the lowest latency, and it automatically stops routing traffic to a Region if its ALB becomes unhealthy, using the inherited ALB health checks without any extra cost or administrative overhead.

Adım Adım Çözüm

Analyze the active-active and latency requirements.

Determine that Latency routing must be used to send clients to the closest Region to minimize latency, rather than Failover routing which is active-passive.

The requirement specifies routing users to the Region with the lowest network latency under normal operating conditions.

Determine the health checking and failover mechanism.

Identify that 'Evaluate Target Health' must be set to Yes to let Route 53 monitor the ALBs automatically.

Enabling Evaluate Target Health allows Route 53 to check the health of the ALB targets and stop routing traffic if they fail, without needing custom HTTP health checks.

Evaluate record types (Alias vs CNAME) for the load balancers.

Select Alias records because Route 53 'Evaluate Target Health' is only supported on Alias records, and Alias records do not incur DNS query charges.

CNAME records do not support the 'Evaluate Target Health' feature directly, requiring additional configurations and costs.

Anahtar Kavram

Route 53 Latency Alias routing with Evaluate Target Health enables cost-effective, low-latency, active-active regional failover.

Soru 51Soru →

A financial services company runs a mission-critical web application on AWS. The application uses Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB) and an Amazon Aurora MySQL database. The company requires a cross-region disaster recovery (DR) solution with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 2 minutes. The architecture must minimize ongoing idle compute costs. Which solution best meets these requirements?

Configure Amazon Aurora Global Database with the primary database cluster in the active Region and a secondary cluster in the recovery Region. Set up an Auto Scaling group in the recovery Region with the desired capacity set to zero, maintaining pre-configured launch templates and target groups. Create a cross-Region Amazon S3 replication pipeline for application state. Use Amazon Route 53 Application Recovery Controller (ARC) routing control to fail over by promoting the secondary Aurora cluster and scaling the Auto Scaling group to the required capacity.

Set up Amazon Aurora cross-Region Read Replicas from the active Region to the recovery Region. Configure an Application Load Balancer in the recovery Region pointing to EC2 instances in a scaled-down Warm Standby state. Rely on Amazon Route 53 Latency routing with health checks to automatically promote the cross-Region Read Replica to primary and route traffic to the recovery Region if the active Region becomes unhealthy.

Establish a Pilot Light disaster recovery environment in the recovery Region. Schedule Aurora database snapshots every 15 minutes and replicate them to the recovery Region. Deploy an Auto Scaling group scaled to zero in the recovery Region. During a failover event, restore the database from the latest replicated snapshot, scale up the EC2 instances, and update Route 53 failover records.

Configure a Backup and Restore strategy by exporting Aurora database backups every 2 minutes to Amazon S3, and use S3 cross-region replication to copy these files to the recovery Region where they are transitioned to Amazon S3 Glacier Flexible Retrieval. Set up an Auto Scaling group in the recovery Region. During failover, use Standard Retrieval to restore the database in the recovery Region.

Cevabı ve açıklamayı göster

Cevap: Configure Amazon Aurora Global Database with the primary database cluster in the active Region and a secondary cluster in the recovery Region. Set up an Auto Scaling group in the recovery Region with the desired capacity set to zero, maintaining pre-configured launch templates and target groups. Create a cross-Region Amazon S3 replication pipeline for application state. Use Amazon Route 53 Application Recovery Controller (ARC) routing control to fail over by promoting the secondary Aurora cluster and scaling the Auto Scaling group to the required capacity.

Cevap

The configuration using Amazon Aurora Global Database satisfies the 2-minute RPO due to its typical sub-second replication latency. Keeping the recovery Region's EC2 Auto Scaling group capacity at zero minimizes compute costs when idle, conforming to the Pilot Light architecture pattern. Since launch templates and target groups are pre-configured, the EC2 instances can scale up quickly, and promoting the Aurora secondary cluster takes less than a minute, allowing the entire recovery workflow to complete well within the 15-minute RTO. Route 53 ARC routing controls provide the mechanism to safely orchestrate this cross-region traffic shift.

Adım Adım Çözüm

Evaluate the RPO requirement of 2 minutes.

Identify that backup-and-restore or database snapshot strategies with intervals greater than 2 minutes are insufficient. Aurora Global Database replication is asynchronous and typically completes in under a second, meeting the RPO.

Choosing the correct replication technology is necessary to ensure data loss is kept within the RPO window.

Evaluate the RTO requirement of 15 minutes and the cost constraint.

Determine that compute resources in the recovery Region should be kept shut down or scaled to zero when idle (Pilot Light) to minimize cost, but must be launchable within minutes to meet the RTO.

Maintaining fully running EC2 instances (Warm Standby or Active-Active) would violate the cost optimization goal, while recreating infrastructure from scratch would violate the RTO.

Analyze database promotion and routing mechanism during failover.

Identify that promoting an Aurora Global Database secondary cluster is a fast, coordinated action (typically under a minute). Route 53 Application Recovery Controller (ARC) provides the necessary health checks and routing controls to coordinate the shift of application traffic safely.

Automated cross-region database promotion does not happen natively via Route 53 DNS policies; it requires orchestration or manual trigger, which Route 53 ARC routing controls support.

Anahtar Kavram

Selecting the appropriate disaster recovery strategy (Pilot Light vs Warm Standby vs Backup & Restore) and technology stack (Aurora Global Database, Route 53 ARC) to meet strict RTO/RPO requirements while optimizing costs.

Tahmini Süre:3m 0s

Soru 52Soru →

A financial services company hosts a report generation API on Amazon EC2 instances. The instances are managed by an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The report generation requests are computationally intensive and can take up to $180$ seconds to complete. To allow fast instance replacement during application deployments, a developer set the ALB target group's deregistration delay to $30$ seconds. However, during scale-in events, users report receiving HTTP 502 (Bad Gateway) errors for reports that were in progress.

Which modification should a solutions architect recommend to resolve these errors?

Add a rule to the private subnet's Network ACL to allow inbound traffic on ephemeral ports (

1024

65535

) from the ALB, and reduce the ASG cooldown period to

30

seconds.

Increase the deregistration delay of the ALB target group to at least

180

seconds.

Configure the ALB target group health check to use a dedicated management port instead of the traffic port, and reduce the health check interval.

Implement an Amazon Route 53 latency-based routing policy to redirect active user sessions to a secondary region during scale-in events.

Cevabı ve açıklamayı göster

Cevap: Increase the deregistration delay of the ALB target group to at least $180$ seconds.

Cevap

Increase the deregistration delay of the ALB target group to at least

180

seconds.

Increasing the deregistration delay (also known as connection draining) of the target group to match or exceed the maximum request processing time (

180

seconds) ensures that the Application Load Balancer allows in-flight requests to complete before the Auto Scaling group terminates the instance.

Adım Adım Çözüm

Analyze the cause of the HTTP 502 errors during scale-in events.

The errors occur because the target group's deregistration delay of

30

seconds is shorter than the maximum request completion time of

180

seconds, leading to premature connection termination.

Understanding the connection lifecycle is key to resolving premature terminations.

Determine the necessary configuration adjustment for the load balancer.

The deregistration delay must be increased to a value equal to or greater than

180

seconds.

This configuration tells the load balancer to wait for active requests to finish before the instances are fully terminated.

Verify if other configuration elements like Network ACLs, health checks, or DNS routing can resolve this.

None of the other options address connection draining; they either misapply network access controls, load balancer health checks, or DNS routing policies.

Deregistration delay is the specific ELB feature designed to manage connection lifecycle during scaling.

Anahtar Kavram

Deregistration delay (connection draining) ensures that a load balancer stops routing new requests to targets that are deregistering, but allows existing in-flight connections to complete before the target is fully terminated.

Soru 53Soru →

A manufacturing company is deploying a smart assembly line where automated robotic arms perform high-precision tasks. Each arm reports telemetry status messages (such as 'calibrating', 'started', and 'completed') that must be processed in the exact order they are generated for each individual arm to maintain a digital twin representation in a database. If messages are processed out of order, the digital twin state becomes corrupt. During peak production hours, the volume of telemetry messages spikes significantly. The downstream backend consists of a fleet of worker processes running in an Auto Scaling group. Which combination of steps should a solutions architect recommend to decouple the ingestion tier from the backend workers while ensuring strict ordering per assembly arm and preventing message loss? (Select TWO.)

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

Create an Amazon SQS FIFO queue and publish the telemetry events to it, using the assembly arm ID as the Message Group ID.

Configure the Auto Scaling group workers to poll the Amazon SQS FIFO queue and delete messages after they are successfully processed.

Create a standard Amazon SQS queue and publish the telemetry events using the assembly arm ID as the Message Group ID.

Create an Amazon SQS FIFO queue and publish the telemetry events using the assembly arm ID as the Message Deduplication ID.

Configure the Auto Scaling group workers to retrieve messages from a standard Amazon SQS queue, utilizing a client-side sorting library to order messages chronologically.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon SQS FIFO queue and publish the telemetry events to it, using the assembly arm ID as the Message Group ID.; Configure the Auto Scaling group workers to poll the Amazon SQS FIFO queue and delete messages after they are successfully processed.

Cevap

To satisfy the requirements, the solutions architect should create an Amazon SQS FIFO queue, publishing telemetry events with the assembly arm ID as the Message Group ID, and configure the Auto Scaling group workers to poll the SQS FIFO queue and delete messages upon successful processing.

To decouple the ingestion tier from backend workers while maintaining message order per assembly arm, a solutions architect should use an Amazon SQS FIFO queue. By using the unique assembly arm ID as the Message Group ID, SQS FIFO ensures that all messages for that specific arm are processed sequentially in the order they were received. The workers in the Auto Scaling group should poll the queue, process the messages, and delete them upon completion. When a worker is processing a message from a specific Message Group, SQS FIFO blocks other workers from receiving messages from the same group, preventing out-of-order execution.

Adım Adım Çözüm

Select a message queuing service that guarantees ordering and grouping.

Amazon SQS FIFO queue is chosen because standard queues do not guarantee FIFO ordering or support message grouping.

Maintaining digital twin states requires strict sequential processing per assembly arm.

Configure message routing parameters to segment messages by source.

Use the assembly arm ID as the Message Group ID.

This guarantees that all messages for a specific arm are processed in order, while allowing messages from different arms to be processed concurrently across multiple backend workers.

Configure the consumer worker processing logic.

Workers poll the FIFO queue and delete the message after successful processing.

Deleting the message releases the next message in the same Message Group for processing, preventing concurrency conflicts and ensuring reliable processing.

Anahtar Kavram

Amazon SQS FIFO queues use Message Group IDs to group messages that must be processed in order. SQS FIFO guarantees first-in, first-out delivery within each message group while allowing parallel processing across different groups.

Soru 54Soru →

A company is deploying a latency-sensitive gRPC microservice on a fleet of Amazon EC2 instances managed by an Auto Scaling group (ASG). The gRPC service communicates over TCP port 50051. A Network Load Balancer (NLB) distributes client traffic to these instances. The solutions architect needs to ensure that the NLB only routes traffic to healthy instances and that the ASG automatically replaces any instances where the microservice application has crashed. Which two configurations should the solutions architect implement to meet these requirements? (Select TWO.)

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

Configure the Auto Scaling group to use ELB health checks instead of the default EC2 health checks.

Configure the target group health check to use TCP protocol on port 50051.

Configure the target group health check to use HTTP protocol on port 80 to minimize CPU usage on the EC2 instances.

Configure a subnet Network ACL rule allowing inbound TCP traffic on port 50051, relying on stateful security groups to permit the return outbound health check response traffic.

Configure Amazon Route 53 with a Latency routing policy pointing to the NLB to automatically route client traffic away from individual unhealthy instances.

Cevabı ve açıklamayı göster

Cevap: Configure the Auto Scaling group to use ELB health checks instead of the default EC2 health checks.; Configure the target group health check to use TCP protocol on port 50051.

Cevap

Configure the Auto Scaling group to use ELB health checks instead of the default EC2 health checks, and configure the target group health check to use TCP protocol on port 50051.

Configuring the load balancer target group to monitor port 50051 via TCP ensures that the NLB only forwards traffic to instances where the gRPC service is active. Furthermore, changing the Auto Scaling group health check source to ELB ensures that when an instance fails the target group health checks, the ASG will automatically terminate and replace the failed instance, ensuring continuous application availability.

Adım Adım Çözüm

Analyze the health check requirements for the gRPC application.

Identify that health checks must target the active application port (50051) using TCP protocol because the application runs on port 50051 and does not listen on port 80.

This ensures the load balancer accurately identifies whether the service itself is running.

Determine the mechanism to automatically replace failed instances.

Enable ELB health checks on the Auto Scaling group.

By default, the ASG only uses EC2 status checks. Enabling ELB health checks ensures the ASG replaces instances that fail target group health checks.

Anahtar Kavram

Auto Scaling Group and Elastic Load Balancing health check synchronization for custom service ports

Soru 55Soru →

A digital music streaming provider hosts its platform backend in the us-east-1 Region. The architecture consists of an Application Load Balancer (ALB) and Amazon EC2 instances in an Auto Scaling group, with data stored in an Amazon RDS for PostgreSQL DB instance. The provider wants to implement a disaster recovery (DR) strategy in the us-west-2 Region to achieve a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. The solution must minimize ongoing infrastructure costs in the secondary region.

Which configuration will meet these requirements?

Configure a cross-region read replica of the RDS DB instance in us-west-2. Deploy a pilot light environment in us-west-2 with an Auto Scaling group set to a minimum capacity of 0. Write a script to promote the read replica, scale up the Auto Scaling group, and configure Amazon Route 53 failover routing.

Configure a cross-region read replica of the RDS DB instance in us-west-2. Deploy a warm standby environment in us-west-2 with an Auto Scaling group running at a reduced capacity of 2 instances. Configure Amazon Route 53 latency routing to route traffic to the region with the lowest latency.

Create hourly snapshots of the RDS DB instance and copy them to us-west-2. Store the snapshots in Amazon S3 Glacier Flexible Retrieval. Deploy a pilot light environment in us-west-2 with an Auto Scaling group set to a minimum capacity of 0. In a failover event, restore the database from the S3 Glacier snapshot.

Deploy a Multi-AZ DB cluster for the RDS PostgreSQL DB instance with the primary in us-east-1 and a standby replica in us-west-2. Configure an Auto Scaling group in us-west-2 to automatically launch EC2 instances when the primary region fails. Configure Amazon Route 53 failover routing.

Cevabı ve açıklamayı göster

Cevap: Configure a cross-region read replica of the RDS DB instance in us-west-2. Deploy a pilot light environment in us-west-2 with an Auto Scaling group set to a minimum capacity of 0. Write a script to promote the read replica, scale up the Auto Scaling group, and configure Amazon Route 53 failover routing.

Cevap

Configure a cross-region read replica of the RDS DB instance in us-west-2, deploy a pilot light environment in us-west-2 with an Auto Scaling group capacity of 0, and use automated scripts to promote the replica, scale up the compute resources, and update Route 53 failover routing.

The correct option uses an Amazon RDS cross-region read replica to satisfy the 5-minute RPO since database replication is asynchronous and near real-time. Deploying a pilot light environment with an Auto Scaling group capacity of 0 ensures that no EC2 instances are running during normal operations, minimizing ongoing costs. In the event of a failover, promoting the replica and scaling up the Auto Scaling group via automated scripts can easily be completed within the 15-minute RTO. Finally, Amazon Route 53 failover routing ensures traffic is redirected to the disaster recovery region.

Adım Adım Çözüm

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

Identify that cross-region read replicas use continuous asynchronous replication, keeping data lag to a few seconds, which satisfies the RPO. Hourly snapshots fail the RPO requirement.

We must ensure database changes are copied to the secondary region fast enough to meet the 5-minute RPO threshold.

Determine the most cost-effective compute deployment in the recovery region.

Choose a Pilot Light configuration where the Auto Scaling group has a minimum capacity of 0. This avoids paying for running EC2 instances during normal operations.

The scenario requires minimizing ongoing infrastructure costs, and a Pilot Light environment is cheaper than a Warm Standby.

Establish the failover mechanism to meet the 15-minute RTO.

Utilize Amazon Route 53 failover routing to automatically detect primary region failure. Write automated scripts to promote the cross-region read replica to a standalone database and scale the EC2 Auto Scaling group from 0 to its target capacity.

Manual promotion and scaling would take too long, so automation is necessary to guarantee recovery within 15 minutes.

Anahtar Kavram

Cross-Region Disaster Recovery (DR) Strategies (Pilot Light vs. Warm Standby) and RDS Replication

Soru 56Soru →

A real estate listing platform needs to process property status update events, such as 'Active', 'Under Contract', and 'Sold'. These events must be processed in strict chronological order per property to prevent data inconsistencies on the website. The volume of events is highly volatile, with massive spikes occurring when new regional properties are listed. Both the search indexing service and the email alert system must receive and process every status update. Which solution meets these requirements with the least operational overhead?

Publish the property status events to a single standard Amazon SQS queue, and configure both the search indexing service and the email alert system to poll this single queue.

Publish the property status events to an Amazon SNS FIFO topic. Subscribe two Amazon SQS FIFO queues to the SNS FIFO topic, with one queue dedicated to the search indexing service and the other to the email alert system.

Publish the property status events to a standard Amazon SNS topic. Subscribe two standard Amazon SQS queues to the SNS topic, with one queue dedicated to the search indexing service and the other to the email alert system.

Publish the property status events to an Amazon SNS topic, and write them to an Amazon DynamoDB table configured with provisioned capacity mode to store and sequence the events for downstream consumption.

Cevabı ve açıklamayı göster

Cevap: Publish the property status events to an Amazon SNS FIFO topic. Subscribe two Amazon SQS FIFO queues to the SNS FIFO topic, with one queue dedicated to the search indexing service and the other to the email alert system.

Cevap

Publish the property status events to an Amazon SNS FIFO topic, and subscribe two Amazon SQS FIFO queues to the topic (one for the search indexing service and one for the email alert system).

The correct solution uses an Amazon SNS FIFO topic to fan out the property status events to two dedicated Amazon SQS FIFO queues. SNS FIFO topics preserve the sequence of messages and can deliver them in-order to subscribed SQS FIFO queues. Having separate SQS FIFO queues for the search indexing service and the email alert system ensures that both applications independently consume every message without competition, while the queues absorb traffic spikes.

Adım Adım Çözüm

Identify the requirement for message fan-out to multiple independent consumer applications.

Two downstream services (search indexing and email alerts) must each receive every property status update.

A pub/sub model using Amazon SNS is required to fan out a single event to multiple destinations.

Determine the ordering requirements for the processed events.

Events must be processed in strict chronological order per property to avoid displaying outdated statuses.

Standard SNS and SQS do not guarantee ordering, so FIFO (First-In-First-Out) configurations must be used for both SNS and SQS.

Evaluate the integration between SNS FIFO and SQS FIFO to manage message delivery and buffering.

Subscribing SQS FIFO queues to an SNS FIFO topic maintains message grouping and ordering while providing a buffer for traffic spikes.

This architecture decouples the services, guarantees ordered delivery per property, and absorbs volatile traffic patterns with minimum operational overhead.

Anahtar Kavram

Decoupling event-driven architectures requiring multi-destination fan-out and strict message ordering.

Tahmini Süre:2m 0s

Soru 57Soru →

An enterprise energy grid monitoring company runs its real-time telemetry processing application on AWS. The application consists of Amazon ECS Fargate tasks in a private VPC subnet in us-east-1 behind an Application Load Balancer (ALB). The database tier stores state in an Amazon Aurora PostgreSQL DB cluster. The data ingest rate is highly critical, and the company requires a cross-region disaster recovery (DR) solution in us-west-2 with a Recovery Time Objective (RTO) of $15$ minutes and a Recovery Point Objective (RPO) of $1$ minute. The solution must minimize operational costs during normal operations. Which TWO actions should a solutions architect recommend to implement this DR strategy?

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

Create an Amazon Aurora Global Database from the primary database cluster. In us-west-2, deploy a secondary DB cluster containing an Amazon Aurora Serverless v2 reader instance configured with a minimum capacity of

0.5

Aurora Capacity Units (ACUs).

In us-west-2, provision the network infrastructure, the Application Load Balancer, and the Amazon ECS service with the desired task count set to 0. Create an automation workflow to scale the ECS service to the required production capacity during a failover.

In us-west-2, deploy a scaled-down Amazon ECS service running at 50% capacity, and configure an Amazon Route 53 latency-based routing policy to automatically distribute incoming traffic across both Regions during normal operations.

Configure Amazon Aurora to export hourly database snapshots to Amazon S3. Use S3 Cross-Region Replication (CRR) to replicate these snapshots to an S3 Glacier Flexible Retrieval vault in us-west-2, and write a script to restore the cluster during failover.

Create a cross-region Amazon RDS PostgreSQL read replica in us-west-2. Configure an AWS Lambda function to automatically promote this replica to a standalone primary database cluster using the RDS API during a primary Region outage.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon Aurora Global Database from the primary database cluster. In us-west-2, deploy a secondary DB cluster containing an Amazon Aurora Serverless v2 reader instance configured with a minimum capacity of $0.5$ Aurora Capacity Units (ACUs).; In us-west-2, provision the network infrastructure, the Application Load Balancer, and the Amazon ECS service with the desired task count set to 0. Create an automation workflow to scale the ECS service to the required production capacity during a failover.

Cevap

Configure an Amazon Aurora Global Database with an Aurora Serverless v2 reader in the secondary Region, and deploy the secondary ECS infrastructure with a task count of 0, scaling up only during failover.

Using an Amazon Aurora Global Database secondary cluster with a Serverless v2 reader instance allows replication to proceed with sub-second latency, ensuring the 1-minute RPO is met while keeping idle compute costs very low (

0.5

ACUs). Setting the ECS service's desired task count to 0 in the secondary Region implements a Pilot Light pattern, which eliminates active ECS compute costs during normal operations. The infrastructure can be scaled up to target capacity within the 15-minute RTO during a failover event.

Adım Adım Çözüm

Determine the database configuration required to meet the 1-minute RPO across regions.

An Amazon Aurora Global Database secondary cluster in the target Region.

Aurora Global Database replication has typical latencies of under 1 second, meeting the 1-minute RPO requirement. To minimize idle cost, deploying an Aurora Serverless v2 reader with a minimum capacity of

0.5

ACUs provides replication support without paying for full-scale provisioned instances.

Determine the application compute configuration required to meet the 15-minute RTO while minimizing running costs.

An ECS service configured in the secondary Region with desired task count set to 0 (Pilot Light strategy).

Because ECS tasks can scale up from 0 to full capacity in under 5 minutes, keeping the ECS service task count at 0 during normal operations saves compute costs while easily fitting within the 15-minute recovery timeline.

Evaluate and rule out standard backup/restore or RDS replica promotion solutions.

Reject database snapshots replicated to S3 Glacier and standard RDS read replicas.

Snapshot restore times and Glacier retrieval delays exceed the 15-minute RTO, and snapshots fail the 1-minute RPO. Standard RDS read replicas are incompatible with Aurora clusters and lack the seamless managed global database failover mechanism.

Anahtar Kavram

Disaster recovery (DR) strategies, specifically Pilot Light database replication and scaled-down ECS Fargate deployments, to meet strict RTO/RPO targets while minimizing idle costs.

Soru 58Soru →

A healthcare provider is designing a medical imaging pipeline. When a clinic uploads a raw MRI scan ( $50 \text{ MB}$ to $200 \text{ MB}$ ) to an Amazon S3 bucket, the scan must be processed by a cluster of CPU-intensive workers. The processing tasks must be handled asynchronously. Due to compliance requirements, the scans must be processed in the exact order they are received by the system to ensure correct chronological correlation, and no scan should be processed more than once. The upload volume can peak unexpectedly, and processing can take up to $12$ minutes per scan.

Which solution meets these requirements with the least operational overhead?

Configure an Amazon S3 event notification to publish ObjectCreated events directly to an Amazon SQS FIFO queue. Configure the workers to consume messages from the FIFO queue.

Configure an Amazon S3 event notification to publish ObjectCreated events directly to an Amazon SQS standard queue. Configure the workers to consume messages from the standard queue.

Enable Amazon EventBridge notifications on the Amazon S3 bucket. Create an EventBridge rule that routes S3 ObjectCreated events to an Amazon SQS FIFO queue, and configure the workers to consume messages from the FIFO queue.

Configure an Amazon S3 event notification to trigger an AWS Lambda function that downloads the scan, performs the CPU-intensive processing directly within the function, and saves the result to another S3 bucket.

Cevabı ve açıklamayı göster

Cevap: Enable Amazon EventBridge notifications on the Amazon S3 bucket. Create an EventBridge rule that routes S3 ObjectCreated events to an Amazon SQS FIFO queue, and configure the workers to consume messages from the FIFO queue.

Cevap

The correct solution uses Amazon S3 EventBridge integration. Because Amazon S3 cannot publish events directly to an Amazon SQS FIFO queue, enabling EventBridge notifications on the bucket allows S3 to emit events to the default event bus. An EventBridge rule can then match these events and route them to an SQS FIFO queue. The SQS FIFO queue guarantees that the messages are processed in the order they were uploaded (first-in, first-out) and prevents duplicate processing (exactly-once processing) through deduplication. This architecture is asynchronous and serverless, minimizing operational overhead.

Adım Adım Çözüm

Enable Amazon EventBridge notifications on the source Amazon S3 bucket.

S3 events are sent to the default EventBridge event bus.

S3 event notifications cannot target SQS FIFO queues directly, so EventBridge must be used as an intermediary.

Create an Amazon EventBridge rule that filters for ObjectCreated events on the specific S3 bucket and targets the SQS FIFO queue.

Object upload events are successfully formatted and routed to the FIFO queue.

EventBridge supports SQS FIFO queues as a target and retains metadata necessary for deduplication and ordering.

Configure the workers to consume messages from the SQS FIFO queue and delete them after successful processing.

The scans are processed in order, and the message visibility timeout prevents duplicate processing.

The SQS FIFO queue enforces first-in, first-out delivery and exactly-once processing by utilizing message deduplication IDs.

Anahtar Kavram

Using Amazon EventBridge to bridge S3 event notifications with Amazon SQS FIFO queues for strict ordering and deduplication.

Soru 59Soru →

A company hosts an internal inventory management service on Amazon EC2 instances within an Auto Scaling group (ASG). The service runs behind an internal Application Load Balancer (ALB) and is configured to listen on custom TCP port 5000. The solutions architect must ensure that the ALB can successfully monitor the health of the application on the instances and route traffic to them securely.

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

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

Configure the target group to perform health checks on the traffic port or explicitly on port 5000.

Configure the security group attached to the EC2 instances to allow inbound TCP traffic on port 5000 from the security group of the ALB.

Configure the target group health check to query the default HTTP port 80 to separate health check traffic from client traffic.

Configure stateless Network Access Control Lists (NACLs) at the subnet level to permit inbound traffic on port 5000, relying on NACL statefulness for return traffic.

Configure an Amazon Route 53 latency routing policy pointing to the load balancer to automatically route users away from unhealthy targets without setting up active health checks.

Cevabı ve açıklamayı göster

Cevap: Configure the target group to perform health checks on the traffic port or explicitly on port 5000.; Configure the security group attached to the EC2 instances to allow inbound TCP traffic on port 5000 from the security group of the ALB.

Cevap

The solutions architect should configure the target group to perform health checks on port 5000 and configure the security group of the EC2 instances to allow inbound traffic on port 5000 from the security group of the Application Load Balancer.

To ensure that the Application Load Balancer can route traffic to and verify the health of the custom service, the target group health checks must query the port where the application is running, which is port 5000. Additionally, the security group of the EC2 instances must permit inbound traffic on port 5000 specifically from the security group of the load balancer to secure the network path and allow traffic flow.

Adım Adım Çözüm

Determine the application port configuration.

The application listens on custom port 5000.

Health checks must be sent to the port where the application is actually running (port 5000) so that the load balancer does not falsely mark the targets as unhealthy.

Configure instance-level security.

Allow inbound traffic on port 5000 from the ALB's security group.

Since the ALB routes requests to the instances on port 5000, the instances' security group must permit this inbound traffic. Referencing the ALB's security group directly ensures least-privilege access.

Anahtar Kavram

Auto Scaling and Application Load Balancer custom port routing and health check configuration

Soru 60Soru →

A financial technology company is designing a transaction processing application. When a customer initiates a fund transfer, the transaction must be processed asynchronously in the exact order it was received to prevent account balance discrepancies. The architecture must decouple the frontend web portal from the backend processing servers to handle traffic peaks without losing messages. Which TWO components should a solutions architect recommend to satisfy these requirements? (Select TWO).

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

Amazon SQS FIFO queue to store the incoming transactions in strict order.

An Auto Scaling group of EC2 instances acting as backend workers that poll the queue.

Amazon SQS Standard queue to buffer the transaction requests.

Amazon RDS Read Replicas configured as the primary write target for failover.

Amazon DynamoDB configured with Provisioned Capacity Mode to scale dynamically for unpredictable traffic spikes.

Cevabı ve açıklamayı göster

Cevap: Amazon SQS FIFO queue to store the incoming transactions in strict order.; An Auto Scaling group of EC2 instances acting as backend workers that poll the queue.

Cevap

The correct architecture uses an Amazon SQS FIFO queue to store and sequence transaction requests, combined with an Auto Scaling group of EC2 worker instances that poll the queue to process messages asynchronously.

The correct solution leverages an Amazon SQS FIFO queue to guarantee first-in, first-out message sequencing and prevent duplicate processing, ensuring the transaction order is maintained. To handle the asynchronous processing and scaling requirements, an Auto Scaling group of EC2 worker instances polls the SQS queue and scales dynamically based on workload demand.

Adım Adım Çözüm

Identify the ordering constraint for the asynchronous transaction requests.

Since messages must be processed in the exact order they are received, an Amazon SQS FIFO queue is required instead of a Standard queue.

Standard queues do not guarantee message ordering, whereas FIFO queues preserve order and prevent duplicate delivery.

Determine the mechanism for decoupling and processing messages asynchronously.

Backend workers hosted on EC2 instances can be grouped in an Auto Scaling group to poll the SQS queue.

This allows the backend to scale independently based on the number of messages in the queue (queue depth), decoupling the front-end submission from the backend processing.

Anahtar Kavram

Decoupling message-driven architectures while guaranteeing strict message ordering using Amazon SQS FIFO queues.

ÖncekiSayfa 3 / 20Sonraki

Design Resilient Architectures

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram