Question

Difficulty: HardContainer-Based Workloads

You are designing the container compute infrastructure for a new retail analytics platform. The platform includes the following two workloads:
- A message-processing service that reads tasks from an Azure Service Bus queue and must scale dynamically based on the queue depth, including scaling down to zero instances.
- A daily reporting job that aggregates transactional data, runs for up to three hours per execution, and must execute to completion.

You need to recommend a containerized hosting solution for both workloads. The solution must minimize administrative effort.

Which two Azure container hosting options should you recommend?

  1. Azure Container Apps to host the message-processing serviceAnswer
  2. Azure Container Apps Jobs to host the daily reporting jobAnswer
  3. C
    Azure Kubernetes Service (AKS) to host both workloads
  4. D
    Azure Functions on a Consumption plan to host the daily reporting job

Answer

Azure Container Apps to host the message-processing service and Azure Container Apps Jobs to host the daily reporting job.
The correct recommendation is to use Azure Container Apps to host the message-processing service and Azure Container Apps Jobs to host the daily reporting job. Azure Container Apps manages event-driven scaling (KEDA) and supports scaling to zero, satisfying the requirements of the message-processing service. Azure Container Apps Jobs provides a serverless execution environment designed for run-to-completion tasks, supporting long-running executions of up to 24 hours, which accommodates the three-hour daily reporting job. Both services are fully managed, meeting the goal of minimizing administrative effort.

Step-by-Step Solution

1
Analyze the scaling and operational requirements of the message-processing workload.
The service needs dynamic scaling based on queue depth (KEDA), scale-to-zero capabilities, and minimized administrative overhead.
This workload maps to Azure Container Apps, which handles event-driven scaling automatically under a fully managed serverless model.
2
Analyze the execution duration and lifecycle of the reporting workload.
The job is a daily, run-to-completion batch process that takes up to three hours.
Azure Container Apps Jobs is ideal for this since it supports executions lasting up to 24 hours without cluster management overhead.
3
Evaluate the administrative overhead of Azure Kubernetes Service (AKS).
AKS is rejected because it requires cluster, virtual machine node pool, and control plane management, failing the requirement to minimize administrative effort.
AKS is suitable when custom Kubernetes API access or deep control plane customization is needed, which is not required here.
4
Evaluate the execution constraints of Azure Functions Consumption plan.
Azure Functions on a Consumption plan is rejected because of its 10-minute timeout limit.
The daily reporting job runs for three hours, which exceeds the platform's hard limits.

Key Concept

Selecting the optimal Azure container hosting option based on scaling needs, execution duration, and administrative overhead constraints.
Rate this question