The answer is to use a stored procedure to compute and update the property in a single transaction. This is correct because stored procedures in Azure Cosmos DB for NoSQL execute within a transactional scope, enabling atomic read-modify-write operations across multiple document fields. When you need a computed property that depends on several fields, a stored procedure can read the current document, perform the server-side computation, and update the property—all as an all-or-nothing unit, ensuring consistency even under concurrent access. On the AZ-204 exam, this scenario tests your understanding of Cosmos DB’s server-side programming model and the limits of other options: pre-triggers lack transactional guarantees, change feeds are asynchronous, and UDFs are read-only. A common trap is choosing a UDF because it can compute values, but it cannot write back atomically. Memory tip: think “SP = Single Transaction” for atomic computed properties.
AZ-204 Practice Question: Connect to and consume Azure services and third-party services
This AZ-204 practice question tests your understanding of connect to and consume azure services and third-party services. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your application uses Azure Cosmos DB for NoSQL. You need to implement server-side computed properties that depend on multiple document fields. The computation must be performed atomically. Which approach should you use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a stored procedure to compute and update the property in a single transaction
Stored procedures in Azure Cosmos DB for NoSQL execute within a transactional scope, allowing you to atomically compute a property based on multiple document fields and update the document in a single operation. This ensures that the computation and update are performed as an all-or-nothing unit, which is required for atomicity. Pre-triggers, change feeds, and UDFs do not provide atomic read-modify-write semantics across multiple fields.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use a pre-trigger to compute the property on write
Why it's wrong here
Pre-triggers run before the write but are not guaranteed to be atomic with the write.
✗
Use the change feed to compute the property asynchronously
Why it's wrong here
Change feed is asynchronous and does not provide atomicity.
✗
Use a user-defined function (UDF) in queries
Why it's wrong here
UDFs are used in queries, not for atomic updates.
✓
Use a stored procedure to compute and update the property in a single transaction
Why this is correct
Stored procedures provide atomic transactional execution within a partition.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the atomic execution of a stored procedure with the eventual consistency of the change feed or the query-time computation of a UDF, failing to recognize that only stored procedures provide a transactional scope for read-modify-write operations on the same document.
Detailed technical explanation
How to think about this question
Stored procedures in Cosmos DB run within a server-side JavaScript environment and are executed as part of a transactional batch, leveraging the database's snapshot isolation to ensure consistency. Under the hood, the stored procedure receives a collection link and can perform multiple read and write operations on documents within the same partition, all committed or rolled back together. In real-world scenarios, this is critical for scenarios like maintaining a running balance in a financial document where the balance depends on multiple transaction fields.
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.
TExam Day Tips
→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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Connect to and consume Azure services and third-party services — This question tests Connect to and consume Azure services and third-party services — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a stored procedure to compute and update the property in a single transaction — Stored procedures in Azure Cosmos DB for NoSQL execute within a transactional scope, allowing you to atomically compute a property based on multiple document fields and update the document in a single operation. This ensures that the computation and update are performed as an all-or-nothing unit, which is required for atomicity. Pre-triggers, change feeds, and UDFs do not provide atomic read-modify-write semantics across multiple fields.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.