Examkin

Question

Difficulty: Very hardServerless and Web Application Hosting

An enterprise is designing a serverless and containerized architecture for a financial reconciliation platform. The system requires hosting two workloads with distinct execution behaviors and networking constraints:

* Workload 1: An API gateway helper that intercepts and validates inbound transactions. It experiences unpredictable, highly spiked traffic (from 0 to thousands of concurrent requests) with long periods of complete inactivity. To access protected on-premises ledger databases, this workload requires integration with an Azure Virtual Network (VNet). Minimizing idle infrastructure costs is critical.
* Workload 2: A batch reconciliation job that runs once daily. The job retrieves transaction logs, executes complex audit rules, and typically runs for 40 minutes. It must also run within a private subnet to securely communicate with back-end databases, and the team wants to minimize operational overhead.

Which two of the following Azure compute solutions should you recommend to support these workloads? (Select TWO.)

  1. Azure Functions on a Flex Consumption plan to host Workload 1Answer
  2. Azure Container Apps Jobs to host Workload 2Answer
  3. C
    Azure Functions on a Consumption plan to host Workload 2
  4. D
    Azure Kubernetes Service (AKS) to host Workload 2
  5. E
    Azure Functions on a Premium plan to host Workload 1

Answer

Azure Functions on a Flex Consumption plan to host the API gateway helper (Workload 1), and Azure Container Apps Jobs to host the daily batch reconciliation job (Workload 2).
The correct solution involves selecting Azure Functions on a Flex Consumption plan for the API endpoint and Azure Container Apps Jobs for the batch reconciliation job. The Flex Consumption plan supports virtual network integration while allowing the application to scale to zero instances during idle periods, satisfying the cost and network security requirements. Azure Container Apps Jobs are designed for run-to-completion workloads, support virtual network integration, can run for up to several hours, and avoid the management overhead associated with Kubernetes clusters.

Step-by-Step Solution

1
Analyze the requirements for Workload 1.
Workload 1 requires virtual network integration, rapid scaling under unpredictable traffic spikes, and scale-to-zero capability to minimize costs during idle periods.
Identifying these key constraints narrows down the options to plans that support virtual network integration without requiring an always-on instance.
2
Evaluate compute candidates for Workload 1.
The Flex Consumption plan satisfies virtual network integration, rapid scale-out, and scales to zero. The Premium plan and Dedicated App Service plans fail the scale-to-zero cost requirement because they charge for a minimum of one running instance.
Matching constraints to Azure compute plans ensures the most cost-effective and compliant serverless host is chosen.
3
Analyze the requirements for Workload 2.
Workload 2 requires running a batch job for 40 minutes inside a private subnet while minimizing operational overhead.
This workload has a long-running execution requirement that exceeds standard serverless timeout limits, and a preference for low operational complexity.
4
Evaluate compute candidates for Workload 2.
Azure Container Apps Jobs support runs of up to several hours, run in a private subnet, scale to zero, and have low overhead. Standard Consumption Functions fail due to a 10-minute timeout. Azure Kubernetes Service (AKS) succeeds technically but introduces high operational overhead.
This step eliminates options that either fail due to execution limits or introduce excessive operational and financial overhead.

Key Concept

Azure serverless compute selection based on execution limits, virtual network integration, scaling behavior, and operational overhead.
Estimated Time:3m 0s
Rate this question

Topics

Serverless and Web Application Hosting

More questions from this topic