A global e-commerce company stores product catalog data in a JSON document format. The application requires low-latency reads and writes from multiple geographic regions. The solution must support multi-region writes with automatic conflict resolution and provide a guaranteed 99th percentile latency. Which Azure Cosmos DB API and consistency level should they choose?

Table API with Eventual consistency

Table API is for key-value data, not JSON documents, and eventual consistency does not guarantee read-your-writes.

SQL API with Strong consistency

Strong consistency has higher latency and cannot guarantee 99th percentile latency across multi-region writes.

MongoDB API with Bounded staleness consistency

MongoDB API is also for document data, but Bounded staleness may still have higher latency than session, and session is more typical for e-commerce.

What does this AZ-305 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: SQL API with Session consistency — Azure Cosmos DB offers multiple APIs; the SQL API is for document data with native JSON support. For multi-region writes and guaranteed 99th percentile latency, you need to enable multi-region writes and choose a consistency level lower than 'Strong' (since strong consistency has higher latency). 'Session' consistency provides a balance: it guarantees monotonic reads, writes, and read-your-writes, and is widely used for e-commerce. It also offers low latency while still providing strong guarantees within a session. 'Eventual' is weaker, 'Bounded staleness' also works but may have higher latency than session. 'Strong' cannot achieve low latency across regions.

What should I do if I get this AZ-305 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.