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 11

Question 100

A security and compliance reviewer considers: An employee's strong multifactor sign-in succeeds, yet a file sharing application mistakenly gives them tenant administrator privileges. Which response and evidence should be linked?

  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 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.
  3. 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.
  4. 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.

Explanation

Correct Answer

D:

The situation is that an employee's strong multifactor sign-in succeeds, yet a file sharing application mistakenly gives them tenant administrator privileges. 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. The action and test belong together because authentication establishes who the requester claims to be, while authorization determines the resources and operations that verified principal may use.

Incorrect Answers

A:

That action-and-evidence pair concerns “distinguish human and application identities”, not this decision. The appropriate action is to authenticate a requesting principal first and then separately authorize only the actions it is allowed to perform on the target resource. To confirm, sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.

B:

The proposed pair focuses on “explain active directory directory service roles” instead. The appropriate action is to authenticate a requesting principal first and then separately authorize only the actions it is allowed to perform on the target resource. To confirm, sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.

C:

“understand federation trust” evaluates a different intervention. The appropriate action is to authenticate a requesting principal first and then separately authorize only the actions it is allowed to perform on the target resource. To confirm, sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.

Question 101

A company wants staff to sign in to multiple approved SaaS apps without separate application-managed password stores for every system. Which action best addresses this requirement?

  1. Use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle.
  2. 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.
  3. Require a trustworthy principal identity and context-aware access decision before granting cloud data access, even when traffic originates from a familiar network.
  4. 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.

Explanation

Correct Answer

A:

Use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos. To verify, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

Incorrect Answers

B:

“explain active directory directory service roles” is related to another task, not the failure shown here. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

C:

This alternative focuses on “treat identity as a primary access boundary” instead of the required outcome. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

D:

That choice concerns “understand federation trust”, not the immediate requirement. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

Question 102

A cloud security learner considers: A company wants staff to sign in to multiple approved SaaS apps without separate application-managed password stores for every system. Which underlying principle applies?

  1. Authentication establishes who the requester claims to be, while authorization determines the resources and operations that verified principal may use.
  2. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.
  3. Cloud users and applications move across devices and locations, making asserted identity and appropriate permissions a more reliable boundary than a building perimeter alone.
  4. A single globally privileged account greatly increases attack impact and auditing difficulty compared with scoped roles limited to a particular service.

Explanation

Correct Answer

B:

An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos. This supports the decision to use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle.

Incorrect Answers

A:

The principle behind “distinguish proof of identity from resource permission” is not the one being tested. Here, an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

C:

“treat identity as a primary access boundary” explains a different mechanism. Here, an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

D:

That statement concerns “use least privilege when assigning directory and resource roles” rather than the cause in this case. Here, an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

Question 103

A company wants staff to sign in to multiple approved SaaS apps without separate application-managed password stores for every system. What should the team examine before accepting the result?

  1. 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. 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. 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

C:

Disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits. It is the relevant test 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” would verify a different part of the system. To check this result, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

B:

That test concerns “explain active directory directory service roles”, not the requested outcome. To check this result, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

D:

This evidence addresses “understand federation trust” instead of confirming the repair. To check this result, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

Question 104

A company wants staff to sign in to multiple approved SaaS apps without separate application-managed password stores for every system. The proposed shortcut is: "Allow each business app to create permanently independent passwords for departing employees with no centralized account lifecycle controls." Which failure is most likely?

  1. Authenticated but overprivileged users may modify or expose assets outside their duties because authorization was omitted.
  2. Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk responsibility.
  3. An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.
  4. A departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

Explanation

Correct Answer

D:

A departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities. The shortcut is unsafe because an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

Incorrect Answers

A:

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, a departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

B:

“Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk…” does not describe the result of this shortcut. Here, a departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

C:

The alternative risk relates to “An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience…”, not the stated mistake. Here, a departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

Question 105

For this case—A company wants staff to sign in to multiple approved SaaS apps without separate application-managed password stores for every system.—which implementation and acceptance check are correctly paired?

  1. 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.
  2. 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.
  3. 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.
  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

A:

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

B:

“understand federation trust” 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 linked action and check for “treat identity as a primary access boundary” would not resolve this case. 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:

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.

Question 106

A human resources departure process disables one corporate account but an unrelated vendor portal still accepts the former employee's local password. Which implementation or design choice most directly mitigates the stated issue?

  1. Authenticate a requesting principal first and then separately authorize only the actions it is allowed to perform on the target resource.
  2. Use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle.
  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. Assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function.

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. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos. To verify, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

Incorrect Answers

A:

“distinguish proof of identity from resource permission” is related to another task, not the failure shown here. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

C:

That choice concerns “explain active directory directory service roles”, not the immediate requirement. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

D:

The proposed action addresses “distinguish human and application identities” rather than the problem described. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

Question 107

A human resources departure process disables one corporate account but an unrelated vendor portal still accepts the former employee's local password. Which technical explanation most directly supports the right approach?

  1. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
  2. Cloud users and applications move across devices and locations, making asserted identity and appropriate permissions a more reliable boundary than a building perimeter alone.
  3. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.
  4. Authentication establishes who the requester claims to be, while authorization determines the resources and operations that verified principal may use.

Explanation

Correct Answer

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. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos. This supports the decision to use a central trusted identity provider to issue and validate sign-in assertions for applications that rely on the same enterprise identity lifecycle.

Incorrect Answers

A:

“distinguish human and application identities” describes another technical distinction. Here, an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

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. “treat identity as a primary access boundary” explains a different mechanism. Here, an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

D:

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. The principle behind “distinguish proof of identity from resource permission” is not the one being tested. Here, an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

Question 108

For this situation—A human resources departure process disables one corporate account but an unrelated vendor portal still accepts the former employee's local password.—which check provides the strongest verification?

  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. Sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.
  3. Sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.
  4. Disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

Explanation

Correct Answer

D:

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. Disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits. It is the relevant test because an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

Incorrect Answers

A:

That test concerns “understand federation trust”, not the requested outcome. To check this result, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

B:

The proposed check is relevant to “distinguish proof of identity from resource permission”, but not sufficient here. To check this result, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

C:

This evidence addresses “use least privilege when assigning directory and resource roles” instead of confirming the repair. To check this result, disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.

Question 109

A human resources departure process disables one corporate account but an unrelated vendor portal still accepts the former employee's local password. If the team does the following—"Allow each business app to create permanently independent passwords for departing employees with no centralized account lifecycle controls."—what could go wrong?

  1. A departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.
  2. The job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
  3. Required confidential records can remain exposed in storage or become irretrievable when hashing and encryption are treated as interchangeable operations.
  4. Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk responsibility.

Explanation

Correct Answer

A:

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. A departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities. The shortcut is unsafe because an identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.

Incorrect Answers

B:

The alternative risk relates to “The job can fail when the employee leaves and may expose broad administrative access because a…”, not the stated mistake. Here, a departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

C:

“Required confidential records can remain exposed in storage or become irretrievable when hashing and encryption are…” can arise elsewhere, but it is not the most direct risk here. Here, a departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

D:

That consequence concerns “Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk…”, which is a different failure. Here, a departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

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.

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