You save $69.98
SC-300 Premium Bundle
- Premium File 490 Questions & Answers
- Last Update: Nov 2, 2026
- Training Course 43 Lectures
- Study Guide 599 Pages
You save $69.98
The security review requires two independent corrections. Requirement A: A device appears in the directory as registered, yet conditional access policy requires a Microsoft Entra joined corporate device. Requirement B: An AD forest attribute conflict creates duplicate or failed sync records when a second identity source joins the tenant. Which complete two-part plan meets both?
Step 1: Registration can represent a personal-device relationship; joining expresses a different organizational device state. Step 2: Hybrid identity linking relies on consistent source anchors and unique account identifiers, not arbitrary matching by display name. Both verification checks are required: The device record reports the required join state and the targeted device condition evaluates correctly; and The repaired source account links to one intended Entra user and no duplicate cloud identity is created.
Registration can represent a personal-device relationship; joining expresses a different organizational device state. The other proposed action (configure cross-tenant synchronization in the source and allow inbound synchronization in the target with controlled assignments) addresses a different operation. Hybrid identity linking relies on consistent source anchors and unique account identifiers, not arbitrary matching by display name.
The plan is partly correct, but Validate the Primary Refresh Token device SSO model rather than treating Seamless SSO as the mechanism for joined modern devices is not the missing control. Instead, use: Determine whether the device is merely registered or Microsoft Entra joined, and perform the supported organizational join if required.
Both actions target other requirements: A Windows 11 Microsoft Entra joined laptop uses a Primary Refresh Token and engineers propose enabling legacy Seamless SSO as its primary mechanism; Two owned tenants need ongoing provisioning of selected employee identities into the target tenant as organization changes occur. Neither completes the stated two-step design.
A Microsoft Entra administrator needs to fix this condition: A governance team stores confidential project clearance labels and must keep assignment separate from ordinary profile administration. Which change is most appropriate if success is measured by: An Attribute Assignment Administrator updates an authorized clearance while an unrelated User Administrator cannot?
Custom security attribute definitions and assignments have specific roles separate from general user-profile read or write permissions. Define and assign custom security attributes using the dedicated attribute roles and permission model. The acceptance check is: An Attribute Assignment Administrator updates an authorized clearance while an unrelated User Administrator cannot.
Assigned membership gives owners explicit control over who belongs to the group instead of recomputing membership from attributes. This does not address the actual issue: A governance team stores confidential project clearance labels and must keep assignment separate from ordinary profile administration.
Administrative units narrow eligible directory-role management scope, while the same role assigned at tenant scope is not limited to the regional objects. In the present case, however, the missing capability is: Define and assign custom security attributes using the dedicated attribute roles and permission model.
Dynamic group membership evaluates configured user attributes rather than requiring manual updates for every joiner. It is useful when: A seasonal workforce needs to be placed automatically in a security group based on the maintained employee-type attribute. This question instead calls for: Define and assign custom security attributes using the dedicated attribute roles and permission model.
A deployment record says the team implemented: Set an access package assignment expiration policy and validate the supported assignment removal behavior. The failure was: A contractor's access package must end automatically at the agreed contract date instead of depending on a manual offboarding reminder. Which test outcome validates this exact change?
Entitlement management policies can provide time-limited assignments rather than permanent grants.
Manager-based review assignment scopes the decision to the responsible reporting relationship. That observation verifies: The test manager sees their relevant employee assignments and does not receive unrelated users. It does not prove the required result: A test package assignment expires at the configured date and its governed resource access is removed.
Incompatible entitlement checks help prevent conflicting privilege combinations despite successful approval workflow. The suggested evidence belongs to a separate control. Here the test must show: A test package assignment expires at the configured date and its governed resource access is removed.
Resource membership can be granted by multiple paths, and access package assignments have their own lifecycle. Instead, the required outcome is: A test package assignment expires at the configured date and its governed resource access is removed.
A security engineer has this implementation task: A suspicious third-party OAuth app requests broad delegated access to user data and users are approving it without central review. Select the best technical action, with this acceptance test: The risky app grant appears in the investigation and an unauthorized access grant is revoked or blocked.
OAuth app governance identifies risky grants and app behavior independently of ordinary SaaS page access. Investigate OAuth app permissions and apply appropriate OAuth app governance or policy controls. The acceptance check is: The risky app grant appears in the investigation and an unauthorized access grant is revoked or blocked.
The Cloud app catalog provides risk and compliance context that can inform a sanctioning decision. It does not resolve A suspicious third-party OAuth app requests broad delegated access to user data and users are approving it without central review.
An enterprise application is the tenant-local service principal representing an app's instance and permissions. It is useful when: A security reviewer wants to know which application instance granted privileges to a third-party vendor. This question instead calls for: Investigate OAuth app permissions and apply appropriate OAuth app governance or policy controls.
Conditional Access and Defender session policies can differentiate managed from unmanaged sessions when supported by the app. In the present case, however, the missing capability is: Investigate OAuth app permissions and apply appropriate OAuth app governance or policy controls.
The reviewed configuration is: Reconcile other group memberships or direct assignments after applying the review decision. The original problem was: Access review results suggest a removal but a required dependency group is still granting the user equivalent permissions. What measured result confirms it works?
Removing one reviewed entitlement may not revoke access granted independently through another resource assignment.
Azure resource PIM settings can be defined at specific scopes and need not inherit exactly from other resource scopes. The suggested evidence belongs to a separate control. Here the test must show: The user no longer accesses the sensitive resource after all independently approved grants are assessed.
A review decision and its enforcement can be separate steps, depending on review settings. Instead, this case needs to establish that The user no longer accesses the sensitive resource after all independently approved grants are assessed.
Access reviews need an accountable decision maker; orphaned ownership can stall or invalidate the review. That observation verifies: A new designated reviewer receives the pending review and decisions are recorded on time. It does not prove the required result: The user no longer accesses the sensitive resource after all independently approved grants are assessed.
After changing the environment to: Use a system-assigned managed identity attached to the Azure function, auditors need to validate the original need: An Azure function is frequently redeployed and its identity should be deleted automatically when that exact function resource is removed. Which result demonstrates the intended behavior?
A system-assigned identity shares its lifecycle with the resource and is removed when the resource is deleted.
Cloud Discovery reveals cloud service usage from supported traffic sources and risk indicators beyond formally registered enterprise apps. Instead, this case needs to establish that Removing the test function also removes its corresponding system-assigned identity principal.
Detaching a user-assigned identity from compute limits where it can be used while preserving its independent resource lifecycle. That observation verifies: Only the approved function retains the identity and the removed workloads can no longer request tokens as it. It does not prove the required result: Removing the test function also removes its corresponding system-assigned identity principal.
A managed identity endpoint is bound to its supported hosting context, while other workload identities need their own federation or credential model. The suggested evidence belongs to a separate control. Here the test must show: Removing the test function also removes its corresponding system-assigned identity principal.
An identity team faces this specific production requirement: A security reviewer wants to know which application instance granted privileges to a third-party vendor. Which control best satisfies it and would produce this evidence: The reviewer identifies the precise service principal and granted permissions for the vendor?
An enterprise application is the tenant-local service principal representing an app's instance and permissions. Inspect the enterprise application service principal and its delegated or app-only grants and ownership. The acceptance check is: The reviewer identifies the precise service principal and granted permissions for the vendor.
OAuth app governance identifies risky grants and app behavior independently of ordinary SaaS page access. In the present case, however, the missing capability is: Inspect the enterprise application service principal and its delegated or app-only grants and ownership.
The enterprise application's assignment requirement limits which directory principals may sign in to that app. It does not resolve A security reviewer wants to know which application instance granted privileges to a third-party vendor.
User consent and privileged admin consent follow separate tenant consent policies and permission sensitivity. It is useful when: A tenant wants a vendor application available but its consent request asks for broad API scopes that users should not approve themselves. This question instead calls for: Inspect the enterprise application service principal and its delegated or app-only grants and ownership.
A Microsoft Entra administrator needs to fix this condition: A data platform team must let only a specific partner organization request an access package from an external collaboration catalog. Which change is most appropriate if success is measured by: A partner from the connected organization can submit a request and an unrelated outsider cannot?
Request policies determine which internal or external identities can request package assignments. Configure the access package request policy and its allowed connected organizations. The acceptance check is: A partner from the connected organization can submit a request and an unrelated outsider cannot.
The entitlement system can reprovision access if its assignment remains active; removal must target the authoritative grant. It does not resolve A data platform team must let only a specific partner organization request an access package from an external collaboration catalog.
Terms of Use can capture policy acceptance but do not, by themselves, grant access or change group membership. This does not address the actual issue: A data platform team must let only a specific partner organization request an access package from an external collaboration catalog.
Entitlement request approval is a narrower responsibility than global tenant or identity governance configuration. In the present case, however, the missing capability is: Configure the access package request policy and its allowed connected organizations.
Identity architecture review identifies the following gap: An automated deployment pipeline receives a federation token, but app registration credential configuration still requires a long-lived password. Which implementation most directly resolves it, demonstrated by: The approved pipeline exchanges its assertion for a token while a mismatched subject is refused?
Workload identity federation validates trusted token claims instead of requiring a stored application secret. Configure the app registration federated identity credential for the trusted issuer, subject and audience. The acceptance check is: The approved pipeline exchanges its assertion for a token while a mismatched subject is refused.
Microsoft identity platform redirects authorization responses only to registered valid callback URIs. It is useful when: A public web client receives an invalid redirect URI error after the app team changed its production hostname. This question instead calls for: Configure the app registration federated identity credential for the trusted issuer, subject and audience.
A group name alone is not the same as an app role assignment that yields a role claim. This does not address the actual issue: An automated deployment pipeline receives a federation token, but app registration credential configuration still requires a long-lived password.
Provisioning user objects in a SaaS app does not automatically bypass Microsoft Entra enterprise app assignment controls. It does not resolve An automated deployment pipeline receives a federation token, but app registration credential configuration still requires a long-lived password.
Identity architecture review identifies the following gap: An administrator assigns the Directory Readers Microsoft Entra role and expects it to grant an app Blob Data Contributor permissions on an Azure storage account. Which implementation most directly resolves it, demonstrated by: The app can perform the intended storage operation without receiving unrelated tenant directory privileges?
Directory roles and Azure resource RBAC control different permission planes. Grant the workload identity the appropriate Azure resource data role at the specific storage account or container. The acceptance check is: The app can perform the intended storage operation without receiving unrelated tenant directory privileges.
A system-assigned identity shares its lifecycle with the resource and is removed when the resource is deleted. This does not address the actual issue: An administrator assigns the Directory Readers Microsoft Entra role and expects it to grant an app Blob Data Contributor permissions on an Azure storage account.
App-only workload authorization uses a workload identity and permission grants rather than a personal user's delegated session. In the present case, however, the missing capability is: Grant the workload identity the appropriate Azure resource data role at the specific storage account or container.
OAuth app governance identifies risky grants and app behavior independently of ordinary SaaS page access. It does not resolve An administrator assigns the Directory Readers Microsoft Entra role and expects it to grant an app Blob Data Contributor permissions on an Azure storage account.
In the identity platform, the requested outcome is: The user-scoped API call succeeds only for resources the user and app are permitted to access. The current problem is: An interactive client signs in employees and calls an API on their behalf but has been configured with app-only access to all tenant data. What implementation meets the requirement?
Delegated access uses the signed-in user's context and scopes rather than unrestricted application authority. Use appropriate delegated API permissions with the least scopes and consent allowed by the tenant. The acceptance check is: The user-scoped API call succeeds only for resources the user and app are permitted to access.
User consent and privileged admin consent follow separate tenant consent policies and permission sensitivity. In the present case, however, the missing capability is: Use appropriate delegated API permissions with the least scopes and consent allowed by the tenant.
Custom API scopes define delegated permission labels that client applications can request and receive after consent. It does not resolve An interactive client signs in employees and calls an API on their behalf but has been configured with app-only access to all tenant data.
An app object defines the software registration while a service principal is its tenant-specific security instance. This does not address the actual issue: An interactive client signs in employees and calls an API on their behalf but has been configured with app-only access to all tenant data.
Please check your mailbox for a message from support@examlabs.com and follow the directions.