Question 330Two finance applications exchange dates as free-text strings and disagree on day-month order in regional feeds. A reviewer proposes: Publish a typed interface contract with unambiguous time zone and date formats. Which data-management principle best supports that choice? Interoperability depends on agreements about data structure and meaning, not merely transport success Interoperability requires consistent semantics and explicit data types across heterogeneous systems Common file formats do not establish interoperable meaning unless data conventions are agreed Data joining needs controlled entity resolution when operational identifiers differ or are ambiguous ExplanationCorrect Answer B:Interoperability requires consistent semantics and explicit data types across heterogeneous systems. This is why the recommended action fits the given facts: Two finance applications exchange dates as free-text strings and disagree on day-month order in regional feeds. Verification would show: Integration fixtures from each region resolve to the same intended settlement date.Incorrect Answers A:Interoperability depends on agreements about data structure and meaning, not merely transport success. This does not establish the proposed intervention. The governing principle here is: Interoperability requires consistent semantics and explicit data types across heterogeneous systems. Apply it by: Publish a typed interface contract with unambiguous time zone and date formats. C:Common file formats do not establish interoperable meaning unless data conventions are agreed. This does not establish the proposed intervention. The governing principle here is: Interoperability requires consistent semantics and explicit data types across heterogeneous systems. Apply it by: Publish a typed interface contract with unambiguous time zone and date formats. D:Data joining needs controlled entity resolution when operational identifiers differ or are ambiguous. This does not establish the proposed intervention. The governing principle here is: Interoperability requires consistent semantics and explicit data types across heterogeneous systems. Apply it by: Publish a typed interface contract with unambiguous time zone and date formats.
Question 331A hospital cannot explain how a risk score in a research report was derived from source laboratory readings. If this weakness continues, what is the most directly associated business or data risk? A small source change may silently break many reports Incorrect lineage may produce false impact warnings and conceal true dependencies Impact analysis may rely on obsolete relationships and miss affected consumers High-impact analytical conclusions may be impossible to validate or correct ExplanationCorrect Answer D:High-impact analytical conclusions may be impossible to validate or correct. This follows from the unresolved case facts. The preventive intervention is: Capture end-to-end lineage for source fields, transformations, and report outputs. The reason is: Lineage records data movement and transformation dependencies needed for trust and auditability.Incorrect Answers A:Metadata supports change impact when it links source fields to downstream consumers. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: High-impact analytical conclusions may be impossible to validate or correct. B:Name similarity is not sufficient proof that values share provenance or meaning. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: High-impact analytical conclusions may be impossible to validate or correct. C:Lineage accuracy declines when documentation is detached from actual implementation. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: High-impact analytical conclusions may be impossible to validate or correct.
Question 332A CRM publishes changes to an analytics API without informing consumers of field removals. After the proposed change—Introduce interface change governance with compatibility windows and consumer notification—which observation best verifies that this specific weakness has been addressed? Contract tests reject the incompatible payload and notify the correct interface owner Peak-load testing demonstrates bounded response latency and recorded fallback outcomes A replay test leaves one shipment lifecycle and a recorded duplicate suppression event Contract tests run against supported versions and consumer teams acknowledge retirement dates ExplanationCorrect Answer D:Contract tests run against supported versions and consumer teams acknowledge retirement dates. This is specific evidence for the intervention: Introduce interface change governance with compatibility windows and consumer notification. The underlying principle is: Data integration is a managed service relationship with version and backward-compatibility obligations.Incorrect Answers A:Interoperability depends on agreements about data structure and meaning, not merely transport success. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Contract tests run against supported versions and consumer teams acknowledge retirement dates. B:Integration design must manage availability coupling and failure propagation between services. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Contract tests run against supported versions and consumer teams acknowledge retirement dates. C:A message broker's reliable delivery does not guarantee exactly-once business effects by itself. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Contract tests run against supported versions and consumer teams acknowledge retirement dates.
Question 333A lending platform relies on OCR text to approve collateral files but never checks extraction confidence against the original document. Which data-management action most directly corrects the identified problem? Inventory preservation requirements and validate migrations against representative originals Apply a controlled content taxonomy and relevant patient and encounter metadata Validate critical extracted fields against source images and route low-confidence cases for review Define a validated digitization and records-disposition procedure for source and electronic copies ExplanationCorrect Answer C:Validate critical extracted fields against source images and route low-confidence cases for review. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: Document digitization converts representation but does not itself establish information accuracy. Practical verification is: A sample audit compares loan identifiers, dates, and amounts with original signed sources.Incorrect Answers A:Digital preservation requires maintaining significant properties and context, not merely changing file formats. That is relevant to a different intervention. For the stated situation, the required action is: Validate critical extracted fields against source images and route low-confidence cases for review. The governing reason is: Document digitization converts representation but does not itself establish information accuracy. B:Good document classification makes retrieval and contextual understanding possible without relying solely on filenames. That is relevant to a different intervention. For the stated situation, the required action is: Validate critical extracted fields against source images and route low-confidence cases for review. The governing reason is: Document digitization converts representation but does not itself establish information accuracy. D:Electronic records conversion needs a policy for authentic copies and lawful original handling. That is relevant to a different intervention. For the stated situation, the required action is: Validate critical extracted fields against source images and route low-confidence cases for review. The governing reason is: Document digitization converts representation but does not itself establish information accuracy.
Question 334A retailer trains a customer targeting model on historic promotions that excluded some neighborhoods without considering the effect on underserved groups. Which data-management action most directly corrects the identified problem? Review pricing inference and customer impact under a transparent ethical decision framework Assess representativeness and unfair impact, document mitigations, and monitor outcomes after launch Evaluate re-identification and downstream harm, then minimize data and strengthen access safeguards Implement controlled policy and definition change requests with stakeholder impact analysis ExplanationCorrect Answer B:Assess representativeness and unfair impact, document mitigations, and monitor outcomes after launch. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: Ethical data use requires examining foreseeable unequal harm, not only technical predictive accuracy. Practical verification is: Impact testing compares outcomes across relevant cohorts and tracks investigated disparities.Incorrect Answers A:A profitable or legally permitted data application can still be manipulative or socially harmful. That is relevant to a different intervention. For the stated situation, the required action is: Assess representativeness and unfair impact, document mitigations, and monitor outcomes after launch. The governing reason is: Ethical data use requires examining foreseeable unequal harm, not only technical predictive accuracy. C:Ethical obligations continue where apparently anonymized records can reasonably be linked back to children. That is relevant to a different intervention. For the stated situation, the required action is: Assess representativeness and unfair impact, document mitigations, and monitor outcomes after launch. The governing reason is: Ethical data use requires examining foreseeable unequal harm, not only technical predictive accuracy. D:Governed information standards are versioned products that require managed change and communication. That is relevant to a different intervention. For the stated situation, the required action is: Assess representativeness and unfair impact, document mitigations, and monitor outcomes after launch. The governing reason is: Ethical data use requires examining foreseeable unequal harm, not only technical predictive accuracy.
Question 335A marketplace treats a nightly copy from its catalog to the recommendation platform as a live consistent view. A reviewer proposes: Set documented freshness service levels and monitor replication lag against consumer needs. Which data-management principle best supports that choice? A message broker's reliable delivery does not guarantee exactly-once business effects by itself Data integration is a managed service relationship with version and backward-compatibility obligations Replication creates a copy with measurable latency and does not automatically provide real-time consistency Data joining needs controlled entity resolution when operational identifiers differ or are ambiguous ExplanationCorrect Answer C:Replication creates a copy with measurable latency and does not automatically provide real-time consistency. This is why the recommended action fits the given facts: A marketplace treats a nightly copy from its catalog to the recommendation platform as a live consistent view. Verification would show: Lag alerts and sample source-target comparisons meet approved freshness thresholds.Incorrect Answers A:A message broker's reliable delivery does not guarantee exactly-once business effects by itself. This does not establish the proposed intervention. The governing principle here is: Replication creates a copy with measurable latency and does not automatically provide real-time consistency. Apply it by: Set documented freshness service levels and monitor replication lag against consumer needs. B:Data integration is a managed service relationship with version and backward-compatibility obligations. This does not establish the proposed intervention. The governing principle here is: Replication creates a copy with measurable latency and does not automatically provide real-time consistency. Apply it by: Set documented freshness service levels and monitor replication lag against consumer needs. D:Data joining needs controlled entity resolution when operational identifiers differ or are ambiguous. This does not establish the proposed intervention. The governing principle here is: Replication creates a copy with measurable latency and does not automatically provide real-time consistency. Apply it by: Set documented freshness service levels and monitor replication lag against consumer needs.
Question 336A retailer relies on a schema registry but has no record of who should approve changes to product attributes. After the proposed change—Record data owner, steward, custodian, and change authority within metadata—which observation best verifies that this specific weakness has been addressed? A regulatory-change audit links revised definitions, approvers, and downstream notification dates Catalog links continue to resolve a dataset after renaming with its prior names retained An auditor reconstructs the definition in effect when last year's report was produced An attribute change request routes automatically to the correct accountable approver ExplanationCorrect Answer D:An attribute change request routes automatically to the correct accountable approver. This is specific evidence for the intervention: Record data owner, steward, custodian, and change authority within metadata. The underlying principle is: Administrative metadata clarifies accountability and operational responsibilities for each asset.Incorrect Answers A:Metadata governance supports accountability by recording who changed meanings and when. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An attribute change request routes automatically to the correct accountable approver. B:Metadata identity must persist across renames and versions to preserve references. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An attribute change request routes automatically to the correct accountable approver. C:Metadata changes can alter interpretation of historical datasets and must be auditable. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An attribute change request routes automatically to the correct accountable approver.
Question 337A credit union's backup dashboard reports success without ever testing whether encrypted backups can be decrypted and restored. After the proposed change—Conduct periodic end-to-end restore tests including key availability and data integrity checks—which observation best verifies that this specific weakness has been addressed? A disaster exercise records end-to-end service availability within the approved RTO Failure tests show restored orders lose no more than the approved interval Checksums and restored comparison records agree after an approved repair A sample restore opens records with verified integrity using authorized recovery keys ExplanationCorrect Answer D:A sample restore opens records with verified integrity using authorized recovery keys. This is specific evidence for the intervention: Conduct periodic end-to-end restore tests including key availability and data integrity checks. The underlying principle is: Backup completion is not evidence that a usable recovery can be executed.Incorrect Answers A:RTO concerns elapsed service restoration time and includes dependencies beyond the file restore. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A sample restore opens records with verified integrity using authorized recovery keys. B:RPO describes tolerated data loss in time and is distinct from how long restoration takes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A sample restore opens records with verified integrity using authorized recovery keys. C:Data availability does not imply data integrity; corruption can be latent until later reads or replication. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A sample restore opens records with verified integrity using authorized recovery keys.
Question 338A large retailer's product master merges different packaging sizes because the matching algorithm ignores unit quantity. If this weakness continues, what is the most directly associated business or data risk? Sensitive balances and risk flags may be wrongly associated across customers Payments or compliance checks may be redirected to a different legal entity Orders may be fulfilled with the wrong package size or quantity One customer may receive duplicate or conflicting service decisions ExplanationCorrect Answer C:Orders may be fulfilled with the wrong package size or quantity. This follows from the unresolved case facts. The preventive intervention is: Define business identity rules that include product variant, pack size, and commercial attributes. The reason is: Master-data matching must reflect the real-world entity granularity needed by the business.Incorrect Answers A:False-positive identity matches can be more harmful than leaving records separate pending investigation. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Orders may be fulfilled with the wrong package size or quantity. B:Master-data updates can alter who a counterparty is, not just a descriptive field. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Orders may be fulfilled with the wrong package size or quantity. D:Master data management reconciles business entities across systems rather than simply copying records. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Orders may be fulfilled with the wrong package size or quantity.
Question 339A bank's fraud model receives yesterday's account status while new closures are recorded continuously. Which data-management action most directly corrects the identified problem? Monitor attribute and event completeness by source, time, and criticality Establish cross-system consistency rules and reconcile amounts using common effective rates Define freshness expectations and monitor data currency at decision time Add referential integrity and approved-master cross-reference checks ExplanationCorrect Answer C:Define freshness expectations and monitor data currency at decision time. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: Currency concerns whether data is sufficiently up to date for a purpose and may differ from delivery punctuality alone. Practical verification is: Decision-time tests show the latest relevant status within an approved freshness threshold.Incorrect Answers A:Completeness describes the presence of required data, not its correctness or timely arrival. That is relevant to a different intervention. For the stated situation, the required action is: Define freshness expectations and monitor data currency at decision time. The governing reason is: Currency concerns whether data is sufficiently up to date for a purpose and may differ from delivery punctuality alone. B:Consistency evaluates agreement among related representations under defined semantics. That is relevant to a different intervention. For the stated situation, the required action is: Define freshness expectations and monitor data currency at decision time. The governing reason is: Currency concerns whether data is sufficiently up to date for a purpose and may differ from delivery punctuality alone. D:Integrity concerns relationships and constraints among related data, not just value formatting. That is relevant to a different intervention. For the stated situation, the required action is: Define freshness expectations and monitor data currency at decision time. The governing reason is: Currency concerns whether data is sufficiently up to date for a purpose and may differ from delivery punctuality alone.
Question 340A hospital labels every analyst a data steward but no one performs dictionary reviews, issue triage, or definition stewardship. After the proposed change—Specify steward duties, capacity, workflows, and measures for the clinical data domain—which observation best verifies that this specific weakness has been addressed? Steward task queues show accepted definitions, investigated issues, and overdue escalations The contract, RACI, and supplier assurance reviews show ongoing internal oversight Ticket histories show accountable decisions, root-cause fixes, and prevention checks Board reports identify risk owners, significant breaches, and tracked remediation decisions ExplanationCorrect Answer A:Steward task queues show accepted definitions, investigated issues, and overdue escalations. This is specific evidence for the intervention: Specify steward duties, capacity, workflows, and measures for the clinical data domain. The underlying principle is: Stewardship requires assigned ongoing activities and accountability rather than an honorary designation.Incorrect Answers B:Delegating processing or custody does not remove the organization's accountability for its information. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Steward task queues show accepted definitions, investigated issues, and overdue escalations. C:Issue management needs joint business-technical ownership aligned with the cause of the data problem. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Steward task queues show accepted definitions, investigated issues, and overdue escalations. D:Data risk is an enterprise business accountability rather than exclusively an IT operational issue. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Steward task queues show accepted definitions, investigated issues, and overdue escalations.