Courseiva

CCNA Dap Data Concepts Questions

75 of 200 questions · Page 1/3 · Dap Data Concepts topic · Answers revealed

Practice these questionsExam hubAll questions
1
MCQeasy

A healthcare provider needs to integrate patient data from multiple clinics into a single data warehouse. Which process is used to extract, transform, and load the data?

A.ELT
B.ETL
C.OLAP
D.OLTP
AnswerB

ETL extracts data from the separate clinic sources, transforms it into a consistent format, and loads it into the central warehouse. This three-stage pipeline directly satisfies the integration requirement, unlike ELT, which loads raw data before transforming.

Why this answer

ETL (Extract, Transform, Load) is the correct process because the healthcare provider must first extract data from multiple source clinics, then transform it (e.g., standardize formats, clean duplicates, apply business rules) before loading it into the target data warehouse. This ensures data quality and consistency, which is critical for clinical analytics and reporting.

Exam trap

The trap here is confusing ETL with ELT, where candidates assume ELT is always better due to modern big data tools, but the question explicitly describes a traditional data warehouse integration requiring pre-load transformations.

How to eliminate wrong answers

Option A is wrong because ELT (Extract, Load, Transform) loads raw data into the target system first and transforms it later, which is less suitable for a data warehouse requiring pre-integrated, clean data from multiple sources; it is more common in big data environments like Hadoop. Option C is wrong because OLAP (Online Analytical Processing) is a category of database systems optimized for complex queries and multidimensional analysis, not a data integration process. Option D is wrong because OLTP (Online Transaction Processing) is designed for high-volume transactional operations (e.g., recording patient visits), not for extracting, transforming, and loading data into a warehouse.

Practice this question →
2
MCQhard

A financial services company is implementing a data governance program. The chief data officer wants to ensure that data is classified according to its sensitivity and that access is restricted accordingly. The company must comply with GDPR and internal policies. Which data governance component is primarily responsible for defining and enforcing data classification and access controls?

A.Data security and access management
B.Data quality management
C.Data stewardship
D.Master data management
AnswerA

Data security and access management encompasses the policies, processes, and technologies that classify data based on sensitivity and enforce access controls. It directly addresses the requirement to restrict access according to classification and comply with regulations like GDPR. This component includes authentication, authorization, and encryption.

Why this answer

Data security and access management is the governance component that defines data classification and enforces access controls. It ensures that sensitive data is protected according to regulations like GDPR. Data stewardship, data quality management, and master data management address different aspects of governance and do not primarily handle classification and access enforcement.

Exam trap

The trap here is confusing data stewardship, which assigns accountability, with data security, which enforces access controls.

Practice this question →
3
MCQmedium

A retail company wants to analyze customer purchase patterns over time. The data is stored in a relational database with tables for Customers, Orders, and Products. Which database concept should be used to ensure that each order references a valid customer?

A.View
B.Index
C.Primary key
D.Foreign key
AnswerD

A foreign key constrains the Orders table's customer reference to values existing in the Customers primary key, enforcing referential integrity so no order can point at an invalid customer. This directly prevents orphaned order records.

Why this answer

A foreign key constraint enforces referential integrity by ensuring that every value in the 'customer_id' column of the Orders table matches a valid primary key value in the Customers table. This prevents orphaned records and guarantees that each order references an existing customer.

Exam trap

CompTIA often tests the distinction between a primary key (which enforces uniqueness within a table) and a foreign key (which enforces relationships between tables), leading candidates to mistakenly choose primary key when the question asks about cross-table validation.

How to eliminate wrong answers

Option A is wrong because a view is a virtual table based on a query and does not enforce any constraints between tables. Option B is wrong because an index speeds up data retrieval but does not enforce referential integrity or validate relationships. Option C is wrong because a primary key uniquely identifies rows within its own table and cannot enforce relationships between different tables.

Practice this question →
4
Multi-Selectmedium

Which TWO of the following are benefits of database normalization to 3NF? (Select 2)

Select 2 answers
A.Improves query performance for all queries
B.Reduces data redundancy
C.Simplifies complex joins
D.Eliminates all data anomalies
E.Increases data integrity
AnswersB, E

Third normal form eliminates repeating groups and transitive dependencies, so each fact is stored once in its owning table. This satisfies the redundancy benefit by removing duplicate copies that would otherwise need synchronising across the schema.

Why this answer

Normalization to 3NF eliminates transitive dependencies, which directly reduces data redundancy by ensuring each non-key attribute depends only on the primary key. This reduction in redundancy also increases data integrity because updates, inserts, and deletes are less likely to create inconsistencies or anomalies. In a relational database, 3NF achieves this without sacrificing the ability to reconstruct the original data via joins.

Exam trap

The trap here is that candidates confuse normalization with denormalization, assuming that reducing redundancy always improves query performance, when in fact normalization often increases join complexity and can slow down read queries.

Practice this question →
5
MCQhard

A data analyst needs to combine customer data from two tables: Customers (CustomerID, Name) and Orders (OrderID, CustomerID, Amount). Only customers who have placed at least one order should be included. Which JOIN type should be used?

A.INNER JOIN
B.LEFT JOIN
C.FULL OUTER JOIN
D.RIGHT JOIN
AnswerA

An INNER JOIN returns only rows where CustomerID matches in both tables, excluding customers with no orders. This directly satisfies the requirement that only customers who have placed at least one order appear in the result, while unmatched customer rows are discarded.

Why this answer

An INNER JOIN returns only rows where there is a match in both tables. Since the requirement is to include only customers who have placed at least one order, the INNER JOIN on CustomerID will filter out any customer without a matching order record, exactly meeting the condition.

Exam trap

The trap here is that candidates often choose LEFT JOIN thinking it 'includes all customers' without realizing it also includes customers with no orders, which fails the explicit condition of 'only customers who have placed at least one order'.

How to eliminate wrong answers

Option B (LEFT JOIN) is wrong because it would include all customers, even those with no orders, with NULL values for order columns, which violates the 'only customers who have placed at least one order' requirement. Option C (FULL OUTER JOIN) is wrong because it would include customers without orders and orders without customers, both of which are not needed. Option D (RIGHT JOIN) is wrong because it would include all orders, potentially including orders with no matching customer, and still would not restrict customers to only those with orders.

Practice this question →
6
Multi-Selecteasy

A data analyst is working with a dataset that includes customer names, email addresses, and purchase history. The analyst wants to ensure that each customer is uniquely identified. Which TWO database concepts should be used to enforce uniqueness and link related data?

Select 2 answers
A.Foreign key
B.Normalization
C.View
D.Primary key
E.Index
AnswersA, D

A foreign key links related data by referencing the primary key of another table, enforcing referential integrity between customer records and their purchase history. Combined with a primary key, which uniquely identifies each customer, it satisfies the stem's requirement to enforce uniqueness and link related data.

Why this answer

A primary key uniquely identifies each row in a table, ensuring no duplicate customer records. A foreign key links related data across tables by referencing the primary key of another table, enforcing referential integrity. Together, they guarantee uniqueness and enable relational joins between customer and purchase history tables.

Exam trap

The trap here is that candidates often confuse normalization with a constraint or think an index enforces uniqueness, when only primary and foreign keys provide the required referential integrity and unique identification.

Practice this question →
7
Matchingmedium

Match each data quality dimension to its description.

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

Concepts
Matches

Degree to which data correctly reflects real-world values

Extent to which all required data is present

Absence of contradictions across data sources

Data is up-to-date and available when needed

No duplicate records exist within the dataset

Why these pairings

The correct matches are: Accuracy - data correctly reflects real-world values; Completeness - all required data is present; Consistency - data values are the same across systems; Timeliness - data is available when needed. Common confusions include mixing timeliness with accuracy and consistency with completeness.

Practice this question →
8
MCQhard

A data analyst notices that a column labeled 'Income' contains values like '$50,000' and '$75,000', but also 'High' and 'Low'. What data concept issue is occurring?

A.Mixing quantitative and qualitative data
B.Mixing discrete and continuous data
C.Mixing nominal and ordinal data
D.Mixing structured and unstructured data
AnswerA

The Income column holds numeric currency amounts alongside categorical labels such as High and Low, so a single field contains both quantitative and qualitative values. This mixed-type inconsistency prevents valid aggregation or statistical analysis of that column.

Why this answer

The 'Income' column contains both numeric values (e.g., '$50,000', '$75,000') which are quantitative data, and categorical labels ('High', 'Low') which are qualitative data. Mixing these two distinct data types in a single column violates data consistency principles and prevents proper statistical analysis or machine learning processing. This is a classic example of mixing quantitative and qualitative data.

Exam trap

CompTIA often tests the distinction between data type categories (quantitative vs. qualitative) versus subtypes (discrete/continuous or nominal/ordinal), so candidates mistakenly pick a subtype option when the core issue is the fundamental type mismatch.

How to eliminate wrong answers

Option B is wrong because discrete and continuous data are both subtypes of quantitative data (e.g., number of children vs. height), but the issue here is mixing numbers with text labels, not distinguishing between countable and measurable values. Option C is wrong because nominal and ordinal data are both categorical (qualitative) subtypes (e.g., colors vs. rankings), but the column includes actual numeric income values, not just ordered categories. Option D is wrong because structured data refers to organized formats like tables (which this column is part of), while unstructured data refers to free-form text or media; the problem is not about format but about inconsistent data types within a structured field.

Practice this question →
9
MCQhard

A company needs to store user session data for a web application. Each session has a unique session ID, and the data must be retrieved very quickly by session ID. The data does not require complex relationships or transactions. Which type of NoSQL database is most appropriate?

A.Key-value store (e.g., Redis)
B.Wide-column store (e.g., Cassandra)
C.Document store (e.g., MongoDB)
D.Graph database (e.g., Neo4j)
AnswerA

A key-value store maps each session ID directly to its session data, giving the fastest possible lookup by key. It satisfies the stem's requirement for quick retrieval by session ID without complex relationships or transactions.

Why this answer

A key-value store like Redis is the most appropriate choice because it is optimized for extremely fast lookups by a unique key (session ID) and does not require complex relationships or transactions. Redis stores data in memory, providing sub-millisecond retrieval times ideal for session management, and supports built-in expiration (TTL) to automatically clean up stale sessions.

Exam trap

The trap here is that candidates often choose a document store like MongoDB because they associate 'session data' with JSON objects, overlooking that key-value stores are purpose-built for the exact use case of fast, simple key-based retrieval without the overhead of document querying.

How to eliminate wrong answers

Option B (Wide-column store, e.g., Cassandra) is wrong because it is designed for high-volume, distributed writes and complex query patterns over column families, not for simple, low-latency key-based lookups; its eventual consistency model and overhead for single-key reads make it overkill for session storage. Option C (Document store, e.g., MongoDB) is wrong because it stores semi-structured JSON-like documents with rich querying capabilities, which adds unnecessary complexity and latency for simple session data that only needs key-based retrieval. Option D (Graph database, e.g., Neo4j) is wrong because it is purpose-built for traversing relationships between entities (nodes and edges), which is irrelevant for session data that has no relational structure.

Practice this question →
10
MCQeasy

A marketing team needs to store customer feedback from social media posts, including text, images, and emojis. Which data concept is most appropriate for this storage?

A.Unstructured data in a NoSQL document database
B.Structured data in a relational database
C.Unstructured data in a relational database
D.Semi-structured data in an XML database
AnswerA

NoSQL document databases store each post as a self-describing document, holding text, image references and emoji characters together without a fixed relational schema. This satisfies the requirement to capture mixed-format social media feedback, which varies in structure between posts.

Why this answer

Customer feedback from social media includes text, images, and emojis, which lack a predefined schema and are best stored as unstructured data. NoSQL document databases (e.g., MongoDB) store such data in flexible JSON-like documents, allowing each record to have varying fields and data types without requiring a fixed schema.

Exam trap

CompTIA often tests the misconception that 'unstructured data' cannot be stored in any database, when in fact NoSQL document databases are purpose-built for it, while relational databases require rigid schemas that fail with variable content.

How to eliminate wrong answers

Option B is wrong because structured data in a relational database requires a fixed schema with predefined columns and data types, which cannot efficiently handle variable-length text, images, and emojis without complex workarounds like BLOBs. Option C is wrong because relational databases are designed for structured data; storing unstructured data in them forces schema rigidity and poor performance for heterogeneous content. Option D is wrong because XML databases are semi-structured and impose hierarchical markup, which is unnecessary overhead for social media posts that are naturally schema-less and better served by document stores.

Practice this question →
11
Multi-Selecthard

A data architect is evaluating storage engines for a new analytics platform. The platform must support storing large volumes of structured historical sales data and must efficiently handle queries that aggregate a few columns across billions of rows. The architect is considering column-oriented storage. Which two characteristics accurately describe column-oriented storage in this context? (Choose two.)

Select 2 answers
A.It requires reading all columns of a row even when only one column is needed for a query
B.It typically achieves better data compression than row-oriented storage for repetitive column values
C.It is optimized for high-frequency single-row inserts and updates typical of transactional workloads
D.It eliminates the need for indexing because every column is stored in sorted order automatically
E.It stores each column's values contiguously, improving compression and scan efficiency for analytical aggregates
AnswersB, E

Because values within a column share the same data type and often repeat or fall within narrow ranges, column-oriented storage can apply dictionary, run-length, and delta encoding effectively. This yields higher compression than row-oriented formats, where heterogeneous row values limit encoding options. Reduced storage and I/O directly benefit large-scale analytical scans.

Why this answer

Column-oriented storage groups values by column, which enables efficient compression and allows queries to read only the columns they need. These two properties directly support aggregating a few columns across billions of rows. The remaining statements describe row-oriented behavior, overstate write performance, or misrepresent indexing requirements, so they do not accurately characterize column-oriented storage for this analytics platform.

Exam trap

The trap here is assuming that column-oriented storage improves all workloads equally, when its advantages apply to analytical scans and compression while row-oriented engines remain superior for frequent single-row writes.

Practice this question →
12
Multi-Selecthard

A data engineer is designing a data pipeline for a retail company. The source system is an OLTP database that records sales transactions. The target is a data warehouse used for reporting. The engineer is evaluating whether to use ETL or ELT. Which three factors would favor using ELT over ETL? (Select THREE)

Select 3 answers
A.The transformation logic requires proprietary functions not available in the warehouse
B.The business analysts need access to raw data for ad-hoc exploration
C.The target data warehouse has massive compute power (e.g., Snowflake) that can handle transformations efficiently
D.Data must be cleansed and validated before loading into the warehouse
E.The source data volume is very large and the warehouse can scale resources on demand
AnswersB, C, E

ELT loads raw data, allowing analysts to explore it before transformation.

Why this answer

ELT loads raw data into the warehouse first, allowing business analysts to perform ad-hoc exploration directly on the source data without pre-transformation. This flexibility is a key advantage of ELT over ETL, where transformations are applied before loading.

Exam trap

The trap here is that candidates often confuse the direction of data flow, mistakenly thinking that ELT requires transformations before loading, when in fact ELT defers transformations until after data is in the warehouse.

Practice this question →
13
MCQhard

A company uses a NoSQL document database to store product catalogs. Each product document includes fields like product_id, name, category, and price. The operations team frequently queries by product_id and by category. Which type of NoSQL database is being used, and what should be created to optimize queries by category?

A.Key-value store; create a secondary index on category
B.Graph database; create a relationship between products
C.Document database; create an index on category
D.Wide-column store; create a column family for category
AnswerC

A document database stores each product as a self-describing JSON-like document, matching the schema described. Indexing the category field builds a secondary lookup structure, so queries filtering by category avoid full collection scans and return results efficiently.

Why this answer

The question explicitly states a document database is used, and the operations team frequently queries by category. In a document database like MongoDB, creating an index on the category field optimizes these queries by allowing the database to quickly locate documents without scanning every document in the collection. This is the standard approach for improving query performance on non-primary-key fields in document stores.

Exam trap

CompTIA Data+ may test the misconception that all NoSQL databases support secondary indexes similarly. The trap here is that document databases natively support secondary indexes, while key-value and wide-column stores require different optimization strategies.

How to eliminate wrong answers

Option A is wrong because a key-value store does not support secondary indexes on fields like category; it only allows lookups by the primary key (product_id), making it unsuitable for the described query pattern. Option B is wrong because a graph database is designed for relationship-heavy data (e.g., social networks), not for product catalogs with simple field queries, and creating relationships between products does not optimize category-based lookups. Option D is wrong because a wide-column store organizes data by column families, not by documents, and creating a column family for category would not provide the index-based optimization needed for document-style queries.

Practice this question →
14
MCQeasy

A data analyst is working with a dataset that contains a column for customer satisfaction ratings on a scale of 1 to 5, where 1 means 'very dissatisfied' and 5 means 'very satisfied'. The analyst wants to calculate the median satisfaction score. Which level of measurement does this data represent?

A.Ratio
B.Ordinal
C.Nominal
D.Interval
AnswerB

Ordinal data has a meaningful order but the intervals between values are not necessarily equal. Satisfaction ratings from 1 to 5 are ordered, but the difference between 1 and 2 may not equal the difference between 4 and 5. The median is a valid measure of central tendency for ordinal data, making this the correct classification.

Why this answer

Customer satisfaction ratings on a 1-5 scale are ordered but the intervals between points are not equal, so they are ordinal. The median is the appropriate measure of central tendency for ordinal data. Nominal data lacks order, interval data requires equal intervals, and ratio data requires a true zero, none of which apply here.

Exam trap

The trap here is assuming that numeric labels always indicate interval or ratio data, when in fact ordered categories like satisfaction ratings are ordinal.

Practice this question →
15
MCQmedium

To consolidate data from multiple operational databases into a central repository for reporting, a company decides to transform data before loading it into the target system. Which data integration approach is being used?

A.ETL (Extract, Transform, Load)
B.Data virtualization
C.Change data capture
D.ELT (Extract, Load, Transform)
AnswerA

ETL transforms data in a staging area before writing to the target, so the central repository receives cleansed, conformed records. This matches the stem's constraint that data is transformed before loading, unlike ELT, which loads raw data first.

Why this answer

The scenario describes transforming data before loading it into the target system, which is the defining characteristic of ETL (Extract, Transform, Load). In ETL, data is extracted from source systems, transformed in a staging area (e.g., cleaning, aggregating, joining), and then loaded into the central repository. This approach is commonly used when the target system (e.g., a data warehouse) requires pre-processed, high-quality data for reporting.

Exam trap

The trap here is that candidates often confuse ETL with ELT, assuming that any transformation before loading is ELT, but the key distinction is that ELT loads raw data first and transforms it later inside the target system, whereas ETL transforms data before it reaches the target.

How to eliminate wrong answers

Option B (Data virtualization) is wrong because it does not physically move or transform data before loading; instead, it creates a virtual layer that queries source systems in real-time, leaving data in place. Option C (Change data capture) is wrong because it is a technique for identifying and capturing only changed data from source systems, not a complete integration approach that includes transformation before loading. Option D (ELT) is wrong because it loads raw data into the target system first and then transforms it within the target, which contradicts the 'transform before loading' requirement in the question.

Practice this question →
16
Multi-Selecthard

Which THREE of the following are NoSQL database types?

Select 3 answers
A.Document
B.Hierarchical
C.Relational
D.Key-Value
E.Graph
AnswersA, D, E

Document stores (e.g., MongoDB) are NoSQL.

Why this answer

Document databases, such as MongoDB, store data in flexible, JSON-like documents (BSON in MongoDB's case). This allows for nested structures and schema-less designs, making them a core NoSQL category distinct from relational models.

Exam trap

CompTIA often tests the distinction between legacy database models (hierarchical) and modern NoSQL categories, leading candidates to mistakenly include hierarchical as a NoSQL type due to its non-relational nature.

Practice this question →
17
MCQeasy

A retail analyst needs to determine the most popular product category. The dataset includes columns: ProductID, Category, SalesDate, QuantitySold, UnitPrice. Which column contains qualitative data?

A.SalesDate
B.QuantitySold
C.UnitPrice
D.Category
AnswerD

Category holds qualitative data because it labels products into named groups rather than measuring amounts. ProductID, SalesDate, QuantitySold and UnitPrice are all quantitative or temporal, so they cannot satisfy the stem's requirement for a qualitative column. Category's non-numeric, descriptive values are precisely what the analyst needs to group and rank popularity.

Why this answer

Qualitative data (also called categorical data) represents non-numeric categories or labels. The 'Category' column contains text values such as 'Electronics' or 'Clothing', which are descriptive and cannot be used in arithmetic operations. This makes it the only qualitative column in the dataset.

Exam trap

The trap here is that candidates often mistake dates (SalesDate) for qualitative data because they are not numeric, but dates are actually quantitative interval data with a meaningful order and equal intervals.

How to eliminate wrong answers

Option A is wrong because SalesDate represents a point in time, which is quantitative (interval) data, not qualitative. Option B is wrong because QuantitySold is a numeric count, making it quantitative (discrete) data. Option C is wrong because UnitPrice is a numeric monetary value, making it quantitative (continuous) data.

Practice this question →
18
MCQmedium

A data engineer is designing a system to store raw sensor data from thousands of IoT devices. The data is expected to be used for exploratory analytics and machine learning. Which storage solution is most appropriate?

A.Data lake
B.Relational database
C.Data mart
D.Key-value store
AnswerA

A data lake stores raw, schema-on-read data at scale without upfront transformation, suiting thousands of IoT devices and varied formats. Exploratory analytics and machine learning need that flexible, unmodelled raw data, which a data warehouse's structured schema would constrain.

Why this answer

A data lake is the most appropriate choice because it can store raw, unprocessed sensor data in its native format (e.g., JSON, Parquet, or binary) without requiring a predefined schema. This flexibility supports exploratory analytics and machine learning workflows where data schemas may evolve or be unknown at ingestion time. Data lakes also scale horizontally to handle the high volume and velocity of data from thousands of IoT devices, unlike traditional storage systems that impose rigid structures or size limits.

Exam trap

The trap here is that candidates often confuse a data lake with a data warehouse or relational database, assuming raw data must be structured immediately, when in fact a data lake's schema-on-read approach is specifically designed for exploratory and machine learning use cases.

How to eliminate wrong answers

Option B is wrong because a relational database enforces a fixed schema and ACID transactions, which are unnecessary for raw sensor data and would introduce significant overhead for high-velocity, schema-on-read workloads. Option C is wrong because a data mart is a subset of data optimized for a specific business function or department, not designed to store raw, exploratory data from thousands of IoT devices. Option D is wrong because a key-value store is optimized for simple lookups by a single key and lacks the query flexibility and analytical capabilities needed for exploratory analytics and machine learning on complex sensor data.

Practice this question →
19
MCQeasy

A data architect is designing a schema for a product catalog where each product has a variable number of attributes. Which NoSQL database type is most appropriate?

A.Graph database
B.Document store
C.Key-value store
D.Relational database
AnswerB

Document stores hold each product as a self-describing JSON-like document, so attributes can vary per item without a fixed schema. This directly satisfies the stem's variable-attribute constraint, unlike columnar or key-value models that require predefined structures. Nested attributes and arrays are queried natively, matching heterogeneous catalog entries.

Why this answer

A document store (e.g., MongoDB, Couchbase) is the most appropriate choice because it stores data in flexible, self-describing documents (typically JSON or BSON), allowing each product to have a variable number of attributes without requiring a predefined schema. This directly matches the requirement of a product catalog where attributes can differ per product, unlike rigid relational tables that would require complex EAV (Entity-Attribute-Value) patterns or frequent schema migrations.

Exam trap

The trap here is that candidates often confuse 'variable attributes' with 'relationships' and incorrectly choose a graph database, or they assume key-value stores are flexible enough, overlooking the need for queryability on individual attributes.

How to eliminate wrong answers

Option A is wrong because graph databases (e.g., Neo4j) are optimized for highly connected data and relationship traversal, not for storing documents with variable attributes; they would force you to model each attribute as a node or relationship, adding unnecessary complexity. Option C is wrong because key-value stores (e.g., Redis, DynamoDB) treat the entire product as an opaque value, making it impossible to query or index individual attributes without application-level parsing, which defeats the purpose of a catalog. Option D is wrong because relational databases require a fixed schema per table; handling variable attributes would necessitate either many nullable columns, frequent ALTER TABLE statements, or a cumbersome EAV pattern, all of which degrade performance and maintainability.

Practice this question →
20
MCQmedium

A data analyst is examining a dataset of customer transactions. The analyst notices that the 'TransactionAmount' column contains values like 100.50, 200.75, and 50.00. The analyst wants to determine the average transaction amount. Which type of data is 'TransactionAmount'?

A.Interval
B.Ratio
C.Nominal
D.Ordinal
AnswerB

Ratio data has all the properties of interval data plus a true zero, allowing for meaningful ratios and arithmetic operations. TransactionAmount has a true zero (no transaction) and equal intervals, so it is ratio data. Averages, sums, and ratios are valid for ratio data.

Why this answer

TransactionAmount is ratio data because it has a true zero point and equal intervals between values. This allows for meaningful arithmetic operations such as calculating an average. Nominal data is categorical, ordinal data has unequal intervals, and interval data lacks a true zero, so none of those fit.

Exam trap

The trap here is confusing interval and ratio data by overlooking the presence of a true zero in monetary values.

Practice this question →
21
MCQhard

A database has a table 'Orders' with columns OrderID (PK), CustomerID, OrderDate, and a table 'OrderDetails' with OrderID (FK), ProductID, Quantity. To ensure that every OrderID in OrderDetails exists in Orders, which integrity constraint is enforced?

A.Entity integrity
B.Domain integrity
C.User-defined integrity
D.Referential integrity
AnswerD

Referential integrity guarantees that every foreign key value in OrderDetails matches an existing primary key in Orders, preventing orphaned detail rows. This directly enforces the stem's requirement that each OrderID in OrderDetails exists in the parent Orders table.

Why this answer

Referential integrity ensures that a foreign key value in a child table (OrderDetails.OrderID) must match an existing primary key value in the parent table (Orders.OrderID) or be NULL. This constraint prevents orphaned records and maintains consistent relationships between tables. Since OrderDetails.OrderID is defined as a foreign key referencing Orders, the database enforces referential integrity to guarantee every OrderID in OrderDetails exists in Orders.

Exam trap

The trap here is confusing the four integrity types—candidates often pick 'entity integrity' because it sounds like it relates to keys, but entity integrity is specifically about primary keys, not foreign keys.

How to eliminate wrong answers

Option A is wrong because entity integrity concerns primary keys—ensuring they are unique and not NULL—not foreign key relationships. Option B is wrong because domain integrity restricts column values to a defined domain (data type, range, format), not cross-table references. Option C is wrong because user-defined integrity covers business rules implemented via triggers or stored procedures, not the standard foreign key constraint described.

Practice this question →
22
MCQmedium

A company's database has a table 'orders' with columns: order_id, customer_id, order_date, and total_amount. A data analyst needs to identify customers who have placed more than 5 orders in the past year. Which data concept should be used to group orders by customer and count them?

A.Joining with other tables
B.Filtering with WHERE clause
C.Sorting with ORDER BY
D.Aggregation with GROUP BY
AnswerD

Aggregation with GROUP BY satisfies the requirement to group orders by customer_id and count them. GROUP BY collapses rows sharing a customer_id into single groups, then COUNT() tallies each customer's orders. Filtering with HAVING COUNT(*) > 5 after grouping identifies those exceeding five orders in the past year, which WHERE cannot do on aggregates.

Why this answer

The requirement to count orders per customer requires grouping rows by customer_id and then applying a count function. The GROUP BY clause in SQL aggregates rows that share a common value (customer_id) into summary rows, and the COUNT function tallies the number of orders per group. This is the standard approach for such 'per-customer' aggregations.

Exam trap

The trap here is that candidates confuse filtering (WHERE) with aggregation (GROUP BY), thinking that a WHERE clause alone can count orders per customer, when in fact WHERE only filters rows and cannot produce grouped counts.

How to eliminate wrong answers

Option A is wrong because joining with other tables merges columns from multiple tables but does not group or count rows; it would not produce a count of orders per customer. Option B is wrong because filtering with a WHERE clause restricts rows before any grouping but does not aggregate or count; it cannot produce a count of orders per customer. Option C is wrong because sorting with ORDER BY only arranges the result set order and has no effect on grouping or counting rows.

Practice this question →
23
MCQeasy

A marketing analyst is building a dashboard that groups customers by the state listed in their billing address so the sales team can compare performance across regions. The analyst retrieves the raw address data stored in a single text column. Which data type classification best describes the state field as the analyst intends to use it?

A.Ordinal
B.Ratio
C.Interval
D.Nominal
AnswerD

Nominal data labels categories with no inherent order, and U.S. states function purely as distinct group labels for comparing regional sales. Nothing about the state field implies a ranking, distance, or mathematical relationship between one state and another, so treating it as nominal is appropriate for grouping and counting customers in each region.

Why this answer

State names are categorical labels used to segment customers into groups, and there is no ranking or numeric distance between them. That makes the field nominal for this dashboard. Ordinal, interval, and ratio all require either an inherent order or numeric measurement properties that state labels do not have, so they cannot apply to this grouping task.

Exam trap

The trap here is assuming that because states are often sorted alphabetically or by sales totals, the field itself is ordinal rather than nominal.

Practice this question →
24
MCQmedium

A data analyst needs to retrieve current weather data from a third-party service. The service provides an endpoint that returns data in JSON format over HTTP. Which data source type is being used?

A.Streaming data
B.Flat file
C.Web scraping
D.API
AnswerD

An HTTP endpoint returning JSON is a REST API, which the analyst queries programmatically to retrieve current weather data. Unlike a flat file or database extract, the API delivers structured, on-demand responses, satisfying the requirement for live third-party weather retrieval.

Why this answer

The data analyst is retrieving data from a third-party service via an HTTP endpoint that returns JSON. This is the classic definition of an API (Application Programming Interface) — specifically a RESTful web API — which allows programmatic access to structured data over HTTP using standard methods like GET. The JSON format confirms it is an API response, not a file or stream.

Exam trap

The trap here is that candidates confuse 'web scraping' (Option C) with API consumption because both involve HTTP, but scraping parses unstructured HTML while an API returns structured JSON, and CompTIA often tests this distinction by describing a direct JSON endpoint to lure test-takers into selecting web scraping.

How to eliminate wrong answers

Option A is wrong because streaming data implies a continuous, real-time flow of data (e.g., from Kafka, WebSockets, or sensor feeds), whereas the question describes a single request-response retrieval over HTTP. Option B is wrong because a flat file (e.g., CSV, TSV, or fixed-width) is a static file stored locally or on a file server, not an HTTP endpoint that returns JSON dynamically. Option C is wrong because web scraping involves parsing raw HTML from a web page to extract data, not consuming a structured JSON response from a dedicated API endpoint.

Practice this question →
25
MCQmedium

A data analyst needs to extract data from a transactional database and load it into a data warehouse for reporting. Which process typically transforms the data before loading it into the warehouse?

A.Data virtualization
B.ELT
C.ETL
D.Data replication
AnswerC

ETL transforms data in a staging area before loading, satisfying the stem's requirement that transformation occur prior to warehouse load. Extract pulls from the transactional database, Transform cleanses and conforms it, then Load writes to the warehouse. ELT instead loads raw data first and transforms inside the warehouse, which contradicts the stated sequence.

Why this answer

ETL (Extract, Transform, Load) transforms data in a staging area before loading it into the target warehouse, which matches the question's requirement that transformation happens before loading. This is the classic pattern for data warehouses where the target schema is fixed and data quality must be enforced upstream. ELT, by contrast, loads raw data first and transforms it inside the warehouse using its compute engine.

Exam trap

The trap here is conflating ETL and ELT — candidates who skim the question miss the phrase 'transforms the data before loading' and pick ELT because it is the more modern pattern.

How to eliminate wrong answers

Option A is wrong because data virtualization presents a virtual query layer over source systems without physically moving or transforming data into a warehouse. Option B is wrong because ELT loads raw data into the warehouse first and performs transformations afterward using the warehouse's compute — the opposite order from what the question describes. Option D is wrong because data replication copies data between systems for availability or synchronization; it does not include a transformation stage before loading.

Practice this question →
26
MCQmedium

A company needs to store raw data from IoT sensors for future machine learning projects. The data is expected to be massive and in various formats. Which storage solution is most appropriate?

A.Data mart
B.Data warehouse
C.Data lake
D.Relational database
AnswerC

A data lake stores raw data in its native format, schema-on-read, so massive volumes of varied IoT sensor output can land without upfront transformation. This satisfies the stem's requirement for diverse formats retained for future machine learning, where structure is imposed only at analysis time.

Why this answer

A data lake stores raw data in its native format without predefined schema, ideal for large volumes of varied data for future use.

Practice this question →
27
MCQhard

A data analyst is working with a dataset that includes a column 'Annual Income' with values ranging from $20,000 to $500,000. The analyst wants to reduce the impact of extreme values on a machine learning model. Which technique should the analyst apply?

A.Log transformation
B.Z-score standardization
C.Winsorizing
D.Min-max normalization
AnswerC

Winsorizing replaces extreme values with a specified percentile, such as the 5th and 95th percentiles, effectively capping outliers. This reduces their impact on the model while retaining the data points. It is a robust technique for handling outliers in skewed data like income.

Why this answer

The correct answer is Winsorizing because it directly caps extreme values at a chosen percentile, reducing their influence on the model. Min-max normalization and z-score standardization do not mitigate outliers, and log transformation only reduces skewness without bounding values.

Exam trap

The trap here is thinking that any scaling method handles outliers; however, only techniques like Winsorizing explicitly limit extreme values.

Practice this question →
28
Multi-Selecthard

A data warehouse team is considering moving from an ETL to an ELT approach. Which THREE of the following are advantages of ELT over ETL?

Select 3 answers
A.Requires less storage space in the data warehouse
B.Reduces data loading time because transformations are done after loading
C.Allows data to be reprocessed easily if transformation logic changes
D.Ensures data is cleaned before loading
E.Eliminates the need for a separate ETL server
AnswersB, C, E

Data is loaded quickly without transformation, reducing initial load time.

Why this answer

In ELT, data is loaded into the data warehouse first and transformations are applied afterward. This reduces the initial loading time since no transformation processing occurs during the load phase, allowing raw data to be ingested more quickly.

Exam trap

CompTIA often tests the misconception that ELT reduces storage requirements, but in reality, ELT increases storage needs because raw data is persisted alongside transformed data, whereas ETL can discard raw data after transformation.

Practice this question →
29
MCQeasy

A data analyst at a logistics company is designing a new database table to store shipment records. Each shipment has a unique tracking number, a weight in kilograms, a destination city, and a delivery date. The analyst needs to choose a data type for the tracking number that ensures uniqueness and efficient lookups. Which data type is most appropriate for the tracking number?

A.Boolean
B.Integer
C.Date/time
D.Character string
AnswerD

Character string (VARCHAR or CHAR) is ideal for tracking numbers because it preserves leading zeros, supports alphanumeric formats, and handles varying lengths. It ensures the exact identifier is stored without numeric conversion issues. Uniqueness can be enforced with a primary key or unique constraint. This data type also supports efficient indexing for lookups, making it the most appropriate choice for shipment tracking numbers.

Why this answer

Tracking numbers are identifiers that may include letters, leading zeros, and varying lengths, so a character string data type preserves their exact format and supports unique constraints. Integer, Boolean, and date/time types each fail to represent the full range of possible tracking numbers, risking data loss or inability to enforce uniqueness. Character strings also allow efficient indexing for fast lookups.

Exam trap

The trap here is assuming that a numeric-looking identifier should be stored as an integer, which discards leading zeros and breaks alphanumeric formats.

Practice this question →
30
Multi-Selectmedium

A data analyst is comparing characteristics of structured and unstructured data. Which TWO of the following are characteristics of structured data? (Choose two.)

Select 2 answers
A.Data is typically stored as raw text
B.Data lacks a fixed format
C.Data is stored in predefined schemas
D.Data often requires NoSQL databases for storage
E.Data can be easily queried using SQL
AnswersC, E

Structured data conforms to a predefined schema, such as relational tables with declared columns and data types. This enforced organisation is what enables consistent storage, validation and predictable retrieval, distinguishing it from unstructured content like free text or media.

Why this answer

Option C is correct because structured data is organized according to a predefined schema—such as tables with defined columns, data types, and relationships—which is the defining trait of structured data in relational systems. Option E is correct because structured data stored in relational tables can be directly queried with SQL, using SELECT, JOIN, WHERE, and other standard statements. The unmarked options do not belong: raw text (A) and lack of a fixed format (B) describe unstructured data such as documents or free-form text, and NoSQL databases (D) are typically used for semi-structured or unstructured data rather than being a characteristic of structured data.

Exam trap

The trap here is that candidates often confuse 'lack of fixed format' (unstructured) with 'flexibility in storage' (NoSQL), leading them to select options B or D, which describe unstructured or semi-structured data, not structured data.

Practice this question →
31
MCQmedium

A data engineer is ingesting streaming data from a fleet of delivery vehicles. Each vehicle sends GPS coordinates, speed, and timestamp every second. The engineer needs to store this data for real-time dashboards and also retain it for long-term historical analysis. Which data storage approach best balances real-time access and cost-effective long-term retention?

A.Store all data in a relational database with row-based storage
B.Keep all data in memory using an in-memory cache
C.Use a time-series database for recent data and archive to object storage
D.Store all data in a key-value store with no secondary indexes
AnswerC

A time-series database is optimized for high-ingest, timestamped data and supports fast real-time queries for dashboards. Archiving older data to object storage (e.g., S3) provides low-cost, durable long-term retention. This hybrid approach balances performance and cost, allowing recent data to be queried quickly while historical data remains accessible for batch analysis.

Why this answer

A time-series database handles high-velocity timestamped writes and enables fast real-time queries for dashboards. Archiving older data to object storage reduces cost while preserving durability for historical analysis. Row-based relational databases, key-value stores without indexes, and in-memory caches each fail to balance real-time performance with cost-effective long-term retention for streaming vehicle telemetry.

Exam trap

The trap here is choosing a single storage technology for both real-time and archival needs, ignoring that a hybrid approach is often required to balance performance and cost.

Practice this question →
32
MCQmedium

A data engineer loads a CSV export into a table. The source system writes the value '007' for a product code, but after loading, an analyst queries the table and sees the value 7. The analyst needs the leading zero preserved for downstream matching against another system. Which action should the engineer take?

A.Create a derived column that concatenates a literal zero with the numeric product code
B.Change the column data type to a numeric type with a display format that pads to three digits
C.Add a check constraint that rejects any product code shorter than three characters
D.Store the product code in a character or string column so the leading zero is retained
AnswerD

A character or string column treats '007' as a sequence of characters, preserving the leading zero exactly as written. This lets downstream matches against another system that uses the same textual code succeed. Since the code is an identifier rather than a quantity to calculate, storing it as text is the correct modeling choice.

Why this answer

Product codes are identifiers, not quantities, so leading zeros are meaningful and must be preserved. Storing the value in a character column keeps '007' intact and allows reliable matching with other systems, whereas numeric storage strips the zero and presentation formats do not survive joins or exports.

Exam trap

The trap here is believing that a numeric display format or a derived expression can permanently restore a leading zero, when the stored data type itself has already discarded it.

Practice this question →
33
MCQmedium

A data scientist is building a model to predict customer churn. The company's internal CRM system provides customer demographics and transaction history. They also purchase demographic data from a third-party vendor. How should the purchased data be classified?

A.Secondary data
B.Internal data
C.Structured data
D.Primary data
AnswerA

Purchased vendor demographics were collected by another party for its own purposes, not by the company for this churn model. That external origin makes it secondary data, satisfying the stem's classification requirement for the third-party demographic feed.

Why this answer

Purchased demographic data from a third-party vendor is classified as secondary data because it was originally collected by another entity for a different purpose and is being reused by the data scientist for churn prediction. Secondary data contrasts with primary data, which is collected firsthand for the specific analysis at hand. This classification is independent of whether the data is structured or unstructured.

Exam trap

The trap here is that candidates confuse 'secondary data' with 'structured data' because purchased data is often delivered in a structured format like CSV, but the classification is based on data origin and collection purpose, not its structure.

How to eliminate wrong answers

Option B (Internal data) is wrong because the purchased data originates from an external vendor, not from the company's own CRM or internal systems. Option C (Structured data) is wrong because the classification of data as primary or secondary is about its origin and collection purpose, not its format; purchased data could be structured or unstructured. Option D (Primary data) is wrong because primary data is collected directly by the researcher for the specific study, whereas this data was pre-existing and collected by a third party.

Practice this question →
34
MCQhard

A data engineer is designing a data pipeline where raw data is loaded into a cloud data warehouse (Snowflake) and then transformed using SQL. This approach is called:

A.ELT
B.ETL
C.Data migration
D.Data wrangling
AnswerA

ELT loads raw data into Snowflake before any transformation, satisfying the stem's requirement that data lands in the warehouse first and SQL runs afterwards. Unlike ETL, where transformation precedes loading, here Snowflake's compute performs the SQL transformations, matching the described pipeline exactly.

Why this answer

ELT (Extract, Load, Transform) loads raw data into the target warehouse first and then performs transformations using the warehouse's compute engine — exactly the pattern described with Snowflake. This leverages Snowflake's elastic compute and SQL capabilities to transform data in place, avoiding a separate transformation tier. ETL, by contrast, transforms data before loading it into the warehouse.

Exam trap

DA0-002 often tests the ETL vs. ELT distinction — candidates pick ETL by default because it is the older, more familiar term, ignoring the clue that transformation happens after loading into the warehouse.

How to eliminate wrong answers

Option B is wrong because ETL transforms data in an intermediate staging/processing layer (e.g., Informatica, SSIS) before loading it into the warehouse, which is the opposite order from the scenario described. Option C is wrong because data migration refers to moving data between systems (e.g., on-prem to cloud), not to a load-then-transform pipeline pattern. Option D is wrong because data wrangling is the manual/semi-automated cleaning and reshaping of data, a subset of transformation work, not the architectural pipeline pattern itself.

Practice this question →
35
Multi-Selecthard

Which THREE data quality dimensions are commonly assessed in a data profiling task?

Select 3 answers
A.Scalability
B.Consistency
C.Uniqueness
D.Availability
E.Completeness
AnswersB, C, E

Consistency ensures uniform data representation, a common profiling check.

Why this answer

Consistency is a core data quality dimension assessed in data profiling because it evaluates whether data values are free from contradiction and adhere to the same representation rules across records. In profiling tools like Informatica or Talend, consistency checks identify violations such as 'NY' vs 'New York' in a state column, ensuring semantic uniformity.

Exam trap

CompTIA often tests the distinction between data quality dimensions (completeness, consistency, uniqueness) and system-level attributes (scalability, availability), leading candidates to mistakenly select non-quality terms like 'Availability' or 'Scalability' because they sound relevant to data management.

Practice this question →
36
Multi-Selectmedium

Which TWO of the following are considered structured data?

Select 2 answers
A.A PDF report with free-form text
B.A relational database table
C.A JPEG image of a product
D.A JSON file with nested key-value pairs
E.A CSV file containing sales records
AnswersB, E

Tables have a fixed schema.

Why this answer

A relational database table stores data in a predefined schema of rows and columns, where each column has a fixed data type. This rigid structure allows for efficient querying, indexing, and relational operations, making it a classic example of structured data.

Exam trap

The trap here is that candidates often mistake semi-structured data (like JSON) for structured data because it has key-value pairs, but the DA0-001 exam strictly defines structured data as having a fixed, predefined schema—typically found in relational databases or CSV files with consistent column headers.

Practice this question →
37
MCQmedium

A data engineer is designing a data warehouse for a retail company. The fact table must record each sale transaction, including product ID, store ID, date, and quantity sold. The product details (name, category, price) are stored in a separate table. This design is an example of which data modeling concept?

A.Star schema
B.Data lake
C.Normalization
D.Snowflake schema
AnswerA

A star schema satisfies this design because it centres a fact table of sale transactions — product ID, store ID, date, quantity — surrounded by denormalised dimension tables such as product, holding name, category and price. The separate product table is precisely that dimension, keeping descriptive attributes out of the fact grain.

Why this answer

This design is a classic star schema, where a central fact table (sales transactions) contains foreign keys to dimension tables (product, store, date). The fact table stores quantitative measures (quantity sold) and foreign keys, while dimension tables hold descriptive attributes (product name, category, price). This separation optimizes query performance for OLAP workloads by reducing joins and enabling straightforward aggregations.

Exam trap

The trap here is that candidates confuse star schema with snowflake schema, but the key differentiator is whether dimension tables are further normalized (snowflake) or kept denormalized (star), and this question's single product table clearly indicates a star schema.

How to eliminate wrong answers

Option B is wrong because a data lake stores raw, unprocessed data in its native format (e.g., CSV, Parquet) without a predefined schema, whereas this design explicitly separates facts and dimensions with a structured schema. Option C is wrong because normalization would split data into many related tables to eliminate redundancy (e.g., separating product category into its own table), but here product details are kept in a single dimension table, which is denormalized. Option D is wrong because a snowflake schema further normalizes dimension tables into sub-dimensions (e.g., splitting product category into a separate table), but this design keeps product details in one table, making it a star schema, not a snowflake.

Practice this question →
38
MCQhard

An e-commerce company stores customer support emails in a text database, product images in a blob store, and sales transactions in a SQL table. Which data store holds only structured data?

A.Blob store
B.Text database
C.SQL table
D.None
AnswerC

The SQL table stores sales transactions in a fixed relational schema with defined columns and types, making it structured data. The text database and blob store hold unstructured content, satisfying the stem's request to identify the structured store.

Why this answer

Structured data conforms to a predefined schema with rows and columns, enforcing data types and relationships. A SQL table is the canonical example of a structured data store because it organizes data into tables with fixed schemas, supports ACID transactions, and enables relational queries via SQL. In contrast, blob stores and text databases store unstructured or semi-structured data without a rigid schema.

Exam trap

The trap here is that candidates confuse 'structured data' with any data that has some organization (like tags in a blob store or fields in a text document), but only a SQL table enforces a rigid, predefined schema with typed columns and relational constraints, which is the defining characteristic of structured data.

How to eliminate wrong answers

Option A is wrong because a blob store (e.g., Amazon S3, Azure Blob Storage) stores binary large objects such as images, videos, or documents as opaque blobs with no inherent schema or structure — it is designed for unstructured data. Option B is wrong because a text database (e.g., a NoSQL document store like MongoDB or a plain text file repository) stores free-form text or semi-structured documents (e.g., JSON, XML) that lack a fixed, predefined schema and are not organized into rows and columns. Option D is wrong because the SQL table explicitly holds structured data, so 'None' is incorrect.

Practice this question →
39
Multi-Selectmedium

Which THREE of the following are components of Master Data Management (MDM)? (Select 3)

Select 3 answers
A.Data governance
B.Data quality management
C.Data encryption
D.Data archival
E.Data integration
AnswersA, B, E

Data governance is a core MDM component, defining ownership, stewardship, policies and standards that keep master data trustworthy across domains. It satisfies the stem's requirement to identify MDM components, providing the control framework within which mastering and integration operate.

Why this answer

MDM includes data governance, data integration, and data quality management to maintain a single source of truth.

Practice this question →
40
MCQhard

A data analyst needs to combine customer data from a MySQL transactional database with product data from a MongoDB document store to create a unified view for reporting. The analyst uses a SQL query that joins the tables after extracting data from both sources. Which database concept is being applied?

A.View
B.Join
C.Stored procedure
D.Index
AnswerB

Joins combine rows from two or more tables based on a related column.

Why this answer

(Join) because the scenario describes combining data from two different sources—MySQL and MongoDB—into a unified view using a SQL query that joins the tables after extraction. This is a classic example of a cross-source join, where data from disparate databases is merged based on a common key, which is the fundamental purpose of a JOIN operation in SQL.

Exam trap

The trap here is that candidates may confuse a 'view' with a cross-source join, thinking a view can span multiple databases, but a view is limited to a single database and cannot directly reference tables from different database systems like MySQL and MongoDB.

How to eliminate wrong answers

Option A (View) is wrong because a view is a saved SQL query that presents data from one or more tables within the same database, not a mechanism to combine data from different source systems like MySQL and MongoDB. Option C (Stored procedure) is wrong because a stored procedure is a precompiled collection of SQL statements that performs a specific task within a single database, not a concept for joining data across heterogeneous data stores. Option D (Index) is wrong because an index is a data structure that improves the speed of data retrieval operations on a table, not a method for combining data from multiple sources.

Practice this question →
41
MCQmedium

Which database concept ensures that data in one table corresponds to data in another table, preventing orphan records?

A.Index
B.Referential integrity
C.Foreign key
D.Primary key
AnswerB

Referential integrity enforces foreign key constraints so every value in a child table matches an existing primary key in the parent table, directly preventing orphan records. This satisfies the stem's requirement that data in one table corresponds to data in another, which entity integrity and normalisation do not guarantee.

Why this answer

Referential integrity is the database principle that ensures relationships between tables remain consistent — every foreign key value must match an existing primary key value, preventing orphan records. It is enforced through constraints like FOREIGN KEY with ON DELETE/UPDATE actions.

Exam trap

DA0-002 often tests the distinction between the foreign key (the column/constraint) and referential integrity (the concept/rule), causing candidates to select the implementation rather than the principle.

How to eliminate wrong answers

Option A is wrong because an index is a performance structure for faster lookups, not a consistency mechanism. Option C is wrong because a foreign key is the column-level construct that implements referential integrity, but the concept itself is referential integrity — the question asks for the concept. Option D is wrong because a primary key uniquely identifies rows in its own table and does not by itself prevent orphans in a related table.

Practice this question →
42
MCQmedium

A data analyst at a hospital is building a report on patient readmissions. The analyst needs to combine the patient demographics table (which uses PatientID as the primary key) with the admissions table (which uses AdmissionID as the primary key and also contains PatientID as a foreign key). Which type of operation should the analyst use to combine these two tables?

A.Aggregate
B.Join
C.Intersect
D.Union
AnswerB

A join combines columns from two or more tables based on a related column, such as PatientID. Here, the demographics and admissions tables share PatientID, so a join will correctly merge patient details with admission records. This is the standard relational operation for combining tables horizontally when a common key exists.

Why this answer

Combining two tables that share a common key, such as PatientID, requires a join operation. A join matches rows from both tables on the key and returns columns from both, enabling the analyst to see patient demographics alongside each admission. Other set operations like union or intersect do not align columns properly for this purpose.

Exam trap

The trap here is confusing set operations like union or intersect with join operations, which are used for different purposes in relational data combination.

Practice this question →
43
MCQeasy

An organization wants to assign responsibility for data quality and metadata management. Which role is primarily accountable for defining data standards and ensuring data quality across a specific domain?

A.Data analyst
B.Data owner
C.Data steward
D.Data custodian
AnswerC

The data steward is accountable within a domain for defining data standards, documenting metadata and monitoring quality. This domain-focused accountability role matches the requirement, unlike executive owners or technical administrators who lack that stewardship mandate.

Why this answer

The data steward is the role primarily accountable for defining data standards and ensuring data quality within a specific domain. This aligns with the DAMA-DMBOK framework, where the data steward acts as the business-side owner of data content, establishing rules for data entry, validation, and metadata management to maintain consistency and accuracy.

Exam trap

The trap here is confusing the data steward with the data owner or data custodian, as many candidates mistakenly think the owner handles domain-level quality or that the custodian defines standards, when in fact the steward is the bridge between business requirements and technical enforcement.

How to eliminate wrong answers

Option A is wrong because a data analyst focuses on querying, analyzing, and reporting data, not on defining standards or governing data quality across a domain. Option B is wrong because a data owner is typically a senior executive accountable for data assets at an enterprise level, not for day-to-day domain-specific standards and quality enforcement. Option D is wrong because a data custodian (or data steward in some frameworks) handles technical implementation, storage, and security, but does not define business-level data standards or quality rules.

Practice this question →
44
MCQeasy

Which of the following data sources is most likely to generate streaming data?

A.Transactional database
B.Flat file
C.API
D.IoT sensors
AnswerD

IoT sensors emit continuous, time-stamped measurements as events occur, making them a natural streaming source. Unlike batch extracts or static reference tables, sensor telemetry arrives incrementally and is consumed by stream processing platforms in near real time.

Why this answer

Streaming data is continuously generated from sources like IoT sensors, clickstreams, and social media feeds.

Practice this question →
45
MCQeasy

A data analyst receives a dataset with a column 'salary' that contains values like '45,000', '55,000', and '65,000'. The analyst notices that the values are stored as text. Which data concept should be applied to convert the salary column from text to numeric format for analysis?

A.Data imputation
B.Data type conversion
C.Data validation
D.Data normalization
AnswerB

Data type conversion casts the text values to a numeric type, stripping the comma separators so arithmetic and aggregation work correctly. The salary column's text storage is the constraint, and conversion changes its type rather than its values.

Why this answer

Data type conversion is the correct concept because the salary values are stored as text (string) but need to be converted to a numeric type (e.g., integer or float) for mathematical operations like aggregation or averaging. In tools like Python (pandas `astype(float)`), SQL (`CAST(salary AS INTEGER)`), or Excel (`VALUE()` function), this explicit conversion ensures the data is treated as numbers, not strings. Without conversion, operations like `SUM` or `AVG` would fail or produce incorrect results.

Exam trap

CompTIA often tests the distinction between data transformation (type conversion) and data preparation techniques like imputation or normalization, trapping candidates who confuse 'changing format' with 'filling gaps' or 'scaling values'.

How to eliminate wrong answers

Option A is wrong because data imputation deals with filling missing values (e.g., using mean or median), not changing the data type of existing values. Option C is wrong because data validation checks whether data meets predefined rules (e.g., range or format constraints), but it does not transform text to numeric format. Option D is wrong because data normalization rescales numeric values to a standard range (e.g., 0–1 or z-scores), which assumes the data is already numeric, not converting text to numbers.

Practice this question →
46
MCQmedium

A company requires real-time masking of credit card numbers for customer support agents while allowing full access for accountants. Which technique should be implemented?

A.Dynamic data masking
B.Tokenization
C.Static data masking
D.Data encryption
AnswerA

Dynamic data masking obscures credit card numbers in query results at runtime based on the requesting user's role, so support agents see masked values while accountants retain full access. Static masking would alter stored data permanently, failing the real-time requirement.

Why this answer

Dynamic data masking (DDM) applies masking rules at query runtime based on user privileges, allowing accountants full access while customer support agents see only masked credit card numbers. Unlike static masking, DDM does not alter the underlying stored data, making it ideal for real-time, role-based obfuscation without duplicating or transforming the database.

Exam trap

CompTIA often tests the misconception that encryption or tokenization can provide real-time, role-based masking, but these technologies either require decryption (exposing the full value) or introduce latency and storage overhead, making dynamic data masking the only correct choice for this use case.

How to eliminate wrong answers

Option B (Tokenization) is wrong because it replaces sensitive data with a non-sensitive token stored in a separate vault, requiring a detokenization process that adds latency and is not designed for real-time, role-based masking within the same database. Option C (Static data masking) is wrong because it creates a permanent, masked copy of the data in a non-production environment, which cannot provide real-time, on-the-fly masking for live queries. Option D (Data encryption) is wrong because encryption protects data at rest or in transit but does not provide role-based masking at query time; decryption keys grant full access, not partial masking.

Practice this question →
47
MCQmedium

A retail company stores customer purchase history in a relational database. The database contains a table 'transactions' with columns: transaction_id, customer_id, product_id, quantity, price, and transaction_date. A data analyst needs to create a report that shows total revenue per customer for the last quarter. Which data concept describes the relationship between customer_id and total revenue?

A.Foreign key
B.Composite attribute
C.Derived attribute
D.Atomic attribute
AnswerC

Total revenue is not stored but computed by aggregating quantity multiplied by price grouped by customer_id. Because it is calculated from existing stored columns rather than persisted, it is a derived attribute, satisfying the report's need for per-customer revenue.

Why this answer

Total revenue is calculated by summing (quantity * price) for each customer, making it a derived attribute because it is computed from existing stored data (quantity and price) rather than stored directly. In the context of the 'transactions' table, customer_id is a stored key, but total_revenue is not stored; it is derived via aggregation, which matches the definition of a derived attribute in database design.

Exam trap

CompTIA often tests the confusion between a derived attribute (computed from other attributes) and a foreign key (a referential constraint), leading candidates to incorrectly select 'foreign key' because customer_id appears in multiple tables.

How to eliminate wrong answers

Option A is wrong because a foreign key is a column that references a primary key in another table to enforce referential integrity; customer_id in the transactions table is a foreign key referencing the customers table, but total revenue is not a key—it is a computed value. Option B is wrong because a composite attribute is an attribute that can be divided into smaller sub-parts (e.g., address into street, city, zip); total revenue is a single calculated value, not composed of multiple atomic sub-attributes. Option D is wrong because an atomic attribute is indivisible and stored directly (e.g., price, quantity); total revenue is not stored but derived, so it violates the atomicity principle.

Practice this question →
48
MCQmedium

A data engineer is choosing a storage approach for a new analytics platform. The workload consists of wide, denormalized event tables with dozens of attributes, queries that scan a few columns across billions of rows, and heavy aggregation rather than single-row lookups. Which storage structure is best suited to this workload?

A.A normalized schema with many small tables joined at query time
B.A columnar storage format that stores values of each column contiguously and supports compression
C.A row-oriented relational table with a B-tree index on the primary key
D.A key-value store that maps each event ID to a serialized JSON document
AnswerB

Columnar storage lays each column's values together, so a query that reads only a few attributes touches only those column segments and skips the rest. Contiguous values of the same type also compress far better, reducing I/O for the large aggregations described. This matches the analytical pattern of scanning few columns across many rows.

Why this answer

The described workload reads a small number of columns from very wide tables and performs large aggregations, which is exactly what columnar storage optimizes: reading only the needed column segments and compressing similar values. Row-oriented tables with B-tree indexes favor point lookups, key-value stores favor document retrieval by key, and heavily normalized schemas add join overhead. Columnar layout therefore fits the analytical scan pattern best.

Exam trap

The trap here is equating fast primary-key lookups with fast analytical scans, when indexing a row store does not reduce the columns read during a wide aggregation.

Practice this question →
49
MCQmedium

A data engineer is designing a database for an online store. The database must enforce strict consistency and handle complex transactions involving multiple tables, such as orders, customers, and inventory. Which database type should the engineer choose?

A.Relational database
B.Graph database
C.Key-value store
D.Document database
AnswerA

Relational databases use ACID transactions, ensuring strict consistency and supporting complex joins across normalized tables. They are ideal for transactional systems like order processing where data integrity is critical. This makes relational the best fit for the scenario.

Why this answer

The correct answer is Relational database because it provides ACID compliance and supports complex joins, which are essential for handling transactions across multiple related tables. Other database types lack the necessary transactional guarantees or relational capabilities for this use case.

Exam trap

The trap here is assuming that any database that can store data is suitable; however, only relational databases provide the strict consistency and multi-table transaction support required for this scenario.

Practice this question →
50
MCQeasy

A data analyst receives a file with the extension .json. This file contains product information with attributes that vary between records. How should this file be classified?

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

JSON stores data in key-value pairs with a defined syntax but no rigid schema, so attributes can vary between records. That self-describing yet non-tabular structure is the defining characteristic of semi-structured data, distinguishing it from structured relational tables and unstructured raw content.

Why this answer

A JSON file with varying attributes per record is a classic example of semi-structured data. Unlike strictly structured data (e.g., a relational table with fixed columns), JSON allows each object to have a different set of key-value pairs, making it schema-flexible. This self-describing nature, where metadata is embedded within the data itself, is the defining characteristic of semi-structured formats.

Exam trap

The trap here is that candidates confuse 'structured data' with any data that has a format or organization, forgetting that structured data specifically requires a fixed, predefined schema enforced at write time, unlike JSON's flexible schema-on-read approach.

How to eliminate wrong answers

Option B is wrong because structured data requires a rigid, predefined schema (like a SQL table with fixed columns and data types), which JSON explicitly does not enforce. Option C is wrong because transactional data refers to records of business events (e.g., sales, orders) and is a classification by use case, not by format; a JSON file can contain transactional data, but the question asks how the file itself should be classified based on its structure. Option D is wrong because unstructured data lacks any internal structure or metadata (e.g., raw text, images, audio), whereas JSON has a clear hierarchical structure with keys and values.

Practice this question →
51
MCQmedium

An organization is implementing a data warehouse to support business intelligence reporting. The data warehouse must ensure that transactions are processed reliably. Which property guarantees that each transaction is treated as a single, indivisible unit?

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

Atomicity guarantees a transaction executes entirely or not at all, treating it as one indivisible unit. If any statement fails, the whole transaction rolls back, leaving no partial writes. Consistency, isolation and durability address different guarantees, so atomicity satisfies the stem's requirement.

Why this answer

Atomicity (option C) is the correct property because it ensures that a transaction is treated as a single, indivisible unit of work. In the context of a data warehouse, this means that either all operations within the transaction are committed successfully, or none are applied, preventing partial updates that could corrupt the data. This is a core component of the ACID (Atomicity, Consistency, Isolation, Durability) model, which is fundamental to reliable transaction processing in databases like SQL Server, Oracle, or PostgreSQL.

Exam trap

The trap here is that candidates often confuse atomicity with consistency, thinking that 'indivisible unit' means the data must be consistent, but consistency is a separate property that ensures data integrity rules are met, not that the transaction is all-or-nothing.

How to eliminate wrong answers

Option A (Consistency) is wrong because consistency ensures that a transaction brings the database from one valid state to another, preserving all defined rules (e.g., constraints, triggers), but it does not guarantee that the transaction is treated as a single unit. Option B (Isolation) is wrong because isolation controls how transaction changes are visible to other concurrent transactions, preventing dirty reads and other anomalies, but it does not address the indivisibility of the transaction itself. Option D (Durability) is wrong because durability guarantees that once a transaction is committed, its changes persist even in the event of a system failure (e.g., via write-ahead logging), but it does not ensure the transaction is atomic.

Practice this question →
52
MCQhard

A data governance team is drafting a policy for handling personally identifiable information (PII). According to data governance best practices, which document should define the classification levels and handling procedures?

A.Data dictionary
B.Data classification policy
C.Data quality report
D.Data flow diagram
AnswerB

A data classification policy defines the tiers of sensitivity and the handling rules for each, directly satisfying the stem's requirement for a document specifying PII classification levels and procedures. It governs how data is labelled and protected, unlike retention schedules or access-control standards, which address different governance concerns.

Why this answer

The data classification policy is the authoritative document that defines classification levels (e.g., public, internal, confidential, restricted) and specifies handling procedures for each category, including PII. This aligns with data governance best practices, as it establishes the rules for labeling, storing, transmitting, and disposing of sensitive data. A data dictionary describes metadata and schema, not classification rules.

Exam trap

The trap here is that candidates confuse the data dictionary (which describes data structure) with the data classification policy (which governs data sensitivity and handling), leading them to select the dictionary as the document that defines classification levels.

How to eliminate wrong answers

Option A is wrong because a data dictionary documents metadata such as field names, data types, and definitions, but it does not define classification levels or handling procedures for PII. Option C is wrong because a data quality report measures data accuracy, completeness, and consistency, not security or classification policies. Option D is wrong because a data flow diagram visually maps how data moves between systems, but it does not prescribe classification levels or handling rules.

Practice this question →
53
MCQeasy

A retail company stores customer transaction data in a relational database. They want to analyze purchasing patterns over time. Which type of data structure best supports this analysis?

A.Relational table
B.Graph database
C.Document store
D.Key-value store
AnswerA

A relational table stores transactions as rows with typed columns, so SQL aggregation and time-series grouping can reveal purchasing trends. Its fixed schema and join support satisfy the requirement to analyse historical transaction records over time, which non-relational or unstructured stores handle less directly.

Why this answer

A relational table is the correct choice because it organizes transaction data into structured rows and columns with defined schemas, enabling efficient SQL-based queries for time-series analysis (e.g., aggregating purchases by date, customer, or product). The relational model supports ACID transactions and joins across related tables (e.g., customers, products, transactions), which is essential for analyzing purchasing patterns over time while maintaining data integrity.

Exam trap

The trap here is that candidates may confuse 'analyzing purchasing patterns over time' with needing a graph database for relationships, but the key requirement is structured time-series aggregation, which is a core strength of relational tables, not graph or NoSQL stores.

How to eliminate wrong answers

Option B (Graph database) is wrong because graph databases excel at modeling relationships between entities (e.g., social networks or recommendation engines) but are not optimized for time-series aggregation or range queries on structured transaction data; they lack native support for SQL-style GROUP BY and window functions. Option C (Document store) is wrong because document stores (e.g., MongoDB) store semi-structured JSON-like documents, which can lead to data duplication and complex aggregation pipelines for time-based analysis, and they typically do not enforce strict schemas or support ACID transactions across multiple collections. Option D (Key-value store) is wrong because key-value stores (e.g., Redis) provide fast lookups by a single key but cannot efficiently query on multiple attributes (e.g., date range, product category) or perform relational joins, making them unsuitable for analytical queries on purchasing patterns.

Practice this question →
54
MCQeasy

A data analyst at a marketing agency is working with a dataset containing customer demographics, purchase history, and social media engagement metrics. The agency wants to perform sentiment analysis on unstructured social media comments to identify brand perception. The dataset also includes structured fields like age, income, and purchase amounts. The analyst needs to choose a storage and processing platform that can handle both structured and unstructured data efficiently without requiring extensive schema definition upfront. Which platform should the analyst recommend?

A.Relational database (RDBMS)
B.Data lake
C.Data warehouse
D.NoSQL document database
AnswerB

A data lake stores raw structured and unstructured data without upfront schema definition, satisfying the stem's schema-on-read constraint. Unlike a data warehouse, which demands schema-on-write modelling, it ingests social media comments and demographic fields together, letting the analyst apply sentiment analysis later.

Why this answer

A data lake is the correct choice because it can store both structured data (e.g., age, income, purchase amounts) and unstructured data (e.g., social media comments) in its native format without requiring a predefined schema. This flexibility allows the analyst to ingest raw social media text for sentiment analysis and later apply schema-on-read for structured queries, avoiding the upfront schema definition needed by other platforms.

Exam trap

The trap here is that candidates often confuse a data warehouse with a data lake, assuming both can handle unstructured data, but a data warehouse requires structured, transformed data and cannot natively store raw social media comments without prior schema definition.

How to eliminate wrong answers

Option A is wrong because a relational database (RDBMS) requires a rigid, predefined schema and is optimized for structured data, making it inefficient for storing and processing unstructured social media comments without extensive ETL. Option C is wrong because a data warehouse is designed for structured, processed data and typically uses a schema-on-write approach, which cannot natively handle unstructured text like social media comments without significant transformation. Option D is wrong because a NoSQL document database can store semi-structured data (e.g., JSON) but is not optimized for large-scale, raw unstructured text and lacks the integrated processing capabilities (e.g., Apache Spark or Hadoop) that a data lake provides for sentiment analysis.

Practice this question →
55
MCQeasy

Which of the following is a characteristic of structured data?

A.It conforms to a fixed schema with rows and columns.
B.It has a flexible schema that can vary per record.
C.It cannot be analyzed using SQL.
D.It is stored as blobs in a data lake.
AnswerA

Structured data is organised into a predefined, fixed schema of rows and columns, typically stored in relational databases and queried with SQL. This tabular rigidity satisfies the stem's characteristic, distinguishing it from semi-structured formats like JSON and unstructured content such as text.

Why this answer

Structured data is defined by its adherence to a fixed schema, typically organized into rows and columns within relational databases. This rigid structure enables efficient querying and manipulation using SQL, as each field has a predefined data type and constraints. The correct answer highlights this fundamental characteristic, which distinguishes structured data from semi-structured or unstructured formats.

Exam trap

The trap here is that candidates often confuse semi-structured data (which has some organizational tags but no fixed schema) with structured data, leading them to select Option B, or they mistakenly think SQL cannot analyze structured data, falling for Option C.

How to eliminate wrong answers

Option B is wrong because a flexible schema that can vary per record describes semi-structured data (e.g., JSON, XML), not structured data. Option C is wrong because structured data is specifically designed to be analyzed using SQL, which is the primary query language for relational databases. Option D is wrong because storing data as blobs in a data lake is characteristic of unstructured data (e.g., images, videos), not structured data, which is stored in tables with defined schemas.

Practice this question →
56
MCQmedium

A company ingests customer clickstream data from its website. The data arrives continuously in JSON format and must be stored for real-time analytics. Which type of data source is being described?

A.Transactional database
B.Flat file
C.Data warehouse
D.Streaming data
AnswerD

Streaming data matches because the clickstream arrives continuously as discrete JSON events requiring real-time analytics, rather than being collected in scheduled batches. This satisfies the stem's ingestion constraint: an unbounded, ongoing flow of records processed as they arrive, distinguishing it from batch or static file sources.

Why this answer

The description matches a streaming data source because clickstream data arrives continuously in JSON format and must be stored for real-time analytics. Streaming data sources, such as Apache Kafka or Amazon Kinesis, ingest unbounded data in real time, enabling immediate processing and analytics without batch delays.

Exam trap

CompTIA Data+ often tests the distinction between 'streaming data' and 'data warehouse' by describing continuous ingestion, leading candidates to mistakenly choose 'data warehouse' because they associate analytics with warehousing, ignoring the real-time requirement.

How to eliminate wrong answers

Option A is wrong because a transactional database (e.g., OLTP system) is designed for ACID-compliant transaction processing, not for ingesting continuous, high-velocity streaming data. Option B is wrong because a flat file (e.g., CSV or text file) is a static, batch-oriented storage format that cannot handle real-time, continuous ingestion without manual intervention or scheduled loads. Option C is wrong because a data warehouse is optimized for structured, historical analytics and typically relies on batch ETL processes, not real-time streaming ingestion from clickstream sources.

Practice this question →
57
MCQmedium

Refer to the exhibit. A data analyst notices that direct S3 access to files outside the "incoming/" prefix is blocked. Which data governance principle does this policy enforce?

A.Data colocation
B.Data retention
C.Data access control
D.Data encryption
AnswerC

Restricting direct S3 access to the incoming/ prefix enforces data access control, the governance principle governing who and what may reach specific datasets. Other principles such as retention or quality do not determine prefix-level read permissions.

Why this answer

The policy blocks direct S3 access to files outside the 'incoming/' prefix, which restricts which users or roles can read or write objects in specific S3 prefixes. This is a classic implementation of data access control, as it enforces permissions based on the resource path, ensuring only authorized operations are allowed on designated data. In AWS S3, such restrictions are typically applied via bucket policies or IAM policies that use conditions like `s3:prefix` to limit access.

Exam trap

CompTIA often tests the distinction between access control and encryption by presenting a policy that restricts access based on a path or condition, leading candidates to confuse it with data encryption, which is about scrambling data rather than authorizing access.

How to eliminate wrong answers

Option A is wrong because data colocation refers to physically or logically placing related data together for performance or compliance, not to restricting access based on a prefix. Option B is wrong because data retention governs how long data is kept (e.g., lifecycle policies or retention periods), not who can access it. Option D is wrong because data encryption protects data at rest or in transit (e.g., using SSE-S3 or TLS), but the policy described does not mention encryption keys, algorithms, or any cryptographic controls.

Practice this question →
58
MCQmedium

A financial analyst is working with a dataset of stock prices. The dataset contains a column 'Price' that records the closing price of each stock in USD. The analyst wants to calculate the percentage change in price from the previous day for each stock. Which data type is most appropriate for the 'Price' column?

A.Integer
B.Float
C.String
D.Boolean
AnswerB

Float data types represent real numbers with fractional components, which is necessary for storing stock prices like $123.45. The analyst needs to compute percentage changes, which involve division and multiplication, so preserving decimal precision is critical. Float types accommodate the continuous nature of price data and support the required arithmetic operations.

Why this answer

Stock prices require decimal precision to accurately represent fractional dollar amounts and to perform arithmetic for percentage changes. Float data types store real numbers with decimals, making them the correct choice. Integer, string, and Boolean types cannot properly capture or compute with the continuous numeric values needed for this analysis.

Exam trap

The trap here is selecting integer because prices are often thought of as whole numbers, but stock prices include cents that are essential for accurate calculations.

Practice this question →
59
MCQhard

A data audit reveals that some numbers in the "Revenue" column were manually entered from PDF invoices. This introduces potential errors. Which data concept is being addressed?

A.Data lineage
B.Data quality
C.Data security
D.Data governance
AnswerB

Manual transcription from PDF invoices introduces typographical and transcription errors, directly degrading accuracy, a core data quality dimension. Data quality addresses fitness for purpose, so the audit's concern with erroneous revenue figures maps to this concept.

Why this answer

The scenario describes a data audit that identifies potential errors from manual data entry from PDF invoices. This directly relates to data quality, which assesses aspects like accuracy, completeness, and consistency. The audit is highlighting a quality concern (potential errors), not lineage tracking.

Data lineage focuses on the origin and transformation of data, but the primary issue here is the risk of inaccuracies, making data quality the correct concept.

Exam trap

Candidates may see the mention of 'audit' and 'origin' and incorrectly choose data lineage. However, the key issue is the potential errors from manual entry, which is a data quality concern. The audit is identifying a quality problem, not tracing the data's path.

How to eliminate wrong answers

Option A is wrong because data lineage tracks the origin, movement, and transformation of data through its lifecycle, not the potential errors from manual entry. Option C is wrong because data security focuses on protecting data from unauthorized access, breaches, or corruption, not on the accuracy of manually entered values. Option D is wrong because data governance defines policies, roles, and procedures for managing data assets, but the specific issue of manual entry errors falls under data quality assessment, not governance frameworks.

Practice this question →
60
MCQmedium

A healthcare analytics team is building a patient readmission risk model. They have a dataset containing admission date, discharge date, primary diagnosis code, and patient age. To predict readmission within 30 days, the team needs to derive a new field that represents the number of days a patient stayed in the hospital. Which data transformation technique should they apply to create this derived field?

A.Date arithmetic
B.Data imputation
C.Data aggregation
D.Data normalization
AnswerA

Date arithmetic subtracts the admission date from the discharge date to produce the length of stay in days. This directly creates the derived field the team needs. It is the standard transformation for calculating durations between two temporal columns and is appropriate for a per-row calculation in a predictive model.

Why this answer

The team needs a derived field representing the number of days between admission and discharge. Date arithmetic is the transformation that subtracts one date from another to yield a duration. Aggregation summarizes groups of rows, normalization rescales values, and imputation fills missing data, none of which produce a per-patient length-of-stay field.

Exam trap

The trap here is confusing data transformation techniques and assuming that any manipulation of date fields qualifies as normalization or aggregation.

Practice this question →
61
Multi-Selecteasy

An organization is implementing a data lake to store raw data from various sources. Which THREE characteristics are typically associated with a data lake compared to a data warehouse?

Select 3 answers
A.Supports batch and real-time processing
B.Stores data in its native format
C.Schema-on-read approach
D.Supports only structured data
E.Requires data transformation before loading
AnswersA, B, C

A data lake ingests streams and files through the same storage layer, so it handles both batch loads and real-time processing. A data warehouse typically relies on scheduled ETL batches, making this a defining capability of the lake architecture.

Why this answer

A is correct because a data lake is designed to handle both batch and real-time/streaming ingestion and processing, unlike a traditional data warehouse that is primarily optimized for batch ETL workloads. B is correct because a data lake stores data in its native/raw format (e.g., JSON, Parquet, CSV, images, logs) without forcing an upfront conversion. C is correct because a data lake applies schema-on-read, meaning the schema is defined when the data is queried rather than when it is written.

D is incorrect because data lakes support structured, semi-structured, and unstructured data, not only structured data. E is incorrect because a data lake typically loads raw data as-is and defers transformation until read/query time, whereas a data warehouse usually requires transformation before loading.

Exam trap

CompTIA often tests the misconception that data lakes require data transformation before loading (schema-on-write), when in fact they use schema-on-read, allowing raw data storage without upfront transformation.

Practice this question →
62
Multi-Selectmedium

A data steward at a retail company is classifying data assets. The company wants to identify which data elements are considered structured data. Which two of the following are examples of structured data? (Choose two.)

Select 2 answers
A.A table of customer orders with columns OrderID, CustomerName, and OrderDate.
B.A collection of emails stored as plain text files.
C.A spreadsheet with rows for employees and columns for EmployeeID, Name, and Department.
D.A JSON document containing nested product details and customer reviews.
E.A video recording of a customer service call.
AnswersA, C

This is structured data because it is organized into a tabular format with predefined columns and data types. Each row represents a single order, and each column holds a specific attribute. The rigid schema makes it easy to query, sort, and analyze using SQL or other relational tools, which is the hallmark of structured data.

Why this answer

Structured data is organized into a predefined format, typically tables with rows and columns, making it easily searchable and analyzable. The customer orders table and the employee spreadsheet both fit this description. Emails, JSON documents, and video recordings lack the rigid schema and tabular organization required for structured data.

Exam trap

The trap here is assuming that any data with labels or tags is structured, but semi-structured formats like JSON still lack the fixed tabular schema that defines structured data.

Practice this question →
63
MCQeasy

A company needs to store raw, unprocessed data from IoT sensors for future machine learning experiments. The data is in various formats and schemas are not yet defined. Which storage solution is most appropriate?

A.Data lake
B.Data mart
C.Data warehouse
D.Operational database
AnswerA

A data lake stores raw data in native formats without requiring a predefined schema, so varied IoT sensor payloads can be landed as-is. Schema-on-read defers structure until analysis, satisfying the undefined-schema, future-machine-learning requirement that a warehouse or relational store cannot meet.

Why this answer

A data lake is the correct choice because it stores raw, unprocessed data in its native format (structured, semi-structured, or unstructured) without requiring a predefined schema. This aligns perfectly with the need to ingest IoT sensor data in various formats for future machine learning experiments, where schemas are not yet defined. Unlike data warehouses or data marts, a data lake supports schema-on-read, allowing the data to be transformed and queried later as needed.

Exam trap

CompTIA often tests the misconception that 'raw data' belongs in a data warehouse because it is 'data,' but the trap is that data warehouses require structured, processed data with a fixed schema, while a data lake is specifically designed for raw, schema-less data storage.

How to eliminate wrong answers

Option B is wrong because a data mart is a subset of a data warehouse designed for a specific business line or department, requiring pre-defined schemas and processed data, not raw unprocessed data. Option C is wrong because a data warehouse stores structured, cleaned, and transformed data optimized for business intelligence and reporting, not raw data in various formats. Option D is wrong because an operational database (e.g., OLTP system) is designed for real-time transaction processing with strict schemas and ACID compliance, not for storing large volumes of raw, schema-less IoT data for future analytics.

Practice this question →
64
Multi-Selectmedium

A data governance team is defining roles and responsibilities for data management. Which TWO of the following are common data governance roles? (Select TWO).

Select 2 answers
A.Data steward
B.Data owner
C.Data scientist
D.Database administrator
E.Data analyst
AnswersA, B

The data steward executes day-to-day governance: maintaining metadata, enforcing quality rules, resolving data issues and applying the owner's policies. This operational role satisfies the need for hands-on responsibility, bridging policy set by owners and the practical management of data assets.

Why this answer

Option A, Data steward, is correct because a data steward is a core data governance role responsible for day-to-day management of data assets, enforcing data policies, maintaining data quality, and resolving data issues within a defined domain. Option B, Data owner, is correct because the data owner is an accountable governance role, typically a senior business leader, who is responsible for the data's classification, access decisions, quality, and compliance with policies for a specific data domain. These two roles are explicitly defined in governance frameworks such as DAMA-DMBOK, which distinguishes accountable owners from custodial stewards.

Option C, Data scientist, is not a governance role but an analytics role focused on building models and deriving insights from data. Option D, Database administrator, is an operational/technical role managing database systems, not a governance role. Option E, Data analyst, is also an analytics role focused on querying and interpreting data rather than defining governance responsibilities.

Exam trap

DA0-002 often tests the distinction between governance roles and operational/analytical roles; candidates may incorrectly select data scientist or database administrator because they are familiar technical roles, but they are not governance-specific.

Practice this question →
65
MCQmedium

A company wants to share a dataset with external partners via an API. Which API type is typically used for web services and uses XML or JSON for messaging?

A.REST API
B.GraphQL API
C.SOAP API
D.WebSocket API
AnswerA

REST APIs use HTTP methods and URIs to expose resources, returning representations in XML or JSON as the stem requires. Their stateless, web-native design makes them the standard choice for partner-facing web service integration, satisfying both the external sharing constraint and the XML/JSON messaging requirement.

Why this answer

REST (Representational State Transfer) is an architectural style for web services that typically uses HTTP methods and supports XML or JSON for message payloads. It is the most common API type for sharing data over the web due to its simplicity, statelessness, and scalability. SOAP also uses XML but is heavier and less common for modern web APIs; GraphQL and WebSocket serve different purposes.

Exam trap

The trap is that SOAP also uses XML, so candidates may pick SOAP thinking it's the standard for web services, but the question emphasizes 'typically used for web services' and 'XML or JSON'—REST is the modern default.

How to eliminate wrong answers

Option B is wrong because GraphQL is a query language for APIs that allows clients to request specific data, but it is not typically described as using XML or JSON for messaging—it uses a single endpoint and a query language, often over HTTP with JSON responses. Option C is wrong because SOAP is a protocol that uses XML for messaging but is not the typical choice for modern web services due to its complexity and overhead. Option D is wrong because WebSocket provides full-duplex communication channels over a single TCP connection, not a request-response API style for sharing datasets.

Practice this question →
66
MCQeasy

Which of the following data types best describes a JSON file containing customer orders with varying fields per record?

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

JSON stores data as nested key-value pairs without a fixed schema, so each order record can carry different fields. That schema-on-read flexibility is the defining trait of semi-structured data, distinguishing it from rigidly tabular structured data and from unstructured raw text.

Why this answer

JSON (JavaScript Object Notation) is a text-based format that uses key-value pairs and nested objects/arrays, providing a flexible schema where each record can have different fields. This self-describing structure—where data carries its own metadata via keys—is the hallmark of semi-structured data. Unlike structured data, it doesn't require a rigid, predefined schema, but unlike unstructured data, it still has an organized, machine-readable format.

Therefore, a JSON file with varying fields per record is best classified as semi-structured data.

Exam trap

The trap here is confusing semi-structured data with unstructured data because both lack a fixed schema; candidates often overlook that JSON's self-describing key-value pairs provide enough structure to separate it from truly unstructured formats like images or free text.

How to eliminate wrong answers

Option A is wrong because unstructured data (e.g., images, audio, free text) lacks any predefined data model or consistent organization, whereas JSON has a clear hierarchical structure with keys and values. Option B is wrong because structured data (e.g., relational tables) adheres to a strict, fixed schema where every record has the same fields and data types, which contradicts the varying fields described. Option C is wrong because relational data is a subset of structured data stored in tables with rows and columns and relationships defined by foreign keys; JSON is not inherently relational and does not enforce such relationships.

Practice this question →
67
MCQeasy

Which of the following best describes a data mart?

A.A repository for raw, unprocessed data
B.An OLTP system for transaction processing
C.A subject-specific subset of a data warehouse
D.A tool for extract, transform, and load processes
AnswerC

A data mart is a subject-specific subset of a data warehouse, scoped to one department or business function. It inherits warehouse data but serves a narrower analytical audience, distinguishing it from the enterprise-wide warehouse itself.

Why this answer

A data mart is a subject-specific subset of a data warehouse, designed to serve the analytical needs of a particular department or business function (e.g., sales, finance, marketing). It contains a focused set of data extracted from the enterprise data warehouse or other sources, optimized for query and reporting by a specific user group. This aligns with the definition of a data mart as a smaller, more specialized version of a data warehouse.

Exam trap

The trap here is confusing data marts with data lakes or ETL tools, as all are related to data warehousing but serve different purposes; candidates might incorrectly choose 'raw, unprocessed data' (data lake) or 'ETL tool' due to familiarity with those terms.

How to eliminate wrong answers

Option A is wrong because a repository for raw, unprocessed data describes a data lake or staging area, not a data mart; data marts contain curated, transformed data for analysis. Option B is wrong because an OLTP system is designed for transactional processing (inserts, updates, deletes) and is not optimized for analytical queries, whereas a data mart is an analytical construct. Option D is wrong because ETL is a process or tool used to move and transform data, not a data mart itself; a data mart is the target repository, not the tool.

Practice this question →
68
MCQeasy

Which of the following is an example of semi-structured data?

A.A CSV file without header
B.An image file
C.A table in a relational database
D.A JSON file
AnswerD

Semi-structured data carries organisational tags or keys but lacks a rigid relational schema. A JSON file uses nested key-value pairs and arrays, fitting this definition, whereas tables and CSV files are structured and free text or images are unstructured.

Why this answer

Semi-structured data has tags or markers to separate data elements, like JSON or XML.

Practice this question →
69
MCQmedium

A company uses a data warehouse for reporting. They need to extract data from multiple sources, load it into a staging area, and then transform it before moving to the warehouse. This process is known as:

A.ELT
B.ETL
C.Data replication
D.Data ingestion
AnswerB

ETL extracts from multiple sources, loads into a staging area, then transforms before loading into the warehouse, matching the stem's stated sequence exactly. ELT would transform after loading, so it does not fit the described staging-then-transform order.

Why this answer

The process described—extracting data from multiple sources, loading it into a staging area, and then transforming it before moving to the warehouse—is the classic definition of ETL (Extract, Transform, Load). In ETL, transformation occurs after extraction but before loading into the target system, which is exactly what the staging area is used for. This contrasts with ELT, where transformation happens after loading into the warehouse.

Exam trap

The trap here is that candidates confuse the order of operations in ETL versus ELT, assuming that because modern cloud warehouses support ELT, the described staging-area process must be ELT, when in fact the staging area is a hallmark of traditional ETL.

How to eliminate wrong answers

Option A is wrong because ELT (Extract, Load, Transform) loads raw data into the target system first and transforms it later, which is the opposite of the described sequence where transformation occurs before moving to the warehouse. Option C is wrong because data replication refers to copying data from one system to another for redundancy or availability, not a multi-stage pipeline with transformation. Option D is wrong because data ingestion is a broad term covering the initial import of data into a system, but it does not specifically include the staging and transformation steps described in the question.

Practice this question →
70
MCQmedium

A healthcare organization maintains a database of patient records. The database has a table 'patients' with columns: patient_id (primary key), first_name, last_name, date_of_birth, gender, and last_visit_date. A data analyst is tasked with creating a report that lists all patients who have not visited in the last two years. The analyst writes a query: SELECT * FROM patients WHERE last_visit_date < DATEADD(year, -2, GETDATE()); However, the query returns zero rows, even though the analyst knows there are patients who have not visited for over two years. Upon inspection, the analyst discovers that the last_visit_date column contains NULL values for patients who have never visited. Which modification to the query should the analyst make to include patients with NULL last_visit_date?

A.Remove the WHERE clause entirely.
B.Add OR last_visit_date IS NULL to the WHERE clause.
C.Use COALESCE(last_visit_date, '1900-01-01') in the WHERE clause.
D.Add AND last_visit_date IS NOT NULL to the WHERE clause.
AnswerB

SQL's three-valued logic evaluates NULL comparisons as UNKNOWN, so last_visit_date < DATEADD(...) never matches NULL rows. Adding OR last_visit_date IS NULL explicitly includes patients who have never visited, satisfying the report's requirement to list all inactive patients.

Why this answer

The original query uses a WHERE clause that compares last_visit_date to a computed date, but NULL comparisons in SQL always yield UNKNOWN, so rows with NULL last_visit_date are excluded. Adding OR last_visit_date IS NULL explicitly includes those rows, ensuring patients who have never visited are listed in the report.

Exam trap

The trap here is that candidates often forget that NULL comparisons in SQL do not return TRUE, leading them to incorrectly think the original query already handles NULLs, and they may choose Option C (COALESCE) as a workaround instead of the simpler and correct IS NULL check.

How to eliminate wrong answers

Option A is wrong because removing the WHERE clause entirely would return all rows, including those with recent visits, which fails to filter for patients who have not visited in two years. Option C is wrong because COALESCE(last_visit_date, '1900-01-01') would replace NULL with a very old date, making the comparison work, but it is not the standard or most efficient approach; the correct method is to use IS NULL to handle NULLs directly. Option D is wrong because AND last_visit_date IS NOT NULL would explicitly exclude rows with NULL last_visit_date, which is the opposite of what is needed.

Practice this question →
71
Multi-Selecteasy

Which TWO of the following are characteristics of a data lake?

Select 2 answers
A.Retains raw data in native format
B.Optimized for OLTP
C.Stores only structured data
D.Enforces ACID transactions
E.Uses schema-on-read
AnswersA, E

Data lakes store data as-is without transformation.

Why this answer

A data lake retains raw data in its native format, meaning data is ingested without transformation or schema enforcement. This allows storage of structured, semi-structured, and unstructured data as-is, preserving fidelity for future analytics. Unlike a data warehouse, a data lake does not require upfront schema definition, enabling flexible exploration and machine learning workloads.

Exam trap

The trap here is that candidates confuse data lakes with data warehouses, assuming all enterprise data stores enforce ACID and schema-on-write, when in fact data lakes prioritize raw storage and schema flexibility.

Practice this question →
72
Multi-Selectmedium

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

Select 2 answers
A.Has a defined schema
B.Requires NoSQL databases for storage
C.Often contains natural language text
D.Cannot be queried using SQL
E.Organized in rows and columns
AnswersA, E

Schema defines structure.

Why this answer

Structured data is defined by having a predefined schema, which specifies the data types, constraints, and relationships for each field. This schema ensures consistency and allows for efficient querying and validation. Option A is correct because a defined schema is a fundamental characteristic of structured data, as seen in relational database tables where each column has a specific data type and constraints.

Exam trap

The trap here is that candidates often confuse structured data with semi-structured data (e.g., JSON or XML) and incorrectly assume that structured data cannot be queried with SQL or that it requires NoSQL databases.

Practice this question →
73
MCQhard

A financial institution wants to analyze transaction networks to detect fraud rings. Which database type is best suited for this analysis?

A.Wide-column store
B.Graph database
C.Key-value store
D.Document store
AnswerB

Graph databases store entities as nodes and relationships as edges, so traversing transaction links between accounts is a native pointer hop rather than an expensive join. This directly satisfies the fraud-ring detection requirement, where identifying circular money flows depends on multi-hop relationship traversal.

Why this answer

A graph database is designed to store and traverse relationships between entities, making it ideal for analyzing transaction networks where connections between accounts, merchants, and transactions reveal fraud rings. Its native graph model (nodes and edges) allows efficient pattern matching and pathfinding queries, such as detecting circular transactions or shared attributes, which are common in fraud detection.

Exam trap

CompTIA often tests the misconception that any NoSQL database can handle relationship-heavy workloads, but the trap here is that only graph databases are purpose-built for deep relationship traversal and pattern matching, while other NoSQL types sacrifice relationship performance for scalability or flexibility.

How to eliminate wrong answers

Option A is wrong because wide-column stores (e.g., Cassandra, HBase) are optimized for high-volume, low-latency reads/writes on sparse data with flexible schemas, but they lack native relationship traversal capabilities, making multi-hop queries across transaction networks slow and complex. Option C is wrong because key-value stores (e.g., Redis, DynamoDB) provide fast lookups by primary key but cannot efficiently model or query the interconnected relationships between transactions and entities, requiring application-level joins that degrade performance. Option D is wrong because document stores (e.g., MongoDB, Couchbase) store semi-structured data as JSON-like documents and support indexing, but they do not have built-in graph traversal algorithms, so analyzing fraud rings would require expensive recursive queries or external graph processing.

Practice this question →
74
MCQhard

An analyst is profiling a table of laboratory test results. The ResultValue column stores numeric readings, but a subset of rows contains the literal text "N/A" in that column, and a separate ResultUnit column records units such as mg/dL or mmol/L. The analyst must compare average ResultValue across two hospital sites. Which data issue most directly prevents a valid comparison, and what is the appropriate first step?

A.The average must be computed as a median because laboratory results are always skewed, so the analyst should replace ResultValue with a rank-based statistic
B.The presence of "N/A" text in a numeric column makes the column string-typed, so the analyst must drop the entire ResultValue column before comparing sites
C.The ResultUnit column contains multiple unit systems, so the analyst must convert all readings to a single unit before averaging
D.The "N/A" text forces the column to be interpreted as text, so numeric averages silently ignore or misorder values, and the analyst must convert or exclude those values before averaging
AnswerD

When a numeric column contains text sentinels, many tools coerce the whole column to a string type, so AVG either fails or sorts lexicographically, producing meaningless results. The analyst must identify the non-numeric rows, decide whether to convert them to nulls or exclude them, and then compute the average on a clean numeric type. Only then is the two-site comparison trustworthy.

Why this answer

A numeric column polluted with text values like "N/A" typically gets coerced to a string type, which breaks arithmetic aggregation and can cause silent misordering or failed averages. The analyst must first isolate the non-numeric rows and convert or exclude them so the column is genuinely numeric, then compute the average for each site. Only after that remediation does the two-site comparison become valid.

Exam trap

The trap here is assuming an average still works on a column that contains text, when the presence of a non-numeric value can change the column's type and silently corrupt the aggregation.

Practice this question →
75
MCQhard

A data analyst is troubleshooting a report that shows unusually high sales for a specific product. Upon investigation, the analyst finds that the product was returned by several customers, but the returns were recorded in a separate system and not reflected in the sales data. Which data integration concept was likely missing?

A.ETL (Extract, Transform, Load)
B.Data reconciliation
C.Data profiling
D.Data governance
AnswerB

Sales figures were never adjusted for returns held in a separate system, so the two datasets disagreed. Data reconciliation compares and aligns records across sources to detect and correct such mismatches, which would have surfaced the unreflected returns before the report ran.

Why this answer

The core issue is that the sales data and returns data are inconsistent because they were not cross-verified. Data reconciliation is the process of comparing datasets to ensure they are in agreement and identifying discrepancies, such as returns not being reflected in sales figures. Without reconciliation, the analyst would not detect that the high sales number is inflated by unrecorded returns.

Exam trap

The trap here is that candidates confuse the data movement process (ETL) with the data validation process (reconciliation), assuming that simply extracting and loading data will automatically ensure consistency between separate systems.

How to eliminate wrong answers

Option A is wrong because ETL (Extract, Transform, Load) is a process for moving and transforming data from source to target systems, but it does not inherently include a step to compare or verify data consistency between separate systems; the missing concept here is not about data movement but about data agreement. Option C is wrong because data profiling focuses on examining data quality, structure, and content (e.g., nulls, duplicates, data types), not on cross-system consistency checks; the problem is not about the quality of the sales data itself but about its mismatch with returns data. Option D is wrong because data governance refers to the overall management of data availability, usability, integrity, and security through policies and standards, not a specific technical process for reconciling discrepancies between two systems.

Practice this question →
Page 1 of 3 · 200 questions totalNext →

Ready to test yourself?

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

Start 20-question session