Courseiva

CCNA Data Concepts and Environments Questions

75 of 186 questions · Page 1/3 · Data Concepts and Environments · Answers revealed

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, transforms it, and loads it into the warehouse, suitable for structured integration.

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.

2
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 links tables by referencing a primary key in another table, maintaining referential integrity.

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.

3
MCQhard

A healthcare organization is subject to strict data privacy regulations requiring the classification of all data assets. The data governance team has identified three data sensitivity levels: Public, Internal, and Restricted. They have a new data pipeline importing patient health records from multiple clinics. The records include patient names, diagnoses, treatment codes, and insurance information. The team must ensure that the classification is applied correctly and that restricted data (e.g., diagnoses) is not exposed to unauthorized personnel. However, the pipeline uses automated tagging based on metadata rules, and some fields are misclassified. What is the most effective immediate action to improve classification accuracy?

A.Encrypt all data at rest and in transit regardless of classification.
B.Require manual review and reclassification of all incoming records.
C.Expand the metadata rule set to include more keywords and patterns.
D.Implement data loss prevention (DLP) tools that inspect content and enforce classification rules.
AnswerD

Correct: DLP can reclassify based on actual content, improving accuracy.

Why this answer

Implementing DLP tools with content inspection can automatically detect sensitive patterns (e.g., diagnosis codes) and enforce correct classification, directly addressing misclassification from incomplete metadata rules. Option A (encrypting all data) is a security measure but does not fix classification accuracy. Option B (manual review) is not scalable for a pipeline.

Option C (expanding metadata rules) may help but is less effective since metadata can still miss patterns that DLP content inspection can catch.

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

Normalization eliminates duplicate data.

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.

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

INNER JOIN returns only matching rows, which are customers with orders.

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.

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 purchase history to customers, maintaining relationships.

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.

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.

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

Income should be quantitative, but text labels are qualitative.

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.

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

Key-value stores provide high-performance lookups by key.

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.

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 unstructured data such as text, images, and emojis without a fixed schema.

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.

11
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.

12
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

Document databases support secondary indexes on any field, which speeds up queries.

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.

13
Multi-Selecteasy

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

Select 2 answers
A.Stored in rows and columns
B.Lacks a fixed schema
C.Has a predefined data model
D.Uses tags to define elements
E.Consists of free-form text
AnswersA, C

Tabular storage is a hallmark of structured data like relational databases.

Why this answer

Structured data is organized into rows and columns, typically within relational databases or spreadsheets, where each column represents a specific attribute and each row represents a record. This tabular format enables efficient querying, sorting, and indexing using languages like SQL. The rigid row-and-column structure ensures data consistency and supports ACID (Atomicity, Consistency, Isolation, Durability) properties.

Exam trap

The trap here is that candidates often confuse semi-structured data (which uses tags or labels) with structured data, or they incorrectly assume structured data can lack a schema, when in fact a predefined schema is its defining requirement.

14
MCQeasy

Which of the following is a characteristic of a NoSQL document database like MongoDB?

A.Schema-flexible, JSON-like documents
B.Data stored in tables with rows and columns
C.Strict schema enforcement
D.Support for ACID transactions across multiple documents
AnswerA

Document databases store data in flexible documents.

Why this answer

Document databases store data in flexible, JSON-like documents, allowing schema variability.

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 during the integration process before loading into the target.

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.

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.

17
MCQmedium

A healthcare analytics team is building a dashboard to monitor patient vitals. They receive data from two sources: Source 1 provides 'heart rate' as an integer (beats per minute), and Source 2 provides 'blood pressure' as a ratio (systolic/diastolic, e.g., 120/80). The team wants to create a combined metric called 'cardiac stress index' that uses both heart rate and systolic blood pressure. However, they notice that heart rate data occasionally contains negative values due to sensor errors. The data governance policy requires that all data be valid and meaningful. Which action best addresses the data quality issue while preserving the data types?

A.Convert heart rate to absolute values (remove the negative sign)
B.Keep negative values but set them to NULL to indicate missing data
C.Change heart rate from integer to categorical (e.g., low, normal, high) to avoid negative issues
D.Remove all records with negative heart rate values as they are invalid
AnswerD

Negative heart rates are not physiologically possible, so deletion is appropriate for data quality.

Why this answer

Negative heart rate values are physiologically impossible and violate the data governance policy requiring valid and meaningful data. Removing these records ensures the dashboard only contains accurate, actionable data without altering the original integer data type of heart rate, preserving its numerical integrity for the 'cardiac stress index' calculation.

Exam trap

The trap here is that candidates may choose Option A (converting to absolute values) thinking it 'fixes' the data, but this introduces false data and violates data validity, whereas the correct approach is to remove invalid records to maintain data integrity.

How to eliminate wrong answers

Option A is wrong because converting negative heart rates to absolute values introduces false data, masking sensor errors and potentially skewing the cardiac stress index with artificially inflated readings. Option B is wrong because setting negative values to NULL retains invalid records in the dataset, which can cause calculation errors or missing data handling issues in the dashboard without addressing the root cause of sensor errors. Option C is wrong because changing heart rate from integer to categorical loses granularity and prevents the precise numerical computation required for the cardiac stress index, violating the requirement to preserve data types.

18
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

Correct. Category is a qualitative variable as it describes a product attribute.

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.

19
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

Data lakes store raw, unprocessed data, suitable for IoT sensor data.

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.

20
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 allow flexible schemas, perfect for variable attributes.

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.

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 ensures foreign key values match primary key values.

Why this answer

Referential integrity, enforced via a foreign key constraint, ensures that values in the foreign key column (OrderID in OrderDetails) match values in the primary key column of the referenced table (Orders).

22
Multi-Selecthard

An organization uses a data warehouse for analytics. Which two characteristics are typical of a data warehouse compared to a data lake? (Select TWO.)

Select 2 answers
A.Optimized for complex queries and reporting
B.Typically uses ELT process
C.Stores raw data in native format
D.Uses schema-on-write
E.Supports all data types including unstructured
AnswersA, D

Data warehouses are designed for analytics.

Why this answer

A data warehouse is optimized for complex queries and reporting (A) because it uses schema-on-write (D), meaning data is transformed and structured before loading to support fast analytical queries. In contrast, a data lake uses schema-on-read and stores raw data. ELT is typical of data lakes, not data warehouses.

Exam trap

The trap here is that candidates often confuse the ETL/ELT processes, incorrectly associating ELT with data warehouses, or assume data warehouses can handle all data types like unstructured data, which is a key differentiator of data lakes.

23
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

GROUP BY groups rows and aggregation functions compute counts.

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.

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

REST API provides structured data via HTTP.

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.

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 before loading.

Why this answer

ETL (Extract, Transform, Load) transforms data before loading it into the warehouse, which is common for traditional data warehousing.

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

Data lakes store raw data in native format, suitable for large-scale, diverse data.

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.

27
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.

28
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 follows a predefined schema, such as tables in a relational database.

Why this answer

Structured data is organized into predefined schemas, such as tables with rows and columns, which enforce a consistent data format and relationships. This rigid structure allows structured data to be easily queried using SQL, as SQL is designed to operate on relational database management systems (RDBMS) that rely on these schemas. Option C is correct because a predefined schema is a defining characteristic of structured data, enabling efficient storage, retrieval, and integrity constraints.

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.

29
Matchingmedium

Match each data visualization type to its best use case.

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

Concepts
Matches

Compare quantities across categories

Show relationship between two numeric variables

Display distribution of a single continuous variable

Show magnitude of values across two dimensions

Summarize distribution and identify outliers

Why these pairings

Correct matches: Bar chart compares categories, Line chart shows trends over time, Pie chart shows proportions. Common confusions: swapping time trend with bar chart or proportion with category comparison.

30
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

Correct. Secondary data is collected by another entity and reused.

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.

31
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, then transforms in the warehouse.

Why this answer

ELT (Extract, Load, Transform) loads raw data first, then transforms it within the warehouse, which is suitable for modern cloud warehouses.

32
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.

33
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.

34
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

Correct: fact table linked to dimension tables.

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.

35
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

Correct. SQL tables have rows and columns with defined data types.

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.

36
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

MDM requires governance policies.

Why this answer

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

37
Drag & Dropmedium

Drag and drop the steps to create a data visualization dashboard in the correct order.

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

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

Why this order

Dashboard creation starts with planning, then chart selection, layout design, building, and testing.

38
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.

39
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 is the constraint that maintains consistency between related tables.

Why this answer

Referential integrity ensures that foreign key values match primary key values in the referenced table.

40
MCQhard

Refer to the exhibit. Based on the data profiling results, what is a likely data quality issue?

A.Completeness
B.Accuracy
C.Validity
D.Consistency
AnswerC

Correct. Values like 0 and 150 violate reasonable constraints.

Why this answer

The min of 0 and max of 150 are biologically implausible for age. A 0-year-old or 150-year-old customer likely indicates invalid data, affecting validity.

41
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

A data steward ensures data quality, standards, and metadata management for a specific domain.

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.

42
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 continuously send data, making them a streaming source.

Why this answer

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

43
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

Conversion changes data type, e.g., string to integer.

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.

44
MCQmedium

A researcher wants to study the effect of a new drug. She collects data directly from clinical trial participants. Later, she compares her findings with historical data from medical journals. Which contrast best describes her data sources?

A.Internal vs. External
B.Quantitative vs. Qualitative
C.Structured vs. Unstructured
D.Primary vs. Secondary
AnswerD

Primary data is collected firsthand; secondary data is obtained from existing sources.

Why this answer

The researcher is directly collecting data from clinical trial participants (primary data) and then comparing it with historical data from medical journals (secondary data). Primary data is original data collected firsthand for a specific purpose, while secondary data is pre-existing data collected by others for different purposes. This contrast directly maps to the primary vs. secondary data classification in data management.

Exam trap

The trap here is that candidates confuse 'internal vs. external' (Option A) with 'primary vs. secondary' because both involve a contrast between data from the researcher's own work versus outside sources, but the DA0-001 exam specifically tests the distinction based on whether the data was collected firsthand (primary) or reused from existing records (secondary).

How to eliminate wrong answers

Option A is wrong because internal vs. external refers to data originating within or outside an organization, not the method of collection; the clinical trial data is internal to the study but the historical data is external, but the core contrast here is about data origin (firsthand vs. reused), not organizational boundary. Option B is wrong because quantitative vs. qualitative describes data types (numerical vs. categorical/textual), not the source of data; both the clinical trial data and historical journal data could be quantitative or qualitative. Option C is wrong because structured vs. unstructured refers to data format (e.g., tables vs. free text), not the source; both data sources could be structured (e.g., trial results in a database) or unstructured (e.g., narrative journal articles).

45
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 masking masks data on-the-fly based on user roles, perfect for this 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.

46
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 calculated from other attributes, making it derived.

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.

47
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 is a common semi-structured format with tags and nested elements.

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.

48
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 ensures a transaction is completed fully or not at all.

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.

49
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 categorizes data by sensitivity and outlines handling rules.

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.

50
MCQhard

A large financial institution is implementing a data governance framework to comply with new regulations requiring strict control over sensitive customer data. The data governance committee has identified several domains, including customer master data, transaction data, and risk assessment data. They need to decide on a master data management (MDM) approach that ensures a single, authoritative source of customer information across all systems. However, the current environment has multiple legacy systems with conflicting customer records. The committee is concerned about downtime and business disruption during the transition. Which MDM approach best balances data consistency with minimal operational impact?

A.Registry MDM, which creates a virtual view by linking records without moving data.
B.Centralized MDM, which replaces all systems with one central master system.
C.Consolidation MDM, which merges all customer data into a single physical hub.
D.Coexistence MDM, which maintains multiple masters with synchronization.
AnswerA

Correct: Registry avoids disruption by leaving data in place and creating a unified index.

Why this answer

Registry MDM is correct because it creates a virtual, unified view of customer data by linking records from multiple legacy systems via a registry index, without physically moving or consolidating data. This approach ensures a single authoritative source of customer information while avoiding downtime and business disruption, as the underlying systems remain unchanged and operational during the transition.

Exam trap

The trap here is that candidates often confuse Registry MDM with Consolidation MDM, assuming that a single authoritative source requires physical data movement, when in fact a virtual registry can achieve the same goal with minimal operational impact.

How to eliminate wrong answers

Option B is wrong because Centralized MDM requires replacing all existing systems with a single central master system, which would cause significant downtime and business disruption due to the need for data migration and system decommissioning. Option C is wrong because Consolidation MDM merges all customer data into a single physical hub, which still requires moving data from legacy systems and can lead to operational interruptions during the consolidation process. Option D is wrong because Coexistence MDM maintains multiple masters with synchronization, which does not ensure a single authoritative source of customer information and can lead to data conflicts and inconsistency across systems.

51
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

Relational tables with SQL support are excellent for structured data and time-series analysis.

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.

52
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

Correct: Data lakes store raw data in native format and support schema-on-read for both structured and unstructured.

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.

53
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

Correct definition of structured data.

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.

54
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

Correct: continuous data from clickstreams.

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.

55
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

The policy restricts which objects can be accessed, controlling access based on prefix.

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.

56
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

Data quality assesses the accuracy, completeness, and reliability of data. Manual entry from PDF invoices introduces potential errors, directly impacting data quality. Thus, this is the correct concept being addressed.

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.

57
MCQmedium

The exhibit shows a JSON schema for a dataset. Which statement correctly describes the data types represented?

A.All fields are qualitative
B.age and income are continuous; customer_id and education are discrete
C.customer_id and age are discrete quantitative; income is continuous quantitative; education is qualitative
D.All fields are quantitative
AnswerA

Correct. All fields are qualitative: customer_id (nominal), education (ordinal), age and income (treated as ordinal categories).

Why this answer

All fields in the dataset are qualitative (categorical or nominal). customer_id is a unique identifier (nominal), education is a categorical variable, age is often grouped into categories (ordinal), and income is typically treated as ordinal when bucketed into ranges. Despite being stored as numbers, age and income are not used for arithmetic in typical data analysis, making them qualitative.

Exam trap

The trap is that candidates assume numeric fields like age and income are quantitative, but in this context they are treated as qualitative categories. Customer_id is a nominal identifier, not a number to be averaged.

How to eliminate wrong answers

Option A is wrong because it claims all fields are qualitative, but age, income, and customer_id are quantitative (numeric) fields, not categorical. Option B is wrong because it states age and income are continuous, but age is discrete (countable integer values) and customer_id is discrete quantitative, not qualitative; it also misclassifies education as discrete instead of qualitative. Option D is wrong because it claims all fields are quantitative, but education is a string field representing categorical data, which is qualitative.

58
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

Correct: Data lakes handle both processing modes.

Why this answer

Data lakes are designed to ingest and process data in both batch and real-time streaming modes, unlike data warehouses which primarily handle batch ETL workloads. This flexibility is enabled by technologies like Apache Kafka for streaming and Apache Spark for batch processing, allowing the data lake to support diverse ingestion patterns without pre-schematization.

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.

59
Multi-Selectmedium

A company needs to store data that is highly interconnected, such as social network relationships. Which two database types are best suited for this? (Select TWO.)

Select 2 answers
A.Relational database
B.Wide-column store (e.g., Cassandra)
C.Document store (e.g., MongoDB)
D.Graph database (e.g., Neo4j)
E.Key-value store (e.g., Redis)
AnswersC, D

Document stores can embed related data and are flexible for interconnected data.

Why this answer

Graph databases excel at storing relationships, and NoSQL databases support flexible schemas for interconnected data.

60
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 its native format and supports schema-on-read, making it ideal for storing unstructured and semi-structured data for future analysis.

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.

61
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

Data steward manages data quality and standards.

Why this answer

Data owner and data steward are standard roles in data governance, responsible for data ownership and stewardship respectively.

62
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 JSON/XML and are widely used for web services.

Why this answer

REST APIs commonly use JSON or XML for messaging, making them a standard choice for data sharing over the web.

63
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 uses tags/elements to organize data but allows flexibility, making it semi-structured.

Why this answer

JSON is a semi-structured data format because it allows flexible schema where fields can vary between records.

64
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

Data marts are subsets of data warehouses.

Why this answer

A data mart is a subject-specific subset of a data warehouse, focused on a particular department or function.

65
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

JSON uses key-value pairs with flexible schema, typical of semi-structured data.

Why this answer

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

66
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, transforms in a staging area, then loads into warehouse.

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.

67
Multi-Selecthard

Which THREE characteristics describe unstructured data? (Select three.)

Select 3 answers
A.Contains text, images, audio, video
B.Easily processed by standard SQL
C.Organised in rows and columns
D.Requires schema-on-read
E.Often stored in data lakes
AnswersA, D, E

Correct. Unstructured data includes multimedia and free text.

Why this answer

Unstructured data lacks a predefined data model and is typically composed of non-tabular formats such as text, images, audio, and video. Unlike structured data, it cannot be directly stored in relational databases without transformation. This characteristic is fundamental to distinguishing unstructured data from structured or semi-structured types.

Exam trap

The trap here is that candidates may confuse 'unstructured' with 'semi-structured' (e.g., JSON or XML) and incorrectly assume that SQL can process all non-tabular data, or they may forget that schema-on-read is a defining trait of unstructured data in modern big data architectures.

68
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

Includes NULLs in the result.

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.

69
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.

70
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.

71
MCQmedium

Refer to the exhibit. Which data concept does this exhibit best represent?

A.Entity relationship diagram
B.JSON schema
C.Data quality rule
D.Data dictionary
AnswerB

The exhibit is a JSON schema that validates the structure of JSON data.

Why this answer

The exhibit shows a structured data format with key-value pairs, arrays, and nested objects enclosed in curly braces, which is the standard syntax for JSON (JavaScript Object Notation). A JSON schema defines the structure, data types, and validation rules for JSON data, making it the best fit for the exhibit. The presence of fields like "name", "age", and "address" with specific types (e.g., string, integer) confirms this is a schema definition, not a generic data representation.

Exam trap

CompTIA often tests the distinction between a JSON schema (a structural definition with type constraints) and a raw JSON object (just data), leading candidates to mistake the schema for a simple data dictionary or ERD.

How to eliminate wrong answers

Option A is wrong because an entity relationship diagram (ERD) uses graphical symbols like rectangles and diamonds to represent entities and their relationships, not structured text with curly braces and key-value pairs. Option C is wrong because a data quality rule defines constraints like uniqueness or completeness (e.g., 'age must be > 0'), but the exhibit shows a structural blueprint with data types, not validation rules. Option D is wrong because a data dictionary is a tabular or textual catalog of data elements with definitions, not a machine-readable schema with nested objects and arrays.

72
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 excel at traversing relationships, perfect for network analysis.

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.

73
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

Reconciliation ensures data matches across sources.

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.

74
MCQmedium

A business needs to store large volumes of raw data in its native format for future analytics. Which storage architecture is most appropriate?

A.Relational database
B.Data lake
C.Operational data store
D.Data warehouse
AnswerB

Data lakes store raw data in its native format without transformation.

Why this answer

A data lake is designed to store large volumes of raw data in its native format (structured, semi-structured, or unstructured) without requiring a predefined schema. This makes it ideal for future analytics where the data schema may not yet be known, as it supports schema-on-read rather than schema-on-write.

Exam trap

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

How to eliminate wrong answers

Option A is wrong because a relational database enforces a strict schema-on-write and is optimized for transactional processing (OLTP), not for storing raw, unprocessed data at scale. Option C is wrong because an operational data store (ODS) is used for integrating data from multiple operational systems for near-real-time reporting, not for storing raw data in native format for future analytics. Option D is wrong because a data warehouse stores cleansed, transformed, and structured data optimized for query performance and business intelligence, not raw data in its native format.

75
MCQeasy

A market research firm collects survey responses where customers rate satisfaction on a scale of 'Very Unsatisfied', 'Unsatisfied', 'Neutral', 'Satisfied', 'Very Satisfied'. What type of data is being collected?

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

The satisfaction scale has a clear order but unequal intervals, fitting ordinal data definition.

Why this answer

The data is ordinal because the satisfaction levels have a clear, ordered ranking from 'Very Unsatisfied' to 'Very Satisfied', but the intervals between categories are not necessarily equal. This type of categorical data preserves the order without assuming a consistent numerical difference between each level.

Exam trap

The trap here is that candidates mistakenly treat ordered categorical data as interval data because they assume the numeric labels (e.g., 1 to 5) imply equal spacing, but the exam expects you to recognize that the underlying measurement scale lacks guaranteed equal intervals.

How to eliminate wrong answers

Option A is wrong because interval data requires equal, measurable intervals between values (e.g., temperature in Celsius), but the satisfaction scale does not guarantee equal psychological distance between categories. Option C is wrong because ratio data requires a true, meaningful zero point (e.g., income, height), and 'Very Unsatisfied' does not represent an absolute absence of satisfaction. Option D is wrong because nominal data is unordered categorical data (e.g., colors, gender), but the satisfaction scale has a natural order that must be preserved.

Page 1 of 3 · 186 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Data Concepts and Environments questions.