Amazon AWS Certified Solutions Architect - Associate SAA-C03 Bundle

The option Add TGW attachment subnets in required AZs with route design addresses a separate condition: a transit-gateway attachment in one AZ becomes a bottleneck for regional traffic. Multi-AZ attachment design extends path availability. The actual requirement is an application route remains pointed at a dead EC2 NAT instance. Recommended corrective action: Implement monitored failover or replace with managed NAT gateways. Managed egress reduces failure handling that self-managed NAT requires.

Configure customer gateway routing/failover across both managed VPN tunnels would help if a branch VPN relies on a single tunnel although AWS provides two tunnels. Dual tunnels provide alternative encrypted paths. That is not the symptom described here: an application route remains pointed at a dead EC2 NAT instance. The matching response is Implement monitored failover or replace with managed NAT gateways, because managed egress reduces failure handling that self-managed NAT requires.

For the alternative failure a Direct Connect circuit is the only path into AWS and its provider fails, the control Deploy redundant Direct Connect and/or VPN backup paths is relevant: independent network paths mitigate single-link failures. Here the evidence instead is an application route remains pointed at a dead EC2 NAT instance. The selected technical mechanism is Implement monitored failover or replace with managed NAT gateways: managed egress reduces failure handling that self-managed NAT requires.

Use supported checkpointing and durable state storage would help if a streaming app requires recovery of processing state after restart. Persistent checkpoints support fault-tolerant stream processors. That is not the symptom described here: a Kinesis consumer fails for two hours and must replay missed data. The matching response is Set suitable stream retention and resume from stored checkpoints, because a retained ordered stream supports replay.

For the alternative failure an event publisher sends messages faster than downstream processing for ten minutes, the control Buffer data in SQS with resilient consumers is relevant: queues absorb transient bursts. Here the evidence instead is a Kinesis consumer fails for two hours and must replay missed data. The selected technical mechanism is Set suitable stream retention and resume from stored checkpoints: a retained ordered stream supports replay.

The competing option Split/recover failed batch items and use DLQ handling would be useful when poison messages repeatedly poison one worker batch. Partial batch failure management isolates records without replaying good work. The present issue is a Kinesis consumer fails for two hours and must replay missed data; it is more directly addressed by Set suitable stream retention and resume from stored checkpoints. A retained ordered stream supports replay.

For the alternative failure poison messages repeatedly poison one worker batch, the control Split/recover failed batch items and use DLQ handling is relevant: partial batch failure management isolates records without replaying good work. Here the evidence instead is an event publisher sends messages faster than downstream processing for ten minutes. The selected technical mechanism is Buffer data in SQS with resilient consumers: queues absorb transient bursts.

Set suitable stream retention and resume from stored checkpoints solves a different operational problem where a Kinesis consumer fails for two hours and must replay missed data. A retained ordered stream supports replay. It does not directly address an event publisher sends messages faster than downstream processing for ten minutes. The case calls for Buffer data in SQS with resilient consumers, since queues absorb transient bursts.

The option Use supported checkpointing and durable state storage addresses a separate condition: a streaming app requires recovery of processing state after restart. Persistent checkpoints support fault-tolerant stream processors. The actual requirement is an event publisher sends messages faster than downstream processing for ten minutes. Recommended corrective action: Buffer data in SQS with resilient consumers. Queues absorb transient bursts.

Set suitable stream retention and resume from stored checkpoints solves a different operational problem where a Kinesis consumer fails for two hours and must replay missed data. A retained ordered stream supports replay. It does not directly address a consumer depends on downstream APIs that throttle under load. The case calls for Use bounded retries with exponential backoff and jitter, since distributed retries should avoid synchronized amplification.

The competing option Split/recover failed batch items and use DLQ handling would be useful when poison messages repeatedly poison one worker batch. Partial batch failure management isolates records without replaying good work. The present issue is a consumer depends on downstream APIs that throttle under load; it is more directly addressed by Use bounded retries with exponential backoff and jitter. Distributed retries should avoid synchronized amplification.

The option Buffer data in SQS with resilient consumers addresses a separate condition: an event publisher sends messages faster than downstream processing for ten minutes. Queues absorb transient bursts. The actual requirement is a consumer depends on downstream APIs that throttle under load. Recommended corrective action: Use bounded retries with exponential backoff and jitter. Distributed retries should avoid synchronized amplification.

The competing option Use supported checkpointing and durable state storage would be useful when a streaming app requires recovery of processing state after restart. Persistent checkpoints support fault-tolerant stream processors. The present issue is poison messages repeatedly poison one worker batch; it is more directly addressed by Split/recover failed batch items and use DLQ handling. Partial batch failure management isolates records without replaying good work.

The option Use bounded retries with exponential backoff and jitter addresses a separate condition: a consumer depends on downstream APIs that throttle under load. Distributed retries should avoid synchronized amplification. The actual requirement is poison messages repeatedly poison one worker batch. Recommended corrective action: Split/recover failed batch items and use DLQ handling. Partial batch failure management isolates records without replaying good work.

Buffer data in SQS with resilient consumers would help if an event publisher sends messages faster than downstream processing for ten minutes. Queues absorb transient bursts. That is not the symptom described here: poison messages repeatedly poison one worker batch. The matching response is Split/recover failed batch items and use DLQ handling, because partial batch failure management isolates records without replaying good work.

The option Use bounded retries with exponential backoff and jitter addresses a separate condition: a consumer depends on downstream APIs that throttle under load. Distributed retries should avoid synchronized amplification. The actual requirement is a streaming app requires recovery of processing state after restart. Recommended corrective action: Use supported checkpointing and durable state storage. Persistent checkpoints support fault-tolerant stream processors.

Buffer data in SQS with resilient consumers would help if an event publisher sends messages faster than downstream processing for ten minutes. Queues absorb transient bursts. That is not the symptom described here: a streaming app requires recovery of processing state after restart. The matching response is Use supported checkpointing and durable state storage, because persistent checkpoints support fault-tolerant stream processors.

Set suitable stream retention and resume from stored checkpoints solves a different operational problem where a Kinesis consumer fails for two hours and must replay missed data. A retained ordered stream supports replay. It does not directly address a streaming app requires recovery of processing state after restart. The case calls for Use supported checkpointing and durable state storage, since persistent checkpoints support fault-tolerant stream processors.

Use managed ACM certificates and tested renewal validation would help if a single customer-hosted certificate renewal outage breaks HTTPS for every region. Certificate lifecycle affects global entry reliability. That is not the symptom described here: a regional ALB is unavailable but public DNS still points only to it. The matching response is Use health-aware Route 53 failover or Global Accelerator region endpoints, because health-based routing avoids a failed region.

Configure multi-region origin/storage failover with compatible CloudFront behavior solves a different operational problem where critical static files must remain accessible during an S3 origin region outage. Geo-redundant origins improve availability. It does not directly address a regional ALB is unavailable but public DNS still points only to it. The case calls for Use health-aware Route 53 failover or Global Accelerator region endpoints, since health-based routing avoids a failed region.

The competing option Create an appropriate regional data DR strategy, not only a CDN would be useful when an application's database is only in one region while edge caches exist worldwide. Edge caching does not protect the underlying database state. The present issue is a regional ALB is unavailable but public DNS still points only to it; it is more directly addressed by Use health-aware Route 53 failover or Global Accelerator region endpoints. Health-based routing avoids a failed region.

For the alternative failure critical static files must remain accessible during an S3 origin region outage, the control Configure multi-region origin/storage failover with compatible CloudFront behavior is relevant: geo-redundant origins improve availability. Here the evidence instead is users around the globe see high latency fetching static content. The selected technical mechanism is Cache static assets at CloudFront edge locations: cDN caching reduces origin latency and load.

Use managed ACM certificates and tested renewal validation solves a different operational problem where a single customer-hosted certificate renewal outage breaks HTTPS for every region. Certificate lifecycle affects global entry reliability. It does not directly address users around the globe see high latency fetching static content. The case calls for Cache static assets at CloudFront edge locations, since cDN caching reduces origin latency and load.

The competing option Create an appropriate regional data DR strategy, not only a CDN would be useful when an application's database is only in one region while edge caches exist worldwide. Edge caching does not protect the underlying database state. The present issue is users around the globe see high latency fetching static content; it is more directly addressed by Cache static assets at CloudFront edge locations. CDN caching reduces origin latency and load.

The competing option Use health-aware Route 53 failover or Global Accelerator region endpoints would be useful when a regional ALB is unavailable but public DNS still points only to it. Health-based routing avoids a failed region. The present issue is critical static files must remain accessible during an S3 origin region outage; it is more directly addressed by Configure multi-region origin/storage failover with compatible CloudFront behavior. Geo-redundant origins improve availability.

The option Cache static assets at CloudFront edge locations addresses a separate condition: users around the globe see high latency fetching static content. CDN caching reduces origin latency and load. The actual requirement is critical static files must remain accessible during an S3 origin region outage. Recommended corrective action: Configure multi-region origin/storage failover with compatible CloudFront behavior. Geo-redundant origins improve availability.

Create an appropriate regional data DR strategy, not only a CDN would help if an application's database is only in one region while edge caches exist worldwide. Edge caching does not protect the underlying database state. That is not the symptom described here: critical static files must remain accessible during an S3 origin region outage. The matching response is Configure multi-region origin/storage failover with compatible CloudFront behavior, because geo-redundant origins improve availability.

The competing option Cache static assets at CloudFront edge locations would be useful when users around the globe see high latency fetching static content. CDN caching reduces origin latency and load. The present issue is a single customer-hosted certificate renewal outage breaks HTTPS for every region; it is more directly addressed by Use managed ACM certificates and tested renewal validation. Certificate lifecycle affects global entry reliability.

The option Configure multi-region origin/storage failover with compatible CloudFront behavior addresses a separate condition: critical static files must remain accessible during an S3 origin region outage. Geo-redundant origins improve availability. The actual requirement is a single customer-hosted certificate renewal outage breaks HTTPS for every region. Recommended corrective action: Use managed ACM certificates and tested renewal validation. Certificate lifecycle affects global entry reliability.

Create an appropriate regional data DR strategy, not only a CDN would help if an application's database is only in one region while edge caches exist worldwide. Edge caching does not protect the underlying database state. That is not the symptom described here: a single customer-hosted certificate renewal outage breaks HTTPS for every region. The matching response is Use managed ACM certificates and tested renewal validation, because certificate lifecycle affects global entry reliability.

The option Use managed ACM certificates and tested renewal validation addresses a separate condition: a single customer-hosted certificate renewal outage breaks HTTPS for every region. Certificate lifecycle affects global entry reliability. The actual requirement is an application's database is only in one region while edge caches exist worldwide. Recommended corrective action: Create an appropriate regional data DR strategy, not only a CDN. Edge caching does not protect the underlying database state.

Configure multi-region origin/storage failover with compatible CloudFront behavior would help if critical static files must remain accessible during an S3 origin region outage. Geo-redundant origins improve availability. That is not the symptom described here: an application's database is only in one region while edge caches exist worldwide. The matching response is Create an appropriate regional data DR strategy, not only a CDN, because edge caching does not protect the underlying database state.

Cache static assets at CloudFront edge locations solves a different operational problem where users around the globe see high latency fetching static content. CDN caching reduces origin latency and load. It does not directly address an application's database is only in one region while edge caches exist worldwide. The case calls for Create an appropriate regional data DR strategy, not only a CDN, since edge caching does not protect the underlying database state.