A company's Azure Function uses a Storage Queue trigger. During a traffic spike, 50,000 messages arrive and the function scales out. Developers notice duplicate message processing. What is causing this and how should it be addressed?
-
A
Queue Storage guarantees at-least-once delivery; use idempotent logic or track processed message IDs
-
B
Increase the visibilityTimeout in host.json to prevent other instances from seeing the message
-
C
Switch to Event Grid trigger, which guarantees exactly-once delivery
-
D
Set maxDequeueCount to 1 to prevent re-processing