You need a small HTTP API that scales with demand, with no servers to manage. What fits?
Why C is the answer
Azure Functions with an HTTP trigger
An HTTP trigger turns an Azure Function into a small serverless API that scales with demand.
In detail
- An HTTP trigger gives you a small API with no servers.
- Plans differ in cold start behavior.
Use case
An illustrative scenario, not a real incident.
A small lookup API has uneven traffic. Azure Functions with an HTTP trigger scales with demand, with no servers to manage.
See it in different ways
flowchart LR A["HTTP or queue trigger"] --> B["Function code"] C["Input binding"] --> B B --> D["Output binding"]
flowchart LR A["Trigger"] --> B["Function"] B --> C["Output binding"] C --> D["Storage"]
flowchart LR S0["Request"] --> S1["HTTP trigger"] --> S2["Function"] --> S3["Response"]
Key point: HTTP triggers give small serverless APIs.
Why the other options are wrong
- A. An AKS cluster with one node pool for it
- A cluster is far more than this needs.
- B. A Container Registry build task
- A build task does not serve requests.
- D. A virtual machine with a web server
- A VM is a server to manage.