An HTTP-triggered Azure Function must save each request body as a message on a Storage queue with the least code. What should you use?
- A A queue output binding (correct answer)
- B A queue trigger
- C The Storage SDK with a connection string in the code
- D A timer trigger that polls the HTTP endpoint
Shortcut: Write to another service with no SDK code = output binding. Run when something happens = trigger. A queue trigger starts a function when a message arrives, which is the opposite direction, and SDK code with an embedded connection string is more work and less secure.
An output binding writes the function's result to the queue without any SDK code, and the connection comes from app settings. A queue trigger starts a function when a message arrives, which is the opposite direction, and SDK code with an embedded connection string is more work and less secure.