Amazon AWS Certified Solutions Architect - Associate SAA-C03 Bundle

The option Make the write idempotent and acknowledge only after durable success addresses a separate condition: a queue consumer crashes after writing a DynamoDB item but before acknowledging the message. At-least-once redelivery may repeat successful processing. The actual requirement is messages that exhaust retries require operator review without blocking all orders. Recommended corrective action: Move terminal failures to a DLQ with controlled redrive. DLQ handling isolates errors while healthy work continues.

Use compensation logic and recorded step state before retrying would help if a Step Functions activity fails after a partial external side effect. Workflow retries cannot automatically undo external effects. That is not the symptom described here: messages that exhaust retries require operator review without blocking all orders. The matching response is Move terminal failures to a DLQ with controlled redrive, because dLQ handling isolates errors while healthy work continues.

For the alternative failure a write succeeds but the caller times out and retries the same order, the control Use idempotency keys and atomic duplicate detection on order storage is relevant: retries must not double-commit business actions. Here the evidence instead is messages that exhaust retries require operator review without blocking all orders. The selected technical mechanism is Move terminal failures to a DLQ with controlled redrive: dLQ handling isolates errors while healthy work continues.

Version container images and task definitions for known-good release restore would help if developers lack a reproducible earlier task configuration for rollback. Versioned deployment artifacts enable deterministic rollback. That is not the symptom described here: an EKS deployment rolls out all replicas at once and drops service capacity. The matching response is Set a rolling update maxUnavailable budget and readiness probes, because rolling deployments preserve a minimum ready replica count.

Move shared state to a multi-AZ data service or replicated storage solves a different operational problem where instances are spread across AZs but both depend on the same single-AZ storage volume. Application availability is limited by dependent state placement. It does not directly address an EKS deployment rolls out all replicas at once and drops service capacity. The case calls for Set a rolling update maxUnavailable budget and readiness probes, since rolling deployments preserve a minimum ready replica count.

The competing option Design health endpoints that reflect required dependency readiness would be useful when a task is reported healthy although its database dependency is unavailable. Readiness should reflect ability to serve meaningful requests. The present issue is an EKS deployment rolls out all replicas at once and drops service capacity; it is more directly addressed by Set a rolling update maxUnavailable budget and readiness probes. Rolling deployments preserve a minimum ready replica count.

For the alternative failure an EKS deployment rolls out all replicas at once and drops service capacity, the control Set a rolling update maxUnavailable budget and readiness probes is relevant: rolling deployments preserve a minimum ready replica count. Here the evidence instead is a broken container image reaches production despite earlier health failures. The selected technical mechanism is Use progressive deployment with health-based automatic rollback: measured rollout gates limit blast radius.

The competing option Move shared state to a multi-AZ data service or replicated storage would be useful when instances are spread across AZs but both depend on the same single-AZ storage volume. Application availability is limited by dependent state placement. The present issue is a broken container image reaches production despite earlier health failures; it is more directly addressed by Use progressive deployment with health-based automatic rollback. Measured rollout gates limit blast radius.

The option Version container images and task definitions for known-good release restore addresses a separate condition: developers lack a reproducible earlier task configuration for rollback. Versioned deployment artifacts enable deterministic rollback. The actual requirement is a broken container image reaches production despite earlier health failures. Recommended corrective action: Use progressive deployment with health-based automatic rollback. Measured rollout gates limit blast radius.

The competing option Set a rolling update maxUnavailable budget and readiness probes would be useful when an EKS deployment rolls out all replicas at once and drops service capacity. Rolling deployments preserve a minimum ready replica count. The present issue is a task is reported healthy although its database dependency is unavailable; it is more directly addressed by Design health endpoints that reflect required dependency readiness. Readiness should reflect ability to serve meaningful requests.

The option Move shared state to a multi-AZ data service or replicated storage addresses a separate condition: instances are spread across AZs but both depend on the same single-AZ storage volume. Application availability is limited by dependent state placement. The actual requirement is a task is reported healthy although its database dependency is unavailable. Recommended corrective action: Design health endpoints that reflect required dependency readiness. Readiness should reflect ability to serve meaningful requests.

Use progressive deployment with health-based automatic rollback would help if a broken container image reaches production despite earlier health failures. Measured rollout gates limit blast radius. That is not the symptom described here: a task is reported healthy although its database dependency is unavailable. The matching response is Design health endpoints that reflect required dependency readiness, because readiness should reflect ability to serve meaningful requests.

The competing option Use progressive deployment with health-based automatic rollback would be useful when a broken container image reaches production despite earlier health failures. Measured rollout gates limit blast radius. The present issue is instances are spread across AZs but both depend on the same single-AZ storage volume; it is more directly addressed by Move shared state to a multi-AZ data service or replicated storage. Application availability is limited by dependent state placement.

The option Design health endpoints that reflect required dependency readiness addresses a separate condition: a task is reported healthy although its database dependency is unavailable. Readiness should reflect ability to serve meaningful requests. The actual requirement is instances are spread across AZs but both depend on the same single-AZ storage volume. Recommended corrective action: Move shared state to a multi-AZ data service or replicated storage. Application availability is limited by dependent state placement.

For the alternative failure an EKS deployment rolls out all replicas at once and drops service capacity, the control Set a rolling update maxUnavailable budget and readiness probes is relevant: rolling deployments preserve a minimum ready replica count. Here the evidence instead is instances are spread across AZs but both depend on the same single-AZ storage volume. The selected technical mechanism is Move shared state to a multi-AZ data service or replicated storage: application availability is limited by dependent state placement.

The option Design health endpoints that reflect required dependency readiness addresses a separate condition: a task is reported healthy although its database dependency is unavailable. Readiness should reflect ability to serve meaningful requests. The actual requirement is developers lack a reproducible earlier task configuration for rollback. Recommended corrective action: Version container images and task definitions for known-good release restore. Versioned deployment artifacts enable deterministic rollback.

For the alternative failure a broken container image reaches production despite earlier health failures, the control Use progressive deployment with health-based automatic rollback is relevant: measured rollout gates limit blast radius. Here the evidence instead is developers lack a reproducible earlier task configuration for rollback. The selected technical mechanism is Version container images and task definitions for known-good release restore: versioned deployment artifacts enable deterministic rollback.

Set a rolling update maxUnavailable budget and readiness probes solves a different operational problem where an EKS deployment rolls out all replicas at once and drops service capacity. Rolling deployments preserve a minimum ready replica count. It does not directly address developers lack a reproducible earlier task configuration for rollback. The case calls for Version container images and task definitions for known-good release restore, since versioned deployment artifacts enable deterministic rollback.

Apply Object Lock retention with the required mode and policy would help if security must ensure archive objects cannot be deleted for a regulated retention period. Object Lock controls version deletion before expiry. That is not the symptom described here: an S3 object is deleted by mistake and the bucket has no versioning. The matching response is Enable S3 Versioning and establish recovery handling for future deletes, because versioning retains previous object versions.

For the alternative failure legacy data is not present in the DR bucket after a new CRR rule, the control Backfill through S3 Batch Replication for eligible objects is relevant: ordinary rules start with eligible new operations. Here the evidence instead is an S3 object is deleted by mistake and the bucket has no versioning. The selected technical mechanism is Enable S3 Versioning and establish recovery handling for future deletes: versioning retains previous object versions.

Configure CRR with S3 versioning and source/destination KMS permissions solves a different operational problem where a second-region copy is required but objects use customer KMS keys. Cross-region encrypted replication needs explicit cryptographic authorization. It does not directly address an S3 object is deleted by mistake and the bucket has no versioning. The case calls for Enable S3 Versioning and establish recovery handling for future deletes, since versioning retains previous object versions.

For the alternative failure an application needs immediate access after a Region outage but only deep-archive objects exist elsewhere, the control Choose suitable storage tiers/retrieval timing for recovery objectives is relevant: deep archives may not meet minute-scale RTOs. Here the evidence instead is security must ensure archive objects cannot be deleted for a regulated retention period. The selected technical mechanism is Apply Object Lock retention with the required mode and policy: object Lock controls version deletion before expiry.

Configure CRR with S3 versioning and source/destination KMS permissions solves a different operational problem where a second-region copy is required but objects use customer KMS keys. Cross-region encrypted replication needs explicit cryptographic authorization. It does not directly address security must ensure archive objects cannot be deleted for a regulated retention period. The case calls for Apply Object Lock retention with the required mode and policy, since object Lock controls version deletion before expiry.

The competing option Enable S3 Versioning and establish recovery handling for future deletes would be useful when an S3 object is deleted by mistake and the bucket has no versioning. Versioning retains previous object versions. The present issue is security must ensure archive objects cannot be deleted for a regulated retention period; it is more directly addressed by Apply Object Lock retention with the required mode and policy. Object Lock controls version deletion before expiry.

The competing option Choose suitable storage tiers/retrieval timing for recovery objectives would be useful when an application needs immediate access after a Region outage but only deep-archive objects exist elsewhere. Deep archives may not meet minute-scale RTOs. The present issue is a second-region copy is required but objects use customer KMS keys; it is more directly addressed by Configure CRR with S3 versioning and source/destination KMS permissions. Cross-region encrypted replication needs explicit cryptographic authorization.

The option Backfill through S3 Batch Replication for eligible objects addresses a separate condition: legacy data is not present in the DR bucket after a new CRR rule. Ordinary rules start with eligible new operations. The actual requirement is a second-region copy is required but objects use customer KMS keys. Recommended corrective action: Configure CRR with S3 versioning and source/destination KMS permissions. Cross-region encrypted replication needs explicit cryptographic authorization.

Apply Object Lock retention with the required mode and policy would help if security must ensure archive objects cannot be deleted for a regulated retention period. Object Lock controls version deletion before expiry. That is not the symptom described here: a second-region copy is required but objects use customer KMS keys. The matching response is Configure CRR with S3 versioning and source/destination KMS permissions, because cross-region encrypted replication needs explicit cryptographic authorization.

The competing option Apply Object Lock retention with the required mode and policy would be useful when security must ensure archive objects cannot be deleted for a regulated retention period. Object Lock controls version deletion before expiry. The present issue is legacy data is not present in the DR bucket after a new CRR rule; it is more directly addressed by Backfill through S3 Batch Replication for eligible objects. Ordinary rules start with eligible new operations.

The option Enable S3 Versioning and establish recovery handling for future deletes addresses a separate condition: an S3 object is deleted by mistake and the bucket has no versioning. Versioning retains previous object versions. The actual requirement is legacy data is not present in the DR bucket after a new CRR rule. Recommended corrective action: Backfill through S3 Batch Replication for eligible objects. Ordinary rules start with eligible new operations.

For the alternative failure a second-region copy is required but objects use customer KMS keys, the control Configure CRR with S3 versioning and source/destination KMS permissions is relevant: cross-region encrypted replication needs explicit cryptographic authorization. Here the evidence instead is legacy data is not present in the DR bucket after a new CRR rule. The selected technical mechanism is Backfill through S3 Batch Replication for eligible objects: ordinary rules start with eligible new operations.

The option Enable S3 Versioning and establish recovery handling for future deletes addresses a separate condition: an S3 object is deleted by mistake and the bucket has no versioning. Versioning retains previous object versions. The actual requirement is an application needs immediate access after a Region outage but only deep-archive objects exist elsewhere. Choose suitable storage tiers/retrieval timing for recovery objectives instead: Deep archives may not meet minute-scale RTOs.

For the alternative failure security must ensure archive objects cannot be deleted for a regulated retention period, the control Apply Object Lock retention with the required mode and policy is relevant: object Lock controls version deletion before expiry. Here the evidence instead is an application needs immediate access after a Region outage but only deep-archive objects exist elsewhere. The selected technical mechanism is Choose suitable storage tiers/retrieval timing for recovery objectives: deep archives may not meet minute-scale RTOs.

Configure CRR with S3 versioning and source/destination KMS permissions solves a different operational problem where a second-region copy is required but objects use customer KMS keys. Cross-region encrypted replication needs explicit cryptographic authorization. It does not directly address an application needs immediate access after a Region outage but only deep-archive objects exist elsewhere. The case calls for Choose suitable storage tiers/retrieval timing for recovery objectives, since deep archives may not meet minute-scale RTOs.