SOA-C03 Compute, Storage and Database Performance Optimization Guide

This lesson covers SOA-C03 Task 1.3: implementing performance optimization strategies for compute, storage, and database resources. AWS is testing diagnostic discipline here. Strong answers do not start with “choose a bigger instance.” They start by locating the constrained layer, selecting the most targeted evidence for that layer, and applying the smallest effective optimization.

Constrained layer: The part of the system that is currently limiting end-to-end performance, such as compute, block storage, shared storage, object transfer, or database load.

Queue depth: Number of outstanding I/O requests waiting for processing, often a useful sign of storage contention.

Multipart upload: S3 upload method that breaks a large object into smaller independent parts for resiliency and throughput handling.

What AWS is really testing here

AWS wants you to separate:

• compute bottlenecks from storage bottlenecks
• local storage performance from transfer-path problems
• database load issues from application-tier guesses
• performance fixes from wasteful overprovisioning
• sustained constraints from short-lived spikes

Start with the constrained layer

Compute optimization choices

When the problem is mainly compute, the exam expects you to think in terms of:

• instance family fit
• horizontal scaling behavior
• placement groups when low-latency networking matters
• autoscaling signals that reflect real workload stress
• avoiding blind overprovisioning when the real issue is somewhere else

Common compute trap

If CPU is not the main constraint, a larger instance can hide the real issue temporarily while leaving storage or database bottlenecks in place.

Storage optimization choices

EBS

Use EBS-focused reasoning when the stem mentions:

• queue depth
• volume latency
• throughput limits
• IOPS limits
• volume-type mismatch

If the workload is clearly block-storage bound, the first move belongs in the EBS lane, not in Route 53, IAM, or a generic instance resize.

S3

Use S3-focused reasoning when the stem mentions:

• large-object upload reliability
• long-distance transfer performance
• repeated retries on uploads
• transfer-path optimization

Multipart upload and Transfer Acceleration solve different problems:

• multipart upload improves resiliency and handling of large uploads
• Transfer Acceleration helps long-distance or internet-path transfers into S3

EFS and FSx

When the requirement is shared storage semantics, the exam often wants you to decide:

• whether a managed shared file system is the right fit
• whether throughput or lifecycle behavior needs tuning
• whether the workload really needs shared storage instead of object storage or block storage

Database optimization choices

If the question is really about the database tier, move quickly into database evidence:

• RDS metrics
• Performance Insights
• connection pressure
• query load behavior
• read scaling or proxy choices

Common database trap

If the database is already the choke point, adding more application instances can increase load on the wrong tier and make the system slower overall.

Performance troubleshooting order that usually wins

1. Identify whether the main symptom is compute, block storage, shared storage, database, or transfer path.
2. Use the nearest service-specific metrics first.
3. Confirm whether the problem is steady-state or bursty.
4. Apply the smallest resource or configuration change that matches the evidence.
5. Re-check the same metrics after the change to prove the bottleneck moved or disappeared.

High-confusion pairs

Sample exam question

A workload running on Amazon EC2 shows acceptable CPU and memory headroom, but during peak periods the attached EBS volume shows high queue depth and increased latency. Users report slower response times, and the operations team wants the most targeted next step.

Which answer is strongest?

1. Increase the number of Route 53 health checks
2. Review the EBS volume type and provisioned storage performance characteristics
3. Rotate all IAM access keys used by the workload
4. Replace CloudTrail with CloudWatch Logs

Correct answer: 2

Why: The evidence points to the block-storage path, not to DNS, identity, or audit telemetry. SOA-C03 rewards targeted diagnosis, so the storage design is the strongest first review.

Common traps

Quiz