Microsoft SC-900 Dumps
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?
Explanation
Correct Answer
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
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.
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.
“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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
“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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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
- Microsoft SC-900 Practice Test 17 - 10 Questions (Last Reviewed 04-Nov-2026)
- Microsoft SC-900 Practice Test 18 - 10 Questions (Last Reviewed 03-Nov-2026)
- Microsoft SC-900 Practice Test 19 - 10 Questions (Last Reviewed 02-Nov-2026)
- Microsoft SC-900 Practice Test 20 - 10 Questions (Last Reviewed 01-Nov-2026)
- Microsoft SC-900 Practice Test 21 - 10 Questions (Last Reviewed 31-Oct-2026)