Courseiva

Microsoft Identity and Access Administrator Associate (SC-300) — Questions 76–150

242 questions total · 4 pages · All types, answers revealed

Page 1

Page 2 of 4

Page 3
76
MCQmedium

Your company uses Microsoft Entra Connect to sync identities from an on-premises Active Directory. You have a user named 'User1' who exists in both environments, but they are not currently linked. You need to perform a 'soft-match' to link them. Which attribute must be identical on both the on-premises and cloud objects?

A.ObjectGUID
B.DisplayName
C.proxyAddresses
D.EmployeeID
AnswerC

Entra Connect uses the primary SMTP address or the proxyAddresses attribute to perform a soft-match. If the SMTP address on-premises matches the 'mail' or 'proxyAddresses' attribute in Entra ID, the sync engine will link the two accounts, assuming no other hard-link (ImmutableID) is already present.

Why this answer

A soft-match in Microsoft Entra Connect links on-premises and cloud objects by comparing the primary SMTP address (proxyAddresses) and, optionally, the userPrincipalName. For a soft-match to succeed, the proxyAddresses attribute must be identical on both objects, as it is the primary anchor for matching.

Exam trap

SC-300 often tests the distinction between hard-match (ObjectGUID) and soft-match (proxyAddresses/UPN), causing candidates to select ObjectGUID incorrectly for soft-match scenarios.

How to eliminate wrong answers

Option A is wrong because ObjectGUID is used for hard-matching (via immutable ID) and is not the attribute for soft-match. Option B is wrong because DisplayName is not a unique or reliable matching attribute and is not used for soft-match. Option D is wrong because EmployeeID is not a default matching attribute for soft-match; it can be used for custom matching but requires configuration.

77
MCQmedium

What is the primary difference between a system-assigned and a user-assigned managed identity?

A.System-assigned identities support more Azure services than user-assigned identities.
B.System-assigned identities are standalone resources, while user-assigned are not.
C.User-assigned identities can be shared across multiple Azure resources.
D.System-assigned identities require manual secret rotation.
AnswerC

Because user-assigned identities are independent Azure resources, they can be assigned to multiple VMs or functions simultaneously. This is ideal for scenarios where a group of services requires identical permissions to access a specific set of data, allowing for centralized permission management rather than individual, redundant configuration.

Why this answer

The primary distinction lies in their lifecycle and reusability. A system-assigned identity is bound to a single Azure resource and is deleted when that resource is removed. Conversely, a user-assigned identity is created as a standalone Azure resource, allowing it to be shared across multiple resources, such as several virtual machines or function apps, offering more flexibility for complex architectural patterns.

Exam trap

A common misconception is that system-assigned identities are more flexible because they are managed by Azure, whereas only user-assigned identities can be shared across multiple different Azure resources.

78
MCQhard

You need to implement Authentication Strengths in Conditional Access to ensure that users access highly sensitive applications using only phishing-resistant MFA. Which method should you select?

A.FIDO2 Security Key
B.SMS-based authentication
C.Microsoft Authenticator push notification
D.Voice call authentication
AnswerA

FIDO2 security keys are hardware-based and inherently phishing-resistant because they bind the authentication to the specific origin of the service. They are the gold standard for MFA, as they cannot be captured or replayed by an attacker in a man-in-the-middle phishing proxy attack.

Why this answer

FIDO2 security keys are phishing-resistant because they use public-key cryptography bound to the origin (domain) of the relying party. The private key never leaves the hardware authenticator, and the authentication challenge is signed only for the legitimate site, preventing credential theft via fake login pages. In Conditional Access Authentication Strengths, FIDO2 is explicitly listed as a phishing-resistant method, satisfying the requirement for highly sensitive apps.

SMS, voice, and push notifications are not phishing-resistant because they rely on shared secrets or user approval that can be relayed or intercepted.

Exam trap

SC-300 often tests the misconception that any MFA method is phishing-resistant, but only FIDO2 and Windows Hello for Business meet that bar; push notifications and OTP-based methods are not.

How to eliminate wrong answers

Option B is wrong because SMS-based authentication uses one-time codes sent over telecom networks, which are vulnerable to SIM swapping, interception, and real-time phishing proxies that relay the code to the attacker. Option C is wrong because Microsoft Authenticator push notifications rely on the user approving a prompt; attackers can spam push requests or use MFA fatigue, and the method is not bound to the origin, so it is not phishing-resistant. Option D is wrong because voice call authentication uses an automated call to read a code or press a key, which is also susceptible to interception and social engineering, and lacks cryptographic binding to the application.

79
MCQmedium

Refer to the exhibit. A user with a 'High' risk level attempts to sign in. Based on the provided policy JSON, what is the expected outcome?

A.The user is blocked from signing in.
B.The user must perform MFA to access resources.
C.The user must change their password.
D.The sign-in is denied because risk level is High.
AnswerC

The policy configuration does not specify a password reset requirement. While password resets are a standard response to high-risk identity detections in Identity Protection, they are not defined within this specific Conditional Access grant control, so the system will not enforce a password change at this step.

Why this answer

The explanation must explicitly reference the 'grant controls' defined in the JSON policy (e.g., 'Require password change'). Without the exhibit, the explanation must clearly state that the outcome is determined by the 'grant' block within the Conditional Access policy JSON, which specifically mandates a password reset for high-risk users.

Exam trap

Candidates often confuse 'Sign-in risk' (which triggers MFA) with 'User risk' (which triggers password reset).

80
MCQhard

A security auditor reviews workload identities in your Microsoft Entra tenant. They find an app registration named ReportingApp that has a client secret expiring in 30 days and is used by an on-premises Linux server to read mail via Microsoft Graph. The server cannot use managed identities and the team wants to eliminate secret rotation. You decide to configure Workload Identity Federation using an OpenID Connect (OIDC) trust to an external identity provider that issues tokens with a subject claim of 'reporting-server'. Which configuration step is required on the app registration?

A.Create a new client secret and store it in Azure Key Vault, then reference it from the server.
B.Add a federated identity credential specifying the issuer, subject, and audience of the external tokens.
C.Upload the external identity provider's signing certificate to the app registration's Certificates & secrets blade.
D.Configure the app registration to use implicit flow and enable ID tokens.
AnswerB

A federated identity credential on the app registration defines the trust relationship. It includes the issuer URL, the subject value (such as 'reporting-server'), and the audience that Microsoft Entra ID expects. This allows the app to exchange externally issued tokens for Microsoft Entra access tokens without a client secret, meeting the requirement to eliminate secret rotation.

Why this answer

Workload identity federation replaces client secrets with a trust relationship configured as a federated identity credential on the app registration. The credential specifies the external issuer, the subject claim value, and the audience, enabling the on-premises server to present an OIDC token and receive a Microsoft Entra access token. This eliminates secret rotation while preserving Microsoft Graph access.

Exam trap

The trap here is thinking that federated identity requires uploading the external provider's certificate, when instead you configure a federated identity credential with issuer, subject, and audience values.

81
MCQmedium

You are the Identity and Access Administrator for a company that uses Microsoft Entra ID. The company has a Microsoft 365 E5 subscription. The security team requires that all users who access the Microsoft Teams web client from unmanaged devices must use multi-factor authentication (MFA) and that their session must be limited to 4 hours. You need to configure a Conditional Access policy to meet these requirements. What should you do?

A.Create a Conditional Access policy that targets the Microsoft Teams cloud app, sets the device state condition to 'Unmanaged', requires MFA as a grant control, and configures the session control to 'Use app enforced restrictions'.
B.Create a Conditional Access policy that targets the Microsoft Teams cloud app, sets the device state condition to 'Unmanaged', requires MFA as a grant control, and sets the sign-in frequency to 4 hours.
C.Create a Conditional Access policy that targets all cloud apps, sets the client apps condition to 'Browser', requires MFA as a grant control, and sets the sign-in frequency to 4 hours.
D.Create a Conditional Access policy that targets the Microsoft Teams cloud app, sets the device platform condition to 'Windows', requires MFA as a grant control, and sets the sign-in frequency to 4 hours.
AnswerB

This policy correctly applies to the Teams cloud app, uses device state to identify unmanaged devices, enforces MFA, and sets sign-in frequency to 4 hours. Conditional Access device state condition filters by device management status, and sign-in frequency controls reauthentication. The combination meets both requirements: MFA and session limitation for unmanaged devices accessing Teams.

Why this answer

The correct policy must target the Teams cloud app, use the device state condition to identify unmanaged devices, require MFA, and set sign-in frequency to 4 hours. This ensures that only unmanaged devices accessing Teams are subject to MFA and a 4-hour session limit. Other options either target the wrong scope, use incorrect conditions, or apply session controls that do not enforce reauthentication.

Exam trap

The trap here is confusing device state with device platform or using app enforced restrictions for session control instead of sign-in frequency.

82
MCQeasy

You need to perform a bulk invite of 50 guest users from a partner company using a CSV file in the Microsoft Entra admin center. Which column is mandatory in the CSV file for the bulk invitation process to succeed?

A.First name
B.Redirect URL
C.User principal name
D.Email address to invite
AnswerD

The 'Email address to invite' is the most critical field because it identifies where the invitation will be sent and serves as the basis for the guest's identity. Without this address, Entra ID cannot initiate the B2B communication or establish the link between the external user and the local tenant.

Why this answer

Bulk operations are a key skill for identity administrators to handle large-scale changes efficiently. For B2B invitations, Entra ID requires specific identifiers to send the invitation emails and create the guest user objects. Knowing the required schema for these CSV files prevents upload errors and ensures a smooth onboarding experience for external partners.

Exam trap

Candidates frequently select 'Display Name' or 'Usage Location' as mandatory fields, failing to realize that the email address is the only unique identifier required to trigger the invitation.

83
MCQhard

Your organization uses Microsoft Entra ID Governance. A service principal named BillingConnector has an access package assignment that grants it membership in a group with access to sensitive billing APIs. Security policy requires that the service principal's access be reviewed every 90 days by the application owner and automatically removed if the owner does not respond. What should you configure?

A.Create an access review for the access package assignment with a recurrence of 90 days, the application owner as reviewer, and auto-apply results with no-response set to remove access.
B.Create an access review scoped to the group membership with the application owner as reviewer and auto-apply enabled.
C.Configure a lifecycle workflow that removes the service principal from the group 90 days after assignment.
D.Enable Privileged Identity Management for the group and require the service principal to activate membership with justification every 90 days.
AnswerA

Access reviews in Microsoft Entra ID Governance can target access package assignments, including those held by service principals. Setting the recurrence to 90 days, assigning the application owner as reviewer, and configuring auto-apply with removal on no response enforces the policy exactly. This provides recurring attestation and automatic revocation without manual intervention.

Why this answer

Access reviews in Microsoft Entra ID Governance can be scoped to access package assignments and support service principals as subjects. Configuring a 90-day recurrence, the application owner as reviewer, and auto-apply with removal on no response satisfies both the periodic attestation and the automatic revocation requirements. Group-only reviews, lifecycle workflows, and PIM activation do not meet the full policy.

Exam trap

The trap here is scoping the review to the group instead of the access package assignment, which can miss access granted indirectly through the package.

84
MCQhard

Refer to the exhibit. You are reviewing the configuration of an application registration. What is the most significant security risk present in this configuration?

A.The use of ClientSecret as an authentication method.
B.The application ID is too short.
C.The Directory.Read.All permission is too broad.
D.The expiry date is in the past.
AnswerC

Directory.Read.All is a highly privileged permission. It grants the application access to sensitive metadata about every user, group, and device in the tenant. This level of access is a major security risk for most applications and should be replaced with more specific, limited permissions whenever possible.

Why this answer

The Directory.Read.All permission is an application-level permission that grants the app the ability to read all directory data, including users, groups, and other objects, without a signed-in user. This is overly broad for most applications and violates the principle of least privilege. If the app is compromised, an attacker could enumerate the entire directory, leading to data exposure.

Therefore, it is the most significant security risk.

Exam trap

SC-300 often tests the principle of least privilege; candidates may focus on authentication methods or expiry dates and miss that overly broad permissions like Directory.Read.All represent a significant security risk.

How to eliminate wrong answers

Option A is wrong because using a client secret is a common and acceptable authentication method for confidential clients, though it should be stored securely; it is not inherently a risk if managed properly. Option B is wrong because the application ID length is determined by Azure AD and is not a security risk. Option D is wrong because an expiry date in the past would cause authentication failures, but it is a configuration error, not a security risk; it does not expose data.

85
MCQmedium

You are the Identity and Access Administrator for a company that uses Microsoft Entra ID. The company has a single tenant and wants to allow users to sign in to Microsoft 365 apps by using only a FIDO2 security key, with no password. Users must first register their security key. You need to configure the authentication methods policy so that only FIDO2 security keys are available for sign-in, and all other methods are disabled. What should you do?

A.Configure a temporary access pass for all users and require its use for sign-in.
B.Enable Windows Hello for Business in the authentication methods policy and set it as the default sign-in method.
C.Enable the FIDO2 security key method and set its target to All users, then disable all other authentication methods in the authentication methods policy.
D.Create a Conditional Access policy that requires compliant devices and blocks all other authentication methods.
AnswerC

This is correct because the authentication methods policy in Microsoft Entra ID controls which methods are enabled and who can use them. Enabling FIDO2 for all users and disabling all other methods ensures users can only sign in with a FIDO2 security key. This meets the requirement for passwordless sign-in with only FIDO2.

Why this answer

The authentication methods policy allows administrators to enable or disable specific authentication methods and target them to users or groups. By enabling FIDO2 security keys for all users and disabling all other methods, you ensure that only FIDO2 security keys can be used for sign-in. This satisfies the passwordless requirement with FIDO2-only authentication.

Exam trap

The trap here is assuming Conditional Access can disable authentication methods; it can require methods but cannot globally disable them.

86
MCQmedium

Your organization is currently using Federated Authentication with AD FS. You want to move to Password Hash Synchronization (PHS) but want to test the transition for a small group of users first. Which feature should you use to accomplish this?

A.Conditional Access 'Session' controls
B.Microsoft Entra Connect 'Express Settings'
C.Staged Rollout
D.Active Directory 'Shadow Groups'
AnswerC

Staged Rollout is the specific feature designed for this scenario. It allows an administrator to select specific groups of users who will authenticate against Microsoft Entra ID using PHS or PTA, even if the domain is still configured as federated. This provides a safe environment for validating the cloud authentication flow.

Why this answer

Staged Rollout (now called staged rollout for cloud authentication) allows you to move a pilot group of users from federated authentication to cloud authentication (PHS or PTA) while the rest of the organization continues using AD FS. This enables testing the transition for a small group before a full cutover.

Exam trap

SC-300 often tests the confusion between Staged Rollout and Conditional Access or Entra Connect Express Settings; candidates incorrectly assume Conditional Access can change the authentication method for a subset of users, when only Staged Rollout provides that capability.

How to eliminate wrong answers

Option A is wrong because Conditional Access session controls govern session lifetime and sign-in frequency, not the authentication method used for a subset of users. Option B is wrong because Express Settings in Entra Connect configures the initial synchronization and authentication method for the entire tenant, not a pilot group. Option D is wrong because Active Directory Shadow Groups are used to replicate group membership for filtering, not to stage authentication method changes.

87
MCQmedium

You need to ensure that administrative accounts are protected by requiring hardware-based MFA. Which feature supports this?

A.Identity Protection risk-based policy
B.Conditional Access Authentication Strength
C.Azure AD PIM role settings
D.Intune app protection policies
AnswerB

Authentication Strength policies allow you to enforce specific methods like hardware-backed FIDO2 keys. By applying this to administrative roles via Conditional Access, you ensure that any user accessing privileged resources must present a hardware token, which is a highly secure, phishing-resistant method of identity verification.

Why this answer

Conditional Access Authentication Strength allows you to require specific authentication methods, such as FIDO2 security keys or Windows Hello for Business, which are hardware-based. This ensures administrative accounts use hardware-based MFA.

Exam trap

SC-300 often tests the difference between Authentication Strength and other MFA controls; candidates may think PIM or Identity Protection can enforce hardware MFA, but only Authentication Strength provides that granular method control.

How to eliminate wrong answers

Option A is wrong because Identity Protection risk-based policies adapt to risk but do not enforce hardware-based MFA; they may allow any MFA method. Option C is wrong because PIM role settings control activation requirements like justification or approval, but do not enforce specific authentication methods. Option D is wrong because Intune app protection policies protect app data on mobile devices, not authentication methods for administrative accounts.

88
MCQmedium

You are automating the offboarding process for employees using Lifecycle Workflows. You want to ensure that 30 days after an employee's departure date, their account is disabled and they are removed from all groups. Which workflow template should you use?

A.Onboard pre-hire employee
B.Real-time termination
C.Post-offboarding of an employee
D.Mover workflow
AnswerC

The Post-offboarding template is intended for 'Leaver' scenarios where actions need to happen after the user's official last day. It supports the 30-day offset requirement, enabling the automation of final account deactivation and group cleanup once the designated grace period for the former employee has elapsed.

Why this answer

Lifecycle workflows support 'scheduled' tasks that can be triggered relative to a user's departure date. The 'Post-offboarding' template is specifically designed for these delayed cleanup tasks, allowing organizations to maintain access for a short period (e.g., for data recovery) before finally securing the environment by disabling the account.

Exam trap

Selecting the 'Offboarding' template instead of 'Post-offboarding' is a frequent mistake; 'Offboarding' triggers on the departure date, while 'Post-offboarding' handles delayed tasks occurring after that date.

89
MCQmedium

You are the Identity and Access Administrator for a Microsoft Entra tenant. A line-of-business application runs as an Azure App Service web app and must read secrets from an Azure Key Vault. The security team requires that the app authenticate without storing any credentials and that access be limited to the specific Key Vault. The app already has a system-assigned managed identity enabled. What should you do to grant the app access to the Key Vault?

A.Add the managed identity to a security group and assign the group the Key Vault Contributor role at the subscription scope.
B.Assign the Key Vault Secrets User role to the managed identity's service principal at the Key Vault scope.
C.Store the Key Vault access policy in the App Service configuration and enable the system-assigned identity.
D.Create an app registration, generate a client secret, and configure the App Service with the client ID and secret.
AnswerB

The system-assigned managed identity represents the App Service in Microsoft Entra ID. Granting it the Key Vault Secrets User role on the specific Key Vault resource uses Azure RBAC to authorize secret reads without any stored credential. This satisfies both the credentialless requirement and the least-privilege scope. The app can then use its managed identity endpoint to obtain a token for Key Vault.

Why this answer

A system-assigned managed identity is automatically created and tied to the App Service resource. To let the app read secrets without credentials, you grant that identity the appropriate data-plane role on the target Key Vault. Key Vault Secrets User provides read access to secret contents at the vault scope, meeting the credentialless and least-privilege requirements.

No secret or certificate needs to be stored in the app.

Exam trap

The trap here is assuming that enabling a managed identity automatically grants it access to resources, when in fact you must explicitly assign a role or access policy to the identity on the target resource.

90
MCQeasy

You accidentally delete a cloud-only user account from the Microsoft Entra admin center. You need to restore the user and their associated group memberships. Within how many days must you perform the restoration before the user is permanently deleted?

A.14 days
B.30 days
C.60 days
D.90 days
AnswerB

Microsoft Entra ID retains deleted users in a soft-deleted state for exactly 30 days. During this time, the account can be restored with its original SID, properties, and group memberships intact. After 30 days, the user is permanently removed from the directory and the data becomes unrecoverable.

Why this answer

When you delete a cloud-only user in Microsoft Entra ID (formerly Azure AD), the user is moved to a soft-deleted state and can be restored within 30 days. After 30 days, the user is permanently deleted and cannot be restored. During the 30-day period, you can restore the user along with their group memberships and other properties.

Exam trap

The trap is confusing the retention period with other Microsoft 365 services like SharePoint or Exchange, which have different retention periods (e.g., 93 days for mailboxes).

How to eliminate wrong answers

Option A is wrong because 14 days is not the retention period for deleted users in Entra ID; it's 30 days. Option C is wrong because 60 days is longer than the actual retention period. Option D is wrong because 90 days is the retention period for some other services, but not for Entra ID user restoration.

91
MCQeasy

Your company requires all users to acknowledge a new Remote Work Policy before they can access any cloud applications. You need to ensure that users are prompted to read and accept the policy every 90 days. Which tool should you use to meet this requirement?

A.Microsoft Entra Terms of Use.
B.Privileged Identity Management (PIM).
C.Azure Information Protection (AIP) labels.
D.Access Reviews.
AnswerA

Microsoft Entra Terms of Use allows you to upload a PDF policy and require users to accept it. It supports 'Require re-accept' settings, which can be configured for a 90-day frequency. This ensures that users remain compliant with organizational policies over time by periodically renewing their agreement to the terms.

Why this answer

Microsoft Entra Terms of Use lets you present a policy document to users and require them to accept it before accessing cloud apps. It supports a reacceptance frequency (e.g., every 90 days), which forces users to re-acknowledge the policy at the configured interval.

Exam trap

SC-300 often tests the confusion between Terms of Use (policy acknowledgment) and Access Reviews (access recertification), causing candidates to pick Access Reviews for policy acceptance requirements.

How to eliminate wrong answers

Option B is wrong because PIM manages just-in-time privileged role activation and approvals, not policy acknowledgment. Option C is wrong because AIP labels classify and protect documents, but they do not prompt users to accept a policy at sign-in. Option D is wrong because Access Reviews are for recertifying group memberships, app assignments, and role assignments, not for presenting terms to users.

92
MCQmedium

You are performing an access review for guest users who have been inactive for 30 days. You want to ensure that if a user's access is denied, they are not only removed from the resource but their account is also blocked from signing in for 30 days and then deleted. Which feature should you use?

A.Lifecycle Workflows with a custom 'Leaver' task.
B.Access review 'Advanced settings' for guest user lifecycle.
C.A Conditional Access policy with a block control.
D.A PIM alert that triggers a PowerShell script.
AnswerA

While Lifecycle Workflows can disable and delete accounts, they are primarily triggered by date attributes in the user profile (like employeeHireDate). For removing access based on the 'results' of an access review, the cleanup settings within the access review itself are more direct and appropriate.

Why this answer

Access Reviews in Microsoft Entra ID allow you to automatically remove access or delete the user, but they do not have a built-in 'block sign-in for 30 days then delete' workflow. This specific automation is a core capability of Lifecycle Workflows, which can trigger based on user properties or access review outcomes.

Exam trap

The question describes a complex automated lifecycle process that is not a native configuration option within the Access Review 'Advanced settings' pane.

93
MCQhard

You are implementing Microsoft Entra ID Governance lifecycle workflows to automate the offboarding of employees. The workflow must trigger when a user's employeeLeaveDateTime is set, and then remove the user from all groups, remove all app assignments, and delete the user account after 30 days. You have created the workflow with the trigger 'Employee leave date reached'. Which task should you add to the workflow to remove the user from all groups?

A.Add the 'Remove user from all groups' task.
B.Add the 'Remove access package assignments' task.
C.Add the 'Delete user' task and configure it to run after 30 days.
D.Add the 'Remove user from selected groups' task and select all groups.
AnswerA

Lifecycle workflows include a built-in task called 'Remove user from all groups' that removes the user from all group memberships, including security groups and Microsoft 365 groups. This task directly fulfills the requirement to remove the user from all groups when the workflow runs.

Why this answer

Lifecycle workflows provide a dedicated task to remove a user from all groups, which automatically handles all current group memberships. This is the most efficient and accurate way to meet the requirement. Other tasks either target specific groups, address different resources like access packages, or perform deletion, which is not the same as removing group memberships.

Exam trap

The trap here is selecting a task that removes from selected groups, thinking it can cover all groups, but it requires manual selection and does not automatically include future groups.

94
Multi-Selecthard

You are configuring an access review for a Microsoft Entra ID security group that grants access to a human resources application. The review must automatically remove access for users who do not respond within the review period. Which two settings must you configure? (Choose two.)

Select 2 answers
A.Enable 'Require justification on approval'.
B.Set 'Auto apply results to resource' to enabled.
C.Set 'If reviewers don't respond' to 'Remove access'.
D.Configure the review to recur on a quarterly basis.
E.Add a custom extension to the access review that removes group membership.
AnswersB, C

Enabling 'Auto apply results to resource' ensures that when the access review completes, decisions are automatically applied to the group membership. Without this, reviewers' decisions would not take effect, and users who did not respond would retain access, violating the requirement to remove access for non-responders.

Why this answer

To automatically remove access for users who do not respond, you must set the 'If reviewers don't respond' option to 'Remove access' and enable 'Auto apply results to resource'. The first defines the default action for non-responders, and the second ensures that action is applied to the group membership. Without both, non-responders may retain access or decisions may not be enforced.

Exam trap

The trap here is focusing on recurrence or justification settings, which control timing and reviewer behavior but do not determine the outcome for non-responders.

95
MCQmedium

A user is unable to sign in because they have lost their primary MFA device and do not have a backup method registered. You need to provide them with a short-term, high-assurance method to bypass MFA and register a new device. What should you generate for the user?

A.A Temporary Access Pass (TAP).
B.A new App Password.
C.An SSPR recovery code.
D.A bypass code from the MFA Server.
AnswerA

A Temporary Access Pass is an administrator-generated code that meets the requirements for strong authentication. It can be configured for one-time use or for a specific duration. This allows the user to sign in securely without their usual MFA device, providing a secure path to register new phishing-resistant methods or standard MFA factors like the Microsoft Authenticator app.

Why this answer

A Temporary Access Pass (TAP) is a time-limited, one-time-or-multi-use passcode issued by an admin that satisfies MFA requirements and lets the user register a new authentication method. It is specifically designed for the lost-MFA-device recovery scenario and provides high assurance because it is admin-issued, time-bound, and can be restricted to specific uses.

Exam trap

SC-300 often tests the confusion between legacy MFA bypass mechanisms (App Passwords, MFA Server bypass codes) and the modern Temporary Access Pass — candidates pick the legacy option because it 'sounds' like a bypass, but only TAP is designed for secure MFA recovery in Entra ID.

How to eliminate wrong answers

Option B is wrong because App Passwords are legacy per-app credentials for clients that do not support modern MFA — they do not help a user register a new MFA device and are being deprecated. Option C is wrong because SSPR recovery codes are used to regain access to self-service password reset, not to bypass MFA and register a new authentication method. Option D is wrong because MFA Server bypass codes belong to the on-premises Azure MFA Server product, not to Entra ID cloud authentication, and they bypass MFA without enabling new device registration.

96
MCQhard

You manage a Microsoft Entra ID tenant. A development team uses a user-assigned managed identity for an Azure Function that accesses Azure Key Vault. The team reports that the Function suddenly cannot retrieve secrets. You verify that the managed identity is assigned to the Function and that the Key Vault access policy grants the managed identity GET permission on secrets. What is the most likely cause?

A.The Function's outbound network access is blocked by a firewall, preventing it from reaching the Microsoft Entra token endpoint.
B.The managed identity's client secret expired and was not renewed.
C.The managed identity's service principal was deleted and recreated, changing its object ID.
D.The Function's identity was reassigned to a different user-assigned managed identity that lacks Key Vault permissions.
AnswerD

User-assigned managed identities are separate resources. If the Function's identity assignment was changed to a different managed identity, that new identity would not have the Key Vault access policy granting GET permission. This would cause the Function to lose access. The scenario mentions the managed identity is assigned, but does not specify which one, making this a plausible cause.

Why this answer

The most likely cause is that the Function's assigned managed identity was changed to a different user-assigned managed identity that does not have the required Key Vault access policy. Even if a managed identity is assigned, it must be the correct one with permissions. Other options are less likely because managed identities do not use secrets and network blocks would typically cause broader failures.

Exam trap

The trap here is assuming that any assigned managed identity automatically has the same permissions; user-assigned identities are distinct and require explicit access grants.

97
MCQmedium

You are the Identity and Access Administrator for a company using Microsoft Entra ID. The company has a Microsoft 365 E5 subscription. Employees use Microsoft Outlook on iOS and Android devices. The security team wants to ensure that users cannot save attachments from Outlook mobile to personal cloud storage services, such as iCloud or Google Drive. They also want to prevent users from copying content from Outlook mobile to other apps. You need to configure a policy that meets these requirements with the least administrative effort. What should you do?

A.Create a Conditional Access policy that requires the device to be marked as compliant.
B.Enable Conditional Access App Control in Microsoft Defender for Cloud Apps.
C.Configure an app protection policy in Microsoft Intune for Outlook mobile.
D.Create an Exchange Online transport rule that blocks attachments with specific file types.
AnswerC

App protection policies in Microsoft Intune (part of Microsoft 365 E5) allow you to restrict data transfer between managed apps and unmanaged apps or services. You can block saving attachments to personal cloud storage and prevent copy-paste to unmanaged apps. This directly addresses the requirements with minimal effort by targeting the Outlook app.

Why this answer

App protection policies in Microsoft Intune allow administrators to control how corporate data is accessed and shared within mobile apps like Outlook. By configuring these policies, you can prevent users from saving attachments to personal cloud storage and restrict copy-paste to unmanaged apps. This meets the security requirements without needing to manage device compliance or complex session controls.

Exam trap

The trap here is assuming that device compliance or Conditional Access alone can prevent data sharing within mobile apps, when app-level controls are needed.

98
MCQhard

You manage a Microsoft Entra ID tenant for a company that uses Microsoft Entra ID P1. The company wants to require multi-factor authentication for all users when they access Microsoft 365 apps from outside the corporate network. The corporate network is defined as a named location with trusted IP addresses. You need to create a Conditional Access policy that meets these requirements. What should you do?

A.Create a policy that targets all users and all cloud apps, sets the condition to include the trusted named location, and requires multi-factor authentication.
B.Create a policy that targets all users and all cloud apps, sets the condition to exclude the trusted named location, and requires multi-factor authentication.
C.Create a policy that targets all users and all cloud apps, sets the condition to include any location, and blocks access.
D.Create a policy that targets all users and all cloud apps, sets the condition to include any location, and requires multi-factor authentication.
AnswerB

This is correct because the policy must exclude the trusted corporate network location. By excluding the named location that contains the corporate IP addresses, the policy applies only when users are outside that network. Requiring MFA for all cloud apps and all users meets the requirement.

Why this answer

To require MFA only outside the corporate network, the Conditional Access policy must exclude the trusted named location that represents the corporate IP addresses. The policy should target all users and all cloud apps and require MFA. This ensures that users inside the network are not prompted for MFA, while those outside must use MFA.

Exam trap

The trap here is confusing include and exclude for locations; including a trusted location would apply the policy inside the network, not outside.

99
Multi-Selectmedium

You are configuring workload identity federation for a GitHub Actions workflow that will deploy resources to Azure. You need to ensure that the federated credential is properly configured to allow the workflow to authenticate without secrets. Which two actions should you perform? (Choose two.)

Select 2 answers
A.Assign the app registration's service principal the necessary Azure RBAC role at the target scope.
B.Upload the app registration's certificate to GitHub and reference it in the workflow.
C.Generate a client secret for the app registration and store it as a GitHub secret.
D.Configure the GitHub Actions workflow to use the azure/login action with the client ID, tenant ID, and subscription ID.
E.Create a federated identity credential on the app registration that specifies the GitHub issuer, subject, and audience.
AnswersA, E

After establishing the trust, the service principal of the app registration must have permissions to deploy resources. Assigning an Azure RBAC role, such as Contributor, at the appropriate scope grants the required access. Without this, the federated token would authenticate but authorization would fail. This step is essential for the workflow to perform actions in Azure.

Why this answer

Workload identity federation requires two key configuration steps: creating a federated identity credential on the app registration that trusts GitHub's OIDC issuer, and granting the app's service principal the necessary Azure RBAC role at the target scope. The federated credential defines the trust relationship, while the role assignment provides authorization. Together, they allow the GitHub Actions workflow to authenticate and deploy without secrets.

Exam trap

The trap here is focusing on workflow-side actions like using azure/login or uploading certificates, when the core configuration involves the federated credential on the app registration and the RBAC role assignment.

100
MCQeasy

You are the Identity and Access Administrator for a company that uses Microsoft Entra ID. The company has recently implemented self-service password reset (SSPR). The help desk reports that users who forget their passwords are unable to reset them because they have not registered authentication methods for SSPR. You need to ensure that users are prompted to register their authentication methods the next time they sign in. What should you do?

A.Enable the 'Number matching' setting in the Microsoft Authenticator authentication methods policy.
B.Configure a Conditional Access policy that requires multi-factor authentication for all users.
C.Enable the 'Require users to register when signing in' option in the password reset properties.
D.Create a group policy object that forces users to enroll in SSPR on their Windows devices.
AnswerC

This setting in the Microsoft Entra ID password reset properties forces users to register their authentication methods for SSPR upon their next interactive sign-in. It ensures users complete registration, enabling them to reset passwords later. This directly addresses the help desk issue by proactively prompting registration.

Why this answer

The 'Require users to register when signing in' option in the password reset properties ensures that users are prompted to register their authentication methods for SSPR at next sign-in. This is the most direct way to enforce registration and resolve the help desk issue.

Exam trap

The trap here is confusing MFA registration with SSPR registration, or thinking that Conditional Access or Authenticator settings will enforce SSPR registration.

101
MCQmedium

When migrating an application from on-premises to Azure, you want to use Workload Identity Federation to access Azure resources. Which of the following is required for the on-premises application?

A.An Azure AD Connect synchronization server.
B.A client secret stored in the application environment.
C.An OIDC-compliant token provider.
D.A hardcoded Azure AD Tenant ID in the application code.
AnswerC

Workload Identity Federation works by validating OIDC tokens from a trusted provider. Your application must be able to obtain such a token to exchange it for an Azure AD access token. This is the fundamental requirement for establishing the trust relationship between your on-premises code and Azure resources.

Why this answer

Workload Identity Federation allows an on-premises application to access Azure resources without storing secrets by using an OIDC-compliant token provider. The application presents a token from the external provider, which Azure AD trusts and exchanges for an Azure access token.

Exam trap

SC-300 often tests that workload identity federation requires an OIDC provider and eliminates secrets; candidates may incorrectly think a client secret or Azure AD Connect is needed.

How to eliminate wrong answers

Option A is wrong because Azure AD Connect synchronization is for synchronizing on-premises directory objects to Azure AD, not for workload identity federation. Option B is wrong because a client secret is exactly what workload identity federation aims to eliminate; it is not required. Option D is wrong because hardcoding a tenant ID is not required; the tenant ID is configured in the federated credential setup, but the application does not need it hardcoded.

102
MCQmedium

An organization wants to collaborate with an external partner. You need to allow the partner's employees to use their own Entra ID credentials to sign in to your applications, but you want to block all other external domains. Where should you configure this?

A.The 'External Identities' section under 'Cross-tenant access settings'.
B.The 'User Settings' blade in the Microsoft Entra admin center.
C.A Conditional Access policy targeting 'All Guest Users'.
D.The 'Identity Governance' dashboard under 'Entitlement Management'.
AnswerA

Cross-tenant access settings are specifically designed to manage B2B collaboration and B2B direct connect with other Entra ID tenants. Here, you can define organizational settings that either allow or block specific tenant IDs or domains, ensuring that collaboration is limited only to the intended external partner.

Why this answer

Cross-tenant access settings under External Identities allow you to define which external organizations can collaborate with your tenant. You can configure inbound and outbound access settings, including allowing specific partner domains and blocking all others. This is the correct place to allow only the partner's domain while blocking all other external domains.

Exam trap

SC-300 often tests the distinction between cross-tenant access settings (for domain-specific collaboration) and Conditional Access (for session controls); candidates may incorrectly choose Conditional Access for domain filtering.

How to eliminate wrong answers

Option B is wrong because User Settings control general guest invitation permissions, not domain-specific allow/block lists. Option C is wrong because a Conditional Access policy targeting all guest users can enforce MFA or device compliance but cannot selectively allow only one external domain. Option D is wrong because Entitlement Management in Identity Governance manages access packages and lifecycle, not domain-level collaboration restrictions.

103
MCQeasy

You are the Identity and Access Administrator for a company that uses Microsoft Entra ID. The company wants to enable users to sign in to Microsoft 365 applications without using a password. The security team requires that users use the Microsoft Authenticator app to approve sign-in requests. You need to configure the authentication method policy to meet these requirements. What should you do?

A.Enable the Windows Hello for Business authentication method and configure it for passwordless sign-in.
B.Enable the Microsoft Authenticator authentication method and configure it to allow passwordless sign-in.
C.Enable the Temporary Access Pass authentication method and issue passes to users.
D.Enable the FIDO2 security key authentication method and require users to register a security key.
AnswerB

The Microsoft Authenticator app supports passwordless sign-in through phone sign-in. By enabling the Microsoft Authenticator method and configuring it for passwordless, users can approve sign-in requests without entering a password. This meets the requirement of using the Authenticator app for passwordless authentication. Other methods like FIDO2 or Windows Hello for Business do not use the Authenticator app.

Why this answer

To enable passwordless sign-in with the Microsoft Authenticator app, you must enable the Microsoft Authenticator authentication method in the authentication methods policy and configure it to allow passwordless sign-in. This allows users to register their phone and then approve sign-in requests without a password. Other passwordless methods do not use the Authenticator app and therefore do not meet the specific requirement.

Exam trap

The trap here is assuming any passwordless method satisfies the requirement when the scenario explicitly requires the Microsoft Authenticator app for approval.

104
MCQhard

You administer a Microsoft Entra ID tenant for a financial services firm. The security policy requires that users accessing sensitive financial applications from outside the corporate network must use multi-factor authentication. However, users on the corporate network should not be prompted for MFA. You create a Conditional Access policy with a location condition that includes a named location for the corporate network and marks it as trusted. You need to configure the grant control to enforce MFA for all other locations. Which configuration should you use?

A.Set the policy to target all users and all cloud apps, set the location condition to 'Any location', and include the trusted named location. Then set the grant control to 'Require multi-factor authentication' and enable 'Require one of the selected controls'.
B.Set the policy to target all users and all cloud apps, set the location condition to 'Any location', and include the trusted named location. Then set the grant control to 'Require multi-factor authentication'.
C.Set the policy to target all users and all cloud apps, set the location condition to 'Any location', and exclude the trusted named location. Then set the grant control to 'Require multi-factor authentication' and enable 'Require one of the selected controls'.
D.Set the policy to target all users and all cloud apps, set the location condition to 'Any location', and exclude the trusted named location. Then set the grant control to 'Require multi-factor authentication'.
AnswerD

Excluding the trusted named location from the policy means users on the corporate network are not subject to the policy, while all other locations are. The grant control then enforces MFA for those external locations. This directly satisfies the requirement without affecting internal users, making it the correct configuration.

Why this answer

To enforce MFA only for users outside the corporate network, the Conditional Access policy must exclude the trusted named location. That way, users on the corporate network are not subject to the policy, while all other locations are. The grant control 'Require multi-factor authentication' then applies to those external locations.

Including the trusted location or adding unnecessary controls would either prompt internal users or complicate the policy without benefit.

Exam trap

The trap here is mixing up include and exclude for trusted locations; including a trusted location in a policy applies the policy to it, while excluding it exempts it from the policy.

105
MCQmedium

You are the Identity and Access Administrator for a company that uses Microsoft Entra ID. The company has a policy that all users must use multi-factor authentication. You need to configure the tenant so that users can only use the Microsoft Authenticator app for MFA, and they cannot use SMS or voice call. What should you do?

A.Configure a sign-in frequency policy that requires users to reauthenticate every hour.
B.Configure the authentication methods policy to enable only the Microsoft Authenticator method and disable SMS and voice call methods.
C.Create a Conditional Access policy that requires authentication strength of multi-factor authentication and excludes SMS and voice.
D.Enable security defaults and require MFA for all users.
AnswerB

This is correct because the authentication methods policy allows you to enable or disable specific methods. By enabling only Microsoft Authenticator and disabling SMS and voice call, you restrict users to only the Microsoft Authenticator app for MFA. This meets the requirement.

Why this answer

The authentication methods policy is the correct place to control which MFA methods are available to users. By enabling only Microsoft Authenticator and disabling SMS and voice call, you ensure that users can only use the Microsoft Authenticator app for MFA. This satisfies the requirement to restrict MFA methods.

Exam trap

The trap here is thinking Conditional Access authentication strength can disable methods; it can require methods but not globally disable others.

106
MCQeasy

In Microsoft Entra Entitlement Management, what is the primary purpose of a 'Catalog'?

A.To store backup copies of all user identities in the directory.
B.To group related resources and access packages for delegated management.
C.To provide a public list of all applications available to guest users.
D.To synchronize on-premises Active Directory objects to the cloud.
AnswerB

This is the core function of a catalog. It provides a container where resource owners can manage their own sets of groups, apps, and sites. This allows a 'Catalog Owner' to create access packages for their specific department or project without needing global administrative rights over the entire tenant.

Why this answer

A Catalog in Microsoft Entra Entitlement Management is a container that groups related resources (such as groups, applications, and SharePoint sites) and access packages. It enables delegated management, allowing specified users (Catalog Owners) to manage access packages and resources within that catalog without needing global administrator permissions.

Exam trap

SC-300 often tests the purpose of catalogs in Entitlement Management, and candidates may confuse them with other Entra features like administrative units or groups; remember that catalogs are specifically for grouping resources and access packages for delegated management.

How to eliminate wrong answers

Option A is wrong because Catalogs do not store backup copies of user identities; they are for grouping resources for access management. Option C is wrong because Catalogs are not public lists of applications for guest users; they are internal containers for organizing resources and access packages. Option D is wrong because Catalogs do not synchronize on-premises Active Directory objects; that is the role of Microsoft Entra Connect.

107
MCQhard

An administrator is configuring Privileged Identity Management (PIM) for Azure Resources. They want to ensure that when a user activates the 'Contributor' role on a production subscription, a ticket number is mandatory, and a second administrator must approve the request. Which PIM setting should be modified?

A.Modify the 'Activation' settings in the Microsoft Entra ID roles section of the PIM dashboard.
B.Adjust the 'Role settings' for the Contributor role within the specific Azure subscription in PIM.
C.Update the 'Privileged Access' settings for the group that contains the users requiring the Contributor role.
D.Create a new Conditional Access policy that targets the 'Azure Management' cloud app with MFA requirements.
AnswerB

Role settings within the Azure Resources section of PIM allow administrators to define activation requirements for each role. By enabling 'Require ticket information on activation' and 'Require approval to activate', the admin ensures that every elevation is documented and verified by another authorized individual before access is granted.

Why this answer

In Privileged Identity Management (PIM) for Azure Resources, role settings are configured per role within a specific scope, such as a subscription. To enforce a ticket number and approval for activation of the Contributor role on a production subscription, you must adjust the role settings for that role in that subscription. This allows you to require justification, approval, and other activation requirements.

Exam trap

SC-300 often tests the scope of PIM settings; candidates may confuse Entra ID role settings with Azure resource role settings, leading to wrong answers.

How to eliminate wrong answers

Option A is wrong because modifying activation settings in the Microsoft Entra ID roles section applies to Entra ID roles, not Azure resource roles; the question specifies Azure Resources. Option C is wrong because 'Privileged Access' settings for a group are related to PIM for Groups, not for Azure resource roles. Option D is wrong because Conditional Access policies control access to cloud apps based on conditions, but they do not enforce approval or ticket number requirements for PIM role activation.

108
MCQmedium

You have an application that uses a client secret for authentication. You want to audit when this secret is used. Which log should you examine in Azure Monitor?

A.AuditLogs
B.ServicePrincipalSignInLogs
C.AzureActivity
D.AppServiceHTTPLogs
AnswerB

This log category is designed to capture every authentication request involving an application or service principal. It includes details such as the application name, the IP address, the authentication method (e.g., secret vs. certificate), and the status of the sign-in attempt, which is essential for security auditing.

Why this answer

ServicePrincipalSignInLogs is the correct log because it captures authentication events for service principals, including those using client secrets. When an application authenticates with a client secret, it signs in as a service principal, and this log records the sign-in activity, including the application ID, secret usage, and result. AuditLogs, AzureActivity, and AppServiceHTTPLogs do not specifically track service principal authentication events.

Exam trap

SC-300 often tests the confusion between audit logs and sign-in logs, leading candidates to choose AuditLogs when they need to track authentication events.

How to eliminate wrong answers

Option A is wrong because AuditLogs records directory-level changes (e.g., user creation, role assignments) but not service principal sign-ins. Option C is wrong because AzureActivity logs control-plane operations on Azure resources, not authentication events for service principals. Option D is wrong because AppServiceHTTPLogs captures HTTP traffic to App Service, not authentication attempts using client secrets.

109
MCQeasy

You are managing a Microsoft Entra ID tenant. You need to configure self-service password reset (SSPR) so that users can reset their passwords without contacting the help desk. The security team requires that users must use two authentication methods to reset their password. What should you do?

A.In the Microsoft Entra admin center, navigate to Authentication methods > Policies and require two authentication methods for all users.
B.In the Microsoft Entra admin center, navigate to Password reset > Authentication methods and set 'Number of methods required to reset' to 2.
C.Enable security defaults in the Microsoft Entra admin center and require MFA for all users.
D.Configure a Conditional Access policy that requires multi-factor authentication for all users when they access the password reset portal.
AnswerB

This setting directly controls how many authentication methods a user must provide during SSPR. Setting it to 2 enforces the security requirement that users use two methods. This is the correct place to configure the number of methods required for password reset.

Why this answer

Self-service password reset settings include a dedicated option to require one or two authentication methods. Setting the number of methods required to reset to 2 ensures users must provide two forms of verification. Other settings, such as Conditional Access MFA or authentication methods policies, govern sign-in and method registration, not the reset process itself.

Exam trap

The trap here is confusing the number of authentication methods required for SSPR with the number of methods required for MFA at sign-in, which are configured in different places.

110
Multi-Selectmedium

You want to allow external users to sign in to your Microsoft Entra tenant using their Google accounts. Which TWO steps are required to configure Google federation?

Select 2 answers
A.Create a Google Cloud Platform project and obtain a Client ID and Client Secret.
B.Enable the 'Email one-time passcode for guests' setting in the Entra admin center.
C.Configure Google as an identity provider in the 'External Identities' section of Entra ID.
D.Assign a Microsoft Entra ID P2 license to every Google user who will sign in.
E.Configure a custom domain in Entra ID that matches the @gmail.com suffix.
AnswersA, C

To enable federation, you must register your Entra ID tenant as an application within the Google Developers Console. This process generates the necessary OAuth 2.0 credentials (Client ID and Secret) that Entra ID uses to communicate with Google's identity services and verify the identity of the signing-in user.

Why this answer

Federating with social identity providers like Google improves the onboarding experience for B2B guests by allowing them to use familiar credentials. This reduces the need for them to manage a separate password for your tenant and leverages the security features of their existing identity provider, such as Google's own multi-factor authentication.

Exam trap

Candidates often assume that simply enabling Google federation in Entra ID is enough. They forget that a developer project must first be created in Google Cloud to generate the necessary OAuth credentials.

111
MCQmedium

An organization is moving toward a highly secure environment and wants to implement Certificate-Based Authentication (CBA) as a primary authentication method. What is a required step to enable CBA in Microsoft Entra ID?

A.Install the Entra Connect Health agent.
B.Upload the Root CA certificate to Entra ID.
C.Disable all other authentication methods.
D.Configure a VPN gateway.
AnswerB

Uploading the Root CA certificate is a foundational step for CBA. It establishes the trust anchor that Entra ID uses to validate user certificates. Without this certificate, the cloud service has no way to verify that a user's certificate is legitimate and was issued by the organization's internal PKI.

Why this answer

To enable Certificate-Based Authentication in Microsoft Entra ID, you must upload the root or intermediate CA certificate(s) that issued the user certificates into the Entra ID CBA configuration. Entra ID uses these trusted CA certificates to validate the certificate chain presented by the client during authentication.

Exam trap

SC-300 often tests the required prerequisite for CBA — candidates confuse it with AD FS configuration or think they must disable other methods, when the actual requirement is uploading the trusted root CA certificate.

How to eliminate wrong answers

Option A is wrong because Entra Connect Health monitors sync and AD FS health; it is not required for CBA. Option C is wrong because disabling other authentication methods is not a prerequisite — CBA can coexist with other methods and is enabled per authentication method policy. Option D is wrong because a VPN gateway is a network component unrelated to Entra ID authentication method configuration.

112
Multi-Selecthard

You are configuring workload identity federation for a service principal so that a Kubernetes cluster running outside Azure can obtain Microsoft Entra tokens without storing client secrets. You create the app registration and configure a federated identity credential. Which two values must match between the external identity provider's token and the federated identity credential configuration for token exchange to succeed? (Choose two.)

Select 2 answers
A.The client secret of the app registration.
B.The issuer URL of the external identity provider.
C.The Azure subscription ID where the workload runs.
D.The tenant ID of the external identity provider.
E.The subject identifier that uniquely identifies the external workload.
AnswersB, E

The federated identity credential includes an issuer setting that must exactly match the iss claim in the external token. If the issuer differs, Microsoft Entra rejects the token exchange because it cannot verify that the token came from the trusted provider. This binding prevents tokens from other issuers being used to impersonate the workload.

Why this answer

For a federated identity credential to validate an external token, the token's issuer and subject claims must match the issuer and subject configured on the credential. These two bindings ensure that only the intended workload from the trusted provider can exchange its token for a Microsoft Entra access token, eliminating the need for client secrets.

Exam trap

The trap here is assuming that a client secret or subscription ID participates in the trust, when federated identity credentials validate only the issuer and subject claims from the external token.

113
MCQeasy

You are the identity administrator for a Microsoft Entra tenant. A new application is being developed that will run as an Azure Function and needs to access an Azure Storage account. The development team wants to avoid managing credentials. You need to configure the Function to authenticate to Azure Storage without storing any secrets. What should you do?

A.Assign the Storage Account Contributor role to the Azure Function's app registration and use the application ID as a credential.
B.Create a service principal and store its client secret in the Azure Function's application settings.
C.Enable a system-assigned managed identity on the Azure Function and grant it the Storage Blob Data Contributor role on the storage account.
D.Generate a shared access signature (SAS) token for the storage account and embed it in the Function code.
AnswerC

A system-assigned managed identity is created in Microsoft Entra ID and tied to the Azure Function's lifecycle. The Function can request tokens for Azure Storage without any credentials in code. Assigning the appropriate RBAC role grants least-privilege access. This is the recommended approach for Azure services to access other Azure resources securely, eliminating secret management overhead.

Why this answer

A system-assigned managed identity is automatically managed by Azure and requires no secrets. The Function can authenticate to Azure Storage using its identity, and RBAC controls access. This is the most secure and operationally simple solution for Azure-to-Azure authentication.

The other options involve secrets or overly broad permissions.

Exam trap

The trap here is confusing a managed identity with a service principal that still requires a secret; a managed identity is a special type of service principal that Azure manages without credentials.

114
Multi-Selecthard

You are implementing Entra ID Password Protection for your on-premises Active Directory Domain Services (AD DS) environment. Which TWO components must be installed on your on-premises servers?

Select 2 answers
A.Microsoft Entra ID Password Protection Proxy
B.Microsoft Entra Connect Sync Engine
C.Microsoft Entra ID Password Protection DC Agent
D.Microsoft Entra Application Proxy Connector
E.Microsoft Entra Connect Health Agent
AnswersA, C

The Proxy service acts as an intermediary between the on-premises Domain Controllers and the Microsoft Entra ID cloud service. It receives password validation requests from the DC agents and forwards them to the cloud to check against the global and custom banned password lists before returning the result.

Why this answer

Option A, the Microsoft Entra ID Password Protection Proxy, is correct because it must be installed on an on-premises server to relay password policy requests from the DC Agents to the Entra ID service in the cloud, enabling the domain controllers to check passwords against Microsoft's global banned-password list. Option C, the Microsoft Entra ID Password Protection DC Agent, is correct because it must be installed on each domain controller (or read-only domain controller) to intercept password-change events and enforce the custom banned password lists and audit mode settings locally. Option B, the Entra Connect Sync Engine, is not required for Password Protection since it handles identity synchronization, not password policy enforcement.

Option D, the Entra Application Proxy Connector, is used for publishing on-premises web applications, not for password protection. Option E, the Entra Connect Health Agent, provides monitoring and health telemetry for identity infrastructure and is unrelated to password filter enforcement.

Exam trap

SC-300 often tests whether candidates confuse the Password Protection Proxy and DC Agent with Entra Connect or Application Proxy components — only the Proxy and DC Agent are required for on-premises password protection.

115
MCQmedium

You are configuring Workload Identity Federation for a GitHub Actions workflow that needs to access an Azure resource. You have created an app registration and added a federated identity credential. The workflow is failing to authenticate. You need to ensure the federated identity credential is correctly configured. Which attribute must match the GitHub Actions workflow's subject claim?

A.The repository name and branch or environment.
B.The GitHub Actions runner's IP address range and the repository's visibility.
C.The GitHub organization's name and the workflow file name.
D.The Azure subscription ID and resource group name.
AnswerA

For GitHub Actions, the subject claim in the federated identity credential must match the format 'repo:<organization>/<repository>:ref:refs/heads/<branch>' for a branch or 'repo:<organization>/<repository>:environment:<environment>' for an environment. This ensures that only workflows from the specified repository and branch/environment can authenticate. The repository name and branch or environment are the key components that must be correctly configured to match the token's subject.

Why this answer

When configuring a federated identity credential for GitHub Actions, the subject must match the 'sub' claim in the OIDC token issued by GitHub. That claim is formatted as 'repo:<org>/<repo>:ref:refs/heads/<branch>' for branches or 'repo:<org>/<repo>:environment:<env>' for environments. Therefore, the repository name and branch or environment are the critical attributes.

The other options include elements not present in the subject claim, so they would not enable successful authentication.

Exam trap

The trap here is assuming that the workflow file name or Azure resource identifiers are part of the subject claim, when only the repository and branch/environment are included.

116
MCQhard

You are managing a Microsoft Entra ID tenant. The security team requires that all administrative roles must use phishing-resistant authentication methods. You need to configure an authentication methods policy that enforces this requirement for administrators only, while allowing other users to use multi-factor authentication with the Microsoft Authenticator app. What should you do?

A.Create a Conditional Access policy that targets the administrative roles and requires authentication strength 'Phishing-resistant MFA'.
B.Create an authentication method policy that targets administrators and enables only certificate-based authentication.
C.Configure the authentication methods policy to enable only FIDO2 security keys and Windows Hello for Business for all users.
D.Assign a Microsoft Entra ID Premium P2 license to all administrators and enable security defaults.
AnswerA

Authentication strength in Conditional Access allows you to require specific authentication methods, such as phishing-resistant MFA, for targeted users or roles. This policy can be scoped to directory roles, ensuring administrators use methods like FIDO2 or Windows Hello for Business, while other users are unaffected. It directly meets the requirement without altering global authentication methods policy.

Why this answer

Conditional Access authentication strength allows you to require phishing-resistant MFA for specific users or roles, such as administrators. This meets the requirement to enforce strong authentication for admins while allowing other users to continue using the Microsoft Authenticator app. It provides granular control without affecting all users.

Exam trap

The trap here is confusing authentication methods policy with Conditional Access authentication strength; the former configures methods globally, while the latter enforces specific strengths per policy.

117
MCQmedium

You manage entitlement management in Microsoft Entra ID. A partner company's users need to request access to an access package that grants access to a SharePoint site. The partner has its own Microsoft Entra tenant, and you want to ensure that only users from that specific partner tenant can request the package. What should you configure?

A.Add the partner users as members of a security group and assign the group to the access package.
B.Enable self-service sign-up for the partner domain in the external collaboration settings.
C.Create a connected organization for the partner tenant and add it to the access package's policy.
D.Configure a cross-tenant synchronization job to provision partner users into your tenant.
AnswerC

A connected organization represents an external directory, such as a partner's Microsoft Entra tenant, and scopes external users who can request access packages. By adding it to the access package policy, you restrict requests to users from that tenant. This is the standard way to enable B2B collaboration for entitlement management while limiting which external organizations can request access.

Why this answer

Connected organizations are the entitlement management feature that defines external directories whose users can request access packages. By creating a connected organization for the partner's Microsoft Entra tenant and referencing it in the access package policy, you ensure that only users from that tenant can submit requests. This provides a controlled B2B collaboration boundary without provisioning those users as members in your own tenant.

Exam trap

The trap here is assuming that any external collaboration feature, such as cross-tenant synchronization or self-service sign-up, can restrict access package requests, when only a connected organization scopes the requesters.

118
MCQeasy

A user reports being unable to sign in to a SaaS application. You check the Microsoft Entra sign-in logs and see a 'Conditional Access policy failure' status. What is the first step you should take to troubleshoot?

A.Examine the 'Conditional Access' tab in the sign-in log entry for the specific failure.
B.Reset the user's password.
C.Ask the user to clear their browser cache.
D.Disable all Conditional Access policies for the tenant.
AnswerA

The Conditional Access tab within the Entra sign-in logs lists every policy applied and whether it resulted in a success, failure, or was not applied. This is the most direct way to identify exactly which policy caused the block and why it occurred for that specific user.

Why this answer

The sign-in log entry for a failed Conditional Access evaluation contains a dedicated 'Conditional Access' tab that lists every policy evaluated, whether it applied, and if it did, which grant control or condition caused the failure (e.g., MFA required, device not compliant, location blocked). Inspecting that tab is the direct, first-step diagnostic.

Exam trap

SC-300 often tests the instinct to jump to credential or client-side fixes — candidates pick password reset or cache clearing because those are common helpdesk steps, but the log explicitly points to Conditional Access, so the CA tab is the correct first move.

How to eliminate wrong answers

Option B is wrong because a Conditional Access policy failure is not a credential problem — resetting the password will not change which CA policies apply and will not resolve the block. Option C is wrong because browser cache issues manifest as token or session errors, not as a CA policy failure status in the sign-in log. Option D is wrong because disabling all CA policies tenant-wide is a security-destructive action that violates least privilege and change management; it is never a first troubleshooting step and would mask the real issue.

119
MCQmedium

You are configuring a Lifecycle Workflow in Microsoft Entra ID Governance to automate the offboarding of employees. The workflow must trigger when a user's employeeLeaveDateTime attribute is set and must run a task to remove all group memberships. Which trigger condition should you use?

A.Employee leave date is set
B.User is created
C.Employee hire date is set
D.User account is enabled
AnswerA

The 'Employee leave date is set' trigger condition activates when the employeeLeaveDateTime attribute is populated. This is the correct trigger for offboarding scenarios based on a leave date, as it directly monitors that attribute. Other triggers do not key off this attribute, so they would not fire when the leave date is set.

Why this answer

Lifecycle Workflows in Microsoft Entra ID Governance provide trigger conditions based on user attributes. The 'Employee leave date is set' trigger specifically monitors the employeeLeaveDateTime attribute and fires when that attribute is populated. This aligns with the offboarding scenario where the workflow must start when the leave date is set.

Other triggers are for different lifecycle events and would not activate in this case.

Exam trap

The trap here is confusing the hire date trigger with the leave date trigger; they monitor different attributes and serve opposite lifecycle events.

120
MCQmedium

You administer a Microsoft Entra tenant. A third-party SaaS application requires an app-only permission to Microsoft Graph to read directory data for users in your tenant. The vendor's administrator will manage the application registration and provide you with a consent URL. You must ensure that an administrator in your tenant can review and approve the request without granting more permissions than requested. What should you instruct the vendor to configure?

A.Instruct the vendor to assign the Global Administrator role to their application's service principal in your tenant so they can grant the required permission.
B.Request that the vendor provide you with the application's client secret and then manually configure the required Microsoft Graph permission in your tenant's enterprise applications blade.
C.Configure the application registration as multi-tenant and ask the vendor to send you the admin consent endpoint URL with the required permission in the scope parameter.
D.Ask the vendor to create a service principal in your tenant using the New-MgServicePrincipal cmdlet with the AppId of their application.
AnswerC

A multi-tenant app registration enables the vendor's application to be consented in your tenant. The admin consent endpoint URL includes the requested Microsoft Graph permission, so your administrator can review and approve exactly what is needed. This provides a controlled consent process without requiring the vendor to have access to your tenant.

Why this answer

For a third-party multi-tenant application, the standard method to request admin consent is to use the admin consent endpoint URL. The vendor configures the required Microsoft Graph permission in their app registration, and your administrator reviews and consents via that URL. This ensures that only the requested permissions are granted and maintains a clear consent workflow.

Exam trap

The trap here is assuming that creating a service principal or sharing a secret grants permissions, when in fact permissions require explicit consent through the admin consent endpoint.

121
MCQmedium

Your organization wants to prevent users from using legacy authentication protocols, such as POP3 and IMAP4, to access Microsoft 365 services. You need to implement a solution that blocks these protocols while allowing modern authentication. What is the most effective way to achieve this using Conditional Access?

A.Create a Conditional Access policy, select All Cloud Apps, and under Client Apps, select only Legacy Authentication clients with a Block grant.
B.Disable the POP3 and IMAP4 services at the tenant level within the Microsoft 365 Admin Center for every individual user mailbox.
C.Enable Security Defaults in the Microsoft Entra admin center to automatically manage all authentication and security settings for the tenant.
D.Update the default Authentication Policy in Exchange Online to set the AllowBasicAuth setting to false for all available mail protocols.
AnswerA

Selecting 'Block' for client apps like Exchange ActiveSync and other legacy clients ensures that any connection attempt using basic authentication is immediately rejected. This setting is globally applied to all users, providing a comprehensive safeguard. It prevents attackers from using compromised credentials on systems that do not support modern MFA prompts or identity-based signals.

Why this answer

A Conditional Access policy that targets All Cloud Apps and selects the 'Legacy Authentication clients' client app condition with a Block grant is the canonical Microsoft-recommended way to block legacy protocols like POP3, IMAP4, SMTP AUTH, and older Office clients. Because legacy clients do not support modern authentication, they cannot satisfy MFA or other CA controls, so blocking them at the CA layer is the most effective and centralized approach.

Exam trap

SC-300 often tests whether candidates confuse tenant-wide Security Defaults with Conditional Access, or mistakenly believe that disabling POP3/IMAP4 per mailbox is equivalent to blocking all legacy authentication clients.

How to eliminate wrong answers

Option B is wrong because disabling POP3/IMAP4 per mailbox in the Microsoft 365 Admin Center is a manual, per-user action that does not scale and does not address other legacy protocols such as SMTP AUTH or older Office clients. Option C is wrong because Security Defaults is a baseline preset that enforces MFA for all users but does not specifically block legacy authentication clients and cannot coexist with custom Conditional Access policies. Option D is wrong because the Exchange Online Authentication Policy's AllowBasicAuth setting is a per-protocol toggle that is being deprecated and does not cover non-Exchange legacy clients or provide the centralized enforcement that Conditional Access does.

122
Multi-Selectmedium

You are configuring Workload Identity Federation for a GitHub Actions workflow to deploy resources to Azure. Which TWO components are required to establish the trust relationship between GitHub and Microsoft Entra ID?

Select 2 answers
A.A client secret with a 24-month expiration.
B.A Federated Identity Credential.
C.A Microsoft Entra ID P2 license for every developer.
D.A User-assigned Managed Identity or App Registration.
E.An Azure Key Vault Access Policy.
AnswersB, D

This component defines the external identity provider and the specific criteria, such as the GitHub repository or environment, that Microsoft Entra ID should trust. It links the external entity to the internal identity, allowing the exchange of OIDC tokens for Azure access tokens without using secrets.

Why this answer

Workload Identity Federation allows you to trust an external identity provider like GitHub. To set this up, you must have an identity in Entra ID (Application or Managed Identity) and a Federated Identity Credential. This credential defines the trust by specifying the issuer and subject identifiers provided by the GitHub OIDC token.

Exam trap

Many candidates try to use a Client Secret for GitHub Actions, failing to realize that Workload Identity Federation is specifically designed to eliminate secrets by using federated credentials.

123
MCQmedium

A company wants to implement a passwordless strategy for its administrative accounts. The administrators work from shared workstations that do not have built-in biometric hardware. Which authentication method should you recommend to provide the highest level of security?

A.Windows Hello for Business
B.Microsoft Authenticator (Phone Sign-in)
C.FIDO2 security keys
D.SMS-based authentication
AnswerC

FIDO2 security keys are external hardware devices that provide phishing-resistant, passwordless authentication. Since they are portable and do not require specific biometric sensors on the workstation itself, they are the perfect fit for administrators moving between shared computers who require the highest level of identity protection.

Why this answer

FIDO2 security keys are the most secure passwordless method for shared workstations because they are hardware-backed and phishing-resistant. Unlike Windows Hello for Business, which is tied to a specific device's TPM, FIDO2 keys are portable, making them ideal for administrators moving between different shared machines that lack biometric hardware.

Exam trap

The exam often tests the distinction between Windows Hello for Business and FIDO2. Remember: Windows Hello is device-bound (tied to the hardware it was set up on), while FIDO2 keys are portable and provide the highest level of phishing resistance for shared environments.

124
MCQmedium

Your organization needs to invite 500 external consultants from a partner firm to collaborate on a temporary project in Microsoft Entra ID. You have a CSV file containing their email addresses and redirection URLs. You must complete this task with the least amount of administrative effort. Which feature should you use to achieve this goal?

A.The New-MgUser PowerShell cmdlet with a ForEach loop.
B.The Bulk invite users operation in the Microsoft Entra admin center.
C.The Microsoft Entra Connect sync tool with a custom connector.
D.The Bulk create users operation in the Microsoft Entra admin center.
AnswerB

This native feature is the most efficient way to process a large list of external users. It provides a downloadable template, validates the input data, and handles the invitation workflow for up to 2,000 users per CSV file, making it the standard choice for bulk B2B collaboration onboarding without custom scripting.

Why this answer

The bulk invite feature in the Microsoft Entra admin center allows administrators to upload a formatted CSV file to send invitations to hundreds of users simultaneously. This method is specifically designed for high-volume onboarding of guest users, significantly reducing the manual labor required compared to individual invitations. It ensures consistency in the invitation process and handles the generation of redemption links automatically for the entire batch.

Exam trap

Candidates often confuse bulk invitation with bulk user creation. Bulk user creation is for internal members, whereas bulk invitation is for external guest users who already have their own credentials elsewhere.

125
Multi-Selecthard

You are designing an access review program in Microsoft Entra ID. Which TWO factors must you consider to ensure the review remains effective and compliant? Select exactly two.

Select 2 answers
A.The frequency of the review cycle
B.The maximum number of users per review
C.The designation of appropriate reviewers
D.The use of self-service groups
E.The integration with external identity providers
AnswersA, C

Determining the frequency, such as quarterly or annually, is critical for compliance. Too frequent reviews cause administrative fatigue and poor decision quality, while infrequent reviews leave excessive permissions active for too long, increasing the window of risk for unauthorized access or compromised accounts.

Why this answer

Effective access reviews require defining both the scope of identities and the specific criteria for decision-making. By choosing the correct reviewers—usually resource owners or direct managers—and setting a clear duration, you ensure that decisions are informed and timely. This practice is essential for maintaining the principle of least privilege, as it forces periodic re-validation of permissions that often suffer from 'privilege creep' over time in large enterprise environments.

Exam trap

Candidates often select options related to automated remediation or technical settings, forgetting that the core of an effective review is defining who performs the review and how often it happens.

126
MCQeasy

You are the Identity and Access Administrator for a company that uses Microsoft Entra ID. The company has a policy that users must not be able to sign in to Microsoft 365 apps from countries where the company does not operate. You need to configure a Conditional Access policy to block access from those countries. What should you use in the policy?

A.Identity Protection risk policies
B.Terms of use
C.Named locations
D.Authentication methods policy
AnswerC

Named locations in Conditional Access allow you to define specific countries or IP ranges. You can then create a policy that blocks access from those locations. This directly meets the requirement to block access from countries where the company does not operate by defining those countries as named locations and setting the policy to block.

Why this answer

To block access from specific countries, you define those countries as named locations in Microsoft Entra ID. Then, in a Conditional Access policy, you configure the conditions to include those named locations and set the access control to block. This effectively prevents sign-ins from those locations.

Other features like terms of use, authentication methods policies, and Identity Protection risk policies do not provide geographic-based access control.

Exam trap

The trap here is assuming that terms of use or risk policies can enforce geographic restrictions, but only named locations in Conditional Access provide that capability.

127
MCQhard

Refer to the exhibit. You are configuring Workload Identity Federation for a GitHub Actions workflow. What is the purpose of the 'subject' field in this configuration?

A.It specifies the display name of the service principal in the Entra ID tenant.
B.It defines the URL of the GitHub repository where the workflow is hosted.
C.It identifies the specific external workload that is authorized to use the federated identity.
D.It lists the Azure resources that the GitHub workflow is permitted to manage.
AnswerC

The subject claim is the unique identifier sent by GitHub Actions that Entra ID checks against the federated identity credential. In this case, it ensures that only the 'main' branch of the specified repository can successfully authenticate, preventing other branches or repositories from using the identity.

Why this answer

The 'subject' field in a federated identity credential defines the subject claim from the external token that is allowed to authenticate. For GitHub Actions, it typically identifies the specific repository, branch, or environment, ensuring only that workload can use the federated identity.

Exam trap

SC-300 often tests the purpose of the subject claim in federated identity; candidates may confuse it with the service principal name or the repository URL, but it is the unique identifier of the external workload.

How to eliminate wrong answers

Option A is wrong because the display name is a property of the service principal, not the subject claim. Option B is wrong because the URL of the repository is not directly the subject; the subject is a string like 'repo:owner/repo:ref:refs/heads/main'. Option D is wrong because the subject does not list Azure resources; that is handled by Azure RBAC assignments.

128
MCQmedium

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. The security team requires that when users sign in from an unmanaged device, they must be prompted to provide a second authentication factor. However, users must not be prompted for MFA when they sign in from a compliant device. The tenant has Microsoft Entra ID P1 licenses. You need to configure a Conditional Access policy that enforces MFA only when the device is not compliant. What should you do?

A.Create a Conditional Access policy with the Grant control 'Require multi-factor authentication' and set the condition 'Device state' to 'Include: All device states' and 'Exclude: Device Hybrid Azure AD joined'.
B.Create a Conditional Access policy with the Grant control 'Require multi-factor authentication' and set the condition 'Client apps' to 'Include: Browser' and 'Exclude: Mobile apps and desktop clients'.
C.Create a Conditional Access policy with the Grant control 'Require multi-factor authentication' and set the condition 'Device platforms' to 'Include: All platforms' and 'Exclude: Windows'.
D.Create a Conditional Access policy with the Grant control 'Require multi-factor authentication' and set the condition 'Device state' to 'Include: All device states' and 'Exclude: Device marked as compliant'.
AnswerD

This policy applies to all device states but excludes devices that Intune marks as compliant. Compliant devices are identified by the device compliance state in Microsoft Entra ID, so excluding them ensures MFA is enforced only on unmanaged or noncompliant devices. This matches the requirement exactly.

Why this answer

The correct configuration uses the device compliance state as an exclusion, so MFA is required for all sign-ins except those from devices Intune has marked compliant. This directly satisfies the need to prompt for a second factor only on unmanaged or noncompliant devices. Conditions based on join type, client app, or platform do not reliably identify compliance and would either over- or under-enforce MFA.

Exam trap

The trap here is confusing device join state (hybrid Azure AD joined) with device compliance state, which are separate signals in Conditional Access.

129
MCQhard

Refer to the exhibit. A user reports they cannot access an app. The error code 50072 appears. What is the most likely cause?

A.The user's account is locked.
B.The user is not registered for MFA.
C.The user's password has expired.
D.The user is on an unauthorized network.
AnswerB

Code 50072 signals that the user has not completed the required MFA registration process. Since the Conditional Access policy mandates MFA for access to the resource, the system denies the request until the user successfully registers a valid secondary factor as required by the organization's policy.

Why this answer

Error code 50072 indicates that the user is required to enroll for MFA, but has not yet completed the registration process. This occurs when a Conditional Access policy requires MFA, but the user has not yet set up their authentication methods.

Exam trap

Candidates often confuse 50072 (MFA enrollment required) with 50076 (MFA is required, but the user has already enrolled and just needs to perform the challenge).

130
MCQmedium

You are assigning a Microsoft 365 Business Premium license to a new user. The assignment fails with an error stating that the usage location is not set. Why is the 'Usage Location' attribute mandatory for license assignment?

A.It determines the physical data center where the user's mailbox will be hosted.
B.Microsoft uses it to comply with local regulations and verify service availability in the user's region.
C.It is used to automatically set the user's time zone and language in Outlook.
D.It is required for the user to be able to register for Multi-Factor Authentication.
AnswerB

Microsoft is legally required to ensure that the services provided in a specific license are authorized for use in the user's country. The 'Usage Location' attribute allows Entra ID to validate that the assigned services meet regional compliance standards and tax requirements before the license is activated.

Why this answer

The 'Usage Location' attribute is not just a metadata field; it has legal and functional implications for Microsoft services. Microsoft must comply with local laws and regulations regarding data residency and service availability, which varies by country. Setting this correctly is a prerequisite for any license-based resource provisioning in Entra ID.

Exam trap

Candidates often think 'Usage Location' is for internal reporting or analytics. They fail to understand it is a mandatory legal requirement for compliance with regional service availability and data residency laws.

131
MCQmedium

You are setting up an Access Review for a security group that contains both internal employees and guest users. You want to ensure that if a reviewer does not respond within the 14-day window, the guest users' access is automatically removed, but internal users keep their access until a manual decision is made. How should you configure the 'Upon non-response' settings?

A.Set 'Upon non-response' to 'Remove access' for the entire review.
B.Create two separate access reviews: one for internal users and one for guests.
C.Enable 'Decision helpers' and set 'Take recommendations'.
D.Set 'Upon non-response' to 'Approve access' and use a Logic App.
AnswerB

By creating a review specifically scoped to 'Guest users only', you can set the 'Upon non-response' action to 'Remove access' without impacting internal employees. A second review for internal users can be configured with 'No change' for non-responses, ensuring that business continuity is maintained for the internal staff.

Why this answer

Access reviews apply 'Upon non-response' settings uniformly to every identity in the review, so you cannot have guests auto-removed while internal users retain access in a single review. The correct approach is to split the population into two separate access reviews — one scoped to guest users with 'Remove access' on non-response, and one scoped to internal users with 'No change' or 'Approve access' on non-response.

Exam trap

SC-300 often tests the assumption that 'Upon non-response' can be configured per user type within a single review — it cannot, so the exam expects you to recognize that separate reviews are required.

How to eliminate wrong answers

Option A is wrong because setting 'Remove access' for the entire review would also strip internal employees who fail to respond, which contradicts the requirement. Option C is wrong because decision helpers only surface recommendations to reviewers; they do not change what happens on non-response. Option D is wrong because 'Approve access' on non-response would keep guests, not remove them, and a Logic App cannot override the built-in non-response behaviour of the review itself.

132
MCQhard

You manage a Microsoft Entra ID tenant. A third-party SaaS application is registered in your tenant as an enterprise application. The SaaS provider requires access to your Microsoft Graph data using a service principal. You need to ensure that the service principal can only access Microsoft Graph and cannot access any other Azure resources. What should you do?

A.Assign the service principal the Microsoft Graph API permission and remove all other API permissions.
B.Configure the enterprise application to require assignment, and assign only the specific users or groups that need access.
C.Ensure the service principal has no Azure RBAC role assignments and only has the required Microsoft Graph API permissions.
D.Enable the service principal to use managed identity and disable secret-based authentication.
AnswerC

Azure RBAC role assignments grant access to Azure resources like subscriptions, resource groups, and individual resources. Microsoft Graph API permissions grant access to Microsoft Graph data. To restrict the service principal to only Microsoft Graph, you must verify it has no Azure RBAC roles and only the necessary Graph permissions. This ensures it cannot access other Azure resources.

Why this answer

To restrict a service principal to only Microsoft Graph, you must ensure it has no Azure RBAC role assignments, which would grant access to Azure resources. Additionally, it should have only the required Microsoft Graph API permissions. This combination ensures the service principal cannot access other Azure resources, aligning with least privilege.

Exam trap

The trap here is focusing only on API permissions and forgetting that Azure RBAC roles can also grant access to Azure resources.

133
Multi-Selecthard

You are configuring Workload Identity Federation for a CI/CD pipeline running on an external CI/CD provider. Which THREE pieces of information are required to create the federated identity credential? (Choose three)

Select 3 answers
A.The Issuer URL of the external OIDC provider.
B.The Client Secret of the service principal.
C.The Subject identifier for the workload.
D.The Audience for the token exchange.
E.The Tenant ID of the external provider.
AnswersA, C, D

The issuer URL is required so Azure AD can fetch the OIDC configuration and public keys from the external provider. This allows Azure AD to verify that the incoming token was signed by the trusted external entity, forming the foundation of the identity federation trust relationship.

Why this answer

To create a federated identity credential for Workload Identity Federation, you must supply the Issuer URL of the external OIDC provider (A), because Microsoft Entra ID uses this URL to fetch the provider's OpenID Connect metadata and validate the token's signing keys. You must also provide the Subject identifier (C), which is the exact 'sub' claim value that the incoming token must match to bind the external workload to the service principal or managed identity. Finally, you must specify the Audience (D), the expected 'aud' claim value, so Entra ID only accepts tokens minted for the intended resource.

The Client Secret (B) is not used, since federation replaces client secrets with token-based trust, and the Tenant ID of the external provider (E) is not a required parameter because the issuer URL already identifies the external authority.

Exam trap

The trap is assuming a client secret is still needed for the service principal; candidates who have configured app registrations with secrets often pick that option, not realizing federation is secretless by design.

134
MCQmedium

You are configuring an Access Review for a group that provides access to sensitive financial data. To comply with internal audits, you must ensure that the review occurs every quarter and that the 'User's manager' is always the primary reviewer. What should you do if some users in the group do not have a manager defined in Microsoft Entra ID?

A.The review will automatically skip users without a manager.
B.Specify a fallback reviewer in the Access Review settings.
C.The Global Administrator will receive all reviews for users without managers.
D.Users without a manager will be prompted to review their own access.
AnswerB

When choosing 'Manager' as the reviewer, the configuration interface allows you to select a fallback reviewer. This person or group will receive the review tasks for any users who do not have a manager assigned in their profile, ensuring that every member of the group is reviewed.

Why this answer

When configuring an Access Review in Microsoft Entra ID, if a reviewer is set to 'User's manager' and some users have no manager attribute populated, the review cannot be assigned to anyone for those users. Microsoft Entra ID Governance provides a 'fallback reviewer' setting specifically for this scenario — you specify a user or group (e.g., a compliance officer or group owner) who will review access for any user whose manager is missing. This ensures the quarterly audit requirement is met without gaps.

Exam trap

SC-300 often tests the misconception that Access Reviews automatically handle missing managers by skipping users or escalating to a Global Admin — candidates must remember that a fallback reviewer must be explicitly configured.

How to eliminate wrong answers

Option A is wrong because Access Reviews do not silently skip users lacking a manager — the review would be left unassigned or fail to generate decisions for those users, creating an audit gap. Option C is wrong because Global Administrators are not automatically assigned as reviewers for orphaned users; reviewer assignment is explicit and does not default to the tenant's highest-privilege role. Option D is wrong because self-review is a separate reviewer option ('Members review their own access') and is not automatically triggered for users without managers — it must be explicitly configured and would violate the requirement that the manager is always the primary reviewer.

135
MCQmedium

You are auditing sign-in logs and see many 'Interrupted' sign-ins. What does this typically indicate?

A.The user is being prompted to complete a required action like MFA registration.
B.The user entered an incorrect password multiple times.
C.The user's device is not compliant with company policy.
D.The service principal has an expired client secret.
AnswerA

The 'Interrupted' status specifically signifies that the sign-in flow was paused by a policy that requires user interaction. This is commonly seen when users are forced to register for MFA or accept the organization's terms of use before they are allowed to proceed to the target application.

Why this answer

An 'Interrupted' sign-in status in Entra ID occurs when the authentication process is paused because the user is required to complete an additional action, such as MFA registration, password reset, or terms of use acceptance. It is not an error, but a state where the identity provider is waiting for the user to fulfill a policy mandate before granting access to the requested application, which is crucial for compliant identity management.

Exam trap

Candidates often mistake 'Interrupted' for a failed authentication or a security threat, failing to recognize it as a standard interactive state where the user must complete a pending identity requirement.

136
MCQeasy

You are an identity administrator for a Microsoft Entra tenant. A developer has registered an application named 'InventoryApp' that needs to access Microsoft Graph to read user profiles. The developer wants to avoid using client secrets and instead use a certificate for authentication. You need to configure the app registration to allow certificate-based authentication. What should you do?

A.Assign the 'Application Administrator' role to the app's service principal and enable 'Assignment required' in the enterprise application properties.
B.Add a federated identity credential to the app registration, specifying the issuer and subject of the certificate.
C.Upload the public key of the certificate to the app registration's 'Certificates & secrets' blade under 'Certificates'.
D.Generate a new client secret and store it in Azure Key Vault, then configure the app to retrieve it at runtime.
AnswerC

To enable certificate-based authentication for an app registration, you upload the public key (.cer, .pem, or .crt) to the 'Certificates & secrets' section. The application then uses the corresponding private key to sign the client assertion during token requests. This is the standard method for configuring certificate credentials in Microsoft Entra ID and avoids the need for client secrets.

Why this answer

Certificate-based authentication for an app registration is configured by uploading the public key of the certificate to the app registration's certificates. The application then uses the private key to sign assertions when requesting tokens from Microsoft Entra ID. This method is more secure than client secrets and is the recommended approach for production workloads.

The other options either do not configure certificate authentication or are meant for different scenarios.

Exam trap

The trap here is confusing federated identity credentials with certificate credentials, when federated credentials are for external identity providers and certificate uploads are for direct app authentication.

137
MCQmedium

Your organization uses Azure Kubernetes Service (AKS). You need to allow a pod to access an Azure Key Vault secret without using Kubernetes secrets or managed identity credentials stored in the pod configuration. What should you implement?

A.Enable Azure AD pod-managed identity for the cluster.
B.Assign a system-assigned managed identity to the AKS node pool.
C.Configure Azure AD Workload Identity and create a federated identity credential.
D.Install the Key Vault CSI driver and store the secret as a K8s secret.
AnswerC

Workload Identity enables Kubernetes service accounts to assume an Azure AD identity. By creating a federated credential linking the Kubernetes namespace and service account to the Azure managed identity, you provide granular, secure, and token-based access to Azure resources without requiring any permanent secrets or hard-coded credentials.

Why this answer

Azure AD Workload Identity is the current, supported mechanism for letting an AKS pod authenticate to Azure services like Key Vault without storing credentials. It uses a federated identity credential that trusts the pod's Kubernetes service account token (via OIDC issuer) so the pod can exchange that token for an Azure AD access token. This eliminates secrets in pod config and avoids the deprecated pod-managed identity approach.

Exam trap

SC-300 often tests the difference between the deprecated pod-managed identity (aad-pod-identity) and the newer Azure AD Workload Identity, so candidates who remember older AKS documentation pick option A.

How to eliminate wrong answers

Option A is wrong because Azure AD pod-managed identity (aad-pod-identity) is deprecated and being retired in favor of Workload Identity; it also relies on NMI pods and IMDS interception rather than OIDC federation. Option B is wrong because a system-assigned managed identity on the node pool grants every pod on that node the same identity, violating least privilege and not scoping access to a specific pod. Option D is wrong because the Key Vault CSI driver still typically requires a managed identity or workload identity to authenticate, and storing the secret as a Kubernetes secret reintroduces the secret-in-cluster problem the question explicitly forbids.

138
MCQhard

You manage a Microsoft Entra tenant. A critical line-of-business application runs as an Azure Function with a system-assigned managed identity. The function needs to access an Azure Storage account and an Azure Key Vault. You need to grant the managed identity the necessary permissions with the least privilege. What should you do?

A.Assign the 'Storage Blob Data Contributor' role and the 'Key Vault Secrets User' role to the managed identity at the respective resource scopes.
B.Enable the managed identity on the function and assign the 'Reader' role on the storage account and Key Vault.
C.Assign the 'Storage Account Key Operator Service Role' and 'Key Vault Administrator' roles to the managed identity.
D.Assign the 'Contributor' role on the subscription to the managed identity.
AnswerA

The Storage Blob Data Contributor role allows read, write, and delete access to blob containers, which is appropriate for a function that needs to manipulate blobs. The Key Vault Secrets User role allows reading secrets, which is likely sufficient for the function to retrieve secrets. Assigning these roles at the resource scopes (Storage account and Key Vault) follows least privilege and grants only the needed permissions.

Why this answer

For a system-assigned managed identity in an Azure Function, you assign Azure RBAC roles at the specific resource scopes. The Storage Blob Data Contributor role provides the necessary data plane access to blobs, while the Key Vault Secrets User role allows reading secrets. This combination adheres to least privilege.

The other options either grant excessive permissions or insufficient permissions, so they are not correct.

Exam trap

The trap here is assuming that the Contributor or Reader roles at a higher scope are needed, when data plane access requires specific roles like Storage Blob Data Contributor and Key Vault Secrets User.

139
MCQeasy

An administrator accidentally deletes a cloud-only user account from the Microsoft Entra admin center. How many days does the administrator have to restore the user account before it is permanently deleted?

A.7 days
B.14 days
C.90 days
D.30 days
AnswerD

Microsoft Entra ID retains deleted users in a 'soft-deleted' state for exactly 30 days. During this time, the user can be restored with all their group memberships, licenses, and properties intact. Once the 30-day period expires, the user is permanently removed from the system and cannot be restored.

Why this answer

Microsoft Entra ID implements a 'soft-delete' state for deleted users, providing a safety net for accidental deletions. Knowing the exact duration of this window is fundamental for identity recovery operations. After this period, the object and its associated data are purged and cannot be recovered through standard administrative tools.

Exam trap

Candidates often confuse the 30-day soft-delete period for users with the 90-day retention period for deleted Microsoft 365 groups or other directory objects, leading to incorrect assumptions about data recovery timelines.

140
MCQhard

You are an identity administrator for a Microsoft Entra tenant. A critical application runs on an Azure Kubernetes Service (AKS) cluster and needs to access Azure Key Vault. You have configured the AKS cluster with the OIDC issuer and enabled workload identity. You created a user-assigned managed identity and granted it the Key Vault Secrets User role. You now need to configure the Kubernetes service account to use the managed identity. What should you do?

A.Assign the managed identity to the AKS node pool and restart the nodes.
B.Create a Kubernetes secret containing the managed identity's client secret and mount it into the pod.
C.Annotate the Kubernetes service account with azure.workload.identity/client-id set to the managed identity's client ID.
D.Configure the pod to use the managed identity by setting the AZURE_CLIENT_ID environment variable to the managed identity's client ID.
AnswerC

In AKS workload identity, the Kubernetes service account must be annotated with the client ID of the user-assigned managed identity. This annotation tells the workload identity webhook which identity to use when projecting the token. The pod then uses this service account to obtain a federated token that Entra ID exchanges for an access token. Without this annotation, the pod cannot authenticate as the managed identity.

Why this answer

To use workload identity in AKS, the Kubernetes service account must be annotated with the client ID of the user-assigned managed identity. This annotation allows the workload identity webhook to inject the necessary token projection into pods using that service account. The pod can then exchange the federated token for an Azure access token.

The other options either do not work with managed identities or do not provide the required configuration.

Exam trap

The trap here is thinking that an environment variable alone is enough, but the service account annotation is the critical step that enables the workload identity webhook.

141
MCQmedium

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. You need to delegate the ability to create and manage users to a helpdesk team without granting excessive permissions. Which Microsoft Entra role should you assign to the helpdesk team members?

A.Helpdesk Administrator
B.Password Administrator
C.Global Administrator
D.User Administrator
AnswerD

The User Administrator role is specifically designed to manage users and groups, including creating and managing users, resetting passwords, and managing licenses. It grants the necessary permissions for helpdesk tasks without the broad access of a Global Administrator. This role aligns with the principle of least privilege, providing exactly the capabilities needed to fulfill the requirement.

Why this answer

The User Administrator role provides the necessary permissions to create and manage users and groups, including resetting passwords and managing licenses, without granting broader administrative access. It is the least privileged role that meets the requirement. Other roles like Global Administrator are too permissive, while Helpdesk Administrator and Password Administrator lack the ability to create users.

Exam trap

The trap here is confusing the Helpdesk Administrator role with the User Administrator role; the former cannot create users, only reset passwords.

142
MCQhard

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. The company requires that all guest users must be reviewed every 90 days by their sponsor. If the sponsor does not respond, the guest account must be disabled automatically. You need to configure this using the least administrative effort. What should you do?

A.Use Microsoft Entra Connect Sync to synchronize guest accounts from an on-premises directory and set an expiration date.
B.Configure a Conditional Access policy that requires guest users to reauthenticate every 90 days.
C.Create an access review for guest users with a recurrence of every 90 days, set the reviewers to the sponsors, and configure the action to take on non-response to disable the user.
D.Create a dynamic group for guests and assign an access package with an expiration policy of 90 days.
AnswerC

Access reviews in Microsoft Entra ID can target guest users, set a recurrence, assign reviewers (such as sponsors), and define automatic actions on non-response. Configuring the action to disable the user meets the requirement. This is a built-in feature that requires minimal ongoing administrative effort once configured, as it automates the review and enforcement.

Why this answer

Access reviews are designed for periodic attestation of access, including guest users. You can configure a review to recur every 90 days, assign sponsors as reviewers, and set the action on non-response to disable the user account. This automates the process and requires minimal administrative effort after initial setup, directly meeting the requirements.

Exam trap

The trap here is confusing access reviews with other features like Conditional Access or access packages, which do not provide sponsor-based review and automatic account disablement.

143
MCQhard

Refer to the exhibit. What is the impact of this command on the user experience?

A.Users must MFA every hour.
B.Session tokens expire after one hour.
C.Users are blocked after one hour.
D.The policy forces MFA for every sign-in.
AnswerB

The command sets the single-factor session lifetime to exactly one hour. Consequently, users will be required to re-authenticate once their current token reaches this age. This is a very restrictive policy that forces frequent re-authentication, which can negatively impact productivity if not planned correctly for the user base.

Why this answer

The command sets the sign-in frequency to one hour, which controls how often a user must reauthenticate; the practical effect is that the session token (refresh token) is invalidated after one hour, forcing reauthentication. This is the standard behavior of the sign-in frequency session control in Conditional Access.

Exam trap

SC-300 often tests the distinction between sign-in frequency (reauthentication interval) and MFA enforcement, causing candidates to pick 'MFA every hour' when the actual effect is token expiry and reauthentication.

How to eliminate wrong answers

Option A is wrong because sign-in frequency does not force MFA every hour; it forces reauthentication, and MFA is only re-prompted if the authentication method requires it or if the tenant enforces MFA on every sign-in. Option C is wrong because the user is not blocked; they are simply asked to sign in again. Option D is wrong because forcing MFA on every sign-in is a separate control (or authentication strength), not the sign-in frequency setting.

144
MCQhard

You are a Microsoft Entra Identity Governance administrator at Contoso. An access review of the 'Finance-Readers' group is configured with 'Auto apply results to resource' enabled. The reviewers are the group owners, and the review is scheduled to recur quarterly. Contoso's security policy states that if a reviewer does not respond before the review period ends, the user must lose access. Which setting must you configure in the access review to meet this policy?

A.Set 'If reviewers don't respond' to 'Approve access'.
B.Set 'Require justification on approval' to 'Yes'.
C.Set 'Reviewers' to 'Selected users or groups' and choose the security team.
D.Set 'If reviewers don't respond' to 'Remove access'.
AnswerD

This setting controls what happens to a user's membership when no reviewer decision is recorded before the review instance ends. Choosing 'Remove access' ensures that non-response results in removal of the group membership, satisfying the policy that silence means loss of access. It works together with 'Auto apply results to resource' so the decision is enforced automatically.

Why this answer

The 'If reviewers don't respond' option determines the outcome for users whose reviewers do not act before the review instance closes. Selecting 'Remove access' aligns the review with the policy that unanswered reviews must result in loss of access. Because 'Auto apply results to resource' is enabled, that decision is automatically enforced on the group membership, ensuring continuous least privilege for financial data.

Exam trap

The trap here is confusing reviewer justification requirements with the fallback decision for non-responsive reviewers, when only the latter controls whether access is removed automatically.

145
MCQeasy

Which type of identity should you use for an application running on an Azure Virtual Machine that needs to access Azure Storage without managing credentials?

A.Service Principal with a certificate.
B.System-assigned managed identity.
C.Shared Access Signature (SAS) token.
D.Azure AD User account.
AnswerB

System-assigned managed identities are tied directly to the lifecycle of the Azure resource. When the VM is deleted, the identity is automatically removed. This is the simplest way to provide a VM with an identity for accessing other Azure resources without manual configuration or credential lifecycle management overhead.

Why this answer

User-assigned or system-assigned managed identities are the industry standard for Azure VMs. They provide an identity in Azure AD that applications can use to authenticate to any service that supports AD authentication, such as Azure Storage. This approach removes the need to store sensitive credentials in code or configuration, significantly improving the security posture of the application and simplifying secret management.

Exam trap

Candidates often suggest using a service principal with a client secret, which introduces unnecessary credential management overhead compared to the built-in managed identity feature.

146
MCQmedium

You need to implement a process to periodically verify that service principals still require their assigned permissions to Microsoft Graph. What should you use to automate this process?

A.Microsoft Entra ID Protection alerts.
B.Microsoft Entra Access Reviews.
C.Azure Monitor Log Analytics alerts.
D.Privileged Identity Management (PIM) for groups.
AnswerB

Microsoft Entra Access Reviews allow you to create recurring reviews for service principals assigned to directory roles or groups. Administrators or designated reviewers can attest to the continued need for access, and the system can automatically remove permissions if the review is not approved or completed.

Why this answer

Access reviews are a core component of Identity Governance. While often used for human users, they can also be applied to service principals that have been assigned high-privilege roles or application permissions. This ensures that workload identities do not retain permissions indefinitely, supporting the principle of least privilege.

Exam trap

Candidates often assume access reviews are exclusively for human users, failing to realize that service principals can be included in access reviews to audit their persistent permissions.

147
MCQmedium

You are the Catalog Owner for the 'Finance' catalog in Entitlement Management. You need to allow a project lead to create access packages within this catalog, but you do not want them to have permissions to add new resources to the catalog itself. Which role should you assign to the project lead?

A.Catalog Owner.
B.Access Package Manager.
C.Access Package Assignment Manager.
D.User Administrator.
AnswerB

The Access Package Manager role allows the user to create, update, and delete access packages within a specific catalog. However, they cannot add or remove resources from the catalog. This role perfectly matches the requirement of allowing package creation while restricting catalog-level resource management to the Catalog Owner.

Why this answer

The Access Package Manager role is specifically designed to allow users to create and manage access packages within a catalog without granting them the ability to add or remove resources from the catalog. This aligns with the principle of least privilege, as the project lead only needs to manage access packages, not the catalog's resource inventory. Catalog Owner would grant full control over the catalog, including resource management, which exceeds the requirement.

Exam trap

SC-300 often tests the distinction between catalog-level roles and their permissions, trapping candidates who assume that managing access packages requires full catalog ownership.

How to eliminate wrong answers

Option A is wrong because Catalog Owner grants full permissions over the catalog, including adding and removing resources, which violates the principle of least privilege. Option C is wrong because Access Package Assignment Manager only allows managing assignments of access packages, not creating them. Option D is wrong because User Administrator is a directory role that manages users and groups, not entitlement management catalogs or access packages.

148
Multi-Selectmedium

You are delegating administrative tasks in Microsoft Entra Entitlement Management. Which THREE roles are specifically designed to manage aspects of access packages and catalogs without requiring the Global Administrator role?

Select 3 answers
A.Catalog owner
B.Billing Administrator
C.Access package manager
D.User Administrator
E.Identity Governance Administrator
AnswersA, C, E

Catalog owners have the authority to manage all aspects of a specific catalog, including the resources and access packages within it. They can delegate further roles, such as access package managers, to handle specific administrative tasks. This role is essential for decentralized governance within large organizations.

Why this answer

Catalog owner (A) is correct because this role is scoped to a specific catalog and can create, edit, and delete access packages within that catalog, manage catalog resources, and assign other catalog owners or access package managers without needing Global Administrator. Access package manager (C) is correct because it is delegated to manage the lifecycle of assigned access packages, including editing policies, assignments, and requests, while being limited to the access packages it owns. Identity Governance Administrator (E) is correct because it is the built-in role designed for Entitlement Management and related governance features, able to manage catalogs, access packages, connected organizations, and policies across the tenant without full Global Administrator privileges.

Billing Administrator (B) is not correct because it manages subscriptions, billing, and purchase-related tasks, not access packages or catalogs. User Administrator (D) is not correct because it manages users, groups, and some password/administrative tasks, but does not provide the delegated Entitlement Management capabilities for catalogs and access packages.

Exam trap

SC-300 often tests the misconception that User Administrator or Billing Administrator can manage Entitlement Management, when in fact only specific governance roles like Catalog owner, Access package manager, and Identity Governance Administrator are designed for this purpose.

149
Multi-Selectmedium

You are implementing Privileged Identity Management (PIM) for Entra ID roles. You need to configure the 'Global Administrator' role to ensure that when a user activates the role, it is done securely and with oversight. Which TWO settings should you configure in the role's activation policy?

Select 2 answers
A.Require approval to activate
B.Maximum activation duration
C.Permanent eligibility
D.Require permanent assignment
E.Allow permanent activation
AnswersA, B

Requiring approval adds a workflow step where a designated person (the approver) must review and authorize the activation request. This provides critical oversight for highly sensitive roles like Global Administrator, ensuring that elevation only occurs for legitimate, documented business reasons during the requested window.

Why this answer

When configuring the activation settings for a highly privileged role like Global Administrator in Microsoft Entra ID PIM, you should configure 'Require approval to activate' to ensure oversight by designated approvers, and 'Maximum activation duration' to limit the exposure window.

Exam trap

Candidates often focus only on justification or ticketing requirements, forgetting that high-privilege roles explicitly demand secondary approval and limited activation windows.

150
MCQhard

You are configuring an access package in Microsoft Entra Entitlement Management for a project that includes internal employees and external users from a partner organization. The partner organization uses its own Microsoft Entra ID tenant. You need to ensure that when a partner user's access is revoked, their guest account in your tenant is automatically deleted after 30 days. What should you configure?

A.In the access package's lifecycle settings, set 'Expiration' to 30 days and enable 'Delete guest accounts'.
B.Create a lifecycle workflow that triggers when a guest user is deleted and waits 30 days before deleting the account.
C.In the access package's assignment policy, set 'Require approval' to 'Yes' and configure a custom extension to delete the guest after 30 days.
D.Configure an external user lifecycle policy in Microsoft Entra ID Governance to delete guest accounts 30 days after they lose their last access package assignment.
AnswerD

Microsoft Entra ID Governance includes external user lifecycle policies that can automatically delete guest accounts after a specified period once they no longer have any access package assignments. This policy directly addresses the requirement by monitoring when a guest loses all assignments and then starting a 30-day countdown before deletion. It is the designed feature for managing guest lifecycle based on entitlement management assignments.

Why this answer

External user lifecycle policies in Microsoft Entra ID Governance are designed to manage the lifecycle of guest users based on their access package assignments. When a guest loses all assignments, the policy can automatically delete the account after a specified inactivity period, such as 30 days. This feature directly fulfills the requirement without custom scripting or manual intervention.

Other options either do not target guest deletion or lack the required delay.

Exam trap

The trap here is confusing access package expiration with guest account deletion, which are separate features; expiration ends the assignment but does not delete the guest account.

Page 1

Page 2 of 4

Page 3

All pages