Question

Difficulty: MediumServerless and Web Application Hosting

A healthcare provider is designing a serverless architecture to ingest and process HL7 clinical data messages and host a lightweight REST API. The REST API will receive incoming message metadata and must respond within 200200 milliseconds to the sender. The clinical data messages are processed asynchronously by a background worker that can take up to 2020 minutes to complete the analysis and transformation for each message. The architecture must minimize administrative overhead and ensure that compute costs are reduced to zero during periods of inactivity. Which of the following Azure services should you recommend to meet these requirements? (Select TWO.)

  1. Azure Container Apps jobs to run the background workerAnswer
  2. Azure Functions on a Consumption plan to host the REST APIAnswer
  3. C
    Azure Functions on a Consumption plan to run the background worker
  4. D
    Azure Kubernetes Service (AKS) to host both the REST API and the background worker

Answer

The architecture should include Azure Container Apps jobs to run the background worker and Azure Functions on a Consumption plan to host the REST API.
To process the 2020-minute background tasks while scaling to zero during inactivity, Azure Container Apps jobs is the correct choice because it does not suffer from the 1010-minute limit of serverless functions. To host the lightweight REST API with zero administrative overhead and zero cost during idle periods, Azure Functions on a Consumption plan is the most efficient choice.

Step-by-Step Solution

1
Analyze execution duration constraints
The background job requires up to 2020 minutes to run. Standard serverless execution limits must be checked.
Azure Functions Consumption plan has a maximum execution limit of 1010 minutes, which makes it unsuitable for this background task.
2
Select hosting for the background worker
Azure Container Apps jobs can execute tasks that run for hours to completion and can scale down to zero when idle.
This satisfies the duration requirements while keeping costs to zero during periods of inactivity with minimal overhead.
3
Select hosting for the REST API
Azure Functions on a Consumption plan is cost-effective, scales to zero, and has minimal administrative overhead.
The REST API only handles metadata ingestion, which fits within the execution window and low-latency bounds of serverless functions.

Key Concept

Selecting Azure serverless hosting options based on execution limits, administrative overhead, and scaling behaviors.
Estimated Time:1m 30s
Rate this question