A municipal soil-lab webhook Function accepts a soil-sample JSON body and must persist one Cosmos DB document per call. The team wants to avoid constructing a Cosmos SDK client inside the function. What should they add?
Select an answer to reveal the explanation.
Short Explanation
Output bindings are the conveyor belt out of the function. Attach a Cosmos DB output binding and drop the document on it—no hand-built CosmosClient required for a simple write.
Full Explanation
Azure Functions supports a Cosmos DB output binding so the runtime persists documents without the function constructing an SDK client for that write path. An input binding reads rather than inserts; timers and Redis are outside this binding scenario (Redis is also out of the January 2026 AZ-204 skill list). Consistency levels and change-feed processors belong to storage design, not this binding choice.