The correct answer is Atomicity. This ACID property guarantees that a transaction in Azure SQL Database is treated as an indivisible unit of work, meaning if a single transaction updates both a patient’s insurance row and their treatment plan row, either both updates are committed together or both are rolled back entirely—never leaving the database with only one change applied. On the Microsoft Azure Data Fundamentals DP-900 exam, this concept tests your understanding of how Azure SQL Database ensures data consistency during multi-row operations; a common trap is confusing atomicity with consistency, which instead ensures data follows all rules and constraints after the transaction. To remember it, think of the word “atom”—just as an atom was once thought to be indivisible, atomicity means the transaction cannot be split: it’s all or nothing.
DP-900 Practice Question: Identify considerations for relational data on Azure
This DP-900 practice question tests your understanding of identify considerations for relational data on azure. 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.
A hospital uses Azure SQL Database to store patient records. The database contains tables for patient information, insurance details, and treatment plans. The system must ensure that if a transaction updates a patient's insurance and their treatment plan in two separate rows, either both updates succeed or both fail. Which ACID property guarantees this behavior?
Why wrong: Durability ensures that once a transaction is committed, it remains saved, even after a system failure. It does not handle partial failures within a transaction.
B
Consistency
Why wrong: Consistency ensures that transactions bring the database from one valid state to another, but it does not guarantee that all parts of a transaction complete together.
C
Isolation
Why wrong: Isolation ensures that concurrent transactions do not interfere with each other, but does not address the all-or-nothing requirement.
D
Atomicity
Atomicity guarantees that all operations within a transaction are completed successfully or none are applied, matching the requirement to update both rows or neither.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Atomicity
Atomicity ensures that a transaction is treated as a single, indivisible unit of work. In Azure SQL Database, if a transaction updates both the insurance and treatment plan rows, atomicity guarantees that either both updates are committed or both are rolled back, preventing partial updates that could leave data in an inconsistent state.
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.
✗
Durability
Why it's wrong here
Durability ensures that once a transaction is committed, it remains saved, even after a system failure. It does not handle partial failures within a transaction.
✗
Consistency
Why it's wrong here
Consistency ensures that transactions bring the database from one valid state to another, but it does not guarantee that all parts of a transaction complete together.
✗
Isolation
Why it's wrong here
Isolation ensures that concurrent transactions do not interfere with each other, but does not address the all-or-nothing requirement.
✓
Atomicity
Why this is correct
Atomicity guarantees that all operations within a transaction are completed successfully or none are applied, matching the requirement to update both rows or neither.
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 confuse atomicity with consistency, thinking that consistency alone ensures all-or-nothing updates, but consistency only enforces rules and constraints—it is atomicity that provides the rollback mechanism to prevent partial transactions.
Detailed technical explanation
How to think about this question
In Azure SQL Database, atomicity is implemented via the transaction log: before any change is written to the data pages, the log records the 'begin transaction' and each modification. If a failure occurs before the 'commit transaction' log record is written, the database engine uses the log to undo (roll back) all changes made by that transaction, ensuring no partial updates remain. This is critical in healthcare systems where a partial update could leave a patient with an insurance change but an outdated treatment plan, potentially causing billing or care errors.
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
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-900 question in full detail.
Identify considerations for relational data on Azure — This question tests Identify considerations for relational data on Azure — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Atomicity — Atomicity ensures that a transaction is treated as a single, indivisible unit of work. In Azure SQL Database, if a transaction updates both the insurance and treatment plan rows, atomicity guarantees that either both updates are committed or both are rolled back, preventing partial updates that could leave data in an inconsistent state.
What should I do if I get this DP-900 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 DP-900 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 DP-900 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.