Courseiva

Microsoft Identity and Access Administrator Associate (SC-300) — Questions 151–225

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

Page 2

Page 3 of 4

Page 4
151
MCQmedium

Your organization is implementing Self-Service Password Reset (SSPR). You want to ensure that users can only reset their passwords if they have registered at least two different authentication methods. Which configuration should you modify in the Microsoft Entra admin center to enforce this?

A.Number of methods required to reset in the SSPR properties
B.The 'Registration' tab in the Password Reset settings
C.The 'Combined security information registration' policy
D.Conditional Access policies for the 'My Profile' application
AnswerA

The 'Number of methods required to reset' setting directly controls the security threshold for the SSPR process. By setting this value to two, you ensure that a user must prove their identity through two distinct channels before the system allows them to choose a new password for their account.

Why this answer

In the Microsoft Entra admin center, under 'Password reset' > 'Authentication methods', the setting is explicitly named 'Number of methods required to reset'. The option text provided is correct, but the explanation claims it is 'slightly imprecise', which is confusing for the candidate. The explanation should confirm the option matches the UI exactly.

Exam trap

Candidates often confuse the 'Registration' tab (which controls how many days until a user is prompted to re-verify) with the 'Authentication methods' tab (which controls the number of methods required for the reset process itself).

152
MCQeasy

A company uses Microsoft Entra ID and has a hybrid environment with on-premises Active Directory Domain Services (AD DS). The security team wants to ensure that when a user's on-premises account is disabled, their Entra ID session is revoked within minutes rather than waiting for token expiration. You need to configure the appropriate feature. What should you enable?

A.Microsoft Entra Password Protection
B.Continuous Access Evaluation (CAE)
C.Microsoft Entra ID Protection
D.Conditional Access sign-in frequency
AnswerB

CAE enables near-real-time revocation of tokens when critical events occur, such as a user account being disabled or a password change. It works with supported clients like Outlook and Teams. Enabling CAE ensures that a disabled on-premises account synced to Entra ID triggers immediate session revocation, satisfying the requirement for rapid enforcement.

Why this answer

Continuous Access Evaluation (CAE) allows Microsoft Entra ID to revoke access tokens in near real time when critical events such as account disablement or password change occur. Supported clients receive the revocation and force reauthentication. Sign-in frequency, Password Protection, and ID Protection do not provide this immediate, event-based token revocation, so CAE is the correct feature to enable.

Exam trap

The trap here is confusing Conditional Access sign-in frequency with real-time revocation; sign-in frequency only sets a maximum session age and does not react to account disablement events.

153
MCQmedium

You have an application that uses a client secret to authenticate as a service principal. The secret is expiring in 30 days. You need to rotate the secret with minimal downtime. What should you do?

A.Delete the existing client secret and immediately create a new one, then update the application configuration.
B.Create a new client secret and immediately delete the old one, then update the application configuration.
C.Create a new client secret, update the application configuration to use the new secret, and then delete the old secret after confirming the application works.
D.Extend the expiration date of the existing client secret by modifying its properties.
AnswerC

Creating a new client secret while the old one is still valid allows the application to be updated without downtime. After the application is successfully using the new secret, the old secret can be deleted. This approach ensures continuous authentication and minimizes the risk of an outage. It is the recommended practice for secret rotation, as it allows for a grace period and verification before removing the old credential.

Why this answer

Creating a new client secret while the old one remains active, updating the application to use the new secret, and then deleting the old secret after verification ensures minimal downtime. This phased approach prevents authentication failures. Other options either cause immediate downtime, are not technically possible, or delete the old secret prematurely.

Exam trap

The trap here is assuming that you can extend the expiration of an existing client secret, which is not supported.

154
Multi-Selectmedium

You are planning to implement Conditional Access policies specifically for workload identities in your Microsoft Entra tenant. Which TWO of the following are mandatory requirements or components for applying Conditional Access to service principals? (Select TWO)

Select 2 answers
A.Microsoft Entra Workload ID Premium license
B.A user account with a FIDO2 security key
C.A service principal object
D.An Azure Information Protection scanner
E.A Microsoft Entra ID Free edition tenant
AnswersA, C

The Workload Identity Premium license is a specific SKU required to unlock advanced security features for non-human identities. This includes Conditional Access for workload identities, access reviews for service principals, and workload identity risk detection, which are not included in standard P1 or P2 licenses.

Why this answer

Conditional Access for workload identities allows organizations to secure service principals based on risk and location. To use this feature, you must have a Workload Identity Premium license. Unlike standard policies for users, these policies specifically target service principal objects, allowing administrators to restrict access to resources based on the specific identity of the application or service.

Exam trap

Candidates often assume that an Entra ID Premium P2 license covers everything. However, Microsoft introduced a specific 'Workload Identity Premium' license for advanced governance and CA features specifically targeting non-human identities.

155
Multi-Selecthard

You are the Identity and Access Administrator for 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 solution must meet the following requirements: users must be required to register for SSPR the next time they sign in, and users must confirm their identity using two methods before resetting their password. Which two actions should you perform? (Choose two.)

Select 2 answers
A.Configure the authentication methods policy to enable only the Microsoft Authenticator app and email OTP.
B.In the authentication methods policy, set the number of methods required to reset to two.
C.Enable password writeback in Microsoft Entra Connect.
D.In the Microsoft Entra admin center, set the self-service password reset property to All users and enable Require users to register when signing in.
E.Create a Conditional Access policy that requires multi-factor authentication for all users.
AnswersB, D

The authentication methods policy includes a setting that defines how many methods a user must verify to reset their password. Setting it to two ensures users must confirm their identity with two distinct methods, meeting the requirement for two-method verification.

Why this answer

To enforce SSPR registration at next sign-in, you enable SSPR for all users and turn on the option to require registration when signing in. To require two methods for reset, you configure the number of methods required to reset in the authentication methods policy. Together, these actions ensure users register and must verify with two methods before resetting.

Exam trap

The trap here is confusing MFA registration with SSPR registration, and assuming that enabling methods alone enforces the number of methods required for reset.

156
MCQeasy

An administrator wants to ensure that users are not prompted for MFA when they are working from the corporate headquarters. What should be configured in Microsoft Entra ID to define the corporate network's public IP ranges as a trusted location?

A.Named Locations with the 'Mark as trusted location' checkbox selected.
B.A 'Trusted IPs' list in the legacy MFA service settings portal.
C.The 'Workplace Join' setting for all corporate-owned Windows devices.
D.An Azure Virtual Network Gateway with a Site-to-Site VPN connection.
AnswerA

In the Entra admin center, you can create a Named Location by IP range. By checking the 'Mark as trusted location' box, you inform the Conditional Access engine that these IPs belong to a known, secure environment. This 'Trusted' status is a specific signal that policies can use to satisfy MFA requirements or provide exceptions for users on-premises.

Why this answer

Named Locations in Microsoft Entra ID allow administrators to define trusted IP ranges and mark them as trusted. When a location is marked as trusted, Conditional Access policies that require MFA can exclude it, so users at the corporate headquarters are not prompted for MFA. This is the correct way to define the corporate network's public IP ranges as a trusted location.

Exam trap

SC-300 often tests whether candidates confuse the legacy 'Trusted IPs' setting in the MFA portal with the modern Named Locations feature in Conditional Access, so knowing that Named Locations is the current supported method is essential.

How to eliminate wrong answers

Option B is wrong because the legacy MFA service settings portal's 'Trusted IPs' list is deprecated and does not integrate with modern Conditional Access policies. Option C is wrong because Workplace Join is a device registration feature and does not define network locations or affect MFA prompts based on IP. Option D is wrong because an Azure Virtual Network Gateway with Site-to-Site VPN is a networking construct for connecting on-premises networks to Azure, not a mechanism for defining trusted locations in Entra ID.

157
MCQhard

Your organization uses GitHub Actions for CI/CD workflows that deploy resources to Azure. You want to implement a security strategy that allows GitHub to authenticate to Microsoft Entra ID without using static secrets. You decide to use workload identity federation. What is the primary component required on the Microsoft Entra ID side to establish this trust?

A.A Managed Identity with a certificate
B.An Application Proxy connector
C.A Federated Identity Credential
D.A Conditional Access policy
AnswerC

The Federated Identity Credential is the specific object added to a software representation in Entra ID to trust an external OIDC provider. It defines which external tokens are valid based on claims like issuer and subject, enabling the GitHub workflow to authenticate securely without secrets.

Why this answer

Workload identity federation allows you to access Microsoft Entra protected resources without needing to manage secrets for external workloads. By creating a federated identity credential, you establish a trust relationship between Microsoft Entra ID and the external identity provider, such as GitHub. This allows the external workload to exchange its own token for an Entra access token.

Exam trap

Many students think that a standard Service Principal is enough. While a Service Principal is used, the 'Federated Identity Credential' is the specific configuration that allows the external OIDC provider to authenticate without a secret.

158
MCQhard

Refer to the exhibit. An application using a service principal is failing to authenticate with the error shown. What is the most likely cause?

A.The service principal has been deleted from Azure AD.
B.The client secret used by the application is invalid or expired.
C.The application lacks RBAC permissions to access the resource.
D.The user is required to perform Multi-Factor Authentication.
AnswerB

This error message is the standard Azure AD response when a client secret is provided that does not match the current valid secret for the application or has passed its expiration date. Replacing the secret with a new, valid one is the standard remediation step for this specific error code.

Why this answer

The error shown in the exhibit is 'AADSTS7000215: Invalid client secret provided.' This specific error code indicates that the client secret (password) used by the application to authenticate is either incorrect, expired, or not matching the one stored in Azure AD. Since the service principal is using a client secret for authentication, the most likely cause is that the secret is invalid or expired.

Exam trap

SC-300 often tests the ability to distinguish between authentication errors (like invalid client secret) and authorization errors (like insufficient permissions), so candidates must carefully read the error code and message to identify the correct cause.

How to eliminate wrong answers

Option A is wrong because if the service principal were deleted, the error would typically be 'AADSTS700016: Application with identifier ... was not found in the directory' or similar, not an invalid client secret error. Option C is wrong because missing RBAC permissions would result in an authorization error (e.g., 403 Forbidden) after successful authentication, not an authentication failure like invalid client secret. Option D is wrong because MFA requirements apply to user authentication, not service principal authentication; service principals do not perform interactive MFA.

159
MCQmedium

A developer is deploying a web application on an Azure Virtual Machine that needs to retrieve connection strings from Azure Key Vault. The security policy mandates that no long-lived credentials, such as client secrets or certificates, should be stored in the application code or environment variables. Which feature should you implement to meet these requirements with the least administrative effort?

A.App registration with a client secret
B.A user-assigned managed identity
C.A service principal with a certificate
D.Shared Access Signatures (SAS)
AnswerB

User-assigned managed identities are standalone Azure resources that provide an identity for the VM. They satisfy the requirement because Entra ID handles the credential lifecycle automatically. Unlike system-assigned identities, user-assigned ones can be shared across multiple resources, offering flexible and secure access to the Key Vault.

Why this answer

Managed identities provide an identity for applications to use when connecting to resources that support Microsoft Entra authentication. By using a managed identity, Microsoft Entra ID manages the credentials for the service principal automatically. This eliminates the need for developers to handle secrets, significantly reducing the risk of credential leakage and simplifying the overall security architecture for Azure-hosted resources.

Exam trap

Candidates often confuse Managed Identities with standard Service Principals. While both use Service Principals internally, Managed Identities remove the manual burden of secret rotation and storage, which is the primary requirement in this specific scenario.

160
MCQeasy

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. A new employee joins the company and needs a user account. The employee will use a company-provided email address that is already verified in the tenant. You need to create the user account with the least administrative effort. What should you use?

A.The Azure AD Connect sync tool to synchronize the user from on-premises Active Directory.
B.The New-MgUser PowerShell cmdlet with the -AccountEnabled parameter set to $true.
C.The Microsoft Graph API by sending a POST request to the /users endpoint with a JSON payload.
D.The Microsoft Entra admin center by selecting New user and filling in the required fields.
AnswerD

The Microsoft Entra admin center provides a straightforward graphical interface to create a new user. It automatically generates a temporary password and guides you through the necessary fields. This is the least administrative effort for creating a single user account, especially when the email is already verified.

Why this answer

Creating a single user account with minimal effort is best done through the Microsoft Entra admin center, which provides a guided interface. The admin center automatically handles password generation and required fields, making it the simplest method for a one-off user creation. Other methods like PowerShell, Azure AD Connect, or Graph API are better suited for bulk or automated scenarios.

Exam trap

The trap here is overcomplicating a simple user creation task by choosing PowerShell or Graph API when the admin center is the most efficient for a single user.

161
MCQmedium

Refer to the exhibit. An administrator creates a dynamic group rule for a management team. After 24 hours, several users with the job title 'Sales Manager' are not appearing in the group. What is the most likely cause for this behavior?

A.The 'contains' operator is case-sensitive in dynamic group rules
B.The users have the 'accountEnabled' attribute set to false
C.The Job Title attribute for those users is currently null or empty
D.Dynamic groups are limited to a maximum of 1,000 members
AnswerC

Dynamic rules only evaluate users who have a non-null value for the attribute being checked. If the 'Job Title' field is empty in the Microsoft Entra ID user profile, the '-contains' operator will fail to find a match, resulting in the user being excluded from the group membership.

Why this answer

The most likely cause is that the Job Title attribute for those users is null or empty. Dynamic group rules evaluate attributes; if the attribute is not populated, the user will not match the rule. Even if the job title appears as 'Sales Manager' in the UI, it might not be set in the attribute used by the rule.

Exam trap

SC-300 often tests attribute-based dynamic membership; candidates might overlook that missing attributes cause exclusion, and instead blame case sensitivity or limits.

How to eliminate wrong answers

Option A is wrong because the 'contains' operator in dynamic group rules is case-insensitive; it does not cause users to be excluded based on case. Option B is wrong because if accountEnabled is false, the user account is disabled and would not be included, but the question states users are not appearing despite having the job title, implying accounts are active. Option D is wrong because dynamic groups do not have a 1,000 member limit; they can support larger memberships, though there are limits on the number of dynamic groups per tenant.

162
Multi-Selectmedium

You are configuring self-service password reset (SSPR) in Microsoft Entra ID for a group of remote users who do not have company-issued mobile phones. You need to enable SSPR with methods that do not require a mobile device. Which two authentication methods should you enable? (Choose two.)

Select 2 answers
A.Email
B.Microsoft Authenticator app
C.SMS
D.Voice call
E.Security questions
AnswersA, E

Email is a valid SSPR authentication method that does not require a mobile device. Users receive a verification code at their registered non-Microsoft email address. It is suitable for remote users without company phones. However, it requires users to have an external email account, and it is less secure than other methods, so it should be combined with another method for MFA.

Why this answer

Email and security questions are the only SSPR methods that do not require a mobile device. They allow users to reset passwords using a non-Microsoft email account or pre-registered answers. The Microsoft Authenticator app, SMS, and voice call all require a phone, which the remote users lack.

Enabling email and security questions provides a viable SSPR experience for these users.

Exam trap

The trap here is assuming that all SSPR methods are available without a phone, but only email and security questions qualify.

163
MCQhard

Refer to the exhibit. What is the primary security implication of running this command as written?

A.The command fails because the scope is too narrow.
B.The client secret is displayed in plain text, exposing it to potential theft.
C.The service principal is not assigned any authentication method by default.
D.The service principal is created with Owner permissions instead of Contributor.
AnswerB

When using the Azure CLI to create a service principal, the secret is output directly to the console. If this command is run in a CI/CD pipeline or a shared terminal, the secret can be intercepted, stored in logs, or seen by others, creating an immediate and serious security vulnerability.

Why this answer

When you create an app registration or service principal via CLI commands such as `az ad sp create-for-rbac`, the generated client secret (password) is returned in the command output in plain text. Anyone with access to the terminal history, logs, or the output stream can capture this credential and use it to authenticate as the service principal, potentially gaining whatever permissions were assigned. This is why the secret must be immediately stored in a secure vault (e.g., Azure Key Vault) and never echoed to logs or shared channels.

Exam trap

SC-300 often tests the misconception that creating a service principal automatically secures its credentials, when in fact the CLI returns the client secret in plain text — candidates overlook the exposure risk and focus on role or scope details instead.

How to eliminate wrong answers

Option A is wrong because the scope parameter (e.g., --scopes) does not cause the command to fail for being 'too narrow' — a narrow scope simply limits permissions, it does not produce an error. Option C is wrong because the service principal is in fact assigned an authentication method (the client secret/password) at creation time; the command generates and returns it. Option D is wrong because the default role assigned by `az ad sp create-for-rbac` is Contributor (unless overridden), not Owner — and in any case the question asks about the security implication of the command output, not the role assignment.

164
MCQhard

Refer to the exhibit. You are reviewing a JSON configuration for a Microsoft Entra access review. What is the expected outcome if the designated reviewer fails to respond to a review request for a specific guest user before the review period expires?

A.The guest user will retain access until the next review cycle begins.
B.The guest user's access to the resource will be automatically revoked.
C.An alert will be sent to the Global Administrator to make a manual decision.
D.The review period will be extended by 7 days automatically.
AnswerB

The configuration specifies 'defaultDecision': 'Deny' and 'autoApplyDecisionsEnabled': true. This means that at the end of the review period, if no decision has been recorded by the administrator, the system will automatically treat the review as a denial and remove the user's access to the associated resource.

Why this answer

The JSON configuration in the exhibit sets the access review's 'defaultDecision' to 'Deny' and 'autoApplyDecisionsEnabled' to true, which means that if the reviewer does not respond before the review ends, the guest user's access is automatically revoked. This is the standard behaviour when non-response is configured to deny and auto-apply is enabled.

Exam trap

SC-300 often tests the interaction between 'defaultDecision' and 'autoApplyDecisionsEnabled' — candidates assume non-response always means 'no change', but the JSON explicitly sets Deny with auto-apply.

How to eliminate wrong answers

Option A is wrong because 'No change' would be the behaviour only if defaultDecision were 'None' or auto-apply were disabled — the exhibit shows Deny with auto-apply. Option C is wrong because the review does not escalate to a Global Administrator on non-response; it applies the default decision. Option D is wrong because access reviews do not auto-extend review periods — the duration is fixed at creation.

165
MCQmedium

You are an Identity and Access Administrator at a company that uses Microsoft Entra ID Governance. The security team wants to ensure that access to a critical application is revoked automatically if a user's manager does not certify the access during a scheduled review. You need to configure an access review for the application's assignment group. What should you do?

A.Set 'Auto apply results to resource' to 'Enable' and configure 'If reviewers don't respond' to 'Remove access'.
B.Set 'Auto apply results to resource' to 'Disable' and configure 'If reviewers don't respond' to 'Remove access'.
C.Set 'Auto apply results to resource' to 'Enable' and configure 'If reviewers don't respond' to 'Approve access'.
D.Set 'Auto apply results to resource' to 'Disable' and configure 'If reviewers don't respond' to 'Approve access'.
AnswerA

This configuration ensures that when reviewers do not respond within the review duration, the system automatically removes the user's access. Enabling auto-apply ensures the decision is enforced without manual intervention, meeting the requirement to revoke access if the manager does not certify.

Why this answer

To automatically revoke access when reviewers do not respond, the access review must have auto-apply enabled and the no-response behavior set to remove access. This ensures that if the manager fails to certify, the system enforces removal without manual intervention, aligning with the security team's directive.

Exam trap

The trap here is assuming that setting 'Remove access' alone will automatically revoke access, but without enabling auto-apply, the decision remains pending until manually applied.

166
MCQmedium

You are implementing Continuous Access Evaluation (CAE) in your tenant. A user's account is disabled by an administrator. How does CAE affect the user's active session with Exchange Online?

A.The session remains active until the access token expires.
B.The session is revoked in near real-time.
C.The user is prompted for MFA at the next sign-in.
D.The session is revoked only if the user's IP changes.
AnswerB

CAE enables a conversation between the identity provider and the resource provider. When a critical event like account disabling or a password reset occurs, the service is notified immediately. This results in the session being terminated within minutes, providing much tighter security than standard token expiration cycles.

Why this answer

Continuous Access Evaluation (CAE) is specifically designed to revoke access in near real-time when critical events occur, such as a user account being disabled. Therefore, option B is the correct answer.

Exam trap

Candidates often confuse CAE with standard token expiration (1 hour), assuming that access will persist until the token expires. CAE overrides this behavior for critical events.

167
MCQmedium

Which Azure AD feature allows you to manage the lifecycle of an application's service principal, including conditional access policies and user assignment, in a centralized manner?

A.Application Registration
B.Enterprise Application
C.Managed Identity
D.Azure Policy
AnswerB

Enterprise Applications represent the service principal instance within the tenant. They allow administrators to apply tenant-specific security policies, such as conditional access, user assignment, and sign-in logs, effectively acting as the management console for how the application is consumed and secured by users in that specific tenant.

Why this answer

The Enterprise Application blade in Microsoft Entra ID is where you manage the service principal — the instance of an application in your tenant. It centralizes user and group assignment, single sign-on configuration, provisioning, conditional access policy targeting, and lifecycle management of the service principal. Application Registration, by contrast, defines the application's identity and permissions but is not where you manage tenant-specific access and lifecycle.

Exam trap

SC-300 often tests the distinction between Application Registration (app object, developer-facing identity definition) and Enterprise Application (service principal, admin-facing access and lifecycle management) — candidates frequently pick App Registration when the question asks about user assignment, conditional access, or lifecycle.

How to eliminate wrong answers

Option A is wrong because Application Registration defines the application object (app registration) — its redirect URIs, API permissions, and credentials — but does not manage the service principal's user assignment, conditional access, or tenant-specific lifecycle. Option C is wrong because Managed Identity provides an automatically managed identity for Azure resources to authenticate to services, but it does not offer centralized lifecycle management of arbitrary application service principals with conditional access and user assignment. Option D is wrong because Azure Policy is a governance service that enforces rules on Azure resources (e.g., allowed locations, tags), not a tool for managing Entra ID application service principals or their access policies.

168
MCQmedium

You need to delegate the ability for a project lead to manage their own resources within Entitlement Management without granting them full Identity Governance Administrator permissions. What is the most restrictive role you should assign the project lead for a specific catalog?

A.Access Package Manager
B.Identity Governance Administrator
C.User Administrator
D.Catalog Owner
AnswerD

The Catalog Owner role is designed for delegation, allowing a user to manage the lifecycle of a specific catalog. This includes adding resources, managing access packages, and assigning other users to roles within that catalog, providing the project lead with complete control over their specific project assets only.

Why this answer

The Catalog Owner role is the most restrictive role that allows a project lead to manage their own resources within Entitlement Management for a specific catalog. Catalog Owners can manage the catalog's resources, access packages, and assignments without having broader administrative permissions. This aligns with the principle of least privilege.

Exam trap

SC-300 often tests the distinction between Entitlement Management roles, and candidates may confuse Catalog Owner with Access Package Manager or broader roles, but the most restrictive role for managing a catalog's resources is Catalog Owner.

How to eliminate wrong answers

Option A is wrong because Access Package Manager can manage access packages but does not have the same level of control over the catalog itself, and it may not be as restrictive as Catalog Owner for managing resources within a catalog. Option B is wrong because Identity Governance Administrator is a broad role that grants full permissions over Entitlement Management, which is more than needed. Option C is wrong because User Administrator manages users and groups, not Entitlement Management resources, and is not the appropriate role for this task.

169
MCQmedium

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. The security team requires that users who are assigned the Global Administrator role must use phishing-resistant authentication. You need to enforce this requirement using a Microsoft Entra ID feature that evaluates the authentication method used at sign-in and blocks access if it is not phishing-resistant. What should you configure?

A.A Microsoft Entra ID Protection risk policy that blocks sign-ins with a high sign-in risk level.
B.A named location that marks the corporate network as trusted, combined with a Conditional Access policy that requires compliant devices.
C.A Microsoft Entra authentication method policy that enables only the Microsoft Authenticator app for all users.
D.A Conditional Access policy that targets the Global Administrator directory role and requires an authentication strength of Phishing-resistant MFA.
AnswerD

Authentication strengths in Conditional Access let you require specific method combinations, such as phishing-resistant MFA. Targeting the Global Administrator role ensures the policy applies to privileged accounts. This directly satisfies the requirement to block non-phishing-resistant sign-ins for those users.

Why this answer

Authentication strengths are predefined or custom sets of authentication methods that meet specific security requirements, such as phishing-resistant MFA. By applying a Conditional Access policy to the Global Administrator role and requiring that strength, any sign-in attempt with a weaker method is denied. This is the precise mechanism in Microsoft Entra ID for enforcing method-specific authentication requirements.

Exam trap

The trap here is assuming that enabling only strong methods in the authentication methods policy automatically blocks weaker sign-ins, when enforcement requires a Conditional Access authentication strength.

170
MCQhard

Refer to the exhibit. An organization is enforcing PIM for the Contributor role. Based on the JSON configuration for the role setting, what is the maximum amount of time a user can have the role active after their request is approved?

A.The user can remain active in the role for a maximum of 8 days.
B.The user's role will never expire as long as they are signed in.
C.The user can remain active in the role for a maximum of 8 hours.
D.The user must renew their activation every 8 minutes to keep the role.
AnswerC

In ISO 8601 duration format, 'PT8H' stands for a period of 8 hours. This configuration ensures that even after a manager approves the request, the user's elevated permissions will be automatically revoked by the system once the 8-hour window has elapsed, supporting the principle of just-in-time access.

Why this answer

The maxExpirationDuration attribute in the provided JSON configuration is set to 'PT8H'. In ISO 8601 duration format, 'PT8H' represents a period of 8 hours. Therefore, the maximum activation duration for the Contributor role is 8 hours.

Exam trap

Candidates may confuse the ISO 8601 duration format 'PT8H' with other time units or misinterpret the 'P' (period) and 'T' (time) designators.

171
MCQeasy

You are an 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 services from unmanaged devices. You need to configure a Conditional Access policy that allows access only from devices that are marked as compliant in Microsoft Intune. What should you select in the Grant controls of the Conditional Access policy?

A.Require device to be marked as compliant
B.Require Hybrid Azure AD joined device
C.Require multi-factor authentication
D.Require approved client app
AnswerA

Selecting 'Require device to be marked as compliant' ensures that only devices that are enrolled in Intune and meet compliance policies are allowed access. This directly enforces the requirement that users cannot sign in from unmanaged devices. It is the correct grant control for this scenario.

Why this answer

The 'Require device to be marked as compliant' grant control in Conditional Access ensures that only devices that are enrolled in Microsoft Intune and meet the organization's compliance policies can access the targeted resources. This directly prevents access from unmanaged devices. Other grant controls like MFA, hybrid Azure AD join, or approved client app do not enforce device compliance and therefore do not satisfy the requirement.

Exam trap

The trap here is confusing device compliance with other device-related controls such as hybrid Azure AD join or approved client app, which do not verify that the device meets compliance policies.

172
Multi-Selectmedium

You are auditing your environment for security risks related to workload identities. Which THREE conditions should you flag as high-security risks? (Choose three)

Select 3 answers
A.Service principals with client secrets that have no expiration date.
B.Managed identities assigned to multiple virtual machines.
C.Multiple applications sharing the same service principal client secret.
D.Service principals with the 'Contributor' role at the subscription scope.
E.Service principals that use certificate-based authentication.
AnswersA, C, D

Secrets without expiration dates pose a severe risk because they remain valid indefinitely. If a developer accidentally leaks such a secret, an attacker can maintain persistent access until the secret is manually deleted. Enforcing expiration dates ensures that credentials must be rotated regularly, limiting the impact of potential leaks.

Why this answer

The selected options (A, C, D) are correct as they represent significant security risks (lack of credential rotation, credential reuse, and excessive privilege). The explanation is accurate.

Exam trap

Candidates might mistakenly identify Managed Identities as a risk, but they are a security best practice as they eliminate the need for credentials.

173
MCQeasy

You are an Identity and Access Administrator for a company using Microsoft Entra ID. The compliance team requires that all access package assignments are reviewed every six months. Which feature should you configure to meet this requirement?

A.Entitlement Management with automatic assignment policies.
B.Privileged Identity Management (PIM) for Groups.
C.Lifecycle Workflows with a scheduled trigger.
D.Access reviews for access packages.
AnswerD

Access reviews can be configured for access packages to periodically review assignments. You can set the recurrence to every six months, and reviewers can attest to the continued need for access. This directly meets the requirement for regular reviews of access package assignments.

Why this answer

Access reviews are the correct feature for periodic attestation of access package assignments. They allow you to set a recurrence, such as every six months, and specify reviewers. The other options either automate assignments, manage privileged access, or automate lifecycle tasks, but none provide the review and certification capability required.

Exam trap

The trap here is confusing access reviews with lifecycle workflows, which automate actions but do not provide a review and attestation process.

174
MCQmedium

You manage a Microsoft Entra tenant with Microsoft Entra Workload ID Premium licenses. A service principal named DataSyncSP accesses several Microsoft Graph endpoints on a schedule. Security requires that DataSyncSP cannot authenticate from any network except a specific Azure region's egress IP range, and that it be blocked if its credentials are used from elsewhere. What should you implement?

A.Create a Conditional Access policy for workload identities that blocks access unless the source IP is in the named location, targeting DataSyncSP.
B.Add DataSyncSP to a security group and apply a Microsoft Entra authentication strength policy to the group.
C.Assign DataSyncSP a Microsoft Entra ID Protection risk policy that blocks sign-ins with a high risk level.
D.Configure a named location and require multi-factor authentication for DataSyncSP.
AnswerA

Conditional Access for workload identities supports conditions including IP-based named locations and can target individual service principals. With Workload ID Premium, you can scope the policy specifically to DataSyncSP and block token issuance from outside the approved IP range. This directly satisfies the network-restriction requirement for a non-human identity.

Why this answer

Conditional Access for workload identities, available with Workload ID Premium, can target specific service principals and evaluate conditions such as IP-based named locations. Blocking access unless the source IP falls within the approved range enforces the regional restriction directly at token issuance. Identity Protection, MFA requirements, and authentication strengths either address different signals or do not apply to non-human identities.

Exam trap

The trap here is assuming that multi-factor authentication conditions apply to service principals, when workload identities cannot perform interactive authentication.

175
Multi-Selectmedium

You are an Identity and Access Administrator for a company that uses Microsoft Entra ID Governance. The security team wants to delegate the creation and management of access packages to department managers without granting them broad administrative rights. You need to configure the necessary roles and resources. Which two actions should you perform? (Choose two.)

Select 2 answers
A.Assign the Application Administrator role to the department managers.
B.Configure an access review for all access packages.
C.Assign the Global Administrator role to the department managers.
D.Assign the Catalog owner role to the department managers.
E.Create a catalog for each department and add the relevant resources.
AnswersD, E

Catalog owner is a delegated role that allows managers to create and manage access packages within a specific catalog, without needing tenant-wide administrative privileges. This aligns with the requirement to delegate management while adhering to least privilege. It enables them to define resources, policies, and assignments for their department's access packages.

Why this answer

To delegate access package management, you must create catalogs to group resources and assign the Catalog owner role to the managers. Catalog owners can then create and manage access packages within their catalog, achieving delegation without granting tenant-wide administrative roles. This follows the principle of least privilege and meets the scenario's requirements.

Exam trap

The trap here is assuming that any administrative role, such as Application Administrator, can manage access packages, when in fact only catalog-specific roles like Catalog owner provide the necessary permissions.

176
MCQmedium

You are managing a Microsoft Entra ID tenant. You need to create a group that automatically includes all users from the Marketing department who are also located in the London office. If a user's department changes, they must be removed from the group automatically. Which group type and membership type should you use?

A.Security group with Assigned membership
B.Microsoft 365 group with Assigned membership
C.Security group with Dynamic User membership
D.Microsoft 365 group with Dynamic Device membership
AnswerC

Dynamic User membership allows for the creation of attribute-based rules that Microsoft Entra ID evaluates periodically. By setting a rule for both department and city, the system ensures that users are only members while they meet both criteria, providing the exact automation and security required for this organizational scenario.

Why this answer

A Security group with Dynamic User membership allows you to define rules based on user attributes such as department and location. When a user's attributes change, the group membership is automatically updated, ensuring that only users from the Marketing department in London are included. This meets the requirement for automatic removal when department changes.

Exam trap

SC-300 often tests the difference between Assigned and Dynamic membership; candidates might choose Microsoft 365 group for collaboration, but the requirement is for automatic user-based membership, which is Security group with Dynamic User.

How to eliminate wrong answers

Option A is wrong because Assigned membership requires manual addition and removal, which does not meet the automatic update requirement. Option B is wrong because Microsoft 365 group with Assigned membership also requires manual management and is typically used for collaboration, not for dynamic security. Option D is wrong because Dynamic Device membership is for devices, not users, and cannot be based on user attributes like department.

177
Multi-Selectmedium

You are configuring an access package for the Marketing department. You need to define who is allowed to request this package. Which TWO options can be selected as requestors in an access package policy?

Select 2 answers
A.Users in your directory
B.Any user with a valid LinkedIn account
C.Only users who have already been assigned a P1 license
D.Users not in your directory
E.Anonymous users via a public URL
AnswersA, D

This option allows you to target existing employees, guests, or members within your own Microsoft Entra tenant. You can further refine this to 'Specific users and groups' or 'All members', ensuring that the access package is visible only to the appropriate internal audience.

Why this answer

In Microsoft Entra entitlement management, the requestor settings in an access package policy determine who can request the access package. The standard options available are 'For users in your directory', 'For users not in your directory' (connected organizations), and 'None (administrator direct assignments only)'.

Exam trap

Candidates look for specific department names within the high-level requestor policy configuration settings instead of recognizing the broad categorical options like internal or external users.

178
MCQmedium

You administer a Microsoft Entra tenant. A team of developers needs to deploy a containerized workload to Azure Kubernetes Service (AKS) that must read secrets from an Azure Key Vault without storing any credentials in the cluster. You have already enabled the OpenID Connect (OIDC) issuer and the Workload Identity feature on the AKS cluster. You need to configure the identity and permissions required for the pod to access the Key Vault. What should you do?

A.Create an app registration with a client secret, store the secret in a Kubernetes Secret, and mount it into the pod as an environment variable.
B.Enable Azure AD Pod Identity on the cluster and assign a managed identity to the pod's service account.
C.Create a user-assigned managed identity, federate it with the AKS cluster's OIDC issuer, and grant it the Key Vault Secrets User role on the Key Vault.
D.Assign the Key Vault Administrator role to the AKS cluster's kubelet identity and use the Azure Key Vault provider for Secrets Store CSI Driver.
AnswerC

A user-assigned managed identity federated with the AKS cluster's OIDC issuer allows the pod's Kubernetes service account token to be exchanged for a Microsoft Entra token. Assigning the Key Vault Secrets User role on the Key Vault grants the identity permission to read secrets. This eliminates the need to store credentials in the cluster, aligning with the workload identity pattern.

Why this answer

The correct approach is to use a user-assigned managed identity with workload identity federation, because it allows the AKS pod to authenticate to Azure services without secrets. Federating the identity with the cluster's OIDC issuer enables the pod's service account token to be trusted by Microsoft Entra ID. Assigning the Key Vault Secrets User role provides least-privilege access to read secrets.

This is the recommended pattern for AKS workloads requiring Azure resource access.

Exam trap

The trap here is assuming that the kubelet identity or legacy Pod Identity should be used for pod-level access, when the modern workload identity feature requires a federated managed identity tied to the pod's service account.

179
MCQeasy

You are an identity administrator for a Microsoft Entra ID tenant. A new application will run as an Azure Automation runbook and needs to authenticate to Microsoft Graph to read user profiles. You want to use a managed identity and grant the least privilege necessary. Which permission should you assign to the managed identity?

A.User.ReadWrite.All application permission
B.User.Read.All application permission
C.User.Read delegated permission
D.Directory.Read.All application permission
AnswerB

User.Read.All application permission allows the managed identity to read all user profiles in Microsoft Graph. This is the least privilege required for reading user profiles. Application permissions are used for daemon apps like runbooks, and this permission grants only read access, aligning with the principle of least privilege.

Why this answer

User.Read.All application permission provides read-only access to all user profiles, which is exactly what the runbook requires. Application permissions are appropriate for daemon services like runbooks. Other options either grant excessive permissions or are delegated permissions that require a user context, which is not present.

Exam trap

The trap here is selecting Directory.Read.All because it sounds similar, but it grants broader access than needed for user profiles.

180
MCQmedium

You are configuring a dynamic group in Microsoft Entra ID to automatically include users from the 'Sales' and 'Marketing' departments who are also based in 'London'. Which membership rule syntax should you use to ensure the group updates correctly?

A.(user.department -eq "Sales" -and user.department -eq "Marketing") -and (user.city -eq "London")
B.(user.department -eq "Sales" -or user.department -eq "Marketing") -and (user.city -eq "London")
C.user.department -contains "Sales" -or "Marketing" -and user.city -match "London"
D.user.department -in ["Sales", "Marketing"] -or user.city -eq "London"
AnswerB

This syntax correctly groups the department criteria with an 'OR' operator, allowing users from either team to qualify. The 'AND' operator then ensures that only those users who also have their city attribute set to London are included in the dynamic membership, meeting all the requirements of the scenario.

Why this answer

Option B is correct because it uses the proper Entra ID dynamic membership rule syntax with the -or operator to include users from either the Sales OR Marketing department, combined with -and to ensure they are also located in London. The parentheses correctly group the department conditions before applying the city filter, ensuring the logical precedence matches the requirement. This rule will evaluate as: (department equals Sales OR department equals Marketing) AND (city equals London).

Exam trap

SC-300 often tests the difference between -and and -or in dynamic group rules, and candidates may mistakenly use -and for multiple values of the same attribute, not realizing it creates an impossible condition.

How to eliminate wrong answers

Option A is wrong because it uses -and between the two department conditions, which would require a user to be in both Sales AND Marketing simultaneously—impossible for a single-valued attribute like department. Option C is wrong because it uses -contains (which checks for substring or collection membership) and -match (regex) operators that are not valid for string equality comparisons in Entra ID dynamic groups; also the syntax '-or "Marketing"' is malformed. Option D is wrong because it uses -in with an array literal, which is not supported in Entra ID dynamic membership rules, and it uses -or between department and city, which would include all users in London regardless of department, violating the requirement.

181
MCQmedium

You manage a Microsoft Entra tenant. A development team uses a service principal to deploy resources via Azure DevOps pipelines. The service principal's credentials are stored as a secret in Azure DevOps. You need to eliminate the use of secrets and implement a more secure authentication method. What should you configure?

A.Use a certificate credential instead of a client secret and upload the certificate to Azure DevOps.
B.Configure Workload Identity Federation for the service principal and set up a federated identity credential that trusts Azure DevOps.
C.Enable managed identity on the Azure DevOps organization and assign it to the service principal.
D.Create a new client secret with a longer expiration and store it in Azure Key Vault, then reference it in the pipeline.
AnswerB

Workload Identity Federation allows Azure DevOps to authenticate to Microsoft Entra ID without storing secrets. You configure a federated identity credential on the service principal that trusts tokens issued by Azure DevOps. The pipeline then uses the Azure DevOps service connection with workload identity federation, eliminating the need for a client secret.

Why this answer

Workload Identity Federation enables Azure DevOps pipelines to authenticate to Microsoft Entra ID using federated credentials instead of secrets. By configuring a federated identity credential on the service principal that trusts Azure DevOps, the pipeline can obtain tokens without storing any secret. This eliminates the risk of secret leakage and simplifies credential management.

Exam trap

The trap here is assuming that managed identities can be used for Azure DevOps, or that certificates are a secretless solution.

182
MCQhard

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. You need to configure self-service password reset (SSPR) for a group of users. The solution must require users to register at least two authentication methods before they can reset their password. Which setting should you configure?

A.Enable password writeback for SSPR
B.Number of methods required to reset: 2
C.Number of methods required to reset: 1
D.Require users to register when signing in: Yes
AnswerB

This setting specifies how many authentication methods users must verify to reset their password. Setting it to 2 ensures that users must provide two forms of verification, thereby encouraging them to register multiple methods. It directly enforces the requirement for two methods during the reset process, which aligns with the policy to enhance security.

Why this answer

The 'Number of methods required to reset' setting determines how many authentication methods a user must successfully verify to reset their password. Configuring it to 2 ensures that users must have at least two methods registered and available. This directly enforces the policy.

Other settings like registration prompts or writeback do not control the number of methods required during reset.

Exam trap

The trap here is confusing the registration prompt with the reset requirement; setting the number of methods required to reset to 2 enforces two methods, not just registration.

183
MCQmedium

Refer to the exhibit. You are configuring an Access Package in Entra Entitlement Management. What is the impact of the configuration shown in the exhibit?

A.The request is auto-approved if the manager does not respond in 24 hours.
B.Only the manager is required to approve the access request.
C.Both the manager and the resource owner must provide justification.
D.The access package is only available to internal users.
AnswerB

The configuration explicitly defines an 'approvalMode' of 'TwoStage' and lists two distinct 'approvalStages'. Therefore, the request must pass through both the manager's approval and the resource owner's approval before access is granted. The configuration cannot be satisfied by a single approver's action.

Why this answer

In Microsoft Entra entitlement management, configuring an approval workflow to require a manager as the approver ensures that only the user's manager must approve the access request before it can be fulfilled.

Exam trap

Assuming that resource owners are always required to approve access packages alongside managers, even when only the manager stage is configured.

184
Multi-Selecthard

You need to ensure that your tenant is protected against common credential-based attacks. Which THREE features should you enable or configure?

Select 3 answers
A.Smart Lockout
B.Microsoft Entra Password Protection
C.Security Defaults
D.Public Preview features for all users.
E.SMS as the only MFA method.
AnswersA, B, C

Smart Lockout helps lock out bad actors who are trying to guess passwords. It intelligently differentiates between a valid user and an attacker, locking out the attacker without affecting the legitimate user, which is a critical feature for mitigating automated brute-force attacks in the modern cloud-first environment.

Why this answer

Smart Lockout (A) is correct because it blocks brute-force and password-spray attacks by locking out an account after a configurable number of failed sign-in attempts and distinguishing valid users from attackers. Microsoft Entra Password Protection (B) is correct because it enforces a global and custom banned-password list, preventing users from setting weak or commonly breached passwords that credential-based attacks exploit. Security Defaults (C) is correct because it enables baseline protections such as requiring MFA registration for all users and blocking legacy authentication, which are common vectors for credential attacks.

Public Preview features (D) do not belong because preview features are not a security control and may introduce instability rather than protection. SMS as the only MFA method (E) does not belong because relying solely on SMS is weaker than stronger methods like Authenticator or FIDO2 and does not by itself protect against credential-based attacks.

Exam trap

The trap is picking broad or weak options like Public Preview features or SMS-only MFA, which sound security-related but do not actually mitigate credential-based attacks.

185
MCQmedium

You need to provide temporary access to an external contractor. What is the most secure way to manage this using Microsoft Entra ID?

A.Use Microsoft Entra B2B collaboration and configure an access review.
B.Create a local user account in the tenant.
C.Create a shared mailbox for the contractor.
D.Share your own administrative credentials with the contractor.
AnswerA

Access reviews allow you to periodically ask the resource owner if the contractor still needs access. If the answer is no, or if they don't respond, the guest account access can be automatically removed, ensuring that external identities do not persist in your environment beyond their legitimate business requirement.

Why this answer

Microsoft Entra B2B collaboration lets you invite the contractor as a guest user in your tenant, where they authenticate with their own credentials and you control access via conditional access and access reviews. Configuring an access review ensures the guest's access is periodically re-certified and automatically removed when no longer needed, which is the most secure and auditable approach.

Exam trap

SC-300 often tests whether candidates choose B2B with governance controls over creating local accounts — the trap is picking the 'simplest' option (local account) instead of the most secure, auditable one.

How to eliminate wrong answers

Option B is wrong because creating a local user account in the tenant gives the contractor a permanent credential in your directory, increasing attack surface and complicating offboarding. Option C is wrong because a shared mailbox is not an identity and does not provide secure, auditable access to applications. Option D is wrong because sharing admin credentials violates least privilege and accountability, and is a critical security anti-pattern.

186
MCQmedium

Your organization uses Microsoft Entra ID Protection. You observe that several users are being blocked because their 'User Risk' level is High. You need to allow these users to self-remediate their risk and regain access without administrative intervention. What should you do?

A.Configure a Sign-in risk policy to require MFA.
B.Configure a User risk policy to require a password change.
C.Manually dismiss the risk for each user in the portal.
D.Disable the User risk policy entirely.
AnswerB

A User risk policy set to require a password change allows users to self-remediate. By successfully changing their password through a secure, verified process, the user demonstrates control over the account and invalidates potentially leaked credentials, which triggers Entra ID to automatically lower their risk level to 'None'.

Why this answer

A User risk policy in Entra ID Protection can be configured to require a secure password change when risk is detected. This allows the user to self-remediate by proving identity (typically via MFA) and setting a new password, which clears the risk and restores access without admin involvement — exactly what the scenario requires.

Exam trap

SC-300 often tests the sign-in risk vs. user risk distinction — candidates pick the MFA policy (A) because MFA is the familiar remediation, but MFA only clears sign-in risk, not user risk, which requires a password change.

How to eliminate wrong answers

Option A is wrong because a Sign-in risk policy responds to sign-in risk (suspicious session characteristics), not user risk (compromised credentials) — it would not remediate the High User Risk state. Option C is wrong because manually dismissing risk requires administrative intervention, which the scenario explicitly wants to avoid, and it does not scale. Option D is wrong because disabling the policy removes protection entirely, leaving compromised accounts unmitigated — a security regression, not a remediation.

187
MCQmedium

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. The security team requires that all new user accounts are automatically assigned a random initial password that must be changed at first sign-in. You create a new user in the Microsoft Entra admin center. Which setting should you configure to meet this requirement?

A.Configure a password expiration policy that expires passwords after 30 days.
B.Enable the 'Require this user to change their password when they first sign in' option.
C.Enable self-service password reset for the user.
D.Assign the User Administrator role to the new user.
AnswerB

This option forces the user to change their password at the next sign-in, which is exactly the requirement. When creating a user, the admin can select this checkbox, and the user will be prompted to change the password upon first authentication. It works for both auto-generated and manually specified passwords, ensuring the initial password is temporary.

Why this answer

The requirement is to force a password change at first sign-in for new accounts. In Microsoft Entra ID, when creating a user, the administrator can select the option to require the user to change their password at first sign-in. This ensures the initial password is temporary and must be replaced immediately, satisfying the security policy without granting unnecessary privileges or relying on separate policies.

Exam trap

The trap here is confusing password expiration or self-service password reset with the explicit first sign-in password change requirement.

188
MCQmedium

Your organization has several financial applications that contain sensitive data. You need to ensure that users are prompted for multi-factor authentication only when they attempt to access these specific applications from outside the corporate network. Which feature should you implement to meet this requirement with the least amount of administrative effort?

A.Security Defaults
B.Conditional Access policies
C.Microsoft Entra ID Protection
D.Authentication Methods Policy
AnswerB

Conditional Access allows administrators to create specific rules that evaluate signals like user location and application metadata before granting access. This ensures that MFA is enforced only when a user attempts to access sensitive financial tools from outside the corporate network, effectively minimizing user friction while maintaining high security standards.

Why this answer

Conditional Access policies allow for granular control based on signals such as the specific application being accessed and the user's network location. By creating a policy that targets the financial applications and excludes the corporate network (Named Locations), you can enforce MFA only for external access, which is the most efficient way to meet the requirement.

Exam trap

Security Defaults is frequently the answer for 'least administrative effort' questions, but it is an 'all-or-nothing' setting. It cannot be scoped to specific applications or specific network locations, making it unsuitable for this requirement.

189
Multi-Selectmedium

A company wants to implement advanced identity management features for their users. You are evaluating the differences between Microsoft Entra ID P1 and P2 licenses. Which TWO features are ONLY available with the Microsoft Entra ID P2 license?

Select 2 answers
A.Self-Service Password Reset (SSPR) for cloud users
B.Conditional Access based on user location and device state
C.Microsoft Entra ID Protection (Risk-based Conditional Access)
D.Application Proxy for accessing on-premises web applications
E.Privileged Identity Management (PIM)
AnswersC, E

Identity Protection, which includes the ability to trigger policies based on 'User Risk' and 'Sign-in Risk' levels (High, Medium, Low), is a premium feature exclusive to the P2 license. It uses machine learning to detect compromised credentials and anomalous sign-in patterns to automatically protect the organization's identities.

Why this answer

Microsoft Entra ID P2 includes all P1 features plus advanced identity protection and governance capabilities. Understanding these differences is crucial for administrators to ensure they have the necessary licensing for high-security environments, specifically regarding automated risk detection and administrative access control through Privileged Identity Management.

Exam trap

Candidates often incorrectly include 'Conditional Access' or 'Self-Service Password Reset' as P2-only features. While P2 enhances these, the base functionality exists in P1, leading to confusion during license evaluation questions.

190
Multi-Selectmedium

Your company uses Azure Kubernetes Service (AKS). You want to implement workload identity to allow pods to access Azure resources without using static credentials. Which TWO steps must you perform to enable this?

Select 2 answers
A.Enable the OIDC issuer and workload identity on the existing AKS cluster.
B.Install the Azure AD Connect tool on every worker node in the cluster.
C.Create a federated identity credential for the Managed Identity pointing to the Service Account.
D.Generate a client secret for the Managed Identity and inject it as a Kubernetes Secret.
E.Assign the Global Administrator role to the AKS cluster service principal.
AnswersA, C

Enabling the OIDC issuer is the foundational requirement for workload identity in AKS. It provides a unique URL that Azure AD uses to verify the identity of the pods. Without this feature enabled, the cluster cannot issue the OIDC tokens required to authenticate with Azure services via federation.

Why this answer

To enable AKS workload identity, you must first enable the OIDC issuer and workload identity features on the AKS cluster. Once the cluster is prepared, you must create a managed identity and establish a federated identity credential that maps the Kubernetes Service Account to the Azure Managed Identity. These steps create the trust relationship necessary for pods to safely authenticate to Azure services using short-lived tokens.

Exam trap

Many candidates mistakenly select 'Azure AD Pod Identity' which is the older, deprecated method, or fail to realize both the OIDC issuer and the federated credential are required.

191
Multi-Selecthard

You are configuring Entra ID PIM for a group of administrators. You need to ensure that when they activate a privileged role, they provide a justification and perform MFA. Which TWO settings should you configure?

Select 2 answers
A.Require Azure MFA on activation
B.Require justification on activation
C.Require ticket number on activation
D.Require approval on activation
E.Enable persistent assignment
AnswersA, B

Enforcing Multi-Factor Authentication during the activation process ensures that the user is who they claim to be at the exact moment of elevation. This mitigates the risk of a compromised account performing privileged actions without an additional layer of verification, strengthening the overall administrative access security.

Why this answer

Privileged Identity Management (PIM) settings allow administrators to enforce specific security requirements for role activations. By configuring the activation requirement for MFA, you ensure the identity is verified during the activation event. Requiring a justification provides an audit trail for why the privilege was elevated.

These controls are foundational for the principle of least privilege, ensuring that high-level administrative access is not only transient but also properly documented and verified.

Exam trap

Candidates often forget that PIM settings are configured at the role assignment level, and they fail to select both MFA and justification, thinking one security control is sufficient for compliance.

192
MCQmedium

Your organization has a hybrid environment with Microsoft Entra Connect syncing on-premises Active Directory users to the cloud. You need to update the 'Department' attribute for a synchronized user. When you attempt to change this in the Microsoft Entra admin center, the field is grayed out. What is the most appropriate action to resolve this?

A.Modify the attribute in the on-premises Active Directory and wait for the next synchronization cycle.
B.Assign the User Administrator role to your account to override the synchronization lock.
C.Disable the Microsoft Entra Connect sync temporarily to allow direct edits in the cloud portal.
D.Use the Microsoft Graph PowerShell module to force the attribute update in the cloud.
AnswerA

On-premises Active Directory serves as the source of authority for synchronized objects, meaning changes made locally are propagated to the cloud during the next sync cycle. Modifying these attributes in the cloud is blocked to prevent data mismatching between the local directory and the cloud-based Microsoft Entra ID instance.

Why this answer

When a user object is synchronized from on-premises Active Directory via Microsoft Entra Connect, the cloud object is mastered on-premises. Attributes like Department are authoritative in AD, so the only supported way to change them is to edit the source object in AD and let the next sync cycle (default 30 minutes for delta sync) propagate the change. Direct cloud edits are blocked because they would be overwritten on the next sync, which is why the field appears grayed out.

Exam trap

SC-300 often tests the misconception that an Entra ID administrative role (like User Administrator) or a Graph API call can override the on-premises source of authority for synchronized objects — candidates must remember that synced attributes are mastered on-premises and cloud edits are blocked or overwritten.

How to eliminate wrong answers

Option B is wrong because assigning the User Administrator role grants administrative permissions in Entra ID but does not override the source-of-authority lock on synchronized attributes — role assignment cannot make a cloud-mastered edit stick. Option C is wrong because disabling Entra Connect sync to allow cloud edits breaks the synchronization model, causes the object to become cloud-mastered only temporarily, and will either create conflicts or be overwritten when sync is re-enabled; it is not a supported administrative practice. Option D is wrong because Microsoft Graph PowerShell writes to the same cloud object and will be rejected or overwritten for a synchronized attribute — the API respects the same source-of-authority rules as the portal.

193
MCQmedium

You need to reduce the attack surface by ensuring that only compliant devices can access Microsoft 365. What should you configure?

A.A device compliance policy in Intune
B.A Conditional Access policy requiring compliant devices
C.An Azure AD Identity Protection policy
D.An authentication strength policy
AnswerB

This policy links the Entra ID access control to the Intune device compliance status. When a user tries to access Microsoft 365, Entra ID verifies the device status in Intune. If the device is not marked compliant, the access is blocked, effectively enforcing the security requirement.

Why this answer

A Conditional Access policy requiring compliant devices ensures that only devices marked as compliant by Intune can access Microsoft 365 resources. This directly reduces the attack surface by blocking access from non-compliant or unmanaged devices. The policy evaluates device compliance status at sign-in and enforces access controls.

Exam trap

SC-300 often tests the confusion between device compliance policies (which define compliance) and Conditional Access policies (which enforce access based on compliance).

How to eliminate wrong answers

Option A is wrong because a device compliance policy alone only defines compliance rules but does not enforce access; it must be combined with Conditional Access. Option C is wrong because Azure AD Identity Protection focuses on user risk and sign-in risk, not device compliance. Option D is wrong because authentication strength policies control authentication methods (e.g., MFA), not device compliance.

194
MCQhard

You manage a Microsoft Entra ID tenant. You need to enable self-service password reset (SSPR) for a group of users who are on-premises and synced from Active Directory. The users must be able to reset their passwords from the Windows login screen. What should you do first?

A.Enable password writeback in Microsoft Entra Connect.
B.Configure the SSPR authentication methods policy to require two methods.
C.Assign the Password Administrator role to the users.
D.Enable Azure AD Connect Health for synchronization services.
AnswerA

For synced users to reset their on-premises passwords via SSPR, password writeback must be enabled in Microsoft Entra Connect. This allows password changes in the cloud to be written back to on-premises Active Directory. Without it, users can reset their cloud password but it will not synchronize, causing a mismatch and login failure on-premises.

Why this answer

For synced users to reset their passwords using SSPR and have the new password work on-premises, password writeback must be enabled in Microsoft Entra Connect. This feature ensures that password changes in the cloud are written back to the on-premises directory. Other options address authentication methods or roles but do not enable the necessary writeback functionality.

Exam trap

The trap here is focusing on SSPR configuration or role assignment while overlooking the need for password writeback to synchronize the password change to the on-premises directory.

195
MCQhard

Refer to the exhibit. This Conditional Access policy uses a specific Authentication Strength. If the ID shown corresponds to the 'Phishing-resistant MFA' built-in strength, which authentication method will NOT satisfy the policy?

A.Microsoft Authenticator push notification with number matching.
B.Windows Hello for Business.
C.FIDO2 security key.
D.Microsoft Entra Certificate-based authentication (Multi-factor).
AnswerA

Push notifications, even with number matching, are not considered phishing-resistant because they do not use hardware-bound keys that verify the domain origin of the request. While they are significantly more secure than SMS or voice, they are excluded from the 'Phishing-resistant MFA' strength. This method is included in the 'Multifactor authentication' strength but falls short of the phishing-resistant requirement.

Why this answer

The 'Phishing-resistant MFA' authentication strength requires methods that are resistant to phishing, such as Windows Hello for Business, FIDO2 security keys, and certificate-based authentication. Microsoft Authenticator push notification with number matching is considered MFA but is not phishing-resistant because it can be relayed by an attacker in real time. Therefore, it will NOT satisfy the policy.

Exam trap

SC-300 often tests whether candidates assume all MFA methods are phishing-resistant, so knowing that push notifications (even with number matching) are not phishing-resistant is a common trap.

How to eliminate wrong answers

Option B is wrong because Windows Hello for Business is a phishing-resistant method that satisfies the Phishing-resistant MFA strength. Option C is wrong because FIDO2 security keys are explicitly phishing-resistant and satisfy the strength. Option D is wrong because Microsoft Entra Certificate-based authentication (Multi-factor) is also classified as phishing-resistant and satisfies the strength.

196
MCQhard

You manage a Microsoft Entra ID tenant. A security team reports that a service principal created three months ago is still active and has been granted the User.Read.All Microsoft Graph application permission. The service principal is not used by any application, and its credentials have not been rotated. You need to identify the risk and mitigate it. What should you do first?

A.Assign a Conditional Access policy to the service principal.
B.Delete the service principal immediately.
C.Rotate the service principal's client secret.
D.Review the sign-in logs for the service principal to confirm whether it is actively used.
AnswerD

Reviewing sign-in logs for the service principal provides evidence of whether it is actually being used. Microsoft Entra ID logs service principal sign-ins, and you can filter by the service principal's object ID. If there are no recent sign-ins, it is likely unused and can be safely disabled or removed. This step is essential before taking any disruptive action.

Why this answer

The first step is to determine whether the service principal is actually used by reviewing its sign-in logs. This evidence-based approach prevents accidental disruption of legitimate workloads. If the logs show no recent activity, you can then proceed to disable or remove the service principal and its permissions, reducing the attack surface.

Exam trap

The trap here is jumping to deletion or secret rotation without first verifying usage through sign-in logs, which could break an active application.

197
Multi-Selecthard

You need to implement Custom Security Attributes in Microsoft Entra ID to store sensitive employee data that should not be visible to standard administrators. Which TWO requirements must be met to manage these attributes?

Select 2 answers
A.You must be assigned the Attribute Definition Administrator role.
B.You must be assigned the Attribute Assignment Administrator role.
C.The tenant must have at least a Microsoft Entra ID Free edition.
D.The attributes must be stored in the 'Default' attribute set.
E.Global Administrators can view all custom attributes by default.
AnswersA, B

The Attribute Definition Administrator role is required to create the schema and define the attributes themselves within the tenant. Standard administrative roles, including Global Administrator, do not have the inherent permissions to define or modify the structure of custom security attributes without this specific assignment.

Why this answer

Custom Security Attributes provide a way to store specialized metadata with enhanced access controls. Unlike standard directory attributes, they are not visible by default to Global Administrators. Implementing them correctly requires specific role assignments and an understanding of how attribute sets function to isolate sensitive information from unauthorized viewing.

Exam trap

Candidates assume Global Administrators automatically have access to Custom Security Attributes, failing to realize these require specific, explicit role assignments regardless of existing high-level administrative permissions in the tenant.

198
MCQmedium

Refer to the exhibit. What is the most likely cause of this sign-in failure for the web application?

A.The redirect URI is missing from the App Registration configuration.
B.The user does not have sufficient permissions to access the application.
C.The client secret has expired.
D.The user is using an unsupported browser.
AnswerA

The Entra ID service rejects the authentication request because the URI provided by the app does not match the allowed list. Adding the correct URL to the App Registration's Redirect URIs section will resolve the mismatch and allow the authentication flow to complete successfully for the users.

Why this answer

The most common cause of an AADSTS50011 error (redirect URI mismatch) during a web app sign-in is that the redirect URI configured in the application code does not match any redirect URI registered in the App Registration. Entra ID rejects the authorization request because the reply URL is not on the allowlist for that client ID.

Exam trap

SC-300 often tests whether candidates can distinguish AADSTS50011 (redirect URI mismatch) from AADSTS7000215 (invalid client secret) or AADSTS65001 (consent/permission) — the error code in the exhibit is the key clue.

How to eliminate wrong answers

Option B is wrong because insufficient permissions typically produce an AADSTS65001 or 403 error after authentication, not a redirect URI mismatch during the authorization request. Option C is wrong because an expired client secret causes an AADSTS7000215 invalid_client error during token exchange, not a redirect URI error. Option D is wrong because an unsupported browser would produce a rendering or compatibility issue, not an Entra ID protocol error about redirect URIs.

199
MCQhard

You are configuring Workload Identity Federation for an application hosted on an on-premises Kubernetes cluster. What is the primary benefit of this configuration over using a standard service principal with a secret?

A.It allows the on-premises cluster to bypass Microsoft Entra authentication entirely.
B.It automatically synchronizes on-premises service accounts to Microsoft Entra ID.
C.It eliminates the need to store and rotate Azure secrets in the on-premises cluster.
D.It provides a faster network connection between on-premises and Azure services.
AnswerC

By using federation, the on-premises application uses its own native OIDC token to authenticate to Azure. Since there is no client secret or certificate stored in the Kubernetes cluster, there is no risk of secret leakage from the cluster and no administrative burden for rotation.

Why this answer

Workload Identity Federation lets an external identity provider (like an on-premises Kubernetes cluster's OIDC issuer or a service account token) exchange a trusted token for a short-lived Microsoft Entra access token. Because the trust is established via federated credentials on an app registration or managed identity, no client secret or certificate needs to be stored in the cluster. This removes the secret rotation burden and the risk of credential leakage from the on-premises environment.

Exam trap

SC-300 often tests the misconception that Workload Identity Federation removes the need for authentication entirely or performs directory synchronization, when in fact it only replaces long-lived secrets with short-lived federated tokens.

How to eliminate wrong answers

Option A is wrong because the cluster still authenticates to Microsoft Entra ID — federation replaces the secret, not the authentication step. Option B is wrong because Workload Identity Federation does not synchronize on-premises service accounts into Entra ID; that is the role of Microsoft Entra Connect or Cloud Sync. Option D is wrong because federation is an authentication mechanism and has no bearing on network latency or routing between on-premises and Azure.

200
Multi-Selectmedium

You are configuring self-service password reset (SSPR) for a group of users in Microsoft Entra ID. You need to ensure that users can reset their passwords using either their mobile phone or their office phone. Which two authentication methods should you enable? (Choose two.)

Select 2 answers
A.Security questions
B.Office phone
C.Mobile phone (SMS or voice call)
D.Mobile app notification
E.Email
AnswersB, C

The 'Office phone' method enables users to receive a voice call at their office phone number. This meets the requirement to use an office phone for password reset. It is a valid authentication method for SSPR and is distinct from mobile phone.

Why this answer

To allow users to reset passwords using a mobile phone or office phone, you must enable the 'Mobile phone' and 'Office phone' authentication methods. These methods support SMS, voice call, or both, depending on configuration. Mobile app notification, email, and security questions do not use phone numbers and thus do not satisfy the requirement.

Exam trap

The trap here is confusing 'Mobile app notification' with mobile phone methods, but app notifications do not use the phone number and are not phone-based authentication.

201
MCQeasy

You delete an Azure Logic App that was configured with a system-assigned managed identity. What happens to the managed identity in Microsoft Entra ID?

A.The identity remains in the tenant and must be manually deleted.
B.The identity is automatically deleted from Microsoft Entra ID.
C.The identity is disabled for 30 days before being permanently deleted.
D.The identity is converted into a standard service principal.
AnswerB

System-assigned managed identities are inextricably linked to the Azure resource they were created for. When the Logic App is deleted, Azure automatically triggers the deletion of the corresponding identity in Microsoft Entra ID, ensuring no unused identities are left behind.

Why this answer

The lifecycle management of system-assigned managed identities is one of their primary administrative benefits. Unlike service principals or user-assigned identities, they do not require manual cleanup, which helps maintain a clean and secure identity environment by preventing the existence of orphaned identities.

Exam trap

Candidates often assume the identity persists in Entra ID as a 'dangling' object, failing to recognize that system-assigned identities are tightly coupled to the lifecycle of the Azure resource.

202
MCQmedium

You are an Identity and Access Administrator for a retail company using Microsoft Entra ID. The company has a policy that all guest users must have their access reviewed every 60 days. You have an access review configured for a group that contains both internal and guest users. You need to ensure that only guest users are reviewed and that if no decision is made, their access is removed. What should you do?

A.In the access review settings, set the scope to 'Guest users only' and configure 'If reviewers don't respond' to 'Remove access'.
B.Configure the access review to include all users, but instruct reviewers to only review guest users. Set 'If reviewers don't respond' to 'Remove access'.
C.Use a Lifecycle Workflow to run a custom task extension that queries for guest users and removes their access if no review is recorded within 60 days.
D.Create a dynamic group that includes only guest users, assign the access review to that group, and set 'If reviewers don't respond' to 'Remove access'.
AnswerA

Access reviews in Microsoft Entra ID allow you to scope the review to guest users only, which directly addresses the policy. Setting the fallback action to remove access ensures that if reviewers do not respond, guest users lose access. This is the correct and efficient configuration.

Why this answer

Access reviews support scoping to guest users only, which ensures that only external users are reviewed according to policy. Configuring the fallback action to remove access enforces the requirement that non-responsive reviews result in access removal. This leverages built-in functionality without additional custom development.

Exam trap

The trap here is thinking that you need to create a separate group for guests; access reviews can be scoped to guest users within an existing group.

203
MCQmedium

You are managing access packages for a Finance department. You need to prevent users who already have access to the 'Payroll Processing' access package from requesting the 'External Audit' access package to maintain separation of duties. What should you configure?

A.Mark the access packages as incompatible with each other.
B.Create a Conditional Access policy to block the specific users.
C.Assign a 'Deny' permission to the Audit group for Payroll users.
D.Configure an access review to remove users with both packages.
AnswerA

Using the incompatible access packages feature is the native way to enforce separation of duties in Entitlement Management. Once configured, the system automatically blocks a user from requesting or being assigned a second package if they already possess the first, providing a robust automated compliance check.

Why this answer

In Microsoft Entra Entitlement Management, access packages can be marked as incompatible with each other. This configuration enforces separation of duties by preventing a user from requesting or holding assignments to both packages simultaneously. When incompatible, the system blocks the request if the user already has the other package, directly addressing the requirement.

Exam trap

SC-300 often tests the difference between preventive and reactive controls; candidates may confuse access reviews (reactive) with incompatible access packages (preventive).

How to eliminate wrong answers

Option B is wrong because Conditional Access policies control authentication and session access, not access package assignment eligibility; they cannot prevent a user from requesting an access package. Option C is wrong because assigning a 'Deny' permission to a group is not a native Entra ID feature for access packages; permissions are managed via roles and access reviews, not direct deny assignments. Option D is wrong because an access review is a periodic attestation process that removes access after the fact, not a preventive control that blocks the initial request.

204
MCQmedium

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. A new security policy mandates that all user accounts must be created with a temporary password that the user must change at first sign-in. You create a new user by using the Microsoft Entra admin center. Which setting should you configure to enforce this requirement?

A.Enable self-service password reset for the user.
B.Configure a Conditional Access policy that requires password change.
C.Set the 'Require this user to change their password when they first sign in' option to Yes.
D.Assign the user a Password Reset Administrator role.
AnswerC

This option directly enforces a password change at first sign-in. When enabled, the user is prompted to update their password immediately after the initial authentication, satisfying the security policy. It is the standard method in Microsoft Entra ID for ensuring temporary passwords are replaced, and it works for both cloud-only and synced users when configured during creation.

Why this answer

The requirement is to force a password change at first sign-in. In Microsoft Entra ID, when creating a user, you can select the option to require a password change at next sign-in. This ensures the temporary password is replaced immediately.

Other methods like role assignments, Conditional Access, or SSPR do not enforce this specific behavior and are therefore incorrect.

Exam trap

The trap here is assuming that Conditional Access or SSPR can enforce a password change at first sign-in, when only the user creation setting does.

205
Multi-Selecthard

Which TWO settings must be configured in an access package to allow users from a specific external partner organization to request access while ensuring all other external users are blocked?

Select 2 answers
A.Add the partner's domain to the 'Connected Organizations' list in Entitlement Management.
B.Create a Conditional Access policy that excludes the partner's IP address range.
C.Enable the 'Allow all external users' setting in the External Identities provider settings.
D.Configure the access package policy for 'Users not in your directory' and select 'Specific connected organizations'.
E.Set the access package 'Hidden' attribute to 'No' so it is visible in the MyAccess portal.
AnswersA, D

Adding a domain as a 'Connected Organization' is a prerequisite for targeted external access. It allows Microsoft Entra to recognize the external tenant and makes it available as a selectable entity when configuring access package policies, enabling a scoped trust relationship with that specific partner.

Why this answer

Option A is correct because adding the partner's domain to the Connected Organizations list in Entitlement Management establishes the trusted external tenant that can be referenced when scoping access package policies. Option D is correct because configuring the access package policy for 'Users not in your directory' and selecting 'Specific connected organizations' restricts requests to only those approved partner organizations, thereby blocking all other external users. Option B is incorrect because a Conditional Access policy excluding an IP range does not scope access package requests to a specific partner organization and is not the mechanism for limiting external requesters.

Option C is incorrect because enabling 'Allow all external users' would permit any external user, which is the opposite of the required restriction. Option E is incorrect because the 'Hidden' attribute only controls visibility in the MyAccess portal and does not restrict which external organizations can request access.

Exam trap

SC-300 often tests the combination of connected organizations and access package policies; candidates might think one setting is sufficient, but both are required to restrict to specific partners.

206
MCQmedium

You are managing a highly sensitive Azure subscription. You have configured PIM to require approval for the 'Owner' role. A user requests activation of this role. As the designated approver, you are unavailable. You need to ensure that the request can still be processed. What is the best way to handle this during the PIM configuration phase?

A.Assign the 'Global Administrator' role to the requesting user permanently.
B.Configure a group as the approver for the role in PIM settings.
C.Set the activation duration to 24 hours to reduce the number of requests.
D.Disable the 'Require approval' setting and use 'Require MFA' only.
AnswerB

In PIM, you can assign a group as the approver instead of a single individual. This allows any member of that group to approve or deny requests. It provides redundancy and ensures that activation requests for sensitive roles like 'Owner' do not get stuck when a specific person is unavailable.

Why this answer

While the explanation mentions 'designating multiple approvers', it fails to explain that PIM allows assigning multiple users or groups as approvers. Using a group is the best practice for scalability and management, as it avoids the need to update PIM settings every time an individual approver changes roles or leaves the organization.

Exam trap

Candidates often assume that PIM approval must be assigned to a single specific user, leading them to look for 'delegate' or 'proxy' settings that do not exist in PIM.

207
MCQmedium

You have a hybrid environment. You need to ensure that only devices that are Hybrid Azure AD joined can access sensitive data. What should you configure?

A.Intune device enrollment
B.Conditional Access grant control
C.Azure AD Connect Health
D.Identity Protection user risk
AnswerB

In Conditional Access policies, you can select the 'Require hybrid Azure AD joined device' grant control. This setting forces Entra ID to perform a check on the device's object status. If the device is not confirmed as Hybrid Azure AD joined, the policy blocks access to the resources.

Why this answer

Conditional Access grant controls allow you to require that devices be Hybrid Azure AD joined before granting access to cloud apps. By creating a Conditional Access policy that targets sensitive applications and sets the grant control to 'Require Hybrid Azure AD joined device', you enforce that only compliant devices can access the data. This is the direct method to meet the requirement.

Exam trap

SC-300 often tests the difference between device enrollment and Conditional Access enforcement; candidates may choose Intune enrollment thinking it restricts access, but only Conditional Access grant controls enforce it.

How to eliminate wrong answers

Option A is wrong because Intune device enrollment alone does not enforce access control; it only registers devices for management. Without a Conditional Access policy, enrolled devices are not required to access resources. Option C is wrong because Azure AD Connect Health monitors synchronization and provides insights, but it does not enforce device-based access restrictions.

Option D is wrong because Identity Protection user risk evaluates sign-in risk and can block or require password change, but it does not check device join status.

208
MCQeasy

A security administrator needs to review which service principals in a Microsoft Entra tenant have highly privileged directory role assignments, such as Global Administrator. The administrator wants a report that lists the role assignments and their members. Which Microsoft Entra feature should the administrator use?

A.Microsoft Entra audit logs filtered by the role management category.
B.The Roles and administrators blade in the Microsoft Entra admin center.
C.The Microsoft Entra provisioning logs for enterprise applications.
D.Microsoft Entra sign-in logs filtered by service principal sign-ins.
AnswerB

The Roles and administrators blade lists each directory role and, when opened, shows all current members, including users, groups, and service principals. This gives the administrator an immediate, accurate view of which service principals hold privileged roles such as Global Administrator, making it the right tool for this review.

Why this answer

The Roles and administrators blade in the Microsoft Entra admin center provides a current inventory of each directory role and its assigned members, including service principals. Opening a privileged role such as Global Administrator immediately shows whether any workload identities hold it, which is exactly the consolidated view the administrator requires.

Exam trap

The trap here is confusing activity logs, such as audit or sign-in logs, with the authoritative role assignment view, which is found under Roles and administrators.

209
MCQmedium

You need to enable Self-Service Password Reset (SSPR) for a pilot group of 50 users. You want to ensure they can reset their passwords from the Windows login screen. What is a prerequisite for this specific functionality?

A.The users' devices must be Microsoft Entra joined or Microsoft Entra hybrid joined.
B.Users must have at least three different authentication methods registered in their profile.
C.The 'Writeback passwords to on-premises AD' option must be disabled for the pilot group.
D.The pilot group users must be assigned the 'Password Administrator' role in Entra ID.
AnswerA

To reset a password directly from the Windows login screen, the device must have a trust relationship with Microsoft Entra ID. This is achieved through Entra Join or Hybrid Join, which allows the login UI to securely communicate with the SSPR service before the user has authenticated.

Why this answer

To enable SSPR on the Windows login screen, the devices must be Microsoft Entra joined or Microsoft Entra hybrid joined. This allows the Windows login screen to communicate with the Entra ID service to facilitate the password reset process.

Exam trap

Candidates might assume that SSPR only requires a license or group membership, forgetting the specific device join state requirement for the Windows login screen integration.

210
MCQmedium

An organization has an Azure Function app that needs to access secrets in Azure Key Vault. The developers want to avoid manual secret management for the application itself. What should be implemented to ensure the highest security while minimizing administrative overhead for secret rotation?

A.System-assigned managed identity
B.User-assigned managed identity
C.Service Principal with a client secret
D.Application Registration with a certificate
AnswerA

System-assigned identities are tied to the specific resource and are automatically cleaned up when the resource is deleted. This reduces the risk of orphaned identities and eliminates the need for manual secret rotation, as Microsoft Entra ID handles the credential management and rotation process automatically for the resource.

Why this answer

A system-assigned managed identity is the best choice because it provides an identity for the Azure Function app that is automatically managed by Azure, eliminating the need for manual secret management. The identity is tied to the app's lifecycle and can be granted access to Key Vault. This minimizes administrative overhead and ensures the highest security since there are no credentials to rotate.

Exam trap

The trap is choosing user-assigned managed identity thinking it is more flexible, but the question emphasizes minimizing administrative overhead, which system-assigned provides by being automatically managed and lifecycle-bound to the app.

How to eliminate wrong answers

Option B is wrong because a user-assigned managed identity is a separate Azure resource that must be created and managed, adding administrative overhead compared to system-assigned. Option C is wrong because a service principal with a client secret requires manual secret rotation, which the developers want to avoid. Option D is wrong because an application registration with a certificate still requires certificate management and rotation, though it is more secure than a secret.

211
MCQmedium

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 register for multi-factor authentication (MFA) using SMS or voice call. You need to configure the authentication methods policy to meet this requirement. What should you do?

A.In the authentication methods policy, disable the SMS and Voice call methods for all users.
B.In the authentication methods policy, target all users and set the state of SMS and Voice call to 'Disabled', and also disable the legacy MFA and SSPR settings for these methods.
C.Create a Conditional Access policy that blocks users from registering security information using SMS or Voice call.
D.In the authentication methods policy, enable only the Microsoft Authenticator method and disable all other methods.
AnswerB

To fully prevent registration and use of SMS and Voice call, you must disable them in both the authentication methods policy and the legacy MFA/SSPR settings. The authentication methods policy controls the new registration experience, but legacy settings can still allow registration if not disabled. By disabling in both places, you ensure users cannot register or use these methods. This meets the requirement comprehensively.

Why this answer

To prevent users from registering for MFA using SMS or Voice call, you must disable these methods in both the authentication methods policy and the legacy MFA/SSPR settings. The authentication methods policy controls the modern registration experience, while legacy settings can still allow registration if not disabled. Disabling in both ensures users cannot register or use these methods.

Other options either do not fully block registration or are too broad.

Exam trap

The trap here is assuming that disabling methods in the authentication methods policy alone is sufficient, when legacy MFA and SSPR settings can still permit registration.

212
MCQmedium

You need to automate the rotation of a certificate used for service principal authentication. Which tool should you use to store the private key and manage the rotation lifecycle?

A.Azure Storage Account
B.Azure Key Vault
C.Azure App Configuration
D.Azure DevOps Secret Variables
AnswerB

Azure Key Vault is specifically designed to store sensitive material like certificate private keys. It supports automated certificate management, including integration with certificate authorities for renewal, and provides secure access control policies to ensure that only authorized services can retrieve or manage these cryptographic assets.

Why this answer

Azure Key Vault is the industry-standard service for managing cryptographic keys and secrets. For service principal certificates, the Key Vault can store the certificate, and integrated automation (such as Logic Apps) can trigger renewal and updates to the Azure AD application registration, ensuring the identity remains secure without manual intervention.

Exam trap

Candidates often select Azure Key Vault but fail to realize that Key Vault itself does not natively 'push' updates to Entra ID, requiring an automation tool like Logic Apps to complete the workflow.

213
MCQmedium

You administer a Microsoft Entra ID tenant. A partner organization needs to call your custom API, which is registered in your tenant as an app registration. The partner will use their own Microsoft Entra tenant to obtain tokens. You must configure the app registration to trust tokens issued by the partner's tenant without requiring a client secret. What should you do?

A.Enable multi-tenant on the app registration and configure the partner as a guest user.
B.Add the partner's service principal as an owner of the app registration.
C.Configure a federated identity credential on the app registration, specifying the partner tenant's issuer and subject.
D.Create a new client secret and share it securely with the partner.
AnswerC

Federated identity credentials allow an app registration to trust tokens from an external identity provider, such as another Microsoft Entra tenant. By configuring the issuer and subject, the app registration can validate tokens without a client secret. This is the correct approach for cross-tenant workload identity federation.

Why this answer

Configuring a federated identity credential on the app registration establishes a trust relationship with the partner's Microsoft Entra tenant. The app registration validates tokens issued by that tenant based on the specified issuer and subject, eliminating the need for a client secret. This approach aligns with the principle of secretless authentication and least privilege.

Exam trap

The trap here is confusing multi-tenant app registration with federated identity credentials; multi-tenant enables user sign-in, not workload token trust.

214
Multi-Selecthard

You are configuring Microsoft Entra Connect to synchronize objects from an on-premises Active Directory forest to Microsoft Entra ID. You need to ensure that only users in specific Organizational Units (OUs) are synchronized, and among those users, only those with the 'ExtensionAttribute1' set to 'SyncMe' are included. Which TWO filtering methods must you configure?

Select 2 answers
A.Group-based filtering using a security group.
B.Domain and OU-based filtering.
C.Password hash synchronization filtering.
D.Attribute-based filtering.
E.User writeback filtering.
AnswersB, D

This filtering method is configured during the initial setup or via the installation wizard. It allows you to select or deselect specific OUs in your Active Directory hierarchy. By selecting only the specific OUs mentioned, you prevent the sync engine from processing any objects located in other parts of the directory.

Why this answer

To achieve this granular level of control, you must combine two different filtering layers. Domain and OU-based filtering limits the scope of objects that the sync engine even considers from the source directory. Attribute-based filtering then applies a logic-based rule to the objects within those OUs to further refine the selection based on specific property values like extension attributes.

Exam trap

Many students think that Attribute-based filtering can replace OU filtering entirely. However, for large directories, failing to use OU filtering first can significantly increase the synchronization time and engine overhead.

215
MCQmedium

You want to delegate the ability for a local office manager to reset passwords for only the users in their specific branch. What is the most efficient way to implement this without granting the manager permissions over the entire tenant?

A.Assign the manager the Helpdesk Administrator role at the tenant level.
B.Create an Administrative Unit (AU), add the branch users to it, and assign the manager the Password Administrator role scoped to that AU.
C.Add the manager to a security group that has 'Full Control' over the branch users' OU in Active Directory.
D.Use a Dynamic Group to identify the branch users and grant the manager 'Owner' rights to the group.
AnswerB

Administrative Units allow you to create a virtual boundary within your tenant. By assigning a role scoped specifically to an AU, the manager's permissions are restricted to only the members of that unit, allowing them to perform resets for their branch without affecting any other users.

Why this answer

Administrative Units (AUs) in Microsoft Entra ID are containers that let you scope role assignments to a subset of users, groups, or devices. Assigning the Password Administrator role to the manager with the AU as the scope grants exactly the branch-level password reset capability requested, with no tenant-wide rights. This is the least-privilege, most efficient design.

Exam trap

SC-300 often tests the confusion between on-premises AD OU delegation and Entra ID Administrative Units — candidates pick the AD OU answer because it 'sounds' like delegation, but cloud scoping requires AUs.

How to eliminate wrong answers

Option A is wrong because Helpdesk Administrator at tenant scope grants password reset (and more) over every user in the tenant, violating least privilege. Option C is wrong because it references on-premises Active Directory OUs and security groups — that model does not apply to Entra ID cloud role scoping and would not restrict the manager to cloud branch users. Option D is wrong because being 'Owner' of a dynamic group grants group management rights, not the ability to reset member passwords; group ownership does not confer user password reset permissions.

216
MCQmedium

You are the Identity and Access Administrator for a company that uses Microsoft Entra ID. The company has a Microsoft 365 E5 subscription that includes Microsoft Entra ID P2. The security team wants to require multi-factor authentication (MFA) for all users when they access the Microsoft Azure Management cloud app. However, they do not want to affect access to any other cloud apps. You need to create a Conditional Access policy that meets these requirements. What should you do?

A.Create a Conditional Access policy that targets all users, selects All cloud apps, and requires multi-factor authentication, then exclude the Microsoft Azure Management app.
B.Create a Conditional Access policy that targets all users, selects All cloud apps, and requires multi-factor authentication, then exclude all other cloud apps except Microsoft Azure Management.
C.Configure a per-user MFA setting to require multi-factor authentication for all users, and then block access to all cloud apps except Microsoft Azure Management using a Conditional Access policy.
D.Create a Conditional Access policy that targets all users, selects the Microsoft Azure Management cloud app, and requires multi-factor authentication.
AnswerD

This correctly scopes the policy to all users and specifically the Microsoft Azure Management cloud app, then enforces MFA as a grant control. Conditional Access policies apply only to the selected cloud apps, so other apps remain unaffected. This meets the security team's requirement exactly without over-scoping or under-scoping, and uses the built-in cloud app identifier for Azure management.

Why this answer

A Conditional Access policy that targets all users and the Microsoft Azure Management cloud app with an MFA grant control precisely enforces MFA only for that app. Other cloud apps remain unaffected because they are not included in the policy scope. This is the recommended approach for app-specific MFA enforcement without impacting other services.

Exam trap

The trap here is assuming that excluding apps from an All cloud apps policy is the way to target a single app, when in fact you should directly select the specific cloud app in the policy.

217
MCQmedium

Your organization needs to ensure that guest users from a specific partner automatically lose access to all resources in a project after 90 days, but they should be able to request an extension that requires approval from their internal project manager. Which configuration in an access package best meets this requirement?

A.Set the lifecycle expiration to 90 days and enable the option for users to request extensions with manager approval.
B.Use a conditional access policy to block access after 90 days based on the account creation date attribute.
C.Configure an access review to occur every 90 days and set the action for non-response to 'Remove access'.
D.Create a lifecycle workflow that deletes the guest account exactly 90 days after the account was first invited.
AnswerA

This configuration directly addresses the 90-day hard limit for initial access while providing a formal workflow for extension requests. Manager approval ensures that any continued access is justified by a business lead, reducing the risk of unauthorized resource retention over time and maintaining strict identity governance.

Why this answer

Access packages in Microsoft Entra ID Governance support lifecycle settings that can expire access after a defined period and allow users to request an extension. When you configure the expiration to 90 days and enable the extension request option with a designated approver (the internal project manager), guests automatically lose access at 90 days unless they request and receive approval for an extension. This directly matches the requirement for automatic expiry plus an approval-gated extension path.

Exam trap

SC-300 often tests the confusion between access reviews (periodic attestation) and access package lifecycle expiration (automatic time-bound expiry with optional extension) — candidates pick access reviews when the requirement is a fixed expiry with user-initiated extension.

How to eliminate wrong answers

Option B is wrong because Conditional Access policies evaluate sign-in conditions (user, device, location, risk) in real time; they cannot expire access based on 'account creation date' as a persistent lifecycle rule, and they do not provide an extension-request workflow. Option C is wrong because access reviews require periodic human review and default to removing access on non-response — they do not offer a user-initiated extension request with manager approval, and the timing is review-cycle-based, not a fixed 90-day expiry. Option D is wrong because deleting the guest account is a destructive action that removes the identity entirely; the requirement is to lose resource access, not delete the account, and there is no extension-request mechanism in a deletion workflow.

218
Multi-Selecthard

You need to configure B2B collaboration settings in Microsoft Entra ID to restrict external access. The solution must meet the following requirements: 1. Allow users to invite guests only from the domain 'fabrikam.com'. 2. Prevent guests from searching the directory for other users. Which TWO settings should you configure?

Select 2 answers
A.Set External user read permissions to 'Guest users are limited to properties and memberships of their own directory objects'.
B.Add 'fabrikam.com' to the Collaboration restrictions list and set the policy to 'Allow invitations only to the specified domains'.
C.Configure a Cross-tenant access policy for 'fabrikam.com' with B2B direct connect enabled.
D.Enable the 'Member users and users assigned to specific admin roles can invite guest users' setting.
E.Create a Conditional Access policy that blocks all external users except those from 'fabrikam.com'.
AnswersA, B

This setting is the most restrictive level of directory visibility for external users in Entra ID. It prevents guests from browsing the full list of users, groups, or other directory objects, effectively isolating them to only the specific resources and profiles they are directly associated with for work.

Why this answer

Option B is correct because the External collaboration settings in Microsoft Entra ID include a Collaboration restrictions list where you add 'fabrikam.com' and select 'Allow invitations only to the specified domains', which precisely enforces requirement 1 by permitting guest invitations solely to that domain. Option A is correct because setting External user read permissions to 'Guest users are limited to properties and memberships of their own directory objects' restricts guests from enumerating other users in the directory, satisfying requirement 2. Option C is incorrect because a cross-tenant access policy with B2B direct connect enabled governs direct connect (Teams shared channels) rather than restricting guest invitations by domain.

Option D is incorrect because it only controls who inside the tenant may invite guests, not which external domains are allowed. Option E is incorrect because Conditional Access cannot enforce a domain-based allow list for guest invitations and does not prevent directory search by guests.

Exam trap

SC-300 often tests the confusion between collaboration restrictions (who can be invited) and external user read permissions (what guests can see), causing candidates to select settings that address only one requirement.

219
MCQmedium

Your organization requires that all guest users accessing a specific SharePoint site must re-authenticate every 24 hours. Which feature should you configure to enforce this requirement?

A.Azure AD Identity Protection risk policies
B.Microsoft Purview Information Protection labels
C.Conditional Access sign-in frequency
D.Access Reviews
AnswerC

Sign-in frequency defines the time period before a user is asked to sign in again when attempting to access a resource. By setting this to 24 hours in a Conditional Access policy, you directly address the requirement to force re-authentication for guest users on a recurring basis.

Why this answer

Conditional Access sign-in frequency lets administrators define how often users must reauthenticate, and it can be scoped to specific users, groups, cloud apps (like SharePoint Online), and even guest/external user types. Setting a sign-in frequency of 24 hours for guest users on a SharePoint site forces reauthentication at that interval. This is the only feature in the list that directly controls reauthentication cadence.

Exam trap

SC-300 often tests whether candidates confuse sign-in frequency with session controls like 'Persistent browser session' or with risk-based policies, so knowing that sign-in frequency is the specific control for reauthentication intervals is critical.

How to eliminate wrong answers

Option A is wrong because Identity Protection risk policies respond to detected risk signals (such as leaked credentials or anomalous sign-ins) and do not enforce a periodic reauthentication timer. Option B is wrong because Purview Information Protection labels classify and protect data content; they have no bearing on authentication session duration. Option D is wrong because Access Reviews are periodic governance attestations where reviewers confirm whether users still need access — they do not force reauthentication every 24 hours.

220
MCQhard

Refer to the exhibit. An administrator has configured a Conditional Access policy using the Microsoft Graph API. Based on the JSON configuration provided, which statement accurately describes the access requirements for users?

A.Users must provide MFA and use a compliant device.
B.Users are required to use MFA for the Microsoft Entra ID service.
C.Users can access applications if they pass MFA or have a compliant device.
D.All users are blocked from all applications regardless of MFA.
AnswerC

The policy utilizes the OR operator for built-in grant controls, allowing for flexibility in how users meet security requirements. By providing two distinct paths to successful authentication, the organization supports different hardware capabilities while ensuring that every sign-in meets at least one of the defined high-security standards.

Why this answer

The JSON configuration uses a grantControls block with operator 'OR' and two built-in controls: 'mfa' and 'compliantDevice'. When the operator is OR, satisfying any one of the listed controls grants access, so users who complete MFA OR present a compliant device are allowed through. This is the classic 'require one of the selected controls' pattern in Conditional Access.

Exam trap

SC-300 often tests the AND vs OR operator in grantControls, tricking candidates into assuming both MFA and compliant device are always required when the JSON actually specifies OR.

How to eliminate wrong answers

Option A is wrong because it describes an AND relationship (MFA plus compliant device), which would require the operator to be 'AND' in the grantControls block. Option B is wrong because it scopes the requirement to the Microsoft Entra ID service only, whereas the policy applies to the configured cloud apps, not just the directory itself. Option D is wrong because a block control would appear as 'block' in grantControls, and no such control is present in the exhibit.

221
MCQmedium

You are an Identity and Access Administrator at a company using Microsoft Entra ID. The legal department requires that all users with the Compliance Administrator role must have their assignment reviewed every 60 days. If a reviewer does not respond, the assignment must be automatically removed. You need to configure an access review for this role. Which setting should you configure to meet the requirement?

A.Set 'Auto apply results to resource' to 'Enable' and configure 'If reviewers don't respond' to 'Approve access'.
B.Set 'Auto apply results to resource' to 'Enable' and configure 'If reviewers don't respond' to 'Take no action'.
C.Set 'Auto apply results to resource' to 'Disable' and configure 'If reviewers don't respond' to 'Remove access'.
D.Set 'Auto apply results to resource' to 'Enable' and configure 'If reviewers don't respond' to 'Remove access'.
AnswerD

This setting ensures that if a reviewer does not respond within the review period, the system automatically removes the user's role assignment. It meets the requirement of automatic removal upon non-response. The 'Auto apply results' setting must be enabled for any action to be taken automatically, and the non-response behavior must be set to remove access. This combination directly satisfies the legal department's mandate without manual intervention.

Why this answer

To automatically remove a role assignment when a reviewer does not respond, the access review must have 'Auto apply results to resource' enabled and 'If reviewers don't respond' set to 'Remove access'. Enabling auto-apply ensures that the decision is enforced without manual intervention, and setting the non-response action to remove access directly fulfills the legal requirement. Other combinations either do not apply results automatically or choose an incorrect action.

Exam trap

The trap here is assuming that setting the non-response action alone is sufficient, without enabling auto-apply, which is required for any automatic enforcement.

222
MCQeasy

You have an application that runs on multiple Azure Virtual Machines. You want to use a single managed identity for all these VMs to access a shared database. Which type of identity should you use?

A.System-assigned managed identity.
B.User-assigned managed identity.
C.Service principal with a certificate.
D.Azure AD Application Proxy.
AnswerB

User-assigned managed identities are created as independent Azure resources. You can assign the same user-assigned identity to multiple virtual machines, allowing them all to share the same identity and permissions, which simplifies access control for shared resources like databases or storage accounts.

Why this answer

A user-assigned managed identity is a standalone Azure resource that can be assigned to multiple Azure VMs, allowing them all to share the same identity and permissions. This is the correct choice when multiple resources need to use the same identity to access a shared resource like a database.

Exam trap

SC-300 often tests the difference between system-assigned and user-assigned managed identities, tricking candidates into picking system-assigned when multiple resources need to share the same identity.

How to eliminate wrong answers

Option A is wrong because a system-assigned managed identity is tied to a single Azure resource and is deleted when that resource is deleted; it cannot be shared across multiple VMs. Option C is wrong because a service principal with a certificate requires managing credentials and is not a managed identity, adding operational overhead. Option D is wrong because Azure AD Application Proxy is for publishing on-premises web apps to remote users, not for granting VMs access to a database.

223
MCQhard

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. The company uses Microsoft Entra Connect to synchronize users from on-premises Active Directory. You need to ensure that when a user is deleted on-premises, their Microsoft Entra ID account is soft-deleted and can be restored within 30 days. What should you do?

A.Configure the Microsoft Entra Connect synchronization rule to soft-delete users in Microsoft Entra ID.
B.Ensure that the on-premises user is deleted (not disabled), and Microsoft Entra Connect will soft-delete the user in Microsoft Entra ID.
C.Enable the 'Prevent accidental deletions' feature in Microsoft Entra Connect and set a deletion threshold.
D.Configure a custom synchronization rule to set the user account as disabled instead of deleted.
AnswerB

When an on-premises user is deleted, Microsoft Entra Connect will delete the corresponding Microsoft Entra ID user. By default, deleted users are soft-deleted in Microsoft Entra ID and can be restored within 30 days. This is the standard behavior without additional configuration.

Why this answer

When an on-premises user is deleted, Microsoft Entra Connect deletes the corresponding Microsoft Entra ID user, which is soft-deleted by default and restorable for 30 days. No additional configuration is needed.

Exam trap

The trap here is assuming that special configuration is required for soft-delete, when it is the default behavior for synchronized deletions.

224
MCQmedium

You need to prevent users from registering their devices for Azure AD Join if they are connecting from non-compliant locations. Which tool should you use?

A.Device compliance policies in Intune
B.Conditional Access policies
C.Identity Protection risk policies
D.Azure AD Connect settings
AnswerB

Conditional Access allows you to target the 'Register or join devices' cloud app. By configuring a policy with location conditions, you can effectively block or require MFA for the device registration process, ensuring that only users in approved locations can successfully join their devices to Azure AD.

Why this answer

Conditional Access policies are the correct tool because they evaluate signals like user location, device compliance, and application sensitivity at sign-in time, and can block or require additional controls for device registration. Specifically, you can create a policy that targets the 'User actions' scope (which includes device registration and Azure AD Join) and applies conditions such as trusted locations or named locations to prevent registration from non-compliant locations. This directly enforces the requirement at the point of device registration, unlike other tools that focus on post-registration compliance or risk detection.

Exam trap

SC-300 often tests the distinction between device compliance (which evaluates device state after enrollment) and Conditional Access (which controls access and actions like device registration based on conditions), so candidates may incorrectly choose Intune compliance policies when the requirement is to block registration from specific locations.

How to eliminate wrong answers

Option A is wrong because Intune device compliance policies define rules that devices must meet (e.g., OS version, encryption) to be marked compliant, but they do not control whether a device can attempt registration from a specific location; they only evaluate devices that are already enrolled. Option C is wrong because Identity Protection risk policies detect and respond to risky user sign-ins or compromised credentials, not location-based restrictions on device registration; they cannot block device registration based on network location. Option D is wrong because Azure AD Connect settings synchronize on-premises identities to Azure AD and configure hybrid identity features like password hash sync or pass-through authentication, but they have no capability to enforce conditional access or location-based policies for device registration.

225
MCQmedium

Which of the following scenarios is the primary use case for utilizing an Azure AD Service Principal over a Managed Identity?

A.When the application runs on an Azure Virtual Machine.
B.When the application requires access to multiple Azure subscriptions.
C.When the application runs on-premises and needs to access Azure APIs.
D.When you need to provide administrative access to the entire tenant.
AnswerC

Managed identities are only available for resources that are hosted in Azure. If an application runs outside of Azure, the platform cannot automatically rotate or provision the identity. Therefore, you must use a standard service principal and manage its credentials manually or via a secure vault system.

Why this answer

Managed identities are limited to Azure-hosted resources. When your application runs on-premises, in another cloud, or on a local machine, you cannot use a managed identity. In these cases, you must register an application in Azure AD and use a service principal with either a certificate or a client secret to establish the required trust and authentication.

Exam trap

Test-takers frequently assume managed identities can be used anywhere, forgetting their strict limitation to resources hosted natively within Azure.

Page 2

Page 3 of 4

Page 4

All pages