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?
- 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
- BDeploy 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.
- CDeploy 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.
- DDeploy 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.