Question

Difficulty: HardCreate and Configure Azure Functions

You are designing a serverless background processing solution using Azure Functions V4. The function app must process large video files uploaded to Azure Blob Storage, where the processing of a single video file can take up to 2525 minutes to complete. The function app must also securely access an Azure SQL Database instance hosted within an Azure Virtual Network without exposing the database to the public internet. You need to select the hosting plan and configuration that satisfies these requirements. Which of the following configurations should you select?

  1. A
    A Consumption plan with regional virtual network integration, and the host.json functionTimeout property set to 00:30:00.
  2. An Elastic Premium plan with regional virtual network integration, and the host.json functionTimeout property set to 00:30:00.Answer
  3. C
    A Dedicated (App Service) plan with Always On disabled, regional virtual network integration, and the host.json functionTimeout property set to 00:45:00.
  4. D
    An Elastic Premium plan with an inbound Private Endpoint, and the host.json functionTimeout property set to 00:10:00.

Answer

An Elastic Premium plan with regional virtual network integration, and the host.json functionTimeout property set to 00:30:00.
The configuration specifying an Elastic Premium plan with regional virtual network integration and a 3030-minute functionTimeout is correct because the Elastic Premium plan supports regional virtual network integration for outbound connectivity to resources within a virtual network. Additionally, the Premium plan allows for execution timeouts beyond 1010 minutes (up to unbounded, with 3030 minutes as the default), which easily accommodates the 2525-minute requirement.

Step-by-Step Solution

1
Analyze execution duration requirements.
The requirement states that execution can take up to 2525 minutes. The Consumption plan has a maximum execution limit of 1010 minutes. Therefore, the Consumption plan is ruled out, and either an Elastic Premium or Dedicated (App Service) plan must be used.
Choosing a hosting plan that supports execution durations longer than 1010 minutes is necessary to prevent function executions from timing out.
2
Analyze networking requirements.
The function app needs outbound connectivity to access an Azure SQL Database within a virtual network. Regional virtual network integration is required for outbound connectivity.
Regional virtual network integration enables the function app to route outbound traffic into the virtual network, while Private Endpoints only control inbound access.
3
Evaluate hosting plan configurations and host.json timeout settings.
An Elastic Premium plan with regional virtual network integration supports both requirements. The default timeout on the Premium plan is 3030 minutes, which can be configured explicitly in host.json using the functionTimeout property (e.g., '00:30:00'). Dedicated plans require Always On to be enabled for background triggers to work properly.
Verifying the correct property and values in host.json ensures the function app scales and executes within the limits of the chosen plan.

Key Concept

Azure Functions hosting plans support different execution limits and networking features. The Elastic Premium plan is required for serverless scaling when regional virtual network integration or executions longer than 1010 minutes are needed.
Estimated Time:2m 0s
Rate this question