Question

Difficulty: Very hardServerless and Web Application Hosting

You are designing the serverless hosting infrastructure for an enterprise application that contains two distinct workloads:

* Workload 1: An HTTP-triggered API that processes incoming vendor requests. The API must access a backend database located in a secured Azure Virtual Network (VNet). The traffic is highly intermittent, with several hours of inactivity followed by unpredictable spikes. To minimize operating costs, the solution must scale to zero instances and incur no compute charges when idle.
* Workload 2: A queue-triggered background job that performs daily inventory synchronization. Each execution takes approximately 18 minutes to complete. The job must run on a serverless compute model that scales to zero when the queue is empty, and it must not experience timeout failures.

Which two hosting plans should you recommend to meet the requirements for both workloads? (Select two.)

  1. Azure Functions Flex Consumption plan for Workload 1Answer
  2. B
    Azure Functions Consumption plan for Workload 1
  3. C
    Azure Kubernetes Service (AKS) for Workload 1
  4. Azure Functions Flex Consumption plan for Workload 2Answer
  5. E
    Azure Functions Consumption plan for Workload 2
  6. F
    Azure App Service Dedicated plan (Premium v3 tier) for Workload 2

Answer

The correct hosting plans are the Azure Functions Flex Consumption plan for Workload 1 and the Azure Functions Flex Consumption plan for Workload 2.
The correct plans are the Azure Functions Flex Consumption plan for Workload 1 and the Azure Functions Flex Consumption plan for Workload 2. For Workload 1, the Flex Consumption plan provides native virtual network integration without any baseline instance charge, scaling down to zero cost during idle periods. For Workload 2, the Flex Consumption plan supports unbounded execution timeouts for queue-triggered functions (configured via host.json) and scales down to zero when the queue is empty, ensuring the 18-minute run completes without timeout errors and costs nothing when idle.

Step-by-Step Solution

1
Analyze Workload 1 requirements for outbound network connectivity and idle pricing behavior.
Workload 1 needs native outbound VNet integration and must scale to zero compute instances with zero idle costs. The standard Consumption plan is ruled out because it lacks VNet support. The Premium plan and Dedicated plans are ruled out because they incur baseline charges even when idle. The Flex Consumption plan supports native VNet integration and scales to zero cost when idle.
Ensures the database can be reached securely without incurring unnecessary infrastructure costs during idle periods.
2
Analyze Workload 2 requirements for execution timeout limits and scaling capabilities.
Workload 2 runs a daily batch job that requires 18 minutes. The standard Consumption plan has a strict 10-minute timeout limit, which would cause execution failure. The Premium and Dedicated plans can run for 18 minutes but charge continuously, violating the idle cost requirement. The Flex Consumption plan allows unbounded execution limits for non-HTTP triggers and scales to zero when no messages are present.
Ensures the 18-minute batch job executes successfully without timing out and only incurs billing during runtime.
3
Select the correct combination of options representing Flex Consumption for both Workload 1 and Workload 2.
Options representing the Azure Functions Flex Consumption plan for Workload 1 and Workload 2 are selected.
Both workloads achieve their required functional constraints at the lowest cost point using the Flex Consumption tier.

Key Concept

Azure Functions hosting plan selection based on virtual network integration, execution limits, and scale-to-zero billing behavior.
Rate this question