mediummultiple choiceObjective-mapped

A company uses AWS Organizations and has separate development, test, and production accounts. The security team wants to ensure that no one in the sandbox organizational unit can disable AWS CloudTrail or delete the central audit bucket, even if an account administrator creates permissive IAM policies later. Which control should they use?

Question 1mediummultiple choice
Full question →

A company uses AWS Organizations and has separate development, test, and production accounts. The security team wants to ensure that no one in the sandbox organizational unit can disable AWS CloudTrail or delete the central audit bucket, even if an account administrator creates permissive IAM policies later. Which control should they use?

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

Attach an identity-based policy in each account that denies CloudTrail changes.

Identity policies are easy to bypass if account admins can create other roles or policies within the same account.

B

Best answer

Use a service control policy on the sandbox organizational unit to deny the prohibited actions.

Service control policies are the correct governance mechanism for setting guardrails across multiple accounts in AWS Organizations. An SCP can explicitly deny sensitive actions such as disabling CloudTrail or deleting the audit bucket, and those denies apply even if administrators create local IAM policies that would otherwise allow the actions. SCPs do not grant permissions by themselves; they only constrain what account principals can ever do within the OU.

C

Distractor review

Create an S3 bucket policy that allows only the audit team role to delete objects.

A bucket policy can protect the bucket itself, but it does not stop CloudTrail from being disabled in the account.

D

Distractor review

Apply a permission boundary to each IAM user in the sandbox accounts.

Permission boundaries help control specific IAM principals, but they do not provide a broad account-level guardrail across all principals and services.

Common exam trap

Common exam trap: ACLs stop at the first match

ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.

Technical deep dive

How to think about this question

ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.

KKey Concepts to Remember

  • Standard ACLs match source addresses.
  • Extended ACLs can match source, destination, protocol and ports.
  • The first matching ACL entry is used.
  • There is usually an implicit deny at the end.

TExam Day Tips

  • Check inbound versus outbound direction.
  • Read the ACL from top to bottom.
  • Look for a broader permit or deny above the intended line.

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?

Standard ACLs match source addresses.

What is the correct answer to this question?

The correct answer is: Use a service control policy on the sandbox organizational unit to deny the prohibited actions. — An SCP is the best control because it sets an upper bound on permissions for every principal in the affected accounts or OU. This is exactly what organizations use when they need centralized guardrails that local administrators cannot override. By denying CloudTrail tampering and audit bucket deletion at the OU level, security preserves logging integrity across all accounts, regardless of permissions created inside each account. Why others are wrong: Identity policies can be overridden by other local roles and do not enforce organization-wide guardrails. A bucket policy protects only that bucket and does not stop CloudTrail from being turned off. Permission boundaries are useful for a specific principal, but they do not scale as an account-level governance control across every user and role.

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.