Amazon AWS Certified Solutions Architect - Associate SAA-C03 Bundle

The option Use ECS service subnets across AZs and suitable task distribution addresses a separate condition: a service requires placement across distinct Availability Zones. Multi-AZ tasks survive a single-zone failure. The actual requirement is a persistent file uploaded to a container vanishes after task replacement. Recommended corrective action: Store durable data in S3 or EFS instead of task ephemeral filesystem. Task storage is not durable across replacement.

For the alternative failure a new ECS task version fails health checks and all previous tasks have been stopped, the control Configure ECS deployment circuit breaker/rollback and minimum healthy percent is relevant: deployment rollback prevents a bad revision from wiping healthy capacity. Here the evidence instead is a persistent file uploaded to a container vanishes after task replacement. The selected technical mechanism is Store durable data in S3 or EFS instead of task ephemeral filesystem: task storage is not durable across replacement.

Configure deregistration delay and graceful termination solves a different operational problem where a container remains routable while it is shutting down. Connection draining reduces dropped in-flight requests. It does not directly address a persistent file uploaded to a container vanishes after task replacement. The case calls for Store durable data in S3 or EFS instead of task ephemeral filesystem, since task storage is not durable across replacement.

Copy and validate selected historical S3 object versions through a controlled Batch Operations copy would help if a DR exercise must recover particular historical object versions that predate replication. Explicit backfill of selected versions restores specific recovery history. That is not the symptom described here: an operator deletes the current copy of a document accidentally. The matching response is Use S3 Versioning to retrieve the previous object version, because versioning preserves noncurrent versions for recovery.

Use S3 Object Lock with suitable retention mode solves a different operational problem where a compliance archive must not permit deletion before retention expires. Object Lock protects selected versions during retention. It does not directly address an operator deletes the current copy of a document accidentally. The case calls for Use S3 Versioning to retrieve the previous object version, since versioning preserves noncurrent versions for recovery.

The competing option Use version IDs and idempotency metadata to identify intended object state would be useful when application retries cause multiple uploads to the same key and operators cannot distinguish versions. Object versioning and operation IDs support reconciliation. The present issue is an operator deletes the current copy of a document accidentally; it is more directly addressed by Use S3 Versioning to retrieve the previous object version. Versioning preserves noncurrent versions for recovery.

For the alternative failure a remote-region bucket already holds S3 replicas but the DR application still reads the failed source endpoint, the control Switch DR reads to the healthy replica bucket and validate version/key accessibility is relevant: replicated storage only supports failover when clients address the recovery copy. Here the evidence instead is a compliance archive must not permit deletion before retention expires. The selected technical mechanism is Use S3 Object Lock with suitable retention mode: object Lock protects selected versions during retention.

The competing option Copy and validate selected historical S3 object versions through a controlled Batch Operations copy would be useful when a DR exercise must recover particular historical object versions that predate replication. Explicit backfill of selected versions restores specific recovery history. The present issue is a compliance archive must not permit deletion before retention expires; it is more directly addressed by Use S3 Object Lock with suitable retention mode. Object Lock protects selected versions during retention.

The option Use S3 Versioning to retrieve the previous object version addresses a separate condition: an operator deletes the current copy of a document accidentally. Versioning preserves noncurrent versions for recovery. The actual requirement is a compliance archive must not permit deletion before retention expires. Recommended corrective action: Use S3 Object Lock with suitable retention mode. Object Lock protects selected versions during retention.

Use S3 Versioning to retrieve the previous object version solves a different operational problem where an operator deletes the current copy of a document accidentally. Versioning preserves noncurrent versions for recovery. It does not directly address a remote-region bucket already holds S3 replicas but the DR application still reads the failed source endpoint. The case calls for Switch DR reads to the healthy replica bucket and validate version/key accessibility, since replicated storage only supports failover when clients address the recovery copy.

The competing option Use S3 Object Lock with suitable retention mode would be useful when a compliance archive must not permit deletion before retention expires. Object Lock protects selected versions during retention. The present issue is a remote-region bucket already holds S3 replicas but the DR application still reads the failed source endpoint; it is more directly addressed by Switch DR reads to the healthy replica bucket and validate version/key accessibility. Replicated storage only supports failover when clients address the recovery copy.

Copy and validate selected historical S3 object versions through a controlled Batch Operations copy would help if a DR exercise must recover particular historical object versions that predate replication. Explicit backfill of selected versions restores specific recovery history. That is not the symptom described here: a remote-region bucket already holds S3 replicas but the DR application still reads the failed source endpoint. The matching response is Switch DR reads to the healthy replica bucket and validate version/key accessibility, because replicated storage only supports failover when clients address the recovery copy.

The competing option Use S3 Object Lock with suitable retention mode would be useful when a compliance archive must not permit deletion before retention expires. Object Lock protects selected versions during retention. The present issue is a DR exercise must recover particular historical object versions that predate replication; it is more directly addressed by Copy and validate selected historical S3 object versions through a controlled Batch Operations copy. Explicit backfill of selected versions restores specific recovery history.

The option Use version IDs and idempotency metadata to identify intended object state addresses a separate condition: application retries cause multiple uploads to the same key and operators cannot distinguish versions. Object versioning and operation IDs support reconciliation. The actual requirement is a DR exercise must recover particular historical object versions that predate replication. Recommended corrective action: Copy and validate selected historical S3 object versions through a controlled Batch Operations copy. Explicit backfill of selected versions restores specific recovery history.

Use S3 Versioning to retrieve the previous object version would help if an operator deletes the current copy of a document accidentally. Versioning preserves noncurrent versions for recovery. That is not the symptom described here: a DR exercise must recover particular historical object versions that predate replication. The matching response is Copy and validate selected historical S3 object versions through a controlled Batch Operations copy, because explicit backfill of selected versions restores specific recovery history.

Use S3 Versioning to retrieve the previous object version would help if an operator deletes the current copy of a document accidentally. Versioning preserves noncurrent versions for recovery. That is not the symptom described here: application retries cause multiple uploads to the same key and operators cannot distinguish versions. The matching response is Use version IDs and idempotency metadata to identify intended object state, because object versioning and operation IDs support reconciliation.

For the alternative failure a remote-region bucket already holds S3 replicas but the DR application still reads the failed source endpoint, the control Switch DR reads to the healthy replica bucket and validate version/key accessibility is relevant: replicated storage only supports failover when clients address the recovery copy. Here the evidence instead is application retries cause multiple uploads to the same key and operators cannot distinguish versions. The selected technical mechanism is Use version IDs and idempotency metadata to identify intended object state: object versioning and operation IDs support reconciliation.

Use S3 Object Lock with suitable retention mode solves a different operational problem where a compliance archive must not permit deletion before retention expires. Object Lock protects selected versions during retention. It does not directly address application retries cause multiple uploads to the same key and operators cannot distinguish versions. The case calls for Use version IDs and idempotency metadata to identify intended object state, since object versioning and operation IDs support reconciliation.

Use per-AZ egress design and route alignment where justified would help if all private subnets share a NAT gateway in one AZ. AZ-local egress avoids dependency on a remote AZ gateway. That is not the symptom described here: a Direct Connect circuit is the only path into AWS and its provider fails. The matching response is Deploy redundant Direct Connect and/or VPN backup paths, because independent network paths mitigate single-link failures.

Configure customer gateway routing/failover across both managed VPN tunnels solves a different operational problem where a branch VPN relies on a single tunnel although AWS provides two tunnels. Dual tunnels provide alternative encrypted paths. It does not directly address a Direct Connect circuit is the only path into AWS and its provider fails. The case calls for Deploy redundant Direct Connect and/or VPN backup paths, since independent network paths mitigate single-link failures.

The competing option Add TGW attachment subnets in required AZs with route design would be useful when a transit-gateway attachment in one AZ becomes a bottleneck for regional traffic. Multi-AZ attachment design extends path availability. The present issue is a Direct Connect circuit is the only path into AWS and its provider fails; it is more directly addressed by Deploy redundant Direct Connect and/or VPN backup paths. Independent network paths mitigate single-link failures.

For the alternative failure an application route remains pointed at a dead EC2 NAT instance, the control Implement monitored failover or replace with managed NAT gateways is relevant: managed egress reduces failure handling that self-managed NAT requires. Here the evidence instead is a transit-gateway attachment in one AZ becomes a bottleneck for regional traffic. The selected technical mechanism is Add TGW attachment subnets in required AZs with route design: multi-AZ attachment design extends path availability.

Use per-AZ egress design and route alignment where justified solves a different operational problem where all private subnets share a NAT gateway in one AZ. AZ-local egress avoids dependency on a remote AZ gateway. It does not directly address a transit-gateway attachment in one AZ becomes a bottleneck for regional traffic. The case calls for Add TGW attachment subnets in required AZs with route design, since multi-AZ attachment design extends path availability.

The competing option Deploy redundant Direct Connect and/or VPN backup paths would be useful when a Direct Connect circuit is the only path into AWS and its provider fails. Independent network paths mitigate single-link failures. The present issue is a transit-gateway attachment in one AZ becomes a bottleneck for regional traffic; it is more directly addressed by Add TGW attachment subnets in required AZs with route design. Multi-AZ attachment design extends path availability.

Implement monitored failover or replace with managed NAT gateways solves a different operational problem where an application route remains pointed at a dead EC2 NAT instance. Managed egress reduces failure handling that self-managed NAT requires. It does not directly address a branch VPN relies on a single tunnel although AWS provides two tunnels. The case calls for Configure customer gateway routing/failover across both managed VPN tunnels, since dual tunnels provide alternative encrypted paths.

The option Use per-AZ egress design and route alignment where justified addresses a separate condition: all private subnets share a NAT gateway in one AZ. AZ-local egress avoids dependency on a remote AZ gateway. The actual requirement is a branch VPN relies on a single tunnel although AWS provides two tunnels. Recommended corrective action: Configure customer gateway routing/failover across both managed VPN tunnels. Dual tunnels provide alternative encrypted paths.

Deploy redundant Direct Connect and/or VPN backup paths would help if a Direct Connect circuit is the only path into AWS and its provider fails. Independent network paths mitigate single-link failures. That is not the symptom described here: a branch VPN relies on a single tunnel although AWS provides two tunnels. The matching response is Configure customer gateway routing/failover across both managed VPN tunnels, because dual tunnels provide alternative encrypted paths.

The competing option Implement monitored failover or replace with managed NAT gateways would be useful when an application route remains pointed at a dead EC2 NAT instance. Managed egress reduces failure handling that self-managed NAT requires. The present issue is all private subnets share a NAT gateway in one AZ; it is more directly addressed by Use per-AZ egress design and route alignment where justified. AZ-local egress avoids dependency on a remote AZ gateway.

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: all private subnets share a NAT gateway in one AZ. The matching response is Use per-AZ egress design and route alignment where justified, because aZ-local egress avoids dependency on a remote AZ gateway.

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 all private subnets share a NAT gateway in one AZ. The selected technical mechanism is Use per-AZ egress design and route alignment where justified: aZ-local egress avoids dependency on a remote AZ gateway.

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.