An enterprise is designing a container-based ingestion and processing solution for healthcare telemetry data. The telemetry is ingested in two distinct geographical regions: East US and West US. The design must accommodate the following requirements:
- Workload 1: A lightweight microservice that processes telemetry messages from an Azure Service Bus queue. The workload must support event-driven scaling using KEDA, including scaling to zero instances when no messages are present, while minimizing infrastructure management overhead.
- Workload 2: A batch processing job that runs model training algorithms. The job requires custom access to the underlying Kubernetes API to orchestrate child pods across dedicated, physically isolated compute nodes.
- Logging: Container logs from the East US and West US regions must be kept strictly segregated within their respective geographical boundaries to comply with local healthcare privacy and data residency laws.
Which three design decisions should you recommend?
- Deploy Workload 1 to Azure Container Apps.Cevap
- Deploy Workload 2 to Azure Kubernetes Service (AKS).Cevap
- Provision two separate regional Log Analytics workspaces to store container logs.Cevap
- DDeploy Workload 1 to Azure Kubernetes Service (AKS) to utilize native KEDA.
- EDeploy Workload 2 to Azure Container Apps Jobs.
- FProvision a single centralized Log Analytics workspace in the primary region for all container logs.