AZ-305 Practice Question 82: Lifecycle Workflows Joiner Leaver
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 9 · question 2 of 10
An HR system holds each employee's hire date and termination date, and it already writes those attributes into Microsoft Entra ID through HR-driven provisioning. The company wants the following to happen automatically, with no administrator running a script:
- Two days before a new hire's start date, send them a welcome email with sign-in instructions and add them to the groups for their department. - On the employee's last day, disable their account, remove them from all groups, and revoke their refresh tokens. - 30 days after the last day, permanently delete the account. - Managers must never approve or trigger these steps; they run purely from the HR attributes.
Which capability should you configure?
Show answer and explanation
Answer:
Lifecycle workflows automate the joiner, mover and leaver tasks that used to require custom scripts or manual work: they run on a schedule or on an attribute change, such as an employee's hire date or termination date already synchronized from HR, and each workflow chains built-in tasks such as sending a welcome email, adding group memberships, disabling the account, removing memberships, revoking sessions, and deleting the account after a delay. None of that needs a person to request or approve anything, which matches the requirement that the steps run purely from HR attributes.
Option A solves a different problem: entitlement management assigns access to resources, such as groups, apps and sites, through access packages. It does not run account lifecycle actions like disabling sign-in, revoking sessions or deleting the account, and its request-based policies put a manager's approval in the path, which the requirements rule out.
Option C manages temporary elevation to privileged roles through activation and approval, not account creation, welcome email delivery, or deprovisioning on termination.
Option D can disable membership in a group as the termination date attribute changes, but it cannot send a welcome email before start date, disable the sign-in account, revoke tokens, or delete the account afterward, so it covers only a fragment of the requirement.
Reference: What are lifecycle workflows?