IAM roles provide delegated access through temporary security credentials. A trusted user, application, workload, federated identity, or AWS service assumes a role and receives time-limited credentials from AWS Security Token Service. The permissions attached to the role determine which actions can be performed on which resources. Because the credentials expire and do not need to be permanently embedded in applications, IAM roles are the correct answer. IAM Access Analyzer identifies external, internal, or unused access and can validate policies, but it does not grant temporary credentials. Service control policies define the maximum permissions that can be available to accounts or organizational units in AWS Organizations. SCPs do not grant access and do not issue credentials. Access control lists are resource-level permission mechanisms supported by certain services; they do not create temporary identity sessions. AWS recommends temporary credentials and roles instead of long-term access keys wherever possible because temporary credentials automatically expire and reduce the risks associated with permanent credentials. The exam association is straightforward: assuming an IAM role produces temporary credentials with permissions limited by the role’s policies.