IAM users and groups in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when an IAM user is removed from a group?

Consider an IAM user who is part of a group with specific permissions. What is the effect on the user's permissions immediately after they are removed from that group?

A The user’s permissions are unaffected because group membership changes do not apply to existing users.

B The user retains the group permissions until they log out and log back in.

C The user keeps the group permissions permanently unless explicitly revoked.

D The user immediately loses all permissions granted by the group.

💡 Hint

Think about how AWS evaluates permissions dynamically.

When a user is removed from a group, the permissions granted by that group are revoked immediately. AWS evaluates permissions in real time, so the user no longer inherits the group's permissions right after removal.

❓ Architecture

intermediate

How to organize IAM users for a company with multiple departments?

A company has three departments: Sales, Engineering, and HR. Each department needs different AWS permissions. What is the best way to organize IAM users and groups to manage permissions efficiently?

A Create one IAM group per department and assign users to their respective groups with department-specific policies.

B Create one IAM group for all users and assign all permissions to that group.

C Create individual IAM users with unique policies for each user without using groups.

D Assign permissions directly to IAM users without using groups or roles.

💡 Hint

Think about how groups help manage permissions for many users.

Using one group per department allows you to assign permissions once to the group. Then, adding or removing users from groups automatically grants or revokes the correct permissions. This is efficient and scalable.

❓ security

advanced

What is the security risk of assigning permissions directly to IAM users instead of groups?

Consider a scenario where permissions are assigned directly to individual IAM users rather than through groups. What is a key security risk of this approach?

A It increases the chance of inconsistent permissions and makes auditing difficult.

B It automatically grants admin access to all users.

C It disables multi-factor authentication for users.

D It prevents users from accessing AWS services.

💡 Hint

Think about managing many users and tracking their permissions.

Assigning permissions directly to users can lead to inconsistent permissions across users and makes it harder to audit and manage permissions. Groups help centralize and simplify permission management.

🧠 Conceptual

advanced

What is the effect of attaching multiple policies to an IAM group?

If an IAM group has multiple policies attached, how are the permissions combined for users in that group?

A Only the permissions from the first attached policy are applied.

B Permissions from all policies are combined, granting the union of all allowed actions.

C Permissions are intersected, so only actions allowed by all policies are granted.

D The last attached policy overrides all previous policies.

💡 Hint

Think about how AWS evaluates multiple policies together.

AWS combines permissions from all attached policies by taking the union of allowed actions. This means users get all permissions granted by any of the policies.

✅ Best Practice

expert

How to securely grant temporary elevated permissions to an IAM user?

An IAM user needs temporary elevated permissions for a specific task. Which approach follows AWS best practices for security?

A Attach the elevated permissions policy directly to the user permanently.

B Add the user to a group with elevated permissions permanently and remove them after the task.

C Create a role with the elevated permissions and allow the user to assume that role temporarily.

D Create a new IAM user with elevated permissions and share the credentials.

💡 Hint

Think about temporary access and avoiding permanent permission changes.

Using roles that users can assume temporarily is the best practice. It avoids permanent permission changes and reduces risk by granting elevated permissions only when needed.