You have an Azure subscription that contains the resources shown in the following table.
You plan to use an Azure key vault to provide a secret to appl.
What should you create for app1 to access the key vault, and from which key vault can the secret be used? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Exhibit

Exhibit
Reveal Solution
Discussion
Correct Answer:

Explanation:
CORRECTED ANSWER: Create a: Managed identity. Use the secret from: Vault1, Vault2, or Vault3 (any of the three key vaults, since RBAC-based Key Vault access via a managed identity has no region or resource- group affinity requirement).
Detailed Explanation
The Azure-recommended, credential-less way for app1 (a Container App) to retrieve a secret is to enable a managed identity and grant it an appropriate Key Vault access role (e.g., Key Vault Secrets User) via Azure RBAC or an access policy - avoiding stored credentials entirely; a service principal would require managing a client secret/certificate, a private endpoint secures network access to a vault but isn ' t itself an identity for app1, and a user account is not applicable to an application workload. Azure Key Vault RBAC role assignments and REST/API access work over HTTPS regardless of the caller ' s region or resource group, so app1 ' s managed identity can be granted access to Vault1, Vault2, or Vault3 equally - none of the vaults ' differing resource groups (RG1 vs RG2) or regions (East US vs West US) restrict this cross-boundary RBAC access, so all three vaults are usable, not only Vault1.
Official Reference
Access Azure Key Vault from Azure Container Apps using a managed identity - https://learn.microsoft.com
/en-us/azure/container-apps/managed-identity