Question

Difficulty: MediumServerless and Web Application Hosting

An organization is designing a serverless backend solution to process data analysis batches. Each batch job takes up to 25 minutes to complete. The solution must auto-scale to meet demand, minimize cost when idle, and require minimal management overhead.

Which two Azure compute options should you recommend for hosting the batch jobs?

  1. Azure Functions on a Premium planAnswer
  2. Azure Container Apps jobsAnswer
  3. C
    Azure Functions on a Consumption plan
  4. D
    Azure Kubernetes Service (AKS)

Answer

Azure Functions on a Premium plan and Azure Container Apps jobs are the recommended choices.
The correct options are Azure Functions on a Premium plan and Azure Container Apps jobs. Azure Functions on a Premium plan allows execution times up to 30 minutes (and can be configured to be unbounded) and scales dynamically, avoiding the strict 10-minute timeout limit of the Consumption plan. Azure Container Apps jobs are built specifically for processing containerized, run-to-completion batch tasks without a strict 10-minute timeout constraint, scaling to zero when no jobs are running. Both options offer a serverless model that minimizes management overhead and cost when idle.

Step-by-Step Solution

1
Evaluate the execution timeout constraint
The execution takes 25 minutes, ruling out options with a 10-minute timeout limit.
Azure Functions on a Consumption plan has a hard 10-minute timeout limitation, making it unsuitable.
2
Evaluate operational overhead and scaling constraints
Identify compute platforms that scale to zero, minimize idle costs, and require minimal infrastructure management.
Azure Kubernetes Service (AKS) requires management of clusters and nodes, violating the minimal management requirement, whereas Azure Functions and Azure Container Apps jobs are serverless and managed.
3
Confirm compatible serverless hosting models
Azure Functions on a Premium plan and Azure Container Apps jobs satisfy both the 25-minute execution requirement and the serverless management and scaling constraints.
Both selected plans support long-running tasks and automatically scale down to zero when idle.

Key Concept

Selecting serverless hosting options based on execution duration limits, scaling behavior, and operational overhead.
Estimated Time:2m 0s
Rate this question