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

  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.

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?

  1. Use supported TLS for sensitive data crossing networks and independently protect data at rest through suitable storage encryption and access permissions.
  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. Assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function.
  4. Grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

“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?

  1. A single globally privileged account greatly increases attack impact and auditing difficulty compared with scoped roles limited to a particular service.
  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. 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

D:

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

A:

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

B:

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.

C:

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?

  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. Sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.
  3. Disable a synthetic test employee in the identity provider and confirm connected applications reject future authenticated sessions as policy permits.
  4. Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Explanation

Correct Answer

A:

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

B:

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.

C:

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

D:

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?

  1. Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk responsibility.
  2. The job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
  3. An unauthorized visitor or compromised device can reach protected data when the system confuses network attachment with identity assurance.
  4. An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience boundaries.

Explanation

Correct Answer

B:

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

A:

The alternative risk relates to “Compromise or mistake involving one routine support user can change enterprise-wide settings beyond any authorized helpdesk…”, not the stated mistake. Here, the job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.

C:

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.

D:

“An attacker may impersonate users when relying services accept assertions without checking trust, signing and audience…” does not describe the result of this shortcut. Here, 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?

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

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

“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?

  1. 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.
  2. Grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing.
  3. 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.
  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

D:

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

A:

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.

B:

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.

C:

“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?

  1. Applications need machine-authenticated service access, while human interactive sign-ins have different lifecycle, risk and authentication controls.
  2. A single globally privileged account greatly increases attack impact and auditing difficulty compared with scoped roles limited to a particular service.
  3. An identity provider authenticates the user and supplies trusted identity claims, allowing relying applications to avoid maintaining unrelated credential silos.
  4. Traditional AD DS provides domain controllers, Kerberos, LDAP and Group Policy, whereas Microsoft Entra ID is a cloud identity platform with different management semantics.

Explanation

Correct Answer

A:

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

B:

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.

C:

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

D:

“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?

  1. Sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.
  2. Review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
  3. Verify the same test identity receives appropriate approved rights from an office and remote location while a different principal is denied.
  4. Test a legacy domain-joined workstation's Kerberos and Group Policy dependencies separately from a Microsoft 365 cloud sign-in scenario.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Decision makers may unknowingly accept unmanaged exposure or fail an audit when declared controls were never implemented or assessed.
  2. Legacy line-of-business computers may lose domain authentication or policy processing when distinct directory service capabilities are conflated.
  3. The job can fail when the employee leaves and may expose broad administrative access because a personal credential was reused.
  4. A departed employee may retain active application accounts after central termination because relying services use unmanaged isolated identities.

Explanation

Correct Answer

C:

The situation is that a 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

A:

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

B:

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.

D:

The alternative risk relates to “A departed employee may retain active application accounts after central termination because relying services use unmanaged…”, not the stated mistake. Here, 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?

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

D:

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

A:

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.

B:

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.

C:

“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