Examkin

Question

Difficulty: HardContainer-Based Workloads

A healthcare technology company is designing a secure cloud-native application on Azure to process patient data. The application requires two primary workloads:

* A front-end REST API that handles user requests, runs continuously, and scales dynamically based on incoming HTTP request volume.
* A background processing component that executes complex medical image analysis tasks. Each analysis task takes between 15 to 45 minutes to complete, must run in its own isolated container environment, and must scale down to zero when no tasks are in the queue.

You need to recommend a compute solution for the application. The design must minimize administrative and operational overhead.

Which two compute options should you recommend?

  1. Azure Container Apps to host the front-end REST APIAnswer
  2. Azure Container Apps jobs to host the background medical image analysis tasksAnswer
  3. C
    Azure Kubernetes Service (AKS) to host both the front-end REST API and background tasks
  4. D
    Azure Functions on a Consumption plan to host the background medical image analysis tasks

Answer

Azure Container Apps to host the front-end REST API, and Azure Container Apps jobs to host the background medical image analysis tasks
The correct recommendation uses Azure Container Apps for the front-end REST API and Azure Container Apps jobs for the background medical image analysis. Azure Container Apps handles continuous HTTP-triggered workloads with automatic scaling and zero cluster management. Azure Container Apps jobs are designed for run-to-completion, event-triggered execution (such as processing from a queue) and support long-running processes up to multiple hours, which easily accommodates the 15 to 45-minute medical image analysis tasks while scaling down to zero when idle and minimizing management overhead.

Step-by-Step Solution

1
Analyze the REST API workload requirements.
The API runs continuously, scales based on HTTP requests, and needs minimal management. Azure Container Apps (ACA) provides serverless container hosting that scales on HTTP traffic and requires very low administrative overhead.
This establishes the best service for the web/API component.
2
Analyze the background image analysis workload requirements.
The background tasks are run-to-completion jobs that take 15 to 45 minutes. This exceeds the 10-minute timeout of serverless options like Azure Functions Consumption plans. Azure Container Apps jobs support longer executions, run containers in isolation, scale to zero, and have low overhead.
This establishes the best service for the long-running batch job component.
3
Evaluate the design constraints for operational efficiency.
Azure Kubernetes Service (AKS) meets the technical capability but introduces high management overhead (cluster upgrades, node pools), violating the 'minimize administrative effort' constraint. Therefore, AKS is ruled out.
This filters out viable but operationally heavy alternatives.

Key Concept

Azure Container Apps and Jobs vs. AKS and Serverless Functions
Rate this question

Topics

Container-Based Workloads

More questions from this topic