mediummultiple choiceObjective-mapped

Exhibit

AWS Organizations policy summary:

Root OU: Full access
Production OU: SCP attached

SCP content:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Action": ["ec2:CreateSnapshot", "ec2:DeleteSnapshot"],
      "Resource": "*"
    }
  ]
}

CloudTrail event:
- userIdentity: arn:aws:iam::444455556666:role/OpsAdmin
- eventName: CreateSnapshot
- errorCode: AccessDenied
- errorMessage: action denied by organizations service control policy

Based on the exhibit, why is the IAM role still receiving AccessDenied even though it has AdministratorAccess attached?

Question 1mediummultiple choice
Full question →

Based on the exhibit, why is the IAM role still receiving AccessDenied even though it has AdministratorAccess attached?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

AdministratorAccess is always evaluated before SCPs, so the SCP is ignored in production accounts.

IAM allows are not evaluated before SCPs in a way that bypasses an SCP deny. The SCP still limits the account.

B

Best answer

The SCP is acting as a maximum permission guardrail, so its explicit deny overrides the IAM allow.

SCPs set the outer boundary for permissions in an account or OU. They do not grant access, but they can block actions even when the IAM role has AdministratorAccess. The explicit deny in the SCP is therefore the reason CreateSnapshot fails. To allow the operation, the organization must change the SCP or move the account out of the restrictive scope.

C

Distractor review

The role needs a session duration of at least 12 hours before SCPs stop applying.

Session duration does not change how SCP evaluation works. The denial is policy-based, not session-length based.

D

Distractor review

The account needs an AWS Config rule to approve the snapshot action before IAM can work.

AWS Config evaluates resource compliance and cannot authorize API calls or override an SCP deny.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: The SCP is acting as a maximum permission guardrail, so its explicit deny overrides the IAM allow. — The exhibit shows an explicit SCP deny for EC2 snapshot actions. In AWS Organizations, SCPs act as permission guardrails: they do not grant permissions, but they can block actions that IAM would otherwise allow. Because the role is in the production OU, the SCP deny takes precedence and causes the AccessDenied result. The fix is to update the SCP or move the account to an OU without that restriction. Why others are wrong: AdministratorAccess does not bypass an SCP deny, so the first option is incorrect. Session duration has nothing to do with policy evaluation, so it cannot remove the denial. AWS Config is for compliance and drift detection, not authorization, so it cannot approve an API call that an SCP blocks.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.