No special regional configuration is required because AWS Identity and Access Management is a global service is correct because IAM identities and roles are global and staff can sign in from any office to manage resources deployed in any AWS Region.

IAM is not tied to a specific Region so a single IAM user or role can be granted policies that permit actions on resources across Regions. This avoids duplicating identities and lets administrators control access centrally with policies and roles.

Create separate IAM users for every person in each AWS Region is wrong because IAM identities are global and creating per Region users adds unnecessary administrative overhead and risks inconsistent permissions.

Allow employees to use a coworker's credentials when traveling is wrong because credential sharing breaks least privilege, prevents reliable auditing, and increases security risk.

Use AWS Organizations to create a dedicated AWS account for each user in every Region is wrong because Organizations is for account governance and isolation rather than per user per Region access and creating one account per user would cause excessive cost and complexity.

Full AWS Practitioner Certification Question