Courseiva

CCNA Core Data Concepts Questions

75 of 235 questions · Page 3/4 · Core Data Concepts topic · Answers revealed

151
MCQeasy

A company stores customer information in a table with columns CustomerID, Name, Address, and PhoneNumber. Every row has values for all these columns, and the data follows a fixed schema. Which type of data does this represent?

A.Unstructured data
B.Semi-structured data
C.Structured data
D.Streaming data
AnswerC

This option is correct because a table with defined columns and specified data types is the hallmark of structured data, which conforms to a fixed schema typical of relational database management systems. Each customer record will have the same set of attributes, and constraints enforce consistency, allowing efficient querying with SQL. Since the company stores customer information in such a normalized, column-based format, the data is structured.

Why this answer

Structured data conforms to a fixed schema where each row has the same columns and data types. The table with CustomerID, Name, Address, and PhoneNumber, where every row contains values for all columns, perfectly fits this definition. This is typical of relational database tables (e.g., in Azure SQL Database) where the schema is enforced at the table level.

Exam trap

The trap here is that candidates may confuse 'semi-structured' with 'structured' because both have some organization, but the key distinction is that structured data enforces a fixed schema for all rows, while semi-structured data allows schema flexibility (e.g., missing attributes or varying data types).

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 the table has a fixed schema with defined columns. Option B is wrong because semi-structured data has some organizational properties (like tags or key-value pairs) but does not enforce a rigid schema across all records (e.g., JSON or XML files), unlike the fixed schema described. Option D is wrong because streaming data refers to data that is continuously generated and processed in real time (e.g., from IoT devices or event hubs), not to the static storage format of a table.

152
MCQeasy

A company stores employee records in a relational database table with columns EmployeeID, FirstName, LastName, Department. They also store employee handbooks as PDF files, and customer feedback as XML documents. Which of the following correctly classifies these data types?

A.Employee records: structured, Employee handbooks: semi-structured, Customer feedback: unstructured
B.Employee records: structured, Employee handbooks: unstructured, Customer feedback: semi-structured
C.Employee records: semi-structured, Employee handbooks: unstructured, Customer feedback: structured
D.Employee records: unstructured, Employee handbooks: semi-structured, Customer feedback: structured
AnswerB

Employee records stored in a relational database have a fixed, predefined schema with columns, data types, and constraints, making them structured data. Employee handbooks are PDF documents containing free-form prose and formatting without any uniform data model, so they are unstructured. Customer feedback in XML uses custom tags and nesting such as <response> and <sentiment> to describe the content, giving it a self-describing yet flexible schema that qualifies as semi-structured.

Why this answer

Employee records in a relational database table have a fixed schema (columns and data types), making them structured data. Employee handbooks stored as PDF files have no internal schema and are binary blobs, classifying them as unstructured data. Customer feedback stored as XML documents have a flexible, self-describing schema with tags, making them semi-structured data.

Exam trap

The trap here is confusing semi-structured data (which has some organizational properties like tags in XML) with unstructured data (which has no inherent structure), leading candidates to misclassify PDFs as semi-structured or XML as structured.

Why the other options are wrong

A

Employee handbooks as PDF files are unstructured data, not semi-structured, because they lack a predefined schema or tags. Customer feedback as XML documents is semi-structured, not unstructured, because XML has a hierarchical structure with tags.

C

Employee records in a relational database are structured (rows and columns), not semi-structured. Customer feedback as XML documents is semi-structured (tags with schema), not structured.

D

Employee records in a relational database are structured, not unstructured. Customer feedback as XML documents is semi-structured, not structured.

153
MCQeasy

A company wants to provide self-service analytics to business users who need to create reports and dashboards from data in Azure Synapse Analytics. Which tool should you recommend?

A.Power BI
B.Microsoft Excel
C.Azure Synapse Studio
D.Azure Data Studio
AnswerA

Power BI is a SaaS-based business analytics service specifically designed for self-service analytics. It provides a low-code environment with drag-and-drop visuals, natural language Q&A, and direct connectivity to a wide range of data sources. Power BI supports self-service data preparation via Power Query and enables governed sharing through workspaces, apps, and row-level security, making it the primary enterprise tool for business users to create and distribute interactive reports and dashboards independently.

Why this answer

Power BI is the correct tool because it is designed specifically for self-service analytics, enabling business users to create interactive reports and dashboards from data stored in Azure Synapse Analytics. Power BI connects directly to Synapse via its built-in connector, allowing users to build visualizations without writing code or relying on IT. This aligns with the requirement for business users to perform ad-hoc analysis and reporting.

Exam trap

The trap here is that candidates may confuse Azure Synapse Studio (a development tool) with a reporting tool, overlooking that Power BI is the designated Microsoft solution for self-service business intelligence and dashboards.

How to eliminate wrong answers

Option B is wrong because Microsoft Excel, while capable of basic data analysis and charting, lacks the native connectivity and interactive dashboard capabilities required for self-service analytics on Azure Synapse Analytics; it is not designed for real-time, large-scale data visualization. Option C is wrong because Azure Synapse Studio is a development and management interface for data engineers and data scientists to build pipelines, write SQL scripts, and manage Spark jobs, not a self-service reporting tool for business users. Option D is wrong because Azure Data Studio is a lightweight database management tool for querying and developing with SQL Server and Azure SQL, focused on developers and DBAs, not on creating business reports and dashboards.

154
MCQhard

Refer to the exhibit. The JSON shows an Azure Policy definition. Which effect should be used to proactively prevent creation of storage accounts without encryption?

A.AuditIfNotExists
B.Deny
C.Disabled
D.Append
AnswerB

The Deny effect actively intercepts resource creation or update requests and compares the request against the policy rule. If the condition matches, Azure returns a 403 Forbidden error, preventing the resource from being provisioned. This is the correct effect when the requirement is to block non-compliant resources, because it enforces the policy at request time and does not allow the deployment to continue.

Why this answer

The 'Deny' effect is correct because it proactively blocks the creation or update of a storage account that does not meet the encryption requirement, preventing non-compliant resources from being provisioned. This aligns with Azure Policy's ability to enforce compliance at resource creation time, rather than auditing or remediating after the fact.

Exam trap

The trap here is that candidates often confuse 'AuditIfNotExists' with a proactive block, not realizing it only logs non-compliance after the resource is created, whereas 'Deny' is the only effect that prevents creation entirely.

How to eliminate wrong answers

Option A (AuditIfNotExists) is wrong because it only logs a compliance warning when a storage account lacks encryption, but does not prevent its creation; it is a reactive audit effect. Option C (Disabled) is wrong because it turns off the policy entirely, allowing any storage account to be created without encryption. Option D (Append) is wrong because it adds additional fields to a resource during creation or update, but it cannot block a request; it is used to add tags or settings, not to deny non-compliant resources.

155
MCQmedium

You are designing a data solution for a retail company that needs to store transactional data (orders, payments) with strong consistency and support for complex joins. The data volume is moderate but expected to grow. Which Azure service should you choose?

A.Azure Cosmos DB
B.Azure Table Storage
C.Azure SQL Database
D.Azure Synapse Analytics
AnswerC

Azure SQL Database is a fully managed PaaS relational database built on the SQL Server engine, offering the full T-SQL language, complex joins, stored procedures, and ACID-compliant transactions. It delivers strong consistency by default, guaranteeing that every query sees the latest committed data, which is essential for retail operations like order management and inventory control. Its relational and transactional capabilities make it the natural choice for a transactional data solution that does not require the massive scale-out of analytics engines.

Why this answer

Azure SQL Database is a fully managed relational database that provides ACID transactions with strong consistency and supports complex joins via T-SQL. It is ideal for transactional workloads like orders and payments where data integrity and relational queries are critical, and it scales elastically to accommodate growing data volumes.

Exam trap

The trap here is that candidates confuse 'scalability' with 'suitability for transactional workloads' and choose Cosmos DB for its global distribution, overlooking that strong consistency and complex joins are not its core strengths.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a NoSQL database that prioritizes horizontal scaling and low latency over strong consistency (defaulting to eventual consistency unless configured for higher cost) and does not natively support complex joins across multiple entities. Option B is wrong because Azure Table Storage is a key-value NoSQL store with no support for joins, foreign keys, or ACID transactions, making it unsuitable for relational transactional data. Option D is wrong because Azure Synapse Analytics is a big data analytics service designed for large-scale data warehousing and complex analytical queries, not for OLTP workloads requiring real-time transactional consistency and frequent small writes.

156
MCQeasy

A bank processes online fund transfers. Each transaction must ensure that either both the debit from the sender's account and the credit to the receiver's account occur, or if any part fails, the entire transaction is rolled back. Which ACID property does this guarantee?

A.Atomicity
B.Consistency
C.Isolation
D.Durability
AnswerA

Atomicity is the ACID property that treats the entire fund transfer—debit source account and credit destination account—as one indivisible unit. If either SQL statement succeeds while the other fails, the transaction manager issues a rollback, discarding the partial write and restoring the original balances. Without this all-or-nothing guarantee, a bank could lose money or create funds from nothing during a network or application failure.

Why this answer

Atomicity ensures that a transaction is treated as a single, indivisible unit of work. In this fund transfer scenario, atomicity guarantees that both the debit and credit operations either complete successfully together or are fully rolled back if any part fails, preventing partial updates that could leave the system in an inconsistent state.

Exam trap

Microsoft often tests atomicity by describing a multi-step operation and asking which ACID property ensures the 'all-or-nothing' behavior, and the trap here is that candidates confuse atomicity with consistency, thinking that consistency alone prevents partial updates, when in fact atomicity is the property that enforces the rollback of incomplete transactions.

Why the other options are wrong

B

The question describes the 'all-or-nothing' execution of a transaction, which is the definition of atomicity, not consistency. Consistency ensures that a transaction brings the database from one valid state to another, preserving integrity constraints.

C

Isolation ensures that concurrent transactions do not interfere with each other, but the question describes a requirement that a transaction must complete entirely or not at all, which is atomicity, not isolation.

D

Durability ensures that once a transaction is committed, its changes persist even after a system failure. The question describes a transaction that either fully completes or fully rolls back, which is the definition of atomicity, not durability.

157
MCQeasy

A company maintains a database of customer orders that are updated frequently. They also store aggregated monthly sales reports that are generated once and then only read. Which statement correctly distinguishes these two types of data workloads?

A.Transactional data is optimized for write operations, and analytical data is optimized for read operations.
B.Transactional data must always be stored in non-relational databases, and analytical data in relational databases.
C.Analytical data always requires real-time processing, whereas transactional data is batch-processed.
D.Transactional data is read-only and analytical data is frequently updated.
AnswerA

In OLTP systems, transactional data is workload-optimized for high-frequency write operations using row-based storage, normalization to minimize redundancy, and fast lookup indexes to support ACID-compliant record-level changes. In contrast, analytical data in OLAP systems is structured for complex read patterns, using columnar storage, denormalized schemas, and pre-aggregated measures to speed up queries across large volumes. This fundamental separation drives the design of data pipelines and database engines.

Why this answer

Transactional workloads (like the frequently updated customer orders) are optimized for write-heavy operations, ensuring ACID compliance and data integrity, while analytical workloads (like the read-only monthly sales reports) are optimized for read-heavy operations, often using columnar storage or pre-aggregated data to speed up queries. This distinction aligns with the core difference between OLTP (Online Transaction Processing) and OLAP (Online Analytical Processing) systems in Azure, such as Azure SQL Database for transactional data and Azure Synapse Analytics for analytical data.

Exam trap

The trap here is that candidates confuse the typical characteristics of OLTP and OLAP, mistakenly thinking analytical data requires real-time processing or that transactional data is read-only, when in fact the opposite is true for each.

How to eliminate wrong answers

Option B is wrong because transactional data can be stored in both relational databases (e.g., Azure SQL Database) and non-relational databases (e.g., Azure Cosmos DB), and analytical data is often stored in relational or specialized columnar stores (e.g., Azure Synapse), not exclusively in one type. Option C is wrong because analytical data typically uses batch processing (e.g., nightly ETL jobs) rather than real-time processing, while transactional data requires real-time or near-real-time processing for individual write operations. Option D is wrong because transactional data is frequently updated (write-heavy), not read-only, and analytical data is typically read-only or updated in bulk during refresh cycles, not frequently updated.

158
MCQmedium

A logistics company collects sensor data from delivery trucks. Each sensor sends a JSON message that includes a fixed set of core fields (truck ID, timestamp) but also includes optional fields such as temperature, humidity, and engine diagnostics depending on the sensor type. The JSON structure varies between messages. How should this data be classified?

A.Structured data
B.Semi-structured data
C.Unstructured data
D.Relational data
AnswerB

Semi-structured data does not enforce a strict schema but uses tags, keys, or markers to give the data some organizational structure. In this scenario, the truck sensor data arrives as JSON, where each document has name-value pairs but the presence and combination of fields can vary, making it self-describing. These properties—some structure, but no rigid tabular schema—are exactly what define semi-structured data, so this is the correct classification.

Why this answer

The JSON messages contain a fixed set of core fields (truck ID, timestamp) but also include optional fields that vary per message, meaning the data has a flexible schema. This mixture of structured fields and variable attributes is the defining characteristic of semi-structured data, which does not require a rigid schema like a relational table but still has organizational properties (e.g., key-value pairs). In Azure, this type of data is commonly stored in services like Azure Cosmos DB or Azure Blob Storage with JSON format.

Exam trap

The trap here is that candidates often mistake any data with a consistent core set of fields as 'structured data', overlooking that the presence of optional, varying fields makes it semi-structured.

How to eliminate wrong answers

Option A is wrong because structured data requires a fixed, predefined schema (e.g., columns in a SQL table) with consistent fields across all records, but the JSON messages here have optional fields that vary. Option C is wrong because unstructured data has no predefined structure or schema (e.g., raw video files, plain text), whereas JSON has a defined key-value format. Option D is wrong because relational data specifically refers to data organized into tables with rows and columns linked by foreign keys, which is not the case for JSON messages with varying fields.

159
MCQhard

A global e-commerce platform uses a combination of relational and NoSQL databases. The order management system requires ACID transactions across multiple tables (Orders, OrderItems, Inventory). The product catalog uses a flexible schema to accommodate varying product attributes and is read-heavy. The session store requires low-latency key-value lookups with eventual consistency. Which of the following pairings of data stores best matches these requirements?

A.Order management: Azure Cosmos DB (NoSQL API) - Product catalog: Azure SQL Database - Session store: Azure Table Storage
B.Order management: Azure SQL Database - Product catalog: Azure Cosmos DB (NoSQL API) - Session store: Azure Cache for Redis
C.Order management: Azure Table Storage - Product catalog: Azure SQL Database - Session store: Azure Cosmos DB (NoSQL API)
D.Order management: Azure Cosmos DB (Table API) - Product catalog: Azure Cache for Redis - Session store: Azure SQL Database
AnswerB

Azure SQL Database provides strong ACID transactions for orders. Cosmos DB with NoSQL API offers flexible schema and low-latency reads for the product catalog. Azure Cache for Redis delivers sub-millisecond key-value lookups ideal for session state with eventual consistency.

Why this answer

Azure SQL Database provides full ACID transaction support across multiple tables, making it ideal for order management. Azure Cosmos DB (NoSQL API) offers a flexible schema and high read throughput for the product catalog. Azure Cache for Redis delivers sub-millisecond key-value lookups with eventual consistency, perfect for session storage.

Exam trap

The trap here is that candidates often assume NoSQL databases like Cosmos DB can handle ACID transactions across multiple tables, but in reality, Cosmos DB only guarantees atomicity within a single document or stored procedure, not across separate containers or tables.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB (NoSQL API) does not support multi-table ACID transactions across separate containers; it only offers single-document atomicity. Option C is wrong because Azure Table Storage lacks ACID transaction support across multiple tables, and Azure SQL Database is not optimized for flexible-schema, read-heavy product catalogs. Option D is wrong because Azure Cosmos DB (Table API) also lacks multi-table ACID transactions, Azure Cache for Redis is not designed for persistent, flexible-schema catalog storage, and Azure SQL Database is not suitable for low-latency key-value session stores with eventual consistency.

160
MCQmedium

A data analyst needs to create interactive dashboards that display real-time data from Azure SQL Database. Which Microsoft tool should they use?

A.Microsoft Excel
B.Microsoft Copilot
C.Azure Data Studio
D.Power BI
AnswerD

Power BI is the correct answer because it is Microsoft's dedicated business analytics platform, with Power BI Desktop for modeling and the Power BI Service for publishing live dashboards. It supports real-time scenarios through DirectQuery, push datasets, streaming datasets, and automatic page refresh, integrating with services like Azure Stream Analytics and Event Hubs. These dashboards offer interactive cross-filtering, natural-language Q&A, and row-level security, making them suitable for operational monitoring.

Why this answer

Power BI is the correct tool because it is designed specifically for creating interactive dashboards and reports, and it supports real-time data connectivity to Azure SQL Database through DirectQuery or streaming datasets. This allows the data analyst to visualize live data without manual refreshes, meeting the requirement for real-time dashboards.

Exam trap

The trap here is that candidates may confuse Azure Data Studio (a database management tool) with a visualization tool, or assume Microsoft Excel is sufficient for real-time dashboards, when Power BI is the only option that natively supports interactive, real-time visualizations with Azure SQL Database.

How to eliminate wrong answers

Option A is wrong because Microsoft Excel is a spreadsheet application that can connect to Azure SQL Database but lacks native support for real-time interactive dashboards; it requires manual data refresh or Power Query, and its visualization capabilities are limited compared to dedicated BI tools. Option B is wrong because Microsoft Copilot is an AI assistant integrated into various Microsoft products (like Power BI or Azure) to help generate content or code, but it is not a standalone tool for creating dashboards or connecting to live data sources. Option C is wrong because Azure Data Studio is a cross-platform database management and query tool for Azure SQL Database, primarily used for writing T-SQL queries, managing databases, and developing scripts; it does not provide dashboard or real-time visualization capabilities.

161
MCQeasy

A data engineer is classifying data types collected from three sources for a data lake. Source 1: Customer records from a SQL database exported as CSV files with fixed columns (CustomerID, Name, Address). Source 2: Product reviews obtained via API as JSON documents with varying fields (e.g., some reviews include 'rating' and 'verified_purchase', others include 'comment'). Source 3: Scanned handwritten order forms saved as TIFF images. Which statement correctly categorizes these data by structure?

A.Source 1: Structured; Source 2: Semi-structured; Source 3: Unstructured
B.Source 1: Structured; Source 2: Structured; Source 3: Unstructured
C.Source 1: Semi-structured; Source 2: Structured; Source 3: Unstructured
D.Source 1: Structured; Source 2: Unstructured; Source 3: Semi-structured
AnswerA

This is correct. Source 1 is a CSV file with fixed columns and defined data types per column, satisfying the rigid schema that defines structured data. Source 2 is JSON with varying fields; it has key-value pairs and hierarchical organization but no fixed schema, so it is semi-structured. Source 3 is TIFF images, which are binary pixel arrays without embedded field names or relational structure, making them unstructured.

Why this answer

Source 1 (CSV from SQL) has a fixed schema with defined columns, making it structured data. Source 2 (JSON from API) allows varying fields per document, which is the hallmark of semi-structured data. Source 3 (TIFF images) contains no inherent schema or machine-readable structure, classifying it as unstructured data.

Exam trap

The trap here is that candidates confuse CSV files (which are structured when they have a fixed schema) with semi-structured data, or assume JSON is always structured because it has key-value pairs, ignoring that varying fields make it semi-structured.

How to eliminate wrong answers

Option B is wrong because it incorrectly classifies Source 2 (JSON with varying fields) as structured, ignoring that JSON documents with optional or varying fields do not enforce a rigid schema like a SQL table. Option C is wrong because it mislabels Source 1 (CSV with fixed columns) as semi-structured, whereas CSV with a consistent schema is structured, and it also mislabels Source 2 as structured instead of semi-structured. Option D is wrong because it classifies Source 2 (JSON) as unstructured, but JSON has key-value pairs and a defined format, making it semi-structured, and it mislabels Source 3 (TIFF images) as semi-structured, but images lack any inherent data structure.

162
MCQeasy

A company stores customer data in a SQL table with fixed columns (CustomerID, Name, Email, SignupDate). They also store product images as JPEG files and application logs as JSON documents. Which of the following correctly classifies each data type?

A.SQL table: structured, JPEG: unstructured, JSON: semi-structured
B.SQL table: structured, JPEG: semi-structured, JSON: unstructured
C.SQL table: semi-structured, JPEG: unstructured, JSON: structured
D.SQL table: unstructured, JPEG: structured, JSON: semi-structured
AnswerA

SQL tables enforce a rigid schema via predefined columns and data types, so every row must conform to that fixed structure, which is the definition of structured data. A JPEG file is a binary image format that stores encoded pixel data and metadata; it has no row/column organization or queryable schema, making it unstructured. JSON documents use key-value pairs and can have optional or nested fields, so they are self-describing and flexible, which is classic semi-structured data. Thus, all three classifications here are accurate.

Why this answer

A SQL table with fixed columns enforces a rigid schema, making it structured data. JPEG files are binary blobs with no internal schema, classifying them as unstructured. JSON documents use key-value pairs with flexible schemas, which is the definition of semi-structured data.

Exam trap

The trap here is confusing semi-structured data (like JSON) with unstructured data (like images), or assuming that any file format with a standard (like JPEG) is semi-structured, when in fact JPEG is purely binary and unstructured.

How to eliminate wrong answers

Option B is wrong because it incorrectly classifies JPEG as semi-structured (JPEG is binary and lacks schema) and JSON as unstructured (JSON has a flexible schema, making it semi-structured). Option C is wrong because it classifies the SQL table as semi-structured (SQL tables with fixed columns are structured, not semi-structured) and JSON as structured (JSON is semi-structured, not rigidly structured). Option D is wrong because it classifies the SQL table as unstructured (SQL tables are highly structured) and JPEG as structured (JPEG files have no schema).

163
MCQeasy

A hospital stores patient records. Each record includes a PatientID (integer), Name (text), DateOfBirth (date), and MRI scan images (binary files). Which classification best describes the MRI scan images?

A.Structured data
B.Semi-structured data
C.Unstructured data
D.Streaming data
AnswerC

Unstructured data has no predefined data model or schema and includes binary files like images, videos, and audio recordings. An MRI scan is exactly that—a binary blob—where the pixel data is not inherently organized into rows/columns, and meaning must be extracted via computer vision or human interpretation, making it a classic example of unstructured data.

Why this answer

MRI scan images are binary files that lack a predefined data model or schema, making them unstructured data. Unlike structured data (e.g., rows in a SQL table) or semi-structured data (e.g., JSON with tags), binary image files cannot be easily queried or organized using traditional relational database tools without additional processing.

Exam trap

Microsoft often tests the misconception that any data stored in a database (e.g., as a BLOB) is structured, but the classification depends on the data's internal format, not its storage location.

How to eliminate wrong answers

Option A is wrong because structured data requires a fixed schema with rows and columns, such as a PatientID integer in a relational table, which does not apply to binary image files. Option B is wrong because semi-structured data has organizational properties like tags or key-value pairs (e.g., JSON or XML), whereas MRI images are raw binary blobs without inherent metadata structure. Option D is wrong because streaming data refers to continuous data flows from sources like IoT sensors or log streams, not static binary files stored in a database.

164
MCQeasy

Your organization has a large dataset of customer transactions stored in Azure Blob Storage as CSV files. You need to run ad-hoc SQL queries on this data without loading it into a database. Which Azure service should you use?

A.Azure Data Factory
B.Azure SQL Database
C.Azure Synapse Serverless SQL pool
D.Azure Analysis Services
AnswerC

Azure Synapse Serverless SQL pool is the correct choice because it is a compute-on-demand query endpoint that runs T-SQL directly over files in Azure Blob Storage or Data Lake Storage Gen2. It uses a distributed query engine to read semi-structured and structured formats like Parquet, Delta, and CSV without any data movement or provisioning of dedicated resources. You can issue standard SELECT statements and let the service scale compute automatically, making it ideal for ad-hoc exploration of large datasets.

Why this answer

Azure Synapse Serverless SQL pool allows you to query data directly from files in Azure Blob Storage using standard T-SQL syntax, without needing to load or move the data into a database. It uses a pay-per-query model and supports CSV, Parquet, and JSON formats, making it ideal for ad-hoc analytical queries over large datasets stored in data lakes.

Exam trap

The trap here is that candidates often confuse Azure Data Factory (a data movement/orchestration tool) with a query engine, or assume Azure SQL Database can query external files via PolyBase (which requires loading into external tables, not direct ad-hoc querying).

How to eliminate wrong answers

Option A is wrong because Azure Data Factory is an ETL and data orchestration service, not a SQL query engine; it cannot run ad-hoc SQL queries directly against files. Option B is wrong because Azure SQL Database requires data to be loaded into its relational storage before querying, which contradicts the requirement to query without loading. Option D is wrong because Azure Analysis Services is an OLAP engine for semantic models and multidimensional analysis, not designed for direct SQL queries over raw CSV files in Blob Storage.

165
MCQmedium

You need to choose a data storage solution for a global e-commerce platform that requires single-digit millisecond read and write latencies across multiple regions. The data is semi-structured and includes user profiles and product catalogs. Which Azure service should you use?

A.Azure Redis Cache
B.Azure Cosmos DB
C.Azure Table Storage
D.Azure SQL Database
AnswerB

Azure Cosmos DB is the correct choice because it natively provides turnkey global distribution across Azure regions with multi-region write support, enabling low-latency reads and writes anywhere in the world. It offers single-digit millisecond latency at the 99th percentile, multiple well-defined consistency levels, and SLAs for availability, throughput, and consistency. Its schema-agnostic NoSQL model supports semi-structured data like product catalogs and user profiles, making it purpose-built for globally distributed e-commerce applications.

Why this answer

Azure Cosmos DB is the correct choice because it is a globally distributed, multi-model database service that guarantees single-digit millisecond read and write latencies at the 99th percentile, regardless of the number of regions. It supports semi-structured data natively through its document (JSON) API, making it ideal for user profiles and product catalogs that require low-latency access across multiple geographic regions.

Exam trap

The trap here is that candidates often confuse Azure Redis Cache's in-memory speed with the need for persistent, globally distributed storage, overlooking that Redis Cache is not designed for durable, multi-region data storage with consistency guarantees.

How to eliminate wrong answers

Option A is wrong because Azure Redis Cache is an in-memory data store designed primarily for caching and session state, not for persistent, globally distributed storage of semi-structured data with multi-region write capabilities. Option C is wrong because Azure Table Storage is a NoSQL key-value store that offers only eventual consistency by default and does not provide guaranteed single-digit millisecond latencies across multiple regions or native global distribution. Option D is wrong because Azure SQL Database is a relational database that requires a fixed schema, making it less suitable for semi-structured data, and its global replication options (e.g., failover groups) do not guarantee single-digit millisecond latencies for writes across multiple regions.

166
MCQeasy

You need to query data stored in Azure Cosmos DB for NoSQL using SQL-like syntax. Which feature should you use?

A.Use Azure SQL Database elastic query
B.Use Power BI DirectQuery
C.Use the SQL API built into Cosmos DB
D.Use Azure Synapse Analytics Serverless SQL pool
AnswerC

Cosmos DB's SQL API is the native query language for the NoSQL API, allowing you to query JSON documents with a SQL-like syntax that supports SELECT, WHERE, JOIN, and functions such as VALUE, ARRAY_CONTAINS, and ST_* spatial functions. Queries are executed directly against the Cosmos DB engine, and the service automatically uses its index to efficiently evaluate predicates. This option is correct because it is the built-in query interface specifically designed for data stored in a Cosmos DB NoSQL account.

Why this answer

Azure Cosmos DB for NoSQL provides a native SQL API that allows you to query JSON documents using SQL-like syntax. This API translates standard SQL queries into Cosmos DB's internal query engine, enabling you to SELECT, filter, and project data directly from containers without any additional services or connectors.

Exam trap

The trap here is that candidates may confuse Azure Synapse Analytics Serverless SQL pool (which can also query Cosmos DB) with the native Cosmos DB SQL API, but the question specifically asks for the feature built into Cosmos DB for NoSQL, not an external query service.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database elastic query is used to query data across multiple Azure SQL databases, not for querying Cosmos DB NoSQL data. Option B is wrong because Power BI DirectQuery is a connection mode for real-time analytics from Power BI, not a feature for directly querying Cosmos DB with SQL-like syntax. Option D is wrong because Azure Synapse Analytics Serverless SQL pool can query Cosmos DB via the Synapse Link feature, but it is not the built-in SQL API of Cosmos DB itself and requires additional configuration.

167
MCQhard

Refer to the exhibit. You are configuring a custom role in Azure RBAC for a team that needs to read and list blobs in a storage account. The JSON snippet shows the permissions assigned. After assigning this role to a user, they report they cannot see the storage account in the Azure portal. What is the most likely cause?

A.The dataActions should be actions instead of dataActions.
B.The role does not include read permission on the storage account resource.
C.The role is not assigned at the subscription scope.
D.The user needs the Contributor role to view the storage account.
AnswerB

The role definition is missing `Microsoft.Storage/storageAccounts/read`, which is the control-plane action required to see the storage account in the Azure portal and to list it with tools like ARM API or PowerShell. Even if `dataActions` grant blob read/write, the user cannot discover or view the storage account resource itself, resulting in an authorization failure when attempting to display the account. This missing read permission is the direct cause of the user's inability to see the storage account.

Why this answer

The custom role definition only includes dataActions for reading and listing blobs, but lacks any actions that grant read permission on the storage account resource itself. In Azure RBAC, viewing a storage account in the Azure portal requires the 'Microsoft.Storage/storageAccounts/read' action at the resource scope. Without this, the user cannot see the storage account in the portal, even though they can interact with blobs via APIs or tools that bypass the portal.

Exam trap

The trap here is that candidates often assume dataActions alone are sufficient for portal visibility, but the portal requires control-plane read permissions to render the storage account in the resource list.

How to eliminate wrong answers

Option A is wrong because dataActions are the correct property for granting permissions to data operations (like reading blobs), and moving them to actions would not grant the necessary control-plane read on the storage account resource. Option C is wrong because the role can be assigned at the resource group or storage account scope; the issue is the missing control-plane read action, not the assignment scope. Option D is wrong because the Contributor role is not required; a custom role with the 'Microsoft.Storage/storageAccounts/read' action would suffice, and the user does not need full Contributor permissions.

168
MCQeasy

Your company is implementing a data governance solution using Microsoft Purview. The data catalog must automatically scan and classify sensitive data in Azure SQL Database, Azure Synapse Analytics, and Amazon S3. The company uses Microsoft Entra ID for identity management. You need to ensure that the Purview managed identity can authenticate to these data sources. Which authentication method should you configure for the Amazon S3 connection?

A.AWS IAM authentication
B.SQL Authentication
C.Windows Authentication
D.Microsoft Entra ID authentication
AnswerA

Amazon S3 only accepts requests signed with AWS credentials, specifically AWS IAM identities such as a user or role. To let Microsoft Purview scan an S3 bucket, you must create an IAM role in the AWS account, configure its trust policy to allow the Purview service principal (via an external ID) to assume the role, and attach policies that grant read access to the bucket. The Purview managed identity then uses that IAM role to authenticate, so AWS IAM authentication is the only valid method for this connection.

Why this answer

Amazon S3 is an external cloud storage service that does not support Microsoft Entra ID, SQL Authentication, or Windows Authentication. To authenticate Purview's managed identity to S3, you must configure AWS IAM authentication, which allows Purview to assume an IAM role with permissions to read the S3 bucket metadata and data for scanning and classification.

Exam trap

The trap here is that candidates may assume Microsoft Entra ID authentication works for all data sources because the question mentions Entra ID for identity management, but Amazon S3 is an AWS service that requires AWS IAM, not Microsoft's identity system.

How to eliminate wrong answers

Option B (SQL Authentication) is wrong because SQL Authentication is used for Azure SQL Database and Azure Synapse Analytics, not for Amazon S3, which is a non-relational object store. Option C (Windows Authentication) is wrong because Windows Authentication is only applicable to on-premises SQL Server or Azure services integrated with Active Directory, not to AWS S3. Option D (Microsoft Entra ID authentication) is wrong because Amazon S3 does not support Microsoft Entra ID; it uses AWS IAM for identity and access management.

169
MCQeasy

A bank's online transaction processing system records every withdrawal and deposit in a database. The bank also runs a monthly report that summarizes total transactions per customer. Which statement correctly identifies these two workloads?

A.Both workloads are OLTP.
B.The transaction recording is OLTP, and the monthly report is OLAP.
C.The transaction recording is OLAP, and the monthly report is OLTP.
D.Both workloads are OLAP.
AnswerB

This classification is correct because the two workloads have fundamentally different processing requirements. Recording each online transaction is an OLTP operation: it involves high-frequency, low-latency writes and reads for individual events, with strict ACID guarantees to ensure data integrity. Generating the monthly report, by contrast, is an OLAP operation: it queries large volumes of accumulated transaction data, applies aggregations, and supports business intelligence analysis, often within a data warehouse environment optimized for complex read-only queries.

Why this answer

The transaction recording system is an OLTP (Online Transaction Processing) workload because it handles individual, real-time transactions (withdrawals and deposits) with high concurrency and low latency. The monthly report summarizing total transactions per customer is an OLAP (Online Analytical Processing) workload because it aggregates historical data for reporting and analysis, typically using batch processing or columnar storage. Option B correctly pairs each workload with its appropriate processing type.

Exam trap

The trap here is that candidates confuse the purpose of the workload—thinking that any database operation is OLTP—and fail to recognize that analytical reporting, even if run on the same database, is an OLAP workload due to its aggregate nature and different performance requirements.

How to eliminate wrong answers

Option A is wrong because it incorrectly classifies both workloads as OLTP, ignoring that the monthly report involves aggregation and analysis, not real-time transaction processing. Option C is wrong because it reverses the roles, claiming transaction recording is OLAP (which is for analytical queries on large datasets) and the monthly report is OLTP (which is for transactional operations). Option D is wrong because it classifies both as OLAP, failing to recognize that the transaction recording system requires immediate, atomic writes characteristic of OLTP.

170
MCQeasy

A retail company stores product inventory data in a SQL database, customer reviews as JSON files, and product images as JPEG files. Which of the following accurately describes the types of data stored?

A.A. Only structured data is stored because the SQL database contains the primary records.
B.B. Only semi-structured and unstructured data is stored because JSON and images are not purely structured.
C.C. Only unstructured data is stored because images have no predefined schema.
D.D. Structured, semi-structured, and unstructured data are stored.
AnswerD

Correct. The SQL database contains structured data (rows and columns), JSON files contain semi-structured data (key-value pairs with some schema flexibility), and JPEG files contain unstructured data (no inherent structure). All three categories are represented.

Why this answer

The company stores product inventory data in a SQL database, which enforces a fixed schema (tables, rows, columns) and is therefore structured data. Customer reviews stored as JSON files are semi-structured because they have a flexible schema (key-value pairs) but no rigid table structure. Product images as JPEG files are unstructured because they lack any predefined schema or organization.

Option D correctly identifies that all three data types are present.

Exam trap

The trap here is that candidates often assume 'data type' is determined by the storage medium (e.g., SQL = structured only) rather than recognizing that a single system can store multiple data types, leading them to overlook the presence of semi-structured and unstructured data.

Why the other options are wrong

A

The company stores JSON files (semi-structured) and JPEG images (unstructured) in addition to the SQL database (structured), so option A incorrectly claims only structured data is stored.

B

The company stores structured data (SQL database), semi-structured data (JSON files), and unstructured data (JPEG images). Option B incorrectly claims only semi-structured and unstructured data are stored, ignoring the structured SQL data.

C

The company stores structured data (SQL database), semi-structured data (JSON files), and unstructured data (JPEG images). Option C incorrectly claims only unstructured data is stored, ignoring the SQL and JSON data.

171
MCQeasy

A social media platform stores user posts as JSON documents. Each document contains text content, image URLs, timestamps, and user tags. The structure is consistent for most fields, but users can add custom key-value pairs. How should this data be classified?

A.Structured data
B.Semi-structured data
C.Unstructured data
D.Relational data
AnswerB

Semi-structured data exhibits organizational properties—such as key-value pairs, tags, and hierarchical nesting—but does not require a uniform, predefined schema across all instances. JSON documents fit this category perfectly because they use explicit keys to define their internal structure, yet the presence and type of those keys can vary from one document to another. This schema-flexibility, combined with inherent self-description, distinguishes semi-structured data from both rigid structured data and completely structureless unstructured data.

Why this answer

The data is semi-structured because it has a consistent schema for most fields (text, image URLs, timestamps, user tags) but allows custom key-value pairs, which introduces schema flexibility. JSON documents inherently support this mix of fixed and variable attributes, fitting the semi-structured data classification. This aligns with Azure Cosmos DB's handling of JSON items, where each document can have a different set of properties.

Exam trap

Microsoft often tests the misconception that any data with a consistent field is structured, but the presence of optional custom key-value pairs makes it semi-structured, not structured.

How to eliminate wrong answers

Option A is wrong because structured data requires a rigid schema with fixed columns and data types (e.g., a SQL table), but JSON documents with optional custom fields violate that strict schema. Option C is wrong because unstructured data has no predefined structure or organization (e.g., raw text files, images, videos), whereas JSON documents have a defined format with keys and values. Option D is wrong because relational data specifically refers to data organized into tables with rows and columns linked by foreign keys, which JSON documents do not enforce.

172
MCQeasy

A company stores customer names and addresses in a relational table, product descriptions as JSON files, and product images as JPEG files. Which of the following correctly classifies these data types from most structured to least structured?

A.Structured (customer table), Semi-structured (JSON), Unstructured (JPEG)
B.Structured (customer table), Unstructured (JSON), Semi-structured (JPEG)
C.Semi-structured (customer table), Structured (JSON), Unstructured (JPEG)
D.Unstructured (customer table), Structured (JSON), Semi-structured (JPEG)
AnswerA

A relational customer table has a fixed schema, so every row shares the same defined columns and data types — that is structured data. JSON documents are self-describing: they contain key-value pairs that can vary from document to document, which classifies them as semi-structured. JPEG images store raw pixel and compression metadata without any queryable semantic fields, so they are unstructured. Therefore, this mapping accurately applies the three data categories to the three storage types.

Why this answer

A is correct because structured data (customer table) has a fixed schema with rows and columns, semi-structured data (JSON) uses tags or key-value pairs without a rigid schema, and unstructured data (JPEG) has no predefined structure. The question tests the standard classification hierarchy from most to least structured.

Exam trap

The trap here is confusing semi-structured (JSON) with unstructured (JPEG) because both lack a rigid schema, but JSON has a logical structure (key-value pairs) while JPEG is raw binary data.

Why the other options are wrong

B

JSON files are semi-structured because they have a schema (key-value pairs) but allow flexibility, not unstructured. JPEG files are unstructured binary data without a schema. This option incorrectly classifies JSON as unstructured and JPEG as semi-structured.

C

A relational table is structured, not semi-structured. JSON files are semi-structured, not structured. JPEG files are unstructured, not semi-structured.

D

This option incorrectly classifies JSON as structured and JPEG as semi-structured. JSON is semi-structured (self-describing schema), while JPEG is unstructured (binary data without schema).

173
MCQmedium

A retail company uploads daily sales data from all stores to Azure Blob Storage at midnight. They then run a series of data transformations using Azure Data Factory on a scheduled trigger at 2:00 AM. This processing pattern is best described as:

A.Batch processing
B.Stream processing
C.Transactional processing
D.Interactive query
AnswerA

This scenario perfectly fits batch processing because the daily sales data from all stores is accumulated over a fixed period and then processed as a single, scheduled bulk job. Batch jobs such as nightly ETL pipelines in Azure Data Factory or scheduled Spark jobs in Azure Databricks ingest a finite, predefined dataset and transform it in one go, making it ideal for periodic reporting and analytics.

Why this answer

This pattern is batch processing because the sales data is collected in Azure Blob Storage over a period (daily) and then processed as a group at a scheduled time (2:00 AM) using Azure Data Factory. Batch processing is designed for high-volume, periodic data loads where latency is acceptable, and the transformation job runs on a complete dataset rather than individual records.

Exam trap

The trap here is that candidates confuse scheduled data movement with stream processing, but the key differentiator is the time delay and the processing of a complete dataset in one job rather than individual events as they occur.

How to eliminate wrong answers

Option B is wrong because stream processing handles data in real-time or near-real-time as it arrives (e.g., using Azure Stream Analytics or Event Hubs), not on a scheduled trigger with a 2-hour delay. Option C is wrong because transactional processing (OLTP) focuses on individual, atomic transactions with ACID guarantees (e.g., Azure SQL Database), not bulk transformations of daily files. Option D is wrong because interactive query implies ad-hoc, user-driven exploration (e.g., using Azure Synapse Serverless SQL or Azure Data Explorer), not a scheduled, automated transformation pipeline.

174
Matchingmedium

Match each Azure Cosmos DB API to its supported data model.

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

Concepts
Matches

Document (JSON)

Document (BSON)

Column-family

Graph

Key-value

Why these pairings

Azure Cosmos DB APIs map to specific data models: SQL and MongoDB for document, Cassandra for wide-column, Gremlin for graph, and Table for key-value. Common confusions involve misassigning Gremlin and Table.

175
MCQeasy

A company stores customer data in a relational table with fixed columns: CustomerID (integer), FirstName (string), LastName (string), Email (string). They also store product images as JPEG files in Azure Blob Storage, and customer feedback as JSON documents where each document may contain fields such as rating, comment, and optional metadata. Which of the following correctly classifies these data types?

A.Relational table – structured, JPEG – unstructured, JSON – semi-structured
B.Relational table – structured, JPEG – semi-structured, JSON – unstructured
C.Relational table – semi-structured, JPEG – unstructured, JSON – structured
D.Relational table – unstructured, JPEG – structured, JSON – semi-structured
AnswerA

Relational tables enforce a fixed schema of columns, data types, and constraints, which is the defining trait of structured data. JPEG files are binary image encodings with no queryable schema or row/column organization, so they are unstructured. JSON documents use named fields and nested objects but allow fields to vary across documents, making them semi-structured rather than fully rigid or schema-free.

Why this answer

A relational table with fixed columns and data types (CustomerID, FirstName, LastName, Email) stores structured data with a rigid schema. JPEG files in Azure Blob Storage are binary blobs with no internal structure that a database can interpret, making them unstructured. JSON documents with optional fields (like rating, comment, metadata) have a flexible schema that can vary per document, which is the definition of semi-structured data.

Exam trap

The trap here is that candidates often confuse 'semi-structured' with 'unstructured' because JSON looks like free-form text, but its key-value structure with optional fields makes it semi-structured, not unstructured.

Why the other options are wrong

B

JPEG files are binary data without inherent structure, making them unstructured, not semi-structured. JSON documents have a flexible schema (key-value pairs), classifying them as semi-structured, not unstructured.

C

Option C incorrectly classifies the relational table as semi-structured (it is structured with fixed columns) and JSON as structured (JSON is semi-structured as it allows flexible fields). JPEG images are correctly classified as unstructured.

D

JPEG files are binary data without inherent structure, making them unstructured, not structured. JSON documents have a flexible schema with optional fields, classifying them as semi-structured, not unstructured.

176
MCQhard

Your company has a data lake in Azure Data Lake Storage Gen2 containing terabytes of parquet files. Data scientists need to explore and prepare this data using Python and SQL. They want to use a collaborative notebook environment that integrates with Git for version control. The solution should automatically scale compute resources based on workload demand and minimize management overhead. Which Azure service should you use?

A.Azure Databricks
B.Azure Machine Learning studio
C.Azure Data Studio
D.Azure Synapse Studio
AnswerA

Azure Databricks provides a unified analytics platform with Apache Spark, offering collaborative notebooks, full Git integration, and auto-scaling clusters. It supports both Python and SQL natively, making it ideal for interactive data exploration and large-scale transformation of data stored in Azure Data Lake Storage Gen2. Its managed infrastructure and notebook environment allow data engineers to prepare and process data efficiently, which aligns perfectly with the requirement.

Why this answer

Azure Databricks is the correct choice because it provides a collaborative notebook environment that natively supports Python and SQL, integrates with Git for version control, and offers auto-scaling clusters that dynamically adjust compute resources based on workload demand. It is purpose-built for big data analytics and data preparation on data lakes, minimizing management overhead through its serverless and managed Spark infrastructure.

Exam trap

The trap here is that candidates often confuse Azure Synapse Studio with Databricks because both offer notebook experiences and Spark support, but Synapse Studio is optimized for enterprise data warehousing and ETL pipelines, not the ad-hoc, collaborative data exploration and auto-scaling flexibility that Databricks provides for data science teams.

How to eliminate wrong answers

Option B is wrong because Azure Machine Learning studio is primarily designed for building, training, and deploying machine learning models, not for ad-hoc data exploration and preparation using Python and SQL in a collaborative notebook environment with Git integration. Option C is wrong because Azure Data Studio is a desktop tool for querying SQL Server and Azure SQL databases, not a cloud-based collaborative notebook environment that auto-scales compute resources. Option D is wrong because Azure Synapse Studio is a unified analytics workspace that does support notebooks and Git, but it is more focused on enterprise data warehousing and large-scale analytics pipelines, and its auto-scaling capabilities are tied to dedicated SQL pools or serverless SQL endpoints, not the flexible, on-demand Spark clusters that Databricks provides for data exploration and preparation.

177
Drag & Dropmedium

Drag and drop the steps to create an Azure SQL Database in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Creating an Azure SQL Database involves selecting the service, configuring the server and database settings, choosing the appropriate tier, and finally deploying.

178
MCQmedium

A retail company uses Azure SQL Database to store customer transactions. They need to analyze sales trends over time. Which Azure service should they use to build interactive dashboards and reports without moving data out of Azure?

A.Azure Analysis Services
B.Azure Synapse Analytics
C.Microsoft Purview
D.Power BI
AnswerD

Power BI is a business analytics service that natively connects to Azure SQL Database through built-in connectors, enabling you to create interactive dashboards and reports directly from your operational data. It supports DirectQuery and import modes, providing live or cached data access for rich, dynamic visualizations that can be refreshed on demand. With features like row-level security and natural language queries, it is the ideal tool for lightweight, user-facing dashboards at the retail company, offering immediate insights without an intermediate data transformation layer.

Why this answer

Power BI is the correct choice because it is a business analytics service that can connect directly to Azure SQL Database to build interactive dashboards and reports without requiring data movement. It supports DirectQuery mode, which queries the source database in real-time, enabling live analysis of sales trends while data remains in Azure.

Exam trap

The trap here is that candidates may confuse Azure Synapse Analytics as a reporting tool, but it is primarily a data warehousing and analytics platform that requires data movement or transformation, whereas Power BI is the native Azure service for direct, no-movement interactive reporting.

How to eliminate wrong answers

Option A is wrong because Azure Analysis Services is an analytical engine that requires data to be loaded into its in-memory tabular model, which involves moving or processing data outside the source database. Option B is wrong because Azure Synapse Analytics is a big data and analytics platform that typically requires data to be ingested into its dedicated SQL pool or data lake, not suitable for direct, no-movement reporting on a transactional Azure SQL Database. Option C is wrong because Microsoft Purview is a data governance and catalog service, not a reporting or dashboard tool; it cannot build interactive visualizations.

179
MCQeasy

A logistics company ingests GPS coordinates from delivery trucks in real-time to update a live tracking dashboard. They also run a nightly job to aggregate the day's deliveries into a report stored in Azure SQL Database. Which statement correctly describes the data processing types used for these two workloads?

A.GPS ingestion is stream processing; nightly aggregation is batch processing.
B.GPS ingestion is batch processing; nightly aggregation is stream processing.
C.Both workloads are examples of stream processing.
D.Both workloads are examples of batch processing.
AnswerA

GPS ingestion is correctly classified as stream processing because telematics devices emit position records as a continuous, unbounded sequence of events that must be captured and processed with low latency to support live tracking. In contrast, the nightly aggregation job is batch processing because it operates on a bounded, finite set of data already collected, executing on a fixed schedule to compute summaries like daily mileage or route efficiency.

Why this answer

The real-time ingestion of GPS coordinates from delivery trucks is a classic stream processing workload, where data is processed continuously as it arrives with low latency. The nightly aggregation of daily deliveries into a report stored in Azure SQL Database is a batch processing workload, where data is processed in bulk at scheduled intervals. Azure Stream Analytics is commonly used for the streaming ingestion, while Azure SQL Database or Azure Synapse Analytics can handle the batch aggregation.

Exam trap

The trap here is that candidates confuse the terms 'stream processing' and 'batch processing' by focusing on the data source (GPS is continuous) versus the processing schedule (nightly is periodic), rather than the fundamental processing paradigm of continuous vs. bulk data handling.

Why the other options are wrong

B

GPS ingestion processes data in real-time as it arrives, which is stream processing, not batch. Nightly aggregation processes a fixed set of data at scheduled intervals, which is batch processing, not stream.

C

The nightly aggregation job processes a full day's data at once, which is batch processing, not stream processing. Stream processing handles data in real-time as it arrives, which applies only to the GPS ingestion.

D

GPS ingestion is real-time (stream processing), and the nightly aggregation is batch processing. Option D incorrectly classifies both as batch processing, ignoring the real-time nature of GPS data ingestion.

180
MCQeasy

A data scientist needs to analyze historical sales data to identify yearly trends. They run SQL queries that aggregate millions of rows. No new data is being added during analysis. Which type of data processing workload does this represent?

A.Online Transaction Processing (OLTP)
B.Online Analytical Processing (OLAP)
C.Batch processing
D.Stream processing
AnswerB

This is the correct classification because OLAP is designed specifically for multidimensional, historical analysis—slicing, dicing, drilling down, and rolling up across dimensions such as time, region, and product. Data is typically stored in columnar, denormalized schemas (star or snowflake) that make full-table scans and aggregations fast, even on billions of rows. A data scientist analyzing historical sales trends matches this analytical workload precisely.

Why this answer

This workload is Online Analytical Processing (OLAP) because the data scientist is running complex SQL queries that aggregate millions of rows of historical sales data to identify yearly trends. OLAP is designed for read-intensive, analytical queries that summarize large volumes of static data, which matches the scenario where no new data is being added during analysis.

Exam trap

Microsoft often tests the distinction between OLTP and OLAP by presenting a scenario with 'SQL queries' and 'aggregation,' leading candidates to mistakenly think any SQL query implies OLTP, when in fact the analytical nature and static dataset clearly indicate OLAP.

How to eliminate wrong answers

Option A is wrong because Online Transaction Processing (OLTP) is optimized for high-volume, low-latency insert/update/delete operations (e.g., order entry), not for aggregating millions of rows for trend analysis. Option C is wrong because batch processing typically involves processing large volumes of data in scheduled, automated jobs (e.g., nightly ETL), whereas this scenario is an interactive analytical query run by a data scientist, not a scheduled batch job. Option D is wrong because stream processing handles continuous, real-time data flows (e.g., sensor data or clickstreams) with low latency, but the question explicitly states no new data is being added during analysis, making it a static dataset.

181
MCQmedium

You are reviewing a Data Factory mapping data flow definition. What is the primary purpose of this data flow?

A.Pivot the data by OrderID
B.Filter rows where OrderID is null
C.Remove duplicate OrderIDs by counting them
D.Merge two data sources
AnswerC

This is correct because the Aggregate transformation in the data flow groups rows by OrderID and applies a count expression, such as count(OrderID), to calculate occurrences per OrderID. Rows with a count greater than 1 are duplicates, allowing the definition to identify (and subsequently remove) duplicate OrderIDs. This matches the requirement to remove duplicate OrderIDs by counting them.

Why this answer

The mapping data flow includes an Aggregate transformation configured with a group by on OrderID and a count aggregation. This removes duplicate OrderIDs by collapsing multiple rows with the same OrderID into a single row and counting the occurrences, which is the primary purpose of the data flow.

Exam trap

The trap here is that candidates may confuse the Aggregate transformation's count with a Filter or Pivot operation, not recognizing that grouping by a column and counting inherently removes duplicates by collapsing rows.

How to eliminate wrong answers

Option A is wrong because pivoting would require a Pivot transformation to rotate data from rows to columns, not an Aggregate with count. Option B is wrong because filtering null OrderIDs would use a Filter transformation, not an Aggregate. Option D is wrong because merging two data sources would require a Join or Union transformation, not a single Aggregate on one stream.

182
MCQhard

You are designing a data solution for a healthcare application that requires ACID transactions for patient records and needs to run complex analytics queries. Which combination of Azure services should you recommend?

A.Azure Cosmos DB for transactions, Power BI for analytics
B.Azure Database for MySQL for transactions, Azure Analysis Services for analytics
C.Azure Blob Storage for transactions, Azure Machine Learning for analytics
D.Azure SQL Database for transactions, Azure Synapse Analytics for analytics
AnswerD

Azure SQL Database provides full ACID transactions with row-level security and compatibility, making it a robust operational store for healthcare applications. Azure Synapse Analytics offers a large-scale analytics platform with dedicated SQL pools, massively parallel processing, and integrated data warehousing, capable of running complex queries across relational and data lake sources. Together they deliver an integrated, high-performance OLTP/OLAP solution that supports transactional integrity and advanced analytics.

Why this answer

Azure SQL Database provides full ACID (Atomicity, Consistency, Isolation, Durability) transaction support, which is essential for healthcare patient records where data integrity is critical. Azure Synapse Analytics is a cloud-based analytics service that can run complex queries against large datasets, including those from Azure SQL Database, using its massively parallel processing (MPP) architecture. This combination allows transactional and analytical workloads to coexist without compromising performance or consistency.

Exam trap

The trap here is that candidates often confuse 'analytics' with visualization tools like Power BI or OLAP cubes, failing to recognize that complex analytics queries require a dedicated MPP engine like Synapse, not just a reporting layer.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a NoSQL database that does not guarantee full ACID transactions across multiple documents (it offers single-document atomicity only), and Power BI is a visualization tool, not an analytics engine capable of running complex queries directly. Option B is wrong because Azure Analysis Services is an OLAP engine for pre-aggregated data, not designed for running complex ad-hoc analytics queries on raw transactional data; it requires a separate data warehouse or model. Option C is wrong because Azure Blob Storage is an object store with no transaction support (it lacks ACID properties), and Azure Machine Learning is for building predictive models, not for running complex analytics queries on transactional data.

183
MCQeasy

A retail company receives real-time data from IoT sensors in its warehouses. Each sensor sends a JSON payload containing a device ID, timestamp, and temperature reading. A data engineer needs to classify this data for storage planning. Which data type best describes the JSON payload?

A.Structured data
B.Semi-structured data
C.Unstructured data
D.Relational data
AnswerB

JSON is a classic example of semi-structured data. It uses key-value pairs and can have nested structures, but it does not enforce a rigid schema. This flexibility is ideal for IoT payloads where fields may vary over time.

Why this answer

The JSON payload is considered semi-structured data because it has organizational properties (key-value pairs, nested structure) that provide a schema, but it does not conform to a rigid tabular schema like a relational database. JSON allows flexible fields and varying data types, which is characteristic of semi-structured data.

Exam trap

The trap here is that candidates confuse 'structured' with 'has a format' — JSON has a clear structure, but it is not rigidly tabular, so it falls under semi-structured, not structured data.

Why the other options are wrong

A

JSON payloads have a flexible schema with tags and key-value pairs, which is characteristic of semi-structured data, not the rigid schema of structured data.

C

JSON payloads have a schema (keys like device ID, timestamp, temperature) but are not rigidly tabular, so they are semi-structured, not unstructured. Unstructured data lacks a predefined data model or schema (e.g., raw text, images).

D

Relational data implies a strict schema of tables with rows and columns, but the JSON payload has a flexible schema with nested fields, making it semi-structured, not relational.

184
MCQhard

Refer to the exhibit. You are analyzing a Kusto query in Azure Data Explorer. The query is intended to return the top 5 event types that caused the most property damage in Florida. However, the query returns an error. What is the most likely cause?

A.The where clause must specify a numeric value.
B.The summarize operator cannot use sum aggregation.
C.The table or column names are incorrect.
D.The top operator requires an order by clause.
AnswerC

A Kusto query that uses structurally valid operators will fail with a semantic recognition error when it references a table or column that does not exist in the current database or schema. Since the syntax of where, summarize, and top is correct, the most plausible cause is a misspelled table name or an incorrect column name (e.g., a missing quotation mark or wrong casing). Verify the exact schema from the Azure Data Explorer or Log Analytics schema pane to resolve the issue.

Why this answer

The query returns an error because the table or column names referenced in the query do not match the actual schema in Azure Data Explorer. In Kusto Query Language (KQL), if a table name like 'Events' or a column like 'PropertyDamage' does not exist in the database, the query will fail with a 'semantic error' indicating an unknown table or column. This is the most likely cause given that the query logic (where, summarize, top) is syntactically correct.

Exam trap

The trap here is that candidates may assume the error is due to a syntax or operator misuse (like top needing order by or sum being invalid), when in reality the error stems from a simple schema mismatch—a common oversight when reading queries without verifying the underlying data model.

How to eliminate wrong answers

Option A is wrong because the where clause in KQL can filter on string columns using equality or pattern matching (e.g., 'State == "Florida"'), not only numeric values. Option B is wrong because the summarize operator fully supports the sum() aggregation function for numeric columns, which is a standard and valid operation. Option D is wrong because the top operator in KQL does not require an explicit order by clause; it internally sorts by the specified column(s) in descending order and returns the top N rows.

185
MCQeasy

A company is evaluating Azure database services for two different workloads. Workload A processes high-volume, low-latency transactions such as order entry and payment processing, where each transaction updates a few rows. Workload B involves running complex aggregations on terabytes of historical sales data to generate monthly business intelligence reports. Which Azure service is best suited for each workload?

A.A. Workload A: Azure SQL Database; Workload B: Azure Cosmos DB
B.B. Workload A: Azure Cosmos DB; Workload B: Azure Synapse Analytics
C.C. Workload A: Azure Synapse Analytics; Workload B: Azure SQL Database
D.D. Workload A: Azure Cosmos DB; Workload B: Azure Cosmos DB
AnswerB

Azure Cosmos DB is a multi-model NoSQL database engineered for single-digit-millisecond write/read latency and instant global distribution, making it the right fit for Workload A's transaction-intensive, low-latency requirements (OLTP). Azure Synapse Analytics is a massively parallel processing (MPP) data warehouse with columnar storage and distributed query execution, built specifically for petabyte-scale analytical scans and complex aggregations (OLAP). This pairing cleanly separates transactional and analytical concerns, so each service is applied where its architecture provides the most benefit.

Why this answer

Workload A requires a low-latency, high-throughput transactional database capable of handling many small, row-level updates. Azure Cosmos DB is a NoSQL database designed for single-digit millisecond latency and horizontal scaling, making it ideal for order entry and payment processing. Workload B involves complex aggregations on terabytes of historical data, which is best handled by Azure Synapse Analytics, a distributed analytics service that uses massively parallel processing (MPP) to run large-scale queries efficiently.

Exam trap

The trap here is that candidates often confuse Azure SQL Database as the default for all transactional workloads, overlooking that Cosmos DB is specifically designed for ultra-low-latency, globally distributed transactions, and they may also assume Azure Synapse Analytics is only for data warehousing without recognizing its role in complex aggregations on historical data.

Why the other options are wrong

A

Workload B requires complex aggregations on terabytes of historical data, which is best suited for Azure Synapse Analytics (a distributed data warehouse), not Azure Cosmos DB (a NoSQL transactional database).

C

Azure Synapse Analytics is designed for large-scale data warehousing and analytics, not for high-volume, low-latency transactional workloads. Azure SQL Database is optimized for OLTP but lacks the massive parallel processing needed for complex aggregations on terabytes of data.

D

Azure Cosmos DB is a NoSQL database optimized for low-latency transactions, but it is not designed for complex aggregations on terabytes of historical data. Workload B requires a dedicated analytics service like Azure Synapse Analytics, not Cosmos DB.

186
MCQmedium

A company stores IoT sensor data in Azure Blob Storage. Data scientists need to query the data using SQL without moving it to another store. Which Azure service should they use?

A.Azure Synapse Serverless SQL pool
B.Azure Analysis Services
C.Azure Data Lake Storage
D.Azure SQL Database
AnswerA

Azure Synapse Serverless SQL pool is the correct choice because it is a serverless query engine that uses T-SQL to query IoT sensor data directly from Azure Blob Storage in place, without requiring any data movement or ingestion. It leverages OPENROWSET or external tables to read files such as CSV, JSON, or Parquet, and is ideal for ad-hoc or interactive analysis over raw data. You only pay for the amount of data processed, making it a cost-effective, on-demand option for exploring Blob Storage data.

Why this answer

Azure Synapse Serverless SQL pool allows you to query data directly from Azure Blob Storage using T-SQL without moving or copying the data. It uses a distributed query engine that reads files (Parquet, CSV, JSON) in place, making it ideal for ad-hoc analytics over IoT sensor data stored in Blob Storage.

Exam trap

The trap here is that candidates confuse Azure Data Lake Storage (a storage layer) with a query service, or assume Azure SQL Database can query external files directly, when in fact only Synapse Serverless SQL pool (or PolyBase in dedicated SQL pool) provides native SQL-on-file capabilities for Blob Storage.

How to eliminate wrong answers

Option B is wrong because Azure Analysis Services is an OLAP engine that requires data to be loaded into a tabular model, not a service for querying raw files in Blob Storage with SQL. Option C is wrong because Azure Data Lake Storage is a storage service (not a query service) that provides hierarchical namespace and POSIX-like access, but it does not natively support SQL querying without an additional compute layer like Synapse. Option D is wrong because Azure SQL Database is a fully managed relational database that requires data to be imported or ingested into tables, not a service for querying files in Blob Storage directly.

187
Multi-Selecthard

A company uses Azure Data Lake Storage Gen2 for a data lake. They need to ensure that only authorized users can access files and that access is audited. Which two Azure services should they combine? (Choose two options that together form the solution.)

Select 2 answers
A.Azure Policy
B.Azure Key Vault
C.Azure RBAC
D.Azure Monitor
E.Microsoft Entra ID
AnswersC, D

RBAC controls access to storage resources.

Why this answer

Azure RBAC (Role-Based Access Control) is correct because it provides fine-grained access management for Azure Data Lake Storage Gen2, allowing you to assign roles (e.g., Storage Blob Data Contributor) to users, groups, or service principals to control who can read, write, or delete files. Azure Monitor is correct because it can collect and analyze activity logs and diagnostic settings for the storage account, enabling auditing of access events such as successful and failed authentication attempts.

Exam trap

The trap here is that candidates often confuse Microsoft Entra ID (the identity provider) with the actual access control mechanism (RBAC) and auditing service (Monitor), thinking Entra ID alone handles both, but it only authenticates identities—RBAC authorizes them and Monitor audits the actions.

188
MCQmedium

Your company uses Azure SQL Database and needs to ensure that transactions are durable even if the database instance fails. Which feature should you enable?

A.Active geo-replication
B.Zone-redundant storage
C.Transparent Data Encryption
D.Auto-failover groups
AnswerB

Zone-redundant storage for Azure SQL Database ensures high availability and durability by synchronously replicating data across three Azure availability zones within a region. This architecture guarantees that transactions are durable and data remains accessible even if a single database instance or an entire availability zone fails. The data is protected against zonal outages, satisfying the requirement for durable transactions despite instance failure.

Why this answer

Zone-redundant storage (ZRS) replicates your Azure SQL Database transaction logs and data files synchronously across three Azure availability zones within the same region. This ensures that even if an entire zone fails, committed transactions are preserved and the database remains available, providing durability at the storage layer without requiring a separate database replica.

Exam trap

The trap here is that candidates often confuse durability (ensuring committed data survives failures) with high availability or disaster recovery features like geo-replication or failover groups, which address availability rather than the storage-level persistence of transactions.

How to eliminate wrong answers

Option A is wrong because active geo-replication creates asynchronous replicas in a paired region for disaster recovery, but it does not guarantee durability of transactions within the primary region during a zone-level failure. Option C is wrong because Transparent Data Encryption (TDE) only encrypts data at rest and in transit, providing security but no durability or availability guarantees. Option D is wrong because auto-failover groups manage failover between primary and secondary databases, but they rely on the underlying storage durability; they do not themselves make transactions durable against a storage failure.

189
MCQeasy

A retail company stores data about their products in different formats. Product ID and price are stored in a relational database table. Product descriptions are stored as plain text files. Product images are stored as JPEG files. Which of the following best categorizes these data types in order?

A.Structured, semi-structured, unstructured
B.Structured, unstructured, unstructured
C.Structured, semi-structured, structured
D.Semi-structured, structured, unstructured
AnswerB

The relational table is the structured component because it imposes a fixed schema of named columns such as product ID and price, each with defined data types and relational constraints. The product descriptions are plain natural-language text files with no predefined fields or data types, so they are unstructured. The product images are binary files (for example, JPEG or PNG) whose content is pixel data with no rows, columns, or queryable schema, making them unstructured as well. Hence the correct classification is structured, unstructured, unstructured.

Why this answer

Product ID and price in a relational database table are structured because they follow a fixed schema with rows and columns. Product descriptions as plain text files have no predefined structure, making them unstructured. Product images as JPEG files are also unstructured because they consist of binary data without a schema.

Thus, the order is structured, unstructured, unstructured, which matches option B.

Exam trap

The trap here is confusing unstructured data (e.g., plain text files) with semi-structured data (e.g., JSON or XML), leading candidates to misclassify product descriptions as semi-structured when they lack any metadata or tags.

Why the other options are wrong

A

Product descriptions as plain text files and product images as JPEG files are both unstructured data, not semi-structured. Semi-structured data has some organizational properties (e.g., JSON, XML), which plain text and JPEG lack.

C

Product descriptions as plain text files are unstructured, not semi-structured. Semi-structured data has tags or markers (e.g., JSON, XML), which plain text lacks.

D

Product descriptions as plain text files are unstructured, not semi-structured. Semi-structured data has tags or markers (e.g., JSON, XML), which plain text lacks.

190
MCQhard

A company stores customer data in a relational table with fixed columns: CustomerID (integer), FirstName (string), LastName (string), Email (string). They also store product images as JPEG files, and customer feedback as JSON documents that may contain varying fields such as rating, comment, and optional metadata. Which of the following correctly orders these data types from most structured to least structured?

A.JSON documents, relational table, JPEG files
B.Relational table, JSON documents, JPEG files
C.JPEG files, JSON documents, relational table
D.Relational table, JPEG files, JSON documents
AnswerB

A relational table is the most structured here because it enforces a fixed schema: each row (customer record) must conform to predefined columns, data types, and constraints such as primary keys or NOT NULL, enabling rigorous integrity and efficient querying. JSON documents are semi-structured because they consist of key-value pairs and nested objects that can vary across documents—there is no required uniform schema, but the names and types of fields provide intrinsic structure. JPEG files are unstructured binary data; their pixel and compression bytes contain no self-describing fields that a database query engine can interpret as discrete attributes. Thus the descending order fixed-schema table → flexible-schema JSON → schema-less binary JPEG is correct.

Why this answer

The relational table is the most structured because it enforces a fixed schema with predefined columns and data types (e.g., CustomerID integer, FirstName string). JSON documents are semi-structured: they have a flexible schema where fields like rating and comment can vary per document, but they still provide key-value organization. JPEG files are unstructured binary data with no internal schema or queryable structure, making them the least structured.

Exam trap

The trap here is that candidates often confuse semi-structured data (JSON) with unstructured data (JPEG), mistakenly thinking JSON is unstructured because its fields can vary, when in fact it retains a key-value structure that makes it semi-structured.

Why the other options are wrong

A

JSON documents are semi-structured (varying fields), not more structured than a relational table (fixed schema). JPEG files are unstructured binary data, so they are the least structured.

C

JPEG files are unstructured binary data, JSON documents are semi-structured (schema-on-read), and relational tables are structured (fixed schema). Ordering from most to least structured should be relational table, JSON documents, JPEG files, not JPEG first.

191
MCQeasy

An organization uses Azure SQL Database and needs to maintain a copy of the database for read-only reporting without affecting the production workload. Which feature should they use?

A.Azure SQL Database read replica
B.Automated backups
C.Active geo-replication
D.Failover groups
AnswerC

Active geo-replication is the correct answer because it provisions a readable secondary database in a different Azure region, with continuous asynchronous data movement from the primary. The secondary can be queried with its own connection string, making it ideal for read-only reporting and analytics while offloading the primary's workload. Because the secondary is a fully accessible online database, it satisfies the requirement for a maintainable read-only copy.

Why this answer

Active geo-replication (Option C) creates a readable secondary replica of an Azure SQL Database in a different Azure region. This secondary replica is continuously updated asynchronously from the primary and can be used for read-only query workloads, offloading reporting traffic without impacting the production database's performance or transaction throughput.

Exam trap

The trap here is that candidates confuse 'read replica' (which exists in Azure SQL Database Hyperscale and Azure SQL Managed Instance) with the standard Azure SQL Database feature, or they mistakenly think failover groups themselves provide the readable copy, when in fact it is Active geo-replication that creates the readable secondary.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database does not support read replicas in the same way as Azure SQL Database for Hyperscale or Azure SQL Managed Instance; the term 'read replica' is not a standard feature for a single Azure SQL Database (non-Hyperscale) — instead, Active geo-replication provides the read-only secondary. Option B is wrong because automated backups are point-in-time restore copies stored in blob storage, not live, readable replicas; they cannot serve ongoing read-only queries without first being restored, which would create a separate database. Option D is wrong because failover groups manage geo-replication and failover orchestration for a group of databases, but the read-only secondary is provided by the underlying Active geo-replication, not by the failover group itself; failover groups are a management layer, not the feature that creates the readable copy.

192
Multi-Selectmedium

Which TWO Azure services are primarily used for data integration and orchestration?

Select 2 answers
A.Azure Logic Apps
B.Azure Synapse Analytics
C.Azure Stream Analytics
D.Azure Analysis Services
E.Azure Data Factory
AnswersA, E

Azure Logic Apps is a cloud service designed for workflow automation and data integration across disparate systems. It provides prebuilt connectors for hundreds of services and enables you to orchestrate data flows using triggers and actions without writing code. This makes it a first-class tool for integrating data between applications and services, which is why it is a correct answer for this question.

Why this answer

Azure Logic Apps is correct because it is a serverless workflow service that integrates apps, data, and services using connectors and triggers, making it ideal for data integration and orchestration. Azure Data Factory is correct because it is a cloud-based ETL and data integration service that orchestrates and automates data movement and transformation across various data stores.

Exam trap

The trap here is that candidates often confuse Azure Synapse Analytics (a data warehouse) or Azure Stream Analytics (a real-time processing service) with data integration tools, because they involve data movement or processing, but they are not primarily designed for orchestration and integration.

193
MCQhard

You are reviewing an ARM template for an Azure Storage account. The container named 'data' is created with public access set to 'None'. What is the primary benefit of this configuration?

A.It encrypts data at rest.
B.It restricts access to authorized users only.
C.It enables soft delete for the container.
D.It prevents accidental deletion of blobs.
AnswerB

When you set a container's public access level to `None`, you disable anonymous access, meaning any request must present valid credentials such as an account key, shared access signature (SAS), or an Azure AD identity with appropriate RBAC role assignments. Authorized users are then the only parties who can read or list blobs in that container. This is the direct function of the `publicAccess` property in the ARM template.

Why this answer

Setting public access to 'None' on a container means that anonymous read requests are not allowed. The primary benefit is that only requests with proper authorization (e.g., using an account key, a shared access signature, or Azure AD credentials) can access the blobs within that container. This directly restricts access to authorized users only, which is the core security advantage.

Exam trap

The trap here is that candidates often confuse 'public access set to None' with broader security features like encryption or deletion protection, when in fact it only controls anonymous read access and does not affect data encryption, soft delete, or accidental deletion safeguards.

How to eliminate wrong answers

Option A is wrong because encryption at rest is enabled by default at the storage account level via Azure Storage Service Encryption (SSE), regardless of the container's public access setting. Option C is wrong because soft delete is a separate data protection feature that must be explicitly enabled on the storage account or container, and it is not a benefit of setting public access to 'None'. Option D is wrong because preventing accidental deletion of blobs is achieved through features like soft delete or immutable storage, not by disabling anonymous access.

194
MCQhard

Your company is designing a data solution for IoT sensor data that arrives in high volume and must be stored for long-term analytics. The data is append-only and rarely updated. You need to choose a storage solution that balances cost and query performance for historical analysis. Which Azure data store should you recommend?

A.Azure Cosmos DB
B.Azure Table Storage
C.Azure SQL Database
D.Azure Data Lake Storage Gen2
AnswerD

Azure Data Lake Storage Gen2 combines the massive, low-cost capacity of Azure Blob Storage with a hierarchical namespace and POSIX-style access control lists, making it ideal for storing raw and curated IoT data at petabyte scale. Append-only files are written sequentially without update-in-place costs, and because storage is decoupled from compute you can run serverless analytics or spin up Spark clusters only when needed. It integrates natively with Azure Synapse Analytics, Azure Databricks, and HDInsight, enabling schema-on-read processing over Parquet or Delta Lake files. For a historical IoT sensor archive, this is the correct foundation because it makes analytics practical and economical.

Why this answer

Azure Data Lake Storage Gen2 is the correct choice because it combines a hierarchical namespace with Azure Blob Storage, offering scalable, cost-effective storage for high-volume append-only data like IoT sensor logs. It supports both structured and unstructured data, integrates with analytics engines like Azure Synapse and Spark, and provides POSIX-compliant access control, making it ideal for long-term historical analysis at low cost.

Exam trap

The trap here is that candidates often confuse Azure Cosmos DB's low-latency capabilities with suitability for high-volume historical analytics, overlooking its cost model and lack of native file-system semantics for append-only workloads.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a NoSQL database optimized for low-latency, transactional workloads with global distribution, not for cost-effective long-term storage of append-only IoT data; its per-request pricing and high throughput costs make it unsuitable for high-volume historical analytics. Option B is wrong because Azure Table Storage is a key-value store designed for simple, semi-structured data with limited query capabilities (only on partition and row keys), lacking the hierarchical namespace, file-level security, and native analytics integration needed for complex historical queries on IoT data. Option C is wrong because Azure SQL Database is a relational database with ACID transactions and indexing, which is over-provisioned and expensive for append-only IoT data that rarely updates; its per-core pricing and storage limits make it cost-prohibitive for high-volume, long-term storage compared to object storage.

195
MCQeasy

A hospital collects patient vital signs every minute using IoT sensors. Each reading contains a timestamp, patient ID, heart rate, blood pressure, and temperature. This data is ingested continuously for real-time monitoring and alerting. Which type of data workload does this scenario best represent?

A.A. Transactional workload
B.B. Analytical workload
C.C. Batch processing
D.D. Real-time streaming
AnswerD

Real-time streaming workloads handle continuous data flows that are processed as soon as they arrive, often with low latency requirements. The hospital's IoT sensors generate data every minute that must be acted on promptly, making this a clear example of a real-time streaming workload.

Why this answer

This scenario requires continuous ingestion of sensor data with immediate processing for real-time monitoring and alerting. Real-time streaming workloads, such as those handled by Azure Stream Analytics or Apache Kafka, are designed to process unbounded data streams with low latency, making option D correct.

Exam trap

The trap here is confusing 'real-time streaming' with 'analytical workload' because both involve data processing, but analytical workloads are designed for historical analysis and reporting, not for sub-second alerting on live data streams.

How to eliminate wrong answers

Option A is wrong because transactional workloads focus on ACID-compliant operations (e.g., OLTP) that handle discrete, small-scale read/write operations, not continuous high-velocity sensor streams. Option B is wrong because analytical workloads typically involve batch or interactive queries over historical data (e.g., using Azure Synapse or Power BI), not millisecond-level alerting on live data. Option C is wrong because batch processing processes data in large, scheduled chunks (e.g., nightly ETL jobs), which cannot meet the real-time alerting requirement of this scenario.

196
MCQeasy

A database system ensures that a transaction either completes fully and all changes are applied, or it is completely rolled back and no partial changes are saved. Which property of ACID transactions does this describe?

A.Atomicity
B.Consistency
C.Isolation
D.Durability
AnswerA

Atomicity treats a transaction as an indivisible unit of work: every statement inside it must succeed for any of them to be applied. If any step fails, a rollback undoes all prior changes, restoring the pre-transaction state. This all-or-nothing property is enforced by database recovery mechanisms such as write-ahead logging or undo segments, ensuring no partial updates survive. Thus, it directly answers the question about a transaction either completing fully or not at all.

Why this answer

Atomicity ensures that a transaction is treated as a single, indivisible unit of work. If any part of the transaction fails, the entire transaction is rolled back, leaving the database in its original state. This property guarantees that no partial changes are saved, which directly matches the description in the question.

Exam trap

Microsoft often tests the distinction between atomicity and consistency by describing a scenario where a transaction either fully applies or fully rolls back, leading candidates to mistakenly choose consistency because they associate 'valid state' with 'complete execution'.

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, cascades, triggers), but it does not address the 'all-or-nothing' execution of the transaction itself. Option C (Isolation) is wrong because isolation controls how transaction changes are visible to other concurrent transactions (e.g., via locking or snapshot isolation), not whether the transaction completes fully or rolls back. Option D (Durability) is wrong because durability guarantees that once a transaction is committed, its changes persist even after a system failure (e.g., via write-ahead logging), but it does not describe the rollback behavior on failure.

197
MCQmedium

A retail company captures real-time sensor data from IoT devices to detect anomalies and predict equipment failures. The data must be processed immediately as it arrives. Which type of data processing workload best describes this scenario?

A.Batch processing
B.Streaming processing
C.Online transaction processing (OLTP)
D.Data warehousing
AnswerB

Streaming processing is the correct choice because it ingests and analyzes data continuously as it arrives, rather than waiting for a complete dataset. For real-time IoT sensor feeds, services like Azure Stream Analytics can process event streams with sub-second latency, applying time-windowed aggregations, filters, and anomaly detection logic to trigger immediate alerts. This supports proactive failure prediction and operational monitoring, which is impossible with store-then-process approaches.

Why this answer

B is correct because streaming processing is designed for continuous, real-time data ingestion and immediate analysis, which matches the requirement to process sensor data as it arrives. Technologies like Azure Stream Analytics or Apache Kafka enable low-latency processing of IoT data streams to detect anomalies and predict failures without batching.

Exam trap

Microsoft often tests the distinction between batch and streaming by describing a scenario with 'immediate' or 'real-time' requirements, and candidates mistakenly choose batch processing because they overlook the latency constraint.

Why the other options are wrong

A

Batch processing processes data in large, scheduled chunks, not immediately as it arrives. The scenario requires real-time processing of sensor data for immediate anomaly detection, which batch processing cannot provide.

C

OLTP is designed for managing transactional data (e.g., order processing) with ACID guarantees, not for real-time processing of continuous sensor data streams for anomaly detection.

D

Data warehousing is designed for storing and analyzing historical, structured data from multiple sources, not for processing real-time streaming data from IoT devices.

198
MCQeasy

A social media application displays the number of posts each user has created. After a user submits a new post, the count must reflect the update across all servers within a few seconds. Which data consistency model best describes this requirement?

A.Strong consistency
B.Eventual consistency
C.Sequential consistency
D.Causal consistency
AnswerB

Eventual consistency allows updates to propagate asynchronously to replicas, guaranteeing that if no further updates occur, all replicas will return the same value after a short period. This matches the requirement of reflecting the update within a few seconds.

Why this answer

Eventual consistency is correct because the requirement allows a few seconds for the update to propagate across all servers, meaning the system does not guarantee immediate uniformity but will converge to the same count eventually. This is typical in distributed systems like social media applications where high availability and partition tolerance are prioritized over immediate consistency, often using techniques like asynchronous replication.

Exam trap

The trap here is that candidates confuse 'eventual consistency' with 'weak consistency' or assume that any delay means strong consistency is required, but the key is the explicit tolerance of a few seconds, which aligns with eventual consistency's convergence guarantee.

How to eliminate wrong answers

Option A is wrong because strong consistency would require all servers to reflect the new post count immediately upon write, which conflicts with the 'within a few seconds' tolerance and would impose performance penalties in a distributed system. Option C is wrong because sequential consistency ensures operations appear in a global order consistent with program order, which is stricter than needed and not typically used for simple count updates across servers. Option D is wrong because causal consistency preserves the order of causally related events, which is unnecessary for a simple counter update that has no causal dependencies with other operations.

199
MCQeasy

A retail company processes customer orders throughout the day. Each order involves inserting a new record into a database table, updating inventory counts, and deleting temporary cart data. At the end of each week, the company runs a query that aggregates all orders by product category and region to generate a sales report. Which of the following best describes these two workloads?

A.Order processing is OLAP; weekly reporting is OLTP
B.Order processing is batch processing; weekly reporting is streaming processing
C.Order processing is OLTP; weekly reporting is OLAP
D.Both workloads are OLTP
AnswerC

Order processing is OLTP because each customer order is a discrete transactional unit—creating, updating, and querying order records with ACID guarantees and low-latency, high-concurrency operations. Weekly reporting is OLAP because it requires complex aggregations and analytical scans over large historical order datasets, a pattern optimized in columnar or data warehouse systems. This correctly distinguishes the two common data workload patterns based on access pattern and purpose.

Why this answer

Order processing involves frequent, small transactions (inserts, updates, deletes) that are typical of Online Transaction Processing (OLTP) workloads, which prioritize data integrity and low-latency writes. The weekly sales report aggregates large volumes of historical data by product category and region, which is characteristic of Online Analytical Processing (OLAP) workloads that support complex queries and data summarization. Option C correctly identifies these two distinct workload types.

Exam trap

The trap here is that candidates confuse the terms OLTP and OLAP, mistakenly thinking that any database operation is OLTP or that reporting is always OLTP, when in fact the key differentiator is the workload pattern—transactional vs. analytical.

Why the other options are wrong

A

Order processing involves individual transactions (inserts, updates, deletes) typical of OLTP, not OLAP. Weekly reporting aggregates historical data across categories and regions, which is OLAP, not OLTP.

B

Order processing involves individual transactions (insert, update, delete) and is OLTP, not batch processing. Weekly reporting aggregates historical data and is OLAP, not streaming processing.

D

The weekly reporting aggregates historical data across product categories and regions, which is analytical processing (OLAP), not OLTP. Both workloads are not OLTP because reporting involves complex queries over large datasets, not transaction-oriented operations.

200
MCQeasy

A data engineer needs to load data from an on-premises SQL Server database to Azure Synapse Analytics every hour with minimal latency. Which Azure service should they use?

A.Azure Databricks
B.Azure Data Factory
C.Azure SQL Database
D.Azure HDInsight
AnswerB

Azure Data Factory is the correct choice because it is a cloud-based ETL and data integration service purpose-built for orchestrating and automating data movement. It provides a self-hosted integration runtime that securely connects to on-premises SQL Server databases, and its schedule triggers can run pipelines every hour with minimal latency. The service is designed specifically for copying data from sources like on-premises SQL Server to cloud destinations, making it the ideal tool for this workload.

Why this answer

Azure Data Factory (ADF) is the correct choice because it provides a fully managed, code-free ETL service that can connect to on-premises SQL Server via self-hosted integration runtime, and load data into Azure Synapse Analytics with low latency using a scheduled trigger (e.g., every hour). ADF supports incremental data loading and parallel copy activities, minimizing latency while handling the required frequency.

Exam trap

The trap here is that candidates often confuse Azure Data Factory with Azure Databricks or HDInsight, assuming any big data or analytics service can handle scheduled data ingestion, but only ADF is purpose-built for orchestration and low-latency data movement from on-premises sources.

How to eliminate wrong answers

Option A is wrong because Azure Databricks is an Apache Spark-based analytics platform designed for big data processing and machine learning, not a dedicated data ingestion or orchestration service; it lacks native scheduling and on-premises connectivity for hourly low-latency loads without additional setup. Option C is wrong because Azure SQL Database is a relational database service, not a data integration or orchestration tool; it cannot directly load data from on-premises SQL Server into Synapse Analytics on a schedule. Option D is wrong because Azure HDInsight is a managed Hadoop/Spark cluster service for big data analytics, not a data movement or orchestration service; it requires custom scripting and manual scheduling to perform hourly loads, adding complexity and latency.

201
MCQeasy

A company stores customer data in a SQL Server database table with columns: CustomerID (integer), Name (varchar), Email (varchar), SignupDate (date). All rows adhere to this schema. Which type of data does this represent?

A.Structured data
B.Unstructured data
C.Semi-structured data
D.Transactional data
AnswerA

Structured data conforms to a rigid, predefined schema, typically organized into rows and columns. In a SQL Server database, the customer table enforces data types, constraints, and relationships, enabling efficient querying via SQL. This fixed tabular format is the hallmark of structured data.

Why this answer

This data is structured because it conforms to a fixed schema with clearly defined columns (CustomerID, Name, Email, SignupDate) and data types (integer, varchar, date). In SQL Server, structured data is stored in tables with rows and columns, enabling efficient querying via T-SQL and indexing. The consistent adherence to the schema across all rows is the hallmark of structured data.

Exam trap

The trap here is that candidates confuse the content of the data (e.g., customer information) with its structure, or mistakenly think that any data in a database is automatically structured, ignoring the distinction between structured, semi-structured, and unstructured formats.

How to eliminate wrong answers

Option B is wrong because unstructured data has no predefined schema or organization (e.g., text files, images, videos), whereas this table has a rigid schema. Option C is wrong because semi-structured data (e.g., JSON, XML) allows schema flexibility and nested structures, but this table enforces fixed columns and data types. Option D is wrong because transactional data refers to records of business transactions (e.g., sales orders, payments), not the general classification of data format; this table could store transactional data, but the question asks about the type of data based on its structure.

202
MCQeasy

A company ingests streaming data from social media feeds and needs to process and analyze the data in real time. Which Azure service should they use to capture the stream?

A.Azure Stream Analytics
B.Azure IoT Hub
C.Azure Event Hubs
D.Azure Data Lake Storage
AnswerC

Azure Event Hubs is a fully managed, highly scalable event ingestion service that accepts millions of events per second from diverse publishers, including social media APIs. It provides partitioned streams with configurable retention, enabling multiple independent consumers to read the same events through separate consumer groups. Its AMQP and Kafka-compatible endpoints make it the standard real-time ingestion front door for high-volume social media feeds.

Why this answer

Azure Event Hubs is a fully managed, real-time data ingestion service designed to capture and process millions of events per second from sources like social media feeds. It provides a scalable, low-latency endpoint for streaming data, making it the correct choice for capturing the stream before further analysis.

Exam trap

The trap here is that candidates confuse Azure Stream Analytics (a processing service) with Event Hubs (an ingestion service), or assume IoT Hub is suitable for non-IoT streaming data due to its similar event ingestion capability.

How to eliminate wrong answers

Option A is wrong because Azure Stream Analytics is a stream processing engine that analyzes data in motion, not a capture/ingestion service; it typically consumes from Event Hubs or IoT Hub. Option B is wrong because Azure IoT Hub is specifically built for bidirectional communication with IoT devices, not for general-purpose social media stream ingestion, and it lacks the high-throughput, multi-protocol ingestion capabilities of Event Hubs. Option D is wrong because Azure Data Lake Storage is a hierarchical file store for batch and analytics workloads, not a real-time streaming capture service; it cannot ingest streaming data directly without an intermediary like Event Hubs or Stream Analytics.

203
MCQeasy

A company stores customer data in a SQL Server table with fixed columns (CustomerID, Name, Email, SignupDate). The company also stores application logs as JSON documents and marketing images as JPEG files. Which data type describes the customer data?

A.Structured data
B.Semi-structured data
C.Unstructured data
D.Relational data
AnswerA

Structured data is correct because the data is stored in a SQL Server table with a fixed schema: every row must conform to predefined column names, data types, and constraints. This rigid, table-based organization allows efficient indexing, querying, and integrity enforcement, making it the textbook definition of structured data. The term directly contrasts with semi-structured and unstructured data, both of which lack such a uniform, enforced schema.

Why this answer

Customer data stored in a SQL Server table with fixed columns (CustomerID, Name, Email, SignupDate) follows a rigid schema where each row has the same set of columns with defined data types. This conforms to the relational model, making it structured data. Structured data is organized into rows and columns with a fixed schema, enabling efficient querying via SQL.

Exam trap

The trap here is that candidates confuse 'relational data' (a storage model) with 'structured data' (a data type category), leading them to pick D instead of A, even though the question explicitly asks for the data type.

How to eliminate wrong answers

Option B is wrong because semi-structured data (e.g., JSON, XML) does not enforce a fixed schema; it allows flexible key-value pairs or nested structures, which does not match the fixed-column SQL Server table. Option C is wrong because unstructured data (e.g., JPEG images, plain text files) lacks a predefined data model or organization, unlike the tabular customer data. Option D is wrong because 'relational data' is not a data type category in the DP-900 core data concepts; it describes a storage model (relational databases) that can hold structured data, but the question asks for the data type, not the storage model.

204
MCQeasy

A retail company maintains a database of customer information including CustomerID, Name, Address, and Phone. Each record follows the same fixed schema. This type of data is best described as:

A.Structured data
B.Semi-structured data
C.Unstructured data
D.Relational data
AnswerA

Structured data adheres to a predefined schema, with each record consisting of named columns that enforce specific data types and constraints. In a retail customer database, tables store fields such as CustomerID, FirstName, LastName, and Email, making the data easily queryable using SQL. This fixed, tabular arrangement is precisely what classifies it as structured data.

Why this answer

Structured data conforms to a fixed schema where each record has the same fields (CustomerID, Name, Address, Phone) and data types, making it ideal for relational database storage. This rigid, tabular format allows efficient querying using SQL and enforces consistency across all rows.

Exam trap

The trap here is that candidates confuse 'relational data' (a storage model) with 'structured data' (a data type), leading them to select Option D, but the DP-900 exam categorizes data by its structure, not by the database system used to store it.

How to eliminate wrong answers

Option B is wrong because semi-structured data (e.g., JSON, XML) does not enforce a fixed schema; fields can vary between records, unlike the uniform schema described. Option C is wrong because unstructured data (e.g., images, videos, text files) has no predefined structure or schema, whereas customer records with fixed fields are clearly organized. Option D is wrong because 'relational data' is not a data type category in the DP-900 taxonomy; it refers to a database model that stores structured data, but the question asks for the data type itself, not the storage model.

205
MCQeasy

A data file contains records for customer orders. Each record has fields for OrderID, CustomerID, and OrderDate that are present in every record. However, some records include an optional 'DiscountCode' field, and others include an optional 'GiftMessage' field. The file is stored in JSON format. Which type of data does this file represent?

A.Structured data
B.Semi-structured data
C.Unstructured data
D.Transactional data
AnswerB

Semi-structured data has organizational properties such as tags, keys, or hierarchies but does not enforce a uniform schema on every record. A JSON file of customer orders fits this definition: each order is a document with key-value pairs, nested objects, and optional properties like shipping_address, while the overall set of documents can vary in shape. This is the correct structural category.

Why this answer

The JSON file contains records with a fixed set of fields (OrderID, CustomerID, OrderDate) that are always present, but also includes optional fields (DiscountCode, GiftMessage) that may appear in some records but not others. This mix of a consistent schema with flexible, self-describing fields is the hallmark of semi-structured data. JSON itself is a semi-structured format because it uses key-value pairs and allows nested or optional attributes without requiring a rigid schema.

Exam trap

The trap here is that candidates confuse 'semi-structured' with 'unstructured' because they see optional fields and think the data has no structure, but the presence of a consistent base schema (OrderID, CustomerID, OrderDate) clearly distinguishes it as semi-structured.

How to eliminate wrong answers

Option A is wrong because structured data requires a fixed schema (e.g., a relational table with predefined columns), but this JSON file allows optional fields that may be missing from some records, violating the strict schema requirement. Option C is wrong because unstructured data has no predefined structure or organization (e.g., raw text, images, audio), whereas this file has a consistent base schema with OrderID, CustomerID, and OrderDate in every record. Option D is wrong because transactional data refers to data that records events or transactions (like orders), but this is a classification of data content, not a classification of data structure; the question asks about the type of data based on its format, not its business use.

206
MCQmedium

Your company stores customer data in Azure Blob Storage. To comply with data residency regulations, you must ensure data is replicated within the same Azure region. Which replication option should you choose?

A.Zone-redundant storage (ZRS)
B.Locally-redundant storage (LRS)
C.Geo-redundant storage (GRS)
D.Read-access geo-redundant storage (RA-GRS)
AnswerB

Locally-redundant storage (LRS) writes three synchronous copies of your customer data within a single physical data center in the primary Azure region. Every replica remains inside the same datacenter and region, so no data is ever replicated across availability-zone or regional boundaries, satisfying strict data-residency requirements. LRS is the lowest-cost redundancy tier that still provides a durable copy when the requirement is simply to keep data in one geography.

Why this answer

Locally-redundant storage (LRS) replicates data three times within a single physical location in the same Azure region, ensuring data residency compliance by never copying data outside that region. This is the only option that guarantees all replicas stay within one region without any cross-region or cross-zone replication.

Exam trap

The trap here is that candidates often confuse 'replication within the same region' with 'zone-redundant storage' (ZRS) because ZRS also stays within the region, but the question's emphasis on 'data residency' and 'same region' is designed to test whether you know that LRS is the simplest and most restrictive option that keeps all copies in a single location, while ZRS still uses multiple zones which may be considered separate data centers for some compliance definitions.

How to eliminate wrong answers

Option A is wrong because Zone-redundant storage (ZRS) replicates data synchronously across three Azure availability zones within the same region, which still satisfies data residency but is not the simplest or most cost-effective choice when only intra-region replication is required; however, the question asks for the option that ensures data is replicated within the same region, and ZRS does that, but LRS is more directly aligned with the 'same region' requirement without zone-level distribution. Option C is wrong because Geo-redundant storage (GRS) replicates data to a secondary region that is hundreds of miles away, violating data residency regulations that require data to stay within a single region. Option D is wrong because Read-access geo-redundant storage (RA-GRS) also replicates data to a secondary region and additionally provides read access to that secondary copy, which still breaks the data residency constraint.

207
MCQeasy

A ride-sharing company processes trip requests from customers. Each trip is recorded as a single transaction that updates the driver's status, calculates the fare, and logs the ride. At the end of each month, the company runs reports that aggregate millions of trips to determine average wait times and revenue per driver. Which pair of terms best describes these two distinct workloads?

A.OLTP and OLAP
B.Batch processing and stream processing
C.ETL and ELT
D.Relational and non-relational
AnswerA

OLTP (Online Transaction Processing) is the correct workload type for the immediate trip-request workflow: each request creates or updates a small, atomic transaction with high concurrency and fast response times. OLAP (Online Analytical Processing) correctly describes the monthly reporting and aggregation workload, which scans and aggregates large volumes of historical trip data for business analysis. Together they identify the operational versus analytical workload split the question is asking about, rather than data movement patterns or storage models.

Why this answer

The first workload (trip request processing) is a classic OLTP (Online Transaction Processing) system because each trip is a single, atomic transaction that updates driver status, calculates fare, and logs the ride in real time. The second workload (monthly aggregation reports) is OLAP (Online Analytical Processing) because it queries millions of historical trip records to compute averages and revenue summaries. These two patterns have fundamentally different data storage and query optimization requirements, making OLTP and OLAP the correct pair.

Exam trap

The trap here is that candidates confuse the processing method (batch/stream) with the workload type (OLTP/OLAP), but the question specifically asks for the pair that best describes the distinct workloads—transactional updates vs. analytical reporting—which is the classic OLTP vs. OLAP distinction.

Why the other options are wrong

B

The question describes two distinct workloads: individual trip transactions (OLTP) and monthly aggregation reports (OLAP). Batch processing and stream processing refer to how data is processed (in batches vs. continuously), not the nature of the workloads themselves, and the monthly reports are batch processing but the trip processing is not stream processing.

C

The question describes two distinct workloads: transaction processing (trip requests) and analytical reporting (monthly aggregates). ETL and ELT are data integration processes, not workload types; they are used to move and transform data between systems, not to describe the operational vs. analytical nature of the workloads.

D

The question contrasts transactional trip processing (OLTP) with analytical monthly reporting (OLAP), not data storage models. Relational vs. non-relational describes database types, not workload categories.

208
MCQeasy

A company stores customer records in a relational database table with fixed columns (CustomerID, Name, Email). They also store product reviews as JSON documents that may contain varying fields such as Rating, Comment, and optional Tags. Additionally, they store product images as JPEG files. Which of the following correctly orders these data types from most structured to least structured?

A.JSON documents, relational table, image files
B.Relational table, JSON documents, image files
C.Image files, relational table, JSON documents
D.Relational table, image files, JSON documents
AnswerB

Relational tables enforce a rigid schema with predefined columns, data types, and constraints, making them the most structured form. JSON documents use key-value pairs and nested objects but permit varying fields across documents, classifying them as semi-structured. Image files are raw binary streams with no inherent schema or semantic structure, therefore unstructured. This ordering correctly progresses from highest to lowest structural organization.

Why this answer

Relational tables enforce a fixed schema with predefined columns and data types, making them the most structured. JSON documents have a flexible schema where fields like Tags are optional, placing them in the middle. Image files are binary blobs with no inherent structure, making them the least structured.

Option B correctly orders these from most structured (relational table) to least structured (image files).

Exam trap

The trap here is that candidates often confuse semi-structured JSON with unstructured data, or assume that all data with a format (like JPEG headers) is structured, but the key distinction is schema rigidity and queryability.

Why the other options are wrong

A

JSON documents are semi-structured (schema-on-read), not more structured than a relational table with fixed columns, which is fully structured. Image files are unstructured, so the correct order is relational table (most structured), JSON documents, image files (least structured).

C

Image files are unstructured, not more structured than relational tables or JSON documents. Relational tables are the most structured, followed by semi-structured JSON, then unstructured images.

D

Image files are unstructured, not more structured than JSON documents. JSON documents have some structure (key-value pairs), while relational tables are fully structured with fixed schema.

209
MCQhard

A data engineer needs to implement a solution that provides near real-time analytics on clickstream data. The data arrives as JSON events and must be queryable with sub-second latency using SQL-like queries. The solution should minimize operational overhead. Which Azure service should they use?

A.Azure Stream Analytics
B.Azure Analysis Services
C.Azure Synapse Analytics
D.Azure Data Explorer
AnswerD

Azure Data Explorer (ADX) is a fully managed, high-performance analytics service built specifically for near real-time telemetry, logs, and time-series data, using the Kusto Query Language (KQL) to filter, aggregate, and join events. It ingests data directly from Event Hubs and IoT Hub with low latency, and its columnar index and sharding design support sub-second query responses on massive streams of append-only data. This combination of rapid ingestion, optimized storage, and fast query execution directly satisfies the requirement for a sub-second analytical solution on streaming data.

Why this answer

Azure Data Explorer (ADX) is designed for interactive analytics on large volumes of streaming and historical data with sub-second query latency using Kusto Query Language (KQL), which supports SQL-like syntax. It natively ingests JSON events, provides near real-time analytics, and minimizes operational overhead as a fully managed, serverless service.

Exam trap

The trap here is that candidates often confuse Azure Stream Analytics (a real-time processing engine) with Azure Data Explorer (an interactive analytics database), failing to recognize that the requirement for 'sub-second latency using SQL-like queries' on stored data points to a query engine, not a stream processor.

How to eliminate wrong answers

Option A is wrong because Azure Stream Analytics is a real-time stream processing engine that outputs to sinks (e.g., Power BI, Event Hubs) but does not natively support sub-second interactive SQL queries on stored data; it is designed for continuous queries, not ad-hoc analytics. Option B is wrong because Azure Analysis Services is an OLAP engine for semantic models and multidimensional cubes, not designed for raw clickstream JSON ingestion or sub-second query latency on streaming data. Option C is wrong because Azure Synapse Analytics is a big data analytics platform optimized for large-scale batch and interactive queries using dedicated SQL pools, but it incurs higher operational overhead and is not purpose-built for near real-time, sub-second latency on high-velocity streaming JSON events.

210
MCQeasy

A retail chain collects sales data from all its stores at the end of each business day by exporting CSV files from each store's database. The data is then combined and analyzed to generate daily sales reports. Which type of data processing does this describe?

A.Batch processing
B.Real-time processing
C.Stream processing
D.Interactive query
AnswerA

Batch processing executes data transformation and loading as discrete, scheduled jobs that operate on a finite set of data accumulated over time. In this scenario, store sales data is uploaded at the end of each business day, and an Azure Data Factory pipeline runs on a fixed schedule to transform and load it into Azure Synapse Analytics. This matches a typical ETL batch pattern, providing predictable, cost-efficient processing while trading off latency — results are ready the next morning, not instantly.

Why this answer

This describes batch processing because sales data is collected from each store at the end of the business day, exported as CSV files, and then combined and analyzed in a scheduled, non-continuous manner. Batch processing is ideal for large volumes of data that are processed at periodic intervals, such as daily sales reports, rather than requiring immediate action.

Exam trap

The trap here is that candidates confuse 'daily export' with 'real-time' because they think 'daily' implies frequent updates, but batch processing is defined by the scheduled, non-continuous nature of the data collection and processing, not the frequency.

Why the other options are wrong

B

The data is collected at the end of each business day, not continuously or with low latency, so it is not real-time processing.

C

Stream processing handles data continuously as it arrives, but here data is collected at the end of each day in batches from CSV exports, not processed in real-time as events occur.

D

Interactive query implies ad-hoc, on-demand analysis of data, but the scenario describes a scheduled, automated process that combines data at the end of each day, which is batch processing.

211
MCQeasy

A company wants to run SQL queries on data stored in Azure Cosmos DB for NoSQL. Which API should they use?

A.Core (SQL) API
B.Gremlin API
C.Cassandra API
D.MongoDB API
AnswerA

The Core (SQL) API is the native and default API for Azure Cosmos DB, optimized for querying JSON documents using a SQL query dialect. It supports familiar relational constructs such as SELECT, WHERE, JOIN, and GROUP BY, adapted to work on schema-flexible NoSQL data. This makes it the only API that directly accepts SQL queries without translation or compatibility layers.

Why this answer

The Core (SQL) API is the native API for Azure Cosmos DB for NoSQL, designed to query JSON documents using a SQL-like syntax. Since the requirement is to run SQL queries on data stored in Azure Cosmos DB for NoSQL, this API directly supports that need without requiring any protocol translation or schema mapping.

Exam trap

The trap here is that candidates often confuse 'SQL queries' with the Cassandra API because both use a SQL-like language, but Cassandra uses CQL, not standard SQL, and is designed for a different data model (wide-column vs. document).

How to eliminate wrong answers

Option B (Gremlin API) is wrong because it is used for graph data models and queries using the Apache TinkerPop graph traversal language, not for SQL queries on NoSQL documents. Option C (Cassandra API) is wrong because it implements the Apache Cassandra wire protocol for wide-column stores and uses CQL (Cassandra Query Language), not standard SQL. Option D (MongoDB API) is wrong because it provides compatibility with MongoDB's document model and query syntax (e.g., BSON, find(), aggregate()), not SQL.

212
Multi-Selectmedium

Which TWO of the following are correct descriptions of data processing workloads in Azure?

Select 2 answers
A.Streaming processing is used for interactive queries on historical data.
B.Streaming processing is used to process data at rest.
C.Streaming processing is used to process data in real time as it arrives.
D.Batch processing is used to process data in real time as it arrives.
E.Batch processing is used to process large volumes of data at scheduled intervals.
AnswersC, E

Streaming processing is purpose-built for real-time data: it ingests events continuously from sources like Azure Event Hubs or IoT Hub and processes them as they arrive, often with sub-second latency. This architecture enables real-time dashboards, anomaly alerts, and event-driven responses where decisions must be made on the latest data. For example, a streaming pipeline might aggregate clickstream events into 5-second windows to show current user activity, which is impossible with batch processing that defers computation until a scheduled run.

Why this answer

Streaming processing in Azure (e.g., Azure Stream Analytics, Event Hubs, or Kafka on HDInsight) is designed to ingest, analyze, and act on data in near real-time as it arrives, often with sub-second latency. This is fundamentally different from batch processing, which handles data at rest.

Exam trap

The trap here is that candidates confuse 'streaming' with 'interactive querying' or assume batch can handle real-time data, but Azure explicitly separates these workloads based on data state (in motion vs. at rest) and latency requirements.

213
MCQmedium

The exhibit shows a T-SQL query against an Azure SQL Database. What is the purpose of the HAVING clause in this query?

A.To sort the result set by TotalSales descending
B.To join two tables
C.To filter groups after aggregation
D.To filter rows before grouping
AnswerC

The HAVING clause is used to filter groups after aggregation has been performed. In the query shown, the GROUP BY clause likely groups rows by one or more columns, and then HAVING applies a condition to the aggregated TotalSales value (e.g., HAVING SUM(TotalSales) > 1000) to keep only certain groups. This differs from WHERE, which cannot reference aggregate functions, whereas HAVING is evaluated after GROUP BY and can directly test SUM, COUNT, AVG, and other aggregate results.

Why this answer

The HAVING clause is used in T-SQL to filter groups after the GROUP BY clause has performed aggregation. In this query, it restricts the result set to only those product categories whose total sales (SUM(Amount)) exceed 1000, which is a condition on the aggregated value, not on individual rows.

Exam trap

The trap here is that candidates often confuse HAVING with WHERE, mistakenly thinking HAVING filters individual rows before grouping, when in fact WHERE performs that role and HAVING only applies after aggregation.

How to eliminate wrong answers

Option A is wrong because sorting the result set is done by the ORDER BY clause, not HAVING. Option B is wrong because joining tables is accomplished with JOIN clauses (e.g., INNER JOIN, LEFT JOIN), not HAVING. Option D is wrong because filtering rows before grouping is the role of the WHERE clause, which operates on individual rows before aggregation; HAVING filters after aggregation.

214
MCQmedium

A healthcare application stores patient vital signs readings. Each reading is a JSON document with fields: PatientID, Timestamp, HeartRate, BloodPressure (systolic and diastolic). The application frequently queries for all readings of a specific patient within a time range, and the schema varies occasionally (e.g., new optional fields are added). How should this data be classified?

A.Structured
B.Semi-structured
C.Unstructured
D.Relational
AnswerB

Semi-structured data, such as JSON, XML, or key-value pairs, uses tags or markers to separate elements and permits schema flexibility. Vital signs readings naturally fit this model because each reading can include a variable set of measured parameters (e.g., some include SpO2, some include respiratory rate) without requiring every record to have identical fields, and the order of fields does not matter.

Why this answer

The data is semi-structured because it is stored as JSON documents, which have a flexible schema that can vary between records (e.g., new optional fields can be added). JSON documents are self-describing and do not require a fixed schema like relational tables, but they still have organizational properties (fields like PatientID, Timestamp) that distinguish them from unstructured data like plain text or images. The application's queries on specific fields (PatientID, Timestamp) further confirm the data has structure, but the schema flexibility rules out structured or relational classifications.

Exam trap

The trap here is that candidates confuse 'structured' with 'having fields'—they see PatientID and Timestamp and assume it must be structured, but the key differentiator is schema flexibility (optional fields, varying structure) which defines semi-structured data.

How to eliminate wrong answers

Option A is wrong because structured data requires a rigid, predefined schema (e.g., fixed columns and data types in a SQL table), but JSON documents allow schema variation and optional fields, which violates the strict schema constraint. Option C is wrong because unstructured data has no predefined data model or organization (e.g., raw text files, images, videos), whereas JSON documents have named fields and a hierarchical structure that can be parsed and queried. Option D is wrong because relational data is a subset of structured data that enforces relationships through foreign keys and normalization, but JSON documents in this scenario are not stored in relational tables and do not enforce referential integrity or a fixed schema.

215
MCQhard

Your organization has a data warehouse in Azure Synapse Analytics. You need to load data from Azure Blob Storage daily, transforming it using a data flow. Which Azure service should you use for the ETL process?

A.Azure Databricks
B.Azure Data Factory
C.Azure Logic Apps
D.Azure Synapse Pipelines
AnswerB

Azure Data Factory is the correct choice because its mapping data flows provide a visual, code-free environment for designing ETL transformations by connecting source and sink datasets and arranging transformation activities on a canvas. These data flows execute on a managed Spark cluster, allowing complex joins, aggregations, and derived columns to be built declaratively without writing any code, making it the core ETL service for a data warehouse in Azure.

Why this answer

Azure Data Factory (ADF) is the correct choice because it provides native integration with Azure Synapse Analytics and Azure Blob Storage, and it includes a visual data flow designer for transforming data without writing code. ADF's mapping data flows execute at scale on Spark clusters, making it ideal for daily ETL workloads that require both ingestion and transformation.

Exam trap

The trap here is that candidates confuse Azure Synapse Pipelines (which is just ADF inside Synapse) as a separate service, but the correct Azure service name for the ETL tool is Azure Data Factory, not Synapse Pipelines.

How to eliminate wrong answers

Option A is wrong because Azure Databricks is a big data analytics platform that requires you to write code (Python, Scala, SQL) to build transformations, and it does not have a native, no-code data flow designer like ADF; it is overkill for a simple daily load with transformations. Option C is wrong because Azure Logic Apps is a workflow automation service designed for integrating SaaS applications and orchestrating business processes, not for performing data transformations at scale or loading data into a data warehouse. Option D is wrong because Azure Synapse Pipelines is actually built on top of Azure Data Factory and shares the same engine, but the standalone service name for the ETL tool is Azure Data Factory; Synapse Pipelines is a feature within Synapse, not a separate service, and the question asks for the Azure service, which is Azure Data Factory.

216
MCQmedium

A company stores customer data in a relational database. The database design includes a rule that every order must be associated with a valid customer ID that exists in the Customers table. This rule is an example of which data concept?

A.Referential integrity
B.Data normalization
C.Entity integrity
D.Data consistency
AnswerA

Referential integrity is a database constraint enforced by foreign keys: it guarantees that every value in a foreign key column exactly matches an existing primary key value in the referenced table, thereby preventing orphaned rows. This rule is precisely what the scenario describes—the relational database uses these key relationships to maintain valid associations between customer records and related tables.

Why this answer

Referential integrity ensures that relationships between tables remain consistent. In a relational database, a foreign key constraint enforces that every order's customer ID must match an existing customer ID in the Customers table, preventing orphaned records. This rule directly implements referential integrity as defined by the SQL standard (e.g., via FOREIGN KEY constraints).

Exam trap

The trap here is that candidates often confuse referential integrity with entity integrity, mistakenly thinking that any rule involving a 'valid ID' is about primary keys, when in fact it is about foreign key relationships between tables.

How to eliminate wrong answers

Option B is wrong because data normalization is a design process to reduce data redundancy and avoid anomalies (e.g., 1NF, 2NF, 3NF), not a rule that enforces valid cross-table relationships. Option C is wrong because entity integrity ensures that the primary key of a table is unique and not null, which applies to the Customers table's customer ID column, not to the foreign key relationship from Orders to Customers. Option D is wrong because data consistency is a broader property of the database state (e.g., ensuring all constraints are satisfied), not a specific constraint type; referential integrity is one mechanism to achieve consistency, but the rule itself is a referential integrity constraint.

217
MCQmedium

A company stores customer transaction data in Azure Blob Storage. The data is rarely accessed after 30 days, but must be retained for 7 years for compliance. Which access tier minimizes storage cost while meeting the retention requirement?

A.Hot tier
B.Cool tier
C.Premium tier
D.Archive tier
AnswerD

Archive tier offers the lowest storage cost of any Blob Storage tier, ideal for data that is seldom accessed and due for long-term retention. It accepts retrieval latency of up to 15 hours and carries a minimum 180-day storage commitment, making it perfect for dormant customer transaction records that must be preserved for compliance. This is why it is the correct selection.

Why this answer

The Archive tier is the correct choice because it offers the lowest storage cost for data that is rarely accessed, which aligns with the scenario where data is accessed infrequently after 30 days but must be retained for 7 years. Azure Blob Storage's Archive tier is designed for long-term retention with a retrieval latency of several hours, making it cost-effective for compliance-driven data that does not require immediate access.

Exam trap

The trap here is that candidates may choose the Cool tier thinking it balances cost and access, but they overlook that the Archive tier is significantly cheaper for data that is accessed less than once a year, which is typical for 7-year compliance retention.

How to eliminate wrong answers

Option A is wrong because the Hot tier is optimized for frequent access and has the highest storage cost, which would be wasteful for data that is rarely accessed after 30 days. Option B is wrong because the Cool tier is designed for data accessed infrequently (e.g., every 30 days or more) but still has higher storage costs than Archive and is not the most cost-effective for 7-year retention with rare access. Option C is wrong because the Premium tier is for high-performance, low-latency access (e.g., via Azure Virtual Machines) and is the most expensive, making it unsuitable for rarely accessed compliance data.

218
MCQhard

A financial services company stores account balances in Azure SQL Database (strong consistency) and transaction audit logs in Azure Cosmos DB (eventual consistency by default). A compliance requirement demands that when a transaction is rolled back in the SQL database, the corresponding audit log entries in Cosmos DB must also be removed within a short time frame. Which term best describes the difficulty of maintaining this constraint?

A.ACID compliance
B.Idempotency
C.Distributed transaction coordination
D.Schema flexibility
AnswerC

A financial transfer that debits one account and credits another touches two independent storage systems. Distributed transaction coordination—via a two-phase commit or a saga pattern with compensating actions—ensures atomicity across those stores, so a failure in one step does not leave a partial, inconsistent state. Without such coordination, one side could commit while the other fails, causing account balances to diverge and require manual reconciliation.

Why this answer

The scenario requires coordinating a rollback across two distinct data stores—Azure SQL Database (ACID-compliant, strong consistency) and Azure Cosmos DB (eventual consistency by default). This cross-system transactional consistency is a classic distributed transaction coordination problem, often addressed via patterns like the two-phase commit (2PC) or the saga pattern, but not natively supported between these two services without custom orchestration.

Exam trap

The trap here is that candidates confuse ACID compliance (which is a property of a single database) with the ability to maintain atomicity across multiple independent data stores, leading them to select Option A instead of recognizing the need for distributed transaction coordination.

Why the other options are wrong

A

ACID compliance applies to a single database system (like Azure SQL) ensuring atomicity, consistency, isolation, durability. The question involves coordinating two different databases (SQL and Cosmos DB) with different consistency models, which is beyond ACID's scope.

B

Idempotency ensures that repeated operations produce the same result, but the difficulty here is coordinating atomic rollback across two different databases (SQL and Cosmos DB), not ensuring idempotent retries.

D

Schema flexibility refers to the ability to store data without a fixed schema, which is irrelevant to the challenge of ensuring atomicity across two different databases (Azure SQL and Cosmos DB) with different consistency models.

219
MCQeasy

A retail company stores customer data in a relational database table with columns for CustomerID, Name, and Email. Product reviews are stored as JSON documents where each document contains review text and a rating. Product images are stored as binary files in Azure Blob Storage. Which of the following correctly categorizes these data types in order: relational table, JSON documents, binary images?

A.Structured, semi-structured, unstructured
B.Semi-structured, structured, unstructured
C.Unstructured, semi-structured, structured
D.Structured, unstructured, semi-structured
AnswerA

Relational database tables are structured because they enforce a fixed schema with defined columns and data types, allowing straightforward SQL queries. JSON is semi-structured since it uses self-describing key-value pairs that can vary from record to record, lacking a rigid schema. Binary image files are unstructured as they contain raw pixel data with no inherent organization or queryable structure, completing the correct classification.

Why this answer

A is correct because relational tables enforce a fixed schema (columns with defined data types), making them structured data. JSON documents have a flexible schema (key-value pairs) but still contain metadata, classifying them as semi-structured. Binary image files in Azure Blob Storage have no inherent structure or schema, making them unstructured data.

This matches the order: structured, semi-structured, unstructured.

Exam trap

The trap here is that candidates often confuse semi-structured data (like JSON) with unstructured data because JSON appears 'flexible,' but it still has a defined key-value structure, whereas truly unstructured data (binary blobs) has no schema at all.

Why the other options are wrong

B

The relational table (structured) is mislabeled as semi-structured, and the JSON documents (semi-structured) are mislabeled as structured, reversing the correct order.

C

Option C orders the data types as unstructured, semi-structured, structured, but the question asks for the order: relational table (structured), JSON documents (semi-structured), binary images (unstructured). This mismatches the correct sequence.

D

The question orders data types as relational table, JSON documents, binary images. Option D (structured, unstructured, semi-structured) incorrectly classifies JSON documents as unstructured and binary images as semi-structured. In reality, JSON is semi-structured and binary images are unstructured.

220
Multi-Selectmedium

Which TWO of the following are characteristics of structured data? (Choose two.)

Select 2 answers
A.No predefined schema
B.Stored in rows and columns
C.Fixed schema
D.Key-value pairs
E.Schema-on-read
AnswersB, C

Structured data is inherently organised with a predefined schema, which mandates its storage in a highly organised format. This characteristic directly aligns with being stored in rows and columns, a hallmark of relational databases. Each row represents a unique record, while columns define specific attributes or fields, ensuring data consistency and enabling efficient querying and analysis. This precise tabular structure is a defining feature of structured data, satisfying the requirement for its organised nature.

Why this answer

Structured data is organized in a tabular format with rows and columns, which is the defining characteristic of relational databases like SQL Server or Azure SQL Database. This structure enforces a fixed schema, meaning the data types and relationships are defined before data is entered, ensuring consistency and enabling efficient querying via SQL.

Exam trap

Microsoft often tests the distinction between 'fixed schema' (structured) and 'schema-on-read' (semi-structured), and candidates mistakenly associate key-value pairs with structured data instead of NoSQL.

221
MCQhard

Your company stores sensitive customer data in Azure SQL Database. You need to implement column-level encryption for the 'SSN' column using a customer-managed key stored in Azure Key Vault. Which feature should you use?

A.Azure Policy
B.Always Encrypted
C.Transparent Data Encryption (TDE)
D.Dynamic Data Masking
AnswerB

Always Encrypted encrypts selected columns client-side using a column encryption key protected by a column master key held outside Azure SQL Database. The database engine stores and processes only ciphertext, so sensitive data is never exposed to SQL Server administrators or to Azure personnel. With deterministic encryption the server can support equality operations (e.g., WHERE clauses and joins) while randomized encryption avoids leaks. The client application and driver must be compatible, and the application must supply the keys.

Why this answer

Always Encrypted is the correct feature because it allows client-side encryption of sensitive columns, such as 'SSN', using a customer-managed key stored in Azure Key Vault. The encryption keys are never exposed to the database engine, ensuring that even database administrators cannot view the plaintext data. This meets the requirement for column-level encryption with customer-managed keys.

Exam trap

The trap here is that candidates often confuse Transparent Data Encryption (TDE) with column-level encryption, but TDE only protects data at rest and does not prevent database administrators or the cloud provider from reading the data in memory or during queries.

How to eliminate wrong answers

Option A is wrong because Azure Policy is a governance tool used to enforce organizational standards and compliance rules across Azure resources, not a data encryption feature for individual columns. Option C is wrong because Transparent Data Encryption (TDE) encrypts the entire database at rest (the storage layer), not at the column level, and it does not support customer-managed keys for column-specific encryption. Option D is wrong because Dynamic Data Masking obfuscates data at query time for unauthorized users but does not encrypt the underlying data; the masked values are still stored in plaintext and can be accessed by privileged users.

222
MCQeasy

Refer to the exhibit. The JSON shows a configuration for which Azure service?

A.Azure Analysis Services
B.Azure Data Factory
C.Power BI
D.Azure Synapse Analytics
AnswerB

Azure Data Factory is correct because it represents linked services, datasets, and pipelines as JSON objects. The exhibit shows a linked service definition with a type and typeProperties containing connection details, which is the standard way ADF stores source and destination connection information. This serialized JSON enables version-controlled, repeatable deployment of data integration artifacts.

Why this answer

The JSON snippet defines a pipeline with a copy activity that moves data from a source (Azure Blob Storage) to a sink (Azure SQL Database). This is the core pattern of Azure Data Factory (ADF), which orchestrates and automates data movement and transformation. The structure with 'name', 'properties', 'activities', 'typeProperties', 'source', and 'sink' is specific to ADF pipeline definitions.

Exam trap

The trap here is that candidates confuse the JSON pipeline definition with Azure Synapse Analytics pipelines, which share the same underlying engine but are accessed via a different portal and have additional Synapse-specific features like Spark job definitions and SQL script activities.

How to eliminate wrong answers

Option A is wrong because Azure Analysis Services is a semantic model and analytics engine (using Tabular or Multidimensional models), not a data orchestration service; it does not use JSON pipeline definitions with copy activities. Option C is wrong because Power BI is a visualization and reporting tool that uses datasets and dashboards, not JSON-based pipeline definitions with source/sink configurations. Option D is wrong because Azure Synapse Analytics is a unified analytics platform that includes dedicated SQL pools, serverless SQL, and Spark, but its native pipeline definitions (Synapse Pipelines) are derived from ADF; the exhibit shows a generic ADF pipeline JSON, not a Synapse-specific artifact like a SQL script or Spark job.

223
MCQeasy

A data engineer needs to process streaming data from IoT devices in near real-time and store the results in Azure Cosmos DB. Which Azure service should they use for the stream processing?

A.Azure Synapse Analytics
B.Azure Databricks
C.Azure Stream Analytics
D.Azure Data Factory
AnswerC

Azure Stream Analytics is a fully managed, purpose-built stream-processing service that handles near real-time IoT telemetry with low latency. It provides a SQL-like query language that natively supports temporal windows, sliding windows, and event-time processing, allowing filters, aggregations, and even anomaly detection directly on the stream. Crucially, it has a native Cosmos DB sink and built-in connectors to Event Hubs, IoT Hub, and other Azure services, eliminating the need for custom glue code. Because it processes each event as it arrives rather than in micro-batches, it is the ideal choice for real-time IoT scenarios that require prompt alerts or continuous output.

Why this answer

Azure Stream Analytics is the correct choice because it is a fully managed, real-time stream processing engine designed specifically for low-latency, near-real-time analytics on streaming data. It can ingest data from IoT devices via Event Hubs or IoT Hub, apply SQL-based transformations, and directly output the results to Azure Cosmos DB with millisecond latency, making it ideal for this scenario.

Exam trap

The trap here is that candidates often confuse Azure Stream Analytics with Azure Data Factory or Azure Databricks, mistakenly thinking that any 'data processing' tool can handle real-time streaming, but only Stream Analytics is purpose-built for near-real-time, serverless stream processing with direct Cosmos DB integration.

How to eliminate wrong answers

Option A is wrong because Azure Synapse Analytics is a unified analytics platform focused on large-scale batch processing and data warehousing, not real-time stream processing; it lacks native support for continuous streaming queries with sub-second latency. Option B is wrong because Azure Databricks is a big data and machine learning platform that can process streaming data via Structured Streaming, but it requires cluster management and is overkill for simple near-real-time IoT processing; it is not the simplest or most cost-effective choice for direct Cosmos DB output. Option D is wrong because Azure Data Factory is a cloud-based ETL and data integration service designed for batch-oriented data movement and orchestration, not for real-time stream processing; it cannot handle continuous, low-latency streaming workloads.

224
MCQeasy

A company receives data from a point-of-sale system. Each row contains TransactionID, ProductID, Quantity, and Price. The data has a fixed schema and is stored in a table. How should this data be classified?

A.Structured data
B.Semi-structured data
C.Unstructured data
D.Transactional data
AnswerA

Structured data has a fixed, predefined schema: every row in this POS dataset contains the same columns (TransactionID, ProductID, Quantity, Price) with consistent data types, allowing direct querying with SQL. This tabular format—organized into rows and columns with strict formatting—is the defining characteristic of structured data. Because the schema is known ahead of time and every record conforms to it, this dataset clearly fits the structured data classification.

Why this answer

The data has a fixed schema with clearly defined columns (TransactionID, ProductID, Quantity, Price) and each row follows the same structure, which is the definition of structured data. In Azure, this would map directly to a table in Azure SQL Database or a fixed-schema table in Azure Synapse Analytics. The rigid schema and consistent data types make it ideal for relational storage and querying.

Exam trap

The trap here is that candidates confuse 'transactional data' (a workload pattern) with 'structured data' (a data classification), leading them to pick Option D because the data comes from a point-of-sale system, but the question explicitly asks about data structure, not data source or usage.

How to eliminate wrong answers

Option B is wrong because semi-structured data (e.g., JSON, XML, Parquet) does not enforce a fixed schema; fields can vary between rows, unlike this rigid table. Option C is wrong because unstructured data (e.g., images, videos, text files) has no predefined schema or organization, whereas this data has a strict columnar structure. Option D is wrong because 'transactional data' describes a workload type (OLTP) or data generated by transactions, not a classification of data structure; the question asks how the data should be classified by structure, not by its source or usage.

225
MCQeasy

A retail company stores customer data in three formats: a relational database table with fixed columns for CustomerID, Name, and Email; customer feedback as JSON documents with varying fields such as rating and comment; and product images as JPEG files. Which of the following correctly classifies these data types from most structured to least structured?

A.JSON documents, relational table, image files
B.Relational table, JSON documents, image files
C.Image files, JSON documents, relational table
D.Relational table, image files, JSON documents
AnswerB

Correct. Relational tables have a fixed schema (structured), JSON documents allow varying fields (semi-structured), and image files lack a predefined schema (unstructured).

Why this answer

Relational tables enforce a fixed schema with defined columns and data types, making them the most structured. JSON documents are semi-structured, allowing varying fields and flexible schemas, while image files are unstructured binary data with no inherent schema. This ordering from most to least structured aligns with the core data classification concept in the DP-900 exam.

Exam trap

The trap here is that candidates often confuse semi-structured JSON with unstructured data, or assume that any file format (like images) has inherent structure, leading them to misorder the classification from most to least structured.

Why the other options are wrong

A

JSON documents are semi-structured (varying fields), not more structured than a relational table with fixed columns. The order from most to least structured should be relational table (structured), JSON (semi-structured), image files (unstructured).

C

Image files are unstructured data, not more structured than JSON documents. The correct order from most to least structured is relational table (highly structured), JSON documents (semi-structured), image files (unstructured).

D

Image files are unstructured data, not semi-structured like JSON. The order should be relational table (structured), JSON documents (semi-structured), image files (unstructured).

← PreviousPage 3 of 4 · 235 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Core Data Concepts questions.