Soru

Zorluk: OrtaContainer-Based Workloads

A financial services company is designing a container-based credit scoring application on Azure. The application has the following design requirements:

* A real-time scoring API that must scale dynamically to zero during periods of inactivity and automatically scale up in response to HTTP request spikes, with minimal administrative and infrastructure management effort.
* A batch risk-processing engine that executes long-running, CPU-intensive simulation tasks that can take up to 4 hours to complete.

Which two container hosting solutions should you recommend to meet these requirements?

  1. Azure Container Apps for the real-time scoring APICevap
  2. Azure Container Apps Jobs for the batch risk-processing engineCevap
  3. C
    Azure Kubernetes Service (AKS) for the real-time scoring API
  4. D
    Azure Functions on a Consumption plan for the batch risk-processing engine
  5. E
    Azure Container Instances (ACI) with a custom scaling script for the real-time scoring API

Cevap

Azure Container Apps for the real-time scoring API and Azure Container Apps Jobs for the batch risk-processing engine.
Selecting Azure Container Apps for the real-time scoring API provides native scale-to-zero capabilities and automatic HTTP scaling without the administrative overhead of cluster management. Selecting Azure Container Apps Jobs for the batch risk-processing engine supports containerized tasks that run to completion and can execute for up to 24 hours, satisfying the 4-hour processing requirement.

Adım Adım Çözüm

1
Evaluate hosting options for the real-time scoring API requiring scale-to-zero capability and minimal administrative overhead.
Azure Container Apps natively scales to zero based on HTTP traffic and requires minimal management. In contrast, Azure Kubernetes Service (AKS) adds significant cluster management overhead, and Azure Container Instances (ACI) lacks native HTTP-based scale-to-zero autoscaling.
This matches the API requirements with the lower-overhead serverless container options.
2
Evaluate hosting options for the batch risk-processing engine running 4-hour simulation tasks.
Azure Container Apps Jobs is selected because it supports batch tasks running up to 24 hours. Azure Functions on a Consumption plan is ruled out because it has a 10-minute maximum execution timeout.
This ensures the long-running task does not time out during execution.

Anahtar Kavram

Choosing Azure container solutions based on operational overhead, scaling behavior, and execution limits.
Bu soruyu puanla