Data Management Fundamentals Free Sample Questions

The DAMA-DMBOK advocates for data stewards to be sourced from and embedded within business units. This model ensures they have the subject matter expertise and are close to the data's creation and use, which is essential for defining business rules, assessing quality, and making authoritative decisions. Placing them in IT centralizes technical control but divorces them from business context.

A foreign key constraint establishes a link between two tables, enforcing referential integrity. In this case, making the OrderID in the Order_Items table a foreign key that references the OrderID primary key in the Orders table ensures that every record in Order_Items must have a valid, existing OrderID in the Orders table.

While a 3NF model is excellent for transactional systems (OLTP) due to its focus on data integrity and eliminating redundancy, it often requires many complex joins for reporting, which slows down queries. A dimensional model is specifically designed for analytical systems (OLAP) by organizing data into facts and dimensions. This denormalized structure simplifies queries (fewer joins) and is optimized for the fast read performance required by business analysts.

The data quality dimension of Uniqueness ensures that there is only one representation of a single real-world entity in a dataset. The presence of duplicate entries for the same customer, even with minor variations, is a direct violation of this dimension. Completeness relates to missing data, and timeliness relates to data being up-to-date.

Data Mesh is a decentralized sociotechnical approach that shifts ownership of data to domain-specific teams. Its core principles are domain-oriented decentralized data ownership and architecture, data as a product, self-serve data infrastructure as a platform, and federated computational governance. The scenario directly describes the 'data as a product' principle.

Accountability is a cornerstone of data ethics and data protection regulations like GDPR. It requires organizations to take responsibility for their data handling practices and to be able to demonstrate compliance with data protection principles. This includes having appropriate measures and records in place.

The ETL (Extract, Transform, Load) pattern involves extracting data from source systems, performing transformations in a separate staging area or engine, and then loading the already-transformed data into the target system. This is ideal for traditional data warehousing where complex business logic and data cleansing must be applied before the data is loaded into the structured target schema. ELT, by contrast, loads raw data into the target and uses the target system's power to perform transformations.

A Data Custodian is responsible for the technical environment and management of data assets. Their role is operational and focuses on tasks like implementing security controls, performing backups and recovery, and managing the database infrastructure. Defining business rules and approving access are typically responsibilities of a Data Steward or Data Owner.

A multi-model NoSQL database is designed to handle various data types and structures efficiently. For instance, a document database (a type of NoSQL) can store structured and semi-structured data within a flexible JSON/BSON format and can link to or store binary files (unstructured data). While an RDBMS can use BLOBs, it is not optimized for querying or managing the content of semi-structured or unstructured data, making a NoSQL approach more suitable for this use case.