A cattail-pond set of Azure Functions sits idle most of the month and spikes hard at filing deadline. Which APIM tier family fits that bursty serverless pattern?
Select an answer to reveal the explanation.
Short Explanation
Bursty and mostly idle? Consumption APIM meters like serverless—you pay for executions, not a full-time Premium footprint sitting quiet all month.
Full Explanation
For a cattail-pond Function estate that sits idle most of the month and spikes hard at filing deadline, the Consumption tier of API Management matches the serverless, per-execution billing pattern: capacity scales with usage rather than keeping a full dedicated gateway footprint warm all month. That fits bursty, mostly idle municipal workloads when VNet injection and multi-region dedicated gateways are not required.
Premium with always-on multi-region gateways is the opposite cost shape—powerful for enterprise networking and steady multi-region presence, but expensive if traffic is rare outside deadline week. Developer tier is explicitly nonproduction and must not be treated as the long-term production SLA. Renaming a dedicated App Service plan does not create an APIM gateway or its product/policy model.
Exam caveat: Consumption APIM trades some advanced networking and scale features for serverless economics—if the city later needs VNet injection or multi-region gateways, plan a tier move rather than forcing Consumption to do Premium’s job.
Operational check: after selecting Consumption, publish a test API, generate load that mimics filing-deadline spikes, and verify billing/metrics reflect execution-oriented usage while idle periods do not retain Premium-class always-on capacity costs.