Assign permissions by adding users to IAM groups and Define reusable customer managed policies instead of inline policies attached to a single identity are the correct approaches because they promote scalable, reusable, and auditable permission management.

Assign permissions by adding users to IAM groups lets you manage permissions in one place and apply them consistently to many users so onboarding and offboarding are simpler and you reduce configuration drift while enforcing least privilege.

Define reusable customer managed policies instead of inline policies attached to a single identity allows you to reuse policies across users and roles and to update, version, and audit permissions centrally while inline policies remain tied to a single principal and are harder to maintain.

Always prefer customer managed policies over AWS managed policies is not correct because AWS managed policies are maintained by AWS and are a recommended starting point and you should create customer managed policies only when you need customization or tighter control.

Share a common IAM user among developers to reduce management overhead is wrong because shared credentials eliminate individual accountability and make credential rotation and auditing difficult and you should use individual identities or federated access with roles.

Use AWS Organizations service control policies to grant permissions to individual users is incorrect because service control policies act as account level guardrails and do not grant permissions to users and you still need IAM policies or roles to authorize actions.

Full AWS Practitioner Certification Question