Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 25

Question 240

A company accepts S3 uploads from multiple contractors. It wants a uniform destination-owner policy instead of per-contractor ownership and ACL grants. Which tradeoff best matches the policy?

Choose S3 Object Ownership Bucket owner enforced and adapt upload clients to ACL-disabled requests.
Keep Object writer ownership and negotiate ACL access for each object.
Create a separate S3 Access Point for every vendor but retain Object writer ownership and per-object ACL grants for vendor uploads.
Give vendors shared AWS account root keys to upload without policies.

Explanation

Correct Answer

The destination account owns objects and manages permissions through policies, reducing dependence on external uploaders’ ACL behavior.

Incorrect Answers

This preserves the exact per-uploader administration the team wants to remove.

Access Points can scope requests but do not inherently change the bucket object ownership mode. Bucket owner enforced disables ACLs and makes the destination owner control uploaded objects.

Root sharing is unsafe and unnecessary for cross-account uploads.

Question 241

A product service receives image-upload jobs faster than its resize workers can process them. Uploads must be accepted immediately and workers must scale independently. Which AWS component best decouples request acceptance from processing?

Queue independent resize jobs in Amazon SQS and let workers retrieve and acknowledge them asynchronously.
Keep the upload HTTP request open until every resize completes.
Send jobs directly to one fixed EC2 instance with no buffering.
Use SNS to broadcast every resize task directly to a transient HTTP worker without a durable retry queue, assuming worker downtime retains every pending task.

Explanation

Correct Answer

SQS buffers work so producers can return quickly and consumers process at their own capacity, with retry and duplicate-safe handling.

Incorrect Answers

Synchronous coupling exposes users to worker delays and failures.

One worker failure or burst can lose or back up requests without durable decoupling.

SNS can fan out notifications, but direct HTTP delivery alone is not a durable worker backlog equivalent to SQS. Use an SQS queue for independent demand buffering and retries.

Question 242

An order processor must handle modifications to each order in sequence while different orders may proceed concurrently. The sender can retry delivery. Which SQS configuration preserves per-order sequencing?

Use an SQS FIFO queue with MessageGroupId per order and stable deduplication semantics, then make consumers idempotent.
Use a standard queue and assume global message processing order is guaranteed.
Use a different FIFO message group for each update of the same order.
Use a standard SQS queue with a per-order message attribute and assume the attribute alone enforces FIFO ordering across concurrent consumers.

Explanation

Correct Answer

FIFO message groups serialize messages within each group, while independent groups can be processed concurrently; deduplication windows are bounded.

Incorrect Answers

Standard queues can deliver out of order and more than once.

That loses the serial dependency between updates for a single order.

A standard queue does not provide strict per-order sequencing merely because it carries an order ID in message attributes. FIFO and a stable MessageGroupId provide ordered lanes.

Question 243

A worker needs six minutes to process an SQS job but the queue visibility timeout is 30 seconds. Other workers repeatedly start the same job before the first finishes. Which setting should be corrected?

Make the queue visibility timeout zero for all long-running tasks.
Disable the consumer’s IAM permissions to delete messages permanently.
Use a visibility timeout appropriate for processing duration, with extensions when needed, and delete successfully processed messages.
Raise only the message retention period to 14 days while leaving visibility at 30 seconds, assuming retention keeps in-flight work invisible for six minutes.

Explanation

Correct Answer

Visibility timeout hides an in-flight message temporarily; when it expires before deletion, another consumer can receive the same work.

Incorrect Answers

Zero visibility enables immediate redelivery and duplicate processing.

Without acknowledgement the job is redelivered, not completed.

Retention governs how long messages remain stored in the queue; visibility controls the temporary lease after receive. Increasing retention cannot prevent premature redelivery.

Question 244

A consumer repeatedly fails a malformed message and the same work occupies a large share of processing capacity. Operations wants to isolate poison messages for investigation. Which SQS policy assists?

Configure a redrive policy and dead-letter queue after an appropriate maximum receive count.
Set MaxReceiveCount to infinity and never investigate failures.
Delete every failed message immediately without a recovery record.
Increase the queue visibility timeout for failing messages forever and treat the absence of new receives as a completed poison-message investigation.

Explanation

Correct Answer

A DLQ removes repeatedly failing messages from the main queue’s retry loop while retaining them for inspection and controlled replay.

Incorrect Answers

Unbounded retries can starve valid work and obscure persistent defects.

Blind deletion loses evidence and potentially recoverable business work.

Longer invisibility may delay retries, but it does not isolate the failing payload after a bounded number of attempts. A redrive policy and DLQ provide quarantine and replay controls.

Question 245

A new invoice event must independently reach compliance, analytics and customer-notification teams. One team’s outage must not prevent the other deliveries. What event fanout pattern fits?

Give all teams one shared SQS queue so exactly one consumer receives each event.
Call all three services synchronously from the invoice request and require every one to finish.
Publish to an SNS topic with separate SQS subscriptions for each team and independent consumer retry policy.
Publish invoice events once into a single SQS queue with three independent worker groups and assume each group receives its own complete copy.

Explanation

Correct Answer

SNS distributes a notification to subscribers, while per-team queues decouple availability and processing rates.

Incorrect Answers

Competing consumers divide messages rather than fan out each event to all teams.

A slow consumer would block the producer and couple availability.

SQS consumers on one ordinary queue compete for messages; there is no automatically separate delivery per team. SNS fanout with one queue per team preserves independent backlogs.

Question 246

A SaaS platform emits structured customer events and five microservices need to filter them by event source and detail fields. Producers should not know destination URLs. Which service routes these events?

Create an EC2 security group rule for every event type.
Use an SNS topic alone and assume that its basic subscriptions natively filter arbitrary nested event detail fields with the same event-pattern rules as EventBridge.
Use Amazon EventBridge event buses with event pattern rules and appropriate service targets.
Write events only to one synchronous API endpoint with no retries or fanout.

Explanation

Correct Answer

EventBridge filters structured events and routes them to independent supported targets without coupling each producer to consumer endpoints.

Incorrect Answers

Network firewall rules cannot inspect application event detail patterns.

SNS has subscription filter policies but their supported semantics and rules differ from EventBridge event patterns; the requested multi-field rule routing is a native EventBridge event-bus use case.

Direct single-consumer coupling defeats routing to several filtered targets.

Question 247

A billing job must run on the first business day of each month independently of customer web traffic. Operators need a managed schedule with retry targets. Which service fits?

Rely on users visiting the billing dashboard to trigger monthly processing.
Keep an always-on server with an unmonitored crontab as the only source of truth.
Use a weekly CloudWatch alarm with a fixed evaluation interval to represent the first holiday-adjusted business day of every month.
Use EventBridge Scheduler with a documented monthly/weekday trigger to invoke a calendar-aware billing task that checks holidays and first business-day rules; configure retry and failure handling.

Explanation

Correct Answer

EventBridge Scheduler reliably invokes a managed target, but a plain first-of-month cron expression does not cover every holiday-adjusted business date. The target must evaluate the organization’s authoritative business calendar and run idempotently, with retries and a DLQ where supported.

Incorrect Answers

Business schedule correctness cannot depend on user traffic.

It adds instance availability and maintenance dependencies unnecessarily.

Metric alarms respond to metric states, not a business calendar. A managed schedule can initiate a calendar-aware job, which must evaluate holidays separately.

Question 248

A claim requires validate → reserve funds → notify, with conditional compensation on errors. The business needs stateful execution history and retries rather than a single long Lambda function. Which architecture is appropriate?

Invoke all three steps simultaneously and assume execution order emerges from arrival time.
Store only the workflow name in Route 53 and expect it to coordinate tasks.
Use AWS Step Functions with explicit states, error handling and authorized task integrations.
Use several sequential Lambda calls directly from the browser and rely on a client reconnect to reconstruct a durable workflow execution history and compensate reserved funds.

Explanation

Correct Answer

A state machine encodes step order, branching, retries and catches while exposing workflow status independent of one function invocation.

Incorrect Answers

Reservation must follow successful validation and cannot safely race prerequisites.

DNS records resolve network names, but Step Functions state transitions and result-dependent retries require a workflow engine rather than a hosted-zone record.

Browser-level calls do not offer service-managed durable orchestration, consistent retries and branching across interruptions. Step Functions captures explicit state transitions and error handling.

Question 249

A payment workflow can remain open for days while awaiting human approval and must avoid duplicate workflow execution. Which Step Functions type should generally be evaluated?

Use Express and assume it can always run for days.
Use a Standard workflow with its durable long-running execution model and careful idempotency for external side effects.
Use only an SNS topic because it stores a waiting approval state for days.
Use EventBridge Scheduler to re-invoke the payment approval every minute, assuming each schedule invocation resumes the same durable in-progress transactional state automatically.

Explanation

Correct Answer

Standard workflows support long waits and detailed execution history. StartExecution can be idempotent for a running execution with the same name/input, but that protection has precise conditions and execution-name retention limits. External payment side effects still need idempotency keys and compensation.

Incorrect Answers

Express workflows have much shorter maximum duration.

SNS fanout does not provide workflow state transitions and approval waits.

Scheduler starts targeted calls; it does not itself persist a multiday workflow wait or execution history. Standard Step Functions is better suited to managed wait/callback state.

Question 250

A Lambda API function opens connections to an RDS database with limited session capacity. Sudden bursts of invocations overwhelm the DB. Which Lambda control can directly cap concurrent handlers?

Set the function memory as high as possible and expect fewer concurrent invocations automatically.
Increase API Gateway cache TTL and assume all writes become safe.
Increase the RDS max_connections setting and rely on Lambda burst concurrency to fall automatically as database session pressure rises.
Configure reserved concurrency for the function based on downstream capacity and queue/throttle excess requests appropriately.

Explanation

Correct Answer

Reserved concurrency provides a per-function limit that helps prevent Lambda bursts from opening more database work than it can support.

Incorrect Answers

Memory allocation affects resources per invocation, not an upper concurrency limit.

Caching does not guarantee a hard concurrency limit on all operations.

Raising the database limit only delays saturation; it does not place a hard bound on Lambda simultaneous execution or shield the database from uncontrolled bursts.

Pass Your Amazon AWS Certified Solutions Architect - Associate SAA-C03 Exam Easy!

Question 240

Explanation

Correct Answer

Incorrect Answers

Question 241

Explanation

Correct Answer

Incorrect Answers

Question 242

Explanation

Correct Answer

Incorrect Answers

Question 243

Explanation

Correct Answer

Incorrect Answers

Question 244

Explanation

Correct Answer

Incorrect Answers

Question 245

Explanation

Correct Answer

Incorrect Answers

Question 246

Explanation

Correct Answer

Incorrect Answers

Question 247

Explanation

Correct Answer

Incorrect Answers

Question 248

Explanation

Correct Answer

Incorrect Answers

Question 249

Explanation

Correct Answer

Incorrect Answers

Question 250

Explanation

Correct Answer

Incorrect Answers

AWS Certified Solutions Architect - Associate SAA-C03 Practice Tests