AWS Trusted Advisor is the exam’s automated best-practice checker: point it at an account and it grades what it finds against AWS’s own recommendations. The SAA-C03 tests two things about it — what it covers, and what it takes to see all of that coverage. The diagram above lays out both: the five categories it reports on, and the support-tier gate beneath them.
The five categories
Trusted Advisor organizes every check into five categories, and the exam’s favorite move is to name a finding and ask which category owns it:
- Cost Optimization — idle and underutilized resources, unassociated Elastic IP addresses, other spend waste.
- Performance — over-utilized instances and configuration that holds back speed.
- Security — security groups open to the world (0.0.0.0/0) on sensitive ports, MFA missing on the root account, exposed access keys.
- Fault Tolerance — backups, Multi-AZ, resource health: can this survive a failure?
- Service Limits — how close the account is to a quota, so provisioning does not fail at the limit.
Learn the categories as a lookup table. A stem describing a wide-open security group is a Security check; one about nearing an EC2 quota is Service Limits; one about idle resources is Cost Optimization.
The support-tier gate
The second thing the exam tests is availability. Trusted Advisor’s breadth depends on your AWS Support tier. On Basic and Developer support you get only a core subset — a handful of security checks and the service-limit checks. The full set of checks across all five categories requires Business or Enterprise Support. When a scenario says a team sees only a few checks and wants the rest, the answer is an upgrade to Business or Enterprise Support — not a config change, not a quota increase.
Trusted Advisor vs AWS Config
These two get offered as each other’s distractors, and the distinction is clean. Trusted Advisor gives best-practice recommendations from a fixed AWS catalog — “this group is too open”, “this instance is idle”. AWS Config evaluates configuration compliance against rules you define — “every EBS volume must be encrypted”, “no security group may allow 0.0.0.0/0 on port 22” — and tracks compliant/non-compliant over time. Best-practice advice from AWS is Trusted Advisor; compliance against your own rules is Config.
Acting on a recommendation
One more expectation the exam checks: Trusted Advisor advises, it does not remediate. It will never close a security group or delete an idle load balancer on its own — acting on a finding is your job, done manually or through automation you build by routing its results to Amazon EventBridge and a remediation workflow. An option claiming Trusted Advisor auto-fixes or rolls back the account is wrong by definition.
How to use the seven scenarios below
Answer each one before opening the explanation, and when you miss, name what the stem was really testing — “which category owns this finding”, “what unlocks the full check set”, “recommend versus enforce”, “advise versus remediate”. Every explanation states that distinction and dismantles the distractors, which usually offer a neighbouring category or confuse Trusted Advisor with Config. For the domain overview, see Design Cost-Optimized Architectures, and for the deeper cost-cutting moves, right-sizing scenarios.
Updated for SAA-C03 (July 2026). The sample questions above are our own work
in the style of the exam — not real exam items. The exam itself is set and marked
by the certification body.