QuestionQ63

VerifiedSecure, monitor, troubleshoot Azure solutions

You are developing a serverless Java application on Azure and create a new Azure Key Vault to use secrets from a new Azure Functions application.

The application must meet these requirements:

  • Reference Azure Key Vault without requiring changes to the Java code.
  • Dynamically add and remove Azure Functions host instances according to the number of incoming application events.
  • Keep instances perpetually warm to prevent cold starts.
  • Connect to a VNet.
  • Remove authentication to the Azure Key Vault instance if the Azure Functions application is deleted.

You need to grant the Azure Functions application access to the Azure Key Vault.

Which three actions should you take, in sequence?

Drag & Drop
Explanation

Azure Functions Premium supports event-driven scaling, VNet integration, and pre-warmed instances that avoid cold starts. A system-assigned managed identity is created for and lifecycle-bound to the Function App, so deleting the app removes that identity. Granting the identity access through a Key Vault access policy lets the application authenticate to Key Vault without embedding credentials or changing the Java code.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!