Examkin

Question

Difficulty: MediumServerless and Web Application Hosting

A utility company is designing a serverless backend architecture to process smart meter telemetry and host a customer-facing billing API. The solution must meet the following requirements:

* Telemetry processing: Ingestion triggers a job that aggregates and stores data streams. Each execution takes up to 1515 minutes to complete.
* Billing API: Must support peak hourly traffic of 5,0005,000 requests, experience minimal latency during sudden scale-up (no cold starts), and require direct integration with an Azure Virtual Network (VNet).
* Operational overhead: Must be minimized.

Which two Azure hosting options should you recommend to meet these requirements? (Select TWO.)

  1. A
    Azure Functions on a Consumption plan to process the telemetry data.
  2. Azure Container Apps Job to process the telemetry data.Answer
  3. Azure Functions on a Premium plan to host the billing API.Answer
  4. D
    An Azure Kubernetes Service (AKS) cluster to host the billing API.

Answer

Azure Container Apps Job to process the telemetry data, and Azure Functions on a Premium plan to host the billing API.
The correct architecture uses Azure Container Apps Jobs for the long-running (1515-minute) telemetry processing job because it supports extended run-to-completion workloads without container management overhead. For the billing API, Azure Functions on a Premium plan is selected because it natively supports virtual network (VNet) integration, scales rapidly to handle peak demand, and uses pre-warmed instances to completely avoid cold start latencies, all while keeping management overhead low.

Step-by-Step Solution

1
Evaluate the telemetry processing requirement against Azure Functions timeout limits.
The telemetry processing execution takes up to 1515 minutes. Under the Azure Functions Consumption plan, the maximum execution timeout is capped at 1010 minutes (600600 seconds). Therefore, a Consumption plan cannot be used for this task.
To prevent jobs from failing due to hard timeout limits.
2
Select a serverless run-to-completion option for the 1515-minute job that minimizes overhead.
Azure Container Apps Jobs allow containerized batch tasks to execute for extended periods beyond 1010 minutes without managing VMs or Kubernetes infrastructure.
To satisfy the long-running processing requirement while minimizing operational overhead.
3
Evaluate the billing API hosting requirements for VNet integration, cold start mitigation, and operational overhead.
Azure Functions on a Premium plan provides VNet integration and pre-warmed instances to avoid cold starts. Azure Kubernetes Service (AKS) is rejected due to high operational management overhead.
To fulfill the latency and network isolation constraints of the customer-facing API.

Key Concept

Selecting serverless compute options based on execution limits, cold start constraints, network isolation, and operational overhead.
Estimated Time:2m 0s
Rate this question

Topics

Serverless and Web Application Hosting

More questions from this topic