Managed vs inline policies in AWS - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference between managed and inline policies

Which statement correctly describes the difference between AWS managed policies and inline policies?

A Inline policies are AWS predefined policies; managed policies are custom policies created by users.

B Inline policies can be reused across multiple users, groups, or roles; managed policies are embedded directly into a single user, group, or role.

C Managed policies cannot be modified once created; inline policies can be attached to multiple users, groups, or roles.

D Managed policies are standalone and can be attached to multiple users, groups, or roles; inline policies are embedded directly into a single user, group, or role.

💡 Hint

Think about how policies are attached and reused in AWS IAM.

Managed policies are standalone and reusable across multiple identities, while inline policies are embedded directly into a single identity and cannot be reused.

❓ Architecture

intermediate

Policy management best practice

You want to apply the same permissions to multiple IAM users and update permissions easily in the future. Which policy type should you use?

A Use inline policies attached to a group containing the users.

B Use a single customer managed policy attached to all users.

C Use inline policies attached to each user separately.

D Use AWS managed policies only.

💡 Hint

Consider ease of updating permissions for many users at once.

Customer managed policies can be attached to multiple users and updated centrally, making permission management easier.

❓ security

advanced

Policy deletion impact

What happens if you delete a customer managed policy that is attached to multiple IAM roles?

A All roles lose the permissions granted by that policy immediately.

B Roles keep the permissions because the policy is cached locally.

C Roles lose permissions only after a 24-hour delay.

D AWS automatically replaces the deleted policy with a default managed policy.

💡 Hint

Think about how AWS enforces permissions from policies.

Deleting a customer managed policy removes it from all attached roles immediately, causing loss of those permissions.

❓ service_behavior

advanced

Inline policy behavior on user deletion

If an IAM user with an inline policy is deleted, what happens to the inline policy?

A The inline policy is deleted along with the user.

B The inline policy remains in AWS and can be attached to another user.

C The inline policy is converted automatically into a managed policy.

D The inline policy is archived but not deleted.

💡 Hint

Consider the lifecycle of inline policies tied to a single identity.

Inline policies are embedded in the user and are deleted when the user is deleted.

✅ Best Practice

expert

Choosing policy type for audit and reuse

Your organization requires strict auditing of policy changes and wants to reuse policies across multiple accounts. Which policy type and approach best meets these requirements?

A Use AWS managed policies only, as AWS audits all changes automatically.

B Use inline policies in each account to keep policies isolated and auditable per user.

C Use customer managed policies stored in AWS Organizations and attach them across accounts.

D Use inline policies attached to groups to simplify reuse and auditing.

💡 Hint

Think about centralized management and audit capabilities across accounts.

Customer managed policies can be centrally managed and audited, and shared across accounts using AWS Organizations, supporting reuse and compliance.

Practice

1. Which statement best describes an AWS managed policy?

easy

A. A policy that cannot be changed once created.

B. A policy embedded directly into a single user, group, or role.

C. A reusable permission set that can be attached to multiple users, groups, or roles.

D. A policy that only applies to AWS services, not users.

Solution

1. Step 1: Understand managed policy characteristics

   Managed policies are standalone and reusable permission sets in AWS.

2. Step 2: Compare with inline policies

   Inline policies are embedded directly into one user, group, or role, unlike managed policies.

3. Final Answer:

   A reusable permission set that can be attached to multiple users, groups, or roles. -> Option C

4. Quick Check:

   Managed policy = reusable permission set [OK]

Hint: Managed = reusable; Inline = embedded [OK]

Common Mistakes:

• Confusing inline policies as reusable
• Thinking managed policies are fixed and unchangeable
• Assuming managed policies apply only to services

2. Which of the following is the correct way to attach an inline policy to a user in AWS IAM?

easy

A. AttachPolicy(userName, policyArn)

B. PutUserPolicy(userName, policyName, policyDocument)

C. AttachUserPolicy(userName, policyName)

D. CreateInlinePolicy(policyDocument)

Solution

1. Step 1: Identify AWS IAM API for inline policies

   The correct API to attach an inline policy to a user is PutUserPolicy, which requires user name, policy name, and policy document.

2. Step 2: Eliminate incorrect options

   AttachPolicy and AttachUserPolicy are not valid AWS IAM API calls for inline policies. CreateInlinePolicy is not a valid standalone call.

3. Final Answer:

   PutUserPolicy(userName, policyName, policyDocument) -> Option B

4. Quick Check:

   Inline policy attachment uses PutUserPolicy [OK]

Hint: Inline policies use PutUserPolicy API [OK]

Common Mistakes:

• Using AttachPolicy which is for managed policies
• Confusing policy ARN with inline policy document
• Trying to create inline policy without specifying user

3. Given the following scenario: A user has both an inline policy allowing S3 read access and a managed policy denying S3 access. What is the effective permission for S3 access?

medium

A. The user cannot read S3 because explicit deny in managed policy overrides allow.

B. The user cannot read S3 because inline policies are ignored when managed policies exist.

C. The user can read S3 because managed policies are ignored if inline policies exist.

D. The user can read S3 because inline policies override managed policies.

Solution

1. Step 1: Understand AWS policy evaluation logic

   AWS evaluates all policies together. Explicit deny in any policy overrides any allow.

2. Step 2: Apply to scenario

   The managed policy denies S3 access explicitly, so even though inline policy allows it, deny takes precedence.

3. Final Answer:

   The user cannot read S3 because explicit deny in managed policy overrides allow. -> Option A

4. Quick Check:

   Explicit deny always overrides allow [OK]

Hint: Explicit deny beats allow, regardless of policy type [OK]

Common Mistakes:

• Thinking inline policies override managed policies
• Assuming allow always wins
• Ignoring explicit deny rules

4. You created an inline policy for a role but it is not granting the expected permissions. What is the most likely cause?

medium

A. The inline policy JSON syntax is invalid.

B. The role already has a managed policy attached with higher priority.

C. Inline policies cannot be attached to roles.

D. The inline policy name conflicts with an existing managed policy.

Solution

1. Step 1: Verify inline policy attachment rules

   Inline policies can be attached to roles, so Inline policies cannot be attached to roles. is incorrect.

2. Step 2: Check common issues with inline policies

   Invalid JSON syntax in the inline policy will prevent permissions from applying correctly.

3. Step 3: Understand policy priority

   Managed and inline policies are evaluated together; no priority overrides permissions except explicit deny.

4. Final Answer:

   The inline policy JSON syntax is invalid. -> Option A

5. Quick Check:

   Invalid JSON breaks policy effect [OK]

Hint: Check JSON syntax first for inline policy issues [OK]

Common Mistakes:

• Assuming inline policies can't attach to roles
• Thinking managed policies override inline by priority
• Confusing policy names causing conflicts

5. You manage a team where multiple users need the same permissions to access DynamoDB. You also have one user who needs a unique permission set. What is the best approach to assign policies?

hard

A. Use only managed policies for all users, including the unique one.

B. Create inline policies for all users to keep permissions separate.

C. Attach the same inline policy to all users and add extra inline policies for the unique user.

D. Create a managed policy for the common permissions and attach it to all users; create an inline policy for the unique user.

Solution

1. Step 1: Identify best practice for shared permissions

   Managed policies are reusable and ideal for common permissions shared by multiple users.

2. Step 2: Handle unique permissions

   Inline policies are best for unique, one-off permissions tied to a single user.

3. Step 3: Combine approaches for efficiency and clarity

   Use managed policy for the team and inline policy for the unique user to avoid duplication and ease management.

4. Final Answer:

   Create a managed policy for the common permissions and attach it to all users; create an inline policy for the unique user. -> Option D

5. Quick Check:

   Managed for shared, inline for unique [OK]

Hint: Managed for many users, inline for one user [OK]

Common Mistakes:

• Using inline policies for all users causing duplication
• Using only managed policies losing unique control
• Attaching same inline policy to multiple users