An inventory tracking solution needs Cosmos DB settings so reads return the most recent committed version of an item and writes provide ordering guarantees. Which consistency level should you choose?

Strong consistency ensures that reads always return the most recent committed version of an item, and writes are guaranteed to be ordered globally. This aligns with the requirement for the most recent data and ordering guarantees in an inventory tracking solution. Consistent Prefix provides ordering guarantees but allows for some staleness, meaning reads might not always get the absolute latest version. Eventual consistency offers the lowest latency and highest throughput but provides no ordering guarantees and allows for significant data staleness. Bounded Staleness allows for a configurable maximum staleness, either by time or by the number of versions, which doesn't meet the "most recent committed version" requirement. Session consistency is scoped to a client session, meaning a client will see its own writes, but other clients might not see those writes immediately, which doesn't provide global ordering or immediate consistency for all reads.