Home / SC-300 / Objective 3.1

Domain 3: Plan and implement workload identities · 24% of the exam · Full exam outline

3.1 Plan and implement identities for applications and Azure workloads

What this objective covers · 4% of the exam

Select appropriate identities for applications and Azure workloads, including managed identities, service principals, user accounts, and managed service accounts; Create managed identities; Assign a managed identity to an Azure resource; Use a managed identity assigned to an Azure resource to access other Azure resources

Practice questions

Question 1easy

An admin deleted a virtual machine whose system-assigned managed identity held a role on a storage account, then created a new VM with the same name and enabled a system-assigned identity again. The app on the new VM is now denied access to storage. What is the cause?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Deleting the VM deleted its identity. Enabling the identity again creates a new service principal, which has never been authorized on the storage account, even though it carries the same name.

Managed identities can authenticate to any resource that supports Microsoft Entra authentication; access keys aren't required.

It is true that only the owning resource can use a system-assigned identity, but code running on that VM is exactly how the identity is used; this doesn't explain the denial.

Key Vault access policies govern key vault objects, not storage accounts; the missing piece is a role assignment for the new identity.

Question 2easy

A developer wants an app hosted in Azure App Service to use a user-assigned managed identity that the platform team already created. Where is the identity attached to the app?

Included in Master: master every domain.See plans