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 13

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.

Question 121

A supplier portal wants trusted partner employees to authenticate at their own organization without copying partner passwords into the portal. Which implementation or design choice most directly mitigates the stated issue?

  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. 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. Evaluate explicit user and device signals, enforce least privilege and assume a breach rather than trusting connections solely for being on the corporate network.

Explanation

Correct Answer

A:

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. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords. To verify, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

Incorrect Answers

B:

“explain active directory directory service roles” is related to another task, not the failure shown here. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

C:

This alternative focuses on “treat identity as a primary access boundary” instead of the required outcome. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

D:

That choice concerns “apply zero trust verification to each access request”, not the immediate requirement. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Question 122

A supplier portal wants trusted partner employees to authenticate at their own organization without copying partner passwords into the portal. Which technical explanation most directly supports the right approach?

  1. Governance sets accountable decisions, risk management evaluates likelihood and impact, and compliance maps applicable rules to controls and evidence rather than promising zero risk.
  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. Authentication establishes who the requester claims to be, while authorization determines the resources and operations that verified principal may use.
  4. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.

Explanation

Correct Answer

B:

Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords. This supports the decision to 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.

Incorrect Answers

A:

The principle behind “treat compliance evidence as distinct from risk acceptance” is not the one being tested. Here, federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

C:

“distinguish proof of identity from resource permission” explains a different mechanism. Here, federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

D:

That statement concerns “distinguish human and application identities” rather than the cause in this case. Here, federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Question 123

For this situation—A supplier portal wants trusted partner employees to authenticate at their own organization without copying partner passwords into the portal.—which check provides the strongest verification?

  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. Inspect the VM's installed security updates and its operating-system maintenance owner while confirming the hosting platform responsibility boundary.
  3. Complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.
  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

C:

Complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused. It is the relevant test because federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Incorrect Answers

A:

“distinguish human and application identities” would verify a different part of the system. To check this result, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

B:

That test concerns “distinguish customer guest os duty in IaaS”, not the requested outcome. To check this result, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

D:

This evidence addresses “treat identity as a primary access boundary” instead of confirming the repair. To check this result, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

Question 124

A supplier portal wants trusted partner employees to authenticate at their own organization without copying partner passwords into the portal. If the team does the following—"Treat any unsigned identity token from a partner website as valid authentication without checking the issuer and intended recipient."—what could go wrong?

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

D:

An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries. The shortcut is unsafe because federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

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, an attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.

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, an attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.

C:

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, an attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.

Question 125

A supplier portal wants trusted partner employees to authenticate at their own organization without copying partner passwords into the portal. Which action and validation evidence belong together?

  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: 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: Retain a customer-managed virtual machine operating-system update plan while distinguishing Azure's responsibility for physical hosts and datacenter infrastructure. Validation: Inspect the VM's installed security updates and its operating-system maintenance owner while confirming the hosting platform responsibility boundary.
  4. 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.

Explanation

Correct Answer

A:

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. The action and test belong together because federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Incorrect Answers

B:

“explain active directory directory service roles” evaluates a different intervention. The appropriate action is to 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. To confirm, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

C:

The linked action and check for “distinguish customer guest os duty in IaaS” would not resolve this case. The appropriate action is to 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. To confirm, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

D:

That action-and-evidence pair concerns “distinguish human and application identities”, not this decision. The appropriate action is to 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. To confirm, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

Question 126

An SC-900 learner considers: A developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. What is the most appropriate next decision?

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

Explanation

Correct Answer

B:

The situation is that a developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. 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. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords. To verify, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

Incorrect Answers

A:

“treat identity as a primary access boundary” is related to another task, not the failure shown here. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

C:

That choice concerns “assign cloud data and identity responsibilities in SaaS”, not the immediate requirement. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

D:

The proposed action addresses “choose a trusted identity provider for shared login” rather than the problem described. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Question 127

A developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. Why does the recommended approach address this particular concern?

  1. Cloud users and applications move across devices and locations, making asserted identity and appropriate permissions a more reliable boundary than a building perimeter alone.
  2. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.
  3. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.
  4. An IaaS provider manages underlying datacenter assets but the tenant still controls supported guest operating systems, installed applications and workload configuration.

Explanation

Correct Answer

C:

The situation is that a developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. Federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords. This supports the decision to 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.

Incorrect Answers

A:

“treat identity as a primary access boundary” describes another technical distinction. Here, federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

B:

“explain active directory directory service roles” explains a different mechanism. Here, federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

D:

The principle behind “distinguish customer guest os duty in IaaS” is not the one being tested. Here, federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Question 128

A developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. Which evidence best validates the proposed outcome?

  1. Sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.
  2. Sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.
  3. Review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
  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

D:

The situation is that a developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. Complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused. It is the relevant test because federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Incorrect Answers

A:

That test concerns “distinguish proof of identity from resource permission”, not the requested outcome. To check this result, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

B:

The proposed check is relevant to “use least privilege when assigning directory and resource roles”, but not sufficient here. To check this result, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

C:

This evidence addresses “distinguish human and application identities” instead of confirming the repair. To check this result, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

Question 129

Consider this situation: A developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. A team member suggests: "Treat any unsigned identity token from a partner website as valid authentication without checking the issuer and intended recipient." What is the main risk?

  1. An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.
  2. The job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
  3. A departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.
  4. Authenticated but overprivileged users may modify or expose assets outside their duties because authorization was omitted.

Explanation

Correct Answer

A:

The situation is that a developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries. The shortcut is unsafe because federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Incorrect Answers

B:

The situation is that a developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. 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, an attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.

C:

“A departed employee may retain active application accounts after central termination because relying services use unmanaged…” can arise elsewhere, but it is not the most direct risk here. Here, an attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.

D:

The situation is that a developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. 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, an attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.

Question 130

A security and compliance reviewer considers: A developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. Which response and evidence should be linked?

  1. 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.
  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: Maintain a governance process that assigns control owners, assesses business risk and documents evidence and residual risk decisions under the organization's obligations. Validation: Review a sample risk register entry with accountable owner, applicable policy, tested control evidence and explicitly approved remaining exposure.
  4. 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.

Explanation

Correct Answer

B:

The situation is that a developer accepts a SAML response for another application as proof that a user may enter a confidential finance service. 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. The action and test belong together because federation passes verifiable identity claims across a trust boundary, so relying services validate assertion issuer, audience and lifetime rather than handling upstream passwords.

Incorrect Answers

A:

“treat identity as a primary access boundary” evaluates a different intervention. The appropriate action is to 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. To confirm, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

C:

That action-and-evidence pair concerns “treat compliance evidence as distinct from risk acceptance”, not this decision. The appropriate action is to 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. To confirm, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

D:

The proposed pair focuses on “distinguish human and application identities” instead. The appropriate action is to 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. To confirm, complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.

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