Question

Difficulty: HardServerless and Web Application Hosting

You are designing the serverless compute architecture for a reporting system that consists of two distinct workloads:

* Workload 1: A data processing service that runs in response to file uploads. Each execution takes up to 25 minutes to complete. The service requires access to an Azure Files share.
* Workload 2: A microservice that processes messages from an Azure Service Bus queue. The service must scale down to zero instances when no messages are present in the queue, and must scale out rapidly during peak loads. The application has no existing Kubernetes configuration, and you must minimize operational and infrastructure overhead.

Which two compute configurations should you recommend?

  1. For Workload 1, deploy an Azure Container Apps Job.Answer
  2. For Workload 2, deploy an Azure Container App.Answer
  3. C
    For Workload 1, deploy an Azure Function on a Consumption plan.
  4. D
    For Workload 2, deploy an Azure Kubernetes Service (AKS) cluster.
  5. E
    For Workload 2, deploy an Azure Kubernetes Service (AKS) cluster configured with virtual nodes.

Answer

Deploy an Azure Container Apps Job for Workload 1 and an Azure Container App for Workload 2.
The correct architecture uses an Azure Container Apps Job for Workload 1 and an Azure Container App for Workload 2. An Azure Container Apps Job is designed for run-to-completion containerized tasks, supports execution times beyond 10 minutes (up to 24 hours), and supports mounting Azure Files shares. An Azure Container App is designed for microservices, supports scaling to zero based on Service Bus queue length via KEDA, and provides a serverless model that minimizes operational overhead, avoiding the infrastructure management required by Azure Kubernetes Service (AKS).

Step-by-Step Solution

1
Analyze Workload 1 execution duration and storage requirements.
Workload 1 runs for up to 25 minutes and requires an Azure Files share mount. Azure Functions on a Consumption plan has a strict 10-minute timeout limit and cannot host this workload.
This rules out standard Consumption plan serverless functions and requires a compute solution that supports longer runtimes and file share integration.
2
Select the correct compute option for Workload 1.
An Azure Container Apps Job is selected. Container Apps Jobs run containers to completion, support execution times of up to 24 hours, and support mounting Azure Files shares.
This configuration meets all requirements of Workload 1 with minimal administrative overhead.
3
Analyze Workload 2 scaling and operational overhead constraints.
Workload 2 must scale to zero when idle, scale out rapidly under load, and minimize operational overhead. There is no existing Kubernetes investment.
This excludes Azure Kubernetes Service (AKS) because AKS introduces significant administrative overhead for managing Kubernetes infrastructure.
4
Select the correct compute option for Workload 2.
An Azure Container App is selected. Azure Container Apps are fully managed, scale to zero using KEDA based on queue length, and avoid the infrastructure overhead of AKS.
This matches all scale-to-zero and low-overhead requirements for a queue-based containerized microservice.

Key Concept

Azure serverless and container hosting options require matching workload runtime limits, storage integrations, and scaling requirements to the appropriate service while minimizing operational overhead.
Rate this question