SC-300 domain - 25% of the exam

Plan and Automate Identity Governance

Plan and Automate Identity Governance is 25% of the SC-300 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

72
Practice questions
6
Objectives
59
Medium
13
Hard

Where people go wrong

  • Confusing access reviews, access packages and PIM

    The wrong answers lend one governance feature the job of another. Access reviews recertify existing access on a schedule, so they cannot gate a new package request or collect a justification at request time. Privileged Identity Management governs activation of roles, not access package requests. Access packages grant bundles of resources on request and do not recertify a privileged role assignment. The assignment policy carries the request scope, multi-stage approval and custom questions for a package.

    See it in a sample question
  • Treating advice and reminders as enforcement

    Decision helpers, mail notifications and a recurrence schedule look as though they act on a review, yet none of them changes membership. Decision helpers only recommend, notifications only remind reviewers, and recurrence only sets when reviews run. A denied user keeps access until results are applied, and the setting Auto apply results to resource applies them automatically when each cycle ends. A separate option, If reviewers don't respond, sets the outcome for members no reviewer decided, which auto-apply does not cover.

    See it in a sample question
  • Treating an active assignment as just-in-time access

    The wrong answers grant the role as an active assignment, whether permanent, time-bound or through group membership, and so leave standing privilege in place before any need arises. Only an eligible assignment gives no access until the user activates it, and activation settings then add approval, multifactor authentication and a bounded duration. Contributor on a subscription is an Azure resource role, so the subscription must first be onboarded to Privileged Identity Management.

    See it in a sample question
  • Confusing activation duration with eligibility expiry

    Maximum activation duration caps how long a single raise of a role lasts. It does not end the eligibility itself. The wrong answers use it, or an access review or an approver, as the way to retire an assignment automatically. Eligibility expires when the eligible assignment is given an end date as it is created, which suits a contractor engagement. The two controls cover separate requirements and are set in different places.

    See it in a sample question
  • Choosing the wrong log for the evidence

    Sign-in logs, provisioning logs and audit logs each answer a different question, and the wrong options pick a neighbour. Sign-in logs record authentication events, not Privileged Identity Management activation justifications or directory changes. Provisioning logs record per-user attribute detail for connected applications, not manual group edits. Audit logs record directory changes with actor, target and time. Activation history with requester, justification and approver sits in the Privileged Identity Management audit history.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free samplePlan and Automate Identity Governancemedium

A compliance team requires that requests for a sensitive access package go through two stages of approval: first the requestor's manager, and then a named security reviewer, with the request denied if either stage does not approve within the configured window. Where in entitlement management is this two-stage approval defined?

  • AIn the catalog settings, by adding the manager and the security reviewer as catalog owners so both must sign off before any package in the catalog is granted.
  • BIn the access package assignment policy approval settings, by enabling approval and adding a first stage with the manager and a second stage with the security reviewer. Correct
  • CIn an access review configured on the access package, by scheduling the manager and the security reviewer as the two reviewers who recertify each new request.
  • DIn Privileged Identity Management activation settings for the package, by requiring the manager and security reviewer to approve each just-in-time activation.
Multi-stage approval for an access package is configured in the assignment policy approval settings, defining ordered stages of approvers and decision windows. Approval in entitlement management is a property of the access package assignment policy. It supports up to multiple sequential stages, each with its own approvers, decision deadline, and escalation. Configuring stage one as the manager and stage two as the security reviewer enforces the required order. Catalog ownership, access reviews, and Privileged Identity Management serve different governance functions.

Why A is wrong: Catalog owners manage resources and packages but are not an approval stage for requests, so adding them as owners does not create a sequential two-stage approval for a specific package.

Why B is correct: The assignment policy's approval settings support multi-stage approval, where each stage names approvers and a decision window, so a manager-then-reviewer sequence is configured exactly there.

Why C is wrong: An access review recertifies existing assignments on a schedule rather than approving incoming requests, so it cannot act as a gate on a new request at the moment of submission.

Why D is wrong: Privileged Identity Management governs activation of Microsoft Entra and Azure roles, not access package requests, so its approval flow does not apply to entitlement management package assignments.

Free samplePlan and Automate Identity Governancemedium

A governance lead schedules an access review for a sensitive group and sets it to recur monthly. Reviewers complete decisions, but the lead wants approved or denied outcomes to be enforced on the group membership automatically at the end of each occurrence, without an administrator manually committing the results every month. Which setting must be enabled?

  • AEnable 'Auto apply results to resource' so completed decisions are committed when each review ends Correct
  • BSet the recurrence frequency to monthly so decisions are committed at each occurrence
  • CSet the 'If reviewers don't respond' option to Remove access for undecided members
  • DEnable email notifications to reviewers so they are reminded to apply their own decisions
Understand that enabling auto apply results to resource commits reviewer decisions to the resource automatically at the end of each access review occurrence. Auto apply results to resource enforces the decisions reviewers recorded by writing them to the group membership when the review ends. Without it, an administrator must manually apply results, so enabling it is what removes the monthly manual step for a recurring review.

Why A is correct: Auto apply results to resource writes the reviewers' approve and deny decisions to the group automatically at the end of each occurrence, removing the need for manual commit each month.

Why B is wrong: Recurrence only schedules when reviews run; it controls timing, not whether reviewer decisions are written back to the group membership, so it cannot enforce outcomes.

Why C is wrong: This only handles members with no decision and does not commit the explicit approve or deny decisions reviewers made, so enforcement would still require manual action.

Why D is wrong: Notifications prompt reviewers to decide but do not apply outcomes to the resource; reviewers cannot commit membership changes themselves through a reminder.

Free samplePlan and Automate Identity Governancehard

A platform engineer is granted access to the Contributor role on a production Azure subscription through Microsoft Entra Privileged Identity Management. The security team requires that the engineer hold no permissions on the subscription until a genuine need arises, at which point they may raise their access for a bounded period and the activation is recorded for audit. Which assignment type should the administrator configure for the engineer?

  • AAn active assignment with a defined start and end date, so the Contributor role is permanently granted only within the scheduled window
  • BA permanent active assignment, relying on Conditional Access to challenge the engineer each time the Contributor role is exercised
  • CAn eligible assignment, so the engineer holds no standing access and must activate the Contributor role for a bounded period before using it Correct
  • DA group-based active assignment through a role-assignable group, so membership confers the Contributor role until the engineer is removed
Distinguish PIM eligible assignments, which grant just-in-time activatable access, from active assignments, which confer standing permissions for the assignment period. PIM eligible assignments grant zero standing permission and require the user to activate the role for a bounded duration, producing an auditable activation event each time, which matches the no-standing-access and bounded-raise requirement. Active assignments, whether permanent or time-bound, hand the user the role continuously for the assignment period without any activation step.

Why A is wrong: A time-bound active assignment is tempting because it expires, but it grants standing access for the whole window with no activation step, so the engineer holds permissions before any need arises.

Why B is wrong: A permanent active assignment gives continuous standing access, which violates the no-standing-permission requirement; Conditional Access challenges sign-in, not role possession.

Why C is correct: An eligible assignment grants no standing permissions; the engineer activates just in time for a bounded window, and each activation is logged, which is exactly what the requirement describes.

Why D is wrong: Group-based active membership still confers standing access for as long as the user is a member, providing no just-in-time activation and no per-use audit of a raise.

Free samplePlan and Automate Identity Governancehard

A contractor is granted an eligible User Administrator assignment in Privileged Identity Management but is told the eligibility should automatically expire at the end of a three-month engagement so it does not require manual cleanup. Which setting on the assignment achieves this?

  • AConfigure a time-bound eligible assignment with a start and end date covering the engagement, so the eligibility itself expires automatically when the period ends. Correct
  • BSet the maximum activation duration of the User Administrator role to ninety days, so the contractor's eligibility lapses once that activation window is exhausted.
  • CCreate a permanent eligible assignment and schedule a recurring access review that removes the contractor when the engagement is judged to be over.
  • DRequire justification and ticket information on activation, which causes Privileged Identity Management to revoke the eligibility once the referenced ticket is closed.
Time-bound eligible assignments in Privileged Identity Management carry explicit start and end dates and expire automatically, removing the need for manual cleanup. Privileged Identity Management assignments can be permanent or time-bound. A time-bound eligible assignment with a defined start and end date is removed automatically when the end date passes, which is the correct mechanism for a fixed-length engagement. Activation duration, access reviews, and ticket fields each serve different purposes and do not set a hard expiry on the eligibility itself.

Why A is correct: Privileged Identity Management supports time-bound assignments with explicit start and end dates, so an eligible assignment that ends after three months expires on its own without any manual removal.

Why B is wrong: Maximum activation duration limits how long a single activation lasts, not how long the eligibility exists, so it would never expire the assignment after three months.

Why C is wrong: An access review depends on a reviewer's decision and a review cadence rather than a fixed expiry date, so it does not guarantee automatic expiry exactly at three months without manual judgement.

Why D is wrong: Justification and ticket fields are recorded for audit only; Privileged Identity Management does not read external ticket status, so closing a ticket has no effect on the eligibility.

Free samplePlan and Automate Identity Governancemedium

An administrator investigates why several users were added to a privileged group last week. The administrator needs to know who performed the membership changes, the target object, and the exact time each change occurred. Which Microsoft Entra log should the administrator examine to find this information?

  • AThe sign-in logs, because they record every interactive and non-interactive authentication and therefore contain the directory changes each administrator made during their session.
  • BThe provisioning logs, because they record all object lifecycle changes synchronised by Microsoft Entra and therefore include group membership edits made through the admin centre.
  • CThe Identity Secure Score history, because it tracks security-relevant configuration changes including modifications to the membership of privileged groups over time.
  • DThe audit logs, because they record directory changes such as group membership additions, including the actor who made the change, the target object, and the timestamp. Correct
Microsoft Entra audit logs record directory changes such as group membership additions with the actor, target object, and timestamp for investigations. Directory changes including adding members to a group are written to the audit logs, which record the activity, the initiating actor, the target object, and the timestamp. Sign-in logs cover authentication, provisioning logs cover the provisioning service's object syncs, and Identity Secure Score history tracks score-affecting actions, so none of those carries the per-change membership detail.

Why A is wrong: Sign-in logs record authentication events and conditional access outcomes, not the directory changes performed afterwards, so they show who signed in but not who modified the group's membership.

Why B is wrong: Provisioning logs cover objects created, updated, or deleted by the provisioning service for connected applications and HR sources, not membership changes made manually in the directory, so they would not list these edits.

Why C is wrong: Identity Secure Score history tracks changes to the score driven by improvement actions, not individual group membership edits with actor and timestamp, so it cannot identify who added the members or when.

Why D is correct: Audit logs capture create, update, and delete activities across the directory, including adding members to a group, and record the initiating actor, the target object, and the time, which is exactly what the investigation needs.

Other domains in this exam

See also the SC-300 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.