What causes the 'Singleton lock' behaviour needed to ensure a timer function runs on only one instance?
- A A blob lease acquired by the runtime (correct answer)
- B A Service Bus session
- C A database row lock
- D Nothing; timers run on all instances
Shortcut: The timer trigger acquires a blob lease in the AzureWebJobsStorage account, guaranteeing a single instance executes each scheduled occurrence.