Question

Difficulty: MediumContainer-Based Workloads

A financial services company is designing a new cloud-native application on Azure. The application will consist of several containerized microservices that process transactions.

The design requirements are as follows:
* The microservices must scale dynamically based on the number of messages in an Azure Service Bus queue using Kubernetes Event-driven Autoscaling (KEDA).
* Administrative effort for infrastructure management, such as cluster upgrades and node patching, must be minimized.
* The application does not require direct access to the Kubernetes API or custom resource definitions (CRDs).
* The application must be deployed across two different Azure regions to comply with strict regional data sovereignty laws. Log data originating from each region must be kept isolated and accessible only within that region.

You need to recommend a solution that meets the requirements.

Which solution should you recommend?

  1. A
    Deploy the microservices to Azure Kubernetes Service (AKS) in each region. Configure a separate Log Analytics workspace in each region.
  2. B
    Deploy the microservices to Azure Container Apps (ACA) in each region. Configure a single centralized Log Analytics workspace.
  3. Deploy the microservices to Azure Container Apps (ACA) in each region. Configure a separate Log Analytics workspace in each region.Answer
  4. D
    Deploy the microservices to Azure Kubernetes Service (AKS) in each region. Configure a single centralized Log Analytics workspace.

Answer

Deploy the microservices to Azure Container Apps (ACA) in each region and configure a separate Log Analytics workspace in each region.
The correct solution uses Azure Container Apps (ACA) combined with separate regional Log Analytics workspaces. Azure Container Apps is a serverless container hosting platform that supports event-driven autoscaling using KEDA natively. Because the workload does not require custom Kubernetes API access, choosing ACA minimizes the administrative overhead of managing underlying nodes and cluster configurations. Configuring separate Log Analytics workspaces in each region ensures logs originating from those regions are isolated, adhering to the data sovereignty rules.

Step-by-Step Solution

1
Analyze compute requirements to select between Azure Kubernetes Service (AKS) and Azure Container Apps (ACA).
Azure Container Apps is chosen because the application requires KEDA scaling, requires no custom Kubernetes API access, and has a strict requirement to minimize infrastructure administration effort.
AKS requires administrative effort for node configuration, cluster upgrades, and patching, which is unnecessary for this microservices application.
2
Analyze compliance requirements for logging and data residency.
Separate Log Analytics workspaces must be deployed in each region.
Data sovereignty laws require that logs from each region remain isolated and accessible only within their respective regions, preventing the use of a single centralized workspace.
3
Combine compute and logging selections to identify the correct architecture.
The final recommendation is Azure Container Apps paired with separate regional Log Analytics workspaces.
This configuration meets all constraints regarding scaling, administrative overhead minimization, and regional log isolation.

Key Concept

Selecting container hosting options based on administrative effort constraints, KEDA integration, and logging isolation compliance.
Rate this question