Soru

Zorluk: ZorContainer-Based Workloads

An automotive manufacturing corporation is designing a container-based telemetry and diagnostics platform on Azure. The platform will be deployed across two European regions. The design must meet the following requirements:
- A set of internal REST APIs must process incoming vehicle diagnostics data.
- A background analytics engine must process messages from an Azure Service Bus queue and scale to zero when no messages are present.
- A third-party security agent must run as a privileged DaemonSet on every container host node to inspect kernel-level system calls.
- Telemetry and logs collected from the workloads in each region must be isolated and stored only within that specific region to meet strict local data residency compliance.

You need to recommend the container hosting and monitoring architecture.

Which solution should you recommend?

  1. Deploy Azure Kubernetes Service (AKS) in both regions with Kubernetes Event-driven Autoscaling (KEDA) configured for the background analytics engine. Configure a separate Azure Log Analytics workspace in each region to collect and store logs locally.Cevap
  2. B
    Deploy Azure Container Apps in both regions, running the APIs as replica apps and the background analytics engine as Azure Container Apps Jobs configured with Service Bus scaling rules. Configure a separate Azure Log Analytics workspace in each region to collect logs.
  3. C
    Deploy Azure Kubernetes Service (AKS) in both regions with Kubernetes Event-driven Autoscaling (KEDA) configured for the background analytics engine. Configure a single centralized Azure Log Analytics workspace to aggregate all logs from both regions to simplify monitoring administration.
  4. D
    Deploy Azure Container Instances (ACI) to host the REST APIs in a container group in both regions, and use Azure Functions on a Consumption plan to run the background analytics engine. Configure a single centralized Azure Log Analytics workspace for all logs.

Cevap

Deploy Azure Kubernetes Service (AKS) in both regions with Kubernetes Event-driven Autoscaling (KEDA) configured for the background analytics engine. Configure a separate Azure Log Analytics workspace in each region to collect and store logs locally.
The correct solution recommends Azure Kubernetes Service (AKS) because running a privileged security agent as a DaemonSet to inspect host-level kernel calls requires access to the underlying VM host nodes, which is supported by AKS but not by serverless container environments like Azure Container Apps. The solution uses KEDA within AKS to natively support event-driven auto-scaling to zero based on Azure Service Bus metrics. To comply with strict regional data isolation rules, the architecture deploys separate Log Analytics workspaces in each region to ensure telemetry data is stored within its local geographic boundary.

Adım Adım Çözüm

1
Analyze the container node access requirement.
The security policy requires a third-party security agent to run as a DaemonSet to inspect kernel-level system calls on container host nodes.
This requirement indicates that the hosting platform must expose access to the underlying virtual machine host nodes. Serverless container offerings like Azure Container Apps and Azure Container Instances abstract host nodes away and do not support DaemonSets or kernel-level inspection.
2
Select the appropriate container hosting service.
Azure Kubernetes Service (AKS) is selected because it provides full control over the node configuration and natively supports DaemonSets.
AKS allows deploying DaemonSets onto the worker nodes to run security agents directly on each VM host, satisfying the security constraint.
3
Evaluate the scaling mechanism for the queue-based worker.
Configure Kubernetes Event-driven Autoscaling (KEDA) on the AKS clusters to scale the background pods based on Service Bus queue metrics.
KEDA allows Kubernetes workloads to scale to zero based on external event sources, meeting the requirement to scale to zero when no Service Bus messages are present.
4
Determine the monitoring and compliance architecture.
Deploy a separate Log Analytics workspace in each European region and route regional cluster logs to their respective local workspaces.
A single centralized Log Analytics workspace would aggregate data across regional boundaries, which violates the strict data residency and isolation compliance requirements.

Anahtar Kavram

Selecting Azure Kubernetes Service (AKS) vs. Azure Container Apps based on node-level control requirements, combined with regional log isolation design.
Tahmini Süre:2m 30s
Bu soruyu puanla