Amazon AWS SAA-C03 Event-Driven Architectures, APIs, Queues, Messaging, and Workflow Orchestration Practice Test 1

 

Topic 07 Practice Test 1 covers Event-Driven Architectures, APIs, Queues, Messaging, and Workflow Orchestration for AWS SAA-C03. For broader exam preparation, review the AWS SAA-C03 Exam Dumps. Every option includes focused technical reasoning explaining both the AWS architecture concept and its fit to the scenario.

Question 1

An order service emits structured domain events. Billing, inventory, and fraud systems need different subsets, and new consumers should be added without changing the producer. Which design choice best route domain events to independently evolving consumers based on event content? Choose ONE.

1. Amazon SQS standard queue
2. EventBridge event bus with content-based rules
3. Amazon SNS standard topic
4. API Gateway HTTP API

Correct Answer(s)

 

B

Rationale

1. Amazon SQS standard queue stores messages durably so independent consumers can absorb variable producer rates with at-least-once delivery and very high throughput. Here, An order service emits structured domain…. The design must route domain events to independently evolving consumers based…. Its behavior does not match the requested outcome.
2. EventBridge event bus with content-based rules routes matching events by fields in the event pattern and can send matched events to AWS or cross-account targets. Here, An order service emits structured domain…. The design must route domain events to independently evolving consumers based…. That is the strongest native fit.
3. Amazon SNS standard topic fans each publication out to multiple subscribed endpoints and is suited to broad pub/sub delivery when strict FIFO semantics are unnecessary. Here, An order service emits structured domain…. The design must route domain events to independently evolving consumers based…. It can complement the design but not satisfy this need.
4. API Gateway HTTP API offers a lower-cost RESTful frontend with built-in JWT authorizers, OIDC support, CORS, and automatic deployments. Here, An order service emits structured domain…. The design must route domain events to independently evolving consumers based…. Its semantics differ from the required behavior.

 

Question 2

A checkout service must notify three independent processors. Each processor needs its own durable backlog so one slow processor never delays the others. Which design choice best fan out one publication into separate durable consumer backlogs? Choose ONE.

1. EventBridge Scheduler
2. Amazon SQS standard queue
3. Step Functions Parallel state
4. SNS topic with separate SQS subscriptions

Correct Answer(s)

 

D

Rationale

1. EventBridge Scheduler invokes a target at a specified one-time or recurring schedule and is suited to scheduled rather than event-pattern triggers. Here, A checkout service must notify three…. The design must fan out one publication into separate durable consumer…. It would leave the controlling constraint unresolved.
2. Amazon SQS standard queue provides a durable asynchronous buffer that decouples senders from receivers and lets workers process messages at their own pace. Here, A checkout service must notify three…. The design must fan out one publication into separate durable consumer…. It lacks the specific behavior required.
3. Step Functions Parallel state starts multiple independent branches concurrently and waits for all of them before the workflow continues. Here, A checkout service must notify three…. The design must fan out one publication into separate durable consumer…. It is plausible here but solves a different problem.
4. SNS topic with separate SQS subscriptions gives each consumer its own durable backlog while a single publication is fanned out to all subscribed queues. Here, A checkout service must notify three…. The design must fan out one publication into separate durable consumer…. That choice fits the resilience objective.

 

Question 3

An SNS FIFO topic carries ordered order-state events for several business units. One FIFO queue subscriber should receive only events for businessUnit=west, and publishers must keep using the same ordered topic. Which design choice best filter one FIFO subscription without giving up the topic’s ordered delivery model? Choose ONE.

1. SNS FIFO subscription filtering
2. EventBridge event pattern filtering
3. SNS topic with separate SQS subscriptions
4. Amazon SNS standard topic

Correct Answer(s)

 

A

Rationale

1. SNS FIFO subscription filtering lets each subscription on an SNS FIFO topic receive only matching messages while the FIFO topic retains ordered deduplicated delivery semantics. Here, The source is an SNS FIFO…. The design must filter one FIFO subscription without giving up the…. It delivers the required integration behavior.
2. EventBridge event pattern filtering matches only events whose structured fields satisfy the rule pattern, avoiding consumer-side polling and discard logic. Here, The source is an SNS FIFO…. The design must filter one FIFO subscription without giving up the…. That choice would not deliver the required semantics.
3. SNS topic with separate SQS subscriptions gives each consumer its own durable backlog while a single publication is fanned out to all subscribed queues. Here, The source is an SNS FIFO…. The design must filter one FIFO subscription without giving up the…. The service is valid, but not for this decision.
4. Amazon SNS standard topic implements managed publish/subscribe fan-out so one published message can be pushed to many independently configured subscriptions. Here, The source is an SNS FIFO…. The design must filter one FIFO subscription without giving up the…. It does not implement the needed control.

 

Question 4

A telemetry producer sends a very large stream of independent records. Consumers can tolerate occasional duplicate delivery and do not need ordering, so the priority is scalable parallel processing rather than FIFO semantics. Which design choice best choose the queue type optimized for high-throughput unordered asynchronous processing? Choose ONE.

1. SNS FIFO topic with SQS FIFO subscriptions
2. Amazon SQS FIFO queue
3. Amazon SQS standard queue
4. Step Functions Standard Workflow

Correct Answer(s)

 

C

Rationale

1. SNS FIFO topic with SQS FIFO subscriptions fans ordered, deduplicated messages to FIFO queues when downstream consumers need ordered near-real-time delivery. Here, The workload prioritizes scalable parallel throughput…. The design must choose the queue type optimized for high-throughput unordered…. Another service owns the behavior being tested.
2. Amazon SQS FIFO queue preserves order within message groups and provides deduplication controls for workloads that cannot tolerate reordering. Here, The workload prioritizes scalable parallel throughput…. The design must choose the queue type optimized for high-throughput unordered…. It is related but not the direct mechanism.
3. Amazon SQS standard queue supports scalable asynchronous work queues without FIFO ordering guarantees, allowing many producers and consumers to operate independently. Here, The workload prioritizes scalable parallel throughput…. The design must choose the queue type optimized for high-throughput unordered…. That capability resolves the key constraint.
4. Step Functions Standard Workflow provides durable, auditable long-running orchestration with exactly-once workflow execution semantics unless retries are configured. Here, The workload prioritizes scalable parallel throughput…. The design must choose the queue type optimized for high-throughput unordered…. Its native function does not fit this scenario.

 

Question 5

A low-volume settlement stream must preserve one global business sequence from producer to consumer. Messages should never be intentionally reordered, and the workload does not need the parallelism of independent message groups. Which design choice best select a queue type that can serialize one ordered business stream? Choose ONE.

1. Amazon SNS standard topic
2. Amazon SQS FIFO queue
3. EventBridge event bus with content-based rules
4. Amazon SQS standard queue

Correct Answer(s)

 

B

Rationale

1. Amazon SNS standard topic broadcasts notifications to multiple subscribers and supports several endpoint types without creating a durable work backlog by itself. Here, One low-volume business stream must be…. The design must select a queue type that can serialize one…. Its operating model does not satisfy the decisive constraint.
2. Amazon SQS FIFO queue preserves order within message groups and provides deduplication controls for workloads that cannot tolerate reordering. Here, One low-volume business stream must be…. The design must select a queue type that can serialize one…. It matches the required delivery semantics.
3. EventBridge event bus with content-based rules routes matching events by fields in the event pattern and can send matched events to AWS or cross-account targets. Here, One low-volume business stream must be…. The design must select a queue type that can serialize one…. The scenario needs a capability this choice does not supply.
4. Amazon SQS standard queue stores messages durably so independent consumers can absorb variable producer rates with at-least-once delivery and very high throughput. Here, One low-volume business stream must be…. The design must select a queue type that can serialize one…. That option would not change the behavior that matters here.

 

Question 6

A FIFO queue handles events for thousands of customer IDs. Events for one customer must stay sequential, but different customers should run concurrently. Which design choice best partition FIFO processing so each customer is ordered without globally serializing the queue? Choose ONE.

1. SQS FIFO message group IDs
2. Amazon SQS standard queue
3. SQS visibility timeout
4. SQS message deduplication ID

Correct Answer(s)

 

A

Rationale

1. SQS FIFO message group IDs serialize messages within each group while allowing separate groups to be processed independently and concurrently. Here, A FIFO queue handles events for…. The design must partition FIFO processing so each customer is ordered…. That directly fits the requirement.
2. Amazon SQS standard queue provides a durable asynchronous buffer that decouples senders from receivers and lets workers process messages at their own pace. Here, A FIFO queue handles events for…. The design must partition FIFO processing so each customer is ordered…. It cannot directly provide the delivery behavior being selected.
3. SQS visibility timeout temporarily hides a received message from competing consumers while a worker is processing that delivery. Here, A FIFO queue handles events for…. The design must partition FIFO processing so each customer is ordered…. This would not produce the routing or control outcome requested.
4. SQS message deduplication ID lets a FIFO producer supply a token so retries inside the deduplication interval do not enqueue another copy. Here, A FIFO queue handles events for…. The design must partition FIFO processing so each customer is ordered…. The component serves another purpose in the architecture.

 

Question 7

A queue worker normally completes tasks in 15 seconds, but when a worker crashes its received task remains hidden for several minutes before another worker can retry it. The team wants failed work to become available sooner without changing retention. Which design choice best shorten the temporary in-flight invisibility window to improve crash recovery time? Choose ONE.

1. SQS delay queue or message timer
2. SQS long polling
3. SQS message retention period
4. SQS visibility timeout

Correct Answer(s)

 

D

Rationale

1. SQS delay queue or message timer defers visibility of newly sent standard-queue messages for a configured delay without running a separate scheduler. Here, Normal processing is short but crashed…. The design must shorten the temporary in-flight invisibility window to improve…. It addresses a neighboring concern instead.
2. SQS long polling waits for messages across SQS servers, reducing empty receives and false empty responses compared with short polling. Here, Normal processing is short but crashed…. The design must shorten the temporary in-flight invisibility window to improve…. Its semantics differ from the required behavior.
3. SQS message retention period controls how long unconsumed messages remain available in a queue before SQS deletes them. Here, Normal processing is short but crashed…. The design must shorten the temporary in-flight invisibility window to improve…. It can complement the design but not satisfy this need.
4. SQS visibility timeout controls how long an in-flight SQS message stays invisible after receipt before it can be delivered again. Here, Normal processing is short but crashed…. The design must shorten the temporary in-flight invisibility window to improve…. That behavior matches the scenario.

 

Question 8

A malformed job is retried repeatedly and consumes worker capacity. Engineers want repeated failures isolated for inspection after several receives. Which design choice best move persistently failing messages out of the primary processing path after a controlled retry count? Choose ONE.

1. SQS visibility timeout
2. EventBridge target dead-letter queue
3. SQS dead-letter queue with redrive policy
4. SQS message retention period

Correct Answer(s)

 

C

Rationale

1. SQS visibility timeout sets the temporary processing lock for received queue messages and therefore affects duplicate work and failure recovery time. Here, A malformed job is retried repeatedly…. The design must move persistently failing messages out of the primary…. Its purpose is adjacent rather than directly applicable.
2. EventBridge target dead-letter queue captures events that EventBridge cannot successfully deliver to a target after its retry policy is exhausted. Here, A malformed job is retried repeatedly…. The design must move persistently failing messages out of the primary…. It lacks the specific behavior required.
3. SQS dead-letter queue with redrive policy isolates messages that exceed a configured receive count so persistent failures can be inspected and later redriven. Here, A malformed job is retried repeatedly…. The design must move persistently failing messages out of the primary…. That is the appropriate managed mechanism.
4. SQS message retention period controls how long unconsumed messages remain available in a queue before SQS deletes them. Here, A malformed job is retried repeatedly…. The design must move persistently failing messages out of the primary…. It would leave the controlling constraint unresolved.

 

Question 9

A producer sends many small queue messages every second. Network round trips and per-request charges are significant, and the application can group several operations into one request while checking per-message results. Which design choice best reduce SQS API request overhead by processing several message operations per call? Choose ONE.

1. SQS batch actions
2. SQS visibility timeout
3. SQS message retention period
4. SQS long polling

Correct Answer(s)

 

A

Rationale

1. SQS batch actions send, delete, or change visibility for up to 10 messages per batch call, reducing request overhead and improving throughput. Here, High message volume makes per-message API…. The design must reduce SQS API request overhead by processing several…. It directly addresses the architecture decision.
2. SQS visibility timeout temporarily hides a received message from competing consumers while a worker is processing that delivery. Here, High message volume makes per-message API…. The design must reduce SQS API request overhead by processing several…. It targets a different integration concern.
3. SQS message retention period controls how long unconsumed messages remain available in a queue before SQS deletes them. Here, High message volume makes per-message API…. The design must reduce SQS API request overhead by processing several…. That choice would not deliver the required semantics.
4. SQS long polling waits for messages across SQS servers, reducing empty receives and false empty responses compared with short polling. Here, High message volume makes per-message API…. The design must reduce SQS API request overhead by processing several…. The service is valid, but not for this decision.

 

Question 10

A team will deploy a new fraud detector next month and wants to reprocess selected historical business events from the existing event bus without producers resending them. Which design choice best retain event-bus traffic and later replay a selected historical time window? Choose ONE.

1. Step Functions Standard Workflow
2. Amazon SNS standard topic
3. SQS dead-letter queue with redrive policy
4. EventBridge archive and replay

Correct Answer(s)

 

D

Rationale

1. Step Functions Standard Workflow provides durable, auditable long-running orchestration with exactly-once workflow execution semantics unless retries are configured. Here, A team will deploy a new…. The design must retain event-bus traffic and later replay a selected…. This mechanism is not responsible for the requested property.
2. Amazon SNS standard topic fans each publication out to multiple subscribed endpoints and is suited to broad pub/sub delivery when strict FIFO semantics are unnecessary. Here, A team will deploy a new…. The design must retain event-bus traffic and later replay a selected…. Its native function does not fit this scenario.
3. SQS dead-letter queue with redrive policy isolates messages that exceed a configured receive count so persistent failures can be inspected and later redriven. Here, A team will deploy a new…. The design must retain event-bus traffic and later replay a selected…. Another service owns the behavior being tested.
4. EventBridge archive and replay stores selected events from one event bus and can later replay a chosen time range back to that source bus. Here, A team will deploy a new…. The design must retain event-bus traffic and later replay a selected…. That behavior matches the scenario.

 

Question 11

Dozens of application accounts must publish operational events to a security account, where central rules decide which analysis targets receive them. Which design choice best centralize multi-account event ingestion and routing in one account? Choose ONE.

1. SNS topic with separate SQS subscriptions
2. Cross-account EventBridge event bus
3. Amazon SQS standard queue
4. API Gateway private REST API

Correct Answer(s)

 

B

Rationale

1. SNS topic with separate SQS subscriptions gives each consumer its own durable backlog while a single publication is fanned out to all subscribed queues. Here, Dozens of application accounts must publish…. The design must centralize multi-account event ingestion and routing in one…. The requirement calls for different managed-service semantics.
2. Cross-account EventBridge event bus accepts events from authorized producer accounts and centralizes routing through rules in a designated account. Here, Dozens of application accounts must publish…. The design must centralize multi-account event ingestion and routing in one…. That choice fits the resilience objective.
3. Amazon SQS standard queue supports scalable asynchronous work queues without FIFO ordering guarantees, allowing many producers and consumers to operate independently. Here, Dozens of application accounts must publish…. The design must centralize multi-account event ingestion and routing in one…. The scenario needs a capability this choice does not supply.
4. API Gateway private REST API exposes a REST API through interface VPC endpoints so it can be invoked without public internet reachability. Here, Dozens of application accounts must publish…. The design must centralize multi-account event ingestion and routing in one…. That option would not change the behavior that matters here.

 

Question 12

An EventBridge Pipe reads records from a supported source, but the target needs only three renamed fields from each record. The team does not need an enrichment call or custom Lambda logic. Which design choice best reshape pipe records before target delivery without invoking compute? Choose ONE.

1. EventBridge Pipes Lambda enrichment
2. Step Functions Express Workflow
3. EventBridge Pipe input transformation
4. EventBridge input transformer

Correct Answer(s)

 

C

Rationale

1. EventBridge Pipes Lambda enrichment invokes Lambda synchronously to add or look up information before a pipe sends the resulting payload to its target. Here, A pipe already connects source and…. The design must reshape pipe records before target delivery without invoking…. This would not produce the routing or control outcome requested.
2. Step Functions Express Workflow supports high-volume short-running orchestration and uses an at-least-once model for asynchronous executions. Here, A pipe already connects source and…. The design must reshape pipe records before target delivery without invoking…. It solves a related problem, not this requirement.
3. EventBridge Pipe input transformation reshapes source or enriched data inside a pipe before sending it to the target, avoiding custom glue code. Here, A pipe already connects source and…. The design must reshape pipe records before target delivery without invoking…. That preserves the intended asynchronous design.
4. EventBridge input transformer selects and reshapes fields from an event into the payload expected by a target without a transformation Lambda function. Here, A pipe already connects source and…. The design must reshape pipe records before target delivery without invoking…. It cannot directly provide the delivery behavior being selected.

 

Question 13

A mortgage workflow can wait days for documents and must preserve an auditable execution history. Individual business actions are not designed for duplicate workflow execution. Which design choice best orchestrate a long-running durable process with exactly-once workflow execution semantics? Choose ONE.

1. EventBridge Scheduler
2. Amazon SQS standard queue
3. Step Functions Express Workflow
4. Step Functions Standard Workflow

Correct Answer(s)

 

D

Rationale

1. EventBridge Scheduler invokes a target at a specified one-time or recurring schedule and is suited to scheduled rather than event-pattern triggers. Here, A mortgage workflow can wait days…. The design must orchestrate a long-running durable process with exactly-once workflow…. It can complement the design but not satisfy this need.
2. Amazon SQS standard queue stores messages durably so independent consumers can absorb variable producer rates with at-least-once delivery and very high throughput. Here, A mortgage workflow can wait days…. The design must orchestrate a long-running durable process with exactly-once workflow…. Its semantics differ from the required behavior.
3. Step Functions Express Workflow supports high-volume short-running orchestration and uses an at-least-once model for asynchronous executions. Here, A mortgage workflow can wait days…. The design must orchestrate a long-running durable process with exactly-once workflow…. Its behavior does not match the requested outcome.
4. Step Functions Standard Workflow provides durable, auditable long-running orchestration with exactly-once workflow execution semantics unless retries are configured. Here, A mortgage workflow can wait days…. The design must orchestrate a long-running durable process with exactly-once workflow…. That is the strongest native fit.

 

Question 14

An IoT ingestion flow launches very high volumes of short, idempotent processing workflows that always finish within a few minutes. Which design choice best run high-throughput short-lived orchestration where at-least-once execution is acceptable? Choose ONE.

1. Step Functions Express Workflow
2. Step Functions callback with task token
3. API Gateway WebSocket API
4. Step Functions Standard Workflow

Correct Answer(s)

 

A

Rationale

1. Step Functions Express Workflow supports high-volume short-running orchestration and uses an at-least-once model for asynchronous executions. Here, An IoT ingestion flow launches very…. The design must run high-throughput short-lived orchestration where at-least-once execution is…. That choice fits the resilience objective.
2. Step Functions callback with task token pauses a Standard workflow until an external actor returns the task token, fitting human or external-system callbacks. Here, An IoT ingestion flow launches very…. The design must run high-throughput short-lived orchestration where at-least-once execution is…. It is plausible here but solves a different problem.
3. API Gateway WebSocket API maintains stateful two-way client connections so backends can push messages through connection callbacks. Here, An IoT ingestion flow launches very…. The design must run high-throughput short-lived orchestration where at-least-once execution is…. It lacks the specific behavior required.
4. Step Functions Standard Workflow provides durable, auditable long-running orchestration with exactly-once workflow execution semantics unless retries are configured. Here, An IoT ingestion flow launches very…. The design must run high-throughput short-lived orchestration where at-least-once execution is…. It would leave the controlling constraint unresolved.

 

Question 15

A loan approval state machine must pause for a human reviewer and resume only after the review system sends a callback tied to that exact workflow task. Which design choice best pause orchestration until an external approval system returns a correlation token? Choose ONE.

1. Amazon SNS standard topic
2. Step Functions Wait state
3. Step Functions callback with task token
4. Step Functions Express Workflow

Correct Answer(s)

 

C

Rationale

1. Amazon SNS standard topic implements managed publish/subscribe fan-out so one published message can be pushed to many independently configured subscriptions. Here, A loan approval state machine must…. The design must pause orchestration until an external approval system returns…. The service is valid, but not for this decision.
2. Step Functions Wait state pauses workflow progress until a duration or timestamp without keeping compute running during the delay. Here, A loan approval state machine must…. The design must pause orchestration until an external approval system returns…. It targets a different integration concern.
3. Step Functions callback with task token pauses a Standard workflow until an external actor returns the task token, fitting human or external-system callbacks. Here, A loan approval state machine must…. The design must pause orchestration until an external approval system returns…. That directly fits the requirement.
4. Step Functions Express Workflow supports high-volume short-running orchestration and uses an at-least-once model for asynchronous executions. Here, A loan approval state machine must…. The design must pause orchestration until an external approval system returns…. It does not implement the needed control.

 

Question 16

A workflow receives a JSON array containing hundreds of independent files. The same validation sequence should run for every file with controlled concurrency. Which design choice best apply one workflow branch repeatedly across items in a collection? Choose ONE.

1. Step Functions Parallel state
2. Step Functions Map state
3. Amazon SQS FIFO queue
4. EventBridge input transformer

Correct Answer(s)

 

B

Rationale

1. Step Functions Parallel state starts multiple independent branches concurrently and waits for all of them before the workflow continues. Here, A workflow receives a JSON array…. The design must apply one workflow branch repeatedly across items in…. This mechanism is not responsible for the requested property.
2. Step Functions Map state runs the same workflow logic over a collection of items and can provide controlled parallel processing. Here, A workflow receives a JSON array…. The design must apply one workflow branch repeatedly across items in…. It directly satisfies the design need.
3. Amazon SQS FIFO queue preserves order within message groups and provides deduplication controls for workloads that cannot tolerate reordering. Here, A workflow receives a JSON array…. The design must apply one workflow branch repeatedly across items in…. It is related but not the direct mechanism.
4. EventBridge input transformer selects and reshapes fields from an event into the payload expected by a target without a transformation Lambda function. Here, A workflow receives a JSON array…. The design must apply one workflow branch repeatedly across items in…. Another service owns the behavior being tested.

 

Question 17

A live trading dashboard needs servers to push price updates to browsers over long-lived two-way connections after each client subscribes. Which design choice best provide stateful bidirectional API connections that allow backend push to connected clients? Choose ONE.

1. API Gateway REST API
2. Amazon SNS standard topic
3. API Gateway WebSocket API
4. API Gateway HTTP API

Correct Answer(s)

 

C

Rationale

1. API Gateway REST API supports richer API-management features such as API keys, usage plans, request validation, WAF integration, caching, and private endpoints. Here, A live trading dashboard needs servers…. The design must provide stateful bidirectional API connections that allow backend…. That option would not change the behavior that matters here.
2. Amazon SNS standard topic broadcasts notifications to multiple subscribers and supports several endpoint types without creating a durable work backlog by itself. Here, A live trading dashboard needs servers…. The design must provide stateful bidirectional API connections that allow backend…. Its operating model does not satisfy the decisive constraint.
3. API Gateway WebSocket API maintains stateful two-way client connections so backends can push messages through connection callbacks. Here, A live trading dashboard needs servers…. The design must provide stateful bidirectional API connections that allow backend…. It provides the requested workflow behavior.
4. API Gateway HTTP API offers a lower-cost RESTful frontend with built-in JWT authorizers, OIDC support, CORS, and automatic deployments. Here, A live trading dashboard needs servers…. The design must provide stateful bidirectional API connections that allow backend…. The requirement calls for different managed-service semantics.

 

Question 18

A mobile backend exposes simple Lambda endpoints, uses OAuth 2.0 JWTs, and does not need API keys, request validation, WAF, or private API endpoints. Cost should be minimized. Which design choice best choose the lower-cost API Gateway product that natively supports JWT authorization? Choose ONE.

1. EventBridge API destination
2. API Gateway HTTP API
3. API Gateway WebSocket API
4. API Gateway REST API

Correct Answer(s)

 

B

Rationale

1. EventBridge API destination delivers matching events to an HTTPS endpoint using a managed connection and configured authentication. Here, A mobile backend exposes simple Lambda…. The design must choose the lower-cost API Gateway product that natively…. It cannot directly provide the delivery behavior being selected.
2. API Gateway HTTP API offers a lower-cost RESTful frontend with built-in JWT authorizers, OIDC support, CORS, and automatic deployments. Here, A mobile backend exposes simple Lambda…. The design must choose the lower-cost API Gateway product that natively…. That preserves the intended asynchronous design.
3. API Gateway WebSocket API maintains stateful two-way client connections so backends can push messages through connection callbacks. Here, A mobile backend exposes simple Lambda…. The design must choose the lower-cost API Gateway product that natively…. It solves a related problem, not this requirement.
4. API Gateway REST API supports richer API-management features such as API keys, usage plans, request validation, WAF integration, caching, and private endpoints. Here, A mobile backend exposes simple Lambda…. The design must choose the lower-cost API Gateway product that natively…. This would not produce the routing or control outcome requested.

 

Question 19

A partner API requires API keys, per-client usage quotas, request-body validation, and AWS WAF integration. Which design choice best select the API Gateway product that supports advanced client management and validation features? Choose ONE.

1. API Gateway WebSocket API
2. API Gateway HTTP API
3. EventBridge API destination
4. API Gateway REST API

Correct Answer(s)

 

D

Rationale

1. API Gateway WebSocket API maintains stateful two-way client connections so backends can push messages through connection callbacks. Here, A partner API requires API keys…. The design must select the API Gateway product that supports advanced…. Its semantics differ from the required behavior.
2. API Gateway HTTP API offers a lower-cost RESTful frontend with built-in JWT authorizers, OIDC support, CORS, and automatic deployments. Here, A partner API requires API keys…. The design must select the API Gateway product that supports advanced…. It addresses a neighboring concern instead.
3. EventBridge API destination delivers matching events to an HTTPS endpoint using a managed connection and configured authentication. Here, A partner API requires API keys…. The design must select the API Gateway product that supports advanced…. Its behavior does not match the requested outcome.
4. API Gateway REST API supports richer API-management features such as API keys, usage plans, request validation, WAF integration, caching, and private endpoints. Here, A partner API requires API keys…. The design must select the API Gateway product that supports advanced…. It directly satisfies the design need.

 

Question 20

Every message entering a standard SQS queue should wait five minutes before any consumer can receive it. Producers all use the same delay, so per-message scheduling is unnecessary. Which design choice best apply one fixed initial delivery delay to all newly enqueued messages? Choose ONE.

1. SQS delay queue
2. Step Functions Wait state
3. SQS visibility timeout
4. EventBridge Scheduler

Correct Answer(s)

 

A

Rationale

1. SQS delay queue applies a queue-level delivery delay of up to 15 minutes so newly sent messages are initially hidden from consumers. Here, All new queue messages need the…. The design must apply one fixed initial delivery delay to all…. It matches the required delivery semantics.
2. Step Functions Wait state pauses workflow progress until a duration or timestamp without keeping compute running during the delay. Here, All new queue messages need the…. The design must apply one fixed initial delivery delay to all…. It lacks the specific behavior required.
3. SQS visibility timeout controls how long an in-flight SQS message stays invisible after receipt before it can be delivered again. Here, All new queue messages need the…. The design must apply one fixed initial delivery delay to all…. Its purpose is adjacent rather than directly applicable.
4. EventBridge Scheduler invokes a target at a specified one-time or recurring schedule and is suited to scheduled rather than event-pattern triggers. Here, All new queue messages need the…. The design must apply one fixed initial delivery delay to all…. It is plausible here but solves a different problem.

• < Amazon AWS SAA-C03 Data Governance, Backup, Replication, Retention, Lifecycle, and Access Controls Practice Test 2
• Amazon AWS SAA-C03 Event-Driven Architectures, APIs, Queues, Messaging, and Workflow Orchestration Practice Test 2 >