A Durable Functions activity charges a payment, then its response is lost and the activity retries. Which mechanism prevents a second charge most directly?

Choose the single best answer.

A.A longer function timeout alone
B.Deterministic orchestrator code alone
C.A more expensive Functions plan alone
D.A stable payment idempotency key enforced by the payment operation

Show the answer and explanation

✓ Correct answer

A stable payment idempotency key enforced by the payment operation

Payment-side idempotency links retries to one intended business effect. Deterministic orchestration is necessary for replay but does not make external side effects exactly once; longer timeouts and larger plans do not close the response-loss duplication window. Source guide: PDF page(s) 47.

Read the source reference

This item is flagged for content review.

Read and review here, or open the app to practise and save your results on this device.

Practise in the app

Unofficial study aid; not affiliated with or endorsed by Microsoft. Original practice questions are not real examination questions and do not guarantee an exam result.