Bitzu

AZ-305 ยท Compute solution design

Azure Functions hosting plans

Azure Functions hosting plans (Flex Consumption, Consumption, Premium, Dedicated), cold start and VNet support, Durable Functions for orchestrations.

Key points

  • Flex Consumption: recommended serverless; Linux, pay per execution, VNet, always-ready; timeout 30 min default, no max.
  • Consumption (legacy): no VNet; timeout 5 min default, 10 max; Linux retires 30 September 2028.
  • Premium (EP): always-ready, at least one instance billed, VNet.
  • Dedicated: App Service plan, needs Always On for long runs.
  • HTTP triggers: respond within 230 seconds; longer: Durable Functions (fan-out/fan-in).

Source: https://learn.microsoft.com/en-us/azure/azure-functions/functions-scale

Practice questions

Single choice

What is the maximum function execution timeout on the legacy Consumption plan?

  1. 5 minutes
  2. 10 minutes
  3. 30 minutes
  4. 60 minutes
Show answer

Answer: B. 10 minutes

The Consumption plan defaults to 5 minutes and allows at most 10 minutes. Flex Consumption, Premium and Dedicated default to 30 minutes and have no enforced maximum.

Select all that apply

Which Azure Functions hosting plans support outbound virtual network integration?

  1. Flex Consumption plan
  2. Premium plan
  3. Consumption plan (legacy)
  4. Dedicated (App Service) plan
  5. Only plans running in an App Service Environment
Show answer

Answer: A. Flex Consumption plan, B. Premium plan, D. Dedicated (App Service) plan

Flex Consumption, Premium and Dedicated (App Service plan or ASE) all support VNet integration. The legacy Consumption plan does not, and you do not need an App Service Environment just to get VNet access.

True or false

Because the Premium plan has no maximum execution timeout, an HTTP-triggered function on it can keep a client request open for 30 minutes before responding.

Show answer

Answer: False

False. Whatever the function timeout, an HTTP-triggered function has at most 230 seconds to respond, because of the Azure Load Balancer idle timeout. For longer work, use the Durable Functions async HTTP pattern or queue the work and respond immediately.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More AZ-305 topics in this module