You want a function to save to storage without writing client code. What do you use?
Why B is the answer
An output binding
Bindings connect to services declaratively, which reduces boilerplate.
In detail
- An output binding saves data with no client code.
- Bindings keep functions short.
Use case
An illustrative scenario, not a real incident.
A function must save each result to storage. An output binding handles it, with no storage client code.
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["Trigger"] --> S1["Function runs"] --> S2["Output binding"] --> S3["Storage"]
Key point: Output bindings write with no client code.
Why the other options are wrong
- A. A Dockerfile added to the project
- A Dockerfile packages code.
- C. A second trigger on the same function
- A function has only one trigger.
- D. A larger hosting plan for the function app
- A plan does not change how code connects to storage.