Microsoft SC-900 Dumps
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?
Explanation
Correct Answer
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
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.
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.
“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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
“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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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
- Microsoft SC-900 Practice Test 11 - 10 Questions (Last Reviewed 10-Nov-2026)
- Microsoft SC-900 Practice Test 12 - 10 Questions (Last Reviewed 09-Nov-2026)
- Microsoft SC-900 Practice Test 13 - 10 Questions (Last Reviewed 08-Nov-2026)
- Microsoft SC-900 Practice Test 14 - 10 Questions (Last Reviewed 07-Nov-2026)
- Microsoft SC-900 Practice Test 15 - 10 Questions (Last Reviewed 06-Nov-2026)