Practice Exams:

Microsoft SC-900 Dumps

EXAM: Microsoft Security, Compliance, and Identity Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

SC-900 Premium Bundle


  • Premium File 259 Questions & Answers
  • Training Course 147 Lectures
  • Study Guide 413 Pages

Microsoft SC-900 Practice Test 19

Question 180

For this case—A managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity.—which implementation and acceptance check are correctly paired?

  1. Action: Classify identities by the actor performing work and apply supported human, service or agent access controls instead of assuming all principals are employee user accounts. Validation: Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.
  2. Action: Use Microsoft Entra ID as the tenant's cloud directory for registered users, groups, applications and sign-in policy without assuming it is a physical domain controller. Validation: List synthetic tenant users, registered applications and sign-in events, then verify a separate legacy AD DS Group Policy test remains outside Entra-only functions.
  3. Action: Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. Validation: Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
  4. Action: Enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. Validation: From a test workload obtain an Entra token and access its permitted Key Vault secret, then delete the resource in a lab and inspect identity lifecycle.

Explanation

Correct Answer

D:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. Enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. Validation: From a test workload obtain an Entra token and access its permitted Key Vault secret, then delete the resource in a lab and inspect identity lifecycle. The action and test belong together because a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Incorrect Answers

A:

That action-and-evidence pair concerns “distinguish workforce workload and agent identities at a conceptual level”, not this decision. The appropriate action is to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. To confirm, from a test workload obtain an Entra token and access its permitted Key Vault secret, then delete the resource in a lab and inspect identity lifecycle.

B:

The proposed pair focuses on “identify a Microsoft entra tenant as cloud identity directory” instead. The appropriate action is to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. To confirm, from a test workload obtain an Entra token and access its permitted Key Vault secret, then delete the resource in a lab and inspect identity lifecycle.

C:

“synchronize hybrid identities with explicit scope and health checks” evaluates a different intervention. The appropriate action is to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. To confirm, from a test workload obtain an Entra token and access its permitted Key Vault secret, then delete the resource in a lab and inspect identity lifecycle.

Question 181

Two Azure automation workers need the same narrowly scoped storage access while one worker may be rebuilt during routine maintenance. Which implementation or design choice most directly mitigates the stated issue?

  1. Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required.
  2. Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health.
  3. Use Microsoft Entra ID as the tenant's cloud directory for registered users, groups, applications and sign-in policy without assuming it is a physical domain controller.
  4. Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.

Explanation

Correct Answer

A:

Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources. To verify, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

Incorrect Answers

B:

“synchronize hybrid identities with explicit scope and health checks” is related to another task, not the failure shown here. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

C:

This alternative focuses on “identify a Microsoft entra tenant as cloud identity directory” instead of the required outcome. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

D:

That choice concerns “distinguish cloud-only and hybrid identity sign-in choices”, not the immediate requirement. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Question 182

Two Azure automation workers need the same narrowly scoped storage access while one worker may be rebuilt during routine maintenance. Which technical explanation most directly supports the right approach?

  1. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.
  2. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.
  3. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.
  4. A Microsoft Entra tenant defines a cloud identity boundary and issues access tokens for supported applications, unlike a classic on-prem AD DS domain controller.

Explanation

Correct Answer

B:

A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources. This supports the decision to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required.

Incorrect Answers

A:

The principle behind “use an app registration and service principal for application access” is not the one being tested. Here, a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

C:

“use system-assigned managed identities for a single Azure resource” explains a different mechanism. Here, a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

D:

That statement concerns “identify a Microsoft entra tenant as cloud identity directory” rather than the cause in this case. Here, a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Question 183

For this situation—Two Azure automation workers need the same narrowly scoped storage access while one worker may be rebuilt during routine maintenance.—which check provides the strongest verification?

  1. Perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.
  2. Run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.
  3. Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.
  4. List synthetic tenant users, registered applications and sign-in events, then verify a separate legacy AD DS Group Policy test remains outside Entra-only functions.

Explanation

Correct Answer

C:

Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself. It is the relevant test because a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Incorrect Answers

A:

“distinguish cloud-only and hybrid identity sign-in choices” would verify a different part of the system. To check this result, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

B:

That test concerns “prefer workload identity federation over stored CI secrets”, not the requested outcome. To check this result, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

D:

This evidence addresses “identify a Microsoft entra tenant as cloud identity directory” instead of confirming the repair. To check this result, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

Question 184

Two Azure automation workers need the same narrowly scoped storage access while one worker may be rebuilt during routine maintenance. If the team does the following—"Assume a system-assigned identity can be freely moved unchanged between unrelated services after its original Azure resource is destroyed."—what could go wrong?

  1. Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.
  2. A migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.
  3. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.
  4. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.

Explanation

Correct Answer

D:

Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood. The shortcut is unsafe because a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Incorrect Answers

A:

That consequence concerns “Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run…”, which is a different failure. Here, workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.

B:

“A migration may break old device policies or application authentication because the architecture confused a cloud…” does not describe the result of this shortcut. Here, workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.

C:

The alternative risk relates to “Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were…”, not the stated mistake. Here, workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.

Question 185

Two Azure automation workers need the same narrowly scoped storage access while one worker may be rebuilt during routine maintenance. Which action and validation evidence belong together?

  1. Action: Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. Validation: Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.
  2. Action: Use Microsoft Entra ID as the tenant's cloud directory for registered users, groups, applications and sign-in policy without assuming it is a physical domain controller. Validation: List synthetic tenant users, registered applications and sign-in events, then verify a separate legacy AD DS Group Policy test remains outside Entra-only functions.
  3. Action: Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. Validation: Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
  4. Action: Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. Validation: Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Explanation

Correct Answer

A:

Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. Validation: Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself. The action and test belong together because a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Incorrect Answers

B:

“identify a Microsoft entra tenant as cloud identity directory” evaluates a different intervention. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

C:

The linked action and check for “synchronize hybrid identities with explicit scope and health checks” would not resolve this case. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

D:

That action-and-evidence pair concerns “use an app registration and service principal for application access”, not this decision. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

Question 186

An SC-900 learner considers: A developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. What is the most appropriate next decision?

  1. Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token.
  2. Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required.
  3. Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.
  4. Use Microsoft Entra ID as the tenant's cloud directory for registered users, groups, applications and sign-in policy without assuming it is a physical domain controller.

Explanation

Correct Answer

B:

The situation is that a developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources. To verify, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

Incorrect Answers

A:

“prefer workload identity federation over stored CI secrets” is related to another task, not the failure shown here. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

C:

The situation is that a developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. That choice concerns “distinguish cloud-only and hybrid identity sign-in choices”, not the immediate requirement. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

D:

The proposed action addresses “identify a Microsoft entra tenant as cloud identity directory” rather than the problem described. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Question 187

A developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. Why does the recommended approach address this particular concern?

  1. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.
  2. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  3. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.
  4. A Microsoft Entra tenant defines a cloud identity boundary and issues access tokens for supported applications, unlike a classic on-prem AD DS domain controller.

Explanation

Correct Answer

C:

The situation is that a developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources. This supports the decision to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required.

Incorrect Answers

A:

“prefer workload identity federation over stored CI secrets” describes another technical distinction. Here, a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

B:

“distinguish cloud-only and hybrid identity sign-in choices” explains a different mechanism. Here, a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

D:

The principle behind “identify a Microsoft entra tenant as cloud identity directory” is not the one being tested. Here, a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Question 188

A developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. Which evidence best validates the proposed outcome?

  1. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  2. List synthetic tenant users, registered applications and sign-in events, then verify a separate legacy AD DS Group Policy test remains outside Entra-only functions.
  3. From a test workload obtain an Entra token and access its permitted Key Vault secret, then delete the resource in a lab and inspect identity lifecycle.
  4. Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

Explanation

Correct Answer

D:

The situation is that a developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself. It is the relevant test because a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Incorrect Answers

A:

That test concerns “separate member and guest identities in collaboration”, not the requested outcome. To check this result, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

B:

The proposed check is relevant to “identify a Microsoft entra tenant as cloud identity directory”, but not sufficient here. To check this result, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

C:

This evidence addresses “use system-assigned managed identities for a single Azure resource” instead of confirming the repair. To check this result, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

Question 189

Consider this situation: A developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. A team member suggests: "Assume a system-assigned identity can be freely moved unchanged between unrelated services after its original Azure resource is destroyed." What is the main risk?

  1. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.
  2. Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.
  3. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.
  4. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

Explanation

Correct Answer

A:

The situation is that a developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood. The shortcut is unsafe because a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Incorrect Answers

B:

The alternative risk relates to “Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a…”, not the stated mistake. Here, workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.

C:

“The app can inherit excessive tenant powers and may stop when the human password or MFA…” can arise elsewhere, but it is not the most direct risk here. Here, workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.

D:

That consequence concerns “Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were…”, which is a different failure. Here, workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.

Question 190

A security and compliance reviewer considers: A developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. Which response and evidence should be linked?

  1. Action: Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. Validation: Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.
  2. Action: Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. Validation: Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.
  3. Action: Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. Validation: Run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.
  4. Action: Classify identities by the actor performing work and apply supported human, service or agent access controls instead of assuming all principals are employee user accounts. Validation: Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

Explanation

Correct Answer

B:

The situation is that a developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. Validation: Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself. The action and test belong together because a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Incorrect Answers

A:

“use an app registration and service principal for application access” evaluates a different intervention. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

C:

That action-and-evidence pair concerns “prefer workload identity federation over stored CI secrets”, not this decision. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

D:

The proposed pair focuses on “distinguish workforce workload and agent identities at a conceptual level” instead. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

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