Free SAA-C03 Exam Braindumps
AWS Certified Solutions Architect - Associate SAA-C03 Questions 361–365 (page: 74)

Updated On: 16-Mar-2026

A company hosts a multiplayer gaming application on AWS. The company wants the application to read data with sub-millisecond latency and run one-time queries on historical data.
Which solution will meet these requirements with the LEAST operational overhead?

  1. Use Amazon RDS for data that is frequently accessed. Run a periodic custom script to export the data to an Amazon S3 bucket.
  2. Store the data directly in an Amazon S3 bucket. Implement an S3 Lifecycle policy to move older data to S3 Glacier Deep Archive for long-term storage. Run one-time queries on the data in Amazon S3 by using Amazon Athena.
  3. Use Amazon DynamoDB with DynamoDB Accelerator (DAX) for data that is frequently accessed. Export the data to an Amazon S3 bucket by using DynamoDB table export. Run one-time queries on the data in Amazon S3 by using Amazon Athena.
  4. Use Amazon DynamoDB for data that is frequently accessed. Turn on streaming to Amazon Kinesis Data Streams. Use Amazon Kinesis Data Firehose to read the data from Kinesis Data Streams. Store the records in an Amazon S3 bucket.

Answer(s): C

Explanation:

D) Use Amazon DynamoDB for data that is frequently accessed. Turn on streaming to Amazon Kinesis Data Streams. Use Amazon Kinesis Data Firehose to read the data from Kinesis Data Streams. Store the records in an Amazon S3 bucket.
A) RDS with periodic export adds latency and operational steps; not sub-millisecond for gaming read latency.
B) S3 with Athena provides only batch/query-based access, not sub-ms latency for hot data; Glacier Deep Archive is for long-term, not hot workloads.
C) DynamoDB with DAX provides microsecond, cache-backed reads for hot data; DynamoDB export to S3 enables analytics with Athena, minimizing ops.
D) Firehose/Streams path adds complexity and may not meet sub-millisecond reads for active data.



A company uses a payment processing system that requires messages for a particular payment ID to be received in the same order that they were sent. Otherwise, the payments might be processed incorrectly.
Which actions should a solutions architect take to meet this requirement? (Choose two.)

  1. Write the messages to an Amazon DynamoDB table with the payment ID as the partition key.
  2. Write the messages to an Amazon Kinesis data stream with the payment ID as the partition key.
  3. Write the messages to an Amazon ElastiCache for Memcached cluster with the payment ID as the key.
  4. Write the messages to an Amazon Simple Queue Service (Amazon SQS) queue. Set the message attribute to use the payment I
  5. Write the messages to an Amazon Simple Queue Service (Amazon SQS) FIFO queue. Set the message group to use the payment ID.

Answer(s): B,E

Explanation:

A concise explanation: Using a Kinesis data stream with the payment ID as the partition key ensures ordered processing per partition, and an SQS FIFO queue with the payment ID as the message group ensures strict per-group ordering. Together, they guarantee that all messages for a given payment ID are delivered in order.
A) DynamoDB with payment ID as partition key does not provide inherent message ordering guarantees for stream processing.
C) ElastiCache Memcached is a cache, not a durable ordered messaging service.
D) SQS standard queue does not guarantee ordering across messages.
E) SQS FIFO queue with the payment ID as the message group ensures per-group in-order delivery.



A company is building a game system that needs to send unique events to separate leaderboard, matchmaking, and authentication services concurrently. The company needs an AWS event-driven system that guarantees the order of the events.
Which solution will meet these requirements?

  1. Amazon EventBridge event bus
  2. Amazon Simple Notification Service (Amazon SNS) FIFO topics
  3. Amazon Simple Notification Service (Amazon SNS) standard topics
  4. Amazon Simple Queue Service (Amazon SQS) FIFO queues

Answer(s): B

Explanation:

Event-driven with strict per-event ordering and separate destinations is provided by SNS FIFO topics, ensuring ordered delivery and deduplication across multiple subscribers, suitable for concurrent services (leaderboard, matchmaking, authentication) that need same-order events. A) EventBridge supports event routing but not guaranteed per-event ordering across multiple targets. C) SNS standard topics do not guarantee ordering. D) SQS FIFO queues guarantee ordering per queue but do not natively publish to multiple distinct services simultaneously from a single source without additional fan-out; SNS FIFO is designed for fan-out to multiple endpoints with ordering. Therefore B is correct.



A hospital is designing a new application that gathers symptoms from patients. The hospital has decided to use Amazon Simple Queue Service (Amazon SQS) and Amazon Simple Notification Service (Amazon SNS) in the architecture.
A solutions architect is reviewing the infrastructure design. Data must be encrypted at rest and in transit. Only authorized personnel of the hospital should be able to access the data.
Which combination of steps should the solutions architect take to meet these requirements? (Choose two.)

  1. Turn on server-side encryption on the SQS components. Update the default key policy to restrict key usage to a set of authorized principals.
  2. Turn on server-side encryption on the SNS components by using an AWS Key Management Service (AWS KMS) customer managed key. Apply a key policy to restrict key usage to a set of authorized principals.
  3. Turn on encryption on the SNS components. Update the default key policy to restrict key usage to a set of authorized principals. Set a condition in the topic policy to allow only encrypted connections over TLS.
  4. Turn on server-side encryption on the SQS components by using an AWS Key Management Service (AWS KMS) customer managed key. Apply a key policy to restrict key usage to a set of authorized principals. Set a condition in the queue policy to allow only encrypted connections over TLS.
  5. Turn on server-side encryption on the SQS components by using an AWS Key Management Service (AWS KMS) customer managed key. Apply an IAM policy to restrict key usage to a set of authorized principals. Set a condition in the queue policy to allow only encrypted connections over TLS.

Answer(s): B,D

Explanation:

Satisfying data at rest with SQS/SNS encryption using AWS KMS customer-managed keys and enforcing access with strict key policies plus transport security across SQS queues.
A) Incorrect: SQS server-side encryption exists, but requires proper KMS key policy and access controls; statement about “default key policy” is insufficient alone and ignores TLS enforcement for in-transit protection on queues.
B) Correct: SNS encryption with a KMS CMK and a restrictive key policy ensures at-rest protection and authorized access.
C) Incorrect: SNS supports encryption at rest; adding a topic policy TLS condition is not applicable to in-transit SNS-to-endpoint; TLS for client connections is not enforced via this policy construct.
D) Correct: SQS SSE with a CMK and restrictive key policy, plus a queue policy condition enforcing TLS, covers both at-rest encryption and only encrypted transit access.
E) Incorrect: IAM policy alone for key usage is not the correct mechanism; key policy (not IAM policy) governs KMS key access; TLS condition on queue policy should be used.



A company runs a web application that is backed by Amazon RDS. A new database administrator caused data loss by accidentally editing information in a database table. To help recover from this type of incident, the company wants the ability to restore the database to its state from 5 minutes before any change within the last 30 days.
Which feature should the solutions architect include in the design to meet this requirement?

  1. Read replicas
  2. Manual snapshots
  3. Automated backups
  4. Multi-AZ deployments

Answer(s): C

Explanation:

Automated backups provide point-in-time recovery for Amazon RDS, enabling restore to any second within a retention period (up to 35 days). The requirement to revert to 5 minutes before any change within the last 30 days is satisfied by automated backups with a suitable backup retention window and, if needed, transaction logs for PITR.
A) Read replicas do not support point-in-time restore of the primary; they are for offloading reads and eventual data consistency, not recovery from accidental edits.
B) Manual snapshots are static and must be created ahead of time; they do not cover continuous 30-day PITR automatically.
D) Multi-AZ improves availability and durability but not PITR restore to a specific prior moment.



Viewing page 74 of 205
Viewing questions 366 - 370 out of 1019 questions


Post your Comments and Discuss Amazon SAA-C03 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!