An architect is listing the identity types that Microsoft Entra ID can represent for machine or non-human workloads, as opposed to human users. Which TWO of the following are machine identity types in Microsoft Entra ID? Select TWO.
- AA guest user account invited from a partner organisation to collaborate
- BA service principal that represents an application instance within the tenant Correct
- CA member user account created directly inside the organisation's own directory
- DA managed identity assigned to an Azure resource so it can reach other services Correct
- EA security group used to grant several users access to a shared application
Why A is wrong: A guest is a real Entra identity, but it represents a human collaborator, so it is not a machine or non-human identity type.
Why B is correct: A service principal is the local identity an application uses to authenticate and be authorised, a core machine identity type.
Why C is wrong: A member user is a human identity native to the tenant, so it does not belong to the machine or non-human category.
Why D is correct: A managed identity gives an Azure resource an automatically managed identity in Entra, a machine identity that removes credential handling.
Why E is wrong: A group bundles users for access management but is not itself an identity that authenticates, so it is not a machine identity.