Free DAMA CDMP Quality Practice Questions: Quality in Data Lifecycle and Operations

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: Quality in Data Lifecycle and Operations

A health insurer is moving claims older than 10 years to archive and testing weekly backups for the active claims store. The analytics mart is refreshed nightly from the active store. Which condition creates the clearest data quality risk during these lifecycle operations?

Options:

• A. Backup files are encrypted by the infrastructure team.

• B. Archive retention rules reference the approved policy.

• C. Archived claims are stored on lower-cost storage.

• D. Restores lack reconciliation for post-backup corrections and deletions.

Best answer: D

Explanation: Backup and restoration are data quality concerns when they can change the business fitness of data after recovery. If a restored copy does not account for corrections, retention deletions, or legal-hold changes made after the backup point, downstream stores may contain stale, inconsistent, or improperly retained records. The risk is not the backup itself, but the loss of alignment between the restored data and the current authoritative lifecycle state. Lower-cost archive storage and encrypted backups may be operational or security details, but they are not quality defects unless they affect accessibility, integrity, timeliness, or correct use. Approved retention rules reduce quality and compliance ambiguity rather than create it.

• Storage tier confusion fails because cheaper archive storage is not a quality issue by itself if records remain trustworthy and usable for their purpose.
• Encryption focus fails because encryption is mainly a protection control, not evidence of inaccurate, incomplete, stale, or inconsistent data.
• Approved retention policy fails because referencing the governed policy supports consistent lifecycle treatment.

Question 2

Topic: Quality in Data Lifecycle and Operations

A distribution company resumes order processing after a storage failover. The product catalog and order tables are current, but the inventory table served to fulfillment is a read-only copy last refreshed 36 hours ago because its refresh job was paused. No restore errors occurred, no rows were purged, and no extra replicas are being queried. Fulfillment is accepting orders for items that are no longer available. Which quality issue is primarily affecting the data?

Options:

• A. Uncontrolled replication

• B. Stale data

• C. Incomplete restoration

• D. Improper deletion

Best answer: B

Explanation: Stale data is a timeliness problem: the data may be structurally valid and complete, but it is too old for the business use. Here, the decisive fact is that the inventory copy was last refreshed 36 hours ago while fulfillment depends on current stock availability. The scenario explicitly rules out restore failure, purge activity, and accidental querying of extra replicas. The quality impact is not that data was lost or duplicated, but that an operational process is using an outdated version for a time-sensitive decision.

• Incomplete restoration would involve missing or partially recovered data after recovery, but the scenario says no restore errors occurred.
• Uncontrolled replication would involve inconsistent or unauthorized copies being used, but no extra replicas are being queried.
• Improper deletion would involve records being purged or removed incorrectly, but no rows were purged.

Question 3

Topic: Quality in Data Lifecycle and Operations

A customer archive was created from the operational CRM for regulatory retention and is replicated to low-cost storage. A marketing team now wants to use the archive for an active suppression list. Profiling shows many addresses and consent statuses no longer match the current master customer record, although the archive is complete and unchanged from the date it was retained. What is the best data quality response?

Options:

• A. Lower the marketing quality thresholds

• B. Cleanse the retained archive in place

• C. Accept it because it is complete and unchanged

• D. Treat it as not fit for active use without revalidation

Best answer: D

Explanation: Data quality is judged by fitness for purpose, not only by whether data is complete or technically unchanged. A retained archive can be high quality for its retention purpose because it preserves a historical record, yet be poor quality for active operational or marketing decisions because it is stale or inconsistent with current master data. The appropriate response is to prevent direct active use unless the data is revalidated, refreshed, or reconciled against the authoritative current source under rules approved for that business use. Preserving the archive may still be required; active-use quality controls should be applied separately.

• Historic validity fails because completeness and preservation do not prove current business fitness.
• In-place cleansing risks changing a retained record that may need to remain an immutable historical snapshot.
• Lowering thresholds avoids the quality issue instead of aligning use with current business rules and authoritative data.

Question 4

Topic: Quality in Data Lifecycle and Operations

A customer analytics team fixes missing consent dates during the warehouse load by applying a default date so reports run on time. Profiling shows the same defect appears in 18% of new records each week, all from the web signup form. The privacy steward owns the consent-date quality rule, but the form is managed by the digital product team. Which action is the best quality decision?

Options:

• A. Increase the warehouse cleansing frequency before each report run

• B. Correct the signup form and monitor the rule at capture

• C. Keep the warehouse default and document it in the report notes

• D. Ask analysts to exclude records with default consent dates

Best answer: B

Explanation: Recurring defects created during original capture should be addressed as close to the source as practical. Downstream cleansing can protect a report temporarily, but it hides the capture failure and allows poor-quality data to continue entering the lifecycle. Here, the repeated weekly pattern, single source process, known business impact, and identified rule owner point to source remediation: the privacy steward should confirm the rule and acceptance criteria, and the digital product team should implement the form control. Ongoing monitoring at capture verifies that the prevention works and supports issue closure. The key distinction is one-time or downstream correction versus sustainable prevention of the root cause.

• Report notes preserve transparency but do not stop invalid records from entering the data lifecycle.
• More cleansing improves operational timing but reinforces reliance on a downstream workaround.
• Analyst exclusions reduce reporting risk but shift the burden to consumers and can create inconsistent use of the data.

Question 5

Topic: Quality in Data Lifecycle and Operations

A bank plans to add a third-party small-business firmographic feed to its credit risk model. Early profiling shows 18% of records lack employee count, the vendor refreshes the file monthly, and the business glossary defines employee count differently from the vendor sample file. Legal has not yet confirmed permitted model-use rights. What is the BEST quality decision before production use?

Options:

• A. Require provenance, definitions, cadence, rights, completeness, and validation evidence

• B. Load the feed and impute missing employee counts downstream

• C. Accept the feed because monthly refresh is documented

• D. Use the vendor sample definitions until internal glossary updates are complete

Best answer: A

Explanation: External and third-party data needs stronger intake controls because the organization does not directly control its creation, definitions, refresh cycle, or usage rights. In this case, several facts affect fitness for purpose: missing employee counts affect completeness, conflicting definitions affect semantic consistency, monthly refresh may or may not meet the model’s timeliness need, and model-use rights are unresolved. Before production use, the bank should require evidence covering provenance, business definitions, refresh cadence, legal rights, completeness, and validation against internal expectations. Downstream fixes may still be needed, but they should not replace intake due diligence and governance approval for a regulated risk use case.

• Imputation first treats a symptom but does not resolve rights, definition conflict, provenance, or refresh suitability.
• Refresh-only acceptance overweights one documented fact while ignoring completeness, semantic alignment, validation, and permitted use.
• Vendor definitions alone may create inconsistent risk variables if they are not reconciled with the approved business glossary.

Question 6

Topic: Quality in Data Lifecycle and Operations

A sales organization is onboarding leads from a new partner feed into its CRM. The leads will drive campaign attribution and consent-based outreach. Profiling shows that email format validity is 98%, but 12% of records lack consent_timestamp, country is captured as free text with many variants, and the partner creates records without a stable source identifier. The partner owns the capture form, while Sales Operations owns CRM quality rules. What is the best quality decision before production onboarding?

Options:

• A. Let the CRM assign identifiers and defer lineage capture

• B. Define intake rules for consent, country codes, and source identifiers

• C. Cleanse country values only after the CRM load

• D. Accept the feed because email validity is already high

Best answer: B

Explanation: Quality risks introduced during data creation and acquisition should be addressed as close to the point of capture as practical. Here, the main risks are not email format alone. Missing consent timestamps affect fitness for consent-based outreach, free-text country values create consistency and reference data issues, and missing source identifiers weaken uniqueness, matching, and lineage. Because the partner owns the capture form and Sales Operations owns CRM rules, the best response is to define intake quality rules and ownership before production onboarding. This may include mandatory consent evidence, controlled country values, stable partner record identifiers, exception handling, and stewardship approval for unresolved issues. Downstream cleansing can still help, but it should not be the primary control for defects introduced at capture.

• Email-only focus misses consent, reference data, uniqueness, and lineage risks that are visible in the profile.
• Post-load cleansing treats symptoms after acquisition and does not prevent recurring capture defects.
• Deferred lineage weakens traceability and matching when the source process already lacks stable identifiers.

Question 7

Topic: Quality in Data Lifecycle and Operations

A data quality analyst investigates a scorecard decline for supplier records. The report shows 22% of new supplier records missing TaxRegistrationNumber. Profiling confirms the field is already blank in the source onboarding form data. The integration mapping preserves the source value, and the report counts blanks according to the approved rule. What action best fits the defect?

Options:

• A. Change the report to exclude incomplete suppliers

• B. Replace blanks with default values during integration

• C. Revise the scorecard threshold for completeness

• D. Add validation and ownership at supplier onboarding

Best answer: D

Explanation: Upstream capture quality concerns whether data is created correctly, completely, and validly at the point of entry or acquisition. Here, profiling shows the missing value exists before integration and reporting, while the mapping and report logic behave as approved. That makes the root issue a capture control and stewardship issue, not a downstream transformation or reporting defect. The sustainable response is to add validation, business rule enforcement, and accountable ownership where supplier records are created. Downstream cleansing may mask symptoms, but it does not prevent recurring incomplete supplier records.

• Reporting exclusion hides incomplete records and weakens transparency instead of fixing the capture defect.
• Default substitution can create inaccurate supplier identifiers and masks missing source data.
• Threshold revision changes tolerance, but the evidence points to a process defect requiring remediation.

Question 8

Topic: Quality in Data Lifecycle and Operations

A health insurer stores monthly claims snapshots used for regulatory reporting and actuarial models. Snapshots must remain available for the required retention period, must not be altered or deleted early, and must be trustworthy before downstream marts consume them. A recent incident showed that row-count checks passed even though a stored partition was corrupted. Which operational quality control best addresses the risk?

Options:

• A. Manual approval of archive deletions

• B. Retention-aware integrity and restore verification

• C. Downstream profiling after mart publication

• D. One-time cleansing of corrupted partitions

Best answer: B

Explanation: Storage operations need controls that preserve data quality over time, not only at load time. For retained snapshots, the decisive control must verify that stored data remains intact, cannot be deleted or altered before its retention obligation is met, and can be recovered for business and regulatory use. Integrity checks such as checksums or reconciliation beyond row counts can detect corruption. Restore verification proves availability. Retention-aware enforcement supports compliance. The control should also prevent or flag release to downstream marts when stored data fails verification. Profiling and cleansing may be useful, but they do not by themselves protect retained storage assets across integrity, availability, and retention needs.

• Late profiling may detect some issues after publication, but it does not prevent corrupted retained data from feeding downstream use.
• Deletion approval supports retention governance, but it does not prove stored data integrity or recoverability.
• One-time cleansing fixes a known defect, but it does not create an ongoing operational control for retained snapshots.

Question 9

Topic: Quality in Data Lifecycle and Operations

A data quality lead is reviewing a proposed archive design for order data. Orders older than 2 years will move to low-cost storage. Warranty analysis and regulatory reporting require 5 years of usable history. The proposal keeps order facts but drops historical product hierarchy versions, customer match keys, and validation results. What action best supports data quality through retention?

Options:

• A. Approve the design because order facts are retained

• B. Cleanse archived records only when restored

• C. Retain required context with defined retrieval expectations

• D. Replace history with current product hierarchy values

Best answer: C

Explanation: Retention decisions affect whether stored data remains fit for purpose, not just whether records still exist. In this scenario, the business use requires 5 years of interpretable history. Dropping historical hierarchies, match keys, and validation results would make old orders harder to reconcile, explain, and trust. A sound storage and retention control should specify what data, metadata, reference versions, quality evidence, and retrieval service expectations must be preserved for the approved business and regulatory uses. The key lifecycle point is that archival storage must maintain usability and meaning for retained data, not only reduce storage cost.

• Facts only fails because retained values may be unusable without historical context and quality evidence.
• Cleansing on restore is reactive and may not recover deleted lineage, match keys, or reference versions.
• Current hierarchy replacement can distort historical reporting by applying today’s structure to past transactions.

Question 10

Topic: Quality in Data Lifecycle and Operations

A retailer plans to enrich its customer master with a partner-provided propensity_segment feed for campaign targeting. Initial profiling shows 99.8% completeness, valid code formats, and no duplicate customer IDs. The partner provides no business definition for the segment, no lineage for how it is calculated, and no commitment to notify the retailer if the calculation changes.

Which data quality risk is most important to identify before approving use of the feed?

Options:

• A. Uncontrolled meaning and comparability of the segment over time

• B. Excessive storage cost for the enriched master data

• C. Duplicate customer records in the customer master

• D. Invalid code format in the segment field

Best answer: A

Explanation: Third-party data quality risk is not limited to profile results such as completeness, validity, or uniqueness. A feed can pass technical checks but still be risky if the consuming organization cannot understand its meaning, provenance, calculation method, refresh behavior, or change controls. In this case, the decisive issue is business fitness for purpose: campaign decisions may depend on a segment whose definition or derivation could change without notice. That threatens consistency and comparability over time, even though the values are populated and formatted correctly.

The key takeaway is to assess external data for provenance, semantics, lineage, and provider change management, not just field-level conformance.

• Format validity is already supported by profiling, so it does not address the missing definition and change-control concern.
• Duplicate customers are not indicated because the profile found no duplicate customer IDs.
• Storage cost may be an operational concern, but it is not the data quality risk created by unclear external data provenance.

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 Maturity and Continuous Improvement
• Specialist Cross-Discipline Judgment