Which guidelines are best practices for using AWS Identity and Access Management (IAM)? (Choose two.)

Sharing access keys is a severe security vulnerability that compromises accountability and makes it difficult to track actions, violating the principle of least privilege.

Creating individual IAM users for each person or service that needs access to AWS resources enables proper auditing, granular access control, and simplifies credential management without sharing root account credentials.

While inline policies have their uses, using customer managed policies is generally preferred for reusability, versioning, and easier management across multiple IAM entities.

Granting maximum privileges to IAM users violates the principle of least privilege, which states that users should only have the minimum permissions necessary to perform their tasks.

Using groups to assign permissions to IAM users simplifies administration and ensures consistency, as you can attach policies to a group, and all users in that group inherit those permissions. This is more scalable than attaching policies directly to individual users.