Practice Exams:

Microsoft SC-900 Dumps

EXAM: Microsoft Security, Compliance, and Identity Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

SC-900 Premium Bundle


  • Premium File 259 Questions & Answers
  • Training Course 147 Lectures
  • Study Guide 413 Pages

Microsoft SC-900 Practice Test 12

Question 110

A human resources departure process disables one corporate account but an unrelated vendor portal still accepts the former employee's local password. Which action and validation evidence belong together?

  1. Action: Assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. Validation: Review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
  2. Action: Use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle. Validation: Disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.
  3. Action: Grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing. Validation: Sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.
  4. Action: Use a supported federated sign-in relationship when an application trusts an external identity provider's signed assertion rather than directly storing every user's password. Validation: Complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

Explanation

Correct Answer

B:

The situation is that a human resources departure process disables one corporate account but an unrelated vendor portal still accepts the former employee's local password. Use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle. Validation: Disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits. The action and test belong together because an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

Incorrect Answers

A:

“distinguish human and application identities” evaluates a different intervention. The appropriate action is to use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle. To confirm, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

C:

The situation is that a human resources departure process disables one corporate account but an unrelated vendor portal still accepts the former employee's local password. That action-and-evidence pair concerns “use least privilege when assigning directory and resource roles”, not this decision. The appropriate action is to use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle. To confirm, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

D:

The proposed pair focuses on “understand federation trust” instead. The appropriate action is to use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle. To confirm, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

Question 111

During a tenant protection and compliance review, An enterprise moves Microsoft 365 sign-in to Entra and asks whether its old domain-joined factory machines still need Kerberos-capable services. What is the most appropriate next decision?

  1. Use a supported federated sign-in relationship when an application trusts an external identity provider's signed assertion rather than directly storing every user's password.
  2. Assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function.
  3. Use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities.
  4. Require a trustworthy principal identity and context-aware access decision before granting cloud data access, even when traffic originates from a familiar network.

Explanation

Correct Answer

C:

Use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics. To verify, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Incorrect Answers

A:

This alternative focuses on “understand federation trust” instead of the required outcome. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

B:

That choice concerns “distinguish human and application identities”, not the immediate requirement. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

D:

“treat identity as a primary access boundary” is related to another task, not the failure shown here. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Question 112

An enterprise moves Microsoft 365 sign-in to Entra and asks whether its old domain-joined factory machines still need Kerberos-capable services. Why does the recommended approach address this particular concern?

  1. An IaaS provider manages underlying datacenter assets but the tenant still controls supported guest operating systems, installed applications and workload configuration.
  2. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.
  3. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.
  4. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Explanation

Correct Answer

D:

Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics. This supports the decision to use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities.

Incorrect Answers

A:

“distinguish customer guest os duty in IaaS” explains a different mechanism. Here, traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

B:

That statement concerns “understand federation trust” rather than the cause in this case. Here, traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

C:

The principle behind “choose a trusted identity provider for shared login” is not the one being tested. Here, traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Question 113

An enterprise moves Microsoft 365 sign-in to Entra and asks whether its old domain-joined factory machines still need Kerberos-capable services. Which evidence best validates the proposed outcome?

  1. Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.
  2. Sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.
  3. Sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.
  4. Verify the same test identity receives appropriate approved rights from an office and remote location while a different principal is denied.

Explanation

Correct Answer

A:

Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario. It is the relevant test because traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Incorrect Answers

B:

This evidence addresses “use least privilege when assigning directory and resource roles” instead of confirming the repair. To check this result, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

C:

“distinguish proof of identity from resource permission” would verify a different part of the system. To check this result, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

D:

That test concerns “treat identity as a primary access boundary”, not the requested outcome. To check this result, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Question 114

Consider this situation: An enterprise moves Microsoft 365 sign-in to Entra and asks whether its old domain-joined factory machines still need Kerberos-capable services. A team member suggests: "Assume cloud Microsoft Entra ID alone automatically supplies every classic AD DS domain-controller and Group Policy function with no architecture planning." What is the main risk?

  1. Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk responsibility.
  2. Legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.
  3. The job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
  4. An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.

Explanation

Correct Answer

B:

Legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated. The shortcut is unsafe because traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Incorrect Answers

A:

The alternative risk relates to “Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk…”, not the stated mistake. Here, legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.

C:

That consequence concerns “The job can fail when the employee leaves and may expose broad administrative access because a…”, which is a different failure. Here, legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.

D:

“An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience…” does not describe the result of this shortcut. Here, legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.

Question 115

A security and compliance reviewer considers: An enterprise moves Microsoft 365 sign-in to Entra and asks whether its old domain-joined factory machines still need Kerberos-capable services. Which response and evidence should be linked?

  1. Action: Authenticate a requesting principal first and then separately authorize only the actions it is allowed to perform on the target resource. Validation: Sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.
  2. Action: Require a trustworthy principal identity and context-aware access decision before granting cloud data access, even when traffic originates from a familiar network. Validation: Verify the same test identity receives appropriate approved rights from an office and remote location while a different principal is denied.
  3. Action: Use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. Validation: Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.
  4. Action: Grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing. Validation: Sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.

Explanation

Correct Answer

C:

Use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. Validation: Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario. The action and test belong together because traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Incorrect Answers

A:

The linked action and check for “distinguish proof of identity from resource permission” would not resolve this case. The appropriate action is to use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. To confirm, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

B:

That action-and-evidence pair concerns “treat identity as a primary access boundary”, not this decision. The appropriate action is to use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. To confirm, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

D:

“use least privilege when assigning directory and resource roles” evaluates a different intervention. The appropriate action is to use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. To confirm, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Question 116

A school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. Which action best addresses this requirement?

  1. Use a supported federated sign-in relationship when an application trusts an external identity provider's signed assertion rather than directly storing every user's password.
  2. Authenticate a requesting principal first and then separately authorize only the actions it is allowed to perform on the target resource.
  3. Assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function.
  4. Use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities.

Explanation

Correct Answer

D:

The situation is that a school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. Use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics. To verify, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Incorrect Answers

A:

That choice concerns “understand federation trust”, not the immediate requirement. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

B:

The proposed action addresses “distinguish proof of identity from resource permission” rather than the problem described. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

C:

“distinguish human and application identities” is related to another task, not the failure shown here. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Question 117

A cloud security learner considers: A school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. Which underlying principle applies?

  1. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.
  2. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.
  3. A single globally privileged account greatly increases attack impact and auditing difficulty compared with scoped roles limited to a particular service.
  4. Authentication establishes who the requester claims to be, while authorization determines the resources and operations that verified principal may use.

Explanation

Correct Answer

A:

The situation is that a school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics. This supports the decision to use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities.

Incorrect Answers

B:

The situation is that a school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. The principle behind “choose a trusted identity provider for shared login” is not the one being tested. Here, traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

C:

“use least privilege when assigning directory and resource roles” describes another technical distinction. Here, traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

D:

“distinguish proof of identity from resource permission” explains a different mechanism. Here, traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Question 118

A school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. What should the team examine before accepting the result?

  1. Complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.
  2. Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.
  3. Disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.
  4. Sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.

Explanation

Correct Answer

B:

The situation is that a school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario. It is the relevant test because traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Incorrect Answers

A:

This evidence addresses “understand federation trust” instead of confirming the repair. To check this result, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

C:

That test concerns “choose a trusted identity provider for shared login”, not the requested outcome. To check this result, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

D:

The proposed check is relevant to “use least privilege when assigning directory and resource roles”, but not sufficient here. To check this result, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Question 119

A school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. The proposed shortcut is: "Assume cloud Microsoft Entra ID alone automatically supplies every classic AD DS domain-controller and Group Policy function with no architecture planning." Which failure is most likely?

  1. Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk responsibility.
  2. Authenticated but overprivileged users may modify or expose assets outside their duties because authorization was omitted.
  3. Legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.
  4. A departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

Explanation

Correct Answer

C:

The situation is that a school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. Legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated. The shortcut is unsafe because traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Incorrect Answers

A:

“Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk…” can arise elsewhere, but it is not the most direct risk here. Here, legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.

B:

That consequence concerns “Authenticated but overprivileged users may modify or expose assets outside their duties because authorization was omitted”, which is a different failure. Here, legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.

D:

The alternative risk relates to “A departed employee may retain active application accounts after central termination because relying services use unmanaged…”, not the stated mistake. Here, legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.

Question 120

For this case—A school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists.—which implementation and acceptance check are correctly paired?

  1. Action: Use a supported federated sign-in relationship when an application trusts an external identity provider's signed assertion rather than directly storing every user's password. Validation: Complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.
  2. Action: Authenticate a requesting principal first and then separately authorize only the actions it is allowed to perform on the target resource. Validation: Sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.
  3. Action: Use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle. Validation: Disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.
  4. Action: Use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. Validation: Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Explanation

Correct Answer

D:

The situation is that a school modernizes cloud user accounts but its local application still queries LDAP and expects a domain controller that no longer exists. Use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. Validation: Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario. The action and test belong together because traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Incorrect Answers

A:

That action-and-evidence pair concerns “understand federation trust”, not this decision. The appropriate action is to use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. To confirm, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

B:

The proposed pair focuses on “distinguish proof of identity from resource permission” instead. The appropriate action is to use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. To confirm, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

C:

“choose a trusted identity provider for shared login” evaluates a different intervention. The appropriate action is to use Active Directory Domain Services for suitable on-premises domain objects and Microsoft Entra ID for cloud identity, while clearly distinguishing their directory and protocol capabilities. To confirm, test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests