Microsoft SC-900 Dumps
Microsoft SC-900 Practice Test 14
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.
Question 131
A nightly invoicing application needs to write only one report dataset without relying on the password of the person who authored it. Which action best addresses this requirement?
Explanation
Correct Answer
Assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls. To verify, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
Incorrect Answers
This alternative focuses on “protect data in transit with authenticated encryption” instead of the required outcome. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
That choice concerns “choose a trusted identity provider for shared login”, not the immediate requirement. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
“use least privilege when assigning directory and resource roles” is related to another task, not the failure shown here. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Question 132
A cloud security learner considers: A nightly invoicing application needs to write only one report dataset without relying on the password of the person who authored it. Which underlying principle applies?
Explanation
Correct Answer
Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls. This supports the decision to assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function.
Incorrect Answers
“use least privilege when assigning directory and resource roles” explains a different mechanism. Here, applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
That statement concerns “explain active directory directory service roles” rather than the cause in this case. Here, applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
The principle behind “distinguish proof of identity from resource permission” is not the one being tested. Here, applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Question 133
A nightly invoicing application needs to write only one report dataset without relying on the password of the person who authored it. What should the team examine before accepting the result?
Explanation
Correct Answer
Review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role. It is the relevant test because applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Incorrect Answers
This evidence addresses “distinguish proof of identity from resource permission” instead of confirming the repair. To check this result, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
“choose a trusted identity provider for shared login” would verify a different part of the system. To check this result, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
That test concerns “explain active directory directory service roles”, not the requested outcome. To check this result, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
Question 134
A nightly invoicing application needs to write only one report dataset without relying on the password of the person who authored it. The proposed shortcut is: "Run an unattended production automation using one employee's administrator password embedded in a scheduled script." Which failure is most likely?
Explanation
Correct Answer
The job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused. The shortcut is unsafe because applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Incorrect Answers
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, the job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
That consequence concerns “An unauthorized visitor or compromised device can reach protected data when the system confuses network attachment…”, which is a different failure. Here, the job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
“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, the job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
Question 135
For this case—A nightly invoicing application needs to write only one report dataset without relying on the password of the person who authored it.—which implementation and acceptance check are correctly paired?
Explanation
Correct Answer
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. The action and test belong together because applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Incorrect Answers
The linked action and check for “treat compliance evidence as distinct from risk acceptance” would not resolve this case. The appropriate action is to assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. To confirm, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
That action-and-evidence pair concerns “choose a trusted identity provider for shared login”, not this decision. The appropriate action is to assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. To confirm, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
“treat identity as a primary access boundary” evaluates a different intervention. The appropriate action is to assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. To confirm, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
Question 136
A cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. Which implementation or design choice most directly mitigates the stated issue?
Explanation
Correct Answer
The situation is that a cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. Assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls. To verify, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
Incorrect Answers
That choice concerns “explain active directory directory service roles”, not the immediate requirement. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
The proposed action addresses “use least privilege when assigning directory and resource roles” rather than the problem described. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
“understand federation trust” is related to another task, not the failure shown here. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Question 137
A cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. Which technical explanation most directly supports the right approach?
Explanation
Correct Answer
The situation is that a cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls. This supports the decision to assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function.
Incorrect Answers
The principle behind “use least privilege when assigning directory and resource roles” is not the one being tested. Here, applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
“choose a trusted identity provider for shared login” describes another technical distinction. Here, applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
“explain active directory directory service roles” explains a different mechanism. Here, applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Question 138
For this situation—A cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar.—which check provides the strongest verification?
Explanation
Correct Answer
The situation is that a cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. Review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role. It is the relevant test because applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Incorrect Answers
The situation is that a cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. This evidence addresses “distinguish proof of identity from resource permission” instead of confirming the repair. To check this result, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
That test concerns “treat identity as a primary access boundary”, not the requested outcome. To check this result, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
The proposed check is relevant to “explain active directory directory service roles”, but not sufficient here. To check this result, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
Question 139
A cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. If the team does the following—"Run an unattended production automation using one employee's administrator password embedded in a scheduled script."—what could go wrong?
Explanation
Correct Answer
The situation is that a cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. The job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused. The shortcut is unsafe because applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Incorrect Answers
“Decision makers may unknowingly accept unmanaged exposure or fail an audit when declared controls were never…” can arise elsewhere, but it is not the most direct risk here. Here, the job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
That consequence concerns “Legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are…”, which is a different failure. Here, the job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
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, the job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
Question 140
A cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. Which action and validation evidence belong together?
Explanation
Correct Answer
The situation is that a cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. 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. The action and test belong together because applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
Incorrect Answers
The situation is that a cloud automation developer stores a domain administrator's password in a repository because service principals appear unfamiliar. That action-and-evidence pair concerns “choose a trusted identity provider for shared login”, not this decision. The appropriate action is to assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. To confirm, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
The proposed pair focuses on “use least privilege when assigning directory and resource roles” instead. The appropriate action is to assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. To confirm, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
“distinguish proof of identity from resource permission” evaluates a different intervention. The appropriate action is to assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. To confirm, review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests
- 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)
- Microsoft SC-900 Practice Test 16 - 10 Questions (Last Reviewed 05-Nov-2026)