Amazon AWS Certified Solutions Architect - Associate SAA-C03 Bundle

The option Place stateless app instances in an EC2 Auto Scaling group behind an ALB addresses a separate condition: traffic bursts overwhelm one oversized instance while other capacity is unused. Horizontal scaling distributes requests across instances. The actual requirement is an Auto Scaling group keeps launching instances that fail its load-balancer health checks. Recommended corrective action: Enable and correctly configure ELB health checks and grace periods. Health evaluation determines whether instances are replaced.

Externalize session state to DynamoDB or ElastiCache as appropriate would help if user sessions disappear when an application instance is replaced. Stateless instances can be safely replaced if session state is external. That is not the symptom described here: an Auto Scaling group keeps launching instances that fail its load-balancer health checks. The matching response is Enable and correctly configure ELB health checks and grace periods, because health evaluation determines whether instances are replaced.

For the alternative failure request rate spikes unpredictably during sales, the control Use target tracking scaling on supported ALB request or utilization metrics is relevant: target tracking adjusts group size from measured load. Here the evidence instead is an Auto Scaling group keeps launching instances that fail its load-balancer health checks. The selected technical mechanism is Enable and correctly configure ELB health checks and grace periods: health evaluation determines whether instances are replaced.

Configure bounded Step Functions Retry settings with backoff would help if an asynchronous Lambda operation fails transiently and should retry with backoff. Explicit retry policies handle transient task failures. That is not the symptom described here: a three-step workflow needs retries and separate failure branches. The matching response is Orchestrate operations with AWS Step Functions state-machine transitions, because step Functions coordinates stateful workflow logic with error paths.

For the alternative failure operators need to inspect the exact failing state and execution history, the control Inspect Step Functions execution events, state input/output and failure details is relevant: execution histories identify the step where orchestration failed. Here the evidence instead is a three-step workflow needs retries and separate failure branches. The selected technical mechanism is Orchestrate operations with AWS Step Functions state-machine transitions: step Functions coordinates stateful workflow logic with error paths.

Model a saga with explicit compensation states for earlier committed work solves a different operational problem where a workflow failure must execute compensation for completed steps. Distributed transactions require application-level rollback semantics. It does not directly address a three-step workflow needs retries and separate failure branches. The case calls for Orchestrate operations with AWS Step Functions state-machine transitions, since step Functions coordinates stateful workflow logic with error paths.

For the alternative failure a three-step workflow needs retries and separate failure branches, the control Orchestrate operations with AWS Step Functions state-machine transitions is relevant: step Functions coordinates stateful workflow logic with error paths. Here the evidence instead is a workflow must wait for a person to approve a high-value refund. The selected technical mechanism is Use Step Functions callback token pattern or supported approval integration: callback workflows pause until an external decision resumes them.

The competing option Model a saga with explicit compensation states for earlier committed work would be useful when a workflow failure must execute compensation for completed steps. Distributed transactions require application-level rollback semantics. The present issue is a workflow must wait for a person to approve a high-value refund; it is more directly addressed by Use Step Functions callback token pattern or supported approval integration. Callback workflows pause until an external decision resumes them.

The option Configure bounded Step Functions Retry settings with backoff addresses a separate condition: an asynchronous Lambda operation fails transiently and should retry with backoff. Explicit retry policies handle transient task failures. The actual requirement is a workflow must wait for a person to approve a high-value refund. Recommended corrective action: Use Step Functions callback token pattern or supported approval integration. Callback workflows pause until an external decision resumes them.

The competing option Inspect Step Functions execution events, state input/output and failure details would be useful when operators need to inspect the exact failing state and execution history. Execution histories identify the step where orchestration failed. The present issue is an asynchronous Lambda operation fails transiently and should retry with backoff; it is more directly addressed by Configure bounded Step Functions Retry settings with backoff. Explicit retry policies handle transient task failures.

The option Model a saga with explicit compensation states for earlier committed work addresses a separate condition: a workflow failure must execute compensation for completed steps. Distributed transactions require application-level rollback semantics. The actual requirement is an asynchronous Lambda operation fails transiently and should retry with backoff. Recommended corrective action: Configure bounded Step Functions Retry settings with backoff. Explicit retry policies handle transient task failures.

Orchestrate operations with AWS Step Functions state-machine transitions would help if a three-step workflow needs retries and separate failure branches. Step Functions coordinates stateful workflow logic with error paths. That is not the symptom described here: an asynchronous Lambda operation fails transiently and should retry with backoff. The matching response is Configure bounded Step Functions Retry settings with backoff, because explicit retry policies handle transient task failures.

The competing option Orchestrate operations with AWS Step Functions state-machine transitions would be useful when a three-step workflow needs retries and separate failure branches. Step Functions coordinates stateful workflow logic with error paths. The present issue is a workflow failure must execute compensation for completed steps; it is more directly addressed by Model a saga with explicit compensation states for earlier committed work. Distributed transactions require application-level rollback semantics.

The option Use Step Functions callback token pattern or supported approval integration addresses a separate condition: a workflow must wait for a person to approve a high-value refund. Callback workflows pause until an external decision resumes them. The actual requirement is a workflow failure must execute compensation for completed steps. Recommended corrective action: Model a saga with explicit compensation states for earlier committed work. Distributed transactions require application-level rollback semantics.

Inspect Step Functions execution events, state input/output and failure details would help if operators need to inspect the exact failing state and execution history. Execution histories identify the step where orchestration failed. That is not the symptom described here: a workflow failure must execute compensation for completed steps. The matching response is Model a saga with explicit compensation states for earlier committed work, because distributed transactions require application-level rollback semantics.

The option Use Step Functions callback token pattern or supported approval integration addresses a separate condition: a workflow must wait for a person to approve a high-value refund. Callback workflows pause until an external decision resumes them. The actual requirement is operators need to inspect the exact failing state and execution history. Recommended corrective action: Inspect Step Functions execution events, state input/output and failure details. Execution histories identify the step where orchestration failed.

Configure bounded Step Functions Retry settings with backoff would help if an asynchronous Lambda operation fails transiently and should retry with backoff. Explicit retry policies handle transient task failures. That is not the symptom described here: operators need to inspect the exact failing state and execution history. The matching response is Inspect Step Functions execution events, state input/output and failure details, because execution histories identify the step where orchestration failed.

For the alternative failure a three-step workflow needs retries and separate failure branches, the control Orchestrate operations with AWS Step Functions state-machine transitions is relevant: step Functions coordinates stateful workflow logic with error paths. Here the evidence instead is operators need to inspect the exact failing state and execution history. The selected technical mechanism is Inspect Step Functions execution events, state input/output and failure details: execution histories identify the step where orchestration failed.

Define EventBridge rules that match the required event patterns would help if events with specific account and detail-type values need separate processing. Event patterns route only matching records. That is not the symptom described here: a service publishes domain events but must not know subscriber URLs. The matching response is Use EventBridge event buses and target rule subscriptions, because producers and consumers stay decoupled through event routing.

For the alternative failure a business wants event replay for a limited audit window, the control Configure an EventBridge archive and controlled replay where supported is relevant: event archives retain event-bus records for replay. Here the evidence instead is a service publishes domain events but must not know subscriber URLs. The selected technical mechanism is Use EventBridge event buses and target rule subscriptions: producers and consumers stay decoupled through event routing.

The competing option Configure bounded retry and dead-letter destination for target delivery would be useful when a consumer endpoint is unavailable when an event is delivered. EventBridge target delivery can retry and preserve failures for inspection. The present issue is a service publishes domain events but must not know subscriber URLs; it is more directly addressed by Use EventBridge event buses and target rule subscriptions. Producers and consumers stay decoupled through event routing.

For the alternative failure a business wants event replay for a limited audit window, the control Configure an EventBridge archive and controlled replay where supported is relevant: event archives retain event-bus records for replay. Here the evidence instead is events with specific account and detail-type values need separate processing. The selected technical mechanism is Define EventBridge rules that match the required event patterns: event patterns route only matching records.

Use EventBridge event buses and target rule subscriptions solves a different operational problem where a service publishes domain events but must not know subscriber URLs. Producers and consumers stay decoupled through event routing. It does not directly address events with specific account and detail-type values need separate processing. The case calls for Define EventBridge rules that match the required event patterns, since event patterns route only matching records.

The competing option Add an EventBridge resource policy constrained to intended sender principals would be useful when an integration partner can only push approved events to a shared bus. Event-bus policies govern cross-account event publishing. The present issue is events with specific account and detail-type values need separate processing; it is more directly addressed by Define EventBridge rules that match the required event patterns. Event patterns route only matching records.

Configure an EventBridge archive and controlled replay where supported solves a different operational problem where a business wants event replay for a limited audit window. Event archives retain event-bus records for replay. It does not directly address a consumer endpoint is unavailable when an event is delivered. The case calls for Configure bounded retry and dead-letter destination for target delivery, since eventBridge target delivery can retry and preserve failures for inspection.

The competing option Define EventBridge rules that match the required event patterns would be useful when events with specific account and detail-type values need separate processing. Event patterns route only matching records. The present issue is a consumer endpoint is unavailable when an event is delivered; it is more directly addressed by Configure bounded retry and dead-letter destination for target delivery. EventBridge target delivery can retry and preserve failures for inspection.

Use EventBridge event buses and target rule subscriptions would help if a service publishes domain events but must not know subscriber URLs. Producers and consumers stay decoupled through event routing. That is not the symptom described here: a consumer endpoint is unavailable when an event is delivered. The matching response is Configure bounded retry and dead-letter destination for target delivery, because eventBridge target delivery can retry and preserve failures for inspection.

The competing option Add an EventBridge resource policy constrained to intended sender principals would be useful when an integration partner can only push approved events to a shared bus. Event-bus policies govern cross-account event publishing. The present issue is a business wants event replay for a limited audit window; it is more directly addressed by Configure an EventBridge archive and controlled replay where supported. Event archives retain event-bus records for replay.

Configure bounded retry and dead-letter destination for target delivery would help if a consumer endpoint is unavailable when an event is delivered. EventBridge target delivery can retry and preserve failures for inspection. That is not the symptom described here: a business wants event replay for a limited audit window. The matching response is Configure an EventBridge archive and controlled replay where supported, because event archives retain event-bus records for replay.

For the alternative failure events with specific account and detail-type values need separate processing, the control Define EventBridge rules that match the required event patterns is relevant: event patterns route only matching records. Here the evidence instead is a business wants event replay for a limited audit window. The selected technical mechanism is Configure an EventBridge archive and controlled replay where supported: event archives retain event-bus records for replay.

Configure an EventBridge archive and controlled replay where supported would help if a business wants event replay for a limited audit window. Event archives retain event-bus records for replay. That is not the symptom described here: an integration partner can only push approved events to a shared bus. The matching response is Add an EventBridge resource policy constrained to intended sender principals, because event-bus policies govern cross-account event publishing.

For the alternative failure events with specific account and detail-type values need separate processing, the control Define EventBridge rules that match the required event patterns is relevant: event patterns route only matching records. Here the evidence instead is an integration partner can only push approved events to a shared bus. The selected technical mechanism is Add an EventBridge resource policy constrained to intended sender principals: event-bus policies govern cross-account event publishing.

Use EventBridge event buses and target rule subscriptions solves a different operational problem where a service publishes domain events but must not know subscriber URLs. Producers and consumers stay decoupled through event routing. It does not directly address an integration partner can only push approved events to a shared bus. The case calls for Add an EventBridge resource policy constrained to intended sender principals, since event-bus policies govern cross-account event publishing.