Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 27
Question 260
A partner SaaS publishes events into the company's account; the team wants no custom poller. Which integration is suited to this delivery?
- Publish events to an EventBridge event bus with rules targeting each consumer.
- Use an EventBridge event pattern matching the source, detail-type, and stopped state.
- Use an EventBridge partner event source associated with an authorized event bus.
- Send matching events to a cross-account EventBridge bus with an explicit resource policy.
Explanation
Correct Answer
C:Partner event sources allow supported SaaS publishers to deliver into EventBridge for rule routing. Confirm events appear on the partner-associated bus and trigger a test rule.
Incorrect Answers
A:EventBridge rules match structured event patterns and forward events without producer-specific consumer routing. Use an EventBridge partner event source associated with an authorized event bus. Confirm events appear on the partner-associated bus and trigger a test rule.
B:Structured patterns can restrict routing to selected service event attributes rather than text matching messages. Use an EventBridge partner event source associated with an authorized event bus. Confirm events appear on the partner-associated bus and trigger a test rule.
D:Cross-account event buses use permissions and rules to route authorized events into the monitoring account. Use an EventBridge partner event source associated with an authorized event bus. Confirm events appear on the partner-associated bus and trigger a test rule.
Question 261
A scheduled report should invoke a target every weekday at a fixed time with timezone handling. Which service is suitable?
- Publish events to an EventBridge event bus with rules targeting each consumer.
- Create an EventBridge Scheduler schedule with the proper cron expression and timezone.
- Send matching events to a cross-account EventBridge bus with an explicit resource policy.
- Configure an event-bus archive and replay the desired interval to that bus.
Explanation
Correct Answer
B:EventBridge Scheduler invokes configured targets at schedule times without a continuously running timer host. Verify the next scheduled executions across daylight-saving changes for that timezone.
Incorrect Answers
A:EventBridge rules match structured event patterns and forward events without producer-specific consumer routing. Create an EventBridge Scheduler schedule with the proper cron expression and timezone. Verify the next scheduled executions across daylight-saving changes for that timezone.
C:Cross-account event buses use permissions and rules to route authorized events into the monitoring account. Create an EventBridge Scheduler schedule with the proper cron expression and timezone. Verify the next scheduled executions across daylight-saving changes for that timezone.
D:EventBridge archives retain eligible events and replay restores matched events for reprocessing. Create an EventBridge Scheduler schedule with the proper cron expression and timezone. Verify the next scheduled executions across daylight-saving changes for that timezone.
Question 262
Events arriving from one account must be routed centrally to a monitoring account. Which access and routing model fits?
- Configure an event-bus archive and replay the desired interval to that bus.
- Publish events to an EventBridge event bus with rules targeting each consumer.
- Use EventBridge rules with precise event patterns for the two accepted event types.
- Send matching events to a cross-account EventBridge bus with an explicit resource policy.
Explanation
Correct Answer
D:Cross-account event buses use permissions and rules to route authorized events into the monitoring account. Send a permitted and denied account event and verify the destination bus behavior.
Incorrect Answers
A:EventBridge archives retain eligible events and replay restores matched events for reprocessing. Send matching events to a cross-account EventBridge bus with an explicit resource policy. Send a permitted and denied account event and verify the destination bus behavior.
B:EventBridge rules match structured event patterns and forward events without producer-specific consumer routing. Send matching events to a cross-account EventBridge bus with an explicit resource policy. Send a permitted and denied account event and verify the destination bus behavior.
C:Event-pattern matching filters before invoking a target and avoids unnecessary worker starts. Send matching events to a cross-account EventBridge bus with an explicit resource policy. Send a permitted and denied account event and verify the destination bus behavior.
Question 263
A producer emits ten event types, but the ingestion worker needs only two. How can the worker avoid parsing the rest?
- Send matching events to a cross-account EventBridge bus with an explicit resource policy.
- Use EventBridge rules with precise event patterns for the two accepted event types.
- Use an EventBridge event pattern matching the source, detail-type, and stopped state.
- Publish events to an EventBridge event bus with rules targeting each consumer.
Explanation
Correct Answer
B:Event-pattern matching filters before invoking a target and avoids unnecessary worker starts. Submit all ten types and count only the two accepted target invocations.
Incorrect Answers
A:Cross-account event buses use permissions and rules to route authorized events into the monitoring account. Use EventBridge rules with precise event patterns for the two accepted event types. Submit all ten types and count only the two accepted target invocations.
C:Structured patterns can restrict routing to selected service event attributes rather than text matching messages. Use EventBridge rules with precise event patterns for the two accepted event types. Submit all ten types and count only the two accepted target invocations.
D:EventBridge rules match structured event patterns and forward events without producer-specific consumer routing. Use EventBridge rules with precise event patterns for the two accepted event types. Submit all ten types and count only the two accepted target invocations.
Question 264
An EventBridge rule targets a service that intermittently rejects delivery. How should failed invocations be captured?
- Set an appropriate target retry policy and dead-letter queue.
- Send matching events to a cross-account EventBridge bus with an explicit resource policy.
- Configure an event-bus archive and replay the desired interval to that bus.
- Publish events to an EventBridge event bus with rules targeting each consumer.
Explanation
Correct Answer
A:EventBridge target retries and DLQ storage provide bounded recovery and inspection of undeliverable events. Force target rejection and inspect both retry metrics and the configured DLQ.
Incorrect Answers
B:Cross-account event buses use permissions and rules to route authorized events into the monitoring account. Set an appropriate target retry policy and dead-letter queue. Force target rejection and inspect both retry metrics and the configured DLQ.
C:EventBridge archives retain eligible events and replay restores matched events for reprocessing. Set an appropriate target retry policy and dead-letter queue. Force target rejection and inspect both retry metrics and the configured DLQ.
D:EventBridge rules match structured event patterns and forward events without producer-specific consumer routing. Set an appropriate target retry policy and dead-letter queue. Force target rejection and inspect both retry metrics and the configured DLQ.
Question 265
An approval workflow has five dependent services and must resume after a worker crashes. What manages orchestration without placing state in one Lambda?
- Use a Step Functions Parallel state with branches for each validation.
- Use a Step Functions Standard workflow with a durable state transition model.
- Use a Step Functions state machine with service integrations and retry states.
- Configure a Step Functions Retry policy with bounded backoff and matching errors.
Explanation
Correct Answer
C:Durable workflow state tracks progress and transitions independently of any particular compute invocation. Fail one integrated step and inspect execution history and configured recovery.
Incorrect Answers
A:Parallel branches coordinate concurrent work and join when branches complete according to workflow semantics. Use a Step Functions state machine with service integrations and retry states. Fail one integrated step and inspect execution history and configured recovery.
B:Standard workflows support long-running executions and durable audit-oriented histories unlike short-lived synchronous patterns. Use a Step Functions state machine with service integrations and retry states. Fail one integrated step and inspect execution history and configured recovery.
D:State-level retry rules can back off transient failures without every Lambda reimplementing retry logic. Use a Step Functions state machine with service integrations and retry states. Fail one integrated step and inspect execution history and configured recovery.
Question 266
A workflow should execute three independent validation checks concurrently and then continue only when all finish. Which state type fits?
- Use a Step Functions Standard workflow with a durable state transition model.
- Use a Step Functions state machine with service integrations and retry states.
- Use a Step Functions Parallel state with branches for each validation.
- Use a Step Functions Map state with controlled concurrency.
Explanation
Correct Answer
C:Parallel branches coordinate concurrent work and join when branches complete according to workflow semantics. Record branch start and completion times and confirm the join waits for all branches.
Incorrect Answers
A:Standard workflows support long-running executions and durable audit-oriented histories unlike short-lived synchronous patterns. Use a Step Functions Parallel state with branches for each validation. Record branch start and completion times and confirm the join waits for all branches.
B:Durable workflow state tracks progress and transitions independently of any particular compute invocation. Use a Step Functions Parallel state with branches for each validation. Record branch start and completion times and confirm the join waits for all branches.
D:A Map state iterates over items and manages separate executions rather than hardcoding each item as a state. Use a Step Functions Parallel state with branches for each validation. Record branch start and completion times and confirm the join waits for all branches.
Question 267
A data processing job needs to invoke the same transform once per item of a list. Which workflow structure is appropriate?
- Use a Step Functions Standard workflow with a durable state transition model.
- Use a Step Functions Map state with controlled concurrency.
- Use a Step Functions state machine with service integrations and retry states.
- Use a Step Functions task token callback and resume on SendTaskSuccess or failure.
Explanation
Correct Answer
B:A Map state iterates over items and manages separate executions rather than hardcoding each item as a state. Run ten distinct items and inspect each iteration's outcome.
Incorrect Answers
A:Standard workflows support long-running executions and durable audit-oriented histories unlike short-lived synchronous patterns. Use a Step Functions Map state with controlled concurrency. Run ten distinct items and inspect each iteration's outcome.
C:Durable workflow state tracks progress and transitions independently of any particular compute invocation. Use a Step Functions Map state with controlled concurrency. Run ten distinct items and inspect each iteration's outcome.
D:A callback task can wait durably for an external actor rather than hold a Lambda invocation open. A Map state iterates over items and manages separate executions rather than hardcoding each item as a state.
Question 268
An external human must authorize a transaction before a workflow proceeds. Which integration pattern works?
- Use Catch transitions to explicit compensating steps for completed operations.
- Configure a Step Functions Retry policy with bounded backoff and matching errors.
- Use a Step Functions Map state with controlled concurrency.
- Use a Step Functions task token callback and resume on SendTaskSuccess or failure.
Explanation
Correct Answer
D:A callback task can wait durably for an external actor rather than hold a Lambda invocation open. Pause a test execution and resume it with the valid callback token.
Incorrect Answers
A:Workflow error paths can implement saga-style compensation; Step Functions does not automatically roll back external writes. Use a Step Functions task token callback and resume on SendTaskSuccess or failure. Pause a test execution and resume it with the valid callback token.
B:State-level retry rules can back off transient failures without every Lambda reimplementing retry logic. Use a Step Functions task token callback and resume on SendTaskSuccess or failure. Pause a test execution and resume it with the valid callback token.
C:A Map state iterates over items and manages separate executions rather than hardcoding each item as a state. Use a Step Functions task token callback and resume on SendTaskSuccess or failure. Pause a test execution and resume it with the valid callback token.
Question 269
A downstream service is rate-limited and a task returns a transient error. How should retry behavior be expressed?
- Use a Step Functions task token callback and resume on SendTaskSuccess or failure.
- Use a Step Functions state machine with service integrations and retry states.
- Configure a Step Functions Retry policy with bounded backoff and matching errors.
- Use Catch transitions to explicit compensating steps for completed operations.
Explanation
Correct Answer
C:State-level retry rules can back off transient failures without every Lambda reimplementing retry logic. Inject throttling and verify delayed attempts and eventual failure handling.
Incorrect Answers
A:A callback task can wait durably for an external actor rather than hold a Lambda invocation open. Configure a Step Functions Retry policy with bounded backoff and matching errors. Inject throttling and verify delayed attempts and eventual failure handling.
B:Durable workflow state tracks progress and transitions independently of any particular compute invocation. Configure a Step Functions Retry policy with bounded backoff and matching errors. Inject throttling and verify delayed attempts and eventual failure handling.
D:Workflow error paths can implement saga-style compensation; Step Functions does not automatically roll back external writes. Configure a Step Functions Retry policy with bounded backoff and matching errors. Inject throttling and verify delayed attempts and eventual failure handling.
Question 270
A payment workflow must run compensation when an earlier step succeeds but a later step fails. How should the architect model this?
- Use Catch transitions to explicit compensating steps for completed operations.
- Use a Step Functions task token callback and resume on SendTaskSuccess or failure.
- Use a Step Functions state machine with service integrations and retry states.
- Use a Step Functions Parallel state with branches for each validation.
Explanation
Correct Answer
A:Workflow error paths can implement saga-style compensation; Step Functions does not automatically roll back external writes. Fail a later step and verify the compensating action reverses the prior side effect.
Incorrect Answers
B:A callback task can wait durably for an external actor rather than hold a Lambda invocation open. Use Catch transitions to explicit compensating steps for completed operations. Fail a later step and verify the compensating action reverses the prior side effect.
C:Durable workflow state tracks progress and transitions independently of any particular compute invocation. Use Catch transitions to explicit compensating steps for completed operations. Fail a later step and verify the compensating action reverses the prior side effect.
D:Parallel branches coordinate concurrent work and join when branches complete according to workflow semantics. Workflow error paths can implement saga-style compensation; Step Functions does not automatically roll back external writes.