Question

Difficulty: HardCreate and Configure Azure Functions

You are designing a new Azure Function App (V4 runtime) to process messages from an Azure Service Bus queue. The function app must meet the following requirements:
- Connect to the queue using outbound virtual network integration.
- Support individual execution times that can last up to 25 minutes.
- Minimize cold starts by maintaining at least one pre-warmed instance at all times.
- Scale dynamically based on the queue length without manual scaling rule configuration.

Which hosting plan should you select for the Azure Function App?

  1. A
    Consumption plan
  2. Elastic Premium planAnswer
  3. C
    Dedicated (App Service) plan using the Basic (B1) tier
  4. D
    Dedicated (App Service) plan using the Standard (S1) tier with Always On enabled

Answer

Elastic Premium plan
The Elastic Premium plan is the correct choice because it natively supports virtual network integration, has a default execution timeout of 30 minutes (which can be configured to run indefinitely), provides pre-warmed instances to eliminate cold starts, and utilizes the Azure Functions scale controller to dynamically scale instances based on Service Bus queue length.

Step-by-Step Solution

1
Analyze virtual network requirements
Outbound VNet integration is required, which eliminates the Consumption plan.
The Consumption plan does not support outbound virtual network integration.
2
Analyze execution duration requirements
The function execution can last up to 25 minutes, which eliminates the Consumption plan (limit is 10 minutes) but is supported by Premium and Dedicated plans.
Premium and Dedicated plans support unbounded execution timeouts, whereas the Consumption plan enforces a hard limit of 10 minutes.
3
Analyze cold start and dynamic scaling requirements
Pre-warmed instances are required to minimize cold starts, and the app must scale dynamically based on event rate (queue length). This points to the Elastic Premium plan.
The Elastic Premium plan offers pre-warmed instances and dynamic serverless scaling, whereas Dedicated (App Service) plans scale based on metric-based autoscale rules rather than the Scale Controller monitoring the queue.

Key Concept

Azure Functions hosting plan comparison, including execution limits, networking features, and scaling behaviors.
Estimated Time:2m 0s
Rate this question