hardmultiple choiceObjective-mapped

A global IoT platform ingests telemetry data from millions of devices. The application requires multi-region writes to support low-latency ingestion from any location. The schema uses JSON documents and fields often vary. The team needs automatic conflict resolution when the same document is updated concurrently from different regions. Additionally, read operations for device commands must use strong consistency, while user-facing dashboard queries can use eventual consistency. Which Azure Cosmos DB configuration should they choose?

Question 1hardmultiple choice
Full question →

A global IoT platform ingests telemetry data from millions of devices. The application requires multi-region writes to support low-latency ingestion from any location. The schema uses JSON documents and fields often vary. The team needs automatic conflict resolution when the same document is updated concurrently from different regions. Additionally, read operations for device commands must use strong consistency, while user-facing dashboard queries can use eventual consistency. 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

Distractor review

Azure Cosmos DB with single-master and multiple read regions

Single-master allows writes only in one region, so multi-region writes are not possible. This does not meet the low-latency ingestion requirement from all regions.

B

Distractor review

Azure Cosmos DB with multi-master and default strong consistency

While multi-master supports multi-region writes, default strong consistency would cause higher write latency due to synchronous replication across regions, which may not be optimal for all operations.

C

Best answer

Azure Cosmos DB with multi-master and per-request consistency override

Multi-master allows writes in any region and automatic conflict resolution. Per-request consistency override enables the application to use strong consistency for critical device command reads and eventual consistency for other reads, meeting all requirements.

D

Distractor review

Azure Cosmos DB with multi-master and eventual consistency only

Eventual consistency only cannot guarantee strong consistency for device command reads, which is required.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

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?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Azure Cosmos DB with multi-master and per-request consistency override — Azure Cosmos DB with multi-region writes (multi-master) enables writes in multiple regions with automatic conflict resolution. It supports multiple consistency levels, including strong and eventual. By setting the consistency at the request level using a programming model like the Azure Cosmos DB SDK, the application can enforce strong consistency for critical reads (device commands) and eventual consistency for others. Single-master configurations do not allow multi-region writes. Multi-master with only eventual consistency would not support strong consistency for device commands. Multi-master with default strong consistency would impose high latency globally. Per-request consistency override is the correct approach.

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.