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
A Microsoft Entra rollout has two issues: first, An internal web application is hosted on-premises, but employees must reach it through Microsoft Entra without making it publicly reachable by direct firewall exposure; second, An application receives tokens for the wrong API because it requested a scope under an unrelated resource identifier. Which paired implementation meets both acceptance criteria?
Step 1: Application Proxy brokers authenticated remote access to supported on-premises applications through connectors. Step 2: OAuth scopes are associated with a specific resource audience, not simply a descriptive permission name. Both verification checks are required: An authorized remote user opens the internal app while the internal server has no new direct public inbound listener; and The token audience and scope match the intended API and a different API rejects the token.
Application Proxy brokers authenticated remote access to supported on-premises applications through connectors. OAuth scopes are associated with a specific resource audience, not simply a descriptive permission name. The proposed steps (Configure application permissions appropriate for app-only access and obtain required administrator consent; configure enterprise application SAML single sign-on and map the required identifier claim to the correct user attribute) address other capabilities instead of this required pair.
Application Proxy brokers authenticated remote access to supported on-premises applications through connectors. The other proposed action (configure enterprise application SAML single sign-on and map the required identifier claim to the correct user attribute) addresses a different operation. OAuth scopes are associated with a specific resource audience, not simply a descriptive permission name.
OAuth scopes are associated with a specific resource audience, not simply a descriptive permission name. The other proposed action (Configure application permissions appropriate for app-only access and obtain required administrator consent) does not implement the first control. Application Proxy brokers authenticated remote access to supported on-premises applications through connectors.
In the identity platform, the requested outcome is: An approved activation produces the configured alert with the correct role and principal. The current problem is: A user repeatedly requests a privileged assignment and the security team wants notification when high-risk roles are activated. What implementation meets the requirement?
PIM can send events and alerts for privileged role activation separate from ordinary group access changes. Configure PIM role-activation notifications and monitoring for the selected privileged roles. The acceptance check is: An approved activation produces the configured alert with the correct role and principal.
Deleting eligible assignments does not automatically remove a distinct permanent active role grant. This does not address the actual issue: A user repeatedly requests a privileged assignment and the security team wants notification when high-risk roles are activated.
PIM activation can require stronger authentication before granting temporary privileges. In the present case, however, the missing capability is: Configure PIM role-activation notifications and monitoring for the selected privileged roles.
Request policies determine which internal or external identities can request package assignments. It does not resolve A user repeatedly requests a privileged assignment and the security team wants notification when high-risk roles are activated.
A tenant review found two gaps: A support administrator with Helpdesk Administrator scoped to an administrative unit can still look up basic users outside that unit and falsely assumes this is a privileged access leak; and A seasonal workforce needs to be placed automatically in a security group based on the maintained employee-type attribute. Select the TWO controls that together resolve both.
This implements requirement A. Administrative units limit role-based write privileges but do not inherently hide all out-of-scope users from directory searches. Verify that the operator can locate a user outside the unit but cannot perform a restricted write to that user.
This implements requirement B. Dynamic group membership evaluates configured user attributes rather than requiring manual updates for every joiner. Verify that a user with the selected employee type joins the group and a nonmatching user remains out.
Privileged Identity Management separates standing eligible role assignment from temporary active permissions.
Microsoft Entra audit events capture relevant administrative unit role and membership changes, unlike sign-in records that only show authentication.
A user principal name change can affect downstream app identifiers even though the object ID remains stable.
Two identity controls must be deployed together. Task 1: Employees can reset passwords in the cloud but forgot to register sufficient alternate security information. Task 2: An administrator incorrectly treats user risk and sign-in risk as the same alert category when investigating suspicious activity. Which coordinated action is appropriate?
Step 1: Self-service password reset depends on sufficient registered recovery methods and the user's enabled policy scope. Step 2: Identity Protection distinguishes accumulated user compromise risk from individual sign-in risk signals. Both verification checks are required: A pilot user with registered methods completes SSPR while an unregistered user receives onboarding guidance; and The case shows which sign-in was risky and whether the user's overall risk remains active.
Both actions target other requirements: Employees access Microsoft 365 from both joined and BYOD devices and security needs conditions that distinguish trusted device posture; An administrator needs to know which existing policies would apply to a hypothetical sign-in from a noncompliant laptop. Neither completes the stated two-step design.
The plan is partly correct, but Use appropriate device filters and Conditional Access conditions validated against registration and compliance properties is not the missing control. Instead, use: Deploy combined security information registration and configure SSPR authentication methods for the appropriate users.
Self-service password reset depends on sufficient registered recovery methods and the user's enabled policy scope. The other proposed action (use the Conditional Access What If tool with the user, resource, client, device and relevant sign-in conditions) addresses a different operation. Identity Protection distinguishes accumulated user compromise risk from individual sign-in risk signals.
Two Microsoft Entra issues require independent fixes. First: An application receives tokens for the wrong API because it requested a scope under an unrelated resource identifier. Second: A security administrator wants to limit a specific corporate app's use from unmanaged browsers but preserve compliant device use. Which TWO actions are necessary?
This implements requirement A. OAuth scopes are associated with a specific resource audience, not simply a descriptive permission name. Verify that the token audience and scope match the intended API and a different API rejects the token.
This implements requirement B. Conditional Access and Defender session policies can differentiate managed from unmanaged sessions when supported by the app. Verify that an unmanaged browser is restricted and a compliant-device test retains its intended functionality.
Delegated access uses the signed-in user's context and scopes rather than unrestricted application authority.
SAML SSO depends on correctly configured identity-provider trust metadata and claim mappings.
Application permissions are represented in app-only tokens; delegated scopes require a user context.
An enterprise requires a narrowly scoped remediation: A tenant wants a vendor application available but its consent request asks for broad API scopes that users should not approve themselves. What should the team implement to verify: A normal user cannot grant the broad scope while an authorized consent decision is recorded?
User consent and privileged admin consent follow separate tenant consent policies and permission sensitivity. Configure a restricted user consent policy and the governed admin consent workflow for the application. The acceptance check is: A normal user cannot grant the broad scope while an authorized consent decision is recorded.
Delegated access uses the signed-in user's context and scopes rather than unrestricted application authority. This does not address the actual issue: A tenant wants a vendor application available but its consent request asks for broad API scopes that users should not approve themselves.
The enterprise application's assignment requirement limits which directory principals may sign in to that app. It does not resolve A tenant wants a vendor application available but its consent request asks for broad API scopes that users should not approve themselves.
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: Configure a restricted user consent policy and the governed admin consent workflow for the application.
An enterprise requires a narrowly scoped remediation: A confidential server-side application uses a client secret stored in source code and security wants a more controlled authentication credential. What should the team implement to verify: The server acquires tokens using the approved certificate and the removed source secret is unusable?
Confidential clients can authenticate with certificates, reducing exposure from hard-coded shared client secrets. Replace the embedded secret with an approved certificate credential stored and rotated through secure operations. The acceptance check is: The server acquires tokens using the approved certificate and the removed source secret is unusable.
Each active application credential can permit token acquisition; unused secrets should not be left valid. In the present case, however, the missing capability is: Replace the embedded secret with an approved certificate credential stored and rotated through secure operations.
Workload identity federation validates trusted token claims instead of requiring a stored application secret. It is useful when: An automated deployment pipeline receives a federation token, but app registration credential configuration still requires a long-lived password. This question instead calls for: Replace the embedded secret with an approved certificate credential stored and rotated through secure operations.
Managed identities remove application-managed client secrets for compatible Azure-hosted authentication flows. This does not address the actual issue: A confidential server-side application uses a client secret stored in source code and security wants a more controlled authentication credential.
A Microsoft Entra administrator needs to fix this condition: A user account has confirmed leaked credentials and needs a secure password change rather than only a new MFA prompt. Which change is most appropriate if success is measured by: A high-risk user receives the configured remediation and risk state changes only through supported actions?
User risk represents potential compromise of the identity over time, distinct from risk of an individual sign-in. Configure a user risk policy with the appropriate secure password change or blocking action. The acceptance check is: A high-risk user receives the configured remediation and risk state changes only through supported actions.
Windows Hello for Business uses device-bound keys or credentials and requires the trust configuration to match hybrid architecture. It does not resolve A user account has confirmed leaked credentials and needs a secure password change rather than only a new MFA prompt.
Emergency access planning must account for risk-triggered CA and access-block policies to preserve recovery capability. This does not address the actual issue: A user account has confirmed leaked credentials and needs a secure password change rather than only a new MFA prompt.
Risk detections provide investigative context that should be reviewed before choosing confirm-safe or dismiss actions. In the present case, however, the missing capability is: Configure a user risk policy with the appropriate secure password change or blocking action.
Identity architecture review identifies the following gap: A privileged resource group requires quarterly certification of membership by designated reviewers. Which implementation most directly resolves it, demonstrated by: Reviewers receive the scheduled membership decisions and the review history records their outcomes?
Access reviews schedule governance decisions about existing access rather than being one-time audit reports. Create a recurring Microsoft Entra access review for the group with selected reviewer assignments. The acceptance check is: Reviewers receive the scheduled membership decisions and the review history records their outcomes.
Azure resource PIM settings can be defined at specific scopes and need not inherit exactly from other resource scopes. It is useful when: An Azure resource PIM role setting is changed at a resource group and administrators expect it to overwrite parent subscription settings. This question instead calls for: Create a recurring Microsoft Entra access review for the group with selected reviewer assignments.
Recurring reviews produce traceable decisions and enforcement records across multiple periods. This does not address the actual issue: A privileged resource group requires quarterly certification of membership by designated reviewers.
A review decision and its enforcement can be separate steps, depending on review settings. In the present case, however, the missing capability is: Create a recurring Microsoft Entra access review for the group with selected reviewer assignments.
Identity architecture review identifies the following gap: A small enterprise wants to synchronize on-premises AD DS users to Entra ID with a configurable synchronization engine and health monitoring. Which implementation most directly resolves it, demonstrated by: A sampled on-premises user appears in Entra ID with correct linked identity attributes and sync errors are monitored?
Connect Sync synchronizes selected on-premises identities while retaining supported hybrid directory source authority. Deploy and configure Microsoft Entra Connect Sync with scoped directories, sign-in mode and health checks. The acceptance check is: 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. This does not address the actual issue: A small enterprise wants to synchronize on-premises AD DS users to Entra ID with a configurable synchronization engine and health monitoring.
PHS enables Microsoft Entra cloud authentication using synchronized derived password hashes rather than online AD validation at every login. In the present case, however, the missing capability is: Deploy and configure Microsoft Entra Connect Sync with scoped directories, sign-in mode and health checks.
Password writeback sends supported cloud-initiated password changes to the local directory so cloud and domain credentials remain coordinated. It does not resolve A small enterprise wants to synchronize on-premises AD DS users to Entra ID with a configurable synchronization engine and health monitoring.
A deployment record says the team implemented: Assign the appropriate least-privilege Azure RBAC data role at the storage scope to that managed identity. The failure was: A managed identity is enabled but the app receives authorization denied from Azure Storage when requesting data. Which test outcome validates this exact change?
Issuing an identity token is not the same as granting data-plane authorization to the protected resource.
A managed identity endpoint is bound to its supported hosting context, while other workload identities need their own federation or credential model. Instead, this case needs to establish that The identified workload can read the permitted container but remains unable to read an unrelated account.
OAuth app governance identifies risky grants and app behavior independently of ordinary SaaS page access. That observation verifies: The risky app grant appears in the investigation and an unauthorized access grant is revoked or blocked. It does not prove the required result: The identified workload can read the permitted container but remains unable to read an unrelated account.
User-assigned managed identities exist as independent resources and can be associated with multiple workloads. Instead, the required outcome is: The identified workload can read the permitted container but remains unable to read an unrelated account.
Please check your mailbox for a message from support@examlabs.com and follow the directions.