A lichen-survey import writes two related items in one Cosmos transactional batch. Readers must never see the second item without the first. Which consistency level should the developer pick?
Select an answer to reveal the explanation.
Short Explanation
Picture a two-page stamp: nobody should see page two without page one. Consistent prefix keeps those transactional batch writes in order for readers. Lone single-item writes still behave more like eventual.
Full Explanation
Consistent prefix guarantees that updates are returned in order—readers never see a later write without earlier writes from the same transactional batch. Eventual allows out-of-order visibility. Session is about read-your-writes within a session, not batch ordering guarantees for all readers. Strong with multi-region writes is not a supported pairing and is not the right framing for this batch-order requirement.