Amazon AWS Certified Solutions Architect - Associate SAA-C03 Bundle

The option Set the correct schedule invocation role and target permission addresses a separate condition: an EventBridge schedule is created but its target receives access denied. Scheduled target invocation requires an authorized role. The actual requirement is an on-demand batch process should not run while no jobs exist. Recommended corrective action: Scale AWS Batch or serverless workers from queue/work demand. Demand-driven compute reduces idle resources.

Select FIFO message groups keyed by customer while allowing independent parallelism would help if a queue worker only needs to process one customer's messages in order. Per-group ordering limits parallel processing only inside that group. That is not the symptom described here: an on-demand batch process should not run while no jobs exist. The matching response is Scale AWS Batch or serverless workers from queue/work demand, because demand-driven compute reduces idle resources.

Use Systems Manager Automation with approval and IAM guardrails where appropriate solves a different operational problem where a workflow executes manual operations across many machines in one account. SSM Automation manages controlled operational runbooks. It does not directly address an on-demand batch process should not run while no jobs exist. The case calls for Scale AWS Batch or serverless workers from queue/work demand, since demand-driven compute reduces idle resources.

Use snapshots or a replicated state architecture for cross-AZ recovery would help if an EBS volume is expected to fail over directly between EC2 instances in different AZs. EBS volumes are AZ-scoped and are not movable live across AZs. That is not the symptom described here: a web tier resides in only one Availability Zone and the AZ fails during peak demand. The matching response is Distribute healthy targets across two or more AZs behind an ALB, because multi-AZ target placement removes a single-AZ web-tier failure.

For the alternative failure the application's EC2 Auto Scaling group is configured for only one subnet, the control Configure the ASG with subnets in multiple AZs is relevant: aSG placement across AZs enables healthy capacity replacement. Here the evidence instead is a web tier resides in only one Availability Zone and the AZ fails during peak demand. The selected technical mechanism is Distribute healthy targets across two or more AZs behind an ALB: multi-AZ target placement removes a single-AZ web-tier failure.

The competing option Correct health checks and remove unhealthy targets from routing would be useful when a load balancer has targets in two AZs but one target is unhealthy and still receives traffic. Load balancers route according to supported target health. The present issue is a web tier resides in only one Availability Zone and the AZ fails during peak demand; it is more directly addressed by Distribute healthy targets across two or more AZs behind an ALB. Multi-AZ target placement removes a single-AZ web-tier failure.

For the alternative failure an EBS volume is expected to fail over directly between EC2 instances in different AZs, the control Use snapshots or a replicated state architecture for cross-AZ recovery is relevant: eBS volumes are AZ-scoped and are not movable live across AZs. Here the evidence instead is the application's EC2 Auto Scaling group is configured for only one subnet. The selected technical mechanism is Configure the ASG with subnets in multiple AZs: aSG placement across AZs enables healthy capacity replacement.

Distribute healthy targets across two or more AZs behind an ALB solves a different operational problem where a web tier resides in only one Availability Zone and the AZ fails during peak demand. Multi-AZ target placement removes a single-AZ web-tier failure. It does not directly address the application's EC2 Auto Scaling group is configured for only one subnet. The case calls for Configure the ASG with subnets in multiple AZs, since aSG placement across AZs enables healthy capacity replacement.

The competing option Correct health checks and remove unhealthy targets from routing would be useful when a load balancer has targets in two AZs but one target is unhealthy and still receives traffic. Load balancers route according to supported target health. The present issue is the application's EC2 Auto Scaling group is configured for only one subnet; it is more directly addressed by Configure the ASG with subnets in multiple AZs. ASG placement across AZs enables healthy capacity replacement.

The competing option Use snapshots or a replicated state architecture for cross-AZ recovery would be useful when an EBS volume is expected to fail over directly between EC2 instances in different AZs. EBS volumes are AZ-scoped and are not movable live across AZs. The present issue is a load balancer has targets in two AZs but one target is unhealthy and still receives traffic; it is more directly addressed by Correct health checks and remove unhealthy targets from routing. Load balancers route according to supported target health.

The option Configure the ASG with subnets in multiple AZs addresses a separate condition: the application's EC2 Auto Scaling group is configured for only one subnet. ASG placement across AZs enables healthy capacity replacement. The actual requirement is a load balancer has targets in two AZs but one target is unhealthy and still receives traffic. Recommended corrective action: Correct health checks and remove unhealthy targets from routing. Load balancers route according to supported target health.

Provision appropriate per-AZ NAT gateways with resilient route-table design would help if a private subnet's NAT gateway sits in an AZ that later fails. NAT gateway placement affects egress availability from each AZ. That is not the symptom described here: a load balancer has targets in two AZs but one target is unhealthy and still receives traffic. The matching response is Correct health checks and remove unhealthy targets from routing, because load balancers route according to supported target health.

The option Correct health checks and remove unhealthy targets from routing addresses a separate condition: a load balancer has targets in two AZs but one target is unhealthy and still receives traffic. Load balancers route according to supported target health. The actual requirement is a private subnet's NAT gateway sits in an AZ that later fails. Recommended corrective action: Provision appropriate per-AZ NAT gateways with resilient route-table design. NAT gateway placement affects egress availability from each AZ.

Use snapshots or a replicated state architecture for cross-AZ recovery would help if an EBS volume is expected to fail over directly between EC2 instances in different AZs. EBS volumes are AZ-scoped and are not movable live across AZs. That is not the symptom described here: a private subnet's NAT gateway sits in an AZ that later fails. The matching response is Provision appropriate per-AZ NAT gateways with resilient route-table design, because nAT gateway placement affects egress availability from each AZ.

For the alternative failure a web tier resides in only one Availability Zone and the AZ fails during peak demand, the control Distribute healthy targets across two or more AZs behind an ALB is relevant: multi-AZ target placement removes a single-AZ web-tier failure. Here the evidence instead is a private subnet's NAT gateway sits in an AZ that later fails. The selected technical mechanism is Provision appropriate per-AZ NAT gateways with resilient route-table design: nAT gateway placement affects egress availability from each AZ.

Correct health checks and remove unhealthy targets from routing would help if a load balancer has targets in two AZs but one target is unhealthy and still receives traffic. Load balancers route according to supported target health. That is not the symptom described here: an EBS volume is expected to fail over directly between EC2 instances in different AZs. The matching response is Use snapshots or a replicated state architecture for cross-AZ recovery, because eBS volumes are AZ-scoped and are not movable live across AZs.

For the alternative failure a web tier resides in only one Availability Zone and the AZ fails during peak demand, the control Distribute healthy targets across two or more AZs behind an ALB is relevant: multi-AZ target placement removes a single-AZ web-tier failure. Here the evidence instead is an EBS volume is expected to fail over directly between EC2 instances in different AZs. The selected technical mechanism is Use snapshots or a replicated state architecture for cross-AZ recovery: eBS volumes are AZ-scoped and are not movable live across AZs.

Provision appropriate per-AZ NAT gateways with resilient route-table design solves a different operational problem where a private subnet's NAT gateway sits in an AZ that later fails. NAT gateway placement affects egress availability from each AZ. It does not directly address an EBS volume is expected to fail over directly between EC2 instances in different AZs. The case calls for Use snapshots or a replicated state architecture for cross-AZ recovery, since eBS volumes are AZ-scoped and are not movable live across AZs.

Copy automated backups or snapshots to another Region using supported workflows would help if a regional outage must not destroy the last copy of critical database backups. Cross-Region copies provide geographic recovery. That is not the symptom described here: the only RDS database instance fails and no standby is configured. The matching response is Enable RDS Multi-AZ deployment with supported automatic failover, because multi-AZ maintains a standby for availability.

For the alternative failure an application opens new connections to a failed RDS host using cached addresses, the control Reconnect through the RDS endpoint with appropriate DNS caching behavior is relevant: managed failover uses endpoint DNS changes rather than fixed instance IPs. Here the evidence instead is the only RDS database instance fails and no standby is configured. The selected technical mechanism is Enable RDS Multi-AZ deployment with supported automatic failover: multi-AZ maintains a standby for availability.

The competing option Create appropriate RDS read replicas for read scaling would be useful when analysts need read capacity without expecting a standby to serve queries. Read replicas are designed for read workloads, unlike a traditional standby. The present issue is the only RDS database instance fails and no standby is configured; it is more directly addressed by Enable RDS Multi-AZ deployment with supported automatic failover. Multi-AZ maintains a standby for availability.

For the alternative failure engineers assume Multi-AZ eliminates the need for logical backups before bad UPDATE statements, the control Keep automated backups/PITR and tested recovery procedures alongside HA is relevant: replicated corruption or user mistakes still require point-in-time recovery. Here the evidence instead is an application opens new connections to a failed RDS host using cached addresses. The selected technical mechanism is Reconnect through the RDS endpoint with appropriate DNS caching behavior: managed failover uses endpoint DNS changes rather than fixed instance IPs.

Enable RDS Multi-AZ deployment with supported automatic failover solves a different operational problem where the only RDS database instance fails and no standby is configured. Multi-AZ maintains a standby for availability. It does not directly address an application opens new connections to a failed RDS host using cached addresses. The case calls for Reconnect through the RDS endpoint with appropriate DNS caching behavior, since managed failover uses endpoint DNS changes rather than fixed instance IPs.

The option Create appropriate RDS read replicas for read scaling addresses a separate condition: analysts need read capacity without expecting a standby to serve queries. Read replicas are designed for read workloads, unlike a traditional standby. The actual requirement is an application opens new connections to a failed RDS host using cached addresses. Recommended corrective action: Reconnect through the RDS endpoint with appropriate DNS caching behavior. Managed failover uses endpoint DNS changes rather than fixed instance IPs.

Reconnect through the RDS endpoint with appropriate DNS caching behavior solves a different operational problem where an application opens new connections to a failed RDS host using cached addresses. Managed failover uses endpoint DNS changes rather than fixed instance IPs. It does not directly address analysts need read capacity without expecting a standby to serve queries. The case calls for Create appropriate RDS read replicas for read scaling, since read replicas are designed for read workloads, unlike a traditional standby.

The competing option Keep automated backups/PITR and tested recovery procedures alongside HA would be useful when engineers assume Multi-AZ eliminates the need for logical backups before bad UPDATE statements. Replicated corruption or user mistakes still require point-in-time recovery. The present issue is analysts need read capacity without expecting a standby to serve queries; it is more directly addressed by Create appropriate RDS read replicas for read scaling. Read replicas are designed for read workloads, unlike a traditional standby.

The option Copy automated backups or snapshots to another Region using supported workflows addresses a separate condition: a regional outage must not destroy the last copy of critical database backups. Cross-Region copies provide geographic recovery. The actual requirement is analysts need read capacity without expecting a standby to serve queries. Recommended corrective action: Create appropriate RDS read replicas for read scaling. Read replicas are designed for read workloads, unlike a traditional standby.

The competing option Create appropriate RDS read replicas for read scaling would be useful when analysts need read capacity without expecting a standby to serve queries. Read replicas are designed for read workloads, unlike a traditional standby. The present issue is a regional outage must not destroy the last copy of critical database backups; it is more directly addressed by Copy automated backups or snapshots to another Region using supported workflows. Cross-Region copies provide geographic recovery.

The option Enable RDS Multi-AZ deployment with supported automatic failover addresses a separate condition: the only RDS database instance fails and no standby is configured. Multi-AZ maintains a standby for availability. The actual requirement is a regional outage must not destroy the last copy of critical database backups. Recommended corrective action: Copy automated backups or snapshots to another Region using supported workflows. Cross-Region copies provide geographic recovery.

For the alternative failure an application opens new connections to a failed RDS host using cached addresses, the control Reconnect through the RDS endpoint with appropriate DNS caching behavior is relevant: managed failover uses endpoint DNS changes rather than fixed instance IPs. Here the evidence instead is a regional outage must not destroy the last copy of critical database backups. The selected technical mechanism is Copy automated backups or snapshots to another Region using supported workflows: cross-Region copies provide geographic recovery.

The option Reconnect through the RDS endpoint with appropriate DNS caching behavior addresses a separate condition: an application opens new connections to a failed RDS host using cached addresses. Managed failover uses endpoint DNS changes rather than fixed instance IPs. The actual requirement is engineers assume Multi-AZ eliminates the need for logical backups before bad UPDATE statements. Recommended corrective action: Keep automated backups/PITR and tested recovery procedures alongside HA. Replicated corruption or user mistakes still require point-in-time recovery.

Copy automated backups or snapshots to another Region using supported workflows would help if a regional outage must not destroy the last copy of critical database backups. Cross-Region copies provide geographic recovery. That is not the symptom described here: engineers assume Multi-AZ eliminates the need for logical backups before bad UPDATE statements. The matching response is Keep automated backups/PITR and tested recovery procedures alongside HA, because replicated corruption or user mistakes still require point-in-time recovery.

Enable RDS Multi-AZ deployment with supported automatic failover solves a different operational problem where the only RDS database instance fails and no standby is configured. Multi-AZ maintains a standby for availability. It does not directly address engineers assume Multi-AZ eliminates the need for logical backups before bad UPDATE statements. The case calls for Keep automated backups/PITR and tested recovery procedures alongside HA, since replicated corruption or user mistakes still require point-in-time recovery.