Contoso deploys 40 virtual machines in a short time by using a single template. All virtual machines need the same permissions on the same storage account, and the deployment engineer doesn't have permission to create role assignments. To avoid managing credentials and minimize the number of role assignments, what should you use?
Show answer and explanation
Answer: A
Explanation
A user-assigned managed identity and its role assignments can be configured in advance of the resources that require them, so users who create the resources only need access to assign the identity, without creating new identities or role assignments.[2] When multiple resources need access to the same resources, they can share a single user-assigned identity, which means fewer identities and role assignments, and only one service principal is created, which avoids the Microsoft Entra object creation rate limit.[2]
B is wrong because system-assigned identities are created along with the resource, so role assignments can’t be created in advance and the deployment can fail when the engineer can’t create role assignments. Creating many identities in a short time can also fail with an HTTP 429 error.[2] C is impossible because a system-assigned identity can only be associated with a single Azure resource and can’t be shared.[1] D is wrong because it brings back the credential management that managed identities eliminate.[1]