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 app requires Microsoft Entra compliant devices, but administrators target an IP range instead of device state; second, A single anomalous login from an unfamiliar location should trigger extra verification without declaring the account permanently compromised. Which paired implementation meets both acceptance criteria?
Step 1: Device compliance is a device management signal distinct from a named location or trusted network assignment. Step 2: Sign-in risk assesses a particular authentication event, not the overall ongoing compromise state of an identity. Both verification checks are required: An enrolled compliant device succeeds while a controlled noncompliant device does not satisfy the grant; and A simulated risky sign-in reaches the extra control while a low-risk sign-in proceeds according to its normal policy.
Sign-in risk assesses a particular authentication event, not the overall ongoing compromise state of an identity. The other proposed action (Configure the supported Microsoft Entra Kerberos trust scenario and verify device and resource prerequisites) does not implement the first control. Device compliance is a device management signal distinct from a named location or trusted network assignment.
Device compliance is a device management signal distinct from a named location or trusted network assignment. Sign-in risk assesses a particular authentication event, not the overall ongoing compromise state of an identity. The proposed steps (Configure the supported Microsoft Entra Kerberos trust scenario and verify device and resource prerequisites; block the user from sign-in and revoke sessions while the incident team performs recovery) address other capabilities instead of this required pair.
The plan is partly correct, but Block the user from sign-in and revoke sessions while the incident team performs recovery is not the missing control. Instead, use: Configure sign-in risk-based Conditional Access controls that require an approved verification response at the configured risk threshold.
A tenant review found two gaps: Several IT administrators should maintain enterprise application user assignments without becoming global administrators; and An employee on an unmanaged laptop should view a corporate SaaS document in-browser but not download a classified file. Select the TWO controls that together resolve both.
This implements requirement B. Reverse-proxy session controls can govern supported cloud app actions in real time instead of simply blocking the entire app. Verify that the unmanaged-browser test can view permitted content but a classified file download is prevented.
This implements requirement A. Enterprise application management can be delegated without providing unrelated tenant-wide privileges. Verify that the operator updates only the approved app's assignments and cannot change global security settings.
Application collections organize apps for discovery independently of the authorization assignments for each app.
The enterprise application's assignment requirement limits which directory principals may sign in to that app.
User-assigned managed identities exist as independent resources and can be associated with multiple workloads.
The organization must fix both requirements before signoff: (1) An employee's refresh tokens should cease being useful after a suspected stolen device, but the team plans only to remove the device from a dashboard; and (2) A recovered user has changed credentials under incident response, but risk state remains visible to the SOC. Select the combined implementation.
Step 1: Session revocation targets session renewal and does not replace account disablement or downstream app token management. Step 2: Risk state remediation and historical telemetry retention are separate identity protection concerns. Both verification checks are required: The controlled session is forced to reauthenticate and the user account is contained according to policy; and The current risk status reflects the authorized disposition while previous detection evidence remains available.
Risk state remediation and historical telemetry retention are separate identity protection concerns. The other proposed action (Investigate the risky service principal detection and related service-principal sign-in activity) does not implement the first control. Session revocation targets session renewal and does not replace account disablement or downstream app token management.
Session revocation targets session renewal and does not replace account disablement or downstream app token management. Risk state remediation and historical telemetry retention are separate identity protection concerns. The proposed steps (Investigate the risky service principal detection and related service-principal sign-in activity; use a Conditional Access grant control requiring device compliance for the selected resources and users) address other capabilities instead of this required pair.
Session revocation targets session renewal and does not replace account disablement or downstream app token management. The other proposed action (use a Conditional Access grant control requiring device compliance for the selected resources and users) addresses a different operation. Risk state remediation and historical telemetry retention are separate identity protection concerns.
Identity architecture review identifies the following gap: A single anomalous login from an unfamiliar location should trigger extra verification without declaring the account permanently compromised. Which implementation most directly resolves it, demonstrated by: A simulated risky sign-in reaches the extra control while a low-risk sign-in proceeds according to its normal policy?
Sign-in risk assesses a particular authentication event, not the overall ongoing compromise state of an identity. Configure sign-in risk-based Conditional Access controls that require an approved verification response at the configured risk threshold. The acceptance check is: A simulated risky sign-in reaches the extra control while a low-risk sign-in proceeds according to its normal policy.
Blocking account sign-in is a tenant identity control whereas removing an individual app assignment is resource-specific. In the present case, however, the missing capability is: Configure sign-in risk-based Conditional Access controls that require an approved verification response at the configured risk threshold.
Risk detections provide investigative context that should be reviewed before choosing confirm-safe or dismiss actions. It does not resolve A single anomalous login from an unfamiliar location should trigger extra verification without declaring the account permanently compromised.
Emergency access planning must account for risk-triggered CA and access-block policies to preserve recovery capability. It is useful when: A Conditional Access risk policy is broad enough to affect an emergency account during an incident. This question instead calls for: Configure sign-in risk-based Conditional Access controls that require an approved verification response at the configured risk threshold.
The organization must fix both requirements before signoff: (1) A tenant wants a vendor application available but its consent request asks for broad API scopes that users should not approve themselves; and (2) An employee on an unmanaged laptop should view a corporate SaaS document in-browser but not download a classified file. Select the combined implementation.
Step 1: User consent and privileged admin consent follow separate tenant consent policies and permission sensitivity. Step 2: Reverse-proxy session controls can govern supported cloud app actions in real time instead of simply blocking the entire app. Both verification checks are required: A normal user cannot grant the broad scope while an authorized consent decision is recorded; and The unmanaged-browser test can view permitted content but a classified file download is prevented.
User consent and privileged admin consent follow separate tenant consent policies and permission sensitivity. The other proposed action (replace the human login with an appropriate app-only service principal and narrowly scoped approved application permissions) addresses a different operation. Reverse-proxy session controls can govern supported cloud app actions in real time instead of simply blocking the entire app.
Reverse-proxy session controls can govern supported cloud app actions in real time instead of simply blocking the entire app. The other proposed action (Use appropriate delegated API permissions with the least scopes and consent allowed by the tenant) does not implement the first control. User consent and privileged admin consent follow separate tenant consent policies and permission sensitivity.
User consent and privileged admin consent follow separate tenant consent policies and permission sensitivity. Reverse-proxy session controls can govern supported cloud app actions in real time instead of simply blocking the entire app. The proposed steps (Use appropriate delegated API permissions with the least scopes and consent allowed by the tenant; replace the human login with an appropriate app-only service principal and narrowly scoped approved application permissions) address other capabilities instead of this required pair.
A deployment record says the team implemented: Investigate the risky service principal detection and related service-principal sign-in activity. The failure was: A security team sees unfamiliar device and IP indicators for a service principal but no human sign-in associated with it. Which test outcome validates this exact change?
Workload identity risk detections can be based on service principal sign-in behavior or offline signals.
Risk and sign-in telemetry can be aggregated for time-series investigations independently of the portal's individual user view. That observation verifies: The analyst produces a time-bounded report linking risk detections to sign-in events with appropriate access controls. It does not prove the required result: The incident report identifies the service principal and its suspicious resource, IP or credential pattern.
Sign-in risk assesses a particular authentication event, not the overall ongoing compromise state of an identity. Instead, the required outcome is: The incident report identifies the service principal and its suspicious resource, IP or credential pattern.
Session revocation targets session renewal and does not replace account disablement or downstream app token management. Instead, this case needs to establish that The incident report identifies the service principal and its suspicious resource, IP or credential pattern.
A tenant review found two gaps: A new employee needs access only to a subset of apps but the admin proposes making that person a global administrator to obtain them; and A tenant wants to restrict B2B invitation domains but the partner is separately allowlisted in cross-tenant access settings. Select the TWO controls that together resolve both.
This implements requirement A. Resource access assignments and directory administration are separate privilege planes. Verify that the employee opens the approved application but cannot change tenant-level security settings.
This implements requirement B. Cross-tenant access and invitation-domain restrictions are complementary layers; passing one does not guarantee the invitation is allowed. Verify that the permitted partner domain can redeem an invitation while an explicitly blocked domain cannot.
Tenant group settings govern self-service creation capabilities independently of whether users can be members of existing groups.
Dynamic group membership evaluates configured user attributes rather than requiring manual updates for every joiner.
Assigned membership gives owners explicit control over who belongs to the group instead of recomputing membership from attributes.
An enterprise requires a narrowly scoped remediation: A security team sees unfamiliar device and IP indicators for a service principal but no human sign-in associated with it. What should the team implement to verify: The incident report identifies the service principal and its suspicious resource, IP or credential pattern?
Workload identity risk detections can be based on service principal sign-in behavior or offline signals. Investigate the risky service principal detection and related service-principal sign-in activity. The acceptance check is: The incident report identifies the service principal and its suspicious resource, IP or credential pattern.
Sign-in risk assesses a particular authentication event, not the overall ongoing compromise state of an identity. This does not address the actual issue: A security team sees unfamiliar device and IP indicators for a service principal but no human sign-in associated with it.
Session revocation targets session renewal and does not replace account disablement or downstream app token management. In the present case, however, the missing capability is: Investigate the risky service principal detection and related service-principal sign-in activity.
Risk and sign-in telemetry can be aggregated for time-series investigations independently of the portal's individual user view. It does not resolve A security team sees unfamiliar device and IP indicators for a service principal but no human sign-in associated with it.
The administrator must address both defects: (1) A group-based licensing rollout leaves some employees unlicensed because their usage location is missing and (2) Partners require access to a shared team site, and administrators intend to create native member accounts for all visitors. Choose exactly TWO appropriate controls.
This implements requirement B. B2B collaboration represents external identities in the resource tenant without routinely provisioning them as permanent internal employee accounts. Verify that a guest redeems the invitation and reads the approved resource without acquiring employee-wide access.
This implements requirement A. License assignment requires compatible license eligibility information and group processing can report failures per user. Verify that a previously failing group member receives the intended license and the processing error clears.
Dynamic group membership evaluates configured user attributes rather than requiring manual updates for every joiner.
Directory group membership can update separately from application session tokens or cached claims.
External collaboration settings control who may invite B2B users independently of each application's sharing grants.
The organization must fix both requirements before signoff: (1) An on-premises Windows Server farm runs the same domain-integrated service on several servers and admins currently coordinate a shared service password manually; and (2) An OAuth investigation finds an app whose publisher and permission grants no longer match its approved risk profile. Select the combined implementation.
Step 1: A gMSA is a domain-managed service principal that provides automatic password management for supported Windows services across multiple hosts. Step 2: An approved app catalog status does not guarantee that every future permission grant remains acceptable. Both verification checks are required: Each authorized server runs the service as the gMSA and administrators do not distribute or rotate a shared password manually; and The removed excessive permission no longer appears and the approved minimum access remains available.
A gMSA is a domain-managed service principal that provides automatic password management for supported Windows services across multiple hosts. 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.
A gMSA is a domain-managed service principal that provides automatic password management for supported Windows services across multiple hosts. An approved app catalog status does not guarantee that every future permission grant remains acceptable. The proposed steps (Inspect the connector group, connector health, backend URL and name-resolution prerequisites; define supported app roles and assign the authorized users or groups to those roles on the enterprise application) address other capabilities instead of this required pair.
The plan is partly correct, but Inspect the connector group, connector health, backend URL and name-resolution prerequisites is not the missing control. Instead, use: Configure a supported Active Directory group managed service account for the Windows service on authorized hosts.
Identity architecture review identifies the following gap: A legacy AD FS deployment must be migrated toward managed Microsoft Entra authentication while business apps continue to work. Which implementation most directly resolves it, demonstrated by: Pilot users authenticate through the intended new method and production apps retain valid sign-ins?
Changing the federated authentication path requires identity and app compatibility validation, not merely stopping AD FS servers. Plan a controlled federation-to-managed authentication migration with staged user testing and rollback safeguards. The acceptance check is: Pilot users authenticate through the intended new method and production apps retain valid sign-ins.
PTA validates the password through on-premises agents rather than using cloud password-hash validation as its primary sign-in path. It is useful when: A compliance requirement calls for validating user passwords against the on-premises AD environment during Microsoft Entra sign-in. This question instead calls for: Plan a controlled federation-to-managed authentication migration with staged user testing and rollback safeguards.
Registration can represent a personal-device relationship; joining expresses a different organizational device state. This does not address the actual issue: A legacy AD FS deployment must be migrated toward managed Microsoft Entra authentication while business apps continue to work.
Modern joined and registered Windows SSO uses PRT, while Seamless SSO primarily targets compatible domain-joined corporate-network sessions. In the present case, however, the missing capability is: Plan a controlled federation-to-managed authentication migration with staged user testing and rollback safeguards.
Please check your mailbox for a message from support@examlabs.com and follow the directions.