CDMP Practice Test

Certified Data Management Professional (CDMP)

CDMP overview

  • 200 practice questions
  • 32 flashcards
  • 8 study guide topics
  • 37 key terms

What you'll study

  • Data Management Fundamentals (DMF)
  • Data Modeling and Design
  • Metadata
  • Data Quality
  • Data Governance
  • Data Warehousing & Business Intelligence
  • Reference and Master Data Management
  • Data Integration and Interoperability

The Certified Data Management Professional (CDMP®) is a data management certification program run by DAMA International®, a not-for-profit association that describes itself as the certifying body for the CDMP®. The credential is built around three progressive levels - Associate, Practitioner and Master - which DAMA states reflect knowledge of data management practices, experience applying them, and professional development goals, and which are "progressive in depth-not tied to job titles or organizational rank." Associate is positioned for students and early-career professionals building a foundation; Practitioner for people actively working in areas such as data governance, data quality, metadata, architecture, modeling or stewardship; and Master for experienced professionals who lead or significantly influence data management capabilities in their organizations. Assessment is exam-based. Every level requires the Data Management Fundamentals (DMF) exam, and Practitioner and Master additionally require two specialist exams chosen from seven subject areas: Data Modeling and Design, Metadata, Data Quality, Data Governance, Data Warehousing & Business Intelligence, Reference and Master Data Management, and Data Integration and Interoperability. DAMA states that the exams are aligned with the DAMA DMBOK®. Preparation therefore means studying the DMBOK subject areas, choosing specialist exams that match your role, and - for Master - documenting at least ten years of relevant experience, since DAMA requires a CV submission for review as part of that process. Certification is maintained annually through Continuing Professional Development (CPD) and a renewal fee. This page is independent study material and is not affiliated with or endorsed by DAMA International®.

Common mistakes

Treating the DAMA-DMBOK 'wheel' as a list of eleven independent functions and answering questions as if each function operates in isolation, rather than recognizing that governance, metadata, and data quality are presented as cross-cutting enablers that touch every other function.

Candidates skim the framework diagram once, memorize the eleven function names, and then study each chapter separately. Exam items frequently describe a scenario where, for example, a metadata repository is the mechanism that makes data quality monitoring possible, and the candidate must identify the relationship rather than a single function.

What to do instead

Redraw the DMBOK wheel from memory, then for each function write one sentence on how it depends on governance, metadata, and data quality. Practice scenario questions by naming both the primary function and the enabling function before choosing an answer.

Confusing data modeling levels by naming a physical model when the scenario describes entities and relationships with no DBMS-specific detail, or selecting 'logical' for a diagram that already shows indexes, data types, and tablespaces.

The three-level convention (conceptual/logical/physical) is stated simply in study material, so candidates memorize the labels but never practice classifying real descriptions. Exam stems often include one detail (a primary key, a data type, a denormalization) that is the deciding clue.

What to do instead

Build a decision rule: conceptual = business terms and scope only; logical = attributes, keys, relationships, fully normalized, DBMS-independent; physical = tables, columns, data types, indexes, partitioning, denormalization for performance. Scan each stem for DBMS-specific nouns before answering.

Answering metadata questions as if metadata means only technical metadata, ignoring business metadata and operational metadata when the scenario is about glossary terms, data stewards, or job run statistics.

Candidates with engineering backgrounds default to 'metadata = column definitions and schemas'. The exam tests the three-type taxonomy and expects the candidate to classify a described artifact correctly.

What to do instead

Memorize the three categories with examples: business (glossary, definitions, ownership), technical (schema, lineage, models), operational (job logs, run times, error counts). For each practice item, label the artifact's category before reading the options.

Choosing 'data cleansing' as the fix for every data quality scenario, including ones where the stem describes a root-cause problem in source entry, a missing control, or an unclear definition.

Cleansing is the most familiar DQ activity, so it becomes a default answer. The exam rewards candidates who distinguish preventive controls (validation at entry, defined business rules) from corrective remediation (cleansing, standardization) and from measurement (profiling, scorecards).

What to do instead

Apply a three-way test to each DQ stem: is the problem definition, prevention, or correction? Map to the matching DQ activity. If the stem mentions recurring errors or unknown cause, prefer profiling and root-cause analysis over cleansing.

Treating Data Governance as a synonym for a data quality program or an IT project, and selecting answers where the CDO or data stewards 'fix the data' rather than define policy, decision rights, and accountability.

Governance is abstract and candidates substitute the concrete activity they know (cleansing, tooling) for the governance concept. Exam items test decision rights, stewardship roles, and policy-setting as distinct from execution.

What to do instead

Internalize the definition: governance is the exercise of authority and control over data management, covering what decisions are made, who makes them, and how they are monitored. Reject any option where the governance body performs hands-on data work; prefer options about policy, standards, roles, and escalation.

Mixing up Inmon and Kimball approaches by assigning the normalized enterprise warehouse to Kimball or the star-schema dimensional marts to Inmon, and then answering architecture questions from the wrong premise.

Both names appear together in study material and candidates memorize 'Inmon = warehouse, Kimball = marts' without attaching the modeling style and design order (top-down normalized vs. bottom-up dimensional).

What to do instead

Anchor each name to its signature: Inmon = top-down, normalized (3NF) enterprise data warehouse, subject-oriented and integrated; Kimball = bottom-up, dimensional (star schema, fact and dimension tables), bus matrix for conformed dimensions. State both pairs aloud before answering.

Using 'master data' and 'reference data' interchangeably, or failing to classify a described data set (for example, currency codes versus customer records) correctly.

The two terms are often taught in one chapter and sound similar. The exam distinguishes them by cardinality and change frequency, and by whether the set describes entities or classifies them.

What to do instead

Use the discriminator: reference data is a controlled set of permitted values used to classify or categorize (codes, hierarchies, lookups), relatively static and shared; master data describes key business entities (customer, product, employee, location) with attributes and lifecycles. Classify the example before reading options.

Assuming data integration means ETL only, and rejecting answers involving ELT, CDC, virtualization, or messaging when the stem describes real-time or high-volume requirements.

ETL is the historical default and candidates map 'integration' to it automatically. Exam items test selection of the appropriate pattern based on latency, volume, and transformation location.

What to do instead

Build a pattern-to-trigger table: batch ETL for scheduled transformation before load; ELT when target warehouse compute is strong; CDC for low-latency change capture; virtualization for on-demand access without persistence; messaging/streaming for event-driven near-real-time. Match the stem's latency and volume cues to the pattern.

Ignoring the exam's structure and weighting, spending equal study time on all domains instead of concentrating on the heavier and more conceptually tested areas such as governance, data quality, and modeling, and never doing timed practice.

Candidates study chapter by chapter in book order and run out of time on scenario items that require reading a long stem carefully. Without timed practice, pacing problems surface only on exam day.

What to do instead

Obtain the official domain weighting for your exam version, allocate study hours proportionally, and do at least two full-length timed practice sets. Track per-domain accuracy and re-study any domain below roughly 70 percent.

Memorizing definitions in isolation and then failing scenario items that require applying a concept to a described situation, such as choosing between a data steward and a data owner, or between a business glossary and a data dictionary.

Definition recall feels productive and is easy to self-test, but the exam is largely application-based. Candidates recognize a term and pick the option containing it, even when the scenario calls for a different role or artifact.

What to do instead

Convert every definition into a 'which would you use when' pair. Practice by writing two-sentence scenarios for each key term and choosing between confusable pairs (owner vs. steward, glossary vs. dictionary, profiling vs. cleansing, reference vs. master data).

Exam requirements can change. Confirm current details with the exam provider.

CDMP practice

200 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Data Management Fundamentals (DMF)

    In the DAMA-DMBOK framework, which component of the data management environment defines the roles, decision rights, and accountability structure for data assets?

    1. Data governance Correct answer.
    2. Data architecture
    3. Data storage and operations
    4. Data integration and interoperability

    Explanation

    Data governance is the central discipline that establishes decision rights, accountability, policies, and standards for managing data as an asset. The other listed areas are execution disciplines that operate within the boundaries governance sets, not the accountability structure itself.

  2. Question 2Data Management Fundamentals (DMF)

    A retail company wants a single agreed definition of 'active customer' used consistently across marketing and finance reporting. Which data management discipline most directly owns this deliverable?

    1. Metadata management
    2. Reference and master data management Correct answer.
    3. Data quality management
    4. Document and content management

    Explanation

    Reference and master data management establishes controlled, shared definitions and values for core business entities so that systems and reports agree. A shared definition of a core entity such as customer is a master data concern, even though metadata and quality practices support it.

  3. Question 3Data Management Fundamentals (DMF)

    Which statement best describes the relationship between data and information within data management?

    1. Data consists of raw facts, while information is data processed and given context and meaning. Correct answer.
    2. Information exists only in structured databases, while data exists only in documents.
    3. Information is raw facts, while data is processed and contextualized.
    4. Data and information are interchangeable terms with no meaningful distinction.

    Explanation

    Data comprises raw, unprocessed facts and symbols, whereas information emerges when data is organized, contextualized, and interpreted so it becomes meaningful. This distinction underpins why data management invests in context such as metadata and definitions.

  4. Question 4Data Management Fundamentals (DMF)

    An organization is defining its data lifecycle. At which stage should retention requirements and archival or destruction rules be established?

    1. Only after data has been archived
    2. After the data has been deleted from production systems
    3. Only when a regulator requests records
    4. During the planning and design stage, before data is created or acquired Correct answer.

    Explanation

    Retention, archival, and destruction requirements should be designed into the lifecycle up front so that data is created and stored with the right controls from the start. Addressing them after the fact risks noncompliance and uncontrolled data accumulation.

  5. Question 5Data Management Fundamentals (DMF)

    Which pair correctly distinguishes structured data from unstructured data?

    1. Structured data is always stored on disk; unstructured data is always stored in memory.
    2. Structured data has a predefined schema such as relational tables; unstructured data lacks a predefined model, such as free text or images. Correct answer.
    3. Structured data is created by machines; unstructured data is created only by humans.
    4. Structured data is always more valuable; unstructured data is always low quality.

    Explanation

    Structured data conforms to a predefined schema, typically rows and columns in relational systems, while unstructured data such as text, images, and audio has no predefined data model. The distinction concerns organization and schema, not storage medium, origin, or inherent value.

  6. Question 6Data Management Fundamentals (DMF)

    A data steward needs to trace where a reported figure originated, how it was transformed, and which downstream reports consume it. Which metadata type primarily serves this need?

    1. Business metadata
    2. Technical metadata Correct answer.
    3. Operational metadata
    4. Reference metadata

    Explanation

    Technical metadata describes structures, transformations, and data flows such as source-to-target mappings and lineage, which is exactly what tracing origin and transformation requires. Business metadata provides definitions and usage context, while operational metadata covers runtime statistics.

  7. Question 7Data Management Fundamentals (DMF)

    Which activity is the primary purpose of a data quality dimension assessment such as completeness, accuracy, and timeliness?

    1. To replace master data management with automated cleansing
    2. To quantify how well data meets defined expectations so improvement can be prioritized Correct answer.
    3. To eliminate the need for data governance policies
    4. To guarantee that data will never contain errors

    Explanation

    Data quality dimensions provide measurable criteria that quantify conformance to expectations, enabling teams to prioritize remediation where gaps are largest. They support governance and improvement rather than replacing those disciplines or promising error-free data.

  8. Question 8Data Management Fundamentals (DMF)

    In a relational database, what does a foreign key enforce?

    1. That all attributes are stored in a single flat file
    2. That values in one table correspond to existing key values in a related table Correct answer.
    3. That every column in a table contains a unique value
    4. That a table cannot be updated once created

    Explanation

    A foreign key is an attribute whose values must match primary key values in a related table, enforcing referential integrity between the two. It constrains relationships, not uniqueness of every column or immutability of tables.

  9. Question 9Data Management Fundamentals (DMF)

    A team stores the same customer address in five separate applications and must update each one manually. Which data management problem does this most clearly illustrate?

    1. Insufficient data encryption
    2. Excessive normalization
    3. Overuse of metadata repositories
    4. Data redundancy and inconsistency risk Correct answer.

    Explanation

    Duplicating the same attribute across multiple systems creates redundancy and raises the risk of inconsistent values when updates are not synchronized. Master data management and integration practices address this by establishing an authoritative source.

  10. Question 10Data Management Fundamentals (DMF)

    Which statement accurately characterizes the role of data architecture within an organization?

    1. It defines the blueprint for data assets, their structure, and how they integrate with business processes and technology. Correct answer.
    2. It is a one-time project deliverable that never changes after approval.
    3. It is limited to selecting a single database vendor for the enterprise.
    4. It replaces data modeling by eliminating the need for entity definitions.

    Explanation

    Data architecture provides the overall blueprint describing data assets, their structure and relationships, and alignment with business processes and technology. It is broader than vendor selection, complements data modeling, and evolves with the organization.

  11. Question 11Data Management Fundamentals (DMF)

    A data management program wants to assign accountability so that each critical data element has a named owner responsible for its definition and quality. Which concept does this describe?

    1. Data virtualization
    2. Data federation
    3. Data replication
    4. Data stewardship and ownership Correct answer.

    Explanation

    Stewardship and ownership assign named accountability for data elements, including defining meaning and monitoring quality. Virtualization, federation, and replication are technical data access and movement techniques that do not assign accountability.

  12. Question 12Data Management Fundamentals (DMF)

    An analyst reports that a dashboard's revenue total differs from the finance ledger by a small margin each month. Which first step best reflects a disciplined data management response?

    1. Immediately rebuild the dashboard in a new tool
    2. Delete the dashboard to avoid confusion
    3. Trace lineage and definitions of the revenue metric to identify the source of divergence Correct answer.
    4. Assume the finance ledger is always correct without investigation

    Explanation

    Investigating lineage and metric definitions determines whether the divergence stems from different sources, transformations, timing, or filters. This evidence-based step addresses root cause before any remediation such as rebuilding or retiring the report.

  13. Question 13Data Management Fundamentals (DMF)

    Which description best captures the purpose of a data model at the conceptual level?

    1. It communicates the key business entities and their relationships independent of technology. Correct answer.
    2. It documents server configuration and backup schedules.
    3. It specifies physical storage parameters and index structures.
    4. It lists the exact SQL data types for every column.

    Explanation

    A conceptual data model presents the important business entities and relationships in technology-neutral terms, serving communication between business and technical stakeholders. Physical details such as storage, data types, and configuration belong to logical and physical models or operations.

  14. Question 14Data Management Fundamentals (DMF)

    A hospital must retain patient records for a legally mandated period and then destroy them in a controlled way. Which data management capability governs this requirement?

    1. Records retention and disposition policy within data governance Correct answer.
    2. Schema versioning in development
    3. Capacity planning for storage hardware
    4. Query performance tuning

    Explanation

    Retention and disposition policies, established under data governance, define how long records are kept and how they are lawfully destroyed. Performance tuning, schema versioning, and capacity planning are technical concerns that do not set legal retention rules.

  15. Question 15Data Management Fundamentals (DMF)

    Which of the following best describes the difference between a data warehouse and a data lake?

    1. A warehouse and a lake are identical concepts with different marketing names.
    2. A warehouse cannot be queried, while a lake always enforces strict relational constraints.
    3. A warehouse stores only unstructured data, while a lake stores only relational tables.
    4. A warehouse typically stores schema-on-write structured data for analytics, while a lake can store raw data of many forms using schema-on-read. Correct answer.

    Explanation

    A data warehouse generally applies schema on write and holds structured, curated data for analytical use, while a data lake stores raw data in varied formats and applies schema on read. This distinction concerns structure and processing approach rather than marketing terminology.

  16. Question 16Data Management Fundamentals (DMF)

    A global firm needs consistent codes for country, currency, and unit of measure shared across all applications. Which type of data is this?

    1. Reference data Correct answer.
    2. Unstructured content
    3. Streaming telemetry
    4. Transactional data

    Explanation

    Reference data consists of controlled, relatively static code sets and valid values, such as country codes, currencies, and units of measure, used to categorize other data. Transactional data records business events, while the other options describe different data forms.

  17. Question 17Data Management Fundamentals (DMF)

    Which practice most directly supports data interoperability between two systems that use different customer identifier formats?

    1. Disabling referential integrity in both systems
    2. Encouraging each system to invent new identifiers independently
    3. Defining a cross-reference or mapping between the identifier schemes Correct answer.
    4. Storing both systems' data in the same physical table without transformation

    Explanation

    Interoperability requires a mapping or cross-reference that translates between differing identifier schemes so records can be reconciled. Shared physical storage without transformation, disabled integrity, or proliferating identifiers all worsen inconsistency.

  18. Question 18Data Management Fundamentals (DMF)

    Which statement best explains why metadata is considered a critical data management asset rather than an optional by-product?

    1. It eliminates the need to store the underlying data itself.
    2. It provides the context, definitions, and lineage needed to trust, find, and govern data effectively. Correct answer.
    3. It guarantees that source systems will never change their schemas.
    4. It replaces the need for data quality measurement.

    Explanation

    Metadata supplies definitions, context, and lineage that let users find, understand, trust, and govern data, which is why it is managed as an asset. It does not substitute for the data, prevent schema changes, or replace quality measurement.

  19. Question 19Data Management Fundamentals (DMF)

    A team is choosing between a normalized operational schema and a denormalized analytical schema. Which rationale best fits the analytical choice?

    1. Normalization is only used for unstructured data.
    2. Denormalization can reduce join complexity and improve query performance for analytical workloads. Correct answer.
    3. Analytical schemas must never duplicate attributes.
    4. Denormalization always reduces storage cost to zero.

    Explanation

    Denormalized structures such as star schemas reduce the number of joins required, which can improve read performance for analytical queries. Operational systems favor normalization to control redundancy and integrity, while analytical systems often trade redundancy for speed.

  20. Question 20Data Management Fundamentals (DMF)

    Which of the following is the most accurate description of a data domain within an enterprise data governance program?

    1. A programming language used to query databases
    2. A physical server partition used only for backups
    3. A logical grouping of data related to a business subject area, governed by assigned owners and policies Correct answer.
    4. A temporary file used during extract-transform-load jobs

    Explanation

    A data domain groups data by business subject area, such as customer or product, and is governed by assigned owners, stewards, and policies. This organizational concept is distinct from physical infrastructure, languages, or transient processing artifacts.

  21. Question 21Data Management Fundamentals (DMF)

    An organization discovers that the same product appears under three different names across systems because no authority was designated. Which root cause does this most directly indicate?

    1. Overinvestment in data encryption
    2. Excessive use of data lineage tools
    3. Insufficient network bandwidth
    4. Absence of master data management for the product entity Correct answer.

    Explanation

    Multiple conflicting names for the same product indicate the lack of an authoritative master data source and governance for that entity. Master data management establishes a trusted, shared record to which other systems conform.

  22. Question 22Data Management Fundamentals (DMF)

    Which statement best describes the purpose of data profiling?

    1. To analyze data for patterns, anomalies, and quality issues such as nulls or outliers Correct answer.
    2. To schedule nightly backup jobs
    3. To design the user interface of a reporting dashboard
    4. To encrypt sensitive columns before storage

    Explanation

    Data profiling examines datasets statistically to reveal patterns, anomalies, and quality issues such as missing values, duplicates, and outliers. It informs quality assessment and modeling decisions rather than encryption, interface design, or backup scheduling.

  23. Question 23Data Management Fundamentals (DMF)

    A data management team is evaluating whether to virtualize access to several source systems instead of copying data into a central store. Which consideration is most relevant to this decision?

    1. Virtualization guarantees better data quality than physical consolidation.
    2. Virtualization removes all need for data governance.
    3. Virtualization can reduce duplication and latency but may depend on source availability and performance. Correct answer.
    4. Virtualization eliminates the need for metadata about sources.

    Explanation

    Data virtualization provides a logical access layer that can reduce duplication and staleness, but query performance and reliability depend on the availability and speed of underlying sources. It does not automatically improve quality, remove metadata needs, or replace governance.

  24. Question 24Data Management Fundamentals (DMF)

    Which activity best exemplifies the practice of data integration?

    1. Transforming and consolidating order data from three systems into a unified view Correct answer.
    2. Writing a policy on records destruction
    3. Defining a conceptual entity-relationship diagram
    4. Assigning a steward to a customer data domain

    Explanation

    Data integration involves combining and transforming data from multiple sources into a consistent, unified view for consumption. Stewardship, retention policy, and conceptual modeling are governance and design activities rather than integration execution.

  25. Question 25Data Management Fundamentals (DMF)

    A data architect argues that the organization needs both a logical and a physical data model. Which justification is most sound?

    1. The logical model is only for auditors, and the physical model is only for executives.
    2. The physical model is optional because databases generate themselves automatically.
    3. The logical model must include exact storage block sizes to be valid.
    4. The logical model captures business rules and relationships independent of technology, while the physical model specifies implementation details for a chosen platform. Correct answer.

    Explanation

    Logical models describe entities, attributes, and relationships with business rules but without platform specifics, while physical models translate that into tables, data types, indexes, and storage for a target platform. Both serve distinct and necessary purposes in design.

  26. Question 26Data Modeling and Design

    In a relational data model, which construct enforces that each row of a table can be uniquely identified and never duplicated?

    1. A check constraint
    2. A default constraint
    3. A foreign key constraint
    4. A primary key constraint Correct answer.

    Explanation

    A primary key uniquely identifies every row in a table and prohibits null or duplicate values in the key columns. Foreign keys instead reference keys in other tables, while check and default constraints restrict or supply column values rather than guaranteeing row uniqueness.

  27. Question 27Data Modeling and Design

    Which modeling notation represents a relationship as an associative entity (associative table) when a many-to-many relationship must be resolved for a relational database?

    1. Crow's foot
    2. Dimensional modeling
    3. Entity-relationship modeling Correct answer.
    4. Object role modeling

    Explanation

    In entity-relationship modeling, a many-to-many relationship is resolved by introducing an associative entity that holds the keys of both participating entities. This associative entity then becomes a junction table in the physical relational schema.

  28. Question 28Data Modeling and Design

    A data modeler normalizes an entity to third normal form. Which condition must the entity satisfy in addition to being in second normal form?

    1. Every non-key attribute must be free of transitive dependency on the primary key. Correct answer.
    2. Every non-key attribute must be functionally dependent on the whole primary key only.
    3. Every foreign key must reference an existing primary key value.
    4. Every attribute must be atomic and free of repeating groups.

    Explanation

    Third normal form eliminates transitive dependencies, meaning no non-key attribute depends on another non-key attribute. First normal form addresses atomicity and repeating groups, and second normal form removes partial dependencies on part of a composite key.

  29. Question 29Data Modeling and Design

    A retail model stores customer, order, and order line entities. Which cardinality correctly describes the relationship between an order and its order lines?

    1. Many-to-many
    2. One-to-many Correct answer.
    3. One-to-one
    4. Zero-to-one

    Explanation

    A single order can contain multiple order lines, but each order line belongs to exactly one order, producing a one-to-many relationship from order to order line. The many side is the child entity that carries the foreign key to the parent.

  30. Question 30Data Modeling and Design

    In dimensional modeling, which schema places a fact table at the center with fully normalized dimension tables joined through intermediate tables?

    1. Snowflake schema Correct answer.
    2. Third normal form schema
    3. Data vault
    4. Star schema

    Explanation

    A snowflake schema normalizes dimension tables into multiple related tables, reducing redundancy at the cost of more joins. A star schema keeps dimensions denormalized and directly joined to the fact table.

  31. Question 31Data Modeling and Design

    A data modeler must record the history of changes to a customer's address over time while preserving each prior version. Which technique best supports this requirement?

    1. Slowly changing dimension type 1
    2. Slowly changing dimension type 2 Correct answer.
    3. Degenerate dimension
    4. Junk dimension

    Explanation

    A slowly changing dimension type 2 adds a new row with effective dates and a current flag for each change, preserving full history. Type 1 overwrites the old value and therefore loses prior versions.

  32. Question 32Data Modeling and Design

    Which element of a data model captures a business rule stating that an account balance may never be negative?

    1. A relationship
    2. A constraint Correct answer.
    3. An attribute
    4. An entity

    Explanation

    A constraint expresses a rule that restricts the values or states data may take, such as a balance that cannot fall below zero. Entities, attributes, and relationships describe structure rather than value restrictions.

  33. Question 33Data Modeling and Design

    A modeler is designing a conceptual data model. Which characteristic is most appropriate at this level?

    1. It shows major entities and relationships without technical detail. Correct answer.
    2. It specifies data types and column lengths.
    3. It defines primary and foreign key columns.
    4. It includes indexes and storage parameters.

    Explanation

    A conceptual model captures the business view, showing major entities and relationships while abstracting away technical implementation. Physical details such as indexes, keys, and data types belong to logical and physical models.

  34. Question 34Data Modeling and Design

    A logical data model shows a many-to-many relationship between Student and Course. What is the standard way to transform this for a relational physical model?

    1. Remove the relationship to avoid redundancy.
    2. Add a foreign key from Student to Course only.
    3. Merge Student and Course into a single table.
    4. Create an associative entity Enrollment with foreign keys to both Student and Course. Correct answer.

    Explanation

    Relational databases cannot directly store a many-to-many relationship, so an associative entity (junction table) with foreign keys to both parents resolves it. This preserves the association while allowing multiple students per course and vice versa.

  35. Question 35Data Modeling and Design

    Which normal form specifically removes partial dependencies of non-key attributes on part of a composite primary key?

    1. Third normal form
    2. First normal form
    3. Second normal form Correct answer.
    4. Boyce-Codd normal form

    Explanation

    Second normal form requires that every non-key attribute depend on the entire primary key, eliminating partial dependency on part of a composite key. Third normal form and Boyce-Codd normal form address transitive and other functional dependencies.

  36. Question 36Data Modeling and Design

    A data modeler adds a surrogate key to a dimension table. What is the primary reason for using a surrogate key rather than the natural business key?

    1. It removes the need for a primary key.
    2. It provides a stable, compact identifier decoupled from business values. Correct answer.
    3. It guarantees the natural key is never changed.
    4. It enforces referential integrity automatically.

    Explanation

    A surrogate key is a system-generated identifier independent of business attributes, so changes to natural keys do not ripple through the warehouse. It is typically compact and stable, simplifying joins and history tracking in dimensions.

  37. Question 37Data Modeling and Design

    In a star schema, which table typically contains the numeric measures and foreign keys to dimension tables?

    1. Bridge table
    2. Dimension table
    3. Staging table
    4. Fact table Correct answer.

    Explanation

    The fact table stores measurable events and foreign keys that reference the surrounding dimension tables. Dimension tables hold descriptive attributes that give context to those measures.

  38. Question 38Data Modeling and Design

    A modeler wants to model a hierarchy in which each employee may report to at most one manager. Which relationship structure fits best?

    1. A one-to-one relationship between Employee and Manager entities
    2. A recursive one-to-many relationship within the Employee entity Correct answer.
    3. A many-to-many relationship between Employee and Department
    4. A recursive many-to-many relationship within the Employee entity

    Explanation

    A self-referencing one-to-many relationship on Employee models the reporting hierarchy: one manager has many direct reports, and each employee has at most one manager. This is also called a recursive or unary relationship.

  39. Question 39Data Modeling and Design

    Which data modeling approach organizes data into hubs, links, and satellites to support integration and auditability?

    1. Snowflake schema
    2. Data vault Correct answer.
    3. Star schema
    4. Object role modeling

    Explanation

    Data vault modeling separates business keys (hubs), relationships (links), and descriptive history (satellites) to support scalable integration and full auditability. Star and snowflake schemas are dimensional patterns for analytics rather than integration-oriented structures.

  40. Question 40Data Modeling and Design

    An attribute in a dimension table has low cardinality with many repeated values across rows. Which design action is most appropriate?

    1. Convert the attribute into a surrogate key.
    2. Move the attribute to a separate normalized table joined to the dimension.
    3. Group the attribute with related flags into a junk dimension. Correct answer.
    4. Remove the attribute from the model.

    Explanation

    Low-cardinality flags and indicators are often combined into a junk dimension to keep the main dimension narrow and avoid many tiny columns. Grouping related flags reduces clutter and improves query performance.

  41. Question 41Data Modeling and Design

    Which statement best describes the purpose of a data model review before physical implementation?

    1. It tunes database indexes for query performance.
    2. It generates the production deployment script.
    3. It validates that the model meets business requirements and modeling standards. Correct answer.
    4. It migrates data from legacy systems.

    Explanation

    A model review checks that the design satisfies business requirements, follows naming and modeling standards, and resolves structural issues before costly implementation. Index tuning, migration, and deployment occur later in the lifecycle.

  42. Question 42Data Modeling and Design

    A modeler wants to represent an optional relationship where a customer may have zero or more phone numbers. Which cardinality notation is correct?

    1. Zero-to-exactly-one
    2. One-to-exactly-one
    3. One-to-zero-or-many Correct answer.
    4. Many-to-many

    Explanation

    An optional one-to-many relationship is expressed as one-to-zero-or-many, meaning a customer exists with any number of phone numbers from zero upward. This captures both optionality and multiplicity correctly.

  43. Question 43Data Modeling and Design

    Which artifact documents the meaning of each attribute, its allowed values, and its source in a data model?

    1. A physical data model
    2. An entity-relationship diagram
    3. A data flow diagram
    4. A data dictionary Correct answer.

    Explanation

    A data dictionary provides metadata for each attribute, including definition, allowed values, data type, and source. Diagrams show structure visually but do not capture detailed attribute semantics.

  44. Question 44Data Modeling and Design

    A modeler is choosing between a star schema and a snowflake schema for a reporting mart. Which trade-off favors the star schema?

    1. Reduced storage through full dimension normalization
    2. Stronger enforcement of third normal form
    3. Elimination of the fact table
    4. Fewer joins and simpler queries for business users Correct answer.

    Explanation

    A star schema keeps dimensions denormalized, so queries require fewer joins and are simpler for business users and BI tools. A snowflake schema reduces redundancy but increases join complexity.

  45. Question 45Data Modeling and Design

    In an entity-relationship model, what does a weak entity require to be uniquely identified?

    1. An identifying relationship to an owner entity plus a partial key Correct answer.
    2. A surrogate key generated by the database
    3. A many-to-many relationship to a dimension
    4. A globally unique natural key

    Explanation

    A weak entity cannot be uniquely identified by its own attributes alone; it depends on an identifying relationship to an owner entity combined with a partial key. Its full identifier is the owner's key plus the partial key.

  46. Question 46Data Modeling and Design

    Which type of data model is most closely tied to a specific database management system and includes data types, indexes, and storage details?

    1. Logical data model
    2. Conceptual data model
    3. Physical data model Correct answer.
    4. Semantic data model

    Explanation

    A physical data model is tailored to a specific DBMS and includes data types, indexes, partitioning, and storage details. Conceptual and logical models remain platform-independent and progressively add detail.

  47. Question 47Data Modeling and Design

    A modeler discovers that a non-key attribute depends on another non-key attribute within the same entity. Which anomaly risk does this transitive dependency primarily create?

    1. Insert anomaly
    2. Referential anomaly
    3. Update anomaly Correct answer.
    4. Deletion anomaly

    Explanation

    A transitive dependency means the same fact is stored in multiple rows, so updating one non-key attribute may require updating many rows and risks inconsistency. This is the classic update anomaly that normalization to third normal form removes.

  48. Question 48Data Modeling and Design

    Which modeling technique uses facts and roles to express business rules in natural-language-like statements?

    1. Object role modeling Correct answer.
    2. Crow's foot notation
    3. Data vault modeling
    4. Dimensional modeling

    Explanation

    Object role modeling represents the domain as elementary facts that objects play roles in, expressed in natural-language-like statements. This supports precise constraint specification and traceability to business rules.

  49. Question 49Data Modeling and Design

    A fact table has a granularity defined at the individual sales transaction level. Which consequence follows from this choice?

    1. It prevents aggregation to daily totals.
    2. It eliminates the need for dimension keys.
    3. It enables flexible aggregation to any higher level. Correct answer.
    4. It requires a snowflaked dimension.

    Explanation

    Defining the fact table at the finest grain stores atomic data that can be aggregated to any higher level, such as daily or monthly totals. Coarser grain would permanently lose detail needed for flexible analysis.

  50. Question 50Data Modeling and Design

    Which practice best supports naming consistency across a large data model with many modelers?

    1. Allowing each modeler to choose names freely
    2. Adopting a documented naming convention and glossary Correct answer.
    3. Naming attributes after their source systems
    4. Using abbreviations without documentation

    Explanation

    A documented naming convention plus a business glossary ensures that entities and attributes are named consistently and understood by all stakeholders. Free-form naming leads to synonyms and ambiguity that complicate integration.

  51. Question 51Metadata

    In a metadata management program, which artifact defines the permitted values, data types, and business meaning for a data element such as Customer Status?

    1. A data quality scorecard for the customer table
    2. A data lineage diagram showing upstream jobs
    3. A backup schedule for the customer database
    4. A data dictionary entry with an associated value domain Correct answer.

    Explanation

    A data dictionary entry documents the element's definition, data type, and permitted value domain, which is the core of structural and definitional metadata. Lineage, quality scorecards, and backup schedules are operational or process metadata and do not define permitted values.

  52. Question 52Metadata

    Which statement best distinguishes technical metadata from business metadata?

    1. Technical metadata describes structure and systems; business metadata describes meaning and usage context. Correct answer.
    2. Technical metadata is created only by data stewards; business metadata is created only by DBAs.
    3. Technical metadata is mandatory; business metadata is optional and never governed.
    4. Technical metadata is always stored in a spreadsheet; business metadata is always stored in a graph database.

    Explanation

    Technical metadata covers physical structure such as tables, columns, data types, and system configuration, while business metadata covers definitions, business rules, and usage context. The split is about content, not about who creates it or which storage technology is used.

  53. Question 53Metadata

    A data steward needs to record that the 'Order Total' attribute must equal the sum of line-item amounts. Where should this rule be captured in a metadata repository?

    1. As a business rule associated with the attribute definition Correct answer.
    2. As a column data type of DECIMAL(12,2)
    3. As a row count statistic refreshed nightly
    4. As a storage location path in the data lake

    Explanation

    A derived-value constraint is a business rule and belongs with the attribute definition so consumers know how the value is computed. Data type, statistics, and storage paths are technical facts that do not express the computation rule.

  54. Question 54Metadata

    Which metadata type captures when a dataset was last loaded and by which job?

    1. Semantic metadata
    2. Operational metadata Correct answer.
    3. Reference metadata
    4. Business metadata

    Explanation

    Operational metadata records runtime facts such as load timestamps, job identifiers, and execution status. Business metadata addresses meaning and rules, and semantic metadata addresses concept relationships rather than job execution.

  55. Question 55Metadata

    What is the primary purpose of a business glossary?

    1. To store the physical DDL for every table in production
    2. To provide agreed business definitions and ownership for terms used across the organization Correct answer.
    3. To archive historical copies of source files for audit
    4. To monitor query performance against service-level targets

    Explanation

    A business glossary is a governed collection of business terms with definitions, synonyms, and stewards, enabling shared vocabulary. It is not a physical schema store, a performance monitor, or an archival system.

  56. Question 56Metadata

    Which practice most directly improves the trustworthiness of metadata in a catalog?

    1. Restricting the catalog to the data engineering team only
    2. Loading all metadata automatically and never curating it
    3. Allowing every user to edit definitions without approval
    4. Assigning accountable stewards and enforcing review before publication Correct answer.

    Explanation

    Metadata quality depends on clear accountability and a controlled review workflow so definitions are accurate and current. Uncontrolled editing or purely automated loading without curation erodes trust, and restricting access prevents the catalog from serving its users.

  57. Question 57Metadata

    In metadata architecture, what role does a metadata repository play?

    1. It replaces the master data management hub.
    2. It enforces row-level security on transactional tables.
    3. It stores and integrates metadata from multiple sources for controlled access and exchange. Correct answer.
    4. It executes ETL transformations against the warehouse.

    Explanation

    A metadata repository is the integrated store that consolidates metadata from various tools and exposes it through governed interfaces. It does not run transformations, substitute for an MDM hub, or enforce row-level security on operational data.

  58. Question 58Metadata

    Which item is an example of structural metadata for a relational table?

    1. The name of the steward who approved the table
    2. The business definition of the table's purpose
    3. Column names, data types, and primary key constraints Correct answer.
    4. The number of rows loaded in the last run

    Explanation

    Structural metadata describes the design of the object, including columns, data types, keys, and constraints. Business purpose, load statistics, and stewardship records are business or operational metadata.

  59. Question 59Metadata

    A data catalog shows that a report column 'Net Revenue' is derived from a stored procedure. A steward wants to trace which source tables feed this column. Which metadata capability is required?

    1. Data profiling at row level
    2. Data masking at column level
    3. Data archiving at table level
    4. Data lineage at column level Correct answer.

    Explanation

    Column-level lineage records the transformation path from source attributes to downstream targets, which is exactly what tracing a derived report column requires. Profiling, masking, and archiving address quality, privacy, and retention rather than traceability.

  60. Question 60Metadata

    An organization wants glossary terms to automatically link to physical columns in the catalog. Which metadata relationship is being established?

    1. A foreign key constraint between two tables
    2. A semantic mapping between business terms and technical assets Correct answer.
    3. A retention rule applied to a column
    4. A replication topology between two databases

    Explanation

    Linking glossary terms to physical assets creates semantic mappings or business-term associations that connect meaning to implementation. Foreign keys, replication, and retention rules are technical or policy constructs, not term-to-asset associations.

  61. Question 61Metadata

    Which approach best supports federated metadata management across business units while preserving central standards?

    1. Automated harvesting only, with no defined ownership model
    2. Central standards with locally accountable stewards publishing to a shared repository Correct answer.
    3. A single central team authoring every definition without business input
    4. Independent unit glossaries with no shared identifiers

    Explanation

    Federated models combine centrally defined standards with distributed stewardship so local knowledge is captured while consistency is maintained. Central-only authoring lacks domain expertise, and fully independent glossaries create conflicting definitions.

  62. Question 62Metadata

    A team discovers two glossary terms with the same name but different definitions across regions. What is the most appropriate metadata governance action?

    1. Merge the terms without documenting the regional distinction
    2. Keep both entries unchanged to avoid conflict
    3. Reconcile the definitions and record regional variants as qualified synonyms under one governed term Correct answer.
    4. Delete both terms and let users define meaning locally

    Explanation

    Conflicting definitions should be reconciled through stewardship, with legitimate regional variants captured as qualified synonyms so context is preserved. Deleting, ignoring, or silently merging loses information and reintroduces ambiguity.

  63. Question 63Metadata

    Which metadata is most useful for impact analysis before changing a source column's data type?

    1. The glossary definition of the column
    2. Downstream lineage showing dependent reports and transformations Correct answer.
    3. The storage cost of the source table
    4. The steward's contact details

    Explanation

    Impact analysis relies on lineage to identify downstream consumers affected by a structural change. Definitions, contacts, and storage costs are useful context but do not reveal dependencies.

  64. Question 64Metadata

    A metadata repository must support versioning of definitions so auditors can see what a term meant at a past date. Which capability is essential?

    1. Full-text search across documents
    2. Temporal version history with effective dates Correct answer.
    3. Real-time streaming ingestion of logs
    4. Role-based access to dashboards

    Explanation

    Audit needs require temporal versioning that records definition changes with effective dates so historical meaning can be reconstructed. Streaming, search, and dashboard access are useful but do not preserve definition history.

  65. Question 65Metadata

    Which pairing correctly matches a metadata source with the metadata it typically contributes?

    1. The backup system contributes business definitions
    2. The business glossary contributes physical data types
    3. The HR system contributes column constraints
    4. ETL tooling contributes transformation logic and data movement lineage Correct answer.

    Explanation

    Integration tooling captures transformation rules and movement paths, making it a primary lineage source. Glossaries hold definitions, backups hold recovery information, and HR systems hold employee data, not schema constraints.

  66. Question 66Metadata

    What is the main risk of relying solely on automated metadata harvesting without curation?

    1. Technical facts are captured but business context and definitions remain missing or inaccurate Correct answer.
    2. Storage costs for metadata will drop to zero
    3. Lineage will always be more accurate than manual documentation
    4. The repository will contain too few technical objects

    Explanation

    Automated harvesting reliably collects technical metadata but cannot infer business meaning, so definitions and context stay absent or wrong unless stewards curate them. Harvesting does not guarantee accuracy of lineage or eliminate costs.

  67. Question 67Metadata

    A data catalog implements a 'certified' badge on datasets. What metadata practice does this represent?

    1. Replicating the dataset to a second region
    2. Encrypting the dataset at rest
    3. Attesting that defined quality and governance criteria have been met by an accountable owner Correct answer.
    4. Compressing the dataset for storage savings

    Explanation

    Certification is a governance signal that an accountable party has verified the asset against documented criteria, helping consumers judge fitness for use. Encryption, replication, and compression are technical operations unrelated to attestation.

  68. Question 68Metadata

    Which metadata standard is designed to exchange technical metadata about relational schemas between tools?

    1. XBRL
    2. HL7 FHIR
    3. ISO 20022
    4. Common Warehouse Metamodel (CWM) Correct answer.

    Explanation

    CWM is an OMG standard for exchanging warehouse and relational metadata between tools. XBRL targets financial reporting, FHIR targets healthcare interoperability, and ISO 20022 targets financial messaging.

  69. Question 69Metadata

    A steward must decide whether a new attribute belongs in the business glossary or only in the technical catalog. Which criterion is most relevant?

    1. Whether the attribute is stored in a cloud platform
    2. Whether the attribute is loaded by a nightly job
    3. Whether the attribute uses a numeric data type
    4. Whether the attribute carries business meaning that users need defined and governed Correct answer.

    Explanation

    Glossary membership is driven by the need for a governed business definition and shared understanding. Data type, platform, and load schedule are technical traits that do not by themselves justify a glossary entry.

  70. Question 70Metadata

    Which control best prevents unauthorized changes to published metadata definitions?

    1. Public read access for all employees
    2. Full-text indexing of all definitions
    3. Weekly full backups of the repository
    4. Workflow-based approval with role-restricted edit rights Correct answer.

    Explanation

    Change control requires restricting who can edit and routing changes through an approval workflow before publication. Backups aid recovery, indexing aids discovery, and open read access does not prevent unauthorized edits.

  71. Question 71Metadata

    An analyst needs to know which systems of record are authoritative for 'Customer Identifier' before building a cross-system join. Which metadata should they consult?

    1. System-of-record designations and cross-reference mappings in the catalog Correct answer.
    2. The query execution plan of a sample join
    3. The physical backup retention policy
    4. The storage tier assignment of the tables

    Explanation

    Authoritative source designations and cross-reference mappings tell the analyst which system owns the identifier and how values correspond across systems. Backup policy, execution plans, and storage tiers do not address authority or correspondence.

  72. Question 72Metadata

    A lineage graph shows a transformation that aggregates transactions by day, but the catalog claims the target is at transaction grain. Which metadata quality dimension is violated?

    1. Consistency between lineage and documented grain Correct answer.
    2. Completeness of the glossary
    3. Precision of the data type
    4. Timeliness of load statistics

    Explanation

    The documented grain contradicts the transformation shown in lineage, so the metadata is internally inconsistent. Completeness, timeliness, and precision describe other quality dimensions and are not the issue here.

  73. Question 73Metadata

    An organization plans to expose metadata through APIs for self-service consumption. Which design consideration is most critical for governed access?

    1. Storing credentials in client applications for convenience
    2. Enforcing authentication, authorization, and sensitivity classification at the API layer Correct answer.
    3. Maximizing the number of endpoints regardless of sensitivity
    4. Caching all metadata publicly to reduce latency

    Explanation

    API-based metadata access must apply authentication, authorization, and classification-based filtering so sensitive metadata is not overexposed. Endpoint sprawl, public caching, and embedded credentials all increase risk.

  74. Question 74Metadata

    Two tools report different lineage for the same target table. What is the most rigorous way to establish the accurate lineage?

    1. Trust the tool with the larger user base
    2. Reconcile against transformation code and runtime logs with steward validation Correct answer.
    3. Trust the tool with the more recent installation date
    4. Average the two lineage graphs into a combined view

    Explanation

    Lineage accuracy is established by verifying against the actual transformation logic and execution evidence, then having stewards confirm the result. Popularity, installation date, and averaging are not evidence of correctness and can propagate errors.

  75. Question 75Metadata

    A metadata repository must support both a hierarchical taxonomy for reporting and a graph of concept relationships for semantic search. Which architecture choice best satisfies both needs?

    1. Duplicate all terms in two disconnected repositories
    2. Use a single free-text document store without relationships
    3. Store only flat term lists and rebuild structure per query
    4. Maintain a controlled vocabulary with typed relationships that can be rendered as hierarchy or graph Correct answer.

    Explanation

    A controlled vocabulary with typed relationships provides one governed source that can be presented as a hierarchy or traversed as a graph, avoiding duplication and drift. Flat lists, free text, and disconnected duplicates cannot represent relationships consistently.

  76. Question 76Data Quality

    Which dimension of data quality is primarily concerned with whether a data value conforms to a defined format, type, and allowed value set?

    1. Timeliness
    2. Uniqueness
    3. Validity Correct answer.
    4. Completeness

    Explanation

    Validity measures conformance of a value to its declared domain: data type, format pattern, range, or enumerated allowed values. It is assessed per attribute against rules, not against duplication or latency.

  77. Question 77Data Quality

    A retail team reports that 4 percent of customer records have no postal code, although postal code is mandatory for shipping. Which quality dimension is being measured?

    1. Completeness Correct answer.
    2. Accuracy
    3. Precision
    4. Consistency

    Explanation

    Completeness measures the proportion of required values that are present. Because postal code is mandatory, its absence is a completeness defect regardless of whether present values are correct.

  78. Question 78Data Quality

    What is the primary purpose of defining a data quality rule in a data quality management program?

    1. To document the business glossary hierarchy
    2. To schedule the extract-transform-load jobs
    3. To specify a testable condition that data must satisfy Correct answer.
    4. To assign stewards to source systems

    Explanation

    A data quality rule expresses an expected condition, such as a range check or referential check, that can be executed against data and measured. Rules make quality expectations objective and repeatable.

  79. Question 79Data Quality

    An organization measures data quality by counting how many records fail each rule and comparing that count to a target threshold. What is this practice called?

    1. Data profiling
    2. Data quality scorecarding Correct answer.
    3. Schema evolution
    4. Master data consolidation

    Explanation

    Scorecarding summarizes rule results against targets to communicate quality levels to stakeholders. The counts and thresholds form measurable indicators that can be tracked over time.

  80. Question 80Data Quality

    Which activity best describes data profiling in a data quality context?

    1. Certifying a dataset for regulatory reporting
    2. Analyzing data statistically to discover patterns, anomalies, and rule candidates Correct answer.
    3. Archiving historical data for retention compliance
    4. Enforcing referential integrity constraints on a warehouse

    Explanation

    Profiling examines actual data to reveal distributions, null rates, distinct values, and anomalies. Its findings inform which quality rules and thresholds should be defined.

  81. Question 81Data Quality

    A data quality issue is best described as which of the following?

    1. A planned change to a data model
    2. A backup failure in the production database
    3. A request to add a new report
    4. A defect or gap that makes data unfit for its intended use Correct answer.

    Explanation

    A data quality issue is a defect or gap that impairs fitness for purpose, such as missing, wrong, or inconsistent values. It is defined relative to the use the data must support.

  82. Question 82Data Quality

    In root cause analysis of a recurring data quality defect, which practice is most appropriate?

    1. Adding more rules to the same field without investigation
    2. Lowering the threshold so the defect no longer triggers
    3. Correcting the individual records and closing the incident
    4. Tracing the defect to its originating process step and remediating that step Correct answer.

    Explanation

    Root cause analysis seeks the process or system step that generates defects so it can be fixed permanently. Correcting records alone treats symptoms and allows recurrence.

  83. Question 83Data Quality

    Which of the following is a characteristic of a well-formed data quality rule?

    1. It requires manual review of every record
    2. It applies to all attributes without exception
    3. It is expressed in business terms and is objectively testable Correct answer.
    4. It changes meaning depending on the reporting period

    Explanation

    A good rule states an expectation clearly, in business language, and can be executed to yield a pass or fail result. Objectivity and testability make results comparable and auditable.

  84. Question 84Data Quality

    A customer master file stores the same customer three times with slightly different name spellings. Which quality dimension is most directly violated?

    1. Timeliness
    2. Uniqueness Correct answer.
    3. Validity
    4. Volume

    Explanation

    Uniqueness requires that each real-world entity be represented once. Duplicate representations of the same customer violate that expectation even if each record is individually valid.

  85. Question 85Data Quality

    Two systems hold the same customer's birth date, but one records 1980-04-12 and the other 1980-12-04. Which dimension is most directly implicated?

    1. Completeness
    2. Precision
    3. Consistency Correct answer.
    4. Accessibility

    Explanation

    Consistency requires that the same fact agree across systems and records. Conflicting birth dates for one customer indicate a cross-system consistency defect.

  86. Question 86Data Quality

    A daily risk report must reflect positions as of the previous close, but it is populated with positions that are three days old. Which dimension is failing?

    1. Accuracy
    2. Uniqueness
    3. Timeliness Correct answer.
    4. Completeness

    Explanation

    Timeliness measures whether data is sufficiently current for its intended use. Positions three days old cannot support a report requiring previous-close values.

  87. Question 87Data Quality

    During profiling, an analyst finds that a country field contains 'US', 'USA', 'U.S.', and 'United States'. Which action best addresses this finding?

    1. Increase the field length to accommodate all variants
    2. Delete the field because it is unreliable
    3. Standardize the values against a reference list and add a validity rule Correct answer.
    4. Add a duplicate-check rule on customer name

    Explanation

    The variants represent a validity and standardization problem that a reference data list and rule can control. Standardization plus an allowed-value rule prevents future variants.

  88. Question 88Data Quality

    What distinguishes a data quality dimension from a data quality metric?

    1. A dimension is quantitative, while a metric is qualitative
    2. A metric is defined once and never revised
    3. A dimension is a category of quality, while a metric is a quantified measurement of it Correct answer.
    4. A dimension applies only to unstructured data

    Explanation

    Dimensions such as completeness and accuracy are categories used to organize quality expectations. Metrics are the quantified indicators, such as a percentage, that measure performance within a dimension.

  89. Question 89Data Quality

    A team sets a completeness threshold of 98 percent but has never validated that the measure counts the right records. What is the most significant risk?

    1. The dimension will change from completeness to accuracy
    2. The rule will run too slowly
    3. The threshold will be too easy to meet
    4. The metric may be measuring the wrong population and mislead decisions Correct answer.

    Explanation

    A metric is only meaningful if its population and definition match the intended business question. An unvalidated population can produce a confident but misleading score.

  90. Question 90Data Quality

    Which of the following best describes the role of a data steward in data quality management?

    1. Writing application code for data pipelines
    2. Approving the annual IT budget for data platforms
    3. Performing external audit of financial statements
    4. Defining and monitoring quality rules for a domain and resolving issues Correct answer.

    Explanation

    Data stewards own quality expectations for a subject area, define rules, monitor results, and drive issue resolution. They connect business definitions with technical implementation.

  91. Question 91Data Quality

    A data quality issue log records the issue, its affected data, severity, owner, and status. Why is the owner field essential?

    1. It replaces the need for a root cause analysis
    2. It establishes accountability for resolution and follow-up Correct answer.
    3. It determines the database schema for the issue
    4. It automatically corrects the defective records

    Explanation

    Assigning an owner creates clear accountability for investigating and resolving the issue. Without ownership, issues tend to remain open and unaddressed.

  92. Question 92Data Quality

    Which approach best prevents defective data from entering a system at the point of capture?

    1. Reporting defects to executives quarterly
    2. Input validation with allowed values and format checks at entry Correct answer.
    3. Periodic cleansing of the warehouse after loading
    4. Increasing storage capacity for the dataset

    Explanation

    Preventive controls at the point of capture stop defects before they propagate downstream. Input validation enforces format and domain rules when data is created.

  93. Question 93Data Quality

    An analyst compares a sample of system addresses against verified postal records and finds a 6 percent mismatch rate. Which dimension is being assessed?

    1. Completeness
    2. Timeliness
    3. Accuracy Correct answer.
    4. Uniqueness

    Explanation

    Accuracy assesses whether values correctly represent the real-world fact. Comparing stored addresses to verified references directly tests correctness.

  94. Question 94Data Quality

    Which pair of activities best represents the difference between data cleansing and data quality monitoring?

    1. Cleansing corrects existing defects; monitoring detects and reports defects over time Correct answer.
    2. Cleansing is a governance council duty; monitoring is a help-desk duty
    3. Cleansing applies only to unstructured data; monitoring applies only to structured data
    4. Cleansing designs schemas; monitoring writes ETL code

    Explanation

    Cleansing is corrective work on existing records, whereas monitoring runs ongoing checks that detect and report defects. Together they address both remediation and sustained control.

  95. Question 95Data Quality

    A quality rule flags a field as invalid whenever it is null, but the field is legitimately optional for some customer types. What is the best correction?

    1. Remove the rule entirely
    2. Lower the severity of all quality issues
    3. Change the field to a numeric type
    4. Scope the rule to the customer types for which the field is mandatory Correct answer.

    Explanation

    Rules should reflect the business context in which a value is required. Scoping the rule to mandatory cases preserves control without generating false positives.

  96. Question 96Data Quality

    Which statement best captures the relationship between data quality and fitness for purpose?

    1. Data is high quality when it is stored in the newest database technology
    2. Data is high quality when it satisfies the requirements of its intended use Correct answer.
    3. Data is high quality when it contains no null values anywhere
    4. Data is high quality when it is duplicated across many systems

    Explanation

    Quality is judged relative to use: data must meet the expectations of the process or decision it supports. The same dataset can be fit for one purpose and unfit for another.

  97. Question 97Data Quality

    A dashboard shows a completeness score of 99 percent, yet downstream users report frequent missing key attributes. Which explanation is most plausible?

    1. The metric averages across all attributes, masking a low score on critical fields Correct answer.
    2. The dashboard is using the wrong color scheme
    3. The users are misreading the dashboard
    4. Completeness is not a real quality dimension

    Explanation

    An aggregate score can hide poor performance on individual critical attributes. Segmenting the metric by field and criticality would reveal the gap users experience.

  98. Question 98Data Quality

    An organization wants to establish a baseline before setting quality targets. Which sequence is most defensible?

    1. Deploy cleansing, set targets, and skip profiling
    2. Set aggressive targets, then profile data to justify them
    3. Set targets first, deploy cleansing, then define metrics
    4. Profile the data, define rules and metrics, measure the baseline, then set targets Correct answer.

    Explanation

    A defensible baseline requires understanding the data through profiling, then defining measurable rules and metrics before targets are set. Targets grounded in an actual baseline are achievable and credible.

  99. Question 99Data Quality

    A defect originates in a source system whose owners refuse to change the process, so the warehouse applies a correction rule at load. What is the main long-term risk of this pattern?

    1. The downstream fix masks the root cause and the source continues generating defects Correct answer.
    2. The warehouse will run out of storage
    3. The correction rule will improve source quality over time
    4. The source system will automatically standardize its data

    Explanation

    Downstream correction treats symptoms while the originating process keeps producing defects. The root cause remains, so effort is spent repeatedly and source quality does not improve.

  100. Question 100Data Quality

    Which design choice best supports sustainable data quality across a large enterprise?

    1. Centralizing all correction in one late-stage cleansing job
    2. Embedding quality checks at each layer with clear ownership and feedback to sources Correct answer.
    3. Relying on periodic manual audits of printed reports
    4. Allowing each team to define conflicting definitions of the same metric

    Explanation

    Embedding checks throughout the pipeline with clear ownership catches defects early and routes feedback to their origin. This distributed control model scales better than a single late cleansing step.

  101. Question 101Data Governance

    In a data governance operating model, what is the primary accountability of a data owner for a domain such as Customer?

    1. Performing the annual external audit of financial statements
    2. Writing every data transformation rule used in the warehouse ETL pipelines
    3. Approving access requests and resolving escalated data quality issues for the domain Correct answer.
    4. Administering the physical database servers that host the domain tables

    Explanation

    A data owner is an accountable business role that decides on access, quality standards, and issue escalation for a defined data domain. Technical build and server administration are delegated to stewards and platform teams, while external audit is outside the governance operating model.

  102. Question 102Data Governance

    Which artifact most directly records the business definition, approved values, and ownership of a critical data element?

    1. The capacity plan for the reporting database
    2. The change management ticket for a firewall rule
    3. The business glossary entry linked to a data dictionary attribute Correct answer.
    4. The disaster recovery runbook for the core banking system

    Explanation

    A business glossary captures approved business definitions and ownership, and linking it to data dictionary attributes ties the term to physical implementation. Runbooks, capacity plans, and firewall tickets describe operational infrastructure rather than semantic definitions.

  103. Question 103Data Governance

    A regulator requires the organization to demonstrate who accessed sensitive customer records and why. Which governance capability primarily provides this evidence?

    1. Audit logging of access events with purpose-of-use capture Correct answer.
    2. Data lineage visualization of ETL jobs
    3. Data quality profiling of customer attributes
    4. Master data consolidation of customer records

    Explanation

    Demonstrating who accessed records and for what purpose requires access audit logs that record identity and declared purpose of use. Lineage shows data flow, master data consolidation removes duplication, and profiling measures quality, none of which prove access accountability.

  104. Question 104Data Governance

    Which statement best distinguishes data stewardship from data ownership in a governance framework?

    1. Stewards approve the enterprise data strategy, while owners execute the budget
    2. Owners and stewards are interchangeable titles used for the same business role
    3. Owners are accountable decision-makers for the domain, while stewards execute quality and definition activities day to day Correct answer.
    4. Stewards hold legal accountability for the domain, while owners perform daily quality checks

    Explanation

    Ownership carries accountability for decisions such as access and standards, whereas stewardship is the hands-on execution of quality monitoring, definition maintenance, and issue triage. The two roles are complementary and are not interchangeable.

  105. Question 105Data Governance

    A data governance council is deciding whether to fund a new enterprise data catalog. Which action best reflects a policy-driven governance decision?

    1. Defer the decision until the vendor offers a discount
    2. Assign the decision to the IT service desk team
    3. Let each business unit independently buy whichever catalog tool it prefers
    4. Assess the proposal against approved metadata management policy and prioritize it against the governance roadmap Correct answer.

    Explanation

    A governance council makes decisions by applying approved policies and prioritization criteria, ensuring alignment with the enterprise roadmap. Fragmented per-unit purchasing or price-driven deferral undermines consistent standards.

  106. Question 106Data Governance

    Which metric best indicates whether a data governance program is achieving adoption rather than merely existing on paper?

    1. The percentage of critical data elements with assigned, active owners and current definitions Correct answer.
    2. The number of pages in the published data governance charter
    3. The number of meetings scheduled by the governance council
    4. The total headcount of the data governance office

    Explanation

    Adoption is demonstrated when critical data elements actually have active owners and maintained definitions, showing the model operates in practice. Counting charter pages, staff, or meetings measures activity and artifacts rather than effective adoption.

  107. Question 107Data Governance

    Under a data classification policy, which combination of controls is most appropriate for data classified as restricted?

    1. Access granted to contractors by default for convenience
    2. Open access for all staff with no logging
    3. Access limited to a named group with encryption and detailed access logging Correct answer.
    4. Access available to any authenticated user with quarterly review

    Explanation

    Restricted data requires the tightest practical controls, typically least-privilege named access combined with encryption and detailed logging for accountability. Broader access models conflict with the risk profile that defines the restricted tier.

  108. Question 108Data Governance

    An organization wants a single accountable forum to resolve cross-domain data conflicts such as competing customer definitions. Which structure is designed for that purpose?

    1. The external penetration testing vendor
    2. The data governance council with cross-functional representation Correct answer.
    3. The application development scrum team
    4. The infrastructure change advisory board

    Explanation

    A data governance council brings together cross-functional stakeholders with authority to arbitrate definitions and resolve conflicts across domains. Infrastructure boards, delivery teams, and external testers lack the mandate for semantic arbitration.

  109. Question 109Data Governance

    A data governance policy states that all critical data elements must have documented lineage before being used in regulatory reports. Which response best demonstrates policy enforcement?

    1. Report developers self-certify that lineage probably exists
    2. Lineage is captured only after the regulator raises a query
    3. A gate in the report release process blocks publication until lineage is documented and reviewed Correct answer.
    4. Lineage documentation is a recommended best practice with no verification

    Explanation

    Enforcement requires a control point that prevents non-compliant use, such as a release gate that verifies lineage before publication. Self-certification without evidence and after-the-fact capture do not enforce the policy.

  110. Question 110Data Governance

    Which is the most appropriate first step when a business unit disputes the accuracy of a KPI reported from the enterprise warehouse?

    1. Rebuild the warehouse from scratch
    2. Remove the KPI from the executive dashboard
    3. Ask the vendor to patch the reporting tool
    4. Log the dispute as a data quality issue and trace the KPI definition and lineage to its source Correct answer.

    Explanation

    Disputes are handled through the issue management process, which records the problem and uses definitions and lineage to locate the root cause. Rebuilding, hiding, or blaming tools bypasses diagnosis and leaves the underlying defect unresolved.

  111. Question 111Data Governance

    Which statement best describes the relationship between a data policy and a data standard?

    1. A policy states mandatory principles and direction, while a standard specifies the mandatory rules and formats that implement it Correct answer.
    2. A standard states high-level principles, while a policy lists technical formats
    3. Policies and standards are optional guidance with identical scope
    4. A standard is a one-off project plan that expires when the project closes

    Explanation

    Policies set mandatory direction and principles, and standards translate that direction into specific, enforceable rules such as formats and naming conventions. This hierarchy keeps intent separate from implementation detail.

  112. Question 112Data Governance

    A new privacy regulation requires that personal data be deleted on request across all systems. Which governance artifact should be updated first to drive consistent execution?

    1. The data model diagram for the marketing schema
    2. The retention and disposal policy with linked procedures and system inventory Correct answer.
    3. The team's agile sprint backlog
    4. The network topology diagram

    Explanation

    A deletion obligation is a retention and disposal matter, so the policy and its procedures must be updated and applied across the inventoried systems holding the data. Schema diagrams, backlogs, and topology maps do not carry the mandate for compliant disposal.

  113. Question 113Data Governance

    Which practice best supports a defensible data ethics review before launching an analytics model that scores customers?

    1. Launching the model and reviewing concerns only if complaints arise
    2. Documenting the model's purpose, potential bias, and affected parties for review by a designated ethics body Correct answer.
    3. Restricting review to the model's code quality checks
    4. Relying solely on the vendor's marketing claims about fairness

    Explanation

    Ethics review requires documented assessment of purpose, bias risk, and impact on affected parties, evaluated by a body with the mandate to approve or reject. Reactive review or narrow technical checks fail to address ethical risk.

  114. Question 114Data Governance

    Which role is typically responsible for maintaining the business glossary and coordinating definition changes with data owners?

    1. The chief information security officer
    2. The external auditor
    3. The network operations engineer
    4. The data steward Correct answer.

    Explanation

    Data stewards maintain glossary content and coordinate proposed definition changes with the accountable owners. Security leadership, auditors, and network engineers have different mandates unrelated to glossary curation.

  115. Question 115Data Governance

    An organization finds the same customer appears with three different identifiers across CRM, billing, and support systems. Which governance initiative most directly addresses this?

    1. A code review standard for application developers
    2. A data visualization refresh of the executive dashboard
    3. A backup and restore testing schedule
    4. A master data management program defining a governed golden record and cross-reference Correct answer.

    Explanation

    Master data management establishes governed identifiers and a golden record with cross-references to reconcile duplicates across systems. Dashboards, backup testing, and code reviews do not resolve entity identity conflicts.

  116. Question 116Data Governance

    Which statement best captures the purpose of a data governance maturity assessment?

    1. It benchmarks current capabilities against a defined model to prioritize improvement actions Correct answer.
    2. It replaces the need for data policies
    3. It certifies that the organization has no remaining data issues
    4. It measures only the number of data stewards employed

    Explanation

    A maturity assessment evaluates current capabilities against a reference model and identifies gaps to prioritize improvement. It is a planning instrument, not a certification of perfection, and does not substitute for policy.

  117. Question 117Data Governance

    A business glossary contains a term 'Active Customer' with two conflicting definitions submitted by sales and finance. What is the most governance-appropriate resolution?

    1. Escalate to the data governance council to agree one approved enterprise definition with owner sign-off Correct answer.
    2. Delete the term entirely to avoid conflict
    3. Keep both definitions and let report authors choose whichever they prefer
    4. Let the IT team select the definition that is easiest to implement

    Explanation

    Conflicting definitions are arbitrated by the governance body with authority to approve a single enterprise definition and record owner sign-off. Allowing per-user choice or unilateral technical selection perpetuates inconsistency.

  118. Question 118Data Governance

    Which control best supports the principle of least privilege for access to a sensitive data domain?

    1. Granting broad access to speed up onboarding
    2. Relying on users to report when they no longer need access
    3. Sharing a single service account among the analytics team
    4. Role-based access reviewed periodically with removal of entitlements no longer required Correct answer.

    Explanation

    Least privilege is sustained through role-based provisioning combined with periodic recertification that removes stale entitlements. Broad grants, shared accounts, and self-reporting all undermine accountability and minimal access.

  119. Question 119Data Governance

    Which outcome most clearly shows that data governance has been embedded into project delivery rather than bolted on afterward?

    1. Data ownership and quality requirements are defined as entry criteria in the delivery lifecycle Correct answer.
    2. Governance reviews occur only after systems go live
    3. Data issues are logged but never assigned to owners
    4. The governance team is consulted only during audits

    Explanation

    Embedding governance means data requirements such as ownership and quality criteria are built into delivery stage gates before go-live. Post-implementation review or unassigned issues indicate governance is peripheral.

  120. Question 120Data Governance

    An organization must show regulators that a reported figure can be traced from the report back to its original source and transformations. Which governance capability is central to this requirement?

    1. Data lineage covering report, transformation, and source layers Correct answer.
    2. Data masking of sensitive fields
    3. Data archiving of historical reports
    4. Data quality dashboards showing defect counts

    Explanation

    End-to-end lineage documents the path from report to source including each transformation, which is what traceability for regulatory reporting requires. Archiving, defect dashboards, and masking serve different purposes.

  121. Question 121Data Governance

    A data governance team wants to prioritize remediation of critical data elements. Which approach is most defensible?

    1. Score elements by business impact and current quality, then sequence work by that combined score Correct answer.
    2. Wait for a regulator to identify which elements matter
    3. Remediate only the elements that are cheapest to fix
    4. Remediate elements alphabetically to keep the plan simple

    Explanation

    Prioritization should combine business criticality with measured quality gaps so effort targets the highest risk and value. Alphabetical, cost-only, or reactive sequencing ignores impact and can leave serious risks unaddressed.

  122. Question 122Data Governance

    Which statement best explains why a data governance charter should define decision rights?

    1. Decision rights transfer all accountability to the IT department
    2. Decision rights remove the need for data stewards
    3. Decision rights clarify who can approve changes and resolve disputes, preventing stalled or duplicated decisions Correct answer.
    4. Decision rights guarantee that no data quality issues will occur

    Explanation

    Decision rights specify authority for approvals and dispute resolution, which prevents deadlock and inconsistent decisions. They do not eliminate quality issues, replace stewards, or shift accountability to IT.

  123. Question 123Data Governance

    Which artifact most directly supports demonstrating compliance with a data retention schedule across systems?

    1. A vendor contract renewal calendar
    2. A list of report subscriptions
    3. A training attendance register
    4. A system-level data inventory mapped to retention rules with disposal evidence Correct answer.

    Explanation

    Compliance with retention requires knowing which systems hold which data and retaining evidence that disposal occurred per the rules. Subscription lists, training registers, and contract calendars do not document retention execution.

  124. Question 124Data Governance

    A governance program reports high policy publication counts but low business engagement. Which diagnosis is most plausible?

    1. Policies are being treated as documents to publish rather than instruments requiring adoption, training, and enforcement Correct answer.
    2. The governance council has too much decision authority
    3. The organization has too few policies and needs to publish more
    4. Business units are fully compliant and engagement is unnecessary

    Explanation

    High publication with low engagement suggests the program measures output rather than adoption and lacks training, incentives, and enforcement. Publishing more documents or assuming compliance would not address the gap.

  125. Question 125Data Governance

    Which statement best describes the role of a data domain in organizing governance accountability?

    1. A domain is a physical database instance on a specific server
    2. A domain is a synonym for a reporting dashboard
    3. A domain groups related data subject areas under a single accountable owner for standards and quality Correct answer.
    4. A domain is a temporary project team disbanded after go-live

    Explanation

    Domains group related subject areas so that one accountable owner can govern definitions, quality, and access consistently. They are organizational constructs, not temporary teams, physical servers, or dashboards.

  126. Question 126Data Warehousing & Business Intelligence

    In dimensional modeling, which schema places a single fact table at the center with denormalized dimension tables joined directly to it?

    1. Snowflake schema
    2. Data vault
    3. Third normal form schema
    4. Star schema Correct answer.

    Explanation

    A star schema keeps each dimension as a single denormalized table joined directly to the central fact table, which minimizes join depth and simplifies query writing for BI tools. Snowflake schemas normalize dimensions into hierarchies, while data vault and 3NF designs serve different modeling goals.

  127. Question 127Data Warehousing & Business Intelligence

    A retail fact table stores one row per product per store per day, with additive columns for units sold, revenue, and discount amount. Which term best describes these columns?

    1. Surrogate keys
    2. Natural keys
    3. Degenerate dimensions
    4. Measures Correct answer.

    Explanation

    Numeric, additive columns stored in a fact table and aggregated across dimensions are measures. Keys identify dimension members, while degenerate dimensions are dimension attributes stored in the fact table itself.

  128. Question 128Data Warehousing & Business Intelligence

    Which slowly changing dimension technique preserves full history by inserting a new row with a new surrogate key and effective dates whenever an attribute changes?

    1. Type 1 overwrite
    2. Type 3 previous-value column
    3. Type 0 retention
    4. Type 2 versioning Correct answer.

    Explanation

    Type 2 adds a new dimension row for each change, carrying new surrogate keys plus effective and expiry dates so historical fact rows still resolve to the attribute values in force at the time. Type 1 overwrites history, Type 3 keeps a limited prior-value column, and Type 0 never changes the attribute.

  129. Question 129Data Warehousing & Business Intelligence

    An analyst needs a report that aggregates sales by region and quarter with subtotals for each region and a grand total. Which SQL feature produces these subtotal rows in a single result set?

    1. Common table expressions
    2. WINDOW functions
    3. GROUPING SETS Correct answer.
    4. HAVING

    Explanation

    GROUPING SETS lets one query compute multiple aggregation levels, such as region-by-quarter plus region subtotals plus a grand total, in a single pass. HAVING filters groups, window functions compute values without collapsing rows, and CTEs are named subqueries rather than a subtotal mechanism.

  130. Question 130Data Warehousing & Business Intelligence

    Which OLAP operation reduces a cube by selecting a single value on one dimension, such as fixing the time dimension to a single year?

    1. Slice Correct answer.
    2. Roll-up
    3. Drill-across
    4. Pivot

    Explanation

    Slicing fixes one dimension to a single member, producing a sub-cube of lower dimensionality. Roll-up aggregates to a coarser level, drill-across combines separate cubes, and pivot rotates the presentation axes.

  131. Question 131Data Warehousing & Business Intelligence

    In a Kimball bus matrix, what does a mark in the intersection of a business process row and a dimension column signify?

    1. The dimension has no surrogate key
    2. The dimension is conformed across that process Correct answer.
    3. The process is out of scope
    4. The dimension is a junk dimension

    Explanation

    The bus matrix maps business processes against shared dimensions, and a mark indicates that the process uses that conformed dimension, enabling integrated cross-process analysis. It is a planning artifact for enterprise consistency, not a statement about keys or scope exclusions.

  132. Question 132Data Warehousing & Business Intelligence

    Which type of fact table records the state of an entity at a point in time, such as the current balance of every account at month end?

    1. Periodic snapshot fact table Correct answer.
    2. Factless fact table
    3. Transactional fact table
    4. Accumulating snapshot fact table

    Explanation

    A periodic snapshot captures standardized measures at regular intervals, such as month-end balances for every account. Transactional facts record individual events, accumulating snapshots track a process through milestones, and factless tables record event occurrences without measures.

  133. Question 133Data Warehousing & Business Intelligence

    Which architecture layer stores integrated, subject-oriented, historical data intended for enterprise reporting rather than day-to-day transactions?

    1. Change data capture buffer
    2. Operational data store
    3. Staging area
    4. Enterprise data warehouse Correct answer.

    Explanation

    An enterprise data warehouse holds integrated, subject-oriented, time-variant data for analysis across the organization. Operational data stores support near-real-time operational needs, staging areas are transient landing zones, and CDC buffers feed incremental loads.

  134. Question 134Data Warehousing & Business Intelligence

    A BI team must report on orders that have no matching customer record in the dimension because the source system delivered late. Which warehouse technique keeps the fact rows loadable while flagging the issue?

    1. Delete the dimension table
    2. Convert the fact table to third normal form
    3. Assign an inferred or unknown member key Correct answer.
    4. Drop the orphan fact rows

    Explanation

    An inferred or unknown dimension member provides a valid surrogate key for unresolved business keys so facts load without loss and can be reconciled later. Dropping facts loses revenue, and altering the schema does not address referential integrity.

  135. Question 135Data Warehousing & Business Intelligence

    A data mart must combine sales and returns facts that share the same date, product, and store dimensions. Which design approach supports this cleanly?

    1. Merge both facts into one table with all possible columns
    2. Build two fact tables using conformed dimensions Correct answer.
    3. Create a snowflaked dimension for each fact
    4. Store returns in a separate database with different keys

    Explanation

    Using conformed dimensions lets separate fact tables at different grains be drilled across and compared consistently. Merging facts with incompatible grains creates sparse, ambiguous rows, while divergent keys or duplicated dimensions block integration.

  136. Question 136Data Warehousing & Business Intelligence

    An ETL process loads fact rows before the corresponding new dimension rows have been inserted. What is the most likely immediate consequence?

    1. Aggregates are silently doubled
    2. Dimension surrogate keys are regenerated
    3. Facts are automatically rejected by the database
    4. Fact-to-dimension joins return nulls or missing rows Correct answer.

    Explanation

    If facts reference surrogate keys that do not yet exist in the dimension, inner joins drop those facts and outer joins yield null attributes, producing incomplete reports. Load ordering or late-arriving dimension handling is required to prevent this.

  137. Question 137Data Warehousing & Business Intelligence

    A dimension table has grown to include many low-cardinality flags such as order channel, payment type, and gift-wrap indicator. Which modeling technique reduces dimension width while keeping them queryable?

    1. Group them into a junk dimension Correct answer.
    2. Move them into the fact table as measures
    3. Replace them with a degenerate dimension
    4. Split each flag into its own dimension table

    Explanation

    A junk dimension combines unrelated low-cardinality flags and indicators into one small dimension, limiting dimension count and table width. Splitting each flag multiplies joins, flags are not additive measures, and a degenerate dimension is typically a single identifier kept in the fact table.

  138. Question 138Data Warehousing & Business Intelligence

    A report shows total revenue that is exactly double the expected amount after a new dimension attribute was added to the query. Which phenomenon most likely explains this?

    1. Fan-out caused by a one-to-many join Correct answer.
    2. Aggregate navigation
    3. Late-arriving facts
    4. Slowly changing dimension Type 2 history

    Explanation

    Joining a fact table to a dimension at a finer grain than the fact, or through a one-to-many relationship, duplicates fact rows and inflates sums. This fan-out or chasm trap is corrected by aggregating before the join or by using a bridge table.

  139. Question 139Data Warehousing & Business Intelligence

    Which approach best supports near-real-time dashboards while protecting the warehouse from heavy ad hoc analytical scans?

    1. Publish curated aggregate tables refreshed incrementally for dashboards Correct answer.
    2. Point all dashboards directly at the source OLTP system
    3. Require analysts to rerun full historical reloads nightly
    4. Disable indexing on the fact table

    Explanation

    Publishing curated aggregate or summary tables refreshed incrementally isolates dashboard workloads from expensive detail scans and reduces latency. Querying OLTP directly adds production risk, full reloads increase latency, and removing indexes degrades performance.

  140. Question 140Data Warehousing & Business Intelligence

    A BI developer needs a metric that returns the count of distinct customers who purchased in the trailing 90 days as of each reporting date. Which technique computes this efficiently?

    1. A cross join to a calendar table without filtering
    2. A correlated subquery executed per report row
    3. A HAVING clause on the customer dimension
    4. A window function with a date range frame Correct answer.

    Explanation

    A window function with a RANGE frame over dates computes rolling distinct counts or aggregates per row without repeated scans. Correlated subqueries per row are costly, unfiltered cross joins explode row counts, and HAVING filters groups rather than computing rolling metrics.

  141. Question 141Data Warehousing & Business Intelligence

    A team is choosing between an Inmon-style corporate warehouse with dependent data marts and a Kimball dimensional approach. Which statement correctly distinguishes them?

    1. Inmon builds normalized enterprise integration first, then derives marts; Kimball builds conformed dimensional marts that integrate via the bus matrix Correct answer.
    2. Both approaches prohibit conformed dimensions
    3. Kimball requires third normal form throughout, while Inmon requires star schemas
    4. Inmon focuses only on real-time streaming, while Kimball focuses only on batch

    Explanation

    Inmon advocates a normalized, integrated enterprise warehouse from which dependent marts are derived, while Kimball builds dimensional marts unified by conformed dimensions and the bus matrix. The other statements invert or misstate these characteristics.

  142. Question 142Data Warehousing & Business Intelligence

    Which data warehouse testing practice verifies that fact rows reconcile to source system totals after a load?

    1. Balance and control reconciliation checks Correct answer.
    2. Load testing of concurrent user sessions
    3. Code review of ETL scripts
    4. Unit testing of stored procedures only

    Explanation

    Balance and control checks compare record counts and measure totals between source and target to detect loss, duplication, or transformation errors. Unit tests, code review, and load testing address code correctness and performance but not data completeness.

  143. Question 143Data Warehousing & Business Intelligence

    A dimension contains a hierarchy of product category, subcategory, and product. Analysts frequently aggregate at category level. Which physical design most directly accelerates this?

    1. Removing the product-level key
    2. Storing product names as free text in the fact table
    3. Adding a materialized aggregate table keyed by category Correct answer.
    4. Converting the dimension to a factless fact table

    Explanation

    A materialized aggregate table precomputes sums at the frequently queried category grain, letting the optimizer or BI tool answer from a much smaller table. The other options either break the hierarchy or add redundancy without improving aggregation.

  144. Question 144Data Warehousing & Business Intelligence

    A team is evaluating an ELT pattern where transformations run inside a cloud columnar warehouse. Which benefit most directly justifies this pattern?

    1. It leverages warehouse compute scalability and set-based SQL for transformations Correct answer.
    2. It removes the need for data quality checks
    3. It eliminates the need for any data modeling
    4. It guarantees zero transformation errors

    Explanation

    ELT pushes transformations into the warehouse, exploiting elastic compute and set-based SQL over columnar storage. It does not remove modeling, quality checks, or the possibility of transformation errors.

  145. Question 145Data Warehousing & Business Intelligence

    In a data vault model, which component stores the descriptive attributes and their history for a business entity?

    1. Hub
    2. Link
    3. Satellite Correct answer.
    4. Reference table

    Explanation

    Satellites hold descriptive attributes and their change history, attached to hubs or links. Hubs store unique business keys, links record relationships among hubs, and reference tables hold lookup values.

  146. Question 146Data Warehousing & Business Intelligence

    A BI tool issues a query that a precomputed summary table can satisfy exactly at the requested grain. Which optimizer capability selects that summary automatically?

    1. Partition pruning
    2. Predicate pushdown
    3. Aggregate navigation Correct answer.
    4. Star transformation

    Explanation

    Aggregate navigation, also called summary or materialized view matching, rewrites a query to use a precomputed aggregate when the requested grain and filters are covered. Partition pruning skips partitions, predicate pushdown filters earlier, and star transformation rewrites joins.

  147. Question 147Data Warehousing & Business Intelligence

    A fact table must record which students attended which classes even though no numeric measure exists for attendance. Which design is appropriate?

    1. A junk dimension of attendance codes
    2. A factless fact table with dimension keys only Correct answer.
    3. A Type 3 attendance flag on the class dimension
    4. A snowflaked student dimension

    Explanation

    Attendance is an event occurrence without a natural numeric measure, so a factless fact table keyed by student, class, and date supports counting and coverage analysis. The other designs either misplace the event or cannot represent many-to-many attendance.

  148. Question 148Data Warehousing & Business Intelligence

    A warehouse must support both current-state operational reporting and full historical trend analysis on the same customer dimension. Which combination best satisfies both needs without duplicating the entire warehouse?

    1. Type 3 only, with one prior-value column
    2. Type 2 history plus a current-view or latest-version flag Correct answer.
    3. Type 1 only, because it is simplest
    4. No history, with nightly truncation and reload

    Explanation

    Type 2 preserves full history for trend analysis, while a current-record flag or view exposes the latest version for operational reporting from the same table. Type 1 and Type 3 lose history, and nightly truncation destroys it entirely.

  149. Question 149Data Warehousing & Business Intelligence

    A fact table and a dimension both have a date column, and a query joins them only on the date column in addition to the surrogate key, multiplying rows. Which design flaw does this reveal?

    1. A non-unique dimension primary key Correct answer.
    2. An unpartitioned fact table
    3. A missing role-playing dimension alias
    4. A missing bridge table

    Explanation

    If the dimension's key is not unique, joins can multiply rows; a properly enforced unique surrogate key prevents this. Role-playing dimensions concern multiple date roles, partitioning affects performance, and bridge tables handle many-to-many relationships.

  150. Question 150Data Warehousing & Business Intelligence

    Which statement best explains why adding a new source system to a mature Kimball warehouse should reuse existing conformed dimensions rather than create new ones?

    1. It guarantees the new source has no data quality issues
    2. It removes the need for ETL testing
    3. It avoids conflicting dimension keys and enables cross-process drill-across reporting Correct answer.
    4. It eliminates the need for surrogate keys

    Explanation

    Reusing conformed dimensions keeps a single key space and consistent attribute definitions, so facts from different processes can be compared and drilled across. It does not eliminate testing, quality issues, or the need for surrogate keys.

  151. Question 151Reference and Master Data Management

    In reference and master data management, which description best characterizes reference data?

    1. Transactional records generated by daily operational activity
    2. A broad set of interchangeable values that are limited to a single application
    3. A controlled set of values used to classify or categorize other data Correct answer.
    4. A set of values that changes with every business transaction

    Explanation

    Reference data is a controlled vocabulary of permissible values used to classify or categorize other data, such as country codes or status codes. It is relatively static and shared across systems, which distinguishes it from transactional data.

  152. Question 152Reference and Master Data Management

    A retail company maintains a single authoritative record for each customer that is shared by sales, service, and billing systems. This asset is best described as which type of data?

    1. Unstructured data
    2. Master data Correct answer.
    3. Metadata
    4. Reference data

    Explanation

    Master data describes the core business entities, such as customers, products, and suppliers, that are shared across multiple processes and systems. A single authoritative customer record shared by several systems is the defining characteristic of master data.

  153. Question 153Reference and Master Data Management

    Which pair correctly matches a common master data domain with a typical reference data set used to classify it?

    1. Employee master data classified by payroll disbursement transactions
    2. Product master data classified by general ledger journal entries
    3. Customer master data classified by country code reference data Correct answer.
    4. Supplier master data classified by sales order line items

    Explanation

    Reference data provides controlled values that classify master data, and country code is a classic reference data set used to categorize customer records. The other options pair master data with transactional data rather than reference data.

  154. Question 154Reference and Master Data Management

    What is the primary purpose of a master data management hub architecture?

    1. To store only historical transactions for reporting
    2. To provide a central authoritative source that governs and distributes master data Correct answer.
    3. To replace all source systems with a single application
    4. To replicate every operational database in real time without governance

    Explanation

    An MDM hub creates a central, governed, authoritative copy of master data and shares it with consuming systems. It coordinates and improves data quality rather than replacing operational source systems or merely copying transactions.

  155. Question 155Reference and Master Data Management

    An organization needs to consolidate customer records from several systems into a golden record but must keep the source systems operating independently. Which MDM implementation style fits best?

    1. Registry style
    2. Coexistence style
    3. Consolidation style Correct answer.
    4. Centralized style

    Explanation

    A consolidation style hub gathers and cleanses master data to produce a golden record for analysis and reporting while leaving source systems as the systems of record. Registry style only indexes keys, and centralized style makes the hub the system of record.

  156. Question 156Reference and Master Data Management

    Which activity is central to data stewardship in a master data program?

    1. Writing application source code for the MDM hub
    2. Assigning accountability for data quality, definitions, and issue resolution Correct answer.
    3. Managing the physical network and server capacity
    4. Approving the annual IT infrastructure budget

    Explanation

    Data stewards are accountable for the quality, definitions, and correct use of data within their domain, and they resolve data issues. Budget, coding, and infrastructure tasks belong to other roles.

  157. Question 157Reference and Master Data Management

    A customer master record contains a field labeled 'CUST_STAT_CD' with no documented meaning. Which metadata element is missing?

    1. Data lineage showing the field's origin systems
    2. A business definition explaining what the field represents Correct answer.
    3. A retention schedule for the field
    4. A backup and recovery procedure for the database

    Explanation

    A cryptic field name without documented meaning lacks its business definition, which is core metadata needed for correct interpretation and use. Lineage, retention, and backup are separate metadata or operational concerns.

  158. Question 158Reference and Master Data Management

    Which data quality dimension is most directly assessed when checking that every customer master record has a valid, populated country code from the approved list?

    1. Consistency
    2. Timeliness
    3. Uniqueness
    4. Validity Correct answer.

    Explanation

    Validity measures conformance to a defined format or domain of permissible values, such as an approved reference data list. Populated, approved country codes are a validity check against reference data.

  159. Question 159Reference and Master Data Management

    What is the primary role of a data governance council in a master data initiative?

    1. Designing the physical database schema
    2. Performing daily data entry corrections
    3. Setting policies, standards, and decision rights for master data Correct answer.
    4. Running nightly batch extraction jobs

    Explanation

    A governance council provides oversight by setting policies, standards, and decision rights, and by resolving cross-functional data issues. Operational corrections, schema design, and batch jobs are execution activities handled by other teams.

  160. Question 160Reference and Master Data Management

    Two source systems store the same customer with different spellings of the name and different identifiers. Which MDM process determines that these records represent the same real-world entity?

    1. Data archival
    2. Schema versioning
    3. Capacity planning
    4. Identity resolution and matching Correct answer.

    Explanation

    Identity resolution uses matching rules and algorithms to determine when records from different sources refer to the same real-world entity. It is the prerequisite for merging or linking records into a golden record.

  161. Question 161Reference and Master Data Management

    A team merges duplicate customer records but keeps a cross-reference table linking each source identifier to the surviving golden record. What is this cross-reference table called?

    1. A star schema
    2. A change log
    3. A data dictionary
    4. A crosswalk or identity mapping Correct answer.

    Explanation

    A crosswalk, also called an identity mapping or cross-reference, preserves the links between source identifiers and the consolidated master record. It enables traceability back to originating systems.

  162. Question 162Reference and Master Data Management

    What distinguishes a master data 'golden record' from a simple copy of the most recent source record?

    1. It is stored only in the system that created it
    2. It is always the record with the earliest creation timestamp
    3. It is the record with the most free-text fields
    4. It is a governed, trusted version that reconciles and survives changes in source systems Correct answer.

    Explanation

    A golden record is a governed, trusted representation of a master entity that reconciles data across sources and persists even if individual source systems change. It is not simply the newest or oldest copy.

  163. Question 163Reference and Master Data Management

    Which is a typical challenge that drives the need for master data management?

    1. A single application serving all business functions
    2. Uniform data definitions across all systems
    3. Multiple systems of entry creating inconsistent versions of the same entity Correct answer.
    4. Complete absence of data quality issues

    Explanation

    When multiple systems independently create and maintain the same entity, inconsistent versions proliferate, which is a core driver for MDM. Uniform definitions and a single application would reduce rather than create the need.

  164. Question 164Reference and Master Data Management

    A product master record must be shared with an e-commerce site, a warehouse system, and a finance system. Which MDM capability ensures each consuming system receives the data in the structure it requires?

    1. Data archival services
    2. Source code version control
    3. Data distribution and synchronization services Correct answer.
    4. Network load balancing

    Explanation

    Distribution and synchronization services publish master data to consuming systems, often transforming it into each target's required format. This ensures consistent, timely delivery of governed master data.

  165. Question 165Reference and Master Data Management

    What is the main purpose of defining data ownership for a master data domain such as supplier data?

    1. To guarantee that no data quality defects will occur
    2. To assign one accountable party who approves changes and resolves conflicts Correct answer.
    3. To transfer all technical support duties to the business unit
    4. To eliminate the need for data stewards

    Explanation

    Data ownership assigns accountability to a defined party who approves changes and arbitrates conflicts for the domain. It establishes decision rights but does not remove the need for stewards or guarantee defect-free data.

  166. Question 166Reference and Master Data Management

    An organization adopts a centralized MDM style. What is the most significant consequence for the source systems?

    1. The hub becomes the system of record and source systems consume master data from it Correct answer.
    2. Reference data is no longer needed anywhere
    3. Source systems must be decommissioned immediately
    4. Source systems become read-only for all users

    Explanation

    In a centralized style, the hub is the authoritative system of record and source systems consume master data from it. This shifts authority to the hub but does not require immediate decommissioning or make source systems read-only.

  167. Question 167Reference and Master Data Management

    Which reference data management practice best prevents divergent code values from spreading across systems?

    1. Allowing business users to edit codes directly in production tables
    2. Letting each application define its own local code list
    3. Removing all validation rules to increase flexibility
    4. Centralizing stewardship and controlled publication of the code set Correct answer.

    Explanation

    Central stewardship with controlled publication ensures a single authoritative code set is distributed consistently. Local definitions, unmanaged edits, and absent validation are exactly what cause divergence.

  168. Question 168Reference and Master Data Management

    What does a data lineage capability contribute to a master data program?

    1. It documents where master data originated and how it moved and transformed Correct answer.
    2. It automatically corrects all data quality defects
    3. It encrypts master data at rest
    4. It defines the pricing of data storage

    Explanation

    Lineage traces the origin, movement, and transformation of data across systems, supporting impact analysis and trust. It does not itself encrypt data, fix defects, or set storage pricing.

  169. Question 169Reference and Master Data Management

    A customer service representative finds two active customer records for the same person and needs a governed way to merge them. Which control should the MDM process provide?

    1. An unmonitored manual delete of one record
    2. A merge workflow with approval and audit trail Correct answer.
    3. A bulk update script run without review
    4. A request to disable all uniqueness checks

    Explanation

    Merging master records should follow a controlled workflow with approval and an audit trail so the action is traceable and reversible. Unmonitored deletes, unreviewed scripts, and disabled checks undermine governance.

  170. Question 170Reference and Master Data Management

    What is survivorship in master data management?

    1. The process of backing up the hub nightly
    2. The process of retiring old servers
    3. The process of selecting which source value prevails for each attribute in a consolidated record Correct answer.
    4. The process of assigning user access permissions

    Explanation

    Survivorship defines rules that determine which source value is retained for each attribute when records are consolidated. It may use recency, source trust, or completeness as criteria.

  171. Question 171Reference and Master Data Management

    Which metric best indicates the effectiveness of an identity resolution process?

    1. The count of database indexes
    2. The number of servers hosting the MDM hub
    3. The average length of customer names
    4. The rate of false matches and missed matches in consolidated records Correct answer.

    Explanation

    Effective identity resolution minimizes false matches, where different entities are merged, and missed matches, where the same entity stays split. These error rates directly measure matching quality.

  172. Question 172Reference and Master Data Management

    Why is reference data often managed separately from master data in an MDM program?

    1. Reference data cannot be stored in a database
    2. Reference data is a shared classification vocabulary with different lifecycle and governance needs Correct answer.
    3. Reference data changes with every transaction
    4. Reference data is always confidential while master data is public

    Explanation

    Reference data serves as a shared classification vocabulary with its own lifecycle, ownership, and change control, which differ from entity master data. Managing it separately allows appropriate governance for each.

  173. Question 173Reference and Master Data Management

    What does a data dictionary provide to users of a master data hub?

    1. A map of office floor plans
    2. A list of all employees with access to the hub
    3. A schedule of software license renewals
    4. Definitions, formats, and allowed values for each data element Correct answer.

    Explanation

    A data dictionary documents each element's definition, format, and permissible values, which supports consistent interpretation and use. Access lists, license schedules, and floor plans are unrelated to data element semantics.

  174. Question 174Reference and Master Data Management

    An MDM program wants to measure how many source records were successfully linked to a golden record. Which indicator is most appropriate?

    1. Total storage consumed by backups
    2. Match rate of source records to consolidated entities Correct answer.
    3. Count of database administrators on staff
    4. Number of governance meetings held

    Explanation

    Match rate measures the proportion of source records successfully linked to a consolidated entity, directly reflecting resolution coverage. Meeting counts, staffing, and backup storage do not measure linkage success.

  175. Question 175Reference and Master Data Management

    A global company discovers that the same product is recorded under three different unit-of-measure conventions across regions. Which action best addresses this master data inconsistency?

    1. Remove unit-of-measure fields from the product master
    2. Delete all product records and rebuild them manually
    3. Allow each region to keep its own convention with no mapping
    4. Define a standard unit of measure with conversion rules and reference values Correct answer.

    Explanation

    Standardizing the unit of measure with defined conversions and reference values lets regions record data consistently while preserving local usability. Leaving conventions unmapped, deleting records, or removing fields perpetuates or worsens inconsistency.

  176. Question 176Data Integration and Interoperability

    In DAMA-DMBOK terms, which pair correctly distinguishes data integration from interoperability?

    1. Integration is a synonym for data virtualization; interoperability is a synonym for replication
    2. Integration is a governance policy; interoperability is a physical database engine
    3. Integration is the technical movement and consolidation of data; interoperability is the ability of systems to exchange and use shared data meaningfully Correct answer.
    4. Integration concerns only batch ETL; interoperability concerns only data modeling notation

    Explanation

    DAMA-DMBOK frames data integration as the practices that move and consolidate data across sources, while interoperability describes the capability of systems to exchange data and interpret it consistently. The two are related but not identical: you can move data without semantic agreement, and you can agree on semantics without automated pipelines.

  177. Question 177Data Integration and Interoperability

    A team needs near-real-time propagation of committed changes from a source database to a downstream warehouse with minimal source impact. Which integration pattern fits best?

    1. Manual CSV export by business users
    2. Full extract-load-refresh each night
    3. Change data capture reading the transaction log Correct answer.
    4. Point-in-time snapshot replication at month end

    Explanation

    Change data capture reads the database log or journal to capture inserts, updates, and deletes as they commit, giving low latency with modest load on the source. Full refreshes and manual exports are periodic and heavy, and month-end snapshots cannot support near-real-time needs.

  178. Question 178Data Integration and Interoperability

    Which statement best describes the role of an enterprise service bus or message broker in a hub-and-spoke integration architecture?

    1. It mediates messages between producers and consumers so point-to-point connections are reduced Correct answer.
    2. It replaces the need for any data quality rules
    3. It guarantees that all payloads share one canonical schema without mapping
    4. It stores the master copy of every domain entity

    Explanation

    A hub-and-spoke bus or broker decouples producers from consumers, routing and often transforming messages so that each system connects to the hub rather than to every other system. It does not by itself create a master data store, enforce data quality, or eliminate the need for schema mapping.

  179. Question 179Data Integration and Interoperability

    Which ETL/ELT component is responsible for converting source codes such as 'M'/'F' into the target's standard gender domain values?

    1. Extraction
    2. Loading
    3. Scheduling
    4. Transformation Correct answer.

    Explanation

    Transformation applies business and data rules such as standardization, decoding, cleansing, and derivation between extraction and loading. Extraction only retrieves data, loading writes it to the target, and scheduling controls timing rather than value conversion.

  180. Question 180Data Integration and Interoperability

    In a batch extract, records are pulled while transactions are still committing, and some rows reflect partial updates. Which data consistency problem does this illustrate?

    1. Cardinality mismatch
    2. Referential integrity violation
    3. Slowly changing dimension type 2
    4. Dirty read / inconsistent extract Correct answer.

    Explanation

    Reading uncommitted or partially committed data during extraction produces a dirty or inconsistent extract, where values may never have existed as a valid state. Referential integrity concerns orphan keys, cardinality concerns relationship counts, and SCD type 2 is a historization technique rather than a consistency defect.

  181. Question 181Data Integration and Interoperability

    Two systems both store 'customer' but one defines a customer as a billing account and the other as a household. Which integration challenge is primarily at play?

    1. Storage capacity
    2. Licensing cost
    3. Network latency
    4. Semantic heterogeneity Correct answer.

    Explanation

    Semantic heterogeneity arises when the same term carries different meanings or the same concept is represented differently across systems, which is exactly the billing-account versus household conflict. Latency, capacity, and licensing are operational constraints that do not explain divergent definitions of an entity.

  182. Question 182Data Integration and Interoperability

    Which approach best supports interoperability when two systems exchange dates but use different calendar conventions and time zones?

    1. Store dates as free-text strings in each system
    2. Rely on each application's default locale at runtime
    3. Convert all dates to the source system's local time only
    4. Define an interchange format (e.g., ISO 8601 with offset) in the integration contract Correct answer.

    Explanation

    Interoperability requires a shared, unambiguous representation agreed in the interface contract, such as ISO 8601 including time-zone offset. Free-text and locale defaults introduce ambiguity, and normalizing only to the source's local time breaks consumers in other zones.

  183. Question 183Data Integration and Interoperability

    A data architect chooses an ELT pattern on a cloud columnar warehouse. What is the primary rationale for this choice?

    1. ELT guarantees no schema drift will occur
    2. Transformations must run on the source database to reduce cost
    3. ELT eliminates the need for any transformation logic
    4. The warehouse can scale compute for in-database transformation after raw load Correct answer.

    Explanation

    ELT loads raw data first and then transforms it using the target platform's scalable compute, which suits elastic columnar warehouses. It does not remove transformation logic, does not push work back to the source, and does not prevent schema drift.

  184. Question 184Data Integration and Interoperability

    Which statement correctly describes the difference between a data warehouse and a data lake in integration roles?

    1. A warehouse and a lake are identical in every respect
    2. A warehouse typically stores schema-on-write curated data; a lake typically stores raw data with schema-on-read Correct answer.
    3. A warehouse stores only unstructured files; a lake stores only relational tables
    4. A warehouse cannot be queried with SQL; a lake always requires SQL

    Explanation

    Warehouses generally apply schema and curation at load time, while lakes land raw data in various formats and impose structure when read. The other options invert or contradict these well-known characteristics.

  185. Question 185Data Integration and Interoperability

    A slowly changing dimension must preserve full history of attribute changes with effective dates and current-flag columns. Which SCD type is this?

    1. Type 3
    2. Type 1
    3. Type 2 Correct answer.
    4. Type 0

    Explanation

    Type 2 keeps multiple rows per natural key with validity dates and often a current-row indicator, preserving complete history. Type 1 overwrites, Type 3 adds a limited prior-value column, and Type 0 retains the original value permanently.

  186. Question 186Data Integration and Interoperability

    Which technique most directly addresses the 'many-to-many' relationship problem when integrating customer records that share no common key?

    1. Deterministic matching on a single exact identifier
    2. Probabilistic matching with weighted attribute comparison and review thresholds Correct answer.
    3. Forcing a surrogate key from the source system
    4. Deleting all duplicate records without review

    Explanation

    When no reliable common identifier exists, probabilistic (fuzzy) matching scores candidate pairs on multiple attributes and routes uncertain cases to review. Exact matching fails without a shared key, blind deletion is unsafe, and a source surrogate key does not link records across systems.

  187. Question 187Data Integration and Interoperability

    In an integration design, what is the purpose of a canonical data model?

    1. To replace all source systems with one database
    2. To provide a common, technology-neutral representation that reduces N-to-N mappings Correct answer.
    3. To enforce that all systems use identical physical schemas
    4. To store the operational transactions of the source system

    Explanation

    A canonical model gives a shared, neutral target so each system maps once to the canonical form rather than to every other system, reducing N-to-N mapping effort. It does not replace source systems or dictate identical physical schemas.

  188. Question 188Data Integration and Interoperability

    Which interoperability standard is most associated with exchanging healthcare administrative and clinical messages between systems?

    1. HL7 (including FHIR) Correct answer.
    2. XBRL
    3. SWIFT MT messages
    4. ISO 20022

    Explanation

    HL7, and its modern FHIR specification, define healthcare message and resource formats for exchanging clinical and administrative data. SWIFT and ISO 20022 are financial messaging standards, and XBRL is for business financial reporting.

  189. Question 189Data Integration and Interoperability

    A service-oriented integration uses an API gateway. Which capability is most characteristic of this layer?

    1. Replacing the need for a data model
    2. Performing the organization's master data stewardship
    3. Centralizing authentication, rate limiting, and routing for service consumers Correct answer.
    4. Guaranteeing business-rule validation in every payload

    Explanation

    An API gateway handles cross-cutting concerns such as authentication, throttling, and request routing so individual services do not reimplement them. It is not a stewardship function, does not remove the need for data models, and typically does not own business-rule validation.

  190. Question 190Data Integration and Interoperability

    Which statement accurately describes data virtualization compared with physical consolidation?

    1. It eliminates the need for query federation or optimization
    2. It requires that all sources be relational databases
    3. It copies all source data into a central repository nightly
    4. It presents a virtual, query-time view across sources without physically moving all the data Correct answer.

    Explanation

    Data virtualization exposes a logical view that federates queries across sources at run time, avoiding full physical copying. It does not require relational-only sources and still depends on query federation and optimization to perform well.

  191. Question 191Data Integration and Interoperability

    During an integration project, source schemas change frequently without notice, breaking downstream loads. Which governance practice best mitigates this?

    1. Disabling all validation to avoid load failures
    2. Removing metadata documentation to reduce maintenance
    3. Establishing a schema change notification and versioned interface contract process Correct answer.
    4. Allowing each developer to alter source schemas freely

    Explanation

    A versioned interface contract with change notification lets producers and consumers coordinate schema evolution and adapt loads before breakage. Uncontrolled changes, disabled validation, and discarded metadata all increase the risk of silent failures.

  192. Question 192Data Integration and Interoperability

    Which DAMA-DMBOK data integration approach is characterized by moving data in real time as events occur, often using publish/subscribe messaging?

    1. Periodic full refresh
    2. Batch ETL
    3. Event-driven or streaming integration Correct answer.
    4. Manual file transfer

    Explanation

    Event-driven or streaming integration propagates data as events happen, typically through publish/subscribe channels, enabling low-latency consumption. Batch ETL, manual transfer, and periodic refresh all operate on scheduled intervals rather than on events.

  193. Question 193Data Integration and Interoperability

    A data steward asks why an integration must handle deletes explicitly. Which rationale is most accurate?

    1. Deletes are automatically propagated by all integration tools without configuration
    2. Deleting records always improves data quality
    3. Without delete handling, targets retain records that no longer exist in the source, causing divergence Correct answer.
    4. Deletes never affect referential integrity

    Explanation

    Many extraction methods capture inserts and updates but miss deletes, so targets accumulate stale rows unless deletes or soft-delete flags are propagated. Assuming automatic propagation is unsafe, deletes can affect referential integrity, and deletion is not inherently a quality improvement.

  194. Question 194Data Integration and Interoperability

    Which practice best supports reliable idempotent loading in an integration pipeline?

    1. Relying on job start time as the only record identifier
    2. Using a natural or surrogate key with merge/upsert logic so re-runs do not duplicate data Correct answer.
    3. Appending every run's rows without any key or deduplication logic
    4. Disabling transaction control during loads

    Explanation

    Idempotent loads use keys with merge or upsert semantics so that reprocessing the same batch yields the same result without duplicates. Blind appends create duplicates, timestamps are not stable identifiers, and disabling transaction control risks partial loads.

  195. Question 195Data Integration and Interoperability

    In a hub-and-spoke MDM implementation, what is the primary function of the hub?

    1. To act as the system of record for all operational transactions
    2. To eliminate the need for data stewardship
    3. To maintain the consolidated golden record and distribute it to subscribing systems Correct answer.
    4. To replace all data quality tooling

    Explanation

    The MDM hub maintains the consolidated, reconciled golden record and publishes it to subscribers, while source systems often remain systems of record for transactions. The hub does not replace quality tooling or stewardship, which remain essential.

  196. Question 196Data Integration and Interoperability

    Which statement about message delivery semantics in integration is correct?

    1. At-most-once delivery guarantees every message arrives exactly once
    2. At-least-once delivery guarantees no duplicates
    3. Exactly-once delivery is trivially guaranteed by every broker
    4. At-least-once delivery may produce duplicates, so consumers should be idempotent Correct answer.

    Explanation

    At-least-once delivery can redeliver a message after an acknowledgment failure, so consumers must be idempotent to avoid double effects. At-most-once may lose messages, and exactly-once is difficult and not universally guaranteed by all brokers.

  197. Question 197Data Integration and Interoperability

    A team integrates 12 systems pairwise without a canonical model, then adds a 13th system. Which outcome best reflects the scaling problem this creates?

    1. The number of interfaces grows roughly with the square of the number of systems Correct answer.
    2. Interfaces become unnecessary once a 13th system exists
    3. The number of interfaces stays constant regardless of system count
    4. Adding systems reduces the total interface count

    Explanation

    Point-to-point integration produces on the order of n(n-1)/2 interfaces, so growth is roughly quadratic in the number of systems. A canonical or hub model reduces this by mapping each system once. Interface counts do not stay constant, decrease with added systems, or vanish.

  198. Question 198Data Integration and Interoperability

    Which metadata capability is most critical for traceable data integration lineage?

    1. Retaining only the last successful load timestamp
    2. Recording only the names of developers on the project
    3. Capturing source-to-target mappings, transformation logic, and run metadata across each hop Correct answer.
    4. Storing only the final report layout

    Explanation

    End-to-end lineage requires metadata that records source-to-target mappings, the transformations applied, and execution context at each hop so data can be traced backward and forward. Report layouts, staff names, and a single timestamp are far too limited to support traceability.

  199. Question 199Data Integration and Interoperability

    When designing an integration solution, which consideration most directly affects whether to use synchronous request/response versus asynchronous messaging?

    1. The number of developers on the team
    2. Whether the caller can tolerate waiting and how tightly coupled the systems should be Correct answer.
    3. The color scheme of the user interface
    4. The physical size of the data center

    Explanation

    Synchronous request/response suits callers that need an immediate answer and can accept tight coupling, while asynchronous messaging decouples systems and tolerates latency and intermittent availability. UI styling, team size, and data center size do not determine this architectural choice.

  200. Question 200Data Integration and Interoperability

    Which statement best captures why data integration must be governed alongside data quality management?

    1. Integration tools automatically enforce all business rules without governance
    2. Integration moves data across boundaries, so without quality rules and stewardship defects propagate and amplify downstream Correct answer.
    3. Governance slows integration and should be avoided entirely
    4. Data quality is only relevant to reporting, not integration

    Explanation

    Because integration transports data between systems, defects introduced or passed along can be replicated and compounded downstream, so quality rules and stewardship must accompany the pipelines. Tools do not enforce all business rules automatically, quality applies throughout, and governance reduces rather than creates risk.

CDMP flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Data governance definition
The exercise of authority and control over data management through policy, standards, decision rights, and accountability, ensuring data is managed as an asset and complies with obligations.
Data steward role
A domain expert accountable for data definitions, quality rules, and issue resolution within a subject area, working under data owners and often part-time.
Decision rights
The formally assigned authority to make specific data decisions, such as approving definitions, access grants, or quality thresholds, preventing unclear ownership and stalled issues.
Data policy vs standard
A policy states mandatory principles and rules; a standard specifies measurable requirements that implement the policy, while procedures describe how to comply.
Data governance maturity
A staged assessment of governance capability from ad hoc to defined, managed, measured, and optimized, requiring documented processes and assigned accountability at each level.
Conceptual data model
A technology-neutral model of business entities and their relationships, used to communicate scope and meaning with business stakeholders before logical and physical design.
Third normal form
A relational design state where no non-key attribute depends transitively on another non-key attribute, eliminating redundancy that causes update anomalies.
Star schema
A dimensional design with a central fact table joined to denormalized dimension tables, optimizing analytical query performance and business usability.
Slowly changing dimension Type 2
A dimension design that preserves full history by inserting a new row with version or effective dates when an attribute changes, keeping prior versions for point-in-time reporting.
Surrogate key
A system-generated, stable identifier independent of business meaning, used in facts and dimensions to insulate the model from changes in natural business keys.
Fact table grain
The precise business meaning of one row in a fact table, declared before selecting dimensions and measures, ensuring every measure is additive at that level.
Business metadata
Metadata describing business definitions, owners, rules, and glossary terms, enabling users to understand and trust data without technical schema knowledge.
Technical metadata
Metadata describing physical structures, data types, schemas, ETL mappings, and lineage, used by engineers to build, operate, and troubleshoot data pipelines.
Data lineage
The recorded path of data from source to target, including transformations, supporting impact analysis when objects change and root-cause tracing when defects appear.
Business glossary
A governed vocabulary of business terms with definitions, synonyms, owners, and rules, linked to technical metadata so users and systems share consistent meaning.
Data catalog
A searchable user interface over a metadata repository that helps users find data assets, view lineage and definitions, and assess fitness for use.
Data quality dimensions
Measurable aspects of data fitness including completeness, accuracy, consistency, timeliness, uniqueness, validity, and conformity, each requiring an operational definition and measurement method.
Data profiling
The statistical analysis of data columns, such as null rates, distinct counts, ranges, and pattern frequencies, used to discover quality issues before defining rules.
Completeness metric
The ratio of non-null or non-missing values to total values for an attribute, commonly expressed as a percentage and tracked against a defined threshold.
Data cleansing
The process of standardizing, parsing, matching, enriching, and correcting data to meet quality rules, ideally paired with root-cause remediation to prevent recurrence.
Data quality rule types
Categories of validation including completeness, validity, range, pattern, referential integrity, uniqueness, and cross-field consistency, each implemented as an automated check.
Data warehouse definition
A subject-oriented, integrated, time-variant, nonvolatile data store built from operational sources to support management reporting and analytical decision-making.
Conformed dimension
A dimension table with identical structure and content shared across multiple fact tables or data marts, enabling consistent drill-across reporting.
ETL versus ELT
ETL transforms data before loading it into the target warehouse; ELT loads raw data first and transforms inside the target platform, common in cloud data warehouses.
Dependent data mart
A data mart whose data is sourced from the enterprise data warehouse rather than directly from operational systems, reducing inconsistent definitions across marts.
OLAP drill-down
An operation that navigates from a summarized level of a dimension hierarchy to a more detailed level, increasing granularity for analysis.
Reference data
Controlled, relatively static code sets used to classify or categorize other data, such as country codes or status codes, shared across systems and requiring governed change control.
Master data
Core business entities such as customer, product, employee, supplier, and location that are shared across processes and require a single trusted version.
Golden record
The single trusted version of a master entity, produced by survivorship rules that select or merge attribute values from multiple source systems.
MDM registry style
A master data management approach that indexes and links source records without creating a central golden record, leaving source systems authoritative.
Entity resolution
The process of identifying records that refer to the same real-world entity using deterministic keys or probabilistic similarity scoring with tuned thresholds.
Change data capture
A data integration technique that identifies inserts, updates, and deletes since the last run using timestamps, log-based capture, or triggers to move only changed data.

CDMP study guide

Data Management Fundamentals (DMF)

Data Management Fundamentals

This domain tests the vocabulary and framework that the rest of CDMP assumes: what data management is, which functions make it up, and how they interlock. Expect definitional questions, questions that map a business scenario to a DAMA knowledge area, and questions about roles, lifecycle, and maturity.

Core rules and concepts

  • Data management is the development, execution, and supervision of plans, policies, programs, and practices that control, protect, deliver, and enhance the value of data and information assets. It is a business capability, not an IT sub-function.
  • The DAMA-DMBOK wheel has eleven knowledge areas: Data Governance, Data Architecture, Data Modeling and Design, Data Storage and Operations, Data Security, Data Integration and Interoperability, Document and Content Management, Reference and Master Data, Data Warehousing and BI, Metadata, and Data Quality. Data Governance sits at the centre because it provides decision rights and oversight.
  • Environmental elements often called the DAMA framework: goals and principles, data management functions, specialized disciplines, organization and culture, roles, processes, technologies, and metrics.
  • The data lifecycle: Plan, Design, Enable, Maintain, Use, Enhance, Dispose. It is iterative, not a waterfall; governance, quality, and metadata work cut across every phase.
  • DIKW: data (raw facts), information (data in context), knowledge (integrated understanding), wisdom (applied judgement). Data management primarily produces reliable information.
  • Roles: data owner (accountable), data steward (custodian of quality and definitions), data custodian (technical safekeeping), CDO, data governance council.
  • Maturity models assess capability across levels such as initial, repeatable, defined, managed, and optimized; strategy must link data goals to business goals and be measured.

Worked example

A retailer has three systems recording customer addresses. Finance reports by region disagree with Marketing campaign counts. Which knowledge area is primary? Reasoning: the disagreement is about a shared business entity, not about a single report. Reference and Master Data Management is primary because it defines the trusted customer record and cross-system identifiers. Data Quality is involved in measuring accuracy and completeness, Data Integration moves and reconciles records, Metadata documents definitions and lineage, and Data Governance decides who owns the definition. Naming governance as primary is the trap; governance enables and arbitrates, but the work of creating one trusted customer view is MDM.

Traps that cost marks

  • Equating data management with database administration.
  • Treating the eleven knowledge areas as sequential phases; they are concurrent and interdependent.
  • Saying governance does data management; it sets decision rights and oversight while functions execute.
  • Forgetting that Dispose is part of the lifecycle and that retention and archiving need policy.
  • Choosing a technology answer for a problem framed as accountability or definition.

Data Modeling and Design

Data Modeling and Design

This domain tests whether you can turn requirements into a precise, usable model and explain why each modeling choice was made. Questions cluster around model levels, notation, keys and relationships, normalization, dimensional design, and model quality review.

Core rules and concepts

  • Three model levels. Conceptual: business entities and relationships, no attributes or keys, technology-neutral. Logical: attributes, keys, cardinality, domains, fully normalized, still technology-independent. Physical: tables, columns, data types, indexes, partitioning, denormalization for performance.
  • Model components: entity, attribute, relationship, domain, key (natural, surrogate, primary, alternate, foreign), constraint, supertype/subtype, and associative entity for many-to-many relationships.
  • Cardinality (one-to-one, one-to-many, many-to-many) and optionality (mandatory or optional participation) are separate facts; a relationship can be one-to-many and optional on one side.
  • Normalization: 1NF removes repeating groups and ensures atomic values; 2NF removes partial dependencies on part of a composite key; 3NF removes transitive dependencies between non-key attributes; BCNF addresses overlapping candidate keys. Normalize logical models to reduce update anomalies; denormalize physical models deliberately for query performance.
  • Dimensional models: declare the grain of the fact table first; facts are numeric, additive measures; dimensions provide the by context. Star schema keeps dimensions one join from the fact; snowflake normalizes dimension hierarchies.
  • Model quality: accuracy, completeness, consistency, precision, and readability; review with business and technical stakeholders; maintain a model repository with versions and lineage.

Worked example

An order line table is keyed by OrderID plus ProductID and contains ProductName and ProductCategory. Is it normalized? ProductName depends only on ProductID, so it is a partial dependency and a 2NF violation. Move product attributes into a Product entity keyed by ProductID; the order line keeps OrderID, ProductID, quantity, and unit price. ProductCategory is transitive from ProductName if left in Product and is moved to a Category entity only if category attributes exist independently. In a warehouse, the same data becomes FactOrderLine at the grain of one row per order line, with dimension keys ProductKey, CustomerKey, and DateKey, and measures Quantity and ExtendedAmount.

Traps that cost marks

  • Putting attributes and primary keys into a conceptual model.
  • Treating denormalization as a modeling error rather than a documented performance trade-off.
  • Confusing cardinality with optionality, or drawing many-to-many without an associative entity.
  • Declaring the grain after choosing dimensions, which produces double-counted facts.
  • Assuming surrogate keys are business keys; surrogate keys are meaningless identifiers and should not be exposed as business codes.

Metadata

Metadata

Metadata is the domain most often under-estimated by candidates: it looks descriptive but is the mechanism by which data becomes findable, trusted, and change-safe. The exam tests metadata types, repositories and catalogs, standards, lineage and impact analysis, and the operating processes that keep metadata current.

Core rules and concepts

  • Metadata is data about data: structure, meaning, ownership, quality, usage, and movement. DAMA separates business metadata (definitions, glossary terms, business rules, ownership), technical metadata (schemas, data types, keys, ETL mappings, models), and operational metadata (row counts, load times, job status, error logs); process, audit, and provenance metadata are often added.
  • A business glossary holds agreed business terms and definitions; a data dictionary holds technical structure. They must be linked, or the glossary remains aspirational.
  • ISO/IEC 11179 provides principles for metadata registries: data elements with names, definitions, value domains, and classification. Other standards include Dublin Core for documents, OMG CWM for warehouse and metadata exchange, and W3C vocabularies.
  • Lineage records where data came from and how it changed. Impact analysis uses lineage in reverse: if a source column changes, which reports, models, or APIs break?
  • Metadata management activities: define strategy, understand requirements, define architecture, create and update, integrate, distribute, query and report, maintain, govern, and measure. Metadata itself needs owners, quality rules, and a lifecycle.
  • Metadata architecture patterns: centralized repository, distributed with a catalog indexing sources, and hybrid; automated harvesting via connectors and APIs is preferred to manual entry.

Worked example

A warehouse column CUST_STAT_CD is being retired. Business metadata tells you it means customer lifecycle status and that the glossary definition was approved by Sales Operations. Technical metadata shows VARCHAR(2), not null, sourced from CRM.customer_status. Operational metadata shows it loads nightly at 02:00 and 3.1 million rows were processed last run. Lineage shows it feeds two churn models and a regulatory report. Impact analysis therefore flags the churn models and the report as affected. Without linked business and technical metadata, a steward would see only a column name and could approve a change that silently breaks a regulatory output.

Traps that cost marks

  • Defining metadata as technical only; operational and business metadata carry equal exam weight.
  • Treating a data catalog as a one-off project rather than a governed, continuously harvested asset.
  • Confusing lineage with ETL job documentation; lineage traces data values through transformations.
  • Assuming a glossary term is a definition of a physical column; the link must be explicit.
  • Ignoring metadata quality: stale definitions and broken lineage cause wrong impact decisions.

Data Quality

Data Quality

Data Quality questions test dimensions, measurement, root-cause analysis, and control. The examiner wants to see that you can define a metric precisely, profile data before cleansing it, and build controls that prevent recurrence rather than running one-off cleanups.

Core rules and concepts

  • DAMA core dimensions: completeness, timeliness, validity, accuracy, consistency, and uniqueness. Related characteristics include precision, accessibility, conformance, integrity, and reasonableness.
  • Each dimension needs an operational definition, a business rule, a threshold, and a measurement method. Saying email is complete is not a metric; percentage of active customer records with a non-null, syntactically valid email at month end is.
  • Data profiling establishes the baseline: null counts, distinct counts, min and max, frequency distributions, pattern analysis, and foreign-key orphan checks. Profile before cleansing so improvement can be proven.
  • Root-cause analysis distinguishes data-entry errors, integration defects, missing business rules, and process gaps. Use the five whys, cause-and-effect diagrams, and Pareto analysis on issue types.
  • Data quality management is a cycle: define quality requirements and rules, assess against them, improve through remediation and process change, and monitor continuously with scorecards and issue logs.
  • Cost of poor quality includes rework, failed regulatory reporting, lost revenue, and mistrust; quantify it in business terms to justify controls.

Worked example

A customer table has 1,000 active records. 60 have no email; 25 of the 940 non-null emails fail the format rule. Completeness of email is 940 divided by 1,000, or 94 percent. Validity is 915 divided by 1,000, or 91.5 percent, if measured against all active records, or 915 divided by 940, or 97.3 percent, if measured only among populated values. State the denominator explicitly, because the two figures drive different conclusions. Profiling shows most invalid values arrive from a legacy batch feed, while missing values cluster in records created by a mobile app whose form does not require email. Root cause is therefore twofold: a feed mapping defect and a capture-process rule gap. Remediation is a mapping fix, a form validation rule, and a monthly monitor with an agreed threshold.

Traps that cost marks

  • Reporting a single quality score that hides which dimension failed.
  • Confusing accuracy (matches reality) with validity (conforms to an allowed format or domain).
  • Cleansing data without profiling or root-cause analysis, so defects return.
  • Measuring timeliness as load duration rather than data availability against a business deadline.
  • Omitting data quality roles and issue escalation; quality needs ownership, not just tools.

Data Governance

Data Governance

This domain tests authority, decision rights, and accountability. The exam asks you to distinguish governance from management, design an operating model, place roles correctly, and show how policies become enforceable standards.

Core rules and concepts

  • Data governance is the exercise of authority and control (planning, monitoring, enforcement) over data management, through shared decision-making. It answers who decides, who is accountable, and how disputes are resolved; it does not perform data quality, modeling, or integration work itself.
  • A governance programme needs a charter, scope, principles, an operating model, policies and standards, decision rights, issue escalation, metrics, and a communication plan.
  • Operating models: centralized (one council decides), decentralized (domains decide within enterprise principles), and federated (hybrid with domain councils reporting to an enterprise council). Choose by organizational culture and regulatory pressure, not by fashion.
  • Roles: data owner (business accountability for a data domain), data steward (defines, monitors, and improves quality and definitions), data custodian (technical storage, backup, access), Chief Data Officer, data governance council, and data governance office.
  • Policies state intent and are mandatory; standards specify measurable requirements; procedures describe execution; guidelines are recommended. A policy without a standard, a control, and an escalation path is unenforceable.
  • Governance domains include data architecture, quality, metadata, master data, security and privacy, and reference data. Metrics include decision cycle time, policy compliance, issue resolution, and stewardship coverage.

Worked example

Marketing defines an active customer as anyone with a login in the last 12 months; Finance defines it as anyone with a transaction in the last 12 months. Both publish reports to the executive committee. The data governance council, chaired by the CDO, rules that active customer is a governed term. The data owner for Customer, a business executive, decides the definition after consultation; the steward documents it in the business glossary with the rule and effective date; the custodian implements it in the warehouse; internal audit checks compliance. The council does not choose the definition itself; it enforces the process and resolves deadlock. That separation of decision rights is what the exam rewards.

Traps that cost marks

  • Equating governance with data management or with IT; governance sets direction and controls.
  • Giving the council operational tasks such as cleansing data or building reports.
  • Confusing data owner (accountable, business) with data custodian (technical safekeeping).
  • Writing principles without standards, controls, and escalation.
  • Attempting enterprise-wide scope first; start with a high-value domain and expand.

Data Warehousing & Business Intelligence

Data Warehousing and Business Intelligence

This domain tests the warehouse as a governed, integrated analytical environment: architecture, dimensional design, load patterns, and how BI delivers trusted information. Expect questions on schemas, slowly changing dimensions, fact table types, and the boundary between warehouse, mart, lake, and ODS.

Core rules and concepts

  • A data warehouse is subject-oriented, integrated, time-variant, and non-volatile, built to support analysis rather than transaction processing. An ODS holds near-real-time integrated operational data; a data mart is a subset for a department; a data lake stores raw and varied data at scale and needs governance to avoid becoming a swamp.
  • Layered architecture: staging for extract and land, integration for conform, cleanse, and historize, presentation for dimensional marts and the semantic layer, plus metadata, quality, and operations across all layers.
  • Dimensional design: choose the business process, declare the grain, identify dimensions, identify facts. Fact types: transactional (one row per event), periodic snapshot (one row per period), accumulating snapshot (one row per process instance with milestone dates).
  • Slowly changing dimensions: Type 1 overwrites and loses history; Type 2 adds a new row with a new surrogate key, effective dates, and current flag; Type 3 keeps a previous-value column. Type 2 preserves history for facts that reference the old key.
  • Conformed dimensions use the same keys and attribute definitions across marts; the bus matrix maps business processes to conformed dimensions.
  • BI layers: data sources, warehouse, semantic model, and presentation. OLAP variants are ROLAP, MOLAP, and HOLAP; self-service BI still depends on governed semantic definitions.

Worked example

A customer moves from Leeds to Bristol on 1 July. Sales facts before that date must still report Leeds. Under SCD Type 2, the dimension row for the customer is closed with an end date of 30 June and current flag N, and a new row opens on 1 July with a new surrogate key and Bristol. The June fact row keeps the old key, so a report by region attributes June revenue to Leeds and July revenue to Bristol. A Type 1 overwrite would move all history to Bristol and misstate regional performance. If the business only needs the current address for mailing, Type 1 is acceptable; the requirement, not preference, drives the choice.

Traps that cost marks

  • Declaring grain after designing dimensions, causing duplicated or double-counted measures.
  • Assuming Type 2 is always right; overwriting is valid when history is not required.
  • Confusing conformed dimensions with identical tables; conformance is about shared keys and definitions.
  • Treating a data lake as a warehouse substitute without schema, quality, and catalog controls.
  • Building BI directly on operational systems and calling it a warehouse.

Reference and Master Data Management

Reference and Master Data Management

This domain tests the data that other systems depend on: shared business entities and controlled value lists. Questions focus on the difference between reference and master data, matching and survivorship, MDM implementation styles, and the governance that makes a golden record credible.

Core rules and concepts

  • Reference data is a controlled set of permissible values or classifications used by multiple processes: country codes, currency codes, status codes, product taxonomies. It is often small, stable, and externally standardized, for example ISO 3166 country codes and ISO 4217 currency codes.
  • Master data describes core business entities: parties such as customers, suppliers, and employees; products; locations; and financial structures such as cost centres. It is shared, relatively stable, and non-transactional.
  • MDM creates and maintains a trusted, consistent view of master data across systems. A golden record is the trusted version, assembled by rules, not necessarily a single physical row in one source system.
  • Entity resolution: standardize and cleanse, block candidate pairs, match using deterministic rules such as tax ID or email, or probabilistic scoring on name and address, apply thresholds, and review false positives and negatives.
  • Survivorship rules decide which source value wins per attribute, for example CRM for contact details and ERP for billing details. Rules must be documented, versioned, and governed.
  • MDM styles: registry (index and cross-reference only), consolidation (analytical hub), coexistence (bidirectional with sources), and centralized or transactional hub, where MDM is the system of record. Choice depends on latency, ownership, and operational risk.
  • Reference data management needs ownership, change workflow, versioning, cross-reference mapping, and distribution to subscribers.

Worked example

CRM holds Jon Smith, 12 High St and ERP holds John Smith, 12 High Street. A deterministic match on tax ID finds no hit because CRM lacks it. Probabilistic matching on normalized name and address scores 0.91, above the 0.85 auto-match threshold, so the records are linked with a cross-reference. Survivorship gives CRM the email and phone, ERP the billing address and credit terms, and the golden record carries both source IDs. The steward reviews matches between 0.70 and 0.85. Publishing the golden record to the data warehouse and to customer service keeps them aligned, while the governance council approves the survivorship policy.

Traps that cost marks

  • Confusing reference data with master data; code lists are not customer entities.
  • Assuming the golden record must overwrite source systems; registry and consolidation styles do not.
  • Setting a matching threshold without measuring false positives and false negatives.
  • Letting IT choose survivorship rules without business owners; rules encode business priority.
  • Ignoring hierarchies and relationships, which are part of master data, not an afterthought.

Data Integration and Interoperability

Data Integration and Interoperability

This domain tests how data moves and how systems exchange meaning, not just bytes. Expect questions on integration patterns and their trade-offs, latency and batch versus streaming, interoperability levels, and the metadata and quality controls that keep integration trustworthy.

Core rules and concepts

  • DAMA defines data integration and interoperability as the acquisition, extraction, transformation, movement, delivery, replication, federation, virtualization, and operational support of data. Integration is movement and combination; interoperability is the ability of systems to exchange and use shared data.
  • Patterns: ETL (transform before load), ELT (load raw and transform in the target), change data capture (read logs or triggers to move only changes), replication, federation (query distributed sources through a virtual layer), virtualization, messaging and publish/subscribe, APIs and services, and streaming.
  • Batch suits large volumes and complex transformations with relaxed latency; streaming suits event-driven needs such as fraud detection. CDC reduces source impact and latency but depends on log access and schema discipline.
  • Interoperability layers: technical (protocols and connectivity), syntactic (format and structure, for example XML or JSON schemas), semantic (shared meaning and code sets), and organizational (process and policy alignment). Most failures are semantic, not technical.
  • Integration must carry metadata such as lineage and mappings, enforce data quality rules, secure data in motion, handle errors and reprocessing, and be monitored for freshness and completeness.
  • Canonical models and standardized code sets reduce point-to-point interfaces; an enterprise service bus or API gateway can mediate, but it does not create semantic agreement by itself.

Worked example

A retailer needs store inventory visible to e-commerce within five minutes. Nightly ETL cannot meet the latency. The team chooses CDC on the inventory database, streams change events through a message broker, and applies a lightweight transformation to a canonical inventory event. A semantic mismatch appears: stores send status code A for available, while e-commerce expects AVAILABLE. A cross-reference maps the codes and the mapping is registered as metadata. The design also includes poison-message handling, replay, and monitoring for event lag. Federation was rejected because querying store systems directly would expose them to e-commerce load and would not meet the latency target reliably.

Traps that cost marks

  • Treating ETL and ELT as synonyms; the transformation location changes performance and governance options.
  • Choosing real-time for every requirement; latency, cost, and complexity must be justified.
  • Assuming federation copies data; it queries at source and inherits source availability and security constraints.
  • Ignoring semantic interoperability and calling a working API integrated.
  • Building point-to-point interfaces without lineage, error handling, or a canonical model.

CDMP cheat sheet

Quick reference

Data Management Fundamentals

  • DAMA-DMBOK wheel: 11 knowledge areas grouped into Data Governance (center), Data Architecture, Data Modeling & Design, Data Storage & Operations, Data Security, Data Integration & Interoperability, Document & Content Management, Reference & Master Data, Data Warehousing & BI, Metadata, Data Quality.

  • Data lifecycle phases: Plan, Design & Enable, Build/Produce, Use & Maintain, Enhance, Dispose/Archive; each phase has data-quality and metadata checkpoints.

  • Data vs. information: data are raw recorded facts; information is data processed into context and meaning; knowledge is information integrated with experience.

  • ACID properties for transactional databases: Atomicity (all-or-nothing), Consistency (valid state transitions), Isolation (concurrent transactions do not interfere), Durability (committed changes survive failure).

  • CAP theorem: a distributed data system can simultaneously guarantee at most two of Consistency, Availability, Partition tolerance; partition tolerance is mandatory in practice, so the real trade-off is C vs. A.

  • Data storage types: relational (row-oriented), columnar (analytics), key-value, document, graph, and object stores; choose by access pattern, consistency need, and schema volatility.

  • Data security controls: authentication, authorization (role-based or attribute-based), encryption at rest and in transit, masking, tokenization, and audit logging.

  • Data management maturity is assessed across capability levels (e.g., 0–5) per knowledge area; maturity models measure process capability, not data quality directly.

Quick reference

Data Modeling and Design

  • Three model levels: conceptual (business entities and relationships, technology-neutral), logical (attributes, keys, normalization, no DBMS specifics), physical (tables, indexes, partitions, data types for a specific DBMS).

  • Entity-relationship notation: entity = noun; relationship = verb; cardinality options are 1:1, 1:M, M:N; optionality is mandatory or optional on each end.

  • Normalization: 1NF removes repeating groups; 2NF removes partial dependencies on part of a composite key; 3NF removes transitive dependencies on non-key attributes; BCNF removes every determinant that is not a candidate key.

  • Denormalization deliberately introduces redundancy (pre-joined tables, derived columns) to reduce join cost in read-heavy or analytical workloads; it trades write complexity and anomaly risk for query speed.

  • Dimensional modeling: fact tables hold measures and foreign keys; dimension tables hold descriptive context; star schema has denormalized dimensions; snowflake schema normalizes dimension hierarchies.

  • Slowly changing dimensions: Type 1 overwrites (no history), Type 2 adds a new row with version/effective dates (full history), Type 3 adds a previous-value column (limited history).

  • Surrogate keys are system-generated, stable, and independent of business keys; natural keys are business-meaningful and may change, so facts should reference surrogates.

  • Grain declares what one fact-table row represents; it must be defined before choosing dimensions and measures, and every measure must be additive at that grain.

Quick reference

Metadata

  • Metadata types: business (definitions, owners, rules), technical (schemas, data types, ETL mappings, lineage), operational (job logs, row counts, refresh times), and administrative (policies, access rights).

  • Metadata is managed through a metadata repository; a data catalog is the user-facing interface over that repository, supporting search, lineage, and glossary terms.

  • Data lineage records the path of data from source to target, including transformations; column-level lineage is required for impact analysis and root-cause tracing.

  • Impact analysis uses lineage in reverse (what downstream objects change if this column changes); root-cause analysis uses lineage forward (where did this bad value originate).

  • A business glossary defines business terms, synonyms, owners, and rules; it is the authoritative vocabulary linked to technical metadata.

  • Metadata integration patterns: a centralized repository (single store), a distributed registry (federated pointers), or a hybrid with a central index and local stores.

  • Metadata quality is assessed by completeness, accuracy, currency, and consistency; stale metadata is a common cause of failed data projects.

  • Metadata drives data quality rules, security classification, retention schedules, and self-service analytics; without it, data users cannot find or trust data.

Quick reference

Data Quality

  • Data quality dimensions: completeness, accuracy, consistency, timeliness, uniqueness, validity, and conformity; each dimension needs an operational definition and measurement method.

  • Completeness = non-null (or non-missing) values / total values; accuracy compares data to a verified source of truth; consistency checks agreement across systems or within a record.

  • Timeliness compares data availability against the required latency; uniqueness detects duplicate records; validity checks conformance to format, range, or domain rules.

  • Data profiling measures column statistics (null rate, distinct count, min/max, pattern frequency) to discover issues before defining rules.

  • Data quality rule types: completeness, validity, range, pattern, referential integrity, uniqueness, and cross-field consistency rules.

  • Data quality management cycle: define dimensions and rules, profile, measure, remediate root causes, monitor, and report; remediation targets process causes, not just bad records.

  • Data cleansing techniques: standardization, parsing, matching/deduplication, enrichment, and correction; cleansing without root-cause fix causes recurring defects.

  • Data quality metrics should be reported as trends with thresholds and ownership; a single score without dimension breakdown hides actionable problems.

Quick reference

Data Governance

  • Data governance is the exercise of authority and control over data management, covering policy, standards, decision rights, and accountability; it is not the same as data management execution.

  • Operating model components: data governance council (strategic decisions), data stewardship (tactical execution), data owners (accountable for a domain), and data custodians (technical care).

  • Decision rights define who decides on data definitions, access, quality thresholds, and issue resolution; unclear decision rights are a primary governance failure.

  • A data policy states principles and mandatory rules; standards specify measurable requirements; procedures describe how to comply; guidelines are recommended practices.

  • Data stewardship roles: business data steward (definitions, quality rules) and technical data steward (implementation, lineage); stewards are usually part-time domain experts.

  • Governance metrics include policy compliance rate, issue resolution time, glossary coverage, and stewardship participation; metrics must be tied to business outcomes.

  • Data governance maturity progresses from ad hoc to defined, managed, measured, and optimized; each level requires documented processes and assigned accountability.

  • Regulatory drivers (privacy, retention, reporting) require governance to map data to legal obligations, define retention/disposal rules, and evidence compliance.

Quick reference

Data Warehousing & Business Intelligence

  • A data warehouse is a subject-oriented, integrated, time-variant, nonvolatile collection of data supporting management decisions; it is built from operational sources via ETL/ELT.

  • Inmon approach: enterprise data warehouse as a normalized central store, then data marts; Kimball approach: dimensional bus matrix and conformed dimensions across marts.

  • Data mart types: dependent (sourced from the warehouse), independent (sourced directly from operational systems), and hybrid; independent marts risk inconsistent definitions.

  • Conformed dimensions are shared, identically defined dimensions across fact tables, enabling drill-across and consistent reporting.

  • ETL vs. ELT: ETL transforms before loading into the warehouse; ELT loads raw data first and transforms inside the target platform, common with cloud warehouses.

  • BI delivery layers: operational reports, dashboards, OLAP cubes, ad hoc query, and advanced analytics; each has different latency and aggregation requirements.

  • OLAP operations: slice, dice, drill-down, roll-up, and pivot; these navigate a multidimensional cube of dimensions and measures.

  • Data warehouse architecture layers: staging, integration, presentation, and metadata/access layers; staging isolates source extraction from transformation and load.

Quick reference

Reference and Master Data Management

  • Reference data are controlled code sets used to classify or categorize other data (country codes, currency codes, status codes); they are relatively static and shared across systems.

  • Master data are the core business entities (customer, product, employee, supplier, location) shared across processes; master data management creates a single trusted version.

  • MDM implementation styles: registry (index and links, no central golden record), consolidation (central read-only copy), coexistence (central copy with bidirectional sync), and centralized (authoritative master store).

  • A golden record is the single trusted version of a master entity, built by survivorship rules that choose or merge attribute values from source systems.

  • Entity resolution (matching) uses deterministic rules (exact keys) and probabilistic matching (similarity scores) to identify duplicates; thresholds control false positives and false negatives.

  • Reference data management requires a governed code-set owner, versioning, effective dates, and controlled distribution to consuming systems.

  • MDM data domains need defined hierarchies (e.g., customer household, product category) and relationships; hierarchy management is part of the MDM platform scope.

  • MDM success metrics: match rate, duplicate reduction, golden-record completeness, cross-system consistency, and time to onboard a new source.

Quick reference

Data Integration and Interoperability

  • Data integration patterns: extract-transform-load (ETL), extract-load-transform (ELT), change data capture (CDC), replication, federation, and virtualization.

  • Batch integration moves data on a schedule; real-time integration uses streaming or messaging; near-real-time uses micro-batch; choose by latency requirement and source capability.

  • Change data capture identifies inserts, updates, and deletes since the last run using timestamps, log-based capture, or triggers; log-based CDC has the least source impact.

  • Data virtualization queries distributed sources through a logical layer without physically moving data; it suits volatile or latency-sensitive access but can strain source systems.

  • Interoperability requires agreed data formats, semantics, and interfaces; standards (e.g., XML, JSON, industry message formats) reduce point-to-point mapping effort.

  • Integration design must handle data quality checks, error handling, restart/recovery, idempotency, and audit logging; silent failures are a common integration defect.

  • A hub-and-spoke integration architecture centralizes transformation and reduces point-to-point interfaces; a bus or messaging backbone decouples producers and consumers.

  • Data integration governance includes interface contracts, schema versioning, SLA monitoring, and lineage capture from source to target.

CDMP key terms

Data Management Body of Knowledge (DMBOK)

A structured framework of data management knowledge organized into eleven function areas, used to define scope, roles, and practices. It serves as a common reference for planning and assessing organizational data management capability.

Related: Data Governance, Data Stewardship
Data Lifecycle

The sequence of stages a data asset passes through, from creation or acquisition through storage, use, sharing, archival, and eventual disposal. Managing each stage explicitly prevents orphaned, duplicated, or unmanaged data.

Related: Data Lineage, Data Retention
Data Stewardship

The assignment of accountability for a data subject area to named individuals who resolve quality issues, approve definitions, and enforce policy. Stewards typically lack budget authority but own decisions about their domain's data content and rules.

Related: Data Owner, Data Governance, Data Quality Dimensions
Data Owner

A senior role accountable for a data domain's protection, access decisions, and policy compliance. Owners approve who may use the data and accept residual risk, delegating day-to-day content decisions to stewards.

Related: Data Stewardship, Data Classification
Data Governance Operating Model

The documented arrangement of decision rights, councils, roles, and escalation paths that determines how data decisions get made. It clarifies which bodies decide, advise, or are merely informed on data matters.

Related: Data Governance, Data Stewardship
Data Governance

The exercise of authority and control over data through policies, standards, decision rights, and oversight mechanisms. It balances defensive needs such as compliance with offensive goals such as analytics value creation.

Related: Data Governance Operating Model, Data Policy, Data Stewardship
Data Policy

A directive statement that mandates or prohibits behaviors regarding data creation, use, access, or disposal. Policies are deliberately broad and stable, with standards and procedures supplying the implementable detail beneath them.

Related: Data Standard, Data Governance
Data Standard

A mandatory, measurable requirement that operationalizes a policy, such as an approved format, code set, or naming convention. Compliance can be tested objectively, unlike the policy intent it supports.

Related: Data Policy, Reference Data
Data Classification

Assigning data to sensitivity tiers such as public, internal, confidential, or restricted so that handling controls scale with risk. Classification drives access rules, encryption requirements, retention periods, and sharing constraints.

Related: Data Retention, Data Owner
Data Retention

Defined periods during which records must be preserved to satisfy legal, regulatory, or business requirements, after which they should be destroyed. Schedules must be defensible and consistently enforced across systems.

Related: Data Classification, Data Lifecycle
Conceptual Data Model

A technology-independent representation of the business entities, their relationships, and key concepts, usually rendered as an entity-relationship diagram. It captures business vocabulary and rules without attributes or keys tied to any implementation.

Related: Logical Data Model, Physical Data Model
Logical Data Model

A refined model that adds attributes, primary and foreign keys, and normalized relationships while remaining independent of a specific database product. It resolves many-to-many relationships and documents cardinality precisely.

Related: Conceptual Data Model, Physical Data Model, Normalization
Physical Data Model

The implementation-ready design specifying tables, columns, data types, indexes, partitions, and constraints for a particular database technology. It reflects performance tuning and platform-specific features.

Related: Logical Data Model, Dimensional Model
Normalization

The progressive removal of redundancy and update anomalies by organizing attributes into relations based on functional dependencies. Third normal form, the common transactional target, ensures non-key attributes depend only on the whole key.

Related: Logical Data Model, Dimensional Model
Dimensional Model

A design pattern for analytical querying in which measurable facts reference descriptive dimensions through foreign keys. Star and snowflake schemas trade some redundancy for simpler, faster aggregation queries.

Related: Fact Table, Dimension Table, Slowly Changing Dimension
Fact Table

A table storing quantitative measurements or events at a declared grain, along with foreign keys to related dimensions. Summing its numeric columns answers most business performance questions.

Related: Dimension Table, Grain, Dimensional Model
Dimension Table

A table holding descriptive attributes that provide context for facts, such as product name, customer segment, or calendar period. Dimensions supply the filtering and grouping used in analytical queries.

Related: Fact Table, Slowly Changing Dimension
Grain

The precise business meaning of a single row in a fact table, stated before design begins. Declaring grain explicitly prevents double counting and mixed-level aggregation errors.

Related: Fact Table, Dimensional Model
Slowly Changing Dimension

A technique for preserving dimension history as attribute values change over time. Type 1 overwrites, Type 2 adds a new row with validity dates, and Type 3 keeps a limited prior-value column.

Related: Dimension Table, Data Warehouse
Data Warehouse

An integrated, subject-oriented, time-variant, nonvolatile store of data assembled from multiple sources for analysis and decision support. It separates analytical workloads from operational systems.

Related: Data Mart, Dimensional Model, ETL
Data Mart

A subset of a warehouse scoped to one business area, team, or analytical need. Marts may be dependent, sourced from the enterprise warehouse, or independent, built directly from operational sources.

Related: Data Warehouse, Dimensional Model
ETL

Extract, transform, and load: a pipeline pattern that pulls source data, applies cleansing and conforming rules in a staging area, then writes results to a target store. Transformation occurs before loading.

Related: ELT, Data Integration, Data Lineage
ELT

Extract, load, and transform: a pattern that lands raw source data in the target platform first and applies transformations there using its compute power. It suits scalable cloud warehouses and preserves raw history.

Related: ETL, Data Warehouse
Data Integration

The practice of combining data from disparate sources into consistent, usable, and shareable information. It spans movement, transformation, virtualization, and the reconciliation of conflicting semantics.

Related: ETL, Data Interoperability, Master Data Management
Data Interoperability

The ability of systems and organizations to exchange and correctly interpret data using agreed formats, interfaces, and semantics. It requires both technical connectivity and shared meaning.

Related: Data Integration, Reference Data, Metadata
Metadata

Data that describes other data, covering structure, meaning, lineage, quality, access rights, and usage. It makes data assets discoverable, understandable, and trustworthy to both people and systems.

Related: Business Glossary, Data Lineage, Data Catalog
Business Glossary

A controlled collection of business terms with approved definitions, owners, and relationships to physical assets. It aligns vocabulary across departments and anchors semantic consistency in analytics and reporting.

Related: Metadata, Reference Data, Data Catalog
Data Lineage

A record of the origin and movement of data across systems, transformations, and reports. It supports impact analysis, root-cause investigation, and regulatory traceability.

Related: Metadata, ETL, Data Quality
Data Catalog

An inventory of data assets with searchable metadata such as definitions, owners, location, sensitivity, and quality scores. It helps users find and assess data before using it.

Related: Metadata, Business Glossary, Data Lineage
Data Quality Dimensions

Measurable characteristics used to assess fitness for use, commonly including completeness, accuracy, consistency, timeliness, uniqueness, and validity. Each dimension needs its own testable rule and threshold.

Related: Data Quality Rule, Data Profiling
Data Quality Rule

A specific, executable test that verifies data against an expected condition, such as a range check or referential constraint. Rules produce measurable pass rates that trigger remediation when thresholds are breached.

Related: Data Quality Dimensions, Data Profiling, Data Cleansing
Data Profiling

Statistical analysis of data to reveal structure, value distributions, null rates, uniqueness, and patterns. Profiling establishes a baseline, exposes anomalies, and informs rule design before remediation begins.

Related: Data Quality Rule, Data Quality Dimensions
Data Cleansing

Correcting or standardizing invalid, incomplete, duplicated, or inconsistent values in a dataset. It is usually a remediation step after profiling and rule evaluation identify defects.

Related: Data Profiling, Data Quality Rule
Reference Data

A controlled set of permissible values used to classify or categorize other data, such as country codes, currency codes, or status codes. It is typically small, stable, and shared across many systems.

Related: Master Data, Data Standard, Business Glossary
Master Data

Core business entities shared across processes and systems, such as customers, products, suppliers, and locations. Consistent master data prevents conflicting views of the same entity.

Related: Master Data Management, Reference Data, Entity Resolution
Master Data Management

The discipline and tooling used to create and maintain a single trusted view of core entities across the organization. It covers governance, matching, survivorship, and controlled distribution to consuming systems.

Related: Master Data, Entity Resolution, Data Integration
Entity Resolution

The process of determining when records from different sources refer to the same real-world entity. It combines deterministic matching rules with probabilistic scoring and often requires manual review of uncertain matches.

Related: Master Data Management, Master Data

CDMP study plan

8 weeks · About 7 hours per week

Week 1

Data Management Fundamentals (DMF)

  • Define each of the eleven data management knowledge areas in your own words and state one business problem each one solves

  • Map the data management lifecycle stages to a real organization you know, naming who owns each stage

  • Distinguish data management from data governance, data architecture, and IT operations with two concrete examples each

  • Explain the difference between data, information, and knowledge and apply it to a single dataset of your choice

Your checkpoint

A one-page concept map linking all eleven knowledge areas to lifecycle stages, with a short written definition for each area

Week 2

Data Modeling and Design

  • Draw conceptual, logical, and physical models for the same small business scenario and annotate what changes at each level

  • Apply normalization rules from first through third normal form to a denormalized sample table and document each fix

  • Build an entity-relationship diagram using both Chen and crow's-foot notation, including cardinality and optionality

  • Explain when denormalization is justified and list three trade-offs against write integrity

Your checkpoint

A three-level model set (conceptual, logical, physical) for one scenario, plus a normalization worksheet showing before and after states

Week 3

Metadata & Data Quality

  • Classify metadata into business, technical, and operational categories using ten examples from a system you can describe

  • Draft a metadata repository entry template covering name, definition, owner, steward, source, and lineage

  • Define six data quality dimensions and write one measurable test for each against a sample dataset

  • Distinguish data profiling, cleansing, and monitoring, and place each in a continuous quality cycle

  • Identify root causes of three common defect types and propose a prevention control for each

Your checkpoint

A metadata dictionary of at least fifteen fields with definitions and owners, plus a data quality scorecard template covering six dimensions

Week 4

Data Governance

  • Describe the operating model choices for a data governance program and justify one for a mid-size organization

  • Write role descriptions for data owner, data steward, and data custodian that separate accountability from execution

  • Draft a decision-rights matrix for three data-related decisions such as access approval and definition changes

  • Explain how a data governance council escalates and resolves cross-functional conflicts

  • Connect governance to policy, standard, and procedure with one example of each

Your checkpoint

A two-page governance charter with operating model, roles, decision rights, and an escalation path

Week 5

Data Warehousing & Business Intelligence

  • Compare Inmon, Kimball, and data vault approaches on structure, purpose, and change tolerance

  • Design a star schema with one fact table and three dimensions, choosing grain and surrogate keys deliberately

  • Explain slowly changing dimension types 1, 2, and 3 and state when each is appropriate

  • Distinguish OLTP from analytical workloads and describe how that shapes physical design

  • Outline the path from source data to a business intelligence report, naming each transformation stage

Your checkpoint

A star schema diagram with documented grain, key strategy, and SCD handling, plus a one-page comparison of the three warehouse approaches

Week 6

Reference and Master Data Management

  • Distinguish reference data from master data and give three examples of each from different industries

  • Describe the four common master data management implementation styles and their trade-offs

  • Explain how entity resolution, matching, and survivorship work together to produce a golden record

  • Identify three sources of duplicate and conflicting master records and a control for each

  • Outline how reference data sets are governed, versioned, and distributed to consuming systems

Your checkpoint

A master data design brief for one domain such as customer or product, covering style choice, matching rules, survivorship logic, and governance touchpoints

Week 7

Data Integration and Interoperability

  • Compare batch, change data capture, and real-time integration patterns on latency, cost, and complexity

  • Describe extract, transform, load versus extract, load, transform and state when each fits

  • Explain how a data integration architecture supports lineage and metadata capture

  • List interoperability standards relevant to your sector and describe what problem each solves

  • Identify three failure modes in integration pipelines and the monitoring control that detects each

Your checkpoint

An integration architecture diagram for one data flow, annotated with pattern choice, latency target, error handling, and lineage capture points

Week 8

Data Management Fundamentals (DMF) & Data Governance

  • Rehearse the full knowledge-area map and correct any weak areas found in a timed self-test

  • Synthesize governance and fundamentals into one argument for how a program matures over time

  • Write concise answers to ten scenario prompts that combine at least two domains each

  • Review every prior deliverable and note the three concepts you still explain least confidently

Your checkpoint

A timed practice exam result log with a written remediation note for every missed item, plus a one-page synthesis of the full program lifecycle

Milestones

Week 2: You can sketch conceptual, logical, and physical models for a new scenario in under twenty minutes and explain each normalization step aloud without notes

Week 4: You can state the difference between metadata and data quality concerns for the same field, and your governance charter names a decision owner for every listed decision

Week 6: You can choose a warehouse approach and an MDM style for a described scenario and defend both choices against two alternatives with trade-offs

Week 8: You score at least 80 percent on a timed mixed-domain self-test and can explain every missed item in your own words without referring to notes

CDMP exam day

Your checklist

Government-issued photo ID

Bring the original, unexpired ID whose name matches your registration exactly. Remote-proctored and test-center deliveries both require it. If your ID name differs from your registration (e.g., a shortened first name), contact the provider before test day to correct the record - do not assume it will be waved through.

Confirm your delivery mode, time zone, and start time

CDMP is delivered through a provider, and scheduling details, appointment time zone, and whether you sit at a test center or proctor remotely should be confirmed with the provider. Re-read your appointment confirmation the day before; time-zone mistakes are a common and avoidable way to miss a slot.

Run the system/equipment check if testing remotely

If you are proctoring from home, run the provider's equipment test on the same machine and network you will use on test day: camera, microphone, browser lockdown, and bandwidth. Confirm with the provider which browsers and operating systems are supported and whether a wired connection is recommended.

Prepare a clear, quiet test space (remote delivery)

A private room, a clear desk, good lighting on your face, and a closed door. Expect the proctor to ask for a room scan. Keep phones and smartwatches out of the room entirely rather than face-down on the desk. Confirm the provider's specific room and desk rules in advance.

Know what materials are permitted

Assume nothing is allowed unless the provider says otherwise. Scratch paper, pens, calculators, notes, and reference sheets are typically restricted or require prior approval. Confirm with the provider what, if anything, you may bring, and whether an on-screen whiteboard or notepad is supplied.

Review the exam structure and timing

Know how many questions, whether they are multiple-choice, multiple-response, or scenario-based, and whether sections are timed separately. Confirm with the provider the current number of questions, time allowance, and pass mark - these details change and should not be taken from memory or forum posts.

Plan arrival or login buffer

Arrive at the test center or log in well before your appointment, allowing time for ID checks, check-in, and any queue. Late arrival can forfeit your seat or fee. Confirm the provider's cutoff for late arrival.

Sort logistics: route, parking, or transit; childcare; work calendar

Remove same-day friction. Know the route and parking, or clear your calendar and silence notifications for a remote session. Tell your household you cannot be interrupted during the window.

Know your reschedule and cancellation terms

Confirm with the provider the deadline and fee for rescheduling or cancelling, and what happens if you are ill or your connection fails. Knowing this reduces panic and prevents a no-show forfeit.

Plan your answer strategy for scenario questions

Decide in advance how you will handle long scenario items: read the question stem first, identify the decision being tested, eliminate options that violate governance or data-quality fundamentals, and flag-and-return rather than stalling. Rehearse this on practice items before test day.

Prepare for the post-exam step

Know how results are reported and how you would claim or maintain the credential afterward, including any continuing-education or renewal requirement. Confirm with the provider or the certifying body how and when results are released.

Backup plan for tech failure (needs_review)

Have the provider's support contact and your appointment number to hand. Confirm with the provider its policy on technical interruptions, whether the clock stops, and how a session is resumed or re-scheduled. Do not assume a disconnect is automatically excused.

Plan the day

Final 72 hours - consolidate, do not cram new topics

Stop adding new material. Rework your weak areas against the exam blueprint: data governance, data quality, metadata and master data, data modeling and architecture, and data integration and interoperability. For each domain, be able to state the core principles, the roles involved, and the trade-offs. Re-read your own notes and error log rather than starting a new resource. Do one timed set of scenario-style questions to recalibrate pacing, then review every miss for the reasoning error, not just the right answer.

Final 72 hours - rehearse the exam mechanics

Confirm the appointment, delivery mode, and start time in your own time zone, and re-check the provider's rules on permitted materials, breaks, and ID. If testing remotely, run the equipment check once more and note the support contact. Decide your pacing rule now: for example, an average budget per question and a hard cutoff at which you flag and move on. Write it down; do not improvise under time pressure.

Final 24 hours - logistics and rest

Lay out your ID, appointment confirmation, and any permitted items the night before. Confirm the route or the room setup. Do a light review of summary sheets only - no new practice exams and no late-night cramming, since fatigue costs more than one extra fact gains. Eat normally, hydrate, set two alarms, and aim for a full night's sleep. Re-read the question-count and time allowance so the pacing plan is fresh.

Morning of - steady and early

Eat a proper meal, limit caffeine to your normal amount, and arrive or log in with a generous buffer. Re-read your one-page strategy note: read the stem first, watch for 'BEST' and 'FIRST' wording, eliminate extremes, and answer every question unless the provider penalizes guessing - confirm that with the provider. At a test center, follow check-in instructions and store personal items as directed; remotely, complete the room scan and close every other application.

During the test - pacing and question handling

Start with a quick scan of the interface and confirm the clock and question count. Work in passes: answer confident items first, flag long scenarios, and return to them. For scenario questions, identify the decision being tested and the constraints (governance, quality, risk, stakeholder impact) before reading the options. Treat 'select all that apply' items as true/false judgments per option. If a question is genuinely ambiguous, choose the answer that reflects sound data-management practice and the stated constraint, then move on. Watch the clock at the halfway point and adjust.

During the test - breaks and interruptions

Take a break only if the provider permits it and understand whether the clock runs during the break - confirm with the provider. If your connection drops or the proctor intervenes, stay calm, follow instructions, and note the time and what happened in case you need to raise it with support afterward. Do not open other applications or leave the camera view.

After the test - capture and plan

Note what felt uncertain while it is fresh, then follow the provider's process for results. If you did not pass, use those notes to build a targeted retake plan around the weakest domains and confirm the retake policy and waiting period with the provider. If you passed, confirm how the credential is claimed and what continuing-education or renewal obligations apply.

Rules to check

  • Bring valid, unexpired government-issued photo ID with a name matching your registration. If there is any mismatch, resolve it with the provider before test day; do not expect an exception at check-in.

  • Follow the provider's rules on permitted materials exactly. Unless the provider explicitly allows an item, assume notes, phones, smartwatches, scratch paper, and calculators are prohibited; confirm what is supplied on screen.

  • Do not communicate with anyone but the proctor during the session, and do not let anyone enter your test space. Any coaching, messaging, or shared screen during the exam is a conduct violation.

  • Breaks, if any, are governed by the provider's policy and may count against your time. Confirm in advance whether scheduled or unscheduled breaks are allowed and whether the clock pauses.

  • Scoring and the pass mark are set by the certifying body; question counts, timing, and the passing standard can change. Confirm the current figures with the provider rather than relying on secondhand reports, and do not assume partial credit on multiple-response items.

  • Report technical problems, interruptions, or suspected exam-content errors to the provider through its official channel immediately or as soon as the session ends, and keep your appointment number; do not assume an issue will be corrected automatically.

  • Rescheduling, cancellation, and no-show terms are set by the provider, with deadlines and fees that vary. Confirm them before you commit to a date, and treat late arrival as a risk of forfeiting your seat or fee.

  • Maintain exam integrity: do not reproduce, share, or discuss specific exam questions afterward. Beyond being a conduct issue, it undermines the value of the credential you are earning.

CDMP FAQ

How many CDMP practice questions are available?

The practice set has 200 CDMP questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many CDMP flashcards are available?

The flashcard set has 32 CDMP cards. Each card shows the term and its definition.

Which topics does the CDMP study material cover?

The CDMP study material has 8 sections, including Data Management Fundamentals (DMF), Data Modeling and Design, and Metadata.

What format facts does the catalog list for the CDMP exam?

The catalog lists these item types: Data Management Fundamentals (DMF) exam and specialist exams for the CDMP exam.