Question 1
A company has verified contoso.example as a Microsoft Entra custom domain. HR needs a new cloud-only employee to sign in as mia@contoso.example tomorrow. No account exists for Mia yet. Which action creates the required sign-in identity?
Explanation
Correct Answer
A Microsoft Entra member user is the directory object that can represent an employee for cloud sign-in. The requested custom suffix has already been verified, so the administrator can create the cloud identity with the specified UPN and the organization's permitted initial credential and authentication settings. A security group or Azure resource group cannot replace an interactive user object. The administrator should also follow onboarding controls for the account rather than granting broad subscription privileges merely to make sign-in possible.
Incorrect Answers
A security group aggregates identities for authorization or policy targeting; it is not itself the employee's sign-in account. Giving the group Reader at subscription scope would create an access grant, not the named user with a usable UPN. It would also introduce unnecessary Azure access before the employee's actual job role has been established.
B2B guest invitations are intended for collaboration with identities managed by an external organization. The case states that HR needs a new cloud-only workforce member and no external home identity is supplied. Creating a guest invitation would not meet the requested member-user lifecycle or initial sign-in configuration for the company's own employee.
Azure resource groups are management containers for Azure resources such as VMs and storage accounts. Naming a resource group after the employee neither creates a Microsoft Entra directory user nor provisions a UPN. Tags only annotate the resource group's metadata, so this operation cannot establish Mia's required authentication identity.