Hotspot QuestionYou have an Azure Functions app using the Consumption hosting plan for a company.

File name: host.json

Function name: f3

Azure Functions dynamic concurrency is enabled at the function-app host level in the host.json file . The concurrency configuration section contains the dynamicConcurrencyEnabled property. Setting this value to true enables the Functions host to dynamically learn and adjust concurrency levels for supported triggers rather than requiring fixed manual limits.

Although dynamic concurrency is enabled globally, Microsoft explicitly states that the learned concurrency level is managed independently for each individual function . This allows a resource-intensive function to operate at a lower concurrency level while a lightweight function in the same app can execute with greater concurrency, protecting host health while maximizing throughput.

Of the functions listed, f3 , which uses an Azure Queue Storage trigger , supports dynamic concurrency. Microsoft currently documents dynamic concurrency support for Azure Queue Storage, Azure Blob Storage, and Azure Service Bus triggers , subject to the required extension versions. HTTP and Timer triggers do not participate in this dynamic-concurrency model.

Therefore, configure dynamic concurrency in host.json , and f3 is the function whose concurrency will be dynamically managed.

Study Guide references: Azure Functions → Concurrency; Dynamic concurrency; host.json; Queue Storage trigger concurrency.