The answer is semi-structured. This classification is correct because JSON documents inherently support schema flexibility, allowing new optional fields like additional vital signs to be added without breaking existing records, while still maintaining organizational properties through key-value pairs such as PatientID and Timestamp. On the Microsoft Azure Data Fundamentals DP-900 exam, this question tests your ability to distinguish data types based on schema rigidity versus flexibility—a common trap is assuming any data with fields is structured, but the key differentiator is whether the schema is fixed (structured) or variable (semi-structured). Remember that JSON, XML, and Parquet are classic semi-structured formats because they are self-describing and allow schema evolution. A useful memory tip: if the schema can change between records, think “semi” for flexible structure, not “strict” like a relational table.
DP-900 Describe core data concepts Practice Question
This DP-900 practice question tests your understanding of describe core data concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 healthcare application stores patient vital signs readings. Each reading is a JSON document with fields: PatientID, Timestamp, HeartRate, BloodPressure (systolic and diastolic). The application frequently queries for all readings of a specific patient within a time range, and the schema varies occasionally (e.g., new optional fields are added). How should this data be classified?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Semi-structured
The data is semi-structured because it is stored as JSON documents, which have a flexible schema that can vary between records (e.g., new optional fields can be added). JSON documents are self-describing and do not require a fixed schema like relational tables, but they still have organizational properties (fields like PatientID, Timestamp) that distinguish them from unstructured data like plain text or images. The application's queries on specific fields (PatientID, Timestamp) further confirm the data has structure, but the schema flexibility rules out structured or relational classifications.
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.
✗
Structured
Why it's wrong here
Structured data follows a rigid schema (e.g., relational tables) and does not accommodate varying fields well.
✓
Semi-structured
Why this is correct
Semi-structured data uses tags or markers (like JSON) to separate data elements and allows schema flexibility.
Related concept
Read the scenario before looking for a memorised answer.
✗
Unstructured
Why it's wrong here
Unstructured data (e.g., plain text, images) has no predefined data model or structure.
✗
Relational
Why it's wrong here
Relational data is a specific type of structured data stored in tables with fixed schemas and relationships.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'structured' with 'having fields'—they see PatientID and Timestamp and assume it must be structured, but the key differentiator is schema flexibility (optional fields, varying structure) which defines semi-structured data.
Detailed technical explanation
How to think about this question
In Azure, this data would typically be stored in Azure Cosmos DB (using the SQL API) or Azure Blob Storage with JSON files, both of which natively support semi-structured data. The JSON format allows schema evolution without downtime—new fields can be added to some documents without affecting existing ones—which is critical for healthcare applications where regulatory changes may require new data points. Under the hood, Cosmos DB indexes every field in the JSON document by default, enabling efficient queries on PatientID and Timestamp even as the schema varies.
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.
Describe core data concepts — This question tests Describe core data concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Semi-structured — The data is semi-structured because it is stored as JSON documents, which have a flexible schema that can vary between records (e.g., new optional fields can be added). JSON documents are self-describing and do not require a fixed schema like relational tables, but they still have organizational properties (fields like PatientID, Timestamp) that distinguish them from unstructured data like plain text or images. The application's queries on specific fields (PatientID, Timestamp) further confirm the data has structure, but the schema flexibility rules out structured or relational classifications.
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.