Bird
0
0

An IAM policy attached to a user is not granting expected permissions. What is a common reason for this issue?

medium📝 Debug Q6 of 15
AWS - Identity and Access Management
An IAM policy attached to a user is not granting expected permissions. What is a common reason for this issue?
AThe user has no active AWS account
BThe user is not logged in to the AWS console
CThere is an explicit deny in another policy
DThe policy uses incorrect JSON syntax
Step-by-Step Solution
Solution:
  1. Step 1: Check for conflicting policies

    Explicit deny in any policy overrides allows and blocks permissions.
  2. Step 2: Understand impact on user permissions

    If another policy explicitly denies actions, the user cannot perform them even if allowed elsewhere.
  3. Final Answer:

    Explicit deny in another policy causes permission failure -> Option C
  4. Quick Check:

    Explicit deny blocks permissions [OK]
Quick Trick: Explicit deny blocks permissions even if allowed elsewhere [OK]
Common Mistakes:
MISTAKES
  • Assuming user login status affects policy evaluation
  • Ignoring explicit deny effects
  • Blaming JSON syntax without error messages

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes