CCNA Describe core data concepts Questions — Page 2 of 4

MCQmedium

A data engineer needs to load 500 GB of CSV files from an on-premises server into Azure Data Lake Storage Gen2 daily. The data must be transferred securely over the internet. Which Azure tool should they use?

A.Azure Data Factory

B.Azure PowerShell

C.Azure Import/Export service

D.AzCopy

AnswerD

AzCopy is a dedicated command-line utility engineered specifically for high-performance, resumable copying between on-premises storage and Azure Blob Storage or Azure Files. It automatically partitions files, spawns multiple concurrent connections to maximize throughput, validates data integrity with checksums, and can resume from a checkpoint if a transfer is interrupted. For moving 500 GB of CSVs, AzCopy provides the simplest and most efficient online solution with one command such as azcopy copy.

Why this answer

AzCopy is the correct tool because it is a command-line utility designed for high-performance, secure copying of data to and from Azure Blob Storage and Azure Data Lake Storage Gen2. It supports the required 500 GB daily transfer over the internet using HTTPS encryption, and can be scripted for automation without the overhead of a full orchestration service.

Exam trap

The trap here is that candidates often confuse Azure Data Factory as the default tool for any data movement, overlooking that AzCopy is the lightweight, purpose-built utility for direct, scriptable bulk transfers without orchestration overhead.

How to eliminate wrong answers

Option A is wrong because Azure Data Factory is a cloud-based ETL and data orchestration service, not a direct data transfer tool; it adds unnecessary complexity and cost for a simple bulk copy task, and is not optimized for single-shot, high-volume transfers like AzCopy. Option B is wrong because Azure PowerShell is a scripting environment for managing Azure resources, not a dedicated data transfer tool; it lacks the parallelization and resume capabilities needed for efficient 500 GB file transfers. Option C is wrong because Azure Import/Export service is designed for physical shipment of hard drives to Azure datacenters, not for transferring data over the internet; it is intended for very large datasets (terabytes to petabytes) where network transfer is impractical.

Practice this question →

MCQmedium

Your organization uses Azure Cosmos DB for a real-time inventory application. The data includes a container with items that have a `category` property. The operations team frequently queries for all items in a specific category. To optimize query performance and minimize request unit (RU) consumption, you decide to implement a materialized view. Which Azure Cosmos DB feature should you use to achieve this?

A.Partition key design

B.Change feed

C.Composite indexes

D.Materialized views (preview)

AnswerD

Materialized views (preview) in Azure Cosmos DB are the correct feature because they let you define a view as a query over a source container, and the service automatically maintains a separate, denormalized container with the query results. This view is updated incrementally when source data changes and is optimized for read-heavy or common-query scenarios, reducing latency and cost. By pre-computing and storing the results, materialized views directly fulfill the requirement for a built-in, automatically refreshed mechanism.

Why this answer

Azure Cosmos DB's materialized views (preview) feature allows you to pre-join, aggregate, and transform data from a source container into a separate container optimized for specific query patterns, such as filtering by `category`. This reduces RU consumption by avoiding full scans or expensive cross-partition queries, as the view is pre-computed and indexed according to the target query.

Exam trap

The trap here is that candidates confuse the change feed (a reactive stream of changes) with materialized views (a persisted, queryable snapshot), or assume that composite indexes alone can achieve the same pre-computation benefits as a materialized view.

How to eliminate wrong answers

Option A is wrong because partition key design distributes data across physical partitions for scalability and write performance, but it does not create a pre-computed, denormalized copy of data optimized for a specific query pattern; a poorly chosen partition key can even increase RU costs for queries. Option B is wrong because the change feed is a mechanism to capture incremental changes (inserts, updates, deletes) to items in a container, enabling event-driven processing or replication, but it does not itself provide a query-optimized, persisted view of the data. Option C is wrong because composite indexes improve query performance by indexing multiple properties in a specific order, but they do not create a separate, pre-materialized dataset; they still require the query engine to scan indexed data at query time, which may not be as efficient as a materialized view for frequent aggregation or filtering.

Practice this question →

MCQeasy

A company stores customer data in a relational table with columns CustomerID, FullName, and Email. They also store product descriptions as JSON documents with varying fields, and product images as JPEG files. Which of the following correctly classifies these data types from most structured to least structured?

A.Structured, semi-structured, unstructured

B.Unstructured, semi-structured, structured

C.Semi-structured, structured, unstructured

D.Structured, unstructured, semi-structured

AnswerA

Correct. A relational table is fully structured because it enforces a fixed schema: predefined columns, data types, and constraints that make every row uniformly queryable. JSON is semi-structured because it uses flexible key-value pairs and nesting that organize data but do not require the same rigid schema. JPEG images are unstructured because their binary pixel encoding has no inherent schema or fields that a database can query directly, so the correct order is structured, semi-structured, unstructured.

Why this answer

The customer data in a relational table with fixed columns (CustomerID, FullName, Email) is structured because it has a rigid schema and defined data types. The JSON documents for product descriptions are semi-structured because they use key-value pairs with flexible fields but still have metadata (tags, keys) that provide organization. The JPEG product images are unstructured because they are binary blobs with no inherent schema or metadata that the database can query directly.

This ordering from most to least structured matches option A.

Exam trap

The trap here is that candidates often confuse semi-structured (JSON) with unstructured (JPEG) because both lack a fixed schema, but JSON has inherent key-value structure that databases can query, whereas JPEG is purely binary with no queryable structure.

Why the other options are wrong

This option orders data types from unstructured to semi-structured to structured, but the question asks for most structured to least structured. Customer data in a relational table is structured, JSON documents are semi-structured, and JPEG images are unstructured, so the correct order is structured, semi-structured, unstructured.

Option C orders semi-structured before structured, but the relational table (structured) is more organized than JSON documents (semi-structured). The correct order from most to least structured is structured, semi-structured, unstructured.

Option D orders structured (relational table) first, then unstructured (JPEG images), then semi-structured (JSON documents). This is incorrect because JSON documents are semi-structured, not unstructured, and they are more structured than JPEG files.

Practice this question →

MCQeasy

Refer to the exhibit. You are designing a fact table for a data warehouse. The table will store sales transactions with daily granularity. Which column would be most appropriate as the distribution column in a hash-distributed table in Azure Synapse Analytics?

A.SalesAmount

B.CustomerKey

C.ProductKey

D.OrderDate

AnswerB

CustomerKey has high cardinality and is frequently used in joins, making it a good distribution column. Each customer has many sales transactions, so hashing on CustomerKey spreads rows evenly across distributions and reduces data skew. In Azure Synapse dedicated SQL pool, this also enables collocated joins with the customer dimension, minimizing data movement during queries.

Why this answer

CustomerKey (B) is the most appropriate distribution column because it has high cardinality and is frequently used in joins with dimension tables, ensuring data is evenly distributed across distributions in Azure Synapse Analytics. A hash-distributed table requires a column with many unique values to avoid data skew, and CustomerKey is a natural key for sales transactions that meets this requirement.

Exam trap

Microsoft often tests the misconception that any column with high cardinality is suitable for hash distribution, but the trap here is that the column must also be frequently used in joins and evenly distribute data, not just have many unique values.

How to eliminate wrong answers

Option A (SalesAmount) is wrong because it is a measure column with continuous values that would cause data skew and poor query performance due to uneven distribution. Option C (ProductKey) is wrong because while it has high cardinality, it is less frequently used in join operations compared to CustomerKey, and using it may lead to suboptimal distribution for common sales analysis queries. Option D (OrderDate) is wrong because it has low cardinality (only 365 distinct values per year) and would cause severe data skew, as all transactions on the same date would hash to the same distribution, leading to hot spots and degraded performance.

Practice this question →

MCQeasy

A company receives customer order data from its online store in a CSV file. Each line contains fields like OrderID, CustomerName, Product, Quantity, and OrderDate. This data is best described as:

A.Structured data

B.Semi-structured data

C.Unstructured data

D.Transactional data

AnswerA

Structured data is the correct classification because the CSV order file has a predefined tabular schema: a header row defines fixed column names and each subsequent row represents one order with values aligned to those columns. Because every record follows the same field order and logical data types, it can be loaded directly into a relational table and queried with SQL, which are the hallmarks of structured data.

Why this answer

A is correct because the CSV file contains data that conforms to a strict tabular schema with predefined columns (OrderID, CustomerName, Product, Quantity, OrderDate) and consistent data types per column. This rigid, row-and-column format with a fixed schema is the defining characteristic of structured data, which can be directly loaded into a relational database or Azure SQL Database without transformation.

Exam trap

The trap here is that candidates confuse 'transactional data' (a workload type) with 'structured data' (a format classification), leading them to pick D because the data describes orders, even though the question explicitly asks about the data's format, not its business purpose.

How to eliminate wrong answers

Option B is wrong because semi-structured data (e.g., JSON, XML, Parquet) allows flexible schema variations, such as missing fields or nested structures, whereas CSV enforces a fixed number of columns per row and a consistent order. Option C is wrong because unstructured data (e.g., text files, images, videos) has no predefined schema or organization, while CSV has a clear row/column structure. Option D is wrong because transactional data refers to a type of workload (OLTP) that records business transactions, not a data format classification; the CSV file itself is a structured data format regardless of whether it contains transactional records.

Practice this question →

MCQeasy

A company wants to store JSON documents that need to be queried with high throughput and low latency globally. Which Azure data service is most appropriate?

A.Azure Table Storage

B.Azure Cosmos DB

C.Azure SQL Database

D.Azure Blob Storage

AnswerB

Azure Cosmos DB is a fully managed NoSQL database explicitly built for JSON documents, offering native JSON support with automatic indexing of all properties. It provides guaranteed low latency (single-digit milliseconds) at any scale, coupled with turnkey global distribution across multiple Azure regions, enabling active-active configurations. Its SQL API allows rich querying over JSON documents using familiar syntax, and it supports multiple consistency models to balance performance and data correctness. This makes it the optimal choice for storing and querying JSON documents with global reach.

Why this answer

Azure Cosmos DB is the most appropriate service because it is a globally distributed, multi-model database that natively supports JSON documents and provides guaranteed single-digit-millisecond latency at the 99th percentile, along with high throughput via configurable request units (RUs). Its turnkey global distribution enables low-latency reads and writes across multiple Azure regions, making it ideal for globally queried JSON workloads.

Exam trap

The trap here is that candidates confuse Azure Table Storage's key-value model with JSON document support, or assume Azure SQL Database's JSON functions make it suitable for globally distributed, high-throughput JSON workloads, missing Cosmos DB's core differentiator of turnkey global distribution and guaranteed low latency.

How to eliminate wrong answers

Option A is wrong because Azure Table Storage is a NoSQL key-value store that stores data in entity/partition structures, not native JSON documents, and it lacks global distribution with guaranteed low-latency SLAs. Option C is wrong because Azure SQL Database is a relational database that stores data in tables with a fixed schema, not as native JSON documents, and while it supports JSON functions, it is not designed for globally distributed, high-throughput JSON queries with multi-region write capabilities. Option D is wrong because Azure Blob Storage is an object storage service for unstructured binary data, not a queryable database; it cannot natively query JSON documents with low latency and high throughput.

Practice this question →

Matchingmedium

Match each Azure data migration tool to its use case.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Migrate databases to Azure with minimal downtime

Copy blobs or files to/from Azure Storage

Offline data transfer for large datasets

Ship physical disks to Azure datacenter

Orchestrate data movement and transformation

Why these pairings

Azure Migrate is for server assessment, Azure Database Migration Service is for database migration, and Azure Data Box is for offline data transfer. Common confusions involve swapping assessment and migration roles.

Practice this question →

MCQhard

A financial analytics company has two distinct data processing workloads. The first workload ingests real-time stock trade data from a message queue, calculates moving averages every minute, and updates a dashboard for traders. The second workload receives daily CSV files containing end-of-day trade summaries, transforms them using Python scripts, and loads the results into a data warehouse for monthly reporting. Which statement correctly characterizes these workloads?

A.First workload: Stream processing, Second workload: Batch processing

B.First workload: Batch processing, Second workload: Stream processing

C.First workload: OLTP, Second workload: OLAP

D.First workload: Transactional processing, Second workload: Analytical processing

AnswerA

This is correct because the first workload requires continuous, low-latency computation over an unbounded sequence of stock trade events; calculating moving averages demands real-time windowing and stateful aggregation as each event arrives, which is the defining characteristic of stream processing (e.g., Apache Kafka, Azure Stream Analytics). The second workload processes a finite, already-completed CSV file generated at end of day, a classic batch job executed on a schedule with high throughput and no requirement for sub-second latency; this distinguishes it as batch processing (e.g., Azure Data Factory, Azure Databricks).

Why this answer

The first workload processes real-time stock trade data from a message queue and calculates moving averages every minute, which is a classic stream processing pattern (continuous, low-latency data ingestion and computation). The second workload handles daily CSV files with end-of-day summaries, transforms them with Python scripts, and loads results into a data warehouse for monthly reporting, which is a classic batch processing pattern (scheduled, high-latency processing of bounded data sets).

Exam trap

The trap here is that candidates confuse 'real-time' with 'transactional processing' (OLTP) or 'analytical processing' (OLAP), when the correct distinction is between stream processing (continuous, low-latency) and batch processing (scheduled, high-latency).

How to eliminate wrong answers

Option B is wrong because it reverses the definitions: the first workload is clearly stream processing (real-time, message queue), not batch processing, and the second workload is batch processing (daily files, scheduled transformation), not stream processing. Option C is wrong because OLTP (Online Transaction Processing) refers to systems that handle high-volume, low-latency transactions (e.g., order entry), not real-time analytics; the first workload is stream processing, not OLTP. Option D is wrong because 'transactional processing' is synonymous with OLTP, not stream processing, and 'analytical processing' is synonymous with OLAP, not batch processing; the first workload is stream processing, and the second is batch processing.

Practice this question →

MCQmedium

Your organization uses Microsoft Fabric to build a data lakehouse. Data engineers need to transform data using Spark and store results in Delta Lake format. Which Fabric component should they use?

A.Dataflows Gen2

B.Pipelines

C.Notebooks

D.Semantic models

AnswerC

Notebooks in Microsoft Fabric are the recommended code-based interface for working with Apache Spark, and they natively support popular languages like Python, Scala, and SQL. They can read raw data from files, apply transformations, and write results to Delta Lake tables within a lakehouse, leveraging ACID transactions and efficient upserts. Because the scenario explicitly calls for Spark and building a data lake, notebooks are the correct tool for executing event-driven or ad-hoc transformation logic directly on the compute engine.

Why this answer

Notebooks in Microsoft Fabric provide an interactive environment for writing and executing Spark code, which is required for transforming data using Spark. The results can be directly written to Delta Lake format, making Notebooks the correct component for this task.

Exam trap

The trap here is that candidates may confuse Pipelines (which orchestrate activities) with the actual compute engine (Notebooks) that runs Spark transformations, leading them to select Pipelines as the component for executing Spark code.

How to eliminate wrong answers

Option A is wrong because Dataflows Gen2 are used for low-code data transformation using Power Query, not for running Spark code. Option B is wrong because Pipelines are used for orchestrating and scheduling data movement and transformation activities, but they do not execute Spark transformations themselves. Option D is wrong because Semantic models are used for defining business logic and measures for reporting in Power BI, not for data transformation or Spark execution.

Practice this question →

MCQmedium

You need to design a data storage solution for a global e-commerce application that must support ACID transactions and require minimal latency for point lookups by a unique key. Which Azure data service should you use?

A.Azure Table Storage

B.Azure SQL Database

C.Azure Blob Storage

D.Azure Cosmos DB

AnswerD

Azure Cosmos DB is a globally distributed, multi-model NoSQL database that offers turnkey distribution across any number of Azure regions, multi-region write support, and single-digit millisecond read and write latencies at the 99th percentile. It also guarantees ACID transactions within a single logical partition using transactional batches or stored procedures, making it the right fit for a global e-commerce platform that needs both low-latency point lookups and data consistency.

Why this answer

Azure Cosmos DB is the correct choice because it provides global distribution with multi-region writes, guarantees ACID transactions through its transactional batch API, and offers single-digit millisecond latency for point reads by a unique key (e.g., id and partition key). This makes it ideal for a global e-commerce application requiring both strong consistency and low-latency lookups.

Exam trap

The trap here is that candidates often assume Azure SQL Database is the only ACID-compliant option, overlooking Cosmos DB's transactional batch support and its superior global low-latency capabilities.

How to eliminate wrong answers

Option A is wrong because Azure Table Storage does not support ACID transactions (it only offers entity-level atomicity) and has higher latency for point lookups compared to Cosmos DB. Option B is wrong because Azure SQL Database, while fully ACID-compliant, is not designed for global distribution with minimal latency; it requires read replicas and manual failover, and its point lookup latency is higher than Cosmos DB's single-digit millisecond SLA. Option C is wrong because Azure Blob Storage is an object store for unstructured data, does not support ACID transactions, and point lookups by unique key are not its primary access pattern (it uses HTTP-based REST operations with higher latency).

Practice this question →

MCQmedium

A team is designing a data pipeline to process streaming sensor data from IoT devices. The data must be ingested, transformed in real time, and stored in a time-series database. Which combination of Azure services should they use?

A.Azure IoT Hub, Azure Data Lake Storage, and Azure Databricks

B.Azure IoT Hub, Azure Stream Analytics, and Azure Data Explorer

C.Azure Event Hubs, Azure Functions, and Azure SQL Database

D.Azure Event Hubs, Azure Synapse Pipelines, and Azure Cosmos DB

AnswerB

IoT Hub ingests device data, Stream Analytics performs real-time transformations, and Data Explorer is a time-series database for fast analytics.

Why this answer

Azure IoT Hub ingests streaming sensor data from IoT devices, Azure Stream Analytics provides real-time transformation and analysis of the data streams, and Azure Data Explorer (ADX) is a fully managed time-series database optimized for high-velocity telemetry data. This combination directly addresses the requirement for ingestion, real-time transformation, and time-series storage.

Exam trap

The trap here is that candidates often confuse Azure Data Explorer with Azure Data Lake Storage or Azure SQL Database, assuming any storage service can handle time-series data, but ADX is the only Azure service purpose-built for high-ingestion-rate time-series analytics with features like materialized views and data sharding.

How to eliminate wrong answers

Option A is wrong because Azure Data Lake Storage is a hierarchical file store for batch/analytics, not a time-series database, and Azure Databricks is primarily for batch and interactive analytics, not real-time stream processing with low-latency time-series storage. Option C is wrong because Azure SQL Database is a relational OLTP database not optimized for time-series workloads, and Azure Functions is event-driven compute, not a dedicated stream processing service for real-time transformations. Option D is wrong because Azure Synapse Pipelines is an orchestration tool for data movement and transformation, not real-time stream processing, and Azure Cosmos DB is a multi-model NoSQL database that lacks native time-series optimizations like automatic retention policies and downsampling.

Practice this question →

MCQeasy

A retail company stores customer transaction data in a relational database. Each transaction is recorded with a fixed schema including TransactionID, CustomerID, ProductID, Quantity, and TotalAmount. Which type of data does this represent?

A.Unstructured data

B.Semi-structured data

C.Structured data

D.Binary data

AnswerC

Structured data conforms to a predefined schema, typically organized into rows and columns within a relational database. The transaction dataset with named columns (e.g., TransactionID, CustomerID, ProductID, Quantity, TotalAmount) and consistent data types fits this model exactly. This structure enables efficient SQL querying, indexing, and transactional integrity, making it the correct classification for customer transaction data.

Why this answer

The data conforms to a fixed schema with defined columns (TransactionID, CustomerID, ProductID, Quantity, TotalAmount) and data types, which is the defining characteristic of structured data. In a relational database, this schema enforces consistency and allows for efficient querying using SQL, making it a classic example of structured data.

Exam trap

The trap here is that candidates may confuse 'structured data' with 'semi-structured data' because both have some organization, but the key differentiator is the rigid, predefined schema enforced by the relational database versus the flexible, self-describing schema of semi-structured formats like JSON or XML.

How to eliminate wrong answers

Option A is wrong because unstructured data has no predefined schema or organization (e.g., text files, images, videos), whereas this data has a fixed schema. Option B is wrong because semi-structured data has some organizational properties but does not conform to a rigid schema (e.g., JSON, XML with flexible tags), while this data uses a strict relational schema. Option D is wrong because binary data refers to raw byte sequences (e.g., executable files, images), not tabular data with typed columns.

Practice this question →

MCQhard

Your company, Contoso Ltd., operates a global e-commerce platform. The data engineering team ingests over 10 TB of raw clickstream data daily into Azure Data Lake Storage Gen2. The data is partitioned by date and hour. Business analysts need to query this data using Azure Synapse Serverless SQL to generate daily sales reports. However, the reports are taking over 30 minutes to run, and the team needs to improve query performance without moving data to a dedicated SQL pool. You are asked to recommend a solution. Which action should you take?

A.Convert the data from JSON to Parquet format and apply Snappy compression.

B.Use Azure Data Factory to copy the data into Azure SQL Database and create indexes.

C.Create a dedicated SQL pool and distribute the data across 60 distributions.

D.Create external tables using a partition elimination strategy and ensure the data is partitioned by date.

AnswerD

Creating external tables with a partition elimination strategy and partitioning the data by date lets the serverless SQL engine skip whole file ranges that do not satisfy the query's predicate, for example when a WHERE clause filters on a date column. You should store the data in a hive-style layout such as /orders/year=2024/month=03 and define the external table so the engine can map the folders to partition columns. This reduces the byte count scanned dramatically and is the biggest lever for performance and cost in a serverless SQL pool.

Why this answer

Azure Synapse Serverless SQL can use external tables with partition elimination to skip irrelevant partitions (e.g., date/hour folders) during query execution. This reduces the amount of data scanned, directly improving query performance without moving data. Partition elimination works by filtering on the partition column (e.g., date) in the WHERE clause, allowing the query engine to read only the necessary files.

Exam trap

The trap here is that candidates often assume converting file format (Parquet) alone is sufficient, but the question specifically targets reducing data scanned via partition elimination, which is a more direct optimization for partitioned data in serverless SQL.

How to eliminate wrong answers

Option A is wrong because while converting to Parquet with Snappy compression can improve performance, it does not address the root cause of scanning all 10 TB daily; partition elimination is more impactful for reducing data scanned. Option B is wrong because copying data to Azure SQL Database defeats the requirement of not moving data to a dedicated SQL pool, and it introduces additional cost and latency. Option C is wrong because creating a dedicated SQL pool explicitly violates the requirement to not move data to a dedicated SQL pool; it also involves provisioning and managing separate compute resources.

Practice this question →

MCQhard

Your team uses Azure SQL Database and wants to implement row-level security (RLS) to restrict access to sales data by region. Which type of data workload characteristic does RLS primarily address?

A.Concurrency

B.Consistency

C.Security

D.Durability

AnswerC

Row-level security is a native security capability that limits row access through an inline table-valued predicate function and a security policy. It can use SESSION_CONTEXT or user identity to return only authorized rows, protecting sensitive data without requiring application-layer WHERE clauses. Thus Security is the correct category for this feature.

Why this answer

Row-level security (RLS) in Azure SQL Database restricts data access at the database engine level by applying a security predicate that filters rows based on user attributes, such as region. This directly addresses the security characteristic of a data workload by ensuring that users can only see data they are authorized to view, without requiring application-level changes.

Exam trap

The trap here is that candidates confuse security (access control) with concurrency (multi-user access) or consistency (data integrity), because RLS involves filtering rows during queries, which might superficially resemble managing concurrent access or ensuring data correctness.

How to eliminate wrong answers

Option A is wrong because concurrency refers to the ability of multiple users to access data simultaneously without conflicts, which is managed by locking and isolation levels, not by row-level filtering. Option B is wrong because consistency ensures that data remains accurate and valid across transactions (e.g., via ACID properties), whereas RLS does not enforce data integrity rules. Option D is wrong because durability guarantees that committed transactions persist even after a system failure, typically achieved through transaction logs and backups, not through access control predicates.

Practice this question →

MCQeasy

A company stores an employee database in a relational database. The Employees table includes columns: EmployeeID (integer), FirstName (text), LastName (text), HireDate (date), and a column called Photo which stores the employee's photo as a binary large object (BLOB). Which statement best describes the data types in this table?

A.All columns store structured data.

B.The Photo column stores unstructured data, while the other columns store structured data.

C.All columns store unstructured data.

D.The HireDate column stores semi-structured data.

AnswerB

Structured data is organized with a fixed schema; the integer, text, and date columns all have a fixed type and format. The Photo column contains binary image data with no inherent structure, making it unstructured data.

Why this answer

The Photo column stores a binary large object (BLOB), which is unstructured data because it does not have a predefined schema or format that can be easily queried or indexed by relational operations. In contrast, EmployeeID, FirstName, LastName, and HireDate are all structured data types (integer, text, date) that conform to a fixed schema and support direct querying, sorting, and indexing. This distinction is fundamental in Azure data services, where structured data is typically stored in Azure SQL Database or Azure Synapse, while unstructured BLOBs are better suited for Azure Blob Storage.

Exam trap

The trap here is that candidates may assume all columns in a relational database are structured, overlooking that BLOB columns store unstructured binary data, which is a key distinction tested in the DP-900 exam under core data concepts.

How to eliminate wrong answers

Option A is wrong because it claims all columns store structured data, but the Photo column as a BLOB is unstructured binary data without a fixed schema. Option C is wrong because it states all columns store unstructured data, but EmployeeID, FirstName, LastName, and HireDate have explicit data types (integer, text, date) that are structured and schema-bound. Option D is wrong because the HireDate column stores a date value, which is structured data, not semi-structured data (semi-structured data would be something like JSON or XML with flexible schema).

Practice this question →

Multi-Selectmedium

Which THREE are characteristics of structured data? (Choose three.)

Select 3 answers

A.Has a predefined schema

B.Consists of audio and video files

C.Uses JSON or XML format

D.Stored in relational databases

E.Organized in rows and columns

AnswersA, D, E

Structured data relies on a predefined schema, meaning the logical model—including column names, data types, and integrity constraints—is designed before any data is written. This schema-on-write approach enforces consistency and validity at ingest time, allowing databases to optimize indexes, partitions, and query plans. Because the schema is fixed, every record must conform, which makes structured data highly predictable and reliably queryable.

Why this answer

Structured data has a predefined schema, meaning the data types, relationships, and constraints are defined before data is entered. This schema ensures consistency and enables efficient querying, which is why relational databases enforce a fixed schema through table definitions and constraints like primary keys and foreign keys.

Exam trap

The trap here is that candidates confuse semi-structured formats like JSON and XML with structured data, but structured data requires a rigid schema enforced by the database, not just a self-describing format.

Practice this question →

MCQeasy

A company stores customer information in a SQL database table with columns: CustomerID, FirstName, LastName, Email, SignupDate. They also store product images as JPEG files in Azure Blob Storage. Which statement correctly describes the types of data involved?

A.Customer data is unstructured, product images are semi-structured.

B.Customer data is structured, product images are unstructured.

C.Both are structured.

D.Customer data is semi-structured, product images are unstructured.

AnswerB

This is correct. Customer data lives in relational tables where each row is a record and each column has a fixed data type, giving it a strict schema and making it fully structured. Product images, such as JPEG files, contain encoded pixel data with no inherent row/column structure and cannot be directly queried with SQL; they are stored as binary blobs and are classified as unstructured data.

Why this answer

Customer data stored in a SQL database table with defined columns (CustomerID, FirstName, LastName, Email, SignupDate) is structured because it adheres to a fixed schema with rows and columns. Product images stored as JPEG files in Azure Blob Storage are unstructured because they lack a predefined data model and are stored as binary large objects (BLOBs) without a schema. Option B correctly identifies this distinction.

Exam trap

The trap here is confusing 'unstructured' with 'semi-structured' — candidates often misclassify JPEG images as semi-structured because they have metadata (e.g., EXIF), but the data itself (pixel values) has no schema, making it unstructured, while semi-structured data like JSON has a self-describing structure.

How to eliminate wrong answers

Option A is wrong because customer data in a SQL table is structured, not unstructured, and product images are unstructured, not semi-structured. Option C is wrong because product images are unstructured, not structured; only the customer data is structured. Option D is wrong because customer data is structured, not semi-structured; semi-structured data (e.g., JSON, XML) has tags or markers but no rigid schema, whereas a SQL table has a fixed schema.

Practice this question →

MCQhard

You are implementing a data pipeline that ingests millions of events per second from IoT devices. The pipeline must tolerate failures and guarantee exactly-once processing. Which Azure service should you use to ingest the events?

A.Azure IoT Hub

B.Azure Event Hubs

C.Azure Service Bus

D.Azure Queue Storage

AnswerB

Azure Event Hubs is a fully managed event streaming platform built for high-throughput telemetry, capable of ingesting millions of events per second across partitioned consumer groups. It supports checkpointing to track processing progress, allowing at-least-once delivery that, when combined with idempotent consumers, enables effectively exactly-once processing. Its design as a distributed log with sequential writes and parallel reads makes it the right choice for massive ingestion workloads.

Why this answer

Azure Event Hubs is the correct choice because it is a big data streaming platform and event ingestion service designed for high-throughput scenarios, capable of ingesting millions of events per second. It supports exactly-once processing through checkpointing and partition-based offset management, and its built-in replication and availability zones provide fault tolerance.

Exam trap

The trap here is that candidates confuse Azure IoT Hub with Event Hubs because both handle IoT data, but IoT Hub is for device management and control, not for high-throughput event ingestion with exactly-once guarantees.

How to eliminate wrong answers

Option A is wrong because Azure IoT Hub is optimized for device management and bi-directional communication with IoT devices, not for high-throughput event ingestion at millions of events per second; it has lower throughput limits and is not designed for exactly-once processing at that scale. Option C is wrong because Azure Service Bus is a message broker for enterprise messaging with features like topics and queues, but it is not built for high-throughput event streaming and has lower throughput ceilings, making it unsuitable for millions of events per second. Option D is wrong because Azure Queue Storage is a simple message queue for decoupling application components with at-least-once delivery semantics and limited throughput, not supporting exactly-once processing or the high ingestion rates required.

Practice this question →

MCQmedium

Refer to the exhibit. A data engineer needs to query the orders.csv file using Azure Synapse Serverless SQL. What is the most efficient way to access this data?

A.Use PolyBase to create external table

B.Use OPENROWSET in Serverless SQL

C.Copy data to Azure SQL Database using ADF

D.Load data into a dedicated SQL pool

AnswerB

OPENROWSET is a T-SQL function available in the built-in serverless SQL endpoint that reads files directly from Azure Data Lake or Blob storage without loading them into a database. You can query CSV, Parquet, JSON, and Delta Lake files by specifying a path and optional WITH clause for schema; the engine processes only the requested data and you pay only for the data scanned. This is the optimal choice for an ad-hoc query because no compute pool, external table, or pipeline must be provisioned beforehand.

Why this answer

Azure Synapse Serverless SQL is designed for on-demand querying of data stored in data lakes without provisioning storage. The OPENROWSET function with the BULK option allows direct querying of CSV files using T-SQL, making it the most efficient method for ad-hoc analysis of the orders.csv file without data movement or schema management.

Exam trap

The trap here is that candidates often confuse PolyBase (which is for dedicated SQL pools) with Serverless SQL's OPENROWSET, or assume that data must be moved to a database before querying, missing the serverless paradigm of query-in-place.

How to eliminate wrong answers

Option A is wrong because PolyBase is used to create external tables in dedicated SQL pools, not in Serverless SQL, and requires defining external data sources and file formats, adding unnecessary overhead for a simple query. Option C is wrong because copying data to Azure SQL Database using ADF involves data movement and additional costs, which is inefficient for a one-time or ad-hoc query. Option D is wrong because loading data into a dedicated SQL pool requires provisioning and managing a dedicated resource, which is overkill and costly for querying a single CSV file.

Practice this question →

MCQeasy

A healthcare organization stores patient records in a relational database table with fixed columns for PatientID, Name, and DateOfBirth. Additionally, they store clinical notes as free-form text files for each patient visit. Which statement correctly classifies these data types?

A.Both patient records and clinical notes are examples of unstructured data.

B.Patient records are structured data, and clinical notes are unstructured data.

C.Both patient records and clinical notes are examples of structured data.

D.Patient records are unstructured data, and clinical notes are semi-structured data.

AnswerB

Patient records are structured because the relational model imposes a predetermined schema: each row is a record, each column is an attribute with a defined data type, and relationships are enforced via keys. Clinical notes are unstructured because they are free-form natural language—physicians type observations, diagnoses, and treatment plans with no fixed length, order, or columnar organization. This distinction is fundamental to choosing appropriate storage and analytics tools.

Why this answer

Patient records stored in a relational database table with fixed columns (PatientID, Name, DateOfBirth) conform to a predefined schema, making them structured data. Clinical notes stored as free-form text files lack a fixed schema or organization, which classifies them as unstructured data. Option B correctly identifies this distinction.

Exam trap

The trap here is that candidates confuse 'free-form text' with semi-structured data (e.g., JSON or XML), but semi-structured data has tags or key-value pairs, whereas free-form text has no inherent structure at all.

Why the other options are wrong

Patient records with fixed columns (PatientID, Name, DateOfBirth) are structured data, not unstructured. Clinical notes as free-form text files are unstructured, but the option incorrectly classifies both as unstructured.

Clinical notes are free-form text files without a predefined schema, making them unstructured data, not structured.

Patient records with fixed columns (PatientID, Name, DateOfBirth) are structured data, not unstructured. Clinical notes as free-form text are unstructured, not semi-structured.

Practice this question →

MCQeasy

A company processes sales transactions in real-time from a retail website. Each transaction is recorded as a row in a relational database. Additionally, the company stores weekly sales reports as PDF files. Which statement correctly describes these data types?

A.Transactions are unstructured, reports are semi-structured.

B.Transactions are structured, reports are unstructured.

C.Both are structured because they are files.

D.Both are unstructured because they are digital.

AnswerB

Correct. Transactions have a rigid schema (structured), and PDF files lack a predefined schema (unstructured).

Why this answer

Transactions are structured because they are stored as rows in a relational database, which imposes a fixed schema with defined columns and data types. Weekly sales reports as PDF files are unstructured because they lack a predefined data model and cannot be easily queried using SQL without additional processing. Option B correctly identifies this distinction.

Exam trap

The trap here is that candidates confuse 'file format' with 'data structure', assuming all files are structured, when in fact PDFs are unstructured binary files that lack the row/column schema of relational data.

How to eliminate wrong answers

Option A is wrong because it reverses the definitions: transactions are structured (not unstructured) and reports are unstructured (not semi-structured). Option C is wrong because not all files are structured; PDF files are binary blobs without a row/column schema, unlike relational database tables. Option D is wrong because being digital does not imply unstructured; structured data like relational tables is also digital but has a rigid schema.

Practice this question →

MCQmedium

You need to choose a data store for a mobile app that requires real-time synchronization of user preferences across devices. The data is small per user and key-value oriented. Which Azure service is most appropriate?

A.Azure Cosmos DB

B.Azure Cache for Redis

C.Azure Blob Storage

D.Azure SQL Database

AnswerA

Azure Cosmos DB is correct because it is a globally distributed, multi-model NoSQL database that provides a key-value API along with single-digit-millisecond read and write latency, which directly satisfies a mobile app's need for fast, scalable access. It also offers SDKs for iOS and Android, turnkey global distribution, and multiple consistency levels, enabling low-latency access from any region and supporting offline or sync-based scenarios.

Why this answer

Azure Cosmos DB is the most appropriate choice because it provides global distribution, low-latency reads and writes, and automatic conflict resolution, which are essential for real-time synchronization of user preferences across devices. Its key-value API (e.g., Table API or Core SQL API with a simple partition key) efficiently handles small, per-user data with a key-value orientation, ensuring that changes made on one device are quickly reflected on others.

Exam trap

The trap here is that candidates often confuse Azure Cache for Redis as a primary data store for persistent, synchronized user preferences, overlooking its transient nature and lack of built-in conflict resolution for multi-device scenarios.

How to eliminate wrong answers

Option B (Azure Cache for Redis) is wrong because it is an in-memory cache designed for temporary, volatile data with limited persistence options; it does not provide built-in conflict resolution or durable, globally distributed synchronization for user preferences that must persist across sessions. Option C (Azure Blob Storage) is wrong because it is optimized for large, unstructured binary objects (e.g., images, videos) and lacks the low-latency, key-value access patterns and real-time sync capabilities needed for small, frequently updated user preferences. Option D (Azure SQL Database) is wrong because it is a relational database that requires a fixed schema and is not optimized for simple key-value workloads; its overhead and lack of native conflict resolution make it unsuitable for real-time synchronization of small, per-user key-value data.

Practice this question →

MCQmedium

In a banking application, a transaction transfers $100 from Account A to Account B. The system deducts $100 from Account A successfully, but due to a network error, the credit to Account B fails. The application rolls back the deduction from Account A, ensuring that neither account is affected. Which ACID property is being enforced?

A.Atomicity

B.Consistency

C.Isolation

D.Durability

AnswerA

Atomicity guarantees that a transaction's operations are executed as an all-or-nothing unit. If the $100 debit from one account succeeds but the $100 credit to another account fails, atomicity requires the entire transaction to be rolled back, returning the database to its pre-transaction state. Without atomicity, a partial transfer would leave the bank with inconsistent balances and potential lost or duplicated funds.

Why this answer

Atomicity ensures that a transaction is treated as a single, indivisible unit of work. In this scenario, the deduction from Account A and the credit to Account B must both succeed or both fail entirely. When the credit to Account B fails, the system rolls back the deduction from Account A, preserving the all-or-nothing nature of the transaction.

This is the core behavior of atomicity in ACID-compliant database systems like Azure SQL Database or SQL Server.

Exam trap

The trap here is that candidates confuse the rollback action with consistency, because both involve maintaining a correct state, but atomicity specifically governs the all-or-nothing completion of the transaction itself, not the validity of the data rules.

Why the other options are wrong

Consistency ensures that a transaction transforms the database from one valid state to another, but here the rollback due to failure maintains consistency. The key property demonstrated is atomicity, which ensures the entire transaction is treated as a single unit that either fully completes or fully rolls back.

Isolation ensures concurrent transactions do not interfere with each other, but this scenario involves a single transaction that fails partway; the rollback enforces atomicity (all-or-nothing), not isolation.

Durability ensures that committed transactions persist permanently, even after system failures. In this scenario, the transaction was rolled back, not committed, so durability is not relevant.

Practice this question →

MCQeasy

A banking system processes a money transfer between two accounts. The system is designed so that after the transaction is committed, the results are permanently saved and survive any subsequent system failure, such as a power outage. Which ACID property ensures this behavior?

A.Durability

B.Atomicity

C.Consistency

D.Isolation

AnswerA

Durability is the ACID property that guarantees once a transaction is committed, its changes are permanently recorded in non-volatile storage, even if a crash occurs immediately afterward. In a money transfer scenario, the updated balances in both the source and destination accounts must survive a power loss, disk failure, or system restart to prevent the transferred funds from disappearing. This is implemented via write-ahead logging or journaling (e.g., SQL Server transaction log), where commit records are forced to disk before the transaction is acknowledged as successful.

Why this answer

Durability ensures that once a transaction is committed, its changes are permanently stored and survive system failures, such as power outages or crashes. In this banking scenario, the money transfer results are written to non-volatile storage (e.g., disk) via a write-ahead log, guaranteeing that the committed state is recoverable even after a restart.

Exam trap

The trap here is that candidates often confuse durability with atomicity, thinking that 'surviving failures' means the transaction either completes fully or not at all, but atomicity handles the rollback of partial transactions, not the persistence of committed ones.

How to eliminate wrong answers

Option B (Atomicity) is wrong because atomicity ensures that a transaction is treated as an all-or-nothing unit, meaning either all operations complete or none do, but it does not guarantee that committed data survives failures. Option C (Consistency) is wrong because consistency ensures that a transaction brings the database from one valid state to another, preserving integrity constraints, but it does not address persistence after a commit. Option D (Isolation) is wrong because isolation ensures that concurrent transactions do not interfere with each other, preventing dirty reads or lost updates, but it does not provide durability against system crashes.

Practice this question →

100

MCQeasy

A company stores customer names, addresses, and order history. They need to perform complex queries that join customer and order data. Which type of data store is most appropriate for this scenario?

A.Key-value store

B.Relational database

C.Document database

D.Graph database

AnswerB

A relational database is the best fit because it stores customers and order history in separate, normalized tables linked by foreign keys, such as a customer ID. ANSI SQL supports JOIN operations to combine these tables on demand, so you can query a specific customer's details alongside all their past orders. Enforcing a defined schema and referential integrity ensures names, addresses, and order records remain consistent and accurate. This matches the structured, transactional nature of customer/order data.

Why this answer

A relational database (e.g., Azure SQL Database) is most appropriate because the scenario requires joining customer and order data via complex queries. Relational databases enforce a fixed schema with tables, primary keys, and foreign keys, enabling efficient JOIN operations using SQL. This structure ensures data integrity and supports ACID transactions, which are essential for accurate order history and customer records.

Exam trap

The trap here is that candidates often choose a document database (Option C) because they associate 'complex queries' with JSON flexibility, but fail to recognize that 'joining' specifically requires relational database features like SQL JOINs and foreign keys, which document stores lack.

Why the other options are wrong

Key-value stores do not support complex queries or joins across multiple data types; they are optimized for simple lookups by key, not for joining customer and order data.

Document databases store semi-structured data (e.g., JSON) and are optimized for queries within a single document, not for complex joins across multiple collections. The requirement for joining customer and order data makes a relational database more appropriate.

Graph databases are optimized for highly interconnected data with complex relationships (e.g., social networks), not for joining structured tabular data like customer and order history, which is better handled by relational databases.

Practice this question →

101

MCQmedium

Refer to the exhibit. You are reviewing an ARM template for a new storage account. The storage account will store data that must be accessible from any Azure region and must be highly durable. Which change should you make to the template?

A.Set supportsHttpsTrafficOnly to false

B.Change the SKU name to Premium_LRS

C.Change the SKU name to Standard_GRS

D.Change the kind to BlobStorage

AnswerC

Changing the SKU name to Standard_GRS switches the storage account to geo-redundant storage, which synchronously copies your data three times within the primary region and then asynchronously copies it to a paired secondary region. If the primary region becomes unavailable, Azure can fail over to the secondary copy, so data survives a regional outage. This directly meets the ARM template requirement for higher durability across regions.

Why this answer

Standard_GRS (Geo-Redundant Storage) is the correct SKU because it replicates data synchronously three times within a primary region and asynchronously to a secondary region hundreds of miles away, ensuring high durability (11 nines) and accessibility from any Azure region via read-access (RA-GRS). The requirement for data to be accessible from any Azure region and highly durable aligns with GRS's geo-replication, whereas LRS only replicates within a single datacenter and Premium_LRS is for low-latency workloads, not geo-accessibility.

Exam trap

Microsoft often tests the misconception that changing the 'kind' (e.g., to BlobStorage) or disabling HTTPS affects durability or geo-accessibility, when in fact only the SKU name (replication strategy) controls these properties, and candidates confuse security settings with replication settings.

How to eliminate wrong answers

Option A is wrong because setting supportsHttpsTrafficOnly to false disables HTTPS enforcement, which is a security setting unrelated to durability or regional accessibility; it would expose data to insecure HTTP traffic. Option B is wrong because Premium_LRS uses SSD-based storage with local redundancy only, offering lower durability (11 nines vs. 16 nines for GRS) and no geo-replication, failing the 'accessible from any Azure region' requirement. Option D is wrong because changing the kind to BlobStorage restricts the account to blob-only storage (block blobs and append blobs), but the question does not specify blob-only data; moreover, the kind does not affect durability or geo-accessibility—that is determined by the SKU.

Practice this question →

102

MCQhard

A healthcare application stores patient medical history in a relational database. The system must ensure that after a transaction updates multiple records (e.g., diagnosis and medication), all changes are saved or none are saved. This property is best described as:

A.Atomicity

B.Consistency

C.Durability

D.Isolation

AnswerA

In this healthcare scenario, Atomicity guarantees that a multi-step transaction—such as writing a patient diagnosis, associated medications, and lab results together—either commits all changes to the medical history or rolls back completely. If any statement in the transaction fails, the database discards all earlier writes, leaving the patient record untouched. This all-or-nothing behavior directly matches the requirement that incomplete updates never appear, which is why Atomicity is correct. Azure SQL Database uses a transaction log and rollback segments to enforce this property even when the service fails mid-transaction.

Why this answer

Atomicity ensures that a transaction is treated as a single, indivisible unit of work. In the context of a relational database storing patient medical history, if a transaction updates both the diagnosis and medication records, atomicity guarantees that either both updates are committed or both are rolled back, preventing partial updates that could leave the data in an inconsistent state.

Exam trap

The trap here is that candidates often confuse atomicity with consistency, mistakenly thinking that 'all-or-nothing' is about maintaining data rules, when in fact atomicity is specifically about the transaction's indivisibility at the write level.

How to eliminate wrong answers

Option B (Consistency) is wrong because consistency ensures that a transaction brings the database from one valid state to another, respecting all defined rules (e.g., constraints, triggers), but it does not directly enforce the all-or-nothing behavior of multiple record updates. Option C (Durability) is wrong because durability guarantees that once a transaction is committed, its changes persist even after a system failure, but it does not control whether the transaction is fully applied or rolled back. Option D (Isolation) is wrong because isolation ensures that concurrent transactions do not interfere with each other, preventing dirty reads or lost updates, but it does not mandate that all changes within a single transaction are saved or none are saved.

Practice this question →

103

Multi-Selecthard

Which THREE of the following are valid Azure data storage services? (Choose three.)

Select 3 answers

A.Azure Files

B.Azure Blob Storage

C.Azure Redis Cache

D.Azure Table Storage

E.Azure Service Bus

AnswersA, B, D

Azure Files is a fully managed file share service that provides Server Message Block (SMB) and Network File System (NFS) protocols, enabling typical network-mounted drive access from multiple VMs or on-premises clients. It is a valid Azure data storage option because it stores files in a shared, persistent manner, similar to a traditional file server but without the maintenance overhead. This differentiates it from block or object storage, making it the correct answer for scenarios requiring file-level access and standard file-sharing protocols.

Why this answer

Azure Files provides fully managed file shares in the cloud that can be accessed via the Server Message Block (SMB) protocol or the Network File System (NFS) protocol. It is a valid Azure data storage service because it stores data as files in a hierarchical structure, making it suitable for lift-and-shift scenarios for on-premises file servers.

Exam trap

The trap here is that candidates may confuse Azure Redis Cache and Azure Service Bus as data storage services because they store data temporarily, but the DP-900 exam defines 'data storage services' as those designed for persistent, structured or unstructured data storage, not transient messaging or caching.

Practice this question →

104

MCQeasy

A retail company stores product information in a relational database table with fixed columns: ProductID (integer), Name (string), Price (decimal). They also store customer reviews as JSON documents where each review may contain different fields such as rating, comment, and optional images. Additionally, they store product images as JPEG files in Azure Blob Storage. Which of the following correctly classifies these data types from most structured to least structured?

A.Structured (product info), Semi-structured (reviews), Unstructured (images)

B.Semi-structured (product info), Structured (reviews), Unstructured (images)

C.Unstructured (product info), Semi-structured (reviews), Structured (images)

D.Structured (product info), Unstructured (reviews), Semi-structured (images)

AnswerA

This pairing is correct because the product table resides in a relational database where each row maps to a fixed set of typed columns, making it structured data. Customer reviews stored as JSON documents contain key-value pairs and nested objects that can vary between records, which is the defining characteristic of semi-structured data. JPEG images are stored as compressed binary files that have no inherent row, column, or field structure, so they are unstructured. Together, these three categories accurately reflect the data-types question being tested.

Why this answer

Product info in a relational table with fixed columns (ProductID, Name, Price) is structured data. Customer reviews stored as JSON documents, which may have varying fields like rating, comment, and optional images, are semi-structured because they have a flexible schema. Product images stored as JPEG files in Azure Blob Storage are unstructured binary data.

This ordering from most to least structured matches option A.

Exam trap

Microsoft often tests the distinction between semi-structured and unstructured data, where candidates mistakenly classify JSON as unstructured because it lacks a fixed schema, but JSON is semi-structured due to its inherent key-value structure and optional fields.

Why the other options are wrong

Product info uses fixed columns (ProductID, Name, Price) making it structured, not semi-structured. Reviews are JSON with varying fields, which is semi-structured, not structured.

Product info is stored in a relational table with fixed columns, making it structured, not unstructured. Images are binary files without schema, making them unstructured, not structured.

Customer reviews are stored as JSON documents with varying fields, which is semi-structured data, not unstructured. Unstructured data lacks a predefined data model, like images, not JSON.

Practice this question →

105

MCQeasy

Refer to the exhibit. You are deploying an Azure Storage account. The JSON snippet represents a template parameter. What does the 'isHnsEnabled' property enable?

A.Blob versioning

B.Soft delete for blobs

C.Geo-redundant storage

D.Hierarchical namespace for the storage account

AnswerD

The hierarchical namespace is a creation-time flag that organizes blobs into directories and nested folder structures, enabling Azure Data Lake Storage Gen2 features like POSIX-like ACLs, atomic directory renames, and higher-throughput analytics workloads. This property cannot be changed after the storage account is provisioned, so it must be set during deployment. Unlike versioning or soft delete, which are optional post-creation protections, this namespace fundamentally changes the account's data model, making it the correct capability referenced in the exhibit.

Why this answer

The 'isHnsEnabled' property enables the hierarchical namespace for the storage account, which is a core feature of Azure Data Lake Storage Gen2. When set to true, it allows the storage account to organize blobs into a directory hierarchy, enabling POSIX-like access control lists (ACLs) and file system semantics. This is essential for big data analytics workloads that require a file system structure rather than a flat blob storage model.

Exam trap

The trap here is that candidates often confuse 'isHnsEnabled' with blob-level features like versioning or soft delete, because all three are related to data management, but only the hierarchical namespace fundamentally changes the storage account's architecture to support file system semantics.

How to eliminate wrong answers

Option A is wrong because blob versioning is enabled via the 'Versioning' property in the Blob service settings, not by 'isHnsEnabled'. Option B is wrong because soft delete for blobs is configured through the 'DeleteRetentionPolicy' property in the Blob service, not through the hierarchical namespace flag. Option C is wrong because geo-redundant storage (GRS) is a replication option set via the 'sku.name' property (e.g., 'Standard_GRS'), not by enabling a hierarchical namespace.

Practice this question →

106

Multi-Selectmedium

Which TWO of the following are common characteristics of a NoSQL database?

Select 2 answers

A.Flexible schema

B.Normalized data storage

C.Strong ACID transaction support

D.Relational data model

E.Horizontal scaling

AnswersA, E

NoSQL databases allow schema flexibility, making them suitable for semi-structured or unstructured data.

Why this answer

NoSQL databases, such as MongoDB or Cassandra, use a flexible schema that allows documents or records to have varying fields without requiring predefined table structures. This enables developers to iterate quickly and store semi-structured or unstructured data, such as JSON documents, without costly schema migrations.

Exam trap

The trap here is that candidates confuse 'flexible schema' with 'no schema at all' or mistakenly think NoSQL always supports strong ACID transactions, when in reality most NoSQL systems trade ACID for scalability and performance.

Practice this question →

107

MCQmedium

Your organization uses Azure SQL Database and needs to ensure that all customer data is encrypted at rest and in transit with minimal administrative overhead. Which solution should you recommend?

A.Use Microsoft Purview Information Protection to label and encrypt the data.

B.Enable Transparent Data Encryption (TDE) and enforce TLS 1.2 for connections.

C.Implement Dynamic Data Masking on the customer table.

D.Enable Always Encrypted for all sensitive columns and use client-side encryption.

AnswerB

Transparent Data Encryption (TDE) automatically encrypts Azure SQL Database data and log files at rest using AES-256, requiring no changes to existing applications or schemas. Enforcing TLS 1.2 as the minimum connection protocol ensures all data is encrypted in transit between the client and the database server. Together, these features provide comprehensive encryption with minimal administrative overhead, making this the correct answer for this requirement.

Why this answer

Transparent Data Encryption (TDE) encrypts Azure SQL Database data files at rest without requiring any application changes, and enforcing TLS 1.2 ensures all data in transit is encrypted using a strong, industry-standard protocol. This combination meets the requirement for encryption at rest and in transit with minimal administrative overhead, as TDE is managed by the platform and TLS enforcement is a simple server-level setting.

Exam trap

The trap here is that candidates often confuse Dynamic Data Masking (which only hides data in results) with encryption, or they overcomplicate the solution by choosing Always Encrypted, which requires client-side changes and key management, when the question explicitly asks for minimal administrative overhead.

How to eliminate wrong answers

Option A is wrong because Microsoft Purview Information Protection is a data classification and labeling service, not a native encryption mechanism for Azure SQL Database; it does not encrypt data at rest or in transit within the database engine. Option C is wrong because Dynamic Data Masking only obfuscates data in query results for unauthorized users, it does not encrypt data at rest or in transit. Option D is wrong because Always Encrypted requires client-side encryption and key management, which adds significant administrative overhead and application changes, contradicting the 'minimal administrative overhead' requirement.

Practice this question →

108

MCQeasy

A company stores employee records in a database. Each employee record contains an EmployeeID (unique), Name, Department, and HireDate. The EmployeeID is used to uniquely identify each employee. Which data concept does the EmployeeID represent?

A.Index

B.Foreign key

C.Primary key

D.Unique constraint

AnswerC

A primary key is the column or set of columns declared to hold a unique, non-null value for every row, and it serves as the table's authoritative identifier for each entity record. For an employee table, an EmployeeID column or a composite of first name, last name, and birth date would be a primary key because it guarantees that each employee row can be individually referenced, updated, or joined to related tables. This is the fundamental relational mechanism for row identity and is what other tables use when they need to reference a specific employee.

Why this answer

The EmployeeID is used to uniquely identify each employee record, which is the defining characteristic of a primary key. In relational databases, a primary key enforces entity integrity by ensuring each row has a unique, non-null identifier. This aligns with the core data concept of a primary key as the unique identifier for a table.

Exam trap

The trap here is that candidates often confuse a unique constraint with a primary key because both enforce uniqueness, but the primary key uniquely identifies the row and cannot contain NULLs, while a unique constraint is a secondary uniqueness enforcement that can allow a single NULL value.

How to eliminate wrong answers

Option A is wrong because an index is a performance optimization structure that speeds up data retrieval, not a constraint that uniquely identifies rows. Option B is wrong because a foreign key is a column that references a primary key in another table to establish a relationship, not a unique identifier within its own table. Option D is wrong because a unique constraint ensures all values in a column are distinct but does not inherently designate the column as the table's primary identifier; a table can have multiple unique constraints but only one primary key.

Practice this question →

109

MCQhard

Refer to the exhibit. You are reviewing an ARM template for an Azure SQL Database deployment. The database must support a read-only workload that requires low latency. The current configuration uses General Purpose tier with 4 vCores. What is the most significant performance improvement you can make without changing the tier?

A.Increase maxSizeBytes to 1 TB

B.Set the edition to 'Serverless'

C.Enable read scale-out by adding 'readScale' property

D.Change requestedBackupStorageRedundancy to 'Local'

AnswerC

Enabling read scale-out by adding the 'readScale' property to your ARM template routes read-only connections to an automatically provisioned read-only replica. This offloads read-heavy query load from the primary replica, freeing up its CPU, memory, and I/O for write operations and transactional workloads. This is the only option that directly improves query performance by scaling out the read path, especially for workloads that separate reporting or analytical queries from OLTP traffic.

Why this answer

Enabling read scale-out by adding the 'readScale' property allows the database to use a read-only replica, offloading read workloads from the primary and providing low-latency reads. This is the most significant performance improvement within the General Purpose tier because it directly addresses the read-only workload requirement without changing the tier or incurring additional compute costs.

Exam trap

The trap here is that candidates often confuse scaling storage (maxSizeBytes) or changing backup redundancy with performance improvements, but the question specifically targets read latency for a read-only workload, which is directly addressed by read scale-out rather than storage or backup changes.

How to eliminate wrong answers

Option A is wrong because increasing maxSizeBytes to 1 TB only expands storage capacity, which does not improve read performance or latency for a read-only workload. Option B is wrong because setting the edition to 'Serverless' changes the tier (from provisioned to serverless compute), which violates the constraint of not changing the tier, and serverless is designed for intermittent workloads, not low-latency read performance. Option D is wrong because changing requestedBackupStorageRedundancy to 'Local' affects backup storage redundancy (e.g., LRS vs.

GRS), not query performance or read latency.

Practice this question →

110

MCQeasy

A retail company collects data from online transactions including order ID, customer details, product IDs, quantities, and timestamps. The data is stored in a relational database and used for order processing and inventory management. Which characteristic of this data makes it structured?

A.It is stored in rows and columns with a predefined schema.

B.It is stored as key-value pairs.

C.It is stored in JSON format with variable fields.

D.It is stored in unstructured text files.

AnswerA

Structured data is defined by a rigid, predefined schema, which means each record conforms to a specified set of columns with fixed data types. This tabular format—rows and columns—enables relational database features such as ACID transactions (atomicity, consistency, isolation, durability), primary/foreign key constraints, and efficient SQL querying. The schema is enforced at write time, so every inserted row matches the expected structure, making it the foundational model for transactional systems like online order processing.

Why this answer

Structured data is defined by a fixed schema where each entity (e.g., orders) is stored in rows and columns with predefined data types (e.g., INT for order ID, VARCHAR for customer details). This relational model enforces consistency and enables efficient querying via SQL for order processing and inventory management.

Exam trap

The trap here is that candidates confuse 'structured' with any organized storage format (like JSON or key-value pairs), but the DP-900 exam specifically defines structured data as having a fixed schema with rows and columns in a relational database.

How to eliminate wrong answers

Option B is wrong because key-value pairs (e.g., in Redis or DynamoDB) are a NoSQL model that does not enforce a fixed schema or relational integrity, unlike the structured data described. Option C is wrong because JSON with variable fields is semi-structured data; it allows flexible schemas and nested structures, not the rigid rows-and-columns format of a relational database. Option D is wrong because unstructured text files (e.g., .txt or .log files) lack any predefined schema or organization, making them unsuitable for direct SQL-based order processing and inventory management.

Practice this question →

111

MCQmedium

You need to design a data storage solution for an e-commerce platform that requires ACID transactions for order processing and high availability across regions. Which Azure service meets these requirements?

A.Azure Database for MySQL with read replicas

B.Azure Synapse Analytics

C.Azure SQL Database with active geo-replication

D.Azure Cosmos DB with multiple write regions

AnswerC

Azure SQL Database with active geo-replication maintains asynchronous, readable secondary replicas in paired or other Azure regions, preserving a mature relational database engine with full ACID transactions on the primary. This design provides a geographically distributed read scale and enables a controlled failover to a secondary region if an outage occurs, delivering a strong high-availability and disaster-recovery posture for a business-critical e-commerce application. The secondaries can also serve read-only traffic, offloading workload from the primary, while writes remain on the primary to maintain consistency.

Why this answer

Azure SQL Database with active geo-region replication supports ACID transactions natively and provides automatic failover to a secondary region, ensuring high availability across regions. This meets the e-commerce platform's need for transactional consistency and regional resilience.

Exam trap

The trap here is that candidates often confuse 'high availability' with 'multi-region writes' and choose Cosmos DB, overlooking that ACID transactions require a relational database with strict consistency guarantees, not just eventual consistency or single-document atomicity.

How to eliminate wrong answers

Option A is wrong because Azure Database for MySQL with read replicas supports ACID transactions but read replicas are read-only and do not provide automatic failover for write workloads, thus failing high availability for order processing writes. Option B is wrong because Azure Synapse Analytics is a big data analytics service optimized for large-scale data warehousing and analytics, not for OLTP workloads requiring ACID transactions. Option D is wrong because Azure Cosmos DB with multiple write regions provides multi-region writes and high availability but does not support full ACID transactions across multiple documents; it offers single-document atomicity and eventual consistency by default, not the strict ACID guarantees needed for order processing.

Practice this question →

112

MCQeasy

A startup is building a mobile app that allows users to share short text updates. Each update includes a user ID, timestamp, and message text. The development team expects rapid growth and needs a storage solution that can scale horizontally, handle high write throughput, and provide low-latency reads globally. Which Azure data service is most appropriate?

A.Azure SQL Database with a single database.

B.Azure Cosmos DB with a multi-master configuration and partition on user ID.

C.Azure Blob Storage with append blobs.

D.Azure Table Storage with user ID as partition key and timestamp as row key.

AnswerB

Azure Cosmos DB with multi-master configuration and partition on user ID is correct because it provides active-active multi-region writes, 99.999% availability, and tunable consistency with single-digit millisecond latencies at the 99th percentile. Using user ID as the partition key co-locates all posts from one user on the same logical partition, enabling efficient queries and scalable writes. Multi-master lets users write to the nearest region while Cosmos DB reconciles conflicts, which is exactly what a high-throughput, globally distributed short-text app needs.

Why this answer

Azure Cosmos DB with a multi-master configuration is the most appropriate choice because it provides global distribution with multiple write regions, enabling horizontal scaling and low-latency reads and writes worldwide. Partitioning on user ID ensures even data distribution and efficient query performance for the app's high write throughput requirements.

Exam trap

The trap here is that candidates often confuse Azure Table Storage's horizontal scaling with the global, multi-master capabilities of Cosmos DB, assuming Table Storage can provide low-latency writes worldwide when it lacks native multi-region write support and has higher latency for cross-region scenarios.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database with a single database is a relational database that scales vertically (up to a maximum size and DTU/vCore limit) and cannot natively handle global low-latency reads or multi-region writes without complex sharding or read replicas. Option C is wrong because Azure Blob Storage with append blobs is designed for unstructured data like logs or files, not for low-latency, high-throughput transactional updates with querying by user ID and timestamp. Option D is wrong because Azure Table Storage, while scalable, does not support multi-master writes or global low-latency reads natively; it is a key-value store with limited query capabilities and eventual consistency by default, which may not meet the app's need for low-latency writes globally.

Practice this question →

113

MCQeasy

A company collects data from multiple sources: IoT sensor streams, social media feeds, and CSV files from legacy systems. They want to store all this data in its original format without any transformation, so that data scientists can later apply machine learning models or run ad-hoc queries. Which data storage pattern best describes this approach?

A.Data warehouse

B.Data lake

C.Relational database

D.Data mart

AnswerB

A data lake is a centralized repository that stores raw data in its native format, from IoT sensor streams to structured files, without requiring a predefined schema. It employs schema-on-read, so data scientists can explore and run ad-hoc analytics before defining structure. This makes it ideal for diverse, high-volume streaming data where format and meaning may evolve over time.

Why this answer

A data lake is designed to store vast amounts of raw data in its native format (structured, semi-structured, or unstructured) without requiring upfront schema or transformation. This aligns perfectly with the scenario of ingesting IoT streams, social media feeds, and CSV files as-is, enabling data scientists to later apply machine learning or run ad-hoc queries directly against the raw data.

Exam trap

The trap here is that candidates often confuse a data lake with a data warehouse, assuming both are for analytics, but the key differentiator is that a data lake stores raw, unprocessed data while a data warehouse requires transformation and schema-on-write.

Why the other options are wrong

A data warehouse requires schema-on-write and data transformation before loading, which contradicts the requirement to store data in its original format without transformation.

A data mart is a subset of a data warehouse focused on a specific business function, not designed to store raw, untransformed data from diverse sources like IoT streams and social media feeds.

Practice this question →

114

MCQmedium

A social media company stores user profiles as JSON documents where each profile may have different attributes (e.g., some profiles include 'education' while others include 'work history'). The company also stores user-generated posts in a relational database table with fixed columns (PostID, UserID, Content, Timestamp). Which of the following best describes the data types used for user profiles and user posts?

A.User profiles are structured data; posts are unstructured data.

B.User profiles are semi-structured data; posts are structured data.

C.Both are semi-structured data.

D.User profiles are unstructured data; posts are structured data.

AnswerB

User profiles are semi-structured because JSON documents allow variable attribute sets—some users may have 'verified' while others have 'pronouns'—so there is no fixed schema, but the data still carries self-describing key-value pairs. Posts, in contrast, are stored in a fixed relational schema with consistent columns such as post_id, user_id, content, and created_timestamp, making them classic structured data. This combination makes the statement correct.

Why this answer

User profiles are stored as JSON documents with varying attributes, which is a classic example of semi-structured data because it has some organizational properties (key-value pairs) but does not enforce a fixed schema. User posts are stored in a relational database table with fixed columns (PostID, UserID, Content, Timestamp), which is structured data because it adheres to a rigid schema with defined data types and relationships.

Exam trap

The trap here is that candidates often confuse 'semi-structured' with 'unstructured' because JSON looks like free-form text, but JSON actually has a defined key-value structure, making it semi-structured, not unstructured.

Why the other options are wrong

User profiles are JSON documents with varying attributes, which is semi-structured data, not structured. Posts have fixed columns, which is structured data, not unstructured.

User posts are stored in a relational database with fixed columns (PostID, UserID, Content, Timestamp), making them structured data, not semi-structured. Only user profiles (JSON with varying attributes) are semi-structured.

User profiles are JSON documents with varying attributes, which is the definition of semi-structured data, not unstructured. Posts have fixed columns, making them structured data, not unstructured.

Practice this question →

115

MCQeasy

A retail company stores product inventory data in a fixed-schema table with columns for ProductID, ProductName, QuantityInStock, and ReorderLevel. How should this data be classified?

A.Structured data

B.Semi-structured data

C.Unstructured data

D.Streaming data

AnswerA

Correct - The data has a fixed schema organized in rows and columns, which is the definition of structured data.

Why this answer

This data is classified as structured data because it conforms to a fixed schema with clearly defined columns (ProductID, ProductName, QuantityInStock, ReorderLevel) and data types, stored in a relational table. Structured data is highly organized, easily queryable via SQL, and follows a rigid schema, which matches the description of the inventory table.

Exam trap

The trap here is that candidates may confuse structured data with semi-structured data because both involve some organization, but the key distinction is that structured data requires a rigid, predefined schema (like a fixed-schema table), while semi-structured data allows schema flexibility (e.g., JSON with optional fields).

How to eliminate wrong answers

Option B is wrong because semi-structured data (e.g., JSON, XML, or CSV with flexible schemas) does not enforce a fixed schema or strict column definitions, whereas this table has a predefined schema. Option C is wrong because unstructured data (e.g., text files, images, or videos) lacks any predefined data model or organization, unlike the tabular inventory data. Option D is wrong because streaming data refers to continuous, real-time data flows (e.g., IoT sensor data or clickstreams), not static data stored in a table.

Practice this question →

116

MCQhard

Match each ACID property with its correct description. Properties: - Atomicity - Consistency - Isolation - Durability Descriptions: 1. Transactions appear to execute one after the other, even if they are concurrent. 2. Once a transaction is committed, the changes are permanently saved and survive failures. 3. A transaction either completes fully or is rolled back entirely. 4. A transaction brings the database from one valid state to another, obeying all rules. Which option correctly maps each property to its description?

A.Atomicity → 3, Consistency → 4, Isolation → 1, Durability → 2

B.Atomicity → 4, Consistency → 3, Isolation → 2, Durability → 1

C.Atomicity → 2, Consistency → 1, Isolation → 3, Durability → 4

D.Atomicity → 1, Consistency → 2, Isolation → 4, Durability → 3

AnswerA

This is the correct mapping of ACID properties to their standard definitions.

Why this answer

It accurately maps each ACID property to its definition. Atomicity ensures a transaction is all-or-nothing (3), Consistency guarantees the database moves from one valid state to another (4), Isolation makes concurrent transactions appear serial (1), and Durability ensures committed changes persist even after a failure (2). These are the standard definitions used in Azure SQL Database and other relational database systems.

Exam trap

The trap here is that candidates confuse the definitions of Consistency and Atomicity, often thinking Consistency means 'all-or-nothing' rather than 'valid state transitions,' or they swap Isolation with Durability by misremembering the 'permanent save' concept.

How to eliminate wrong answers

Option B is wrong because it swaps Atomicity and Consistency: Atomicity is about all-or-nothing execution, not bringing the database to a valid state (which is Consistency). Option C is wrong because it assigns Durability to 'transactions appear to execute one after the other' (Isolation) and Atomicity to 'changes are permanently saved' (Durability), completely inverting the properties. Option D is wrong because it maps Atomicity to 'transactions appear to execute one after the other' (Isolation) and Isolation to 'brings the database from one valid state to another' (Consistency), mixing up the core definitions.

Practice this question →

117

MCQmedium

You design a data solution for an e-commerce platform. Transactional data must be stored with ACID compliance for order processing, while clickstream data from the website will be used for analytics. Which combination of Azure data services best meets these needs?

A.Azure Cosmos DB for transactions; Azure SQL Database for analytics

B.Azure SQL Database for transactions; Azure Synapse Analytics for analytics

C.Azure Blob Storage for transactions; Azure Data Lake Storage for analytics

D.Azure Database for MySQL for transactions; Azure Analysis Services for analytics

AnswerB

Azure SQL Database is a fully managed relational database engine that provides built-in features such as automatic backups, high availability, and strict ACID transaction guarantees, making it ideal for capturing e-commerce orders, inventory, and payments. Azure Synapse Analytics is a limitless analytics service that separates storage from compute and uses a massively parallel processing (MPP) architecture to run complex queries over trillions of rows, with built-in integration for data lakes, pipelines, and Power BI. This combination cleanly separates the operational and analytical layers, letting each service optimize for its own workload.

Why this answer

Azure SQL Database provides full ACID compliance for transactional workloads like order processing, ensuring data integrity. Azure Synapse Analytics is optimized for large-scale analytics on clickstream data, offering massively parallel processing (MPP) and integration with data lakes. This combination separates OLTP and OLAP workloads efficiently.

Exam trap

The trap here is that candidates often assume Azure Cosmos DB (Option A) is ACID-compliant because it supports multi-document transactions within a single partition, but it does not guarantee full ACID across partitions, making it unsuitable for strict order processing.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a NoSQL database that offers configurable consistency levels (not full ACID across all operations) and is not ideal for strict ACID-compliant order processing; Azure SQL Database is transactional but not optimized for large-scale analytics like Synapse. Option C is wrong because Azure Blob Storage is an object store with no ACID transaction support (it offers eventual consistency for blobs) and is unsuitable for order processing; Azure Data Lake Storage is for raw data storage, not interactive analytics. Option D is wrong because Azure Database for MySQL provides ACID compliance but Azure Analysis Services is a semantic modeling layer (not a scalable analytics engine) and lacks the MPP capabilities needed for clickstream analytics.

Practice this question →

118

MCQeasy

A healthcare company stores patient records in a relational database with fixed columns (PatientID, Name, DOB, BloodType). Medical images such as X-rays are stored as DICOM files. Clinical notes are stored as free-text documents. Which of the following correctly classifies these data types from most structured to least structured?

A.Patient records (structured), DICOM files (structured), Clinical notes (unstructured)

B.Patient records (structured), DICOM files (semi-structured), Clinical notes (unstructured)

C.Patient records (semi-structured), DICOM files (unstructured), Clinical notes (structured)

D.Patient records (unstructured), DICOM files (semi-structured), Clinical notes (structured)

AnswerB

Patient records in a relational database have a fixed schema of columns and data types, so they are structured. DICOM files contain header fields with standardized metadata tags plus pixel data, which fits the semi-structured category because they have an organized structure but not a rigid tabular schema. Clinical notes are free-form text written by clinicians, lacking any predefined format, so they are unstructured. This combination correctly maps each data type to its storage and query characteristics.

Why this answer

Patient records in a fixed-column relational database are structured data because they conform to a rigid schema with defined data types. DICOM files are semi-structured because they contain a structured header with metadata tags (e.g., patient ID, study date) alongside an unstructured binary image payload. Clinical notes as free-text documents are unstructured because they lack a predefined schema or organization, making them difficult to query without natural language processing.

Exam trap

The trap here is that candidates often misclassify DICOM files as fully structured due to their standardized header, overlooking the unstructured binary image payload that makes them semi-structured.

Why the other options are wrong

DICOM files are semi-structured because they contain a structured header (metadata) and unstructured pixel data; classifying them as structured is incorrect.

Patient records with fixed columns are structured, not semi-structured. DICOM files contain metadata tags and image data, making them semi-structured, not unstructured. Clinical notes are free-text, which is unstructured, not structured.

Patient records with fixed columns are structured, not unstructured. Clinical notes are free-text and unstructured, not structured. DICOM files are semi-structured because they contain metadata tags alongside binary image data, not semi-structured in the wrong order.

Practice this question →

119

MCQmedium

An e-commerce company runs a data pipeline that reads all orders from the previous hour, aggregates total sales per product category, and writes the results to a reporting database. The pipeline executes at the start of every hour. Which type of data processing workload does this pipeline represent?

A.Batch processing

B.Stream processing

C.Transactional processing

D.Interactive processing

AnswerA

The pipeline processes a batch of data (hourly orders) on a schedule, which is batch processing.

Why this answer

This pipeline reads all orders from the previous hour, aggregates total sales per product category, and writes results to a reporting database at the start of every hour. This is a classic batch processing workload because data is collected over a fixed time window (one hour) and processed as a single, scheduled job, not continuously. Batch processing is ideal for non-real-time, high-volume data transformations like hourly sales aggregation.

Exam trap

The trap here is that candidates confuse scheduled batch processing with stream processing because both can handle time-windowed aggregations, but batch processes data in discrete, scheduled chunks while stream processes data continuously as it arrives.

Why the other options are wrong

The pipeline processes data in hourly intervals, not continuously, and does not require real-time or near-real-time analysis of streaming data.

Transactional processing focuses on individual transactions (e.g., order placement) with ACID guarantees, not on aggregating historical data in scheduled batches.

Interactive processing involves real-time user interaction and immediate response, but the pipeline runs automatically every hour without user input, making it batch processing.

Practice this question →

120

MCQeasy

A company wants to run complex analytics queries across petabytes of data stored in Azure Data Lake Storage. They need a serverless option that supports T-SQL. Which Azure service should they use?

A.Azure SQL Database serverless

B.Azure Analysis Services

C.Azure Databricks

D.Azure Synapse Serverless SQL pool

AnswerD

Azure Synapse Serverless SQL pool is the correct service because it provides a serverless, on-demand T-SQL query engine that runs directly against files in Azure Data Lake Storage. It allows you to query data in place using standard T-SQL without provisioning or managing dedicated infrastructure, and you are billed only for the amount of data processed per query. It supports a variety of file formats such as Parquet, JSON, and CSV, enabling complex analytics and join operations across the data lake. This exactly meets the company's need for running complex analytics queries across petabyte-scale data with a familiar SQL interface.

Why this answer

Azure Synapse Serverless SQL pool is the correct choice because it provides a serverless, on-demand query service that allows you to run T-SQL queries directly against data stored in Azure Data Lake Storage (ADLS). It supports complex analytics over petabytes of data without provisioning any infrastructure, and it uses T-SQL as the query language, meeting all the stated requirements.

Exam trap

The trap here is that candidates often confuse 'serverless' with 'Azure SQL Database serverless' (Option A) because of the name, but fail to recognize that Azure SQL Database serverless is a transactional database, not a data lake query engine, and does not support querying external storage like ADLS with T-SQL.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database serverless is a serverless compute tier for a relational database, but it is designed for transactional workloads and does not natively query data stored in Azure Data Lake Storage; it requires data to be loaded into the database first. Option B is wrong because Azure Analysis Services is a fully managed platform as a service (PaaS) that provides enterprise-grade data modeling and semantic layers, but it does not support direct T-SQL queries against ADLS; it uses DAX or MDX and requires data to be imported or queried via a gateway. Option C is wrong because Azure Databricks is an Apache Spark-based analytics platform that supports SQL queries via Spark SQL, but it does not use T-SQL; it uses Spark SQL syntax and requires a cluster to be running, even if auto-terminating, making it not a true serverless T-SQL option.

Practice this question →

121

Multi-Selecteasy

A car manufacturing company has two data processing systems: one system processes real-time sensor data from assembly lines to immediately detect equipment failures, and another system processes historical production records to generate monthly efficiency reports. Which two types of data processing workloads best describe these systems?

Select 1 answer

A.Stream processing and batch processing

B.OLTP and OLAP

C.Online processing and offline processing

D.Transactional processing and analytical processing

AnswersA

Correct: Stream processing handles real-time sensor data with low latency, and batch processing handles historical data at scheduled intervals.

Why this answer

Stream processing (option A) handles real-time sensor data from the assembly line to detect equipment failures immediately, while batch processing (option A) is ideal for processing historical production records on a scheduled basis to generate monthly efficiency reports. Transactional processing (option D) refers to OLTP workloads that process business transactions, not real-time sensor streams, so it is not a correct description for the first system. The correct answer is A only.

Exam trap

Candidates may incorrectly assume that any real-time workload is transactional processing. In DP-900, transactional processing specifically means OLTP systems that handle business transactions, such as orders or financial records. Real-time sensor data should be classified as stream processing.

Practice this question →

122

MCQmedium

You are designing a data pipeline that ingests sales transactions from an on-premises SQL Server database into Azure Synapse Analytics for reporting. The data must be processed incrementally every hour with minimal latency. Which Azure service should you use to orchestrate the pipeline?

A.Azure Logic Apps

B.Azure Databricks

C.Azure Functions

D.Azure Data Factory

AnswerD

Azure Data Factory is a fully managed, code-free ETL/ELT and orchestration service built specifically for ingesting data from many sources, including on-premises databases, and moving it to cloud destinations. It provides scheduled triggers, pipeline dependencies, and a self-hosted integration runtime for secure hybrid connectivity, enabling reliable incremental loads of sales transactions by using watermark columns or change tracking mechanisms. This makes it the correct choice for designing a production-grade data pipeline.

Why this answer

Azure Data Factory (ADF) is the correct choice because it is a cloud-based ETL and data orchestration service designed specifically for building complex, schedule-driven pipelines. It natively supports incremental data loading from on-premises SQL Server via self-hosted integration runtime, and can trigger pipelines on an hourly schedule with minimal latency, making it ideal for this scenario.

Exam trap

The trap here is that candidates confuse orchestration services with compute or processing services, assuming Azure Databricks or Azure Functions can handle scheduling and data movement, when in fact Azure Data Factory is the dedicated PaaS orchestrator for such pipelines.

How to eliminate wrong answers

Option A is wrong because Azure Logic Apps is a workflow automation service for integrating apps and services, not designed for heavy data movement or complex ETL orchestration; it lacks native support for self-hosted integration runtime and incremental data loading from on-premises databases. Option B is wrong because Azure Databricks is an Apache Spark-based analytics platform for big data processing and machine learning, not a pipeline orchestration service; while it can process data, it requires additional tooling for scheduling and orchestration. Option C is wrong because Azure Functions is a serverless compute service for running event-driven code, not a data pipeline orchestrator; it lacks built-in connectors for on-premises SQL Server and does not provide scheduling or monitoring capabilities for complex data movement.

Practice this question →

123

MCQeasy

A manufacturing company collects sensor data from equipment on the factory floor. The data is generated continuously and must be processed immediately to detect anomalies and trigger alerts. Which type of data processing workload best describes this scenario?

A.Batch processing

B.Stream processing

C.Transactional processing

D.Analytical processing

AnswerB

Stream processes data in real time as it arrives, making it suitable for scenarios requiring immediate alerts and actions.

Why this answer

B is correct because the scenario requires continuous data ingestion and immediate processing to detect anomalies and trigger alerts, which is the defining characteristic of stream processing. Technologies like Azure Stream Analytics or Apache Kafka are designed to handle unbounded data streams with low-latency processing, unlike batch processing which operates on static datasets at scheduled intervals.

Exam trap

The trap here is that candidates confuse 'stream processing' with 'batch processing' because both can involve large volumes of data, but the key differentiator is the requirement for immediate, continuous processing versus scheduled, deferred processing.

Why the other options are wrong

The scenario requires immediate processing of continuously generated sensor data to detect anomalies and trigger alerts, which is the definition of stream processing. Batch processing processes data in large, delayed chunks, which cannot meet the real-time requirement.

Transactional processing is designed for discrete, ACID-compliant transactions (e.g., order entry), not for continuous, real-time sensor data streams that require immediate anomaly detection.

Analytical processing is used for historical analysis and reporting on large datasets, not for immediate anomaly detection and alerting on continuously generated sensor data.

Practice this question →

124

MCQmedium

A database system must ensure that when a transfer of funds between two accounts is processed, if the system crashes after debiting the first account but before crediting the second, the database automatically undoes the debit. This property is best described as:

A.Atomicity

B.Consistency

C.Isolation

D.Durability

AnswerA

Atomicity treats the transfer as a single indivisible unit: both the debit from one account and the credit to another must succeed together. If any operation fails or the system crashes mid-transaction, the database rolls back to the pre-transaction state, so the partial debit is undone. This ensures no orphaned or incomplete financial entry persists.

Why this answer

Atomicity ensures that a transaction is treated as a single, indivisible unit of work. If the system crashes after debiting one account but before crediting the other, the database's transaction log records the partial changes, and during recovery, the database engine (e.g., SQL Server's ARIES recovery model) performs an automatic rollback of the uncommitted transaction, undoing the debit to maintain atomicity.

Exam trap

The trap here is that candidates confuse atomicity with consistency, thinking that maintaining a correct total balance (consistency) is what undoes the debit, but atomicity is the property that specifically handles the rollback of incomplete transactions after a crash.

How to eliminate wrong answers

Option B is wrong because consistency ensures that a transaction brings the database from one valid state to another, enforcing integrity constraints (e.g., total balance remains constant), but it does not inherently handle crash recovery or undo partial changes. Option C is wrong because isolation controls how concurrent transactions interact (e.g., via locking or snapshot isolation), preventing dirty reads or lost updates, but it does not address crash recovery or rollback of incomplete transactions. Option D is wrong because durability guarantees that once a transaction is committed, its changes persist even after a crash (e.g., via write-ahead logging), but it does not undo uncommitted changes; durability applies only to committed transactions.

Practice this question →

125

MCQeasy

A marketing company collects data from social media feeds including text posts, images, and videos. The data arrives in various formats with no fixed structure or schema. This type of data is best described as:

A.A) Structured data

B.B) Semi-structured data

C.C) Unstructured data

D.D) Relational data

AnswerC

Unstructured data has no predefined schema or data model, consisting primarily of free-form text, images, videos, and audio. Social media feeds are a classic example because posts combine casual text, photographs, hashtags, links, and other media with no enforced structure. This makes them ideal for schema-on-read analytics and storage in data lakes rather than in relational databases.

Why this answer

Unstructured data lacks a predefined data model or schema, making it ideal for storing text posts, images, and videos that arrive in varied formats. Unlike structured or semi-structured data, unstructured data cannot be easily organized into rows and columns or parsed with tags, which is why option C is correct for this scenario.

Exam trap

The trap here is that candidates confuse semi-structured data (e.g., JSON with tags) with unstructured data, but the key differentiator is the complete absence of any schema or metadata markers in the described social media feeds.

How to eliminate wrong answers

Option A is wrong because structured data requires a fixed schema with rows and columns (e.g., a SQL table), which does not apply to free-form text, images, or videos. Option B is wrong because semi-structured data has some organizational properties like tags or key-value pairs (e.g., JSON, XML), but the data described has no fixed structure or schema at all. Option D is wrong because relational data is a subset of structured data stored in tables with defined relationships, which is not the case for heterogeneous social media feeds.

Practice this question →

126

MCQeasy

A company collects data from three sources: Source A: Customer records from a relational database with fixed columns (CustomerID, Name, Address). Source B: Social media posts in JSON format with varying fields (e.g., some posts have 'likes', others have 'shares'). Source C: Handwritten notes saved as scanned images in TIFF format. Which statement correctly categorizes the data by structure?

A.Source A: Structured, Source B: Semi-structured, Source C: Unstructured

B.Source A: Structured, Source B: Unstructured, Source C: Semi-structured

C.Source A: Semi-structured, Source B: Structured, Source C: Unstructured

D.Source A: Semi-structured, Source B: Unstructured, Source C: Structured

AnswerA

Customer records from a relational database are textbook structured data: fixed columns, enforced data types, primary keys, and SQL-based querying all depend on that rigid schema. JSON posts are semi-structured because each record is self-describing, containing named keys, arrays, and nested objects even though fields can vary between posts. Images of handwritten notes are unstructured—they consist of raw pixels with no inherent fields, keys, or tabular order. This option correctly labels all three sources, which is why it is the correct answer.

Why this answer

Source A's relational database with fixed columns (CustomerID, Name, Address) enforces a strict schema, making it structured data. Source B's JSON format allows varying fields like 'likes' or 'shares' per record, which is the hallmark of semi-structured data (self-describing, schema-on-read). Source C's scanned TIFF images are binary blobs with no inherent internal structure for querying, classifying them as unstructured data.

This matches the standard DP-900 categorization: structured (fixed schema), semi-structured (flexible schema), unstructured (no schema).

Exam trap

Microsoft often tests the misconception that 'JSON is unstructured because it looks like text' or that 'scanned images are semi-structured because they have metadata,' but the DP-900 definition hinges on whether the data has a fixed schema (structured), flexible schema (semi-structured), or no schema (unstructured).

How to eliminate wrong answers

Option B is wrong because it misclassifies Source B (JSON with varying fields) as unstructured, but JSON is the classic example of semi-structured data due to its key-value pairs and flexible schema. Option C is wrong because it labels Source A (relational database with fixed columns) as semi-structured, but relational databases enforce a rigid schema (rows and columns) that defines structured data. Option D is wrong because it calls Source A semi-structured (should be structured) and Source C structured (should be unstructured), completely reversing the correct categorization.

Practice this question →

127

MCQeasy

Your team is migrating a data warehouse to Azure Synapse Analytics. You need to ensure that the data model supports both historical trend analysis and current-day reporting with minimal storage redundancy. Which table design pattern should you use?

A.Single flat table containing all attributes

B.Wide table with repeated customer attributes per order

C.Highly normalized design with many tables

D.Star schema with dimension and fact tables

AnswerD

This design is the industry-standard dimensional model for data warehousing, consisting of a central fact table that stores numeric measures and foreign keys, surrounded by denormalized dimension tables that describe business entities. It minimizes redundancy because each dimension attribute is stored once, while the fact table remains lean and scalable. Queries benefit from star join optimizations, efficient use of columnstore indexes, and the ability to pre-aggregate facts at different grain levels. In Azure Synapse Analytics, designers can hash-distribute fact tables on a key and replicate dimension tables to reduce data movement, directly improving analytical query performance.

Why this answer

The star schema is the correct choice because it separates business processes into fact tables (for measures like sales quantities) and dimension tables (for descriptive attributes like customer or date). This design directly supports both historical trend analysis (by joining facts with the date dimension) and current-day reporting (by filtering on the latest date) while minimizing storage redundancy through normalized dimensions. Azure Synapse Analytics is optimized for star schemas, leveraging columnstore indexes and distributed tables to accelerate such queries.

Exam trap

The trap here is that candidates often confuse 'normalization' (Option C) with data warehouse best practices, not realizing that star schemas intentionally denormalize dimensions to optimize for read-heavy analytical queries, while highly normalized designs are better suited for OLTP systems, not Azure Synapse Analytics.

How to eliminate wrong answers

Option A is wrong because a single flat table containing all attributes would cause massive data duplication and poor query performance, as every row repeats customer and product details for each order, leading to high storage costs and slow analytical scans. Option B is wrong because a wide table with repeated customer attributes per order introduces significant redundancy and update anomalies, making it inefficient for both historical analysis and current reporting, and it contradicts the goal of minimal storage redundancy. Option C is wrong because a highly normalized design with many tables (e.g., 3NF) requires complex joins across numerous tables, which degrades query performance in a data warehouse context and is not optimized for the analytical workloads that Synapse is designed for.

Practice this question →

128

MCQeasy

Which classification of data describes information that has a fixed schema and is organized into rows and columns, such as data found in a relational database table?

A.Unstructured data

B.Semi-structured data

C.Structured data

D.Transformed data

AnswerC

Structured data is information that conforms to a fixed schema, typically represented in tables with defined columns and rows. This is the fundamental format used by relational database management systems, where each table has a predetermined set of attributes and data types. If the question describes information with an explicit, predefined structure, structured data is the correct classification.

Why this answer

Structured data is defined by a fixed schema, where each data element adheres to a predefined data type and relationship, organized into rows and columns. This is the fundamental model of a relational database table, such as those in Azure SQL Database or SQL Server, where constraints like primary keys and foreign keys enforce the schema.

Exam trap

Microsoft often tests the distinction between structured and semi-structured data, where candidates mistakenly classify JSON or XML as structured because it has some organization, but the key differentiator is the rigid, predefined schema enforced by the database, not just the presence of tags or keys.

Why the other options are wrong

Unstructured data lacks a fixed schema and is not organized into rows and columns; it includes formats like text, images, and videos, which do not fit the relational table description.

Transformed data refers to data that has been processed or altered from its original form, not to data with a fixed schema organized into rows and columns. The question specifically describes structured data.

Practice this question →

129

MCQhard

A healthcare organization needs to store patient records that must be immutable and cannot be modified or deleted for 7 years due to regulatory compliance. Which Azure feature should they use?

A.Microsoft Purview

B.Azure Policy

C.Azure Blob Storage immutable storage

D.Microsoft Defender for Cloud

AnswerC

Provides WORM (write once, read many) capability for compliance.

Why this answer

Azure Blob Storage immutable storage is correct because it provides WORM (Write Once, Read Many) capabilities that prevent data from being modified or deleted for a specified retention period. This directly meets the regulatory requirement for patient records to remain immutable for 7 years, as the policy is enforced at the storage level and cannot be overridden by any user, including administrators.

Exam trap

The trap here is that candidates confuse Azure Policy (which enforces resource-level compliance rules) with data-level immutability, but Azure Policy cannot prevent data modification within a blob—only Azure Blob Storage immutable storage provides that guarantee.

How to eliminate wrong answers

Option A is wrong because Microsoft Purview is a data governance and catalog service for discovering and classifying data, not a storage-level immutability enforcement mechanism. Option B is wrong because Azure Policy enforces organizational rules and compliance across Azure resources (e.g., restricting resource locations), but it cannot prevent modification or deletion of data within a storage blob. Option D is wrong because Microsoft Defender for Cloud is a security posture management and threat protection service, not a data immutability feature.

Practice this question →

130

MCQmedium

A retail company wants to run real-time analytics on streaming clickstream data from their website. Which Azure service should they use to ingest and process the data?

A.Azure Analysis Services

B.Azure Data Lake Storage

C.Azure SQL Database

D.Azure Stream Analytics

AnswerD

Azure Stream Analytics is a fully managed, real-time data stream processing engine that can continuously ingest events from Azure Event Hubs, IoT Hub, and Blob Storage, then apply time-windowed SQL-like queries without infrastructure management. It supports sub-second to minute-level latencies, event ordering and late-arrival handling, and can produce alerting, dashboards, or aggregated results in real time. Because it is purpose-built for streaming data, it is the appropriate choice for the retail company’s requirement to run real-time analytics on a live stream rather than storing and batch-processing it later.

Why this answer

Azure Stream Analytics is a real-time analytics and event-processing engine designed to ingest, process, and analyze high-velocity streaming data, such as clickstream data from a website. It can directly consume data from Azure Event Hubs or IoT Hub and output results to sinks like Power BI, Azure SQL Database, or Azure Data Lake Storage, making it the correct choice for real-time analytics on streaming data.

Exam trap

The trap here is that candidates often confuse Azure Stream Analytics with Azure SQL Database or Azure Data Lake Storage, mistakenly thinking a traditional database or storage service can handle real-time streaming ingestion and processing, when in fact they lack the necessary low-latency, event-driven architecture.

How to eliminate wrong answers

Option A is wrong because Azure Analysis Services is an OLAP engine for creating semantic models and running ad-hoc analytical queries on pre-processed data, not for ingesting or processing real-time streaming data. Option B is wrong because Azure Data Lake Storage is a scalable and secure data lake for storing large volumes of raw or processed data, but it does not provide real-time stream ingestion or processing capabilities. Option C is wrong because Azure SQL Database is a relational database service for storing and querying structured data, not designed for high-throughput, low-latency stream ingestion or real-time event processing.

Practice this question →

131

MCQeasy

A healthcare organization stores patient medical records in a relational database with columns such as PatientID, Name, and DateOfBirth. They also store radiology images as DICOM files in Azure Blob Storage. Which statement correctly classifies these data types?

A.Both patient records and radiology images are structured data.

B.Patient records are semi-structured, and radiology images are unstructured.

C.Patient records are structured, and radiology images are unstructured.

D.Patient records are unstructured, and radiology images are semi-structured.

AnswerC

In a relational database, patient records are assigned to tables with predefined columns and data types, such as integer IDs, VARCHAR names, and DATE fields, making them structured data that can be queried with SQL. Radiology images, by contrast, are stored as DICOM binary files containing raw pixel data; they lack a schema and cannot be queried directly, so they are unstructured. This distinction drives storage choices, such as using SQL for records and BLOB/object storage for images.

Why this answer

Patient records in a relational database with fixed columns like PatientID, Name, and DateOfBirth adhere to a predefined schema, making them structured data. Radiology images stored as DICOM files in Azure Blob Storage have no internal schema or tabular format and are therefore unstructured data. Option C correctly matches these classifications.

Exam trap

The trap here is conflating 'semi-structured' with 'structured' or 'unstructured'—candidates often misclassify relational database records as semi-structured because they have multiple columns, but the key is the rigid schema enforced by the relational model.

Why the other options are wrong

Patient records in a relational database with defined columns like PatientID, Name, and DateOfBirth are structured data, not semi-structured. Radiology images as DICOM files in Blob Storage are unstructured, not structured.

Patient records in a relational database with fixed columns like PatientID, Name, and DateOfBirth are structured data, not semi-structured. Radiology images as DICOM files are binary files without a predefined schema, making them unstructured.

Patient records in a relational database with fixed columns are structured data, not unstructured. Radiology images as DICOM files are binary files without a predefined schema, making them unstructured, not semi-structured.

Practice this question →

132

MCQmedium

A data analyst needs to combine sales data from Azure SQL Database and inventory data from Azure Cosmos DB into a single Power BI report. Which Power BI feature should they use?

A.Power Query

B.Power BI Desktop

C.DAX formulas

D.Dataflows

AnswerA

Power Query is the data transformation and connectivity engine built into Power BI Desktop, Excel, and other products. It lets analysts connect to Azure SQL Database, preview and shape the data, and then combine it with other sources using merge (join) or append (union) operations. Its M language provides precise control over transforms before data is loaded into the model, making it the correct direct tool for combining sales data.

Why this answer

Power Query is the correct feature because it is the data connection and transformation engine in Power BI that allows you to connect to multiple data sources—such as Azure SQL Database and Azure Cosmos DB—and combine them into a single dataset for reporting. It provides a graphical interface to merge, append, and shape data from disparate sources before loading it into the data model, which is exactly what the analyst needs to do.

Exam trap

The trap here is that candidates often confuse the tool (Power BI Desktop) with the feature (Power Query), or they mistakenly think DAX is used for data integration, when in fact DAX operates only on data already in the model, not on source connections.

How to eliminate wrong answers

Option B (Power BI Desktop) is wrong because Power BI Desktop is the application that hosts Power Query, not the specific feature for combining data from multiple sources; it is the environment where the report is built, not the tool for data integration. Option C (DAX formulas) is wrong because DAX (Data Analysis Expressions) is used for creating calculated columns, measures, and custom aggregations within the data model after data is loaded, not for connecting to or combining data from different source systems. Option D (Dataflows) is wrong because Dataflows are a cloud-based ETL tool for preparing and reusing data across workspaces, but they are not the direct feature used within a single Power BI Desktop report to combine live connections from Azure SQL Database and Azure Cosmos DB; Power Query is the immediate tool for that task.

Practice this question →

133

MCQeasy

A data analyst needs to query a large dataset stored in Azure Blob Storage using serverless SQL pool in Azure Synapse Analytics. Which data format should they use to minimize storage costs while still supporting efficient querying?

A.CSV

B.JSON

C.Parquet

D.Avro

AnswerC

Parquet is a columnar storage format that groups values by column, enabling modern compression techniques like dictionary and run-length encoding to dramatically reduce storage footprint. Analytical engines can push predicate filters and column projections down to the file layer, reading only the needed columns and row groups, which minimizes I/O and query latency. This design makes Parquet the optimal choice for large analytical workloads in Azure, including Azure Synapse, Databricks, and Data Lake Storage.

Why this answer

Parquet is a columnar storage format that compresses data efficiently and supports predicate pushdown, allowing serverless SQL pool in Azure Synapse to read only the necessary columns and rows. This minimizes storage costs while maintaining high query performance, unlike row-oriented formats such as CSV or JSON.

Exam trap

The trap here is that candidates often assume all compressed formats (like Avro) are equally efficient for analytics, but Azure Synapse serverless SQL pool is specifically optimized for columnar formats like Parquet, not row-oriented ones.

How to eliminate wrong answers

Option A is wrong because CSV is a row-oriented, plain-text format with no compression or schema, leading to larger storage footprint and slower queries due to full file scans. Option B is wrong because JSON is also row-oriented and self-describing, resulting in poor compression and inefficient querying as serverless SQL pool must parse the entire file. Option D is wrong because Avro, while compact and schema-based, is row-oriented and not optimized for analytical queries that benefit from columnar storage and predicate pushdown.

Practice this question →

134

MCQmedium

Your team is building a real-time dashboard for monitoring website traffic. The data source is streaming click events from Azure Event Hubs. The dashboard must update within seconds. Which Azure service should you use to process the stream?

A.Azure Stream Analytics

B.Azure Synapse Pipelines

C.Azure Data Factory

D.Azure Databricks Structured Streaming

AnswerA

Azure Stream Analytics is a fully managed stream processing engine that natively supports real-time ingestion from Azure Event Hubs and IoT Hub. It provides sub-second latency via continual SQL-like queries over temporal windows, and it has a built-in Power BI output adapter, making it ideal for live dashboards. Unlike batch tools, it executes queries continuously on unbounded streams, delivering results as events arrive.

Why this answer

Azure Stream Analytics is designed for real-time stream processing with low-latency output, making it ideal for processing click events from Event Hubs and updating a dashboard within seconds. It provides a SQL-like query language to define transformations and can output directly to Power BI or other visualization tools for near-instantaneous dashboard updates.

Exam trap

Microsoft often tests the misconception that any data processing service can handle streaming, but the trap here is that Azure Data Factory and Synapse Pipelines are batch-oriented, while Databricks Structured Streaming, though capable, is not the simplest or most cost-effective choice for a quick, SQL-based real-time dashboard.

How to eliminate wrong answers

Option B (Azure Synapse Pipelines) is wrong because it is primarily an orchestration tool for data movement and transformation in batch scenarios, not for real-time stream processing with sub-second latency. Option C (Azure Data Factory) is wrong because it is a cloud-based ETL service for batch data integration and scheduling, lacking native support for continuous streaming inputs like Event Hubs. Option D (Azure Databricks Structured Streaming) is wrong because while it can process streams, it is a more complex, code-heavy solution (Spark-based) that is overkill for simple dashboard updates and does not offer the same turnkey, low-latency output to Power BI as Stream Analytics.

Practice this question →

135

MCQhard

A healthcare organization must store patient health records for 7 years to meet regulatory requirements. After 7 years, data must be deleted immediately. They use Azure Blob Storage. Which policy should they implement?

A.Soft delete policy

B.Legal hold policy

C.Lifecycle management policy with deletion after 7 years

D.Time-based retention policy

AnswerD

A time-based retention policy, often implemented as immutable blob storage, locks data in a write-once, read-many (WORM) state for a specified interval, preventing modification or deletion until that interval elapses. In Azure, you set a retention period in days or years, and the service enforces the policy globally, blocking any attempts to overwrite or remove the data. This satisfies the healthcare requirement to preserve patient records for exactly seven years, after which deletion is allowed.

Why this answer

A time-based retention policy (immutability policy) in Azure Blob Storage ensures that blobs are stored in a WORM (Write Once, Read Many) state for a specified period, preventing modification or deletion. After the retention period expires, the data can be deleted immediately, meeting the 7-year regulatory requirement. This policy is designed specifically for compliance scenarios where data must be preserved for a fixed duration and then removed.

Exam trap

The trap here is that candidates confuse lifecycle management (which automates deletion but does not prevent premature modification) with time-based retention (which enforces immutability during the retention period), leading them to choose lifecycle management despite its inability to guarantee data integrity before deletion.

How to eliminate wrong answers

Option A is wrong because a soft delete policy only protects against accidental deletion by retaining deleted blobs for a configurable period, but it does not enforce a minimum retention duration or guarantee immediate deletion after 7 years. Option B is wrong because a legal hold policy indefinitely prevents deletion or modification of blobs for legal or investigation purposes, with no automatic expiration, so it cannot enforce a fixed 7-year retention followed by deletion. Option C is wrong because a lifecycle management policy can delete blobs after a specified age, but it does not prevent modification or deletion during the retention period, meaning data could be altered or deleted before 7 years, violating compliance requirements.

Practice this question →

136

MCQmedium

An e-commerce application processes customer orders. When an order is placed, the system must decrement the inventory count and process the payment. The application ensures that either both operations complete successfully or both are rolled back if any error occurs. Which database property does this guarantee?

A.Atomicity

B.Consistency

C.Isolation

D.Durability

AnswerA

Atomicity is the ACID property that treats a transaction as a single, indivisible unit of work. If any statement within the transaction (such as updating inventory or recording the order) fails, the entire transaction is rolled back, leaving the database exactly as it was before the transaction began. This all-or-nothing behavior prevents partial updates, ensuring that a customer order is either fully recorded or not recorded at all.

Why this answer

Atomicity ensures that a transaction is treated as a single, indivisible unit of work: either all operations within it (decrement inventory and process payment) complete successfully, or none are applied. If any part fails, the database rolls back all changes, maintaining the 'all-or-nothing' guarantee. This is the core property described in the scenario.

Exam trap

The trap here is that candidates confuse atomicity with consistency, thinking that 'keeping data valid' is the same as 'all-or-nothing execution,' but atomicity is specifically about the transaction's indivisibility, not about data integrity rules.

Why the other options are wrong

Consistency ensures that a transaction transforms the database from one valid state to another, but the question specifically describes the 'all-or-nothing' execution of multiple operations, which is the definition of atomicity, not consistency.

Isolation ensures concurrent transactions do not interfere, but the question describes a single transaction that must complete entirely or not at all, which is Atomicity, not Isolation.

Durability ensures that once a transaction is committed, its changes persist even after a system failure. The question describes a scenario where operations are rolled back on error, which is about atomicity (all-or-nothing), not durability.

Practice this question →

137

MCQeasy

A company stores three types of data: 1) Customer orders in a SQL table with fixed columns for OrderID, CustomerID, and OrderDate. 2) Product reviews in XML files where each file contains varying tags such as <rating> and <comment>. 3) Video files of product demonstrations. Which of the following correctly classifies these data types in order from first to third?

A.Structured, Semi-structured, Unstructured

B.Semi-structured, Unstructured, Structured

C.Unstructured, Structured, Semi-structured

D.Structured, Unstructured, Semi-structured

AnswerA

This classification is correct because each data type is matched to its intrinsic format. Customer orders in a SQL table have a fixed schema with rows and columns, enforcing structured data. XML files use custom tags and a hierarchical tag-based format that does not require a rigid relational schema, making them semi-structured. Video files are binary streams with no predefined data model or queryable structure, so they are unstructured.

Why this answer

Customer orders in a SQL table with fixed columns (OrderID, CustomerID, OrderDate) are structured data because they conform to a rigid schema. Product reviews in XML files with varying tags like <rating> and <comment> are semi-structured data because they have tags/metadata but no fixed schema. Video files of product demonstrations are unstructured data because they lack any predefined data model or organization.

Exam trap

Microsoft often tests the distinction between semi-structured and unstructured data by using XML/JSON as semi-structured examples, where candidates mistakenly classify them as unstructured due to the lack of a fixed schema, ignoring the presence of metadata tags.

Why the other options are wrong

The order is incorrect: video files are unstructured, not semi-structured; product reviews in XML are semi-structured, not unstructured.

The third data type (video files) is unstructured, not semi-structured. Semi-structured data has some organizational properties (like XML tags), but video files lack any structure or schema.

Practice this question →

138

MCQeasy

A data analyst receives a dataset containing customer order details stored in a CSV file, a JSON file with product reviews, and a folder of JPEG images of products. Which of the following correctly categorizes these data types from most structured to least structured?

A.CSV → JPEG → JSON

B.JSON → CSV → JPEG

C.CSV → JSON → JPEG

D.JPEG → JSON → CSV

AnswerC

CSV is the most structured because it enforces a tabular schema—every row has the same ordered columns and each field is a scalar value. JSON is semi-structured: it uses named key-value pairs and can nest arrays/objects, but no fixed schema is required and structure can vary per record. JPEG is unstructured: its binary encoding represents compressed pixel data, not queryable fields or relationships. Ordering them most-to-least structured therefore must place CSV first, JSON second, and JPEG last.

Why this answer

CSV files are highly structured with rows and columns defined by a schema, making them the most structured. JSON files are semi-structured, using key-value pairs and nested objects that allow flexibility but lack a fixed schema. JPEG images are unstructured binary data with no inherent schema, so the correct order from most to least structured is CSV → JSON → JPEG, making option C correct.

Exam trap

Microsoft often tests the misconception that JSON is more structured than CSV because it uses named keys, but in reality, CSV's fixed schema makes it more structured than JSON's flexible, self-describing format.

Why the other options are wrong

CSV is structured (rows/columns), JSON is semi-structured (key-value pairs), and JPEG is unstructured (binary). Option A incorrectly places JSON after JPEG, but JSON is more structured than JPEG.

JSON is less structured than CSV because CSV has a strict tabular schema with rows and columns, while JSON allows nested, hierarchical data without a fixed schema. JPEG images have no inherent structure, so the correct order from most to least structured is CSV → JSON → JPEG.

JPEG images are unstructured data, while JSON is semi-structured and CSV is structured. Ordering JPEG before JSON and CSV incorrectly suggests images are more structured than text-based formats.

Practice this question →

139

MCQhard

A company's data engineering team uses Azure Data Factory to orchestrate a pipeline that ingests data from Azure Blob Storage, transforms it using Azure Databricks, and loads it into Azure Synapse Dedicated SQL Pool. The pipeline fails intermittently due to transient errors. Which pattern should they implement to improve reliability?

A.Replace Azure Databricks with Azure Functions

B.Increase the pipeline timeout to 24 hours

C.Split the pipeline into multiple smaller pipelines

D.Configure retry policy with exponential backoff on activities

AnswerD

Configuring a retry policy on the failing activity causes Azure Data Factory to automatically re-attempt the operation when it detects an error, and adding exponential backoff spaces out those attempts so the transient condition (such as throttling or a temporary service outage) has time to clear. With a retry count and interval set on the activity, you avoid hard failures caused by intermittent issues without manual intervention. This is the standard, directly-scoped solution for transient errors in ADF pipelines.

Why this answer

Configuring a retry policy with exponential backoff on the Azure Data Factory activities directly addresses transient errors (e.g., network blips, throttling) by automatically retrying the failed activity after increasing delays. This pattern is specifically designed for intermittent failures and is a built-in feature of Azure Data Factory, improving pipeline reliability without architectural changes.

Exam trap

The trap here is that candidates confuse increasing timeout (Option B) with retry logic, or think splitting pipelines (Option C) improves reliability against transient errors, when in fact only a retry policy with backoff directly mitigates intermittent failures in Azure Data Factory.

How to eliminate wrong answers

Option A is wrong because replacing Azure Databricks with Azure Functions would remove the distributed compute engine needed for complex transformations, and Azure Functions are not designed for long-running, data-intensive ETL workloads. Option B is wrong because increasing the pipeline timeout to 24 hours does not handle transient errors; it only allows the pipeline to run longer, but a single transient failure still causes the entire pipeline to fail. Option C is wrong because splitting the pipeline into multiple smaller pipelines does not inherently handle transient errors; it may reduce blast radius but does not provide automatic retry logic for intermittent failures.

Practice this question →

140

MCQeasy

A retail company operates an online store. The store processes each customer's order immediately upon submission, updating inventory and payment records in real-time. Additionally, the company's business analysts run weekly reports that aggregate sales data over the past month to identify trends. Which of the following correctly describes the two workload types represented in this scenario?

A.The order processing is an OLTP workload; the weekly reporting is an OLAP workload.

B.The order processing is an OLAP workload; the weekly reporting is an OLTP workload.

C.Both workloads are OLTP workloads.

D.Both workloads are batch processing workloads.

AnswerA

This correctly distinguishes the two workloads. Order processing captures discrete, high-frequency events such as placing an item in a cart and confirming payment, which are classic OLTP transactions requiring atomicity and low latency. Weekly reporting, by contrast, reads and aggregates large volumes of historical order data across the week to produce revenue summaries, a classic OLAP analytical workload.

Why this answer

The order processing system handles individual transactions (inserts/updates) in real-time, which is the hallmark of an Online Transaction Processing (OLTP) workload. The weekly reporting aggregates large volumes of historical data for trend analysis, which is an Online Analytical Processing (OLAP) workload. OLTP is optimized for high-volume, low-latency writes, while OLAP is optimized for complex read-heavy queries over large datasets.

Exam trap

The trap here is that candidates confuse the real-time nature of order processing with batch processing or mistakenly think that any reporting is OLTP, failing to recognize that OLAP is specifically designed for analytical queries over historical data.

Why the other options are wrong

Order processing involves real-time transactions (OLTP), not analytical queries (OLAP). Weekly reporting aggregates historical data (OLAP), not transactional processing (OLTP).

The weekly reporting aggregates historical data for trend analysis, which is an OLAP workload, not OLTP. OLTP is for real-time transaction processing, not for both workloads.

The weekly reporting is not batch processing in the traditional sense; it is an OLAP workload that aggregates data for analysis, not a batch processing workload that processes large volumes of data in batches without real-time requirements.

Practice this question →

141

MCQhard

A retail company uses Azure SQL Database to store transactional data. They need to ensure that reporting queries do not impact the performance of the transactional workload. Which solution should you recommend?

A.Configure a read replica in Azure SQL Database

B.Increase the DTU or vCore limit of the database

C.Add indexes to the reporting tables

D.Partition the largest tables by date

AnswerA

Configuring a read replica in Azure SQL Database creates a separate, readable secondary instance that handles reporting and analytical queries without consuming the primary's CPU, I/O, or locks. Azure SQL Database's active geo-replication or built-in read scale-out allows the replica to maintain a transactionally consistent (though potentially slightly delayed) copy of the data, enabling reporting workloads to run alongside OLTP without interference. This is the correct approach because it physically isolates the reporting load from the transactional database engine.

Why this answer

A read replica in Azure SQL Database allows reporting queries to be offloaded to a read-only copy of the database, isolating them from the primary transactional workload. This ensures that reporting activities do not consume resources (CPU, IO, memory) on the primary instance, preventing performance degradation for transactional operations.

Exam trap

The trap here is that candidates often confuse scaling up the database (Option B) with workload isolation, not realizing that scaling up only adds more resources but does not separate read and write operations, so reporting queries can still cause blocking or resource contention on the primary.

How to eliminate wrong answers

Option B is wrong because increasing DTU or vCore limits scales up the entire database, which does not isolate reporting queries from transactional workloads; both workloads still compete for the same resources. Option C is wrong because adding indexes to reporting tables can improve query performance but does not prevent reporting queries from impacting the transactional workload, as they still run on the same database engine. Option D is wrong because partitioning tables by date can improve query performance and manageability but does not provide workload isolation; reporting queries still execute on the same primary database and can contend with transactional operations.

Practice this question →

142

MCQeasy

A retail company uses a point-of-sale (POS) system that records each sales transaction in a database. Each transaction involves reading the current inventory, updating the stock level, and recording the sale. The database must ensure that concurrent transactions do not interfere with each other, so that one transaction does not see partially updated data from another. Which property of a database transaction ensures this isolation?

A.Atomicity

B.Consistency

C.Isolation

D.Durability

AnswerC

Isolation is the ACID property that separates the effects of concurrent transactions so that one transaction cannot see the intermediate, uncommitted state of another. Without isolation, a POS system could read inventory levels that another sale is in the middle of updating, leading to overselling or duplicate charges. Isolation ensures that the concurrent execution produces the same result as some serial order of the transactions, thereby preventing dirty reads, non-repeatable reads, and phantom reads. This directly addresses the retail scenario described.

Why this answer

Isolation ensures that concurrent transactions do not interfere with each other, so each transaction sees a consistent snapshot of the database as if it were the only transaction running. In the POS scenario, isolation prevents one transaction from reading partially updated inventory data from another transaction, which could lead to overselling or stock discrepancies. This property is typically implemented through locking mechanisms or multi-version concurrency control (MVCC).

Exam trap

The trap here is that candidates often confuse isolation with atomicity, thinking that 'not seeing partially updated data' is about the transaction being all-or-nothing, when in fact it is about preventing interference between concurrent transactions.

How to eliminate wrong answers

Option A is wrong because atomicity ensures that a transaction is treated as a single, indivisible unit that either fully completes or fully rolls back, but it does not control how concurrent transactions interact. Option B is wrong because consistency ensures that a transaction brings the database from one valid state to another, preserving integrity constraints, but it does not manage concurrent access. Option D is wrong because durability guarantees that once a transaction is committed, its changes persist even in the event of a system failure, but it has no role in isolating concurrent transactions.

Practice this question →

143

MCQeasy

A company stores customer contact information in a table with columns for CustomerID, Name, Email, and Phone. They also store customer support chat transcripts as plain text files. Which of the following correctly classifies these data types?

A.Both are structured data

B.Customer contact information is structured; chat transcripts are semi-structured

C.Customer contact information is structured; chat transcripts are unstructured

D.Both are semi-structured

AnswerC

Customer contact information is structured because it resides in a table with a fixed, predefined schema: each column (name, phone, email) has a strict data type and every row must conform to that schema, making it directly queryable via SQL. Chat transcripts, by contrast, are unstructured because the conversation is free-flowing natural language with no fixed format, row/column structure, or guaranteed fields; the text is stored as a whole and cannot be reliably queried by column value without additional processing like text mining or NLP.

Why this answer

Customer contact information stored in a table with columns like CustomerID, Name, Email, and Phone is structured data because it has a fixed schema with rows and columns. Chat transcripts stored as plain text files have no predefined schema or organization, making them unstructured data. Therefore, option C correctly classifies the contact info as structured and the chat transcripts as unstructured.

Exam trap

The trap here is that candidates often confuse semi-structured data (like JSON or XML) with unstructured data (like plain text), incorrectly classifying chat transcripts as semi-structured because they contain some implicit structure (e.g., timestamps or user names) when in fact they lack a formal schema or metadata tags.

Why the other options are wrong

Customer contact information in a table with defined columns (CustomerID, Name, Email, Phone) is structured data, but chat transcripts as plain text files have no predefined schema or organization, making them unstructured, not structured.

Chat transcripts are plain text files without any inherent structure or metadata, making them unstructured data, not semi-structured (which requires tags or markers like JSON or XML).

Chat transcripts are plain text files without a predefined schema or structure, making them unstructured data, not semi-structured. Semi-structured data (e.g., JSON, XML) has tags or markers to separate elements, which plain text lacks.

Practice this question →

144

MCQmedium

A marketing team needs to analyze customer purchase history data stored in Azure SQL Database. They want to create interactive dashboards with drill-down capabilities. Which Microsoft tool should they use?

A.Power BI

B.Azure Data Studio

C.Microsoft Excel

D.Azure Analysis Services

AnswerA

Power BI is designed for interactive dashboards with drill-down capabilities.

Why this answer

Power BI is the correct tool because it is designed specifically for creating interactive dashboards with drill-down capabilities using data from Azure SQL Database. It connects directly to Azure SQL Database via built-in connectors, allowing users to build visualizations that support hierarchical navigation and real-time filtering.

Exam trap

The trap here is that candidates confuse Azure Analysis Services as a visualization tool, when in fact it is a backend analytical engine that requires Power BI or another client for dashboard creation.

How to eliminate wrong answers

Option B is wrong because Azure Data Studio is a database management and query tool, not a dashboarding or visualization tool; it lacks native interactive dashboard and drill-down features. Option C is wrong because Microsoft Excel can create charts and pivot tables, but it does not provide native drill-down capabilities for interactive dashboards and is not optimized for real-time, cloud-based data exploration. Option D is wrong because Azure Analysis Services is a data modeling and analytical engine that provides OLAP cubes and tabular models, but it is not a front-end visualization tool; it requires a separate client like Power BI to render interactive dashboards.

Practice this question →

145

MCQeasy

The exhibit shows a KQL query in Azure Data Explorer. What is the output of this query?

A.Bottom 5 states by total property damage

B.Top 5 states by total property damage

C.All states with total property damage

D.All storm events after 2024-01-01

AnswerB

This query filters storm events to those on or after 2024-01-01, groups the remaining rows by State using `summarize`, and computes the sum of DamageProperty for each state. The subsequent `top 5 by DamageProperty desc` operator sorts these state-level sums in descending order and returns the first five rows, which are exactly the five states with the highest total property damage. The result is a ranked list of the top 5 states by total damage.

Why this answer

The KQL query uses `summarize` to aggregate total property damage by state, then `top 5 by total_property_damage` to return the five states with the highest total damage. The `desc` argument (default) orders the results in descending order, making option B correct.

Exam trap

The trap here is that candidates may confuse `top` with `take` or `limit`, forgetting that `top` implicitly sorts in descending order unless `asc` is specified, leading them to think it returns the bottom values or all rows.

How to eliminate wrong answers

Option A is wrong because `top 5` returns the highest values, not the lowest; to get bottom 5, you would need `top 5 by total_property_damage asc`. Option C is wrong because `top 5` limits the output to exactly five rows, not all states. Option D is wrong because the query does not filter by date; it aggregates all storm events regardless of date.

Practice this question →

146

MCQeasy

A company stores customer orders in a database. Each order has an OrderID (integer), CustomerName (text), OrderDate (date), and a JSON column for order details that contains varying fields such as discount codes or gift messages. Which statement best describes the data types in this table?

A.The table stores only structured data.

B.The table stores both structured and semi-structured data.

C.The table stores only unstructured data.

D.The table stores only semi-structured data.

AnswerB

The OrderID, CustomerName, and OrderDate columns have fixed data types and enforce a rigid schema, exactly fitting the structured category. In contrast, the JSON column stores order details that can differ per customer order, such as optional fields or nested line items, which is typical of semi-structured data. A single table can therefore mix both categories, and that is precisely what this design does.

Why this answer

The table includes structured columns (OrderID integer, CustomerName text, OrderDate date) and a JSON column for order details, which stores semi-structured data because JSON allows flexible schemas with varying fields like discount codes or gift messages. This combination of fixed-schema columns and a schema-less JSON column means the table holds both structured and semi-structured data, making option B correct.

Exam trap

The trap here is that candidates often mistake JSON for unstructured data, but JSON is semi-structured because it has a logical structure (key-value pairs) even though the schema is flexible, leading them to incorrectly choose option C.

How to eliminate wrong answers

Option A is wrong because the JSON column contains semi-structured data, not purely structured data, as structured data requires a fixed schema with consistent fields. Option C is wrong because unstructured data (e.g., images, videos, raw text files) is not present; JSON is semi-structured, not unstructured. Option D is wrong because the table also includes structured columns (OrderID, CustomerName, OrderDate) with fixed data types, so it does not store only semi-structured data.

Practice this question →

147

MCQhard

The exhibit shows a Kusto Query Language (KQL) query run in Azure Data Explorer. What is the output of this query?

A.All storm events in Texas with property damage

B.The total property damage for all event types in Texas

C.The top 5 event types in Texas by total property damage

D.A list of the top 5 property damage amounts in Texas

AnswerC

This is exactly what the query does: summarize by EventType groups the Texas storm records by event category, sum(PropertyDamage) totals the damage within each group, and the top operator (or order by + take) selects the five highest groups. Each output row pairs an EventType with its aggregated damage, which is the standard KQL pattern for a ranked breakdown. The result therefore identifies which event types had the most total property damage in Texas.

Why this answer

The query uses `summarize sum(PropertyDamage) by EventType` to aggregate total property damage per event type, then `top 5 by TotalPropertyDamage` to return the five event types with the highest totals. The `where State == 'TEXAS'` filter ensures only Texas storms are considered. This directly yields the top 5 event types in Texas by total property damage.

Exam trap

The trap here is that candidates confuse 'top 5 property damage amounts' (raw values) with 'top 5 event types by total property damage' (aggregated categories), or they think the query lists individual events rather than summarized groups.

How to eliminate wrong answers

Option A is wrong because the query does not list individual storm events; it aggregates damage by event type, so it cannot output 'all storm events'. Option B is wrong because the query groups by EventType and returns multiple rows (top 5), not a single total for all event types combined. Option D is wrong because the query outputs event types, not raw property damage amounts; the `top 5` operator returns the entire row (EventType and TotalPropertyDamage), not just the damage values.

Practice this question →

148

MCQhard

A banking application processes a funds transfer transaction consisting of two steps: debit $100 from Account A and credit $100 to Account B. If the system crashes after debiting Account A but before crediting Account B, the database automatically reverts the debit, restoring Account A to its original balance. Which ACID property guarantees this behavior?

A.Atomicity

B.Consistency

C.Isolation

D.Durability

AnswerA

Atomicity is the correct property here because it enforces the all-or-nothing execution of a transaction. In this funds transfer, the debit step was written, but the corresponding credit never completed before the crash. Atomicity requires the entire transaction to be treated as a single, indivisible unit, so the partial debit must be rolled back and the account restored to its original state. Without atomicity, a system failure could leave a half-applied transaction, corrupting financial records.

Why this answer

Atomicity ensures that a transaction is treated as a single, indivisible unit of work. In this scenario, the debit and credit are part of one transaction; if the system crashes after the debit but before the credit, the database management system (DBMS) automatically rolls back the entire transaction, undoing the debit to restore Account A's original balance. This all-or-nothing behavior is the defining characteristic of atomicity.

Exam trap

The trap here is that candidates often confuse atomicity with consistency, thinking that 'restoring the original balance' is about maintaining data rules, when in fact it is the rollback of an incomplete transaction that demonstrates atomicity.

How to eliminate wrong answers

Option B (Consistency) is wrong because consistency ensures that a transaction brings the database from one valid state to another, preserving all defined rules (e.g., constraints, triggers), but it does not inherently handle crash recovery or rollback of partial changes. Option C (Isolation) is wrong because isolation governs how concurrent transactions are executed independently to prevent interference, not how a single transaction recovers from a crash. Option D (Durability) is wrong because durability guarantees that once a transaction is committed, its changes persist even after a system failure; it does not apply to uncommitted transactions that need to be rolled back.

Practice this question →

149

MCQhard

You are designing a data lake architecture for a large enterprise. You need to organize data into zones (raw, curated, and analytics) and enforce data lineage tracking. Which Azure service should you use to catalog and govern the data?

A.Azure Synapse Analytics

B.Azure Data Factory

C.Microsoft Purview

D.Azure Databricks

AnswerC

Microsoft Purview is a unified data governance and cataloging service that automatically scans Azure, on-premises, and multi-cloud sources, building a data map of technical and business metadata. It provides a searchable catalog, sensitive data classification, glossary, and end-to-end lineage across various data processes. This makes Purview the correct choice for governing a data lake, ensuring data is discoverable, understandable, and compliant.

Why this answer

Microsoft Purview is the correct choice because it is a unified data governance service designed specifically for cataloging data assets, tracking lineage across hybrid and multi-cloud environments, and enforcing data policies. Unlike the other options, Purview provides out-of-the-box lineage scanning, a business glossary, and automated classification, making it the appropriate tool for organizing data into zones and ensuring end-to-end lineage in a data lake architecture.

Exam trap

The trap here is that candidates confuse data integration or analytics services (like Azure Data Factory or Synapse) with a dedicated governance and cataloging tool, assuming lineage tracking is a built-in feature of those services rather than a separate function provided by Microsoft Purview.

How to eliminate wrong answers

Option A is wrong because Azure Synapse Analytics is an analytics service that combines data warehousing and big data processing, but it does not provide native data cataloging or lineage tracking capabilities beyond basic metadata; it relies on Purview for governance. Option B is wrong because Azure Data Factory is an ETL and data integration service that can capture lineage during pipeline runs, but it is not a dedicated catalog or governance tool; it lacks persistent cataloging, business glossary, and policy enforcement features. Option D is wrong because Azure Databricks is a unified analytics platform for data engineering and machine learning, but it does not include a built-in data catalog or lineage governance; it integrates with Purview for such purposes.

Practice this question →

150

MCQeasy

Your organization wants to run SQL queries on data stored in Azure Blob Storage without moving the data. Which Azure service supports this?

A.Azure SQL Database

B.Azure Analysis Services

C.Azure Synapse Serverless SQL pool

D.Azure Data Lake Storage Gen2

AnswerC

Azure Synapse Serverless SQL pool is a serverless query service that lets you run T-SQL queries directly against files stored in Azure Blob Storage or Azure Data Lake Storage Gen2. Using OPENROWSET or external tables, you can query CSV, JSON, or Parquet files without loading them into a database first. It scales on demand and charges by the amount of data processed, making it the correct choice for running SQL directly on stored data.

Why this answer

Azure Synapse Serverless SQL pool allows you to query data directly from Azure Blob Storage using T-SQL without moving the data. It uses a distributed query engine that reads files in place, supporting formats like Parquet, CSV, and JSON, making it ideal for ad-hoc analytics on stored data.

Exam trap

The trap here is that candidates confuse Azure Data Lake Storage Gen2 (a storage service) with a query engine, or assume Azure SQL Database can query external blobs natively, when in fact only Synapse Serverless SQL pool provides serverless T-SQL querying over Blob Storage without data movement.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a fully managed relational database that requires data to be imported or loaded into its storage; it cannot query external Blob Storage directly without additional tools like PolyBase. Option B is wrong because Azure Analysis Services is an OLAP engine that requires data to be loaded into its in-memory tabular model from sources like SQL databases; it does not support direct querying of Blob Storage. Option D is wrong because Azure Data Lake Storage Gen2 is a storage service built on Blob Storage with a hierarchical namespace, but it is not a query engine; it stores data but does not provide SQL query capabilities itself.

Practice this question →