Which event causes billing to start for an Azure Function running on the Consumption plan?
Think about what triggers actual work and resource use.
In the Consumption plan, billing starts only when the function runs in response to an event, not when deployed or idle.
Which statement correctly describes the scaling behavior difference between Azure Functions Consumption and Premium plans?
Consider how each plan handles instance readiness.
The Consumption plan scales automatically but may have cold starts. The Premium plan pre-warms instances to reduce cold starts.
Which Azure Function pricing plan supports Virtual Network (VNet) integration for secure network isolation?
Think about which plan offers advanced networking features.
Only the Premium plan supports VNet integration for secure network isolation.
You have an Azure Function with a steady, predictable workload that requires no cold starts and needs to run 24/7. Which plan is best?
Consider the need for no cold starts and always-on availability.
The Premium plan supports pre-warmed instances and always-on, making it ideal for steady workloads without cold starts.
How does memory allocation affect billing in Azure Functions Consumption vs Premium plans?
Think about how memory customization affects billing in each plan.
Consumption plan bills per GB-second based on allocated memory (default 1.5 GB). Premium plan allows custom memory and bills per vCPU and memory allocated.