mediummultiple choiceObjective-mapped

A global company stores customer profile data in JSON format. The application requires low-latency writes and reads from multiple regions. The solution must support multi-region writes with automatic conflict resolution and provide high availability. Which Azure Cosmos DB configuration should they choose?

Question 1mediummultiple choice
Full question →

A global company stores customer profile data in JSON format. The application requires low-latency writes and reads from multiple regions. The solution must support multi-region writes with automatic conflict resolution and provide high availability. Which Azure Cosmos DB configuration should they choose?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

SQL API with eventual consistency and multi-region writes enabled

SQL API handles JSON, eventual consistency supports multi-region writes, and conflict resolution is automatic.

B

Distractor review

MongoDB API with strong consistency and multi-region writes enabled

Strong consistency is not compatible with multi-region writes; this configuration is invalid.

C

Distractor review

Table API with consistent prefix consistency and single-region writes

Table API stores key-value data, not JSON; single-region writes do not meet the multi-region write requirement.

D

Distractor review

Gremlin API with session consistency and multi-region writes enabled

Gremlin API is for graph databases, not suitable for JSON document storage.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related AZ-305 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

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 eventual consistency and multi-region writes enabled — Azure Cosmos DB SQL API natively supports JSON documents and allows multi-region writes with automatic conflict resolution when using a relaxed consistency level like eventual. Eventually consistent reads provide low latency and high availability. Strong consistency is not supported with multi-region writes. Single-region writes do not meet the multi-region write requirement. The Gremlin API is for graph data, not JSON documents.

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.

Discussion

Loading comments…

Sign in to join the discussion.