AZ-500 · Question #546
Case Study 4 - Fabrikam, Inc Overview Fabrikam, Inc. is a consulting company. The company has a main office in New York City and branch offices in Amsterdam and Singapore. Existing Environment…
The correct answer is C. Configure a system-assigned managed identity on VM1. When a virtual machine with a system-assigned managed identity is deleted, the managed identity is also automatically deleted. This is because system-assigned managed identities are directly tied to the lifecycle of the Azure resource they are associated with, meaning they…
Question
Options
- AAdd a role assignment condition to storage1.
- BConfigure federated identity credentials for ID1.
- CConfigure a system-assigned managed identity on VM1.
- DAssign the Storage Blob Data Reader role to storage1.
- EAssign ID1 to VM1.
How the community answered
(32 responses)- A13% (4)
- B6% (2)
- C75% (24)
- D3% (1)
- E3% (1)
Explanation
When a virtual machine with a system-assigned managed identity is deleted, the managed identity is also automatically deleted. This is because system-assigned managed identities are directly tied to the lifecycle of the Azure resource they are associated with, meaning they share the same existence. Note: A managed identity is an identity that can be assigned to an Azure compute resource (Virtual Machine (VM), Virtual Machine Scale Set (VMSS), Service Fabric Cluster, Azure Kubernetes cluster) or any App hosting platform supported by Azure. Once a managed identity is assigned on the compute resource, it can be authorized, directly or indirectly, to access downstream dependency resources, such as a storage account, SQL database, CosmosDB, and https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview
Topics
Community Discussion
No community discussion yet for this question.