Identity and Access Management is where the Security and Compliance domain is at its most concrete. There is no architecture to reason about — just four building blocks and a handful of rules AWS repeats everywhere. Get the blocks straight and this is some of the most reliable scoring on the whole exam.
The four building blocks
Everything in IAM is one of four things:
- A user is a permanent identity, usually for one person. It has its own sign-in and its own credentials.
- A group bundles users so that a policy attached to the group applies to all of them. Groups are how you avoid attaching the same policy to twenty people by hand.
- A role is an identity that is assumed temporarily. A person can assume one, but more importantly so can a service — an EC2 instance or a Lambda function assumes a role to get short-lived credentials with exactly the permissions it needs.
- A policy is the JSON document that actually grants or denies permissions. You attach it to a user, a group or a role. The policy is the “what is allowed”; the others are the “who”.
If you can place any IAM term into one of those four slots, most questions answer themselves.
Roles beat stored keys — every time
The single most tested IAM idea beyond the vocabulary is this: when an application or an AWS service needs access to another service, give it a role, not an access key. A role hands out temporary credentials that rotate on their own, so there is nothing to hard-code and nothing to leak. Any option that involves pasting access keys into code, baking them into an AMI, or reusing the root user’s keys is there to be rejected. This is the exam’s favourite “secure versus convenient” fork, and secure always wins.
MFA, and the shape of a sign-in
Multi-factor authentication adds a second factor — a one-time code from a device — on top of the password. It does not replace the password and it does not grant any permissions; it simply means a stolen password alone cannot sign in. Expect at least one question that offers MFA as “encrypts your data” or “gives admin rights” to see whether you know what it actually does.
One fact worth memorising: IAM is global
IAM is a global service. A user or role exists across all Regions — you do not recreate identities Region by Region. It is a small fact, but the exam likes small facts that sound plausible when stated the wrong way, and “you must create IAM users in each Region” is a classic wrong option.
How to use the questions below
Answer each one first, then read the explanation past the correct letter to the part that says why the other three fail. IAM distractors are always real AWS ideas put in the wrong slot — a group offered where a role belongs, an access key offered where a role belongs — and separating them on sight is the whole skill the exam is testing here.
Updated for CLF-C02 (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.