Amazon AWS Certified Solutions Architect - Associate SAA-C03 Bundle

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.

Extend recovery point lifecycle retention in the backup plan would help if backup retention was set shorter than legal data recovery policy. Retention rules define available recovery history. That is not the symptom described here: snapshots finish successfully but a disaster recovery rehearsal cannot access the KMS key. The matching response is Ensure backup-restore role has key access and backup copy key availability, because encrypted backups remain unusable without their cryptographic key.

For the alternative failure the RTO calls for recovery in minutes but full restore needs several hours, the control Use warm standby or another lower-RTO DR pattern is relevant: backup and restore alone may not satisfy short RTO requirements. Here the evidence instead is snapshots finish successfully but a disaster recovery rehearsal cannot access the KMS key. The selected technical mechanism is Ensure backup-restore role has key access and backup copy key availability: encrypted backups remain unusable without their cryptographic key.

The competing option Run end-to-end restore tests with application data validation would be useful when an administrator has never confirmed application consistency after restoring an RDS snapshot. A restored database's availability does not prove logical correctness. The present issue is snapshots finish successfully but a disaster recovery rehearsal cannot access the KMS key; it is more directly addressed by Ensure backup-restore role has key access and backup copy key availability. Encrypted backups remain unusable without their cryptographic key.

For the alternative failure the RTO calls for recovery in minutes but full restore needs several hours, the control Use warm standby or another lower-RTO DR pattern is relevant: backup and restore alone may not satisfy short RTO requirements. Here the evidence instead is backups are stored only in the production account targeted by ransomware. The selected technical mechanism is Copy recovery points to an isolated backup account/vault: separate backup custody reduces common compromise.

Run end-to-end restore tests with application data validation solves a different operational problem where an administrator has never confirmed application consistency after restoring an RDS snapshot. A restored database's availability does not prove logical correctness. It does not directly address backups are stored only in the production account targeted by ransomware. The case calls for Copy recovery points to an isolated backup account/vault, since separate backup custody reduces common compromise.

The option Ensure backup-restore role has key access and backup copy key availability addresses a separate condition: snapshots finish successfully but a disaster recovery rehearsal cannot access the KMS key. Encrypted backups remain unusable without their cryptographic key. The actual requirement is backups are stored only in the production account targeted by ransomware. Recommended corrective action: Copy recovery points to an isolated backup account/vault. Separate backup custody reduces common compromise.

Run end-to-end restore tests with application data validation solves a different operational problem where an administrator has never confirmed application consistency after restoring an RDS snapshot. A restored database's availability does not prove logical correctness. It does not directly address the RTO calls for recovery in minutes but full restore needs several hours. The case calls for Use warm standby or another lower-RTO DR pattern, since backup and restore alone may not satisfy short RTO requirements.

The option Ensure backup-restore role has key access and backup copy key availability addresses a separate condition: snapshots finish successfully but a disaster recovery rehearsal cannot access the KMS key. Encrypted backups remain unusable without their cryptographic key. The actual requirement is the RTO calls for recovery in minutes but full restore needs several hours. Recommended corrective action: Use warm standby or another lower-RTO DR pattern. Backup and restore alone may not satisfy short RTO requirements.

Extend recovery point lifecycle retention in the backup plan would help if backup retention was set shorter than legal data recovery policy. Retention rules define available recovery history. That is not the symptom described here: the RTO calls for recovery in minutes but full restore needs several hours. The matching response is Use warm standby or another lower-RTO DR pattern, because backup and restore alone may not satisfy short RTO requirements.

The competing option Ensure backup-restore role has key access and backup copy key availability would be useful when snapshots finish successfully but a disaster recovery rehearsal cannot access the KMS key. Encrypted backups remain unusable without their cryptographic key. The present issue is backup retention was set shorter than legal data recovery policy; it is more directly addressed by Extend recovery point lifecycle retention in the backup plan. Retention rules define available recovery history.

Use warm standby or another lower-RTO DR pattern would help if the RTO calls for recovery in minutes but full restore needs several hours. Backup and restore alone may not satisfy short RTO requirements. That is not the symptom described here: backup retention was set shorter than legal data recovery policy. The matching response is Extend recovery point lifecycle retention in the backup plan, because retention rules define available recovery history.

For the alternative failure backups are stored only in the production account targeted by ransomware, the control Copy recovery points to an isolated backup account/vault is relevant: separate backup custody reduces common compromise. Here the evidence instead is backup retention was set shorter than legal data recovery policy. The selected technical mechanism is Extend recovery point lifecycle retention in the backup plan: retention rules define available recovery history.

The option Extend recovery point lifecycle retention in the backup plan addresses a separate condition: backup retention was set shorter than legal data recovery policy. Retention rules define available recovery history. The actual requirement is an administrator has never confirmed application consistency after restoring an RDS snapshot. Recommended corrective action: Run end-to-end restore tests with application data validation. A restored database's availability does not prove logical correctness.

For the alternative failure the RTO calls for recovery in minutes but full restore needs several hours, the control Use warm standby or another lower-RTO DR pattern is relevant: backup and restore alone may not satisfy short RTO requirements. Here the evidence instead is an administrator has never confirmed application consistency after restoring an RDS snapshot. The selected technical mechanism is Run end-to-end restore tests with application data validation: a restored database's availability does not prove logical correctness.

Ensure backup-restore role has key access and backup copy key availability solves a different operational problem where snapshots finish successfully but a disaster recovery rehearsal cannot access the KMS key. Encrypted backups remain unusable without their cryptographic key. It does not directly address an administrator has never confirmed application consistency after restoring an RDS snapshot. The case calls for Run end-to-end restore tests with application data validation, since a restored database's availability does not prove logical correctness.

For the alternative failure recovery must occur within two hours while keeping only core data replicated, the control Use pilot light with automated scale-out for the recovery region is relevant: pilot-light architecture maintains minimal regional primitives. Here the evidence instead is the business accepts twelve hours of downtime for rarely used reports. The selected technical mechanism is Choose backup-and-restore DR and test reconstruction steps: infrequent workloads can trade recovery time for lower steady cost.

Maintain a warm standby regional workload with replicating data solves a different operational problem where the application must resume within fifteen minutes using reduced standby capacity. Warm standby predeploys an operable reduced-scale stack. It does not directly address the business accepts twelve hours of downtime for rarely used reports. The case calls for Choose backup-and-restore DR and test reconstruction steps, since infrequent workloads can trade recovery time for lower steady cost.

The competing option Measure actual failover and data loss during controlled DR drills would be useful when the team documents RPO/RTO requirements but cannot demonstrate actual results. Verified metrics reveal whether recovery objectives are met. The present issue is the business accepts twelve hours of downtime for rarely used reports; it is more directly addressed by Choose backup-and-restore DR and test reconstruction steps. Infrequent workloads can trade recovery time for lower steady cost.

For the alternative failure the business accepts twelve hours of downtime for rarely used reports, the control Choose backup-and-restore DR and test reconstruction steps is relevant: infrequent workloads can trade recovery time for lower steady cost. Here the evidence instead is recovery must occur within two hours while keeping only core data replicated. The selected technical mechanism is Use pilot light with automated scale-out for the recovery region: pilot-light architecture maintains minimal regional primitives.

Architect active-active multi-region routing and data consistency handling solves a different operational problem where the customer requires continuous service despite an entire AWS Region outage. Active-active workloads are ready in both regions. It does not directly address recovery must occur within two hours while keeping only core data replicated. The case calls for Use pilot light with automated scale-out for the recovery region, since pilot-light architecture maintains minimal regional primitives.

The option Maintain a warm standby regional workload with replicating data addresses a separate condition: the application must resume within fifteen minutes using reduced standby capacity. Warm standby predeploys an operable reduced-scale stack. The actual requirement is recovery must occur within two hours while keeping only core data replicated. Recommended corrective action: Use pilot light with automated scale-out for the recovery region. Pilot-light architecture maintains minimal regional primitives.

Choose backup-and-restore DR and test reconstruction steps solves a different operational problem where the business accepts twelve hours of downtime for rarely used reports. Infrequent workloads can trade recovery time for lower steady cost. It does not directly address the application must resume within fifteen minutes using reduced standby capacity. The case calls for Maintain a warm standby regional workload with replicating data, since warm standby predeploys an operable reduced-scale stack.

The competing option Measure actual failover and data loss during controlled DR drills would be useful when the team documents RPO/RTO requirements but cannot demonstrate actual results. Verified metrics reveal whether recovery objectives are met. The present issue is the application must resume within fifteen minutes using reduced standby capacity; it is more directly addressed by Maintain a warm standby regional workload with replicating data. Warm standby predeploys an operable reduced-scale stack.

Architect active-active multi-region routing and data consistency handling would help if the customer requires continuous service despite an entire AWS Region outage. Active-active workloads are ready in both regions. That is not the symptom described here: the application must resume within fifteen minutes using reduced standby capacity. The matching response is Maintain a warm standby regional workload with replicating data, because warm standby predeploys an operable reduced-scale stack.

The option Choose backup-and-restore DR and test reconstruction steps addresses a separate condition: the business accepts twelve hours of downtime for rarely used reports. Infrequent workloads can trade recovery time for lower steady cost. The actual requirement is the customer requires continuous service despite an entire AWS Region outage. Recommended corrective action: Architect active-active multi-region routing and data consistency handling. Active-active workloads are ready in both regions.

Use pilot light with automated scale-out for the recovery region would help if recovery must occur within two hours while keeping only core data replicated. Pilot-light architecture maintains minimal regional primitives. That is not the symptom described here: the customer requires continuous service despite an entire AWS Region outage. The matching response is Architect active-active multi-region routing and data consistency handling, because active-active workloads are ready in both regions.

For the alternative failure the team documents RPO/RTO requirements but cannot demonstrate actual results, the control Measure actual failover and data loss during controlled DR drills is relevant: verified metrics reveal whether recovery objectives are met. Here the evidence instead is the customer requires continuous service despite an entire AWS Region outage. The selected technical mechanism is Architect active-active multi-region routing and data consistency handling: active-active workloads are ready in both regions.

The option Maintain a warm standby regional workload with replicating data addresses a separate condition: the application must resume within fifteen minutes using reduced standby capacity. Warm standby predeploys an operable reduced-scale stack. The actual requirement is the team documents RPO/RTO requirements but cannot demonstrate actual results. Recommended corrective action: Measure actual failover and data loss during controlled DR drills. Verified metrics reveal whether recovery objectives are met.

Choose backup-and-restore DR and test reconstruction steps would help if the business accepts twelve hours of downtime for rarely used reports. Infrequent workloads can trade recovery time for lower steady cost. That is not the symptom described here: the team documents RPO/RTO requirements but cannot demonstrate actual results. The matching response is Measure actual failover and data loss during controlled DR drills, because verified metrics reveal whether recovery objectives are met.

For the alternative failure recovery must occur within two hours while keeping only core data replicated, the control Use pilot light with automated scale-out for the recovery region is relevant: pilot-light architecture maintains minimal regional primitives. Here the evidence instead is the team documents RPO/RTO requirements but cannot demonstrate actual results. The selected technical mechanism is Measure actual failover and data loss during controlled DR drills: verified metrics reveal whether recovery objectives are met.