DP-900 Describe core data concepts Practice Question
A company maintains a database of customer orders that are updated frequently. They also store aggregated monthly sales reports that are generated once and then only read. Which statement correctly distinguishes these two types of data workloads?
⚠ Common exam trap
Many candidates confuse the typical characteristics of OLTP and OLAP, mistakenly thinking analytical data requires real-time processing or that transactional data is read-only, when in fact the opposite is true for each.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Transactional data is optimized for write operations, and analytical data is optimized for read operations.
Transactional workloads (like the frequently updated customer orders) are optimized for write-heavy operations, ensuring ACID compliance and data integrity, while analytical workloads (like the read-only monthly sales reports) are optimized for read-heavy operations, often using columnar storage or pre-aggregated data to speed up queries. This distinction aligns with the core difference between OLTP (Online Transaction Processing) and OLAP (Online Analytical Processing) systems in Azure, such as Azure SQL Database for transactional data and Azure Synapse Analytics for analytical data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Transactional data is optimized for write operations, and analytical data is optimized for read operations.
Why this is correct
In OLTP systems, transactional data is workload-optimized for high-frequency write operations using row-based storage, normalization to minimize redundancy, and fast lookup indexes to support ACID-compliant record-level changes. In contrast, analytical data in OLAP systems is structured for complex read patterns, using columnar storage, denormalized schemas, and pre-aggregated measures to speed up queries across large volumes. This fundamental separation drives the design of data pipelines and database engines.
- ✗
Transactional data must always be stored in non-relational databases, and analytical data in relational databases.
Why it's wrong here
There is no architectural requirement that transactional data reside exclusively in non-relational databases or that analytical data be confined to relational systems. Relational databases such as SQL Server and PostgreSQL excel at transactional workloads with strong consistency, and many analytical platforms run on relational data warehouses like Azure Synapse or SQL Server columnstore. Conversely, NoSQL databases can support analytical use cases—for example, Azure Cosmos DB's analytical store or Cassandra-based time-series analytics. The actual choice depends on the data model, query patterns, latency, and consistency requirements rather than a hard categorization by workload type.
- ✗
Analytical data always requires real-time processing, whereas transactional data is batch-processed.
Why it's wrong here
Analytical workloads rarely require mandatory real-time processing; instead, they commonly rely on batch ETL/ELT jobs that refresh data warehouses nightly or hourly, and modern systems may incorporate streaming for near-real-time needs as an enhancement rather than a core requirement. Transactional workloads, however, are interactive and typically must process orders or account changes immediately, often in milliseconds to seconds. Confusing these patterns reverses the true scheduling priorities: OLTP demands low-latency writes, while OLAP is largely batch-oriented with occasional incremental loads.
- ✗
Transactional data is read-only and analytical data is frequently updated.
Why it's wrong here
Transactional data is inherently mutable: order records are frequently created, updated, and even deleted as the business operates, and the database must support these changes while preserving data integrity. Analytical data, after being transformed and loaded into a warehouse, is almost never modified; only new data is appended, making it effectively read-only for reporting and BI queries. This wrong statement flips the actual characteristic: it is analytical data that is typically read-only and append-only, not transactional data.
Go deeper
Related to this question
Learn chapter
Data Roles and Core Concepts
Key term
Transactional data
Transactional data is information that captures a specific event or exchange, such as a sale, a payment, or a system log entry, and is recorded in a database or log system.
Key term
Azure Synapse Analytics
Azure Synapse Analytics is a cloud-based data integration, warehousing, and analytics service that brings together big data and data warehouse capabilities under one platform.
About these practice questions
Courseiva writes every DP-900 question from scratch — 820 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.