Pass Microsoft SC-900 Exam in First Attempt Guaranteed!

The intended application sessions are governed and unrelated apps are not accidentally blocked. This item belongs to a different control area: Conditional Access application targeting. Its appropriate purpose is: A policy should be tested for targeted principals and applications, with emergency-access exclusions where appropriate. For the stated case, Self-service password reset is the closer match. SSPR helps account recovery; it does not grant additional resource authorization or bypass verification.

Inspect guest account records, cross-tenant access settings and assigned resource permissions. This item belongs to a different control area: External guest collaboration. Its appropriate purpose is: B2B collaboration supports external users while preserving explicit guest access and tenant policy boundaries. For the stated case, Self-service password reset is the closer match. SSPR helps account recovery; it does not grant additional resource authorization or bypass verification.

Use Microsoft Entra ID Protection signals to identify and respond to risky users or sign-ins. This item belongs to a different control area: Identity Protection risk detection. Its appropriate purpose is: Identity Protection detects identity-related risk signals; a generic role assignment alone does not assess risk. For the stated case, Self-service password reset is the closer match. SSPR helps account recovery; it does not grant additional resource authorization or bypass verification.

Use the Microsoft Defender portal to review integrated Defender alerts, incidents and security investigations. This item belongs to a different control area: Microsoft Defender portal. Its appropriate purpose is: The Defender portal provides a unified security operations interface; it is not a replacement for configuring every underlying product. For the stated case, Azure Key Vault keys and certificates is the closer match. Key Vault supports cryptographic key and certificate lifecycle; secret storage alone is not a substitute for proper key policy.

Inspect protected resource coverage, workload alerts, enabled plans and alert investigation evidence. This item belongs to a different control area: Defender for Cloud workload protection. Its appropriate purpose is: Cloud workload protection detects threat signals and suspicious runtime behavior; CSPM primarily addresses configuration posture. For the stated case, Azure Key Vault keys and certificates is the closer match. Key Vault supports cryptographic key and certificate lifecycle; secret storage alone is not a substitute for proper key policy.

The targeted risky process behavior is blocked without unnecessarily disrupting approved workloads. This item belongs to a different control area: Endpoint attack surface reduction. Its appropriate purpose is: ASR rules reduce common exploit paths on endpoints and can be tested in audit mode before enforcement. For the stated case, Azure Key Vault keys and certificates is the closer match. Key Vault supports cryptographic key and certificate lifecycle; secret storage alone is not a substitute for proper key policy.

Apply Microsoft's published privacy principles when assessing transparency, control and responsible handling of personal data. This item belongs to a different control area: Microsoft privacy principles. Its appropriate purpose is: Privacy principles guide responsible data handling and transparency; they do not automatically classify every document. For the stated case, Retention policies is the closer match. Retention policies apply lifecycle rules to selected locations or content sets; they do not substitute for DLP sharing blocks.

Use the Microsoft Purview portal to discover and administer supported compliance, information protection and risk capabilities. This item belongs to a different control area: Microsoft Purview portal. Its appropriate purpose is: The Purview portal is a central interface for multiple compliance and data-governance solutions, not itself a finished compliance certification. For the stated case, Retention policies is the closer match. Retention policies apply lifecycle rules to selected locations or content sets; they do not substitute for DLP sharing blocks.

Use the compliance score in Microsoft Purview Compliance Manager as a progress indicator for assessed improvement actions. This item belongs to a different control area: Compliance score. Its appropriate purpose is: Compliance score measures tracked improvement progress; it is not a universal regulatory certification or breach-risk guarantee. For the stated case, Retention policies is the closer match. Retention policies apply lifecycle rules to selected locations or content sets; they do not substitute for DLP sharing blocks.

Offer phishing-resistant FIDO2 passkey authentication with supported Microsoft Entra methods. This item belongs to a different control area: Passkeys and FIDO2. Its appropriate purpose is: FIDO2 passkeys bind authentication to the legitimate relying party and resist credential phishing more effectively than SMS codes. For the stated case, Identity Protection risk detection is the closer match. Identity Protection detects identity-related risk signals; a generic role assignment alone does not assess risk.

Register an application and control its service principal permissions for unattended application access. This item belongs to a different control area: Service principals. Its appropriate purpose is: Service principals represent applications or services rather than individual human users; credentials and consent must be governed. For the stated case, Identity Protection risk detection is the closer match. Identity Protection detects identity-related risk signals; a generic role assignment alone does not assess risk.

Assign the least-privileged supported Microsoft Entra administrative role for a directory task. This item belongs to a different control area: Microsoft Entra role-based access control. Its appropriate purpose is: Entra administrative roles govern directory and identity operations; Azure resource RBAC is a separate scope model. For the stated case, Identity Protection risk detection is the closer match. Identity Protection detects identity-related risk signals; a generic role assignment alone does not assess risk.

The specified lifecycle event triggers consistent identity tasks and leaves auditable results. This item belongs to a different control area: Lifecycle workflows. Its appropriate purpose is: Lifecycle workflows automate repeatable identity onboarding and offboarding tasks; review of ongoing entitlements remains a separate control. For the stated case, Service principals is the closer match. Service principals represent applications or services rather than individual human users; credentials and consent must be governed.

The intended application sessions are governed and unrelated apps are not accidentally blocked. This item belongs to a different control area: Conditional Access application targeting. Its appropriate purpose is: A policy should be tested for targeted principals and applications, with emergency-access exclusions where appropriate. For the stated case, Service principals is the closer match. Service principals represent applications or services rather than individual human users; credentials and consent must be governed.

The operator can perform the approved directory task without access to unrelated privileged functions. This item belongs to a different control area: Microsoft Entra role-based access control. Its appropriate purpose is: Entra administrative roles govern directory and identity operations; Azure resource RBAC is a separate scope model. For the stated case, Service principals is the closer match. Service principals represent applications or services rather than individual human users; credentials and consent must be governed.

An eligible sign-in is completed only after the required second factor or equivalent strong authentication is satisfied. This item belongs to a different control area: Multifactor authentication. Its appropriate purpose is: MFA combines different factor categories to reduce account takeover from a stolen password alone. For the stated case, Microsoft Entra Connect synchronization is the closer match. Directory synchronization must be scoped and observed; enabling it without verifying source objects can create identity drift.

The specified lifecycle event triggers consistent identity tasks and leaves auditable results. This item belongs to a different control area: Lifecycle workflows. Its appropriate purpose is: Lifecycle workflows automate repeatable identity onboarding and offboarding tasks; review of ongoing entitlements remains a separate control. For the stated case, Microsoft Entra Connect synchronization is the closer match. Directory synchronization must be scoped and observed; enabling it without verifying source objects can create identity drift.

Authorized users can reset forgotten passwords after meeting the defined verification requirements. This item belongs to a different control area: Self-service password reset. Its appropriate purpose is: SSPR helps account recovery; it does not grant additional resource authorization or bypass verification. For the stated case, Microsoft Entra Connect synchronization is the closer match. Directory synchronization must be scoped and observed; enabling it without verifying source objects can create identity drift.

Inspect application and service principal objects, consented permissions and authentication credential lifecycle. This item belongs to a different control area: Service principals. Its appropriate purpose is: Service principals represent applications or services rather than individual human users; credentials and consent must be governed. For the stated case, Microsoft Entra role-based access control is the closer match. Entra administrative roles govern directory and identity operations; Azure resource RBAC is a separate scope model.

Inspect access package catalogs, eligibility, request policy and expiration configuration. This item belongs to a different control area: Entitlement management access packages. Its appropriate purpose is: Entitlement management standardizes access bundles and access-request governance for groups, apps and sites. For the stated case, Microsoft Entra role-based access control is the closer match. Entra administrative roles govern directory and identity operations; Azure resource RBAC is a separate scope model.

Inspect synchronization status, source directories and matching cloud user identities. This item belongs to a different control area: Hybrid identity. Its appropriate purpose is: Hybrid identity coordinates on-premises and cloud identity management; it does not automatically move every workload to Azure. For the stated case, Microsoft Entra role-based access control is the closer match. Entra administrative roles govern directory and identity operations; Azure resource RBAC is a separate scope model.

A controlled test shows protected ciphertext at rest and secure transport during approved client communication. This item belongs to a different control area: Encryption. Its appropriate purpose is: Encryption makes data unreadable to an unauthorized party without the appropriate key; it differs from a one-way hash. For the stated case, Identity federation is the closer match. Federation extends authentication trust across security domains; it does not automatically grant unrestricted permissions.

Access decisions re-evaluate context and give only the privileges required for an approved task. This item belongs to a different control area: Zero Trust. Its appropriate purpose is: Zero Trust does not automatically trust a user, device or connection because it originates on a corporate network. For the stated case, Identity federation is the closer match. Federation extends authentication trust across security domains; it does not automatically grant unrestricted permissions.

Risks have assigned treatment decisions and controls have evidence linked to applicable requirements. This item belongs to a different control area: Governance risk and compliance. Its appropriate purpose is: Governance sets direction, risk management evaluates exposure, and compliance verifies obligations against controls. For the stated case, Identity federation is the closer match. Federation extends authentication trust across security domains; it does not automatically grant unrestricted permissions.

Use Microsoft Entra ID as the cloud identity and access-management service for users, groups and applications. This item belongs to a different control area: Microsoft Entra ID cloud identity. Its appropriate purpose is: Microsoft Entra ID provides cloud directory and identity services, not network packet filtering or document retention. For the stated case, Azure resource RBAC versus Entra roles is the closer match. Azure RBAC governs Azure resource permissions, whereas Microsoft Entra roles govern directory services.

Configure and monitor an appropriate supported Microsoft Entra Connect synchronization method for hybrid users. This item belongs to a different control area: Microsoft Entra Connect synchronization. Its appropriate purpose is: Directory synchronization must be scoped and observed; enabling it without verifying source objects can create identity drift. For the stated case, Azure resource RBAC versus Entra roles is the closer match. Azure RBAC governs Azure resource permissions, whereas Microsoft Entra roles govern directory services.

Connect on-premises Active Directory identities with Microsoft Entra ID for a coordinated hybrid identity experience. This item belongs to a different control area: Hybrid identity. Its appropriate purpose is: Hybrid identity coordinates on-premises and cloud identity management; it does not automatically move every workload to Azure. For the stated case, Azure resource RBAC versus Entra roles is the closer match. Azure RBAC governs Azure resource permissions, whereas Microsoft Entra roles govern directory services.

Relevant on-premises directory attack behavior generates supported identity threat detections. This item belongs to a different control area: Defender for Identity. Its appropriate purpose is: Defender for Identity monitors on-premises identity threats and domain controller signals; it is not a cloud app SaaS discovery catalog. For the stated case, Azure Bastion is the closer match. Bastion supplies browser- or client-mediated secure VM management access; it is not a DDoS service.

The intended risky session action is monitored or restricted according to configured controls. This item belongs to a different control area: Defender for Cloud Apps session controls. Its appropriate purpose is: Session controls provide real-time governance of supported cloud app activities; discovery alone does not enforce session behaviors. For the stated case, Azure Bastion is the closer match. Bastion supplies browser- or client-mediated secure VM management access; it is not a DDoS service.

The compliance dashboard reflects assessment status and supporting remediation evidence for selected standards. This item belongs to a different control area: Defender for Cloud regulatory compliance. Its appropriate purpose is: Regulatory compliance views relate assessed technical controls to frameworks; they do not by themselves certify organizational legal compliance. For the stated case, Azure Bastion is the closer match. Bastion supplies browser- or client-mediated secure VM management access; it is not a DDoS service.

Disallowed network flows are blocked by the expected rule without disrupting explicitly permitted connections. This item belongs to a different control area: Network security groups. Its appropriate purpose is: NSGs provide ordered L3/L4 traffic filtering in Azure, not deep web-request inspection. For the stated case, Defender for Identity is the closer match. Defender for Identity monitors on-premises identity threats and domain controller signals; it is not a cloud app SaaS discovery catalog.

Use Azure DDoS Protection for protection of exposed Azure public IP resources against volumetric network attacks where appropriate. This item belongs to a different control area: Azure DDoS Protection. Its appropriate purpose is: DDoS Protection addresses distributed denial-of-service traffic aimed at network services; it does not replace a web-application rule engine. For the stated case, Defender for Identity is the closer match. Defender for Identity monitors on-premises identity threats and domain controller signals; it is not a cloud app SaaS discovery catalog.

Inspect VNet and subnet address plans, peering relationships and route tables. This item belongs to a different control area: Azure virtual network segmentation. Its appropriate purpose is: Virtual networks provide logical network isolation; separate security policies may still be needed to limit allowed flows. For the stated case, Defender for Identity is the closer match. Defender for Identity monitors on-premises identity threats and domain controller signals; it is not a cloud app SaaS discovery catalog.