Free DAMA CDMP Quality Practice Questions: Specialist Cross-Discipline Judgment

Topic snapshot

Sample questions

These are original IT Mastery practice questions aligned to this topic area. They are not official exam questions, copied live-exam content, or exam dumps. Use them for self-assessment, scope review, and deciding what to drill next.

Question 1

Topic: Specialist Cross-Discipline Judgment

A bank’s customer analytics team reports recurring defects in the customer_segment field. Monthly profiling shows 8-12% of records use segment codes created locally by branches and not approved in the enterprise reference data list. Downstream cleansing fixes reports temporarily, but the same defects reappear after each branch campaign. Which governance action best supports sustainable quality improvement?

Options:

• A. Assign stewardship ownership and approval control for segment codes

• B. Expand the analytics mapping to accept all local codes

• C. Cleanse invalid codes in the analytics data mart monthly

• D. Publish a profiling scorecard for branch managers

Best answer: A

Explanation: The recurring defect is not just a data cleansing problem; it is a governance breakdown in reference data control. Branches are creating local values outside the approved enterprise code set, so the sustainable action is to establish clear stewardship ownership, approval workflow, and accountability for segment codes and the related quality rule. That governance control can then drive source validation, issue escalation, and monitoring. Monthly cleansing treats symptoms after poor-quality data has already entered the environment. A scorecard may reveal the issue, but measurement alone does not control who can create or approve valid codes.

• Monthly cleansing fixes reports temporarily but leaves the branch process that creates invalid codes unchanged.
• Scorecard publishing improves visibility, but it does not define ownership or approval authority for the code set.
• Accepting local codes weakens enterprise consistency and bypasses the governed reference data standard.

Question 2

Topic: Specialist Cross-Discipline Judgment

A data quality scorecard shows that the enterprise “active customer” metric fails its consistency threshold. Profiling confirms that CRM, billing, and loyalty systems each follow their own approved local definition, and no enterprise policy identifies the authoritative definition or source. Marketing and Finance cannot agree because the metric drives both campaign counts and revenue reporting. What is the best next governance action?

Options:

• A. Change the scorecard threshold until the metric passes

• B. Ask data stewards to standardize the records manually

• C. Let the CRM data owner approve the enterprise definition

• D. Escalate the definition and authority conflict to the governance council

Best answer: D

Explanation: A data quality defect that comes from conflicting business definitions is a governance issue, especially when it crosses domains and affects enterprise reporting. The stewards have already confirmed that each system is applying its own approved local rule, so the problem is not simple invalid data. Because Marketing and Finance have competing uses and no policy names the authoritative definition or source, a governance council is the right forum to resolve the conflict, assign authority, and approve the enterprise standard. After that decision, stewards and owners can update rules, metadata, scorecards, and remediation plans. Local cleansing would treat symptoms, while threshold changes would hide the unresolved governance gap.

• Manual standardization fails because the records are not proven wrong; the definitions behind them conflict.
• Single-owner approval fails because CRM cannot unilaterally define an enterprise metric used by other domains.
• Threshold adjustment fails because it masks the consistency issue instead of resolving definition and authority.

Question 3

Topic: Specialist Cross-Discipline Judgment

A data quality team is triaging defects found during profiling of customer service data. Leadership wants to know which item should be escalated to the data governance council as an ethical data quality concern, not just handled as an operational cleanup or report presentation issue. Which defect best fits that escalation?

Options:

• A. A daily exception report arrives 30 minutes late

• B. Missing accessibility needs flags suppress service accommodations

• C. Duplicate supplier rows increase invoice matching effort

• D. A dashboard label uses an outdated department name

Best answer: B

Explanation: Ethical data quality concerns arise when poor quality can materially affect people’s rights, access, safety, fairness, or dignity. A missing accessibility needs flag is not merely incomplete data; it can prevent customers from receiving needed accommodations and create unequal treatment. That makes the issue appropriate for governance escalation, stewardship attention, root-cause analysis, and sustained controls. Operational inefficiency, cosmetic reporting defects, and minor timing issues may still need remediation, but they do not automatically create an ethical concern unless they materially affect decisions about people or expose them to harm.

• Supplier duplication creates process inefficiency and possible payment risk, but the facts point to operational cleanup rather than ethical impact.
• Outdated labeling is a presentation and metadata issue, but it does not show unfair treatment or harm.
• Late reporting may affect operations, but a 30-minute delay alone does not indicate an ethical quality concern.

Question 4

Topic: Specialist Cross-Discipline Judgment

A data quality council reviews proposed rules for a patient outreach dataset. All rules can be implemented accurately and measured consistently. Which proposed rule most needs ethical review before adoption?

Options:

• A. Measure duplicate patient records by matching identifiers

• B. Validate diagnosis codes against approved reference data

• C. Include full patient identifiers in every exception report

• D. Flag birth dates later than the load date

Best answer: C

Explanation: A data quality rule can be technically valid and still create an ethical problem if it increases privacy exposure, unfairly excludes a population, or encourages misleading use. Exception reports often support remediation, but they should follow data minimization and need-to-know principles. Full patient identifiers may not be necessary for every reviewer or every failed rule, especially when pseudonymized IDs, limited fields, role-based access, or aggregated results would support the quality process with less exposure. The issue is not whether the rule can be measured; it is whether the design creates unnecessary ethical risk while pursuing quality improvement.

• Future birth dates are a standard validity check and do not create an obvious ethical issue under the stated facts.
• Reference-code validation supports consistency and validity when the approved code set is appropriate for the business use.
• Duplicate matching is a normal uniqueness control when identifiers are handled with appropriate access safeguards.

Question 5

Topic: Specialist Cross-Discipline Judgment

A customer analytics team finds that the same customer can have different “active customer” statuses in CRM, billing, and the data warehouse. Profiling confirms the differences, and prior cleansing has corrected reports only temporarily. Sales and Finance disagree on which status should be authoritative for revenue reporting. What action best fits the situation?

Options:

• A. Run more frequent profiling on all customer status fields

• B. Escalate the definition and authority decision to data governance

• C. Add the status discrepancy rate to the quality scorecard

• D. Cleanse the warehouse status values before each report cycle

Best answer: B

Explanation: Data governance is needed when a quality issue depends on business decision rights, shared definitions, ownership, or authority across functions. Profiling can show the inconsistency, remediation can temporarily correct values, and monitoring can track recurrence, but none of these decides which source or definition is authoritative. Because Sales and Finance disagree about the meaning and approved use of “active customer” for revenue reporting, the issue must be resolved through governance roles such as data owners, stewards, or a data governance council. After the decision is made, quality rules, lineage, controls, and scorecards can enforce and monitor it.

• More profiling only produces additional evidence; it does not resolve the cross-functional authority conflict.
• Repeated cleansing treats symptoms in the warehouse while leaving the approved business definition unresolved.
• Scorecard tracking makes the defect visible, but a metric cannot choose the authoritative status for revenue reporting.

Question 6

Topic: Specialist Cross-Discipline Judgment

A retailer’s certified customer profitability report shows duplicate customers and conflicting loyalty statuses. Profiling shows that each source application has valid status codes, required fields are complete, and local customer IDs are unique. The duplicates appear only after two parallel integration paths load the warehouse: a nightly file from CRM and a near-real-time API from the loyalty platform. Stewards have already approved the customer definition and quality rules. Which action is the BEST quality decision?

Options:

• A. Redesign the integration architecture around an authoritative customer identity path

• B. Ask stewards to rewrite the customer definition

• C. Require source teams to add stricter field-entry validation

• D. Modify the report to suppress duplicate rows

Best answer: A

Explanation: Architecture-driven quality causes appear when data is valid in source systems but becomes defective because of how systems, integrations, identifiers, or repositories are designed. Here, source profiling does not show missing values, invalid codes, or local uniqueness failures. Stewardship work is also mature because the customer definition and rules are already approved. The defect appears only after two separate ingestion paths combine customer data in the warehouse, which points to an integration and identity architecture issue. A durable fix should establish one authoritative customer identity path, crosswalk, or mastering approach and remove conflicting parallel loads. Downstream report changes may reduce visible symptoms, but they do not prevent recurring defects.

• Stricter source validation does not fit because the sources already pass validity, completeness, and local uniqueness checks.
• Rewriting definitions is weak because the stewardship definition and quality rules are already approved.
• Suppressing duplicates hides the reporting symptom while leaving the integration architecture defect in place.

Question 7

Topic: Specialist Cross-Discipline Judgment

A regional insurer reports conflicting “active policy” counts between claims analytics and finance reporting. Profiling shows both marts are technically valid and complete, but they use different policy status definitions and receive status updates through separate feeds from the policy administration system. Finance uses the count for regulatory reporting, and the data governance council has asked for a sustainable quality decision rather than another reconciliation spreadsheet. Which decision best improves data quality?

Options:

• A. Ask each reporting team to document its local definition

• B. Create a monthly manual tie-out between marts

• C. Define an authoritative policy source and shared status model

• D. Increase completeness checks on both reporting marts

Best answer: C

Explanation: Conflicting counts can occur even when each dataset is valid and complete if architecture allows multiple flows, duplicated transformations, and inconsistent business definitions. The sustainable data quality response is to clarify the authoritative source, standardize the policy status model, and route downstream reporting through governed, well-defined flows. That improves consistency and fitness for purpose, especially where finance relies on the measure for regulatory reporting. Local documentation or recurring reconciliations may expose differences, but they do not remove the redundant logic that creates them.

• More completeness checks miss the issue because the facts say the marts are complete; the defect is inconsistent definition and flow.
• Local definitions preserve conflicting interpretations instead of governing a shared business meaning.
• Manual tie-out treats symptoms after the fact and does not prevent recurring inconsistency.

Question 8

Topic: Specialist Cross-Discipline Judgment

A city agency plans to use an integrated resident dataset to prioritize eligibility reviews for housing assistance. Profiling shows high rates of missing income updates and inconsistent household-size values, but program staff have not defined how much uncertainty is acceptable for this use. What is the best data quality response before the dataset is used for these decisions?

Options:

• A. Publish a completeness scorecard for the integrated dataset

• B. Exclude records with missing income updates from the review

• C. Escalate for a fitness-for-purpose review and decision-use controls

• D. Run automated standardization on income and household fields

Best answer: C

Explanation: When data affects people, the key issue is not only whether defects exist, but whether the data is fit for the specific decision and whether limitations are understood by accountable stakeholders. Missing income updates and inconsistent household size may directly affect eligibility prioritization, so program owners and data stewards should define acceptable quality thresholds, assess potential harm or bias, document limitations, and apply controls such as restricted use, manual review, or remediation before operational use. Profiling evidence is an input to that governance decision; it is not sufficient by itself. The strongest response connects quality measurement to ethical decision use and business accountability.

• Standardization alone may improve format consistency, but it does not establish whether the data is reliable enough for eligibility decisions.
• Scorecard reporting communicates measurement, but reporting defects without decision controls leaves the risk unresolved.
• Record exclusion can create unfair outcomes and should not be chosen without approved rules and impact assessment.

Question 9

Topic: Specialist Cross-Discipline Judgment

A data quality team finds recurring conflicts in customer_status between CRM, billing, and the enterprise warehouse. Profiling shows each value is valid within its source, but lineage shows both CRM and billing can update the attribute and the warehouse load uses whichever update arrives last. Which interaction is most needed to prevent recurrence?

Options:

• A. Add a stricter warehouse validity rule for status codes

• B. Create a scorecard metric for status-code completeness

• C. Run a one-time cleansing job on conflicting warehouse records

• D. Align system-of-record boundaries and data flows with data architecture

Best answer: D

Explanation: When values are individually valid but conflict across systems, the issue is not primarily a format or code-set defect. It reflects weak data architecture: unclear system-of-record boundaries, ambiguous data flows, and possibly inconsistent meanings for the same attribute. Data quality work should engage data architecture to define which system is authoritative for customer_status, how changes move through the environment, and how the shared model represents the attribute. Rules and monitoring still matter, but they should enforce an agreed architecture rather than compensate for an unclear one. Sustainable prevention comes from clarifying authority and flow, not repeatedly correcting downstream symptoms.

• Stricter validity fails because the profile already shows source values are valid; the defect is cross-system conflict.
• One-time cleansing fixes current records but leaves the same ambiguous update path in place.
• Completeness scorecarding measures a different condition and would not resolve competing authoritative updates.

Question 10

Topic: Specialist Cross-Discipline Judgment

A data quality team finds that 12% of customer records are missing a consent status. The validation job detects and routes exceptions correctly, and the source-system team can add a required-field control. Work is stalled because Marketing, Legal, and Customer Service disagree on which consent statuses are valid and who can approve the standard. What is the best classification of the primary problem?

Options:

• A. Governance decision-rights problem

• B. Downstream cleansing problem

• C. Quality rule execution problem

• D. Profiling coverage problem

Best answer: A

Explanation: A quality execution problem occurs when agreed rules are not implemented, controls fail, exceptions are not detected, or remediation work is not performed as designed. Here, the validation job works and the source team can implement the control. The unresolved issue is authority: multiple business stakeholders disagree on the valid values and no accountable role can approve the consent-status standard. That is a governance decision-rights problem because stewardship and governance must define who decides, approves, and resolves conflicts for business rules and quality thresholds. Once the decision right is assigned and the standard is approved, quality execution can proceed.

• Execution failure does not fit because the detection and routing process is already working.
• Profiling coverage does not fit because the defect rate is known and the issue is not lack of discovery.
• Downstream cleansing is not the primary need because cleanup without an approved standard would not prevent recurrence.

Continue in the web app

Use IT Mastery for interactive DAMA CDMP Data Quality Specialist practice with mixed sets, timed mocks, topic drills, explanations, and progress tracking.

Try DAMA CDMP Data Quality Specialist on Web

Related focused pages

• Free DAMA CDMP Data Quality Specialist Full-Length Practice Exam
• Data Quality Foundations and Business Fitness
• Quality Strategy Business Case and Prioritization
• Profiling Discovery and Assessment
• Quality Rules Standards and Requirements
• Root Cause Analysis and Remediation
• Monitoring Scorecards and Measurement
• Quality Governance Roles and Stewardship
• Metadata Lineage and Quality Evidence
• Master Reference and Warehouse Quality
• Quality in Data Lifecycle and Operations
• Quality Maturity and Continuous Improvement