Question

Difficulty: MediumContainer-Based Workloads

A financial technology company is designing a container-based background processing service on Azure. The service must retrieve and process transaction records from an Azure Service Bus queue. Each transaction record takes up to 1212 minutes to process.

The solution must meet the following requirements:
- Automatically scale down to zero instances when no messages are in the queue.
- Scale out dynamically based on the queue depth using Kubernetes Event-driven Autoscaling (KEDA).
- Support strict regulatory compliance requiring complete administrative and network isolation between production and development environments.
- Minimize administrative effort and operational overhead.

Which two configurations should you recommend as part of the architecture? (Select two.)

  1. Azure Container Apps to host the background processing serviceAnswer
  2. Separate Azure Container Apps environments, each connected to a dedicated Log Analytics workspace, for production and developmentAnswer
  3. C
    Azure Kubernetes Service (AKS) to host the containerized service
  4. D
    Azure Functions on a Consumption plan to host the processing service
  5. E
    A single Azure Container Apps environment with a single shared Log Analytics workspace for both production and development environments

Answer

Deploy the background processing service on Azure Container Apps, and isolate production and development workloads by running them in separate Azure Container Apps environments configured with dedicated Log Analytics workspaces.
Deploying the workload to Azure Container Apps is correct because it is a serverless platform that supports containerized workloads, scales dynamically to zero, and integrates natively with KEDA out of the box, fulfilling all scaling and management requirements with minimal administrative overhead. Using separate environments, each with its own Log Analytics workspace, fulfills the compliance requirement by enforcing strict administrative and network isolation boundaries between production and development.

Step-by-Step Solution

1
Evaluate the hosting requirements for container workloads that scale to zero and leverage KEDA while minimizing administrative overhead.
Azure Container Apps is identified as the best fit because it provides serverless containers with native KEDA integration, avoiding the cluster management overhead of Azure Kubernetes Service (AKS).
This filters out AKS as it increases administrative effort, and highlights Azure Container Apps as the primary compute candidate.
2
Check the execution time constraints against the serverless hosting options.
Since processing a record can take up to 12 minutes, Azure Functions on a Consumption plan is ruled out because it enforces a maximum timeout of 10 minutes.
This prevents runtime failures caused by system-level execution timeout limits.
3
Determine the isolation configuration needed to meet regulatory compliance for separate environments.
Separate Azure Container Apps environments and separate Log Analytics workspaces must be deployed.
A single environment or shared workspace violates compliance requirements for absolute administrative and network boundary isolation.

Key Concept

Selecting the optimal Azure container hosting option (Azure Container Apps vs. AKS vs. Azure Functions) based on scaling mechanisms, execution timeouts, operational overhead, and compliance isolation boundaries.
Rate this question