Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This alternative, Select DynamoDB global tables with explicit application conflict expectations, is appropriate when A global key-value service must accept local writes in two regions and resolve replication conflicts. Global tables provide multi-Region multi-active asynchronous replication.

For the separate situation A regional database must survive one Availability Zone failure with minimal loss of committed data, Use an RDS Multi-AZ standby arrangement with managed failover could be useful. Synchronous AZ standby reduces loss from a single-AZ outage.

Use an appropriate RDS cross-Region read replica and direct reads to it solves the related scenario A read-heavy online shop needs a cross-Region read copy and can tolerate lag; asynchronous read replicas serve read traffic but may lag behind the writer.

Instrument replication lag and redesign data transfer or consistency guarantees solves the related scenario A regulated app's RPO is five minutes but its cross-Region replication sometimes lags 15 minutes; recovery point compliance depends on observed data lag rather than DNS failover speed.

Although Keep a scaled-down warm standby environment and test automated scale-up can be valid when A manufacturing service must resume within 30 minutes while backup-only restoration takes six hours, it targets a different technical condition. Warm standby shortens startup and recovery time with partial always-on capacity.

This alternative, Implement a pilot-light footprint with scripted infrastructure expansion, is appropriate when A team requires only foundational databases and configuration ready while app compute is started during failover. Pilot light preserves core state and scales remaining application components on recovery.

Although Maintain a fully provisioned multi-Region serving stack with health-based traffic switching can be valid when An e-commerce platform needs a subminute failover without rebuilding application instances after a regional outage, it targets a different technical condition. Multi-site readiness minimizes time needed to restore the request-serving tier.

Keep a scaled-down warm standby environment and test automated scale-up would address a different requirement: A manufacturing service must resume within 30 minutes while backup-only restoration takes six hours. Warm standby shortens startup and recovery time with partial always-on capacity.

This alternative, Implement a pilot-light footprint with scripted infrastructure expansion, is appropriate when A team requires only foundational databases and configuration ready while app compute is started during failover. Pilot light preserves core state and scales remaining application components on recovery.

Use backup-and-restore DR with documented backup age and recovery tests would address a different requirement: A finance reporting workload may require four hours to recover and can tolerate restoring last night's data. Loose objectives allow lower-cost recovery from backups instead of standing capacity.

For the separate situation A regulated app's RPO is five minutes but its cross-Region replication sometimes lags 15 minutes, Instrument replication lag and redesign data transfer or consistency guarantees could be useful. Recovery point compliance depends on observed data lag rather than DNS failover speed.

Maintain a fully provisioned multi-Region serving stack with health-based traffic switching solves the related scenario An e-commerce platform needs a subminute failover without rebuilding application instances after a regional outage; multi-site readiness minimizes time needed to restore the request-serving tier.

This alternative, Instrument replication lag and redesign data transfer or consistency guarantees, is appropriate when A regulated app's RPO is five minutes but its cross-Region replication sometimes lags 15 minutes. Recovery point compliance depends on observed data lag rather than DNS failover speed.

For the separate situation An e-commerce platform needs a subminute failover without rebuilding application instances after a regional outage, Maintain a fully provisioned multi-Region serving stack with health-based traffic switching could be useful. Multi-site readiness minimizes time needed to restore the request-serving tier.

Although Keep a scaled-down warm standby environment and test automated scale-up can be valid when A manufacturing service must resume within 30 minutes while backup-only restoration takes six hours, it targets a different technical condition. Warm standby shortens startup and recovery time with partial always-on capacity.

For the separate situation A finance reporting workload may require four hours to recover and can tolerate restoring last night's data, Use backup-and-restore DR with documented backup age and recovery tests could be useful. Loose objectives allow lower-cost recovery from backups instead of standing capacity.

Keep a scaled-down warm standby environment and test automated scale-up solves the related scenario A manufacturing service must resume within 30 minutes while backup-only restoration takes six hours; warm standby shortens startup and recovery time with partial always-on capacity.

Implement a pilot-light footprint with scripted infrastructure expansion would address a different requirement: A team requires only foundational databases and configuration ready while app compute is started during failover. Pilot light preserves core state and scales remaining application components on recovery.

Although Enable S3 versioning and suitable retention controls on the source bucket can be valid when An S3 bucket stores records that must be protected from accidental deletes before monthly backup runs, it targets a different technical condition. Object versioning preserves earlier revisions independently of scheduled backup cadence.

Perform a supported encrypted snapshot copy specifying an authorized destination KMS key would address a different requirement: An encrypted database snapshot must be copied to a Region with a different customer-managed KMS key. Snapshot copies can reencrypt eligible data under the destination Region key.

This alternative, Conduct staged restore exercises and measure actual end-to-end RTO, is appropriate when Backups report success but recovery procedures have never been timed against the four-hour SLA. Successful backup jobs alone do not prove an application can meet its recovery time objective.

Perform a supported encrypted snapshot copy specifying an authorized destination KMS key would address a different requirement: An encrypted database snapshot must be copied to a Region with a different customer-managed KMS key. Snapshot copies can reencrypt eligible data under the destination Region key.

This alternative, Conduct staged restore exercises and measure actual end-to-end RTO, is appropriate when Backups report success but recovery procedures have never been timed against the four-hour SLA. Successful backup jobs alone do not prove an application can meet its recovery time objective.

For the separate situation An organization needs point-in-time rollback of a DynamoDB table after accidental writes, Enable DynamoDB point-in-time recovery and restore to a new table could be useful. PITR provides continuous recovery within the available retention window.

This alternative, Perform a supported encrypted snapshot copy specifying an authorized destination KMS key, is appropriate when An encrypted database snapshot must be copied to a Region with a different customer-managed KMS key. Snapshot copies can reencrypt eligible data under the destination Region key.

Configure cross-account snapshot or AWS Backup copy policies and destination key access solves the related scenario An audit-controlled workload needs copies of EBS backups in an independent security account; separate-account recovery copies reduce exposure to production-account compromise.

Although Enable S3 versioning and suitable retention controls on the source bucket can be valid when An S3 bucket stores records that must be protected from accidental deletes before monthly backup runs, it targets a different technical condition. Object versioning preserves earlier revisions independently of scheduled backup cadence.

For the separate situation An audit-controlled workload needs copies of EBS backups in an independent security account, Configure cross-account snapshot or AWS Backup copy policies and destination key access could be useful. Separate-account recovery copies reduce exposure to production-account compromise.

Although Enable S3 versioning and suitable retention controls on the source bucket can be valid when An S3 bucket stores records that must be protected from accidental deletes before monthly backup runs, it targets a different technical condition. Object versioning preserves earlier revisions independently of scheduled backup cadence.

Conduct staged restore exercises and measure actual end-to-end RTO would address a different requirement: Backups report success but recovery procedures have never been timed against the four-hour SLA. Successful backup jobs alone do not prove an application can meet its recovery time objective.

Enable DynamoDB point-in-time recovery and restore to a new table solves the related scenario An organization needs point-in-time rollback of a DynamoDB table after accidental writes; pITR provides continuous recovery within the available retention window.

Perform a supported encrypted snapshot copy specifying an authorized destination KMS key would address a different requirement: An encrypted database snapshot must be copied to a Region with a different customer-managed KMS key. Snapshot copies can reencrypt eligible data under the destination Region key.

This alternative, Configure cross-account snapshot or AWS Backup copy policies and destination key access, is appropriate when An audit-controlled workload needs copies of EBS backups in an independent security account. Separate-account recovery copies reduce exposure to production-account compromise.