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 18

Question 170

At Brightstone Legal, a regulatory evidence review uncovers the following situation affecting matter files and sensitive case records: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. An identity inventory lists application service principals separately from workforce user accounts and group memberships.
  2. A new assignment appears only in the intended tenant and the unrelated tenant's access report is unchanged.
  3. A test user exists in the correct Entra tenant and receives only explicitly assigned access to a subscription resource.
  4. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.

Explanation

Correct Answer

A:

An identity inventory lists application service principals separately from workforce user accounts and group memberships. This is the relevant proof because it tests whether the selected corrective action (Distinguish application registrations, service principals and human user objects for accurate lifecycle management) addressed the initiating problem (An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory) in Brightstone Legal's matter files and sensitive case records environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A new assignment appears only in the intended tenant and the unrelated tenant's access report is unchanged. This is useful evidence for a different situation (Two enterprise tenants share a name and admins assign privileges in the wrong one because they ignore tenant context) and action (Verify tenant identity and administrator directory context before changing Entra objects or enterprise applications). For the reported issue at Brightstone Legal, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

C:

A test user exists in the correct Entra tenant and receives only explicitly assigned access to a subscription resource. This is useful evidence for a different situation (An organization plans to deploy an identity directory in Azure but mistakenly assumes an Azure subscription itself replaces a tenant's identity directory) and action (Use Microsoft Entra ID as the cloud identity directory and distinguish tenant identity administration from Azure subscription resource management). For the reported issue at Brightstone Legal, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

D:

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 Brightstone Legal, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

Question 171

During an incident follow-up at Lakeview Insurance, the compliance analyst identifies this issue: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. Which action BEST addresses the described security, identity, or compliance gap?

  1. Distinguish application registrations, service principals and human user objects for accurate lifecycle management.
  2. Use Microsoft Entra ID as the cloud identity directory and distinguish tenant identity administration from Azure subscription resource management.
  3. Give the application an app registration and workload identity with the required API permissions.
  4. Verify tenant identity and administrator directory context before changing Entra objects or enterprise applications.

Explanation

Correct Answer

A:

Distinguish application registrations, service principals and human user objects for accurate lifecycle management. This directly addresses the observed weakness: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. For Lakeview Insurance and its broker collaboration and claim applications, a meaningful acceptance check would be: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

Incorrect Answers

B:

Use Microsoft Entra ID as the cloud identity directory and distinguish tenant identity administration from Azure subscription resource management. This addresses a different security or governance gap: An organization plans to deploy an identity directory in Azure but mistakenly assumes an Azure subscription itself replaces a tenant's identity directory. For Lakeview Insurance and its broker collaboration and claim applications, the issue is instead: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. This alternative alone would not demonstrate the needed result: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

C:

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 Lakeview Insurance and its broker collaboration and claim applications, the issue is instead: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. This alternative alone would not demonstrate the needed result: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

D:

Verify tenant identity and administrator directory context before changing Entra objects or enterprise applications. This addresses a different security or governance gap: Two enterprise tenants share a name and admins assign privileges in the wrong one because they ignore tenant context. For Lakeview Insurance and its broker collaboration and claim applications, the issue is instead: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. This alternative alone would not demonstrate the needed result: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

Question 172

During an incident follow-up at Lakeview Insurance, the compliance analyst identifies this issue: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. An identity inventory lists application service principals separately from workforce user accounts and group memberships.
  2. A test user exists in the correct Entra tenant and receives only explicitly assigned access to a subscription resource.
  3. A new assignment appears only in the intended tenant and the unrelated tenant's access report is unchanged.
  4. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.

Explanation

Correct Answer

A:

An identity inventory lists application service principals separately from workforce user accounts and group memberships. This is the relevant proof because it tests whether the selected corrective action (Distinguish application registrations, service principals and human user objects for accurate lifecycle management) addressed the initiating problem (An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory) in Lakeview Insurance's broker collaboration and claim applications environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A test user exists in the correct Entra tenant and receives only explicitly assigned access to a subscription resource. This is useful evidence for a different situation (An organization plans to deploy an identity directory in Azure but mistakenly assumes an Azure subscription itself replaces a tenant's identity directory) and action (Use Microsoft Entra ID as the cloud identity directory and distinguish tenant identity administration from Azure subscription resource management). For the reported issue at Lakeview Insurance, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

C:

A new assignment appears only in the intended tenant and the unrelated tenant's access report is unchanged. This is useful evidence for a different situation (Two enterprise tenants share a name and admins assign privileges in the wrong one because they ignore tenant context) and action (Verify tenant identity and administrator directory context before changing Entra objects or enterprise applications). For the reported issue at Lakeview Insurance, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

D:

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 Lakeview Insurance, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

Question 173

The tenant administration team at Blue Haven Media supports creative files and production workspaces. An assessment finds: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. Which action BEST addresses the described security, identity, or compliance gap?

  1. Use Microsoft Entra ID as the cloud identity directory and distinguish tenant identity administration from Azure subscription resource management.
  2. Distinguish application registrations, service principals and human user objects for accurate lifecycle management.
  3. Give the application an app registration and workload identity with the required API permissions.
  4. Verify tenant identity and administrator directory context before changing Entra objects or enterprise applications.

Explanation

Correct Answer

B:

Distinguish application registrations, service principals and human user objects for accurate lifecycle management. This directly addresses the observed weakness: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. For Blue Haven Media and its creative files and production workspaces, a meaningful acceptance check would be: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

Incorrect Answers

A:

Use Microsoft Entra ID as the cloud identity directory and distinguish tenant identity administration from Azure subscription resource management. This addresses a different security or governance gap: An organization plans to deploy an identity directory in Azure but mistakenly assumes an Azure subscription itself replaces a tenant's identity directory. For Blue Haven Media and its creative files and production workspaces, the issue is instead: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. This alternative alone would not demonstrate the needed result: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

C:

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 Blue Haven Media and its creative files and production workspaces, the issue is instead: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. This alternative alone would not demonstrate the needed result: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

D:

Verify tenant identity and administrator directory context before changing Entra objects or enterprise applications. This addresses a different security or governance gap: Two enterprise tenants share a name and admins assign privileges in the wrong one because they ignore tenant context. For Blue Haven Media and its creative files and production workspaces, the issue is instead: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. This alternative alone would not demonstrate the needed result: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

Question 174

The tenant administration team at Blue Haven Media supports creative files and production workspaces. An assessment finds: An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A new assignment appears only in the intended tenant and the unrelated tenant's access report is unchanged.
  2. An identity inventory lists application service principals separately from workforce user accounts and group memberships.
  3. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.
  4. A test user exists in the correct Entra tenant and receives only explicitly assigned access to a subscription resource.

Explanation

Correct Answer

B:

An identity inventory lists application service principals separately from workforce user accounts and group memberships. This is the relevant proof because it tests whether the selected corrective action (Distinguish application registrations, service principals and human user objects for accurate lifecycle management) addressed the initiating problem (An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory) in Blue Haven Media's creative files and production workspaces environment, not merely whether a task was marked complete.

Incorrect Answers

A:

A new assignment appears only in the intended tenant and the unrelated tenant's access report is unchanged. This is useful evidence for a different situation (Two enterprise tenants share a name and admins assign privileges in the wrong one because they ignore tenant context) and action (Verify tenant identity and administrator directory context before changing Entra objects or enterprise applications). For the reported issue at Blue Haven Media, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

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 Blue Haven Media, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

D:

A test user exists in the correct Entra tenant and receives only explicitly assigned access to a subscription resource. This is useful evidence for a different situation (An organization plans to deploy an identity directory in Azure but mistakenly assumes an Azure subscription itself replaces a tenant's identity directory) and action (Use Microsoft Entra ID as the cloud identity directory and distinguish tenant identity administration from Azure subscription resource management). For the reported issue at Blue Haven Media, it does not establish the required outcome: An identity inventory lists application service principals separately from workforce user accounts and group memberships.

Question 175

The tenant administration team at Oceanview Payments supports regulated card workflows and employee access. An assessment finds: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. 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 user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  3. Use a managed identity for the supported Azure workload and grant it the smallest appropriate role.
  4. Give the application an app registration and workload identity with the required API permissions.

Explanation

Correct Answer

C:

Use a managed identity for the supported Azure workload and grant it the smallest appropriate role. This directly addresses the observed weakness: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. For Oceanview Payments and its regulated card workflows and employee access, a meaningful acceptance check would be: The function obtains a token without a committed secret and an unauthorized resource operation fails.

Incorrect Answers

A:

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 Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

B:

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 Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

D:

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 Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

Question 176

The tenant administration team at Oceanview Payments supports regulated card workflows and employee access. An assessment finds: 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. 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

C:

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 Oceanview Payments's regulated card workflows and employee access 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 Oceanview Payments, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

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 Oceanview Payments, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

D:

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 Oceanview Payments, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

Question 177

At Orion Network Services, a new-service rollout uncovers the following situation affecting subscriber applications and remote operations: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. 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. Use a managed identity for the supported Azure workload and grant it the smallest appropriate role.
  3. Recognize that a system-assigned managed identity follows the lifecycle of its associated resource.
  4. Give the application an app registration and workload identity with the required API permissions.

Explanation

Correct Answer

B:

Use a managed identity for the supported Azure workload and grant it the smallest appropriate role. This directly addresses the observed weakness: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. For Orion Network Services and its subscriber applications and remote operations, a meaningful acceptance check would be: The function obtains a token without a committed secret and an unauthorized resource operation fails.

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 Orion Network Services and its subscriber applications and remote operations, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

C:

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 Orion Network Services and its subscriber applications and remote operations, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

D:

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 Orion Network Services and its subscriber applications and remote operations, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

Question 178

At Orion Network Services, a new-service rollout uncovers the following situation affecting subscriber applications and remote operations: 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. 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. A replacement compute resource uses the same authorized identity without creating a new embedded credential.
  4. The function obtains a token without a committed secret and an unauthorized resource operation fails.

Explanation

Correct Answer

D:

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 Orion Network Services's subscriber applications and remote 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 Orion Network Services, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

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 Orion Network Services, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

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 Orion Network Services, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.

Question 179

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. 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. 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. Give the application an app registration and workload identity with the required API permissions.

Explanation

Correct Answer

C:

Use a managed identity for the supported Azure workload and grant it the smallest appropriate role. This directly addresses the observed weakness: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. For Aspen Digital and its client advisory systems and shared files, a meaningful acceptance check would be: The function obtains a token without a committed secret and an unauthorized resource operation fails.

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 Aspen Digital and its client advisory systems and shared files, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

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 Aspen Digital and its client advisory systems and shared files, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

D:

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 Aspen Digital and its client advisory systems and shared files, the issue is instead: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. This alternative alone would not demonstrate the needed result: The function obtains a token without a committed secret and an unauthorized resource operation fails.

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.