SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
SAA-C03 · Domain 3

Design High-Performing Architectures practice questions

Design High-Performing Architectures is worth 24% of the SAA-C03 exam — the 3rd-heaviest of the 4 domains. Matching storage, compute, database, network, and data-pipeline services to performance and scale requirements. 6 fully worked examples are further down this page, answers included.

Exam weight
24%
the 3rd-heaviest of the 4 domains
Questions
135
across 5 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 4 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Design High-Performing Architectures questions, fully explained

Questions from the SAA-C03 bank mapped to domain 3, with the answer key and the reasoning behind every option. None of them repeat the examples on the main SAA-C03 practice page.

Question 1Design High-Performing Architectures

A data engineering team runs a nightly job on EC2 that reads multi-terabyte log files from start to finish on an attached EBS volume, computes aggregates, and writes a small summary. The job performs almost no random I/O, but it must finish inside its nightly window, so the volume has to stream data quickly every night. Which volume type meets the requirement MOST cost-effectively?

Choose one.

  • a
    General Purpose SSD (gp3) with throughput raised above baseline

    gp3 would meet the throughput need but charges SSD prices for IOPS capability this sequential workload never uses.

  • b
    Provisioned IOPS SSD (io2) sized for the data set

    io2 is the most expensive option and sells sustained random IOPS — the one thing this workload does not need.

  • c
    Throughput Optimized HDD (st1) sized for the data set Correct

    st1 is built exactly for cheap, high sequential throughput on big-data and log-processing workloads, at a much lower price per gigabyte than SSD.

  • d
    Cold HDD (sc1) sized for the data set

    sc1 is cheaper still, but it is designed for infrequently accessed data and offers lower throughput; a nightly high-throughput scan is a regular, performance-sensitive access pattern.

The concept

HDD volumes sell throughput and SSD volumes sell IOPS; for large sequential scans, st1 delivers the required throughput at HDD prices.

Why that’s the answer

The access pattern is large and sequential with almost no random I/O, which is what st1 is built for: high sequential throughput at HDD prices. gp3 and io2 would both work, but they charge SSD prices for random-I/O capability the job never uses, which the cost qualifier punishes. sc1 is the trap in the other direction: it is cheaper per gigabyte but is designed for cold, rarely read data and delivers lower throughput, so a nightly job with a deadline can miss its window.

How to reason it out
  1. Identify the access pattern: large sequential reads, minimal random I/O.
  2. Map pattern to media: sequential throughput favors HDD volumes over SSD on price.
  3. Check the access frequency: nightly, throughput-sensitive scans are regular work, ruling out cold-tier sc1.
  4. Confirm st1 meets the throughput requirement at lower cost than gp3 or io2.

Exam tip: Sequential big-data scans resolve to st1 — SSDs overpay for unused IOPS, and sc1 undershoots on regularly accessed data.

High-Performing Storage: S3 vs EBS vs EFS, Volume Types, and Hybrid Options — the lesson that teaches this.

Question 2Design High-Performing Architectures

A company keeps several large EBS volumes of historical project data attached to a records-management EC2 instance. Auditors access the data only a few times per year, and retrieval speed is not a concern. The data must remain available as mounted volumes. Which volume type minimizes storage cost?

Choose one.

  • a
    Modify the volumes to Throughput Optimized HDD (st1)

    st1 is cheaper than SSD but costs more per gigabyte than sc1, and its higher throughput is wasted on data read a few times a year.

  • b
    Keep the volumes on gp3 and lower IOPS to the 3,000 baseline

    Removing provisioned IOPS trims the performance charge, but gp3 storage still costs SSD prices per gigabyte, well above HDD volume types.

  • c
    Modify the volumes to Cold HDD (sc1) with Elastic Volumes Correct

    sc1 has the lowest cost per gigabyte of any EBS volume type and is designed for infrequently accessed data; Elastic Volumes changes the type in place, so the data stays mounted.

  • d
    Archive snapshots of the volumes, then delete the volumes

    EBS Snapshots Archive is cheap long-term storage, but the data would no longer be mounted, which breaks the stated requirement; restores also take hours.

The concept

sc1 is the bottom of the EBS cost ladder: lowest price per gigabyte, lowest performance, intended for cold, infrequently accessed volume data.

Why that’s the answer

The requirement is cost, with two constraints: the data must stay on mounted volumes and access is rare with speed not a concern. sc1 is the cheapest EBS volume type per gigabyte and is designed for exactly this pattern, and Elastic Volumes can change the volume type in place. st1 is the near-miss (also HDD, but pricier and faster than needed). Lowering gp3 to its baseline only removes the performance surcharge; the SSD storage price remains. Archiving snapshots is cheaper still but breaks the mounted-volume requirement.

How to reason it out
  1. Note the constraint: data must remain available as mounted EBS volumes, which rules out snapshot archiving.
  2. Note the access pattern: a few reads per year, no performance requirement.
  3. Rank EBS types by price per gigabyte: sc1 is the lowest, below st1 and every SSD type.
  4. Confirm sc1's lower performance is acceptable because speed is explicitly not required.

Exam tip: When EBS data is cold and cost is the only requirement, sc1 is the answer — st1 is the overpriced near-miss.

High-Performing Storage: S3 vs EBS vs EFS, Volume Types, and Hybrid Options — the lesson that teaches this.

Question 3Design High-Performing Architectures

A trading application on EC2 issues a continuous stream of small, random reads and writes against its data volume. To reduce storage spend, an engineer proposes replacing the current SSD volume with a Throughput Optimized HDD (st1) volume, noting its lower price per gigabyte. Which volume type should a solutions architect recommend to meet the performance need MOST cost-effectively?

Choose one.

  • a
    Throughput Optimized HDD (st1)

    st1 is cheaper on paper but performs poorly on small random I/O — it sells sequential throughput, so the application would suffer despite the savings.

  • b
    Cold HDD (sc1)

    sc1 is the lowest-performing EBS type, designed for infrequently accessed data; it fails a continuous random-I/O workload even more severely than st1.

  • c
    Provisioned IOPS SSD (io2)

    io2 would perform well but is the most expensive type, and nothing in the scenario states a requirement beyond what gp3 can provision.

  • d
    General Purpose SSD (gp3) Correct

    Small random I/O requires SSD; gp3 serves it at the lowest SSD cost, making it the cheapest option that actually meets the performance need.

The concept

The SSD-versus-HDD split is decided by access pattern, not price: SSD volumes serve small random I/O, HDD volumes serve large sequential throughput.

Why that’s the answer

The workload is continuous small random reads and writes — transactional shape — so the HDD proposal fails on physics before it saves a cent: st1 and sc1 are sequential-throughput devices that degrade badly under random I/O, so the cheaper volume would not meet the performance need at all. Among SSDs, the qualifier decides: gp3 handles the workload at balanced cost, and the scenario states no sustained-extreme-IOPS or latency-consistency requirement that would justify io2's premium. gp3 is therefore the cheapest option that still meets the requirement, which is what MOST cost-effectively means.

How to reason it out
  1. Read the access pattern: continuous small random reads and writes.
  2. Apply the media rule: random I/O requires SSD, eliminating st1 and sc1 regardless of price.
  3. Check for io2 justification: no stated demand beyond gp3's envelope, so io2 is an overshoot.
  4. Select gp3 as the lowest-cost volume that meets the performance requirement.

Exam tip: Cost-effective never means the cheapest volume — it means the cheapest volume whose media matches the access pattern.

High-Performing Storage: S3 vs EBS vs EFS, Volume Types, and Hybrid Options — the lesson that teaches this.

Question 4Design High-Performing Architectures

A database running on a gp3 EBS volume is hitting its provisioned IOPS limit during peak hours, causing query latency. The volume is only 40 percent full, and the team does not expect the dataset to grow significantly. What is the MOST cost-effective way to resolve the bottleneck?

Choose one.

  • a
    Grow the gp3 volume so that its larger size brings more IOPS

    Tying IOPS to size is the gp2 model; gp3 IOPS are provisioned directly, so a larger volume only adds capacity the team does not need.

  • b
    Change the volume type to io2 and provision the peak IOPS

    io2 would remove the bottleneck, but it costs more and nothing indicates the requirement is beyond what gp3 can be provisioned to.

  • c
    Raise the gp3 volume's provisioned IOPS and keep its size Correct

    gp3 decouples performance from capacity, so IOPS can be raised in place with Elastic Volumes and only the extra IOPS are billed.

  • d
    Stripe the data across two more gp3 volumes in RAID 0

    Striping adds IOPS but also adds volumes to manage and failure points, for a problem a single setting change solves.

The concept

gp3's defining feature is that IOPS and throughput are provisioned independently of volume size — performance is a dial, not a side effect of capacity.

Why that’s the answer

The volume is well under capacity, so the team needs more IOPS without more storage — the exact case gp3's decoupling exists for. Raising provisioned IOPS on the existing volume adds only the incremental performance cost. Growing the volume is the gp2-era reflex: it buys 60 percent more unneeded space and is not how gp3 scales performance. io2 works but is the overpriced rung of the ladder when gp3 can still reach the required number. RAID 0 striping also works but multiplies volumes to manage, doubles the blast radius of a single volume failure, and replaces a one-line configuration change with an infrastructure project — losing on both cost and overhead.

How to reason it out
  1. Identify the constraint: IOPS ceiling reached while capacity is barely used.
  2. Recall gp3's model: IOPS and throughput are provisioned independently of size.
  3. Eliminate size increases (buys capacity, not the performance mechanism) and io2 (higher cost tier not justified).
  4. Eliminate RAID 0 as added complexity for a problem a setting solves.
  5. Raise provisioned IOPS on the existing gp3 volume.

Exam tip: Needs more IOPS but not more storage resolves to adjusting gp3's provisioned performance, never to a bigger disk.

High-Performing Storage: S3 vs EBS vs EFS, Volume Types, and Hybrid Options — the lesson that teaches this.

Question 5Design High-Performing Architectures

A video-rendering pipeline on EC2 reads source footage from Amazon S3, writes large volumes of intermediate scratch data to local storage during processing, and uploads the finished output back to S3. The intermediate data is regenerated automatically if a job restarts. Which storage choice for the scratch data is MOST performant?

Choose one.

  • a
    An io2 Block Express EBS volume provisioned at maximum IOPS

    io2 is very fast and durable, but it is still network-attached; local NVMe outperforms it, and scratch data does not need its durability.

  • b
    A gp3 EBS volume with IOPS and throughput raised to the maximum

    gp3 is network-attached general-purpose storage; even at its maximums it is slower than local NVMe and pays for durability scratch data does not need.

  • c
    An Amazon EFS file system using Elastic throughput mode

    EFS adds network file-system latency and is built for shared access across instances, not private maximum-speed scratch space.

  • d
    Local NVMe instance store on a storage-optimized instance Correct

    Instance store is physically attached to the host with no network hop, giving the highest IOPS and lowest latency EC2 offers; the scratch data is regenerable, so ephemerality costs nothing.

The concept

Instance store is the fastest storage an EC2 instance can touch because it is physically attached to the host; its ephemerality is acceptable only when the data is replaceable — which scratch data is by definition.

Why that’s the answer

The qualifier is MOST performant and the data is explicitly regenerable, which removes instance store's only weakness. Physical attachment beats every network-attached option, so instance store outruns io2 and gp3 alike; the durable copies live in S3 at both ends of the pipeline, so losing a node's scratch data merely restarts a job. io2 is the tempting distractor — very fast, very durable — but it pays a premium for durability the scratch data does not need and still crosses the network on every operation. gp3 is slower again, and EFS is the worst fit: shared NFS semantics and network latency for data no other instance ever reads.

How to reason it out
  1. Check whether the data must survive the instance: it is regenerated on restart, so no.
  2. With durability off the table, rank raw speed: physically attached NVMe instance store beats all network-attached EBS options.
  3. Eliminate io2 and gp3 as slower and paying for durability the workload does not need.
  4. Eliminate EFS as shared file storage with network latency for single-instance scratch.
  5. Confirm the durable system of record is S3, keeping the architecture safe.

Exam tip: For replaceable scratch data under a MOST performant qualifier, instance store beats every EBS type — including io2.

High-Performing Storage: S3 vs EBS vs EFS, Volume Types, and Hybrid Options — the lesson that teaches this.

Question 6Design High-Performing Architectures

A company runs a self-managed distributed NoSQL database on EC2. Each node stores a partition of the data, and the database replicates every partition across three nodes in different Availability Zones. The team needs the highest possible storage I/O performance per node while keeping the overall dataset recoverable from a complete cluster failure. Which combination of steps should a solutions architect take? (Select TWO.)

Choose TWO.

  • a
    Attach one io2 volume with Multi-Attach enabled to the cluster nodes

    Multi-Attach works only within one Availability Zone and needs a cluster-aware file system; it is also slower than local NVMe and contradicts the per-node partition design.

  • b
    Run the nodes on storage-optimized instances using local NVMe instance store Correct

    Storage-optimized families ship large, fast local NVMe for I/O-hungry distributed databases; physical attachment gives the highest per-node I/O, and cross-AZ replication covers a lost node.

  • c
    Mount an Amazon EFS file system as each node's database directory

    EFS adds network file-system latency that database storage engines are not designed for, so it cannot deliver the highest per-node I/O.

  • d
    Run the nodes on general purpose instances with io2 Block Express volumes

    io2 Block Express is durable and fast, but it is network-attached, so it cannot match local NVMe for the highest possible per-node I/O.

  • e
    Back up the database files to Amazon S3 on a schedule Correct

    Instance store is ephemeral and replication dies with the cluster, so a durable S3 backup layer is what survives a complete cluster failure.

The concept

Instance store is correct when data is replicated or replaceable, and well-designed architectures pair its speed with a durable layer — cluster replication rebuilds a lost node, while S3 backups survive a whole-cluster loss.

Why that’s the answer

The database already replicates each partition across three AZs, so losing one node's ephemeral disk costs nothing: peers rebuild it. That makes local NVMe instance store on storage-optimized instances the maximum-I/O choice, faster than any network-attached volume including io2 Block Express. But the requirement also names recovery from a complete cluster failure, which replication cannot survive; scheduled backups to S3 provide that durable layer. io2 Block Express is the tempting durable alternative but loses on raw speed. Multi-Attach is single-AZ and needs a cluster-aware file system. EFS adds NFS latency.

How to reason it out
  1. Confirm per-node data is replaceable: three-way cross-AZ replication rebuilds any lost node.
  2. Choose maximum per-node I/O: storage-optimized instances with local NVMe instance store beat any network-attached volume.
  3. Address the whole-cluster failure case: replication dies with the cluster, so back up to S3.
  4. Eliminate io2 (durable but slower), Multi-Attach (single-AZ, cluster file system) and EFS (file latency).

Exam tip: Pair instance store's unmatched speed with a durable layer: replication covers node loss, S3 backups cover cluster loss.

High-Performing Storage: S3 vs EBS vs EFS, Volume Types, and Hybrid Options — the lesson that teaches this.

What SAA-C03 domain 3 tests, topic by topic

The official exam guide breaks Design High-Performing Architectures into 5 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published SAA-C03 practice questions per topic in Design High-Performing Architectures
TopicWhat it coversQuestions
Determine high-performing and/or scalable storage solutionsExam guide task 3.1. Matching object, file, and block storage (S3, EFS, EBS) and their characteristics to performance demands; hybrid storage solutions; selecting configurations that meet requirements now and scale for future needs.27
Design high-performing and elastic compute solutionsExam guide task 3.2. Compute services with appropriate use cases (EC2 instance types, AWS Batch, EMR, Fargate); serverless patterns (Lambda, Fargate) and container orchestration (ECS, EKS); EC2 Auto Scaling and AWS Auto Scaling — the metrics and conditions that trigger scaling actions; decoupling workloads so components scale independently; resource sizing (e.g. Lambda memory).27
Determine high-performing database solutionsExam guide task 3.3. Relational vs non-relational vs serverless vs in-memory databases (Aurora, DynamoDB, ElastiCache) and engine selection (e.g. MySQL vs PostgreSQL); caching strategies, read replicas, and database proxies/connections; capacity planning (capacity units, instance types, Provisioned IOPS) for read-intensive vs write-intensive access patterns.27
Determine high-performing and/or scalable network architecturesExam guide task 3.4. Edge networking (CloudFront, Global Accelerator); selecting a load-balancing strategy; network design — subnet tiers, routing, IP addressing; topologies for global, hybrid, and multi-tier architectures; connection options (AWS VPN, Direct Connect, PrivateLink) and resource placement for performance.27
Determine high-performing data ingestion and transformation solutionsExam guide task 3.5. Streaming and ingestion (Kinesis), data transfer (DataSync, Storage Gateway, Transfer Family), transformation (AWS Glue, e.g. CSV to Parquet), building and securing data lakes (Lake Formation, S3), analytics and visualization (Athena, Lake Formation, Amazon Quick), and compute for data processing (EMR).27
Total135

Revise Design High-Performing Architectures before you drill it

Other SAA-C03 domains

Design High-Performing Architectures: your questions

Design High-Performing Architectures is domain 3 of the SAA-C03 exam guide and carries 24% of the scored content — the 3rd-heaviest of the 4 domains. On a 65-question paper that works out to roughly 16 questions, though AWS does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official SAA-C03 exam guide.