Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft Certified: Azure Solutions Architect Expert · Microsoft
Interactive Drag & Drop Matching
Drag each configuration to its target, or tap an option then tap a target slot.
Hotspot Solution:
Answer 1: System-assigned MI 2: Access Policy Why not the other? User-assigned managed identity: While user-assigned identities can be used across multiple resources, this option is not selected as it would contradict the requirement that credentials should not be shared between services. Role assignment: While this is used for access control in Azure resources, role-based access control (RBAC) in Key Vault is more commonly used for higher-level management tasks, whereas access policies are typically used to control access to secrets.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Drop Down 1: System assigned - "The credentials must NOT be shared between services" Drop Down 2 Either Access policies or role assignments can work. Assuming MS wants not legacy model, the role assignments win.
Drop Down 1: A system-assigned managed identity Drop Down 2: Role Assigment Reference for Drop Down 2: https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-access-policy?utm_source=chatgpt.com
Access policy is currently marked as legacy: https://learn.microsoft.com/en-us/azure/key-vault/general/assign-access-policy?tabs=azure-portal New method is RBAC(Role based access control), which means you need to do Role assignment to get proper reference to a secret in KV.