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
Two identity controls must be deployed together. Task 1: A managed identity is enabled but the app receives authorization denied from Azure Storage when requesting data. Task 2: A high-risk newly discovered cloud application should be flagged as unsanctioned for the organization to enforce a controlled policy. Which coordinated action is appropriate?
Step 1: Issuing an identity token is not the same as granting data-plane authorization to the protected resource. Step 2: Sanctioning classifies cloud app use; blocking may depend on supported endpoint or network enforcement integration. Both verification checks are required: The identified workload can read the permitted container but remains unable to read an unrelated account; and The application appears as unsanctioned and the enabled enforcement channel applies the intended restriction.
Sanctioning classifies cloud app use; blocking may depend on supported endpoint or network enforcement integration. The other proposed action (Investigate OAuth app permissions and apply appropriate OAuth app governance or policy controls) does not implement the first control. Issuing an identity token is not the same as granting data-plane authorization to the protected resource.
Both actions target other requirements: A suspicious third-party OAuth app requests broad delegated access to user data and users are approving it without central review; A business-to-business service is registered for users from only the organization's home tenant, but a developer accidentally allows personal accounts. Neither completes the stated two-step design.
The plan is partly correct, but Set the application registration supported account types to the intended single-tenant organizational audience is not the missing control. Instead, use: Mark the reviewed app unsanctioned and integrate the relevant enforcement path where supported.
A Microsoft Entra administrator needs to fix this condition: A scheduled daemon calls Microsoft Graph without any signed-in user but developers request only delegated API scopes. Which change is most appropriate if success is measured by: The daemon's app-only token includes approved roles and does not depend on a user's login?
Application permissions are represented in app-only tokens; delegated scopes require a user context. Configure application permissions appropriate for app-only access and obtain required administrator consent. The acceptance check is: The daemon's app-only token includes approved roles and does not depend on a user's login.
OAuth scopes are associated with a specific resource audience, not simply a descriptive permission name. It is useful when: An application receives tokens for the wrong API because it requested a scope under an unrelated resource identifier. This question instead calls for: Configure application permissions appropriate for app-only access and obtain required administrator consent.
Custom API scopes define delegated permission labels that client applications can request and receive after consent. This does not address the actual issue: A scheduled daemon calls Microsoft Graph without any signed-in user but developers request only delegated API scopes.
Application Proxy brokers authenticated remote access to supported on-premises applications through connectors. In the present case, however, the missing capability is: Configure application permissions appropriate for app-only access and obtain required administrator consent.
After changing the environment to: Inspect entitlement assignment records and the target resource membership source together, auditors need to validate the original need: An administrator needs to know whether a user's permission came from an access package or a manually granted group membership. Which result demonstrates the intended behavior?
Resource membership can be granted by multiple paths, and access package assignments have their own lifecycle.
PIM records eligible assignment and activation events with actor, timing and workflow context. The suggested evidence belongs to a separate control. Here the test must show: The reviewer identifies the active package assignment and any separate manual grant before removing access.
Entitlement management policies can provide time-limited assignments rather than permanent grants. Instead, this case needs to establish that The reviewer identifies the active package assignment and any separate manual grant before removing access.
Access packages combine selected resource roles into a governed requestable entitlement. That observation verifies: A test requester receives all bundled resources only after the policy's approval requirements are satisfied. It does not prove the required result: The reviewer identifies the active package assignment and any separate manual grant before removing access.
A deployment record says the team implemented: Deploy and configure Microsoft Entra Connect Sync with scoped directories, sign-in mode and health checks. The failure was: A small enterprise wants to synchronize on-premises AD DS users to Entra ID with a configurable synchronization engine and health monitoring. Which test outcome validates this exact change?
Connect Sync synchronizes selected on-premises identities while retaining supported hybrid directory source authority.
Password writeback sends supported cloud-initiated password changes to the local directory so cloud and domain credentials remain coordinated. Instead, the required outcome is: A sampled on-premises user appears in Entra ID with correct linked identity attributes and sync errors are monitored.
PHS enables Microsoft Entra cloud authentication using synchronized derived password hashes rather than online AD validation at every login. Instead, this case needs to establish that A sampled on-premises user appears in Entra ID with correct linked identity attributes and sync errors are monitored.
Device join settings can limit who joins organizational Windows devices and are distinct from ordinary identity or group settings. That observation verifies: An excluded test user cannot join a new device while an allowed enrollment user succeeds. It does not prove the required result: A sampled on-premises user appears in Entra ID with correct linked identity attributes and sync errors are monitored.
Two identity controls must be deployed together. Task 1: An Azure virtual machine has both system-assigned and user-assigned identities and the SDK unexpectedly selects the wrong identity. Task 2: Several IT administrators should maintain enterprise application user assignments without becoming global administrators. Which coordinated action is appropriate?
Step 1: Hosts with multiple identities need explicit selection to avoid receiving tokens for a different principal. Step 2: Enterprise application management can be delegated without providing unrelated tenant-wide privileges. Both verification checks are required: The token resolves to the selected identity and an access test uses only its permitted role assignments; and The operator updates only the approved app's assignments and cannot change global security settings.
Enterprise application management can be delegated without providing unrelated tenant-wide privileges. The other proposed action (Configure enterprise application provisioning with the supported SCIM integration and scope) does not implement the first control. Hosts with multiple identities need explicit selection to avoid receiving tokens for a different principal.
Hosts with multiple identities need explicit selection to avoid receiving tokens for a different principal. The other proposed action (create a user-assigned managed identity and attach it to the supported Azure resources) addresses a different operation. Enterprise application management can be delegated without providing unrelated tenant-wide privileges.
Hosts with multiple identities need explicit selection to avoid receiving tokens for a different principal. Enterprise application management can be delegated without providing unrelated tenant-wide privileges. The proposed steps (Configure enterprise application provisioning with the supported SCIM integration and scope; create a user-assigned managed identity and attach it to the supported Azure resources) address other capabilities instead of this required pair.
An identity engineer needs to validate the completed action: Create a supported dynamic membership security group with a validated rule matching employeeType. Its original requirement was: A seasonal workforce needs to be placed automatically in a security group based on the maintained employee-type attribute. Which evidence should be accepted?
Dynamic group membership evaluates configured user attributes rather than requiring manual updates for every joiner.
Resource access assignments and directory administration are separate privilege planes. That observation verifies: The employee opens the approved application but cannot change tenant-level security settings. It does not prove the required result: A user with the selected employee type joins the group and a nonmatching user remains out.
License assignment requires compatible license eligibility information and group processing can report failures per user. The suggested evidence belongs to a separate control. Here the test must show: A user with the selected employee type joins the group and a nonmatching user remains out.
Tenant group settings govern self-service creation capabilities independently of whether users can be members of existing groups. Instead, the required outcome is: A user with the selected employee type joins the group and a nonmatching user remains out.
After changing the environment to: Verify the custom domain and configure it as the tenant's primary domain rather than bulk-editing existing accounts, auditors need to validate the original need: An organization wants a new custom domain to be the default suffix for future cloud user creation without renaming all existing users. Which result demonstrates the intended behavior?
Primary-domain selection determines the default domain for new users, while already-provisioned UPNs are separately managed.
A custom role can collect allowed directory permissions without bundling unrelated capabilities from a broad built-in role. The suggested evidence belongs to a separate control. Here the test must show: A newly created user receives the intended default suffix and existing users keep their original UPNs.
Tenant group settings govern self-service creation capabilities independently of whether users can be members of existing groups. Instead, this case needs to establish that A newly created user receives the intended default suffix and existing users keep their original UPNs.
Password writeback sends supported cloud-initiated password changes to the local directory so cloud and domain credentials remain coordinated. That observation verifies: A test user resets the password in cloud SSPR and signs in on-premises with the new credential. It does not prove the required result: A newly created user receives the intended default suffix and existing users keep their original UPNs.
A Microsoft Entra administrator needs to fix this condition: Branch offices use remote network connectivity and administrators expect it to carry Private Access application traffic without endpoint clients. Which change is most appropriate if success is measured by: The branch's Microsoft traffic works via remote network and the private app becomes reachable when the approved endpoint client is enabled?
Remote network connectivity supports the applicable Microsoft and Internet profiles, whereas Private Access requires compatible client acquisition. Use supported remote network acquisition for Microsoft and Internet traffic, and deploy clients for Private Access resources. The acceptance check is: The branch's Microsoft traffic works via remote network and the private app becomes reachable when the approved endpoint client is enabled.
The Microsoft profile handles supported Microsoft application traffic separately from the general Internet Access profile. This does not address the actual issue: Branch offices use remote network connectivity and administrators expect it to carry Private Access application traffic without endpoint clients.
The application segment identifies what private destination traffic the GSA client should acquire and route. In the present case, however, the missing capability is: Use supported remote network acquisition for Microsoft and Internet traffic, and deploy clients for Private Access resources.
Entra Kerberos can support specific hybrid authentication flows when infrastructure and trust requirements are satisfied. It is useful when: Hybrid users must use supported Entra Kerberos authentication to reach a protected on-premises resource from a compliant cloud-managed device. This question instead calls for: Use supported remote network acquisition for Microsoft and Internet traffic, and deploy clients for Private Access resources.
A tenant review found two gaps: A user-assigned managed identity was attached to several resources but should be used by only one approved function going forward; and A custom app requires application roles for employees but users receive no role claim after a group has been created. Select the TWO controls that together resolve both.
This implements requirement B. A group name alone is not the same as an app role assignment that yields a role claim. Verify that a group member's issued token contains the intended app role and an unrelated user does not.
This implements requirement A. Detaching a user-assigned identity from compute limits where it can be used while preserving its independent resource lifecycle. Verify that only the approved function retains the identity and the removed workloads can no longer request tokens as it.
A system-assigned identity shares its lifecycle with the resource and is removed when the resource is deleted.
Hosts with multiple identities need explicit selection to avoid receiving tokens for a different principal.
SCIM provisioning synchronizes users and groups through application provisioning rather than relying solely on login federation.
An operator has applied the control: Remove or expire active privileged role assignments separately from unactivated eligibility and disable the account as appropriate. It was intended to address: A leaver still has a permanent active Microsoft Entra directory administrator assignment even though their eligible assignments were removed. Which observation is the strongest proof of success?
Deleting eligible assignments does not automatically remove a distinct permanent active role grant.
Privileged role assignment governance differs from an ordinary app-membership review. That observation verifies: A role assignment appears in the privileged review and a denied role is removed after results apply. It does not prove the required result: The offboarded account has no active directory role and cannot perform a privileged operation.
Eligibility alone does not create currently active directory privileges. The suggested evidence belongs to a separate control. Here the test must show: The offboarded account has no active directory role and cannot perform a privileged operation.
PIM offers just-in-time role activation so administrators are not permanently granted high-risk privileges. Instead, this case needs to establish that The offboarded account has no active directory role and cannot perform a privileged operation.
Two identity controls must be deployed together. Task 1: An Azure function is frequently redeployed and its identity should be deleted automatically when that exact function resource is removed. Task 2: An OAuth investigation finds an app whose publisher and permission grants no longer match its approved risk profile. Which coordinated action is appropriate?
Step 1: A system-assigned identity shares its lifecycle with the resource and is removed when the resource is deleted. Step 2: An approved app catalog status does not guarantee that every future permission grant remains acceptable. Both verification checks are required: Removing the test function also removes its corresponding system-assigned identity principal; and The removed excessive permission no longer appears and the approved minimum access remains available.
The plan is partly correct, but Use appropriate delegated API permissions with the least scopes and consent allowed by the tenant is not the missing control. Instead, use: Use a system-assigned managed identity attached to the Azure function.
A system-assigned identity shares its lifecycle with the resource and is removed when the resource is deleted. The other proposed action (define supported app roles and assign the authorized users or groups to those roles on the enterprise application) addresses a different operation. An approved app catalog status does not guarantee that every future permission grant remains acceptable.
Both actions target other requirements: 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; A custom app requires application roles for employees but users receive no role claim after a group has been created. Neither completes the stated two-step design.
Please check your mailbox for a message from support@examlabs.com and follow the directions.