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 19

Question 180

During a scheduled security audit at Aspen Digital, the identity operations team identifies this issue: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. The function obtains a token without a committed secret and an unauthorized resource operation fails.
  2. A replacement compute resource uses the same authorized identity without creating a new embedded credential.
  3. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.
  4. After resource deletion the old identity can no longer be used and its former permissions are reviewed.

Explanation

Correct Answer

A:

The function obtains a token without a committed secret and an unauthorized resource operation fails. This is the relevant proof because it tests whether the selected corrective action (Use a managed identity for the supported Azure workload and grant it the smallest appropriate role) addressed the initiating problem (A scheduled Azure function stores a long-lived client secret in source code to access another Azure service) in Aspen Digital's client advisory systems and shared files environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is useful evidence for a different situation (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) and action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources). For the reported issue at Aspen Digital, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

C:

Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked. This is useful evidence for a different situation (A system integration uses a human administrator identity for app-only API calls and fails whenever the administrator changes their password) and action (Give the application an app registration and workload identity with the required API permissions). For the reported issue at Aspen Digital, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

D:

After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is useful evidence for a different situation (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) and action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource). For the reported issue at Aspen Digital, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

Question 181

During an incident follow-up at Silver Cove Payments, the identity operations team identifies this issue: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. Which action BEST addresses the described security, identity, or compliance gap?

  1. Give the application an app registration and workload identity with the required API permissions.
  2. Use a managed identity for the supported Azure workload and grant it the smallest appropriate role.
  3. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  4. Recognize that a system-assigned managed identity follows the lifecycle of its associated resource.

Explanation

Correct Answer

C:

Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources. This directly addresses the observed weakness: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. For Silver Cove Payments and its transaction data and fraud monitoring, a meaningful acceptance check would be: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Incorrect Answers

A:

Give the application an app registration and workload identity with the required API permissions. This addresses a different security or governance gap: A system integration uses a human administrator identity for app-only API calls and fails whenever the administrator changes their password. For Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

B:

Use a managed identity for the supported Azure workload and grant it the smallest appropriate role. This addresses a different security or governance gap: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. For Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

D:

Recognize that a system-assigned managed identity follows the lifecycle of its associated resource. This addresses a different security or governance gap: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. For Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Question 182

During an incident follow-up at Silver Cove Payments, the identity operations team identifies this issue: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. After resource deletion the old identity can no longer be used and its former permissions are reviewed.
  2. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.
  3. The function obtains a token without a committed secret and an unauthorized resource operation fails.
  4. A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Explanation

Correct Answer

D:

A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is the relevant proof because it tests whether the selected corrective action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources) addressed the initiating problem (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) in Silver Cove Payments's transaction data and fraud monitoring environment, not merely whether a task was marked complete.

Incorrect Answers

A:

After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is useful evidence for a different situation (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) and action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource). For the reported issue at Silver Cove Payments, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

B:

Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked. This is useful evidence for a different situation (A system integration uses a human administrator identity for app-only API calls and fails whenever the administrator changes their password) and action (Give the application an app registration and workload identity with the required API permissions). For the reported issue at Silver Cove Payments, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

C:

The function obtains a token without a committed secret and an unauthorized resource operation fails. This is useful evidence for a different situation (A scheduled Azure function stores a long-lived client secret in source code to access another Azure service) and action (Use a managed identity for the supported Azure workload and grant it the smallest appropriate role). For the reported issue at Silver Cove Payments, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Question 183

The compliance analyst at Horizon Energy Services supports remote field-worker sign-ins and operations. An assessment finds: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. Which action BEST addresses the described security, identity, or compliance gap?

  1. Give the application an app registration and workload identity with the required API permissions.
  2. Recognize that a system-assigned managed identity follows the lifecycle of its associated resource.
  3. Use a managed identity for the supported Azure workload and grant it the smallest appropriate role.
  4. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.

Explanation

Correct Answer

D:

Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources. This directly addresses the observed weakness: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. For Horizon Energy Services and its remote field-worker sign-ins and operations, a meaningful acceptance check would be: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Incorrect Answers

A:

Give the application an app registration and workload identity with the required API permissions. This addresses a different security or governance gap: A system integration uses a human administrator identity for app-only API calls and fails whenever the administrator changes their password. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

B:

Recognize that a system-assigned managed identity follows the lifecycle of its associated resource. This addresses a different security or governance gap: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

C:

Use a managed identity for the supported Azure workload and grant it the smallest appropriate role. This addresses a different security or governance gap: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Question 184

The compliance analyst at Horizon Energy Services supports remote field-worker sign-ins and operations. An assessment finds: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. After resource deletion the old identity can no longer be used and its former permissions are reviewed.
  2. The function obtains a token without a committed secret and an unauthorized resource operation fails.
  3. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.
  4. A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Explanation

Correct Answer

D:

A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is the relevant proof because it tests whether the selected corrective action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources) addressed the initiating problem (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) in Horizon Energy Services's remote field-worker sign-ins and operations environment, not merely whether a task was marked complete.

Incorrect Answers

A:

After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is useful evidence for a different situation (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) and action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource). For the reported issue at Horizon Energy Services, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

B:

The function obtains a token without a committed secret and an unauthorized resource operation fails. This is useful evidence for a different situation (A scheduled Azure function stores a long-lived client secret in source code to access another Azure service) and action (Use a managed identity for the supported Azure workload and grant it the smallest appropriate role). For the reported issue at Horizon Energy Services, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

C:

Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked. This is useful evidence for a different situation (A system integration uses a human administrator identity for app-only API calls and fails whenever the administrator changes their password) and action (Give the application an app registration and workload identity with the required API permissions). For the reported issue at Horizon Energy Services, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Question 185

At Marshfield Bank, a migration readiness assessment uncovers the following situation affecting payments and confidential client information: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. Which action BEST addresses the described security, identity, or compliance gap?

  1. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  2. Give the application an app registration and workload identity with the required API permissions.
  3. Use a managed identity for the supported Azure workload and grant it the smallest appropriate role.
  4. Recognize that a system-assigned managed identity follows the lifecycle of its associated resource.

Explanation

Correct Answer

A:

Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources. This directly addresses the observed weakness: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. For Marshfield Bank and its payments and confidential client information, a meaningful acceptance check would be: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Incorrect Answers

B:

Give the application an app registration and workload identity with the required API permissions. This addresses a different security or governance gap: A system integration uses a human administrator identity for app-only API calls and fails whenever the administrator changes their password. For Marshfield Bank and its payments and confidential client information, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

C:

Use a managed identity for the supported Azure workload and grant it the smallest appropriate role. This addresses a different security or governance gap: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. For Marshfield Bank and its payments and confidential client information, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

D:

Recognize that a system-assigned managed identity follows the lifecycle of its associated resource. This addresses a different security or governance gap: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. For Marshfield Bank and its payments and confidential client information, the issue is instead: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. This alternative alone would not demonstrate the needed result: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Question 186

At Marshfield Bank, a migration readiness assessment uncovers the following situation affecting payments and confidential client information: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A replacement compute resource uses the same authorized identity without creating a new embedded credential.
  2. The function obtains a token without a committed secret and an unauthorized resource operation fails.
  3. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.
  4. After resource deletion the old identity can no longer be used and its former permissions are reviewed.

Explanation

Correct Answer

A:

A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is the relevant proof because it tests whether the selected corrective action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources) addressed the initiating problem (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) in Marshfield Bank's payments and confidential client information environment, not merely whether a task was marked complete.

Incorrect Answers

B:

The function obtains a token without a committed secret and an unauthorized resource operation fails. This is useful evidence for a different situation (A scheduled Azure function stores a long-lived client secret in source code to access another Azure service) and action (Use a managed identity for the supported Azure workload and grant it the smallest appropriate role). For the reported issue at Marshfield Bank, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

C:

Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked. This is useful evidence for a different situation (A system integration uses a human administrator identity for app-only API calls and fails whenever the administrator changes their password) and action (Give the application an app registration and workload identity with the required API permissions). For the reported issue at Marshfield Bank, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

D:

After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is useful evidence for a different situation (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) and action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource). For the reported issue at Marshfield Bank, it does not establish the required outcome: A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Question 187

At Northbridge University, a new-service rollout uncovers the following situation affecting student collaboration and research access: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. Which action BEST addresses the described security, identity, or compliance gap?

  1. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  2. Distinguish application registrations, service principals and human user objects for accurate lifecycle management.
  3. Recognize that a system-assigned managed identity follows the lifecycle of its associated resource.
  4. Use a managed identity for the supported Azure workload and grant it the smallest appropriate role.

Explanation

Correct Answer

C:

Recognize that a system-assigned managed identity follows the lifecycle of its associated resource. This directly addresses the observed weakness: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. For Northbridge University and its student collaboration and research access, a meaningful acceptance check would be: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

Incorrect Answers

A:

Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources. This addresses a different security or governance gap: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. For Northbridge University and its student collaboration and research access, the issue is instead: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. This alternative alone would not demonstrate the needed result: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

B:

Distinguish application registrations, service principals and human user objects for accurate lifecycle management. This addresses a different security or governance gap: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. For Northbridge University and its student collaboration and research access, the issue is instead: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. This alternative alone would not demonstrate the needed result: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

D:

Use a managed identity for the supported Azure workload and grant it the smallest appropriate role. This addresses a different security or governance gap: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. For Northbridge University and its student collaboration and research access, the issue is instead: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. This alternative alone would not demonstrate the needed result: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

Question 188

At Northbridge University, a new-service rollout uncovers the following situation affecting student collaboration and research access: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. After resource deletion the old identity can no longer be used and its former permissions are reviewed.
  2. A replacement compute resource uses the same authorized identity without creating a new embedded credential.
  3. An identity inventory lists application service principals separately from workforce user accounts and group memberships.
  4. The function obtains a token without a committed secret and an unauthorized resource operation fails.

Explanation

Correct Answer

A:

After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is the relevant proof because it tests whether the selected corrective action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource) addressed the initiating problem (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) in Northbridge University's student collaboration and research access environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is useful evidence for a different situation (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) and action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources). For the reported issue at Northbridge University, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

C:

An identity inventory lists application service principals separately from workforce user accounts and group memberships. This is useful evidence for a different situation (An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory) and action (Distinguish application registrations, service principals and human user objects for accurate lifecycle management). For the reported issue at Northbridge University, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

D:

The function obtains a token without a committed secret and an unauthorized resource operation fails. This is useful evidence for a different situation (A scheduled Azure function stores a long-lived client secret in source code to access another Azure service) and action (Use a managed identity for the supported Azure workload and grant it the smallest appropriate role). For the reported issue at Northbridge University, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

Question 189

During a scheduled security audit at Brightstone Legal, the SOC analyst identifies this issue: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. Which action BEST addresses the described security, identity, or compliance gap?

  1. Recognize that a system-assigned managed identity follows the lifecycle of its associated resource.
  2. Use a managed identity for the supported Azure workload and grant it the smallest appropriate role.
  3. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  4. Distinguish application registrations, service principals and human user objects for accurate lifecycle management.

Explanation

Correct Answer

A:

Recognize that a system-assigned managed identity follows the lifecycle of its associated resource. This directly addresses the observed weakness: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. For Brightstone Legal and its matter files and sensitive case records, a meaningful acceptance check would be: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

Incorrect Answers

B:

Use a managed identity for the supported Azure workload and grant it the smallest appropriate role. This addresses a different security or governance gap: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. For Brightstone Legal and its matter files and sensitive case records, the issue is instead: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. This alternative alone would not demonstrate the needed result: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

C:

Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources. This addresses a different security or governance gap: A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource. For Brightstone Legal and its matter files and sensitive case records, the issue is instead: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. This alternative alone would not demonstrate the needed result: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

D:

Distinguish application registrations, service principals and human user objects for accurate lifecycle management. This addresses a different security or governance gap: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. For Brightstone Legal and its matter files and sensitive case records, the issue is instead: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. This alternative alone would not demonstrate the needed result: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

Question 190

During a scheduled security audit at Brightstone Legal, the SOC analyst identifies this issue: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. The function obtains a token without a committed secret and an unauthorized resource operation fails.
  2. An identity inventory lists application service principals separately from workforce user accounts and group memberships.
  3. A replacement compute resource uses the same authorized identity without creating a new embedded credential.
  4. After resource deletion the old identity can no longer be used and its former permissions are reviewed.

Explanation

Correct Answer

D:

After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is the relevant proof because it tests whether the selected corrective action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource) addressed the initiating problem (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) in Brightstone Legal's matter files and sensitive case records environment, not merely whether a task was marked complete.

Incorrect Answers

A:

The function obtains a token without a committed secret and an unauthorized resource operation fails. This is useful evidence for a different situation (A scheduled Azure function stores a long-lived client secret in source code to access another Azure service) and action (Use a managed identity for the supported Azure workload and grant it the smallest appropriate role). For the reported issue at Brightstone Legal, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

B:

An identity inventory lists application service principals separately from workforce user accounts and group memberships. This is useful evidence for a different situation (An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory) and action (Distinguish application registrations, service principals and human user objects for accurate lifecycle management). For the reported issue at Brightstone Legal, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.

C:

A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is useful evidence for a different situation (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) and action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources). For the reported issue at Brightstone Legal, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.