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 20

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.

Question 191

The identity operations team at Lakeview Insurance supports broker collaboration and claim applications. An assessment finds: 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. Distinguish application registrations, service principals and human user objects for accurate lifecycle management.
  2. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  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 Lakeview Insurance and its broker collaboration and claim applications, 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:

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 Lakeview Insurance and its broker collaboration and claim applications, 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:

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 Lakeview Insurance and its broker collaboration and claim applications, 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 Lakeview Insurance and its broker collaboration and claim applications, 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 192

The identity operations team at Lakeview Insurance supports broker collaboration and claim applications. An assessment finds: 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. A replacement compute resource uses the same authorized identity without creating a new embedded credential.
  2. An identity inventory lists application service principals separately from workforce user accounts and group memberships.
  3. After resource deletion the old identity can no longer be used and its former permissions are reviewed.
  4. The function obtains a token without a committed secret and an unauthorized resource operation fails.

Explanation

Correct Answer

C:

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 Lakeview Insurance's broker collaboration and claim applications environment, not merely whether a task was marked complete.

Incorrect Answers

A:

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 Lakeview Insurance, 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 Lakeview Insurance, 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 Lakeview Insurance, 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 193

The identity operations team at Seabright Municipal Works supports public-sector records and operations. An assessment finds: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. 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 user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  3. Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets.
  4. Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow.

Explanation

Correct Answer

C:

Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets. This directly addresses the observed weakness: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. For Seabright Municipal Works and its public-sector records and operations, a meaningful acceptance check would be: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Seabright Municipal Works and its public-sector records and operations, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Seabright Municipal Works and its public-sector records and operations, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

D:

Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow. This addresses a different security or governance gap: A partner consultant needs temporary collaboration in Microsoft 365 but is provisioned as an ordinary permanent internal employee. For Seabright Municipal Works and its public-sector records and operations, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

Question 194

The identity operations team at Seabright Municipal Works supports public-sector records and operations. An assessment finds: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.
  2. The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity.
  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

A:

The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange. This is the relevant proof because it tests whether the selected corrective action (Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets) addressed the initiating problem (A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job) in Seabright Municipal Works's public-sector records and operations environment, not merely whether a task was marked complete.

Incorrect Answers

B:

The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity. This is useful evidence for a different situation (A partner consultant needs temporary collaboration in Microsoft 365 but is provisioned as an ordinary permanent internal employee) and action (Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow). For the reported issue at Seabright Municipal Works, it does not establish the required outcome: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Seabright Municipal Works, it does not establish the required outcome: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Seabright Municipal Works, it does not establish the required outcome: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

Question 195

At Oceanview Payments, a migration readiness assessment uncovers the following situation affecting regulated card workflows and employee access: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. 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. Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets.
  3. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  4. Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow.

Explanation

Correct Answer

B:

Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets. This directly addresses the observed weakness: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. For Oceanview Payments and its regulated card workflows and employee access, a meaningful acceptance check would be: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

D:

Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow. This addresses a different security or governance gap: A partner consultant needs temporary collaboration in Microsoft 365 but is provisioned as an ordinary permanent internal employee. For Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

Question 196

At Oceanview Payments, a migration readiness assessment uncovers the following situation affecting regulated card workflows and employee access: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. 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 trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.
  3. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.
  4. The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity.

Explanation

Correct Answer

B:

The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange. This is the relevant proof because it tests whether the selected corrective action (Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets) addressed the initiating problem (A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job) in Oceanview Payments's regulated card workflows and employee access environment, not merely whether a task was marked complete.

Incorrect Answers

A:

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 trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Oceanview Payments, it does not establish the required outcome: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

D:

The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity. This is useful evidence for a different situation (A partner consultant needs temporary collaboration in Microsoft 365 but is provisioned as an ordinary permanent internal employee) and action (Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow). For the reported issue at Oceanview Payments, it does not establish the required outcome: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

Question 197

During a regulatory evidence review at Orion Network Services, the tenant administration team identifies this issue: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. 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. Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow.
  3. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  4. Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets.

Explanation

Correct Answer

D:

Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets. This directly addresses the observed weakness: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. For Orion Network Services and its subscriber applications and remote operations, a meaningful acceptance check would be: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Orion Network Services and its subscriber applications and remote operations, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

B:

Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow. This addresses a different security or governance gap: A partner consultant needs temporary collaboration in Microsoft 365 but is provisioned as an ordinary permanent internal employee. For Orion Network Services and its subscriber applications and remote operations, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Orion Network Services and its subscriber applications and remote operations, the issue is instead: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. This alternative alone would not demonstrate the needed result: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

Question 198

During a regulatory evidence review at Orion Network Services, the tenant administration team identifies this issue: A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked.
  2. The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.
  3. The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity.
  4. A replacement compute resource uses the same authorized identity without creating a new embedded credential.

Explanation

Correct Answer

B:

The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange. This is the relevant proof because it tests whether the selected corrective action (Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets) addressed the initiating problem (A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job) in Orion Network Services's subscriber applications and remote operations environment, not merely whether a task was marked complete.

Incorrect Answers

A:

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 trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

C:

The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity. This is useful evidence for a different situation (A partner consultant needs temporary collaboration in Microsoft 365 but is provisioned as an ordinary permanent internal employee) and action (Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow). For the reported issue at Orion Network Services, it does not establish the required outcome: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

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 Orion Network Services, it does not establish the required outcome: The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange.

Question 199

During a scheduled security audit at Linden Manufacturing, the tenant administration team identifies this issue: A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule. Which action BEST addresses the described security, identity, or compliance gap?

  1. Apply appropriate group-based licensing and monitor allocation failures where supported.
  2. Recognize that a system-assigned managed identity follows the lifecycle of its associated resource.
  3. Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources.
  4. Consider dynamic group membership with properly defined identity attributes where the feature is available.

Explanation

Correct Answer

D:

Consider dynamic group membership with properly defined identity attributes where the feature is available. This directly addresses the observed weakness: A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule. For Linden Manufacturing and its plant operations and product design information, a meaningful acceptance check would be: Membership changes when a sample user department attribute changes without manual edits to every application assignment.

Incorrect Answers

A:

Apply appropriate group-based licensing and monitor allocation failures where supported. This addresses a different security or governance gap: A training application is assigned individual user licenses one account at a time and new starters routinely miss access. For Linden Manufacturing and its plant operations and product design information, the issue is instead: A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule. This alternative alone would not demonstrate the needed result: Membership changes when a sample user department attribute changes without manual edits to every application assignment.

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 Linden Manufacturing and its plant operations and product design information, the issue is instead: A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule. This alternative alone would not demonstrate the needed result: Membership changes when a sample user department attribute changes without manual edits to every application assignment.

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 Linden Manufacturing and its plant operations and product design information, the issue is instead: A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule. This alternative alone would not demonstrate the needed result: Membership changes when a sample user department attribute changes without manual edits to every application assignment.

Question 200

During a scheduled security audit at Linden Manufacturing, the tenant administration team identifies this issue: A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule. 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 new eligible group member receives the assigned entitlement and the license assignment report shows no unresolved errors.
  3. A replacement compute resource uses the same authorized identity without creating a new embedded credential.
  4. Membership changes when a sample user department attribute changes without manual edits to every application assignment.

Explanation

Correct Answer

D:

Membership changes when a sample user department attribute changes without manual edits to every application assignment. This is the relevant proof because it tests whether the selected corrective action (Consider dynamic group membership with properly defined identity attributes where the feature is available) addressed the initiating problem (A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule) in Linden Manufacturing's plant operations and product design information 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 Linden Manufacturing, it does not establish the required outcome: Membership changes when a sample user department attribute changes without manual edits to every application assignment.

B:

A new eligible group member receives the assigned entitlement and the license assignment report shows no unresolved errors. This is useful evidence for a different situation (A training application is assigned individual user licenses one account at a time and new starters routinely miss access) and action (Apply appropriate group-based licensing and monitor allocation failures where supported). For the reported issue at Linden Manufacturing, it does not establish the required outcome: Membership changes when a sample user department attribute changes without manual edits to every application assignment.

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 Linden Manufacturing, it does not establish the required outcome: Membership changes when a sample user department attribute changes without manual edits to every application assignment.