Final answer:
IAM Roles in AWS are not associated with long-term credentials but can be assumed to provide temporary credentials. Roles are not logged into directly but assumed, which mirrors the process of logging in and results in the generation of temporary credentials for access.
Step-by-step explanation:
The question is regarding IAM Roles in a cloud computing context, likely referring to AWS (Amazon Web Services). Let's clarify each point:
Roles do not have associated Long Term Credentials (Access Keys) - this statement is false. IAM Roles are designed to be secure and do not have static credentials. Instead, they grant required permissions without the need for access keys that are long-term.
Roles can be assumed - this statement is true. IAM Roles can be assumed by AWS services or users, allowing temporary security credentials to be used to make AWS API calls.
When assumed, temporary credentials are generated - this is true. Once an IAM Role is assumed, temporary credentials are provided to access AWS services.
Roles themselves cannot be directly 'logged into' like a user - however, you can assume a role to obtain temporary credentials that enable you to access AWS resources.
When an identity logs into a role, temporary credentials are generated - this is contextually true. When you assume a role, for all intents and purposes, it's akin to 'logging in' and does indeed generate temporary credentials.