Sign in
Home/AWS/Associate (SAA-C03)/Free questions

AWS Certified Solutions Architect - Associate (SAA-C03) — Free Practice Questions

10 free sample questions from a bank of 1018, with the correct answers and explanations. No signup required — start practising right now.

1A company collects data for temperature, humidity, and atmospheric pressure in cities across multiple continents. The average volume of data that the company collects from each site daily is 500 GB. Each site has a high-speed Internet connection. The company wants to aggregate the data from all these global sites as quickly as possible in a single Amazon S3 bucket. The solution must minimize operational complexity. Which solution meets these requirements?
  • Turn on S3 Transfer Acceleration on the destination S3 bucket. Use multipart uploads to directly upload site data to the destination S3 bucket.
  • Upload the data from each site to an S3 bucket in the closest Region. Use S3 Cross-Region Replication to copy objects to the destination S3 bucket. Then remove the data from the origin S3 bucket.
  • Schedule AWS Snowball Edge Storage Optimized device jobs daily to transfer data from each site to the closest Region. Use S3 Cross-Region Replication to copy objects to the destination S3 bucket.
  • Upload the data from each site to an Amazon EC2 instance in the closest Region. Store the data in an Amazon Elastic Block Store (Amazon EBS) volume. At regular intervals, take an EBS snapshot and copy it to the Region that contains the destination S3 bucket. Restore the EBS volume in that Region.
Answer: A

The short version

A — S3 Transfer Acceleration with multipart uploads aggregates fastest. Edge-accelerated direct uploads minimize complexity versus replication or devices.

Key concepts in this question

  • Transfer Acceleration: CloudFront edge ingestion speeding long-distance S3 uploads over high-speed site links.
  • Multipart uploads: parallel part transfer for 500 GB daily site volumes with retry and throughput gains.
  • Single-bucket aggregation: all global sites writing directly to one destination without intermediate buckets.
  • Operational complexity: minimizing moving parts such as replication cleanup, Snowball scheduling, or EC2 staging.

Why A is correct

A is correct because each site already has high-speed internet, so edge-accelerated multipart PUTs exploit available bandwidth to the single bucket. Direct upload avoids managing per-region staging buckets, replication rules, and deletions. Acceleration plus parallelism therefore delivers the quickest global aggregation with least upkeep.

Why the others are wrong

  • B. Staging plus Cross-Region Replication adds bucket management and delete steps without speed benefit.
  • C. Daily Snowball Edge jobs add shipping latency and handling, unsuitable for fastest daily aggregation.
  • D. EC2 plus EBS snapshots for transfer is convoluted and far slower than direct S3 ingestion.

SAA-C03 exam tip

Use Acceleration for fast global S3 ingest: high-speed sites plus one bucket means Transfer Acceleration with multipart.

2A company needs the ability to analyze the log files of its proprietary application. The logs are stored in JSON format in an Amazon S3 bucket. Queries will be simple and will run on-demand. A solutions architect needs to perform the analysis with minimal changes to the existing architecture. What should the solutions architect do to meet these requirements with the LEAST amount of operational overhead?
  • Use Amazon Redshift to load all the content into one place and run the SQL queries as needed.
  • Use Amazon CloudWatch Logs to store the logs. Run SQL queries as needed from the Amazon CloudWatch console.
  • Use Amazon Athena directly with Amazon S3 to run the queries as needed.
  • Use AWS Glue to catalog the logs. Use a transient Apache Spark cluster on Amazon EMR to run the SQL queries as needed.
Answer: C

The short version

C — query JSON logs in place with Athena. Serverless SQL on S3 needs no loads, clusters, or moves.

Key concepts in this question

  • Athena serverless SQL: on-demand Presto and Trino queries against S3 without provisioning.
  • JSON native support: schema-on-read parsing for simple ad-hoc log analysis.
  • Minimal architecture change: leaving logs in the existing bucket while adding query capability.
  • Overhead contrast: Redshift loads, CloudWatch moves, and EMR clusters all add steps and cost.

Why C is correct

C is correct because Athena reads JSON directly from S3 and charges only per query, matching simple on-demand needs. No data movement, catalog builds, or cluster sizing is required for occasional analysis. This preserves existing storage while delivering SQL with least operational overhead.

Why the others are wrong

  • A. Redshift requires loading all content and managing a warehouse for simple queries.
  • B. CloudWatch Logs forces log migration and console querying, adding relocation overhead.
  • D. Glue plus transient EMR Spark adds cataloging and cluster orchestration for modest SQL.

SAA-C03 exam tip

Keep logs in S3 and query there: simple on-demand JSON SQL means Athena directly. Schema-on-read handles evolving log fields while pay-per-query keeps occasional analysis cost minimal.

3A company uses AWS Organizations to manage multiple AWS accounts for different departments. The management account has an Amazon S3 bucket that contains project reports. The company wants to limit access to this S3 bucket to only users of accounts within the organization in AWS Organizations. Which solution meets these requirements with the LEAST amount of operational overhead?
  • Add the aws PrincipalOrgID global condition key with a reference to the organization ID to the S3 bucket policy.
  • Create an organizational unit (OU) for each department. Add the aws:PrincipalOrgPaths global condition key to the S3 bucket policy.
  • Use AWS CloudTrail to monitor the CreateAccount, InviteAccountToOrganization, LeaveOrganization, and RemoveAccountFromOrganization events. Update the S3 bucket policy accordingly.
  • Tag each user that needs access to the S3 bucket. Add the aws:PrincipalTag global condition key to the S3 bucket policy.
Answer: A

The short version

A — limit the bucket with aws PrincipalOrgID to the organization ID. One bucket-policy condition confines access to member accounts.

Key concepts in this question

  • PrincipalOrgID condition: global key matching the AWS Organizations ID of the caller principal.
  • Management-account bucket: central S3 store for project reports needing org-only isolation.
  • Least overhead goal: single policy statement versus per-account lists or event-driven updates.
  • Paths versus tags: finer OrgPaths and PrincipalTag controls that add complexity beyond the requirement.

Why A is correct

A is correct because adding aws PrincipalOrgID with the organization ID to the bucket policy automatically allows only principals from that org. New and removed accounts inherit correct access without policy edits, unlike CloudTrail-driven rewrites. It is the simplest condition covering all departments in the organization.

Why the others are wrong

  • B. OrgPaths per OU adds unnecessary hierarchy management when whole-org access suffices.
  • C. CloudTrail monitoring plus manual policy updates creates ongoing operational burden.
  • D. Tagging every user and checking PrincipalTag adds tagging governance for no extra benefit.

SAA-C03 exam tip

Restrict to the org with one key: PrincipalOrgID plus org ID is the least-effort S3 org guard.

4An application runs on an Amazon EC2 instance in a VPC. The application processes logs that are stored in an Amazon S3 bucket. The EC2 instance needs to access the S3 bucket without connectivity to the internet. Which solution will provide private network connectivity to Amazon S3?
  • Create a gateway VPC endpoint to the S3 bucket.
  • Stream the logs to Amazon CloudWatch Logs. Export the logs to the S3 bucket.
  • Create an instance profile on Amazon EC2 to allow S3 access.
  • Create an Amazon API Gateway API with a private link to access the S3 endpoint.
Answer: A

The short version

A — create a gateway VPC endpoint for S3. It adds private S3 routing without internet, NAT, or proxies.

Key concepts in this question

  • Gateway endpoint: VPC route-table target for S3 and DynamoDB traffic staying on the AWS backbone.
  • No-internet constraint: EC2 in a VPC needing S3 without public egress or gateways.
  • Instance profile distinction: IAM permissions authorize access but do not provide network path.
  • PrivateLink versus gateway: interface endpoints suit most services, while S3 offers a free gateway route.

Why A is correct

A is correct because a gateway VPC endpoint inserts a prefix-list route letting the EC2 subnet reach S3 privately. It requires no internet gateway, NAT, or API Gateway plumbing and incurs no hourly charge. Combined with an instance role for authorization, it satisfies private connectivity cleanly.

Why the others are wrong

  • B. Streaming to CloudWatch then exporting to S3 adds services without creating private S3 network path.
  • C. Instance profile grants permission but supplies no private route to S3.
  • D. API Gateway private link fronts APIs and does not provide S3 bucket routing.

SAA-C03 exam tip

Reach S3 privately via gateway: VPC endpoint route plus IAM role covers network plus auth.

5A company is hosting a web application on AWS using a single Amazon EC2 instance that stores user-uploaded documents in an Amazon EBS volume. For better scalability and availability, the company duplicated the architecture and created a second EC2 instance and EBS volume in another Availability Zone, placing both behind an Application Load Balancer. After completing this change, users reported that, each time they refreshed the website, they could see one subset of their documents or the other, but never all of the documents at the same time. What should a solutions architect propose to ensure users see all of their documents at once?
  • Copy the data so both EBS volumes contain all the documents
  • Configure the Application Load Balancer to direct a user to the server with the documents
  • Copy the data from both EBS volumes to Amazon EFS. Modify the application to save new documents to Amazon EFS
  • Configure the Application Load Balancer to send the request to both servers. Return each document from the correct server
Answer: C

The short version

C — consolidate documents on EFS and point the app there. Shared file system lets both AZ instances see every upload at once.

Key concepts in this question

  • EBS zonal isolation: volumes attach to one instance in one AZ, so duplicated stacks split document sets.
  • ALB symptom: alternating subsets on refresh proving sticky state is stored locally per server.
  • EFS shared access: regional NFS mountable from multiple AZ instances simultaneously.
  • Scalability plus availability: shared storage behind a load balancer serving consistent content from any node.

Why C is correct

C is correct because copying both EBS datasets to EFS creates one authoritative document set visible to all instances. Modifying the app to save new uploads to EFS keeps future writes shared rather than re-splitting state. Behind the ALB, either EC2 can now serve the full collection, fixing the refresh-split symptom.

Why the others are wrong

  • A. Copying data to both EBS volumes duplicates state and re-diverges on every new upload.
  • B. Sticky routing to one server masks inconsistency while sacrificing availability and scaling.
  • D. Fanning requests to both servers and merging responses adds custom aggregation complexity.

SAA-C03 exam tip

Split views behind a balancer mean local disks: move state to EFS for shared consistent serving.

6A company uses NFS to store large video files in on-premises network attached storage. Each video file ranges in size from 1 MB to 500 GB. The total storage is 70 TB and is no longer growing. The company decides to migrate the video files to Amazon S3. The company must migrate the video files as soon as possible while using the least possible network bandwidth. Which solution will meet these requirements?
  • Create an S3 bucket. Create an IAM role that has permissions to write to the S3 bucket. Use the AWS CLI to copy all files locally to the S3 bucket.
  • Create an AWS Snowball Edge job. Receive a Snowball Edge device on premises. Use the Snowball Edge client to transfer data to the device. Return the device so that AWS can import the data into Amazon S3.
  • Deploy an S3 File Gateway on premises. Create a public service endpoint to connect to the S3 File Gateway. Create an S3 bucket. Create a new NFS file share on the S3 File Gateway. Point the new file share to the S3 bucket. Transfer the data from the existing NFS file share to the S3 File Gateway.
  • Set up an AWS Direct Connect connection between the on-premises network and AWS. Deploy an S3 File Gateway on premises. Create a public virtual interface (VIF) to connect to the S3 File Gateway. Create an S3 bucket. Create a new NFS file share on the S3 File Gateway. Point the new file share to the S3 bucket. Transfer the data from the existing NFS file share to the S3 File Gateway.
Answer: B

The short version

B — use Snowball Edge for 70 TB of static video to S3. Offline transfer minimizes bandwidth and time versus network copies.

Key concepts in this question

  • 70 TB fixed corpus: large non-growing NFS dataset where network upload would saturate links.
  • Snowball Edge workflow: AWS ships a device, local client copies at LAN speed, AWS ingests to S3.
  • Least bandwidth mandate: avoiding 70 TB over the internet or Direct Connect provisioning.
  • Soonest migration: parallel local copy plus AWS backbone ingest beating throttled CLI sync.

Why B is correct

B is correct because Snowball Edge moves tens of terabytes locally without consuming WAN bandwidth for the bulk payload. Returning the device lets AWS load directly into S3 at datacenter speed, handling 1 MB to 500 GB objects reliably. Gateway or CLI paths would stream all bytes over constrained networks and take far longer.

Why the others are wrong

  • A. CLI copy pushes 70 TB over the internet, maximizing bandwidth and duration.
  • C. File Gateway still sends all bytes over the public endpoint, using full network bandwidth.
  • D. Direct Connect plus gateway adds costly circuit setup while still transferring all data by network.

SAA-C03 exam tip

Move huge static bulk offline: 70 TB non-growing to S3 means Snowball Edge, not network copy.

7A company has an application that ingests incoming messages. Dozens of other applications and microservices then quickly consume these messages. The number of messages varies drastically and sometimes increases suddenly to 100,000 each second. The company wants to decouple the solution and increase scalability. Which solution meets these requirements?
  • Persist the messages to Amazon Kinesis Data Analytics. Configure the consumer applications to read and process the messages.
  • Deploy the ingestion application on Amazon EC2 instances in an Auto Scaling group to scale the number of EC2 instances based on CPU metrics.
  • Write the messages to Amazon Kinesis Data Streams with a single shard. Use an AWS Lambda function to preprocess messages and store them in Amazon DynamoDB. Configure the consumer applications to read from DynamoDB to process the messages.
  • Publish the messages to an Amazon Simple Notification Service (Amazon SNS) topic with multiple Amazon Simple Queue Service (Amazon SOS) subscriptions. Configure the consumer applications to process the messages from the queues.
Answer: D

The short version

D — fan out through SNS to multiple SQS queues. Pub-sub decouples ingestion from dozens of consumers and absorbs 100K bursts.

Key concepts in this question

  • Decoupling need: isolating fast ingestion from variable consumer processing rates.
  • SNS topic fan-out: one publish replicated to many subscribed SQS queues for parallel consumers.
  • Burst scalability: SQS buffering 100K messages per second without provisioning shards or instances.
  • Kinesis and EC2 limits: single-shard streams and CPU-based scaling that bottleneck sudden spikes.

Why D is correct

D is correct because SNS accepts the ingest burst once and fans each message to dedicated SQS queues per application family. Each microservice then drains its own queue at its own pace, preserving decoupling and independent scaling. Managed queues absorb sudden 100K-per-second spikes without shard or fleet tuning.

Why the others are wrong

  • A. Kinesis Data Analytics analyzes streams and does not provide multi-consumer queue buffering.
  • B. EC2 Auto Scaling on CPU reacts slowly and couples ingestion to compute capacity.
  • C. Single-shard Kinesis caps throughput and DynamoDB polling adds coupling and hot-partition risk.

SAA-C03 exam tip

Decouple many consumers at burst scale: SNS topic plus SQS subscriptions buffers and fans out cleanly.

8A company is migrating a distributed application to AWS. The application serves variable workloads. The legacy platform consists of a primary server that coordinates jobs across multiple compute nodes. The company wants to modernize the application with a solution that maximizes resiliency and scalability. How should a solutions architect design the architecture to meet these requirements?
  • Configure an Amazon Simple Queue Service (Amazon SQS) queue as a destination for the jobs. Implement the compute nodes with Amazon EC2 instances that are managed in an Auto Scaling group. Configure EC2 Auto Scaling to use scheduled scaling.
  • Configure an Amazon Simple Queue Service (Amazon SQS) queue as a destination for the jobs. Implement the compute nodes with Amazon EC2 instances that are managed in an Auto Scaling group. Configure EC2 Auto Scaling based on the size of the queue.
  • Implement the primary server and the compute nodes with Amazon EC2 instances that are managed in an Auto Scaling group. Configure AWS CloudTrail as a destination for the jobs. Configure EC2 Auto Scaling based on the load on the primary server.
  • Implement the primary server and the compute nodes with Amazon EC2 instances that are managed in an Auto Scaling group. Configure Amazon EventBridge (Amazon CloudWatch Events) as a destination for the jobs. Configure EC2 Auto Scaling based on the load on the compute nodes.
Answer: B

The short version

B — queue jobs in SQS and scale EC2 on queue depth. Backlog-driven scaling maximizes resiliency for variable coordinator workloads.

Key concepts in this question

  • Primary-plus-compute legacy: single coordinator bottleneck replaced by durable queue dispatch.
  • SQS durability: managed backlog absorbing variable job arrivals without losing work.
  • Queue-depth scaling: Auto Scaling policy growing compute nodes as visible messages accumulate.
  • Scheduled versus dynamic: fixed schedules miss spikes, while backlog metrics track real demand.

Why B is correct

B is correct because placing jobs in SQS removes the primary server as a single point of failure and buffers variable load. Configuring EC2 Auto Scaling on queue size adds nodes when backlog grows and shrinks them when drained, matching capacity to demand. This combination delivers resiliency through durability plus scalability through demand-driven compute.

Why the others are wrong

  • A. Scheduled scaling cannot react to unpredictable variable workloads despite using a queue.
  • C. Keeping the primary on EC2 preserves the bottleneck, and CloudTrail is audit, not job dispatch.
  • D. EventBridge routing plus primary-based nodes retains coordination fragility and misuses event bus.

SAA-C03 exam tip

Modernize coordinators with queues: SQS for jobs plus Auto Scaling on queue depth handles variable load.

9A company is running an SMB file server in its data center. The file server stores large files that are accessed frequently for the first few days after the files are created. After 7 days the files are rarely accessed. The total data size is increasing and is close to the company's total storage capacity. A solutions architect must increase the company's available storage space without losing low-latency access to the most recently accessed files. The solutions architect must also provide file lifecycle management to avoid future storage issues. Which solution will meet these requirements?
  • Use AWS DataSync to copy data that is older than 7 days from the SMB file server to AWS.
  • Create an Amazon S3 File Gateway to extend the company's storage space. Create an S3 Lifecycle policy to transition the data to S3 Glacier Deep Archive after 7 days.
  • Create an Amazon FSx for Windows File Server file system to extend the company's storage space.
  • Install a utility on each user's computer to access Amazon S3. Create an S3 Lifecycle policy to transition the data to S3 Glacier Flexible Retrieval after 7 days.
Answer: B

The short version

B — extend with S3 File Gateway and tier after 7 days. Cached gateway keeps hot files fast while lifecycle offloads cold data.

Key concepts in this question

  • SMB hot window: frequent access for first days, rare after 7 days, demanding tiered latency.
  • S3 File Gateway: on-premises SMB presentation caching hot data locally while backing to S3.
  • S3 Lifecycle policy: timed transition to Glacier Deep Archive for cold objects after 7 days.
  • Capacity relief: offloading growth to S3 without losing low-latency recent-file access.

Why B is correct

B is correct because File Gateway stores the working set locally for low-latency SMB while S3 holds the full corpus. A lifecycle rule transitioning objects older than 7 days to Deep Archive automates cost control as data grows. This satisfies space expansion, hot performance, and future lifecycle management together.

Why the others are wrong

  • A. DataSync copying old data to AWS lacks gateway caching and automated archival tiering.
  • C. FSx for Windows adds managed file storage without 7-day archival lifecycle control.
  • D. Per-user S3 utilities break SMB semantics and push Glacier transitions to clients.

SAA-C03 exam tip

Cache hot plus archive cold: SMB with 7-day warmth means File Gateway plus lifecycle to Deep Archive.

10A company is building an ecommerce web application on AWS. The application sends information about new orders to an Amazon API Gateway REST API to process. The company wants to ensure that orders are processed in the order that they are received. Which solution will meet these requirements?
  • Use an API Gateway integration to publish a message to an Amazon Simple Notification Service (Amazon SNS) topic when the application receives an order. Subscribe an AWS Lambda function to the topic to perform processing.
  • Use an API Gateway integration to send a message to an Amazon Simple Queue Service (Amazon SQS) FIFO queue when the application receives an order. Configure the SQS FIFO queue to invoke an AWS Lambda function for processing.
  • Use an API Gateway authorizer to block any requests while the application processes an order.
  • Use an API Gateway integration to send a message to an Amazon Simple Queue Service (Amazon SQS) standard queue when the application receives an order. Configure the SQS standard queue to invoke an AWS Lambda function for processing.
Answer: B

The short version

B — send API Gateway orders to SQS FIFO then Lambda. FIFO ordering preserves receive sequence for downstream processing.

Key concepts in this question

  • Order guarantee: ecommerce requirement that orders process in arrival sequence.
  • SQS FIFO queue: exactly-once-ish ordered queue with message groups and deduplication for sequencing.
  • API Gateway integration: direct service proxy pushing order payloads to the queue on receipt.
  • SNS versus standard queue: topic fan-out and standard queues provide at-least-once without strict ordering.

Why B is correct

B is correct because SQS FIFO retains the order messages are received and invokes Lambda in that sequence for processing. API Gateway integration enqueues each order immediately, preserving arrival order end to end. SNS topics and standard queues cannot guarantee global ordering, and authorizer blocking does not sequence work.

Why the others are wrong

  • A. SNS topic to Lambda fans out without FIFO ordering guarantees.
  • C. Authorizer blocking serializes crudely and blocks throughput instead of queuing ordered work.
  • D. Standard SQS offers scale but only best-effort ordering, violating sequence needs.

SAA-C03 exam tip

Need order plus API intake: API Gateway to SQS FIFO to Lambda preserves receive sequence.

Want the full bank of 1018 questions for AWS Certified Solutions Architect - Associate (SAA-C03)? See all practice exams.