Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

For the separate situation A high-traffic service expects thousands of Lambda invocations but unexpectedly hits regional concurrency throttling, Model and request appropriate Lambda concurrency capacity while protecting downstream limits could be useful. Concurrency quotas can cap execution independently of workload demand.

Expand subnet CIDR capacity and plan ENI/IP requirements for task scaling solves the related scenario A production ECS service cannot launch enough tasks because the VPC subnets run out of IPs; container network interfaces consume address capacity during elastic scale-out.

Although Introduce RDS Proxy or bounded client pooling with safe concurrency limits can be valid when An RDS connection storm overwhelms the writer after many Lambda functions scale out, it targets a different technical condition. Database connection pools protect the backend from bursty client creation.

Document and rehearse write endpoint updates and conflict-aware regional recovery solves the related scenario An Aurora Global Database failover requires choosing a new primary region and replaying the application write path; global replication and writer relocation require controlled failover procedures.

Although Delete the SQS message only after durable idempotent processing completes can be valid when An SQS consumer acknowledges a job before committing its database transaction, then crashes, it targets a different technical condition. Early deletion risks losing unfinished work even though the queue is durable.

This alternative, Use strongly consistent reads in the same-region table where supported, is appropriate when A critical DynamoDB read after a write uses an eventually consistent read and returns the prior value. Strongly consistent table reads can avoid stale values after committed writes in a Region.

Although Document and rehearse write endpoint updates and conflict-aware regional recovery can be valid when An Aurora Global Database failover requires choosing a new primary region and replaying the application write path, it targets a different technical condition. Global replication and writer relocation require controlled failover procedures.

This alternative, Delete the SQS message only after durable idempotent processing completes, is appropriate when An SQS consumer acknowledges a job before committing its database transaction, then crashes. Early deletion risks losing unfinished work even though the queue is durable.

For the separate situation A multi-region S3 disaster-recovery plan assumes replication is instantaneous for every object, Monitor S3 replication metrics and define an RPO that tolerates actual asynchronous lag could be useful. S3 replication can be delayed and does not guarantee zero-lag copies.

Use strongly consistent reads in the same-region table where supported would address a different requirement: A critical DynamoDB read after a write uses an eventually consistent read and returns the prior value. Strongly consistent table reads can avoid stale values after committed writes in a Region.

For the separate situation A multi-region S3 disaster-recovery plan assumes replication is instantaneous for every object, Monitor S3 replication metrics and define an RPO that tolerates actual asynchronous lag could be useful. S3 replication can be delayed and does not guarantee zero-lag copies.

Account for asynchronous replica lag in writer promotion and application recovery solves the related scenario An RDS read replica is promoted after a writer outage but a few committed writes are missing; read-replica promotion can lose writes that were not replicated before failure.

This alternative, Monitor S3 replication metrics and define an RPO that tolerates actual asynchronous lag, is appropriate when A multi-region S3 disaster-recovery plan assumes replication is instantaneous for every object. S3 replication can be delayed and does not guarantee zero-lag copies.

Document and rehearse write endpoint updates and conflict-aware regional recovery solves the related scenario An Aurora Global Database failover requires choosing a new primary region and replaying the application write path; global replication and writer relocation require controlled failover procedures.

Although Use strongly consistent reads in the same-region table where supported can be valid when A critical DynamoDB read after a write uses an eventually consistent read and returns the prior value, it targets a different technical condition. Strongly consistent table reads can avoid stale values after committed writes in a Region.

For the separate situation An Aurora Global Database failover requires choosing a new primary region and replaying the application write path, Document and rehearse write endpoint updates and conflict-aware regional recovery could be useful. Global replication and writer relocation require controlled failover procedures.

Delete the SQS message only after durable idempotent processing completes solves the related scenario An SQS consumer acknowledges a job before committing its database transaction, then crashes; early deletion risks losing unfinished work even though the queue is durable.

Account for asynchronous replica lag in writer promotion and application recovery would address a different requirement: An RDS read replica is promoted after a writer outage but a few committed writes are missing. Read-replica promotion can lose writes that were not replicated before failure.

Although Add meaningful endpoint health checks to regional Route 53 latency records can be valid when An application uses latency routing without checking health and sends users to a failed low-latency Region, it targets a different technical condition. Health-aware latency routing avoids selecting an unavailable low-latency target.

Remove the shared identity single point with resilient federated access and tested fallback would address a different requirement: A disaster-recovery design publishes two Regions but both depend on the same sole corporate identity server. Multi-region compute cannot compensate for a shared unavailable authentication dependency.

This alternative, Review DNS TTLs, health-check recovery times and client connection persistence, is appropriate when A regional active-passive design fails over only after DNS caches retain the old answer too long. DNS propagation and client caching affect real failover duration.

This alternative, Remove the shared identity single point with resilient federated access and tested fallback, is appropriate when A disaster-recovery design publishes two Regions but both depend on the same sole corporate identity server. Multi-region compute cannot compensate for a shared unavailable authentication dependency.

For the separate situation An EC2-backed application survives AZ failure but S3 access fails because route tables point through a dead NAT gateway, Add gateway VPC endpoints and AZ-resilient network routes for AWS dependencies could be useful. Endpoint paths remove a fragile zonal NAT dependency from regional S3 access.

Add meaningful endpoint health checks to regional Route 53 latency records solves the related scenario An application uses latency routing without checking health and sends users to a failed low-latency Region; health-aware latency routing avoids selecting an unavailable low-latency target.

This alternative, Probe a representative application transaction endpoint and alert on business failures, is appropriate when A Route 53 failover health check tests a static home page but misses failed checkout transactions. A shallow endpoint can appear healthy while essential application behavior is broken.

Review DNS TTLs, health-check recovery times and client connection persistence solves the related scenario A regional active-passive design fails over only after DNS caches retain the old answer too long; dNS propagation and client caching affect real failover duration.

Although Add meaningful endpoint health checks to regional Route 53 latency records can be valid when An application uses latency routing without checking health and sends users to a failed low-latency Region, it targets a different technical condition. Health-aware latency routing avoids selecting an unavailable low-latency target.

Review DNS TTLs, health-check recovery times and client connection persistence solves the related scenario A regional active-passive design fails over only after DNS caches retain the old answer too long; dNS propagation and client caching affect real failover duration.

Although Remove the shared identity single point with resilient federated access and tested fallback can be valid when A disaster-recovery design publishes two Regions but both depend on the same sole corporate identity server, it targets a different technical condition. Multi-region compute cannot compensate for a shared unavailable authentication dependency.

Probe a representative application transaction endpoint and alert on business failures would address a different requirement: A Route 53 failover health check tests a static home page but misses failed checkout transactions. A shallow endpoint can appear healthy while essential application behavior is broken.

Add meaningful endpoint health checks to regional Route 53 latency records solves the related scenario An application uses latency routing without checking health and sends users to a failed low-latency Region; health-aware latency routing avoids selecting an unavailable low-latency target.

Although Probe a representative application transaction endpoint and alert on business failures can be valid when A Route 53 failover health check tests a static home page but misses failed checkout transactions, it targets a different technical condition. A shallow endpoint can appear healthy while essential application behavior is broken.

This alternative, Add gateway VPC endpoints and AZ-resilient network routes for AWS dependencies, is appropriate when An EC2-backed application survives AZ failure but S3 access fails because route tables point through a dead NAT gateway. Endpoint paths remove a fragile zonal NAT dependency from regional S3 access.