問題文
A function is triggered by a queue and must, within the same invocation, write to two different containers such that either both writes happen or neither does. What is the limitation?
選択肢
- The limitation disappears if both containers are placed in the same account and share a partition key value, because writes then land in the same logical partition
- The function can enable a distributed transaction setting in its host configuration, which coordinates the two writes through a two-phase commit
- Output bindings provide a transaction across all bound targets, so declaring both writes as bindings gives the all-or-nothing behavior the requirement asks for
- There is no cross-container transaction, so the function must be designed to be safely repeatable and to reconcile partial writes after a failure