Amazon AWS Certified Solutions Architect - Associate SAA-C03 Bundle

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.

Use supported cross-region replica/global database and latency-aware failover plan would help if the service needs an immediately available reader in another AWS Region. Continuously replicated regional readers reduce recovery setup time. That is not the symptom described here: a serverless function fleet exhausts RDS max_connections under spikes. The matching response is Use RDS Proxy with suitable pool sizing and connection behavior, because database connection pooling limits backend connection pressure.

For the alternative failure a regional database disaster requires cross-region restore, the control Maintain tested cross-region snapshots or backups and recovery runbooks is relevant: regional backup copies survive source-region loss. Here the evidence instead is a serverless function fleet exhausts RDS max_connections under spikes. The selected technical mechanism is Use RDS Proxy with suitable pool sizing and connection behavior: database connection pooling limits backend connection pressure.

Add supported read replicas when read scaling is required solves a different operational problem where a Multi-AZ standby is expected to increase read query capacity. Traditional standby nodes are not read-serving replicas. It does not directly address a serverless function fleet exhausts RDS max_connections under spikes. The case calls for Use RDS Proxy with suitable pool sizing and connection behavior, since database connection pooling limits backend connection pressure.

For the alternative failure a regional database disaster requires cross-region restore, the control Maintain tested cross-region snapshots or backups and recovery runbooks is relevant: regional backup copies survive source-region loss. Here the evidence instead is a database instance reboots and the app refuses to resolve its new endpoint address. The selected technical mechanism is Re-resolve DNS and reconnect using the managed endpoint: database endpoint addresses can change after failover.

The competing option Use supported cross-region replica/global database and latency-aware failover plan would be useful when the service needs an immediately available reader in another AWS Region. Continuously replicated regional readers reduce recovery setup time. The present issue is a database instance reboots and the app refuses to resolve its new endpoint address; it is more directly addressed by Re-resolve DNS and reconnect using the managed endpoint. Database endpoint addresses can change after failover.

The option Add supported read replicas when read scaling is required addresses a separate condition: a Multi-AZ standby is expected to increase read query capacity. Traditional standby nodes are not read-serving replicas. The actual requirement is a database instance reboots and the app refuses to resolve its new endpoint address. Recommended corrective action: Re-resolve DNS and reconnect using the managed endpoint. Database endpoint addresses can change after failover.

Use RDS Proxy with suitable pool sizing and connection behavior solves a different operational problem where a serverless function fleet exhausts RDS max_connections under spikes. Database connection pooling limits backend connection pressure. It does not directly address a Multi-AZ standby is expected to increase read query capacity. The case calls for Add supported read replicas when read scaling is required, since traditional standby nodes are not read-serving replicas.

The option Re-resolve DNS and reconnect using the managed endpoint addresses a separate condition: a database instance reboots and the app refuses to resolve its new endpoint address. Database endpoint addresses can change after failover. The actual requirement is a Multi-AZ standby is expected to increase read query capacity. Recommended corrective action: Add supported read replicas when read scaling is required. Traditional standby nodes are not read-serving replicas.

Use supported cross-region replica/global database and latency-aware failover plan would help if the service needs an immediately available reader in another AWS Region. Continuously replicated regional readers reduce recovery setup time. That is not the symptom described here: a Multi-AZ standby is expected to increase read query capacity. The matching response is Add supported read replicas when read scaling is required, because traditional standby nodes are not read-serving replicas.

The competing option Use RDS Proxy with suitable pool sizing and connection behavior would be useful when a serverless function fleet exhausts RDS max_connections under spikes. Database connection pooling limits backend connection pressure. The present issue is a regional database disaster requires cross-region restore; it is more directly addressed by Maintain tested cross-region snapshots or backups and recovery runbooks. Regional backup copies survive source-region loss.

The option Add supported read replicas when read scaling is required addresses a separate condition: a Multi-AZ standby is expected to increase read query capacity. Traditional standby nodes are not read-serving replicas. The actual requirement is a regional database disaster requires cross-region restore. Recommended corrective action: Maintain tested cross-region snapshots or backups and recovery runbooks. Regional backup copies survive source-region loss.

For the alternative failure a database instance reboots and the app refuses to resolve its new endpoint address, the control Re-resolve DNS and reconnect using the managed endpoint is relevant: database endpoint addresses can change after failover. Here the evidence instead is a regional database disaster requires cross-region restore. The selected technical mechanism is Maintain tested cross-region snapshots or backups and recovery runbooks: regional backup copies survive source-region loss.

The option Add supported read replicas when read scaling is required addresses a separate condition: a Multi-AZ standby is expected to increase read query capacity. Traditional standby nodes are not read-serving replicas. The actual requirement is the service needs an immediately available reader in another AWS Region. Recommended corrective action: Use supported cross-region replica/global database and latency-aware failover plan. Continuously replicated regional readers reduce recovery setup time.

Re-resolve DNS and reconnect using the managed endpoint would help if a database instance reboots and the app refuses to resolve its new endpoint address. Database endpoint addresses can change after failover. That is not the symptom described here: the service needs an immediately available reader in another AWS Region. The matching response is Use supported cross-region replica/global database and latency-aware failover plan, because continuously replicated regional readers reduce recovery setup time.

For the alternative failure a serverless function fleet exhausts RDS max_connections under spikes, the control Use RDS Proxy with suitable pool sizing and connection behavior is relevant: database connection pooling limits backend connection pressure. Here the evidence instead is the service needs an immediately available reader in another AWS Region. The selected technical mechanism is Use supported cross-region replica/global database and latency-aware failover plan: continuously replicated regional readers reduce recovery setup time.

For the alternative failure operators cannot determine which instance version is serving requests, the control Tag instances and record deployment build IDs in metrics and logs is relevant: version identification supports incident diagnosis and rollback. Here the evidence instead is an administrator patches EC2 servers in place and each server drifts differently. The selected technical mechanism is Build a versioned AMI and replace instances through an Auto Scaling deployment: immutable replacement reduces configuration drift.

Move uploads to S3 or another durable shared data store solves a different operational problem where the only server stores upload files on its instance store. Instance store data is lost when the instance terminates. It does not directly address an administrator patches EC2 servers in place and each server drifts differently. The case calls for Build a versioned AMI and replace instances through an Auto Scaling deployment, since immutable replacement reduces configuration drift.

The competing option Preserve the previous launch template version and test ASG rollback would be useful when a failed deployment must roll back to the last healthy server build. Versioned launch templates provide controlled rollback candidates. The present issue is an administrator patches EC2 servers in place and each server drifts differently; it is more directly addressed by Build a versioned AMI and replace instances through an Auto Scaling deployment. Immutable replacement reduces configuration drift.

For the alternative failure a launch template references an AMI that is unavailable in the recovery region, the control Copy and validate required AMIs and dependencies in the recovery region is relevant: dR launch needs local machine images and compatible references. Here the evidence instead is the only server stores upload files on its instance store. The selected technical mechanism is Move uploads to S3 or another durable shared data store: instance store data is lost when the instance terminates.

Preserve the previous launch template version and test ASG rollback solves a different operational problem where a failed deployment must roll back to the last healthy server build. Versioned launch templates provide controlled rollback candidates. It does not directly address the only server stores upload files on its instance store. The case calls for Move uploads to S3 or another durable shared data store, since instance store data is lost when the instance terminates.

The option Tag instances and record deployment build IDs in metrics and logs addresses a separate condition: operators cannot determine which instance version is serving requests. Version identification supports incident diagnosis and rollback. The actual requirement is the only server stores upload files on its instance store. Recommended corrective action: Move uploads to S3 or another durable shared data store. Instance store data is lost when the instance terminates.

Build a versioned AMI and replace instances through an Auto Scaling deployment solves a different operational problem where an administrator patches EC2 servers in place and each server drifts differently. Immutable replacement reduces configuration drift. It does not directly address a launch template references an AMI that is unavailable in the recovery region. The case calls for Copy and validate required AMIs and dependencies in the recovery region, since dR launch needs local machine images and compatible references.

The option Tag instances and record deployment build IDs in metrics and logs addresses a separate condition: operators cannot determine which instance version is serving requests. Version identification supports incident diagnosis and rollback. The actual requirement is a launch template references an AMI that is unavailable in the recovery region. Recommended corrective action: Copy and validate required AMIs and dependencies in the recovery region. DR launch needs local machine images and compatible references.

Move uploads to S3 or another durable shared data store would help if the only server stores upload files on its instance store. Instance store data is lost when the instance terminates. That is not the symptom described here: a launch template references an AMI that is unavailable in the recovery region. The matching response is Copy and validate required AMIs and dependencies in the recovery region, because dR launch needs local machine images and compatible references.

The option Copy and validate required AMIs and dependencies in the recovery region addresses a separate condition: a launch template references an AMI that is unavailable in the recovery region. DR launch needs local machine images and compatible references. The actual requirement is a failed deployment must roll back to the last healthy server build. Recommended corrective action: Preserve the previous launch template version and test ASG rollback. Versioned launch templates provide controlled rollback candidates.

Tag instances and record deployment build IDs in metrics and logs would help if operators cannot determine which instance version is serving requests. Version identification supports incident diagnosis and rollback. That is not the symptom described here: a failed deployment must roll back to the last healthy server build. The matching response is Preserve the previous launch template version and test ASG rollback, because versioned launch templates provide controlled rollback candidates.

For the alternative failure the only server stores upload files on its instance store, the control Move uploads to S3 or another durable shared data store is relevant: instance store data is lost when the instance terminates. Here the evidence instead is a failed deployment must roll back to the last healthy server build. The selected technical mechanism is Preserve the previous launch template version and test ASG rollback: versioned launch templates provide controlled rollback candidates.

The option Preserve the previous launch template version and test ASG rollback addresses a separate condition: a failed deployment must roll back to the last healthy server build. Versioned launch templates provide controlled rollback candidates. The actual requirement is operators cannot determine which instance version is serving requests. Recommended corrective action: Tag instances and record deployment build IDs in metrics and logs. Version identification supports incident diagnosis and rollback.

For the alternative failure the only server stores upload files on its instance store, the control Move uploads to S3 or another durable shared data store is relevant: instance store data is lost when the instance terminates. Here the evidence instead is operators cannot determine which instance version is serving requests. The selected technical mechanism is Tag instances and record deployment build IDs in metrics and logs: version identification supports incident diagnosis and rollback.

Build a versioned AMI and replace instances through an Auto Scaling deployment solves a different operational problem where an administrator patches EC2 servers in place and each server drifts differently. Immutable replacement reduces configuration drift. It does not directly address operators cannot determine which instance version is serving requests. The case calls for Tag instances and record deployment build IDs in metrics and logs, since version identification supports incident diagnosis and rollback.