McAfee-Secured Website

Exam Bundle

Exam Code: SC-900

Exam Name Microsoft Security, Compliance, and Identity Fundamentals

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Security, Compliance, and Identity Fundamentals

Microsoft SC-900 Bundle $44.99

100% Microsoft SC-900 Guaranteed Success With Testking Training Materials

Get Real SC-900 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    SC-900 Questions & Answers

    259 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual SC-900 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • SC-900 Video Course

    SC-900 Video Course

    147 Video Lectures

    SC-900 Video Course is developed by Microsoft Professionals to help you pass the SC-900 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Security, Compliance, and Identity Fundamentals exam.
  • Study Guide

    SC-900 Study Guide

    413 PDF Pages

    Developed by industry experts, this 413-page guide spells out in painstaking detail all of the information you need to ace SC-900 exam.

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

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    259 Questions

    $124.99
  • SC-900 Video Course

    Video Course

    147 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    413 PDF Pages

    $29.99

Microsoft SC-900 Practice Test 13

Question 120

The tenant administration team at Blue Haven Media supports creative files and production workspaces. An assessment finds: A contractor is authorized for one document library but receives organization-wide write access after group membership is misapplied. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. The contractor edits only the assigned library and encounters an access denial in unrelated libraries.
  2. Sign-in evidence confirms the person was authenticated while the resource audit records a distinct permission denial.
  3. A user signs in once but is denied an application role that was never assigned.
  4. A valid federated user session still fails a resource authorization check unless the intended local role is assigned.

Explanation

Correct Answer

A:

The contractor edits only the assigned library and encounters an access denial in unrelated libraries. This is the relevant proof because it tests whether the selected corrective action (Evaluate group and role assignments as authorization controls limited to the intended resource) addressed the initiating problem (A contractor is authorized for one document library but receives organization-wide write access after group membership is misapplied) in Blue Haven Media's creative files and production workspaces environment, not merely whether a task was marked complete.

Incorrect Answers

B:

Sign-in evidence confirms the person was authenticated while the resource audit records a distinct permission denial. This is useful evidence for a different situation (A user enters correct credentials but cannot open a restricted payroll application and the help desk treats the failure as unsuccessful authentication) and action (Separate authentication of the identity from subsequent authorization to the payroll resource). For the reported issue at Blue Haven Media, it does not establish the required outcome: The contractor edits only the assigned library and encounters an access denial in unrelated libraries.

C:

A user signs in once but is denied an application role that was never assigned. This is useful evidence for a different situation (A single sign-on deployment is expected to grant every application role simply because the user authenticated once) and action (Keep application authorization decisions separate from the convenience of a shared single sign-on session). For the reported issue at Blue Haven Media, it does not establish the required outcome: The contractor edits only the assigned library and encounters an access denial in unrelated libraries.

D:

A valid federated user session still fails a resource authorization check unless the intended local role is assigned. This is useful evidence for a different situation (A directory administrator believes identity federation automatically copies every authorization permission from a partner tenant) and action (Document the federation authentication trust separately from locally configured application roles and access policy). For the reported issue at Blue Haven Media, it does not establish the required outcome: The contractor edits only the assigned library and encounters an access denial in unrelated libraries.

Question 121

The tenant administration team at Oceanview Payments supports regulated card workflows and employee access. An assessment finds: A product manager confuses identifying an employee's username with establishing that the person controls that account. Which action BEST addresses the described security, identity, or compliance gap?

  1. Require a valid authentication method rather than accepting the mere presentation of an account identifier.
  2. Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account.
  3. Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions.
  4. Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in.

Explanation

Correct Answer

A:

Require a valid authentication method rather than accepting the mere presentation of an account identifier. This directly addresses the observed weakness: A product manager confuses identifying an employee's username with establishing that the person controls that account. For Oceanview Payments and its regulated card workflows and employee access, a meaningful acceptance check would be: A claim of a known username without valid authentication proof does not produce a signed-in session.

Incorrect Answers

B:

Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account. This addresses a different security or governance gap: A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities. For Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

C:

Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions. This addresses a different security or governance gap: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. For Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

D:

Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in. This addresses a different security or governance gap: A development team generates homegrown proof-of-login strings instead of trusting the organization's designated identity provider. For Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

Question 122

The tenant administration team at Oceanview Payments supports regulated card workflows and employee access. An assessment finds: A product manager confuses identifying an employee's username with establishing that the person controls that account. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected.
  2. Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.
  3. A claim of a known username without valid authentication proof does not produce a signed-in session.
  4. The export runs with an auditable workload identity and an unrelated privilege request is denied.

Explanation

Correct Answer

C:

A claim of a known username without valid authentication proof does not produce a signed-in session. This is the relevant proof because it tests whether the selected corrective action (Require a valid authentication method rather than accepting the mere presentation of an account identifier) addressed the initiating problem (A product manager confuses identifying an employee's username with establishing that the person controls that account) in Oceanview Payments's regulated card workflows and employee access environment, not merely whether a task was marked complete.

Incorrect Answers

A:

A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected. This is useful evidence for a different situation (A development team generates homegrown proof-of-login strings instead of trusting the organization's designated identity provider) and action (Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in). For the reported issue at Oceanview Payments, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

B:

Disabling the account and revoking active access prevents the former employee from obtaining another trusted session. This is useful evidence for a different situation (A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access) and action (Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions). For the reported issue at Oceanview Payments, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

D:

The export runs with an auditable workload identity and an unrelated privilege request is denied. This is useful evidence for a different situation (A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities) and action (Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account). For the reported issue at Oceanview Payments, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

Question 123

At Orion Network Services, an incident follow-up uncovers the following situation affecting subscriber applications and remote operations: A product manager confuses identifying an employee's username with establishing that the person controls that account. Which action BEST addresses the described security, identity, or compliance gap?

  1. Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account.
  2. Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in.
  3. Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions.
  4. Require a valid authentication method rather than accepting the mere presentation of an account identifier.

Explanation

Correct Answer

D:

Require a valid authentication method rather than accepting the mere presentation of an account identifier. This directly addresses the observed weakness: A product manager confuses identifying an employee's username with establishing that the person controls that account. For Orion Network Services and its subscriber applications and remote operations, a meaningful acceptance check would be: A claim of a known username without valid authentication proof does not produce a signed-in session.

Incorrect Answers

A:

Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account. This addresses a different security or governance gap: A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities. For Orion Network Services and its subscriber applications and remote operations, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

B:

Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in. This addresses a different security or governance gap: A development team generates homegrown proof-of-login strings instead of trusting the organization's designated identity provider. For Orion Network Services and its subscriber applications and remote operations, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

C:

Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions. This addresses a different security or governance gap: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. For Orion Network Services and its subscriber applications and remote operations, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

Question 124

At Orion Network Services, an incident follow-up uncovers the following situation affecting subscriber applications and remote operations: A product manager confuses identifying an employee's username with establishing that the person controls that account. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A claim of a known username without valid authentication proof does not produce a signed-in session.
  2. A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected.
  3. The export runs with an auditable workload identity and an unrelated privilege request is denied.
  4. Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

Explanation

Correct Answer

A:

A claim of a known username without valid authentication proof does not produce a signed-in session. This is the relevant proof because it tests whether the selected corrective action (Require a valid authentication method rather than accepting the mere presentation of an account identifier) addressed the initiating problem (A product manager confuses identifying an employee's username with establishing that the person controls that account) in Orion Network Services's subscriber applications and remote operations environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected. This is useful evidence for a different situation (A development team generates homegrown proof-of-login strings instead of trusting the organization's designated identity provider) and action (Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in). For the reported issue at Orion Network Services, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

C:

The export runs with an auditable workload identity and an unrelated privilege request is denied. This is useful evidence for a different situation (A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities) and action (Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account). For the reported issue at Orion Network Services, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

D:

Disabling the account and revoking active access prevents the former employee from obtaining another trusted session. This is useful evidence for a different situation (A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access) and action (Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions). For the reported issue at Orion Network Services, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

Question 125

During a protection architecture discussion at Aspen Digital, the identity operations team identifies this issue: A product manager confuses identifying an employee's username with establishing that the person controls that account. Which action BEST addresses the described security, identity, or compliance gap?

  1. Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in.
  2. Require a valid authentication method rather than accepting the mere presentation of an account identifier.
  3. Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account.
  4. Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions.

Explanation

Correct Answer

B:

Require a valid authentication method rather than accepting the mere presentation of an account identifier. This directly addresses the observed weakness: A product manager confuses identifying an employee's username with establishing that the person controls that account. For Aspen Digital and its client advisory systems and shared files, a meaningful acceptance check would be: A claim of a known username without valid authentication proof does not produce a signed-in session.

Incorrect Answers

A:

Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in. This addresses a different security or governance gap: A development team generates homegrown proof-of-login strings instead of trusting the organization's designated identity provider. For Aspen Digital and its client advisory systems and shared files, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

C:

Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account. This addresses a different security or governance gap: A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities. For Aspen Digital and its client advisory systems and shared files, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

D:

Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions. This addresses a different security or governance gap: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. For Aspen Digital and its client advisory systems and shared files, the issue is instead: A product manager confuses identifying an employee's username with establishing that the person controls that account. This alternative alone would not demonstrate the needed result: A claim of a known username without valid authentication proof does not produce a signed-in session.

Question 126

During a protection architecture discussion at Aspen Digital, the identity operations team identifies this issue: A product manager confuses identifying an employee's username with establishing that the person controls that account. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A claim of a known username without valid authentication proof does not produce a signed-in session.
  2. A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected.
  3. Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.
  4. The export runs with an auditable workload identity and an unrelated privilege request is denied.

Explanation

Correct Answer

A:

A claim of a known username without valid authentication proof does not produce a signed-in session. This is the relevant proof because it tests whether the selected corrective action (Require a valid authentication method rather than accepting the mere presentation of an account identifier) addressed the initiating problem (A product manager confuses identifying an employee's username with establishing that the person controls that account) in Aspen Digital's client advisory systems and shared files environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected. This is useful evidence for a different situation (A development team generates homegrown proof-of-login strings instead of trusting the organization's designated identity provider) and action (Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in). For the reported issue at Aspen Digital, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

C:

Disabling the account and revoking active access prevents the former employee from obtaining another trusted session. This is useful evidence for a different situation (A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access) and action (Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions). For the reported issue at Aspen Digital, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

D:

The export runs with an auditable workload identity and an unrelated privilege request is denied. This is useful evidence for a different situation (A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities) and action (Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account). For the reported issue at Aspen Digital, it does not establish the required outcome: A claim of a known username without valid authentication proof does not produce a signed-in session.

Question 127

During a controlled policy review at Silver Cove Payments, the identity operations team identifies this issue: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. Which action BEST addresses the described security, identity, or compliance gap?

  1. Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions.
  2. Document the federation authentication trust separately from locally configured application roles and access policy.
  3. Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account.
  4. Evaluate identity federation to accept authentication assertions from an approved external identity provider.

Explanation

Correct Answer

A:

Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions. This directly addresses the observed weakness: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. For Silver Cove Payments and its transaction data and fraud monitoring, a meaningful acceptance check would be: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

Incorrect Answers

B:

Document the federation authentication trust separately from locally configured application roles and access policy. This addresses a different security or governance gap: A directory administrator believes identity federation automatically copies every authorization permission from a partner tenant. For Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. This alternative alone would not demonstrate the needed result: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

C:

Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account. This addresses a different security or governance gap: A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities. For Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. This alternative alone would not demonstrate the needed result: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

D:

Evaluate identity federation to accept authentication assertions from an approved external identity provider. This addresses a different security or governance gap: Two independent organizations share a web application but require users to create duplicate local passwords because no trust relationship exists. For Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. This alternative alone would not demonstrate the needed result: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

Question 128

During a controlled policy review at Silver Cove Payments, the identity operations team identifies this issue: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.
  2. A valid federated user session still fails a resource authorization check unless the intended local role is assigned.
  3. The export runs with an auditable workload identity and an unrelated privilege request is denied.
  4. A partner user signs in with the home identity while access to the application remains governed by local authorization rules.

Explanation

Correct Answer

A:

Disabling the account and revoking active access prevents the former employee from obtaining another trusted session. This is the relevant proof because it tests whether the selected corrective action (Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions) addressed the initiating problem (A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access) in Silver Cove Payments's transaction data and fraud monitoring environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A valid federated user session still fails a resource authorization check unless the intended local role is assigned. This is useful evidence for a different situation (A directory administrator believes identity federation automatically copies every authorization permission from a partner tenant) and action (Document the federation authentication trust separately from locally configured application roles and access policy). For the reported issue at Silver Cove Payments, it does not establish the required outcome: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

C:

The export runs with an auditable workload identity and an unrelated privilege request is denied. This is useful evidence for a different situation (A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities) and action (Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account). For the reported issue at Silver Cove Payments, it does not establish the required outcome: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

D:

A partner user signs in with the home identity while access to the application remains governed by local authorization rules. This is useful evidence for a different situation (Two independent organizations share a web application but require users to create duplicate local passwords because no trust relationship exists) and action (Evaluate identity federation to accept authentication assertions from an approved external identity provider). For the reported issue at Silver Cove Payments, it does not establish the required outcome: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

Question 129

The compliance analyst at Horizon Energy Services supports remote field-worker sign-ins and operations. An assessment finds: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. Which action BEST addresses the described security, identity, or compliance gap?

  1. Document the federation authentication trust separately from locally configured application roles and access policy.
  2. Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions.
  3. Evaluate identity federation to accept authentication assertions from an approved external identity provider.
  4. Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account.

Explanation

Correct Answer

B:

Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions. This directly addresses the observed weakness: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. For Horizon Energy Services and its remote field-worker sign-ins and operations, a meaningful acceptance check would be: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

Incorrect Answers

A:

Document the federation authentication trust separately from locally configured application roles and access policy. This addresses a different security or governance gap: A directory administrator believes identity federation automatically copies every authorization permission from a partner tenant. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. This alternative alone would not demonstrate the needed result: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

C:

Evaluate identity federation to accept authentication assertions from an approved external identity provider. This addresses a different security or governance gap: Two independent organizations share a web application but require users to create duplicate local passwords because no trust relationship exists. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. This alternative alone would not demonstrate the needed result: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

D:

Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account. This addresses a different security or governance gap: A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. This alternative alone would not demonstrate the needed result: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

Question 130

The compliance analyst at Horizon Energy Services supports remote field-worker sign-ins and operations. An assessment finds: A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A partner user signs in with the home identity while access to the application remains governed by local authorization rules.
  2. Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.
  3. A valid federated user session still fails a resource authorization check unless the intended local role is assigned.
  4. The export runs with an auditable workload identity and an unrelated privilege request is denied.

Explanation

Correct Answer

B:

Disabling the account and revoking active access prevents the former employee from obtaining another trusted session. This is the relevant proof because it tests whether the selected corrective action (Design identity lifecycle offboarding and regularly review trust relationships and downstream sessions) addressed the initiating problem (A former employee retains federated access because the identity lifecycle in the home organization was not connected to downstream application access) in Horizon Energy Services's remote field-worker sign-ins and operations environment, not merely whether a task was marked complete.

Incorrect Answers

A:

A partner user signs in with the home identity while access to the application remains governed by local authorization rules. This is useful evidence for a different situation (Two independent organizations share a web application but require users to create duplicate local passwords because no trust relationship exists) and action (Evaluate identity federation to accept authentication assertions from an approved external identity provider). For the reported issue at Horizon Energy Services, it does not establish the required outcome: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

C:

A valid federated user session still fails a resource authorization check unless the intended local role is assigned. This is useful evidence for a different situation (A directory administrator believes identity federation automatically copies every authorization permission from a partner tenant) and action (Document the federation authentication trust separately from locally configured application roles and access policy). For the reported issue at Horizon Energy Services, it does not establish the required outcome: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.

D:

The export runs with an auditable workload identity and an unrelated privilege request is denied. This is useful evidence for a different situation (A scheduled data export is run using a shared employee password because the team assumes only human beings can have identities) and action (Assign the nonhuman workload a governed service identity and scoped authorization instead of a personal account). For the reported issue at Horizon Energy Services, it does not establish the required outcome: Disabling the account and revoking active access prevents the former employee from obtaining another trusted session.