Question 670A retailer tries to infer lineage solely from matching column names, creating false relationships between unrelated sales fields. If this weakness continues, what is the most directly associated business or data risk? High-impact analytical conclusions may be impossible to validate or correct Analysts may misclassify customer service states from opaque codes Incorrect lineage may produce false impact warnings and conceal true dependencies Impact analysis may rely on obsolete relationships and miss affected consumers ExplanationCorrect Answer C:Incorrect lineage may produce false impact warnings and conceal true dependencies. This follows from the unresolved case facts. The preventive intervention is: Validate inferred lineage against executed transformations and owner-reviewed mappings. The reason is: Name similarity is not sufficient proof that values share provenance or meaning.Incorrect Answers A:Lineage records data movement and transformation dependencies needed for trust and auditability. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Incorrect lineage may produce false impact warnings and conceal true dependencies. B:A technical column name alone rarely conveys the semantics needed for correct reuse. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Incorrect lineage may produce false impact warnings and conceal true dependencies. D: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: Incorrect lineage may produce false impact warnings and conceal true dependencies.
Question 671A large retailer's product master merges different packaging sizes because the matching algorithm ignores unit quantity. After the proposed change—Define business identity rules that include product variant, pack size, and commercial attributes—which observation best verifies that this specific weakness has been addressed? A reviewed sample preserves distinct package sizes while merging genuine duplicates A challenged matching set retains distinct identities and documents exception review High-impact identity changes show verified documentation and approval audit trails A reviewed sample shows legitimate merges and retained source provenance ExplanationCorrect Answer A:A reviewed sample preserves distinct package sizes while merging genuine duplicates. This is specific evidence for the intervention: Define business identity rules that include product variant, pack size, and commercial attributes. The underlying principle is: Master-data matching must reflect the real-world entity granularity needed by the business.Incorrect Answers B:False-positive identity matches can be more harmful than leaving records separate pending investigation. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A reviewed sample preserves distinct package sizes while merging genuine duplicates. C:Master-data updates can alter who a counterparty is, not just a descriptive field. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A reviewed sample preserves distinct package sizes while merging genuine duplicates. D:Master data management reconciles business entities across systems rather than simply copying records. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A reviewed sample preserves distinct package sizes while merging genuine duplicates.
Question 672A fraud-detection application reads a synchronous profile API that routinely times out during peak order traffic. If this weakness continues, what is the most directly associated business or data risk? Network retries can turn one payroll instruction into multiple payments Dependent applications can fail after a technically successful upstream deployment An outage in one information service can halt unrelated customer orders Material reported numbers may be impossible to explain or recreate ExplanationCorrect Answer C:An outage in one information service can halt unrelated customer orders. This follows from the unresolved case facts. The preventive intervention is: Introduce timeouts, bounded retries, circuit-breaker behavior, and safe fallback decisions. The reason is: Integration design must manage availability coupling and failure propagation between services.Incorrect Answers A:Distributed integration cannot assume a failed acknowledgment means an operation never occurred. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An outage in one information service can halt unrelated customer orders. B:Data integration is a managed service relationship with version and backward-compatibility obligations. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An outage in one information service can halt unrelated customer orders. D:Reproducibility requires traceability through data movements and transformations. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An outage in one information service can halt unrelated customer orders.
Question 673A large retailer's product master merges different packaging sizes because the matching algorithm ignores unit quantity. A reviewer proposes: Define business identity rules that include product variant, pack size, and commercial attributes. Which data-management principle best supports that choice? False-positive identity matches can be more harmful than leaving records separate pending investigation Master-data matching must reflect the real-world entity granularity needed by the business Master-data updates can alter who a counterparty is, not just a descriptive field Master data management reconciles business entities across systems rather than simply copying records ExplanationCorrect Answer B:Master-data matching must reflect the real-world entity granularity needed by the business. This is why the recommended action fits the given facts: A large retailer's product master merges different packaging sizes because the matching algorithm ignores unit quantity. Verification would show: A reviewed sample preserves distinct package sizes while merging genuine duplicates.Incorrect Answers A:False-positive identity matches can be more harmful than leaving records separate pending investigation. This does not establish the proposed intervention. The governing principle here is: Master-data matching must reflect the real-world entity granularity needed by the business. Apply it by: Define business identity rules that include product variant, pack size, and commercial attributes. C:Master-data updates can alter who a counterparty is, not just a descriptive field. This does not establish the proposed intervention. The governing principle here is: Master-data matching must reflect the real-world entity granularity needed by the business. Apply it by: Define business identity rules that include product variant, pack size, and commercial attributes. D:Master data management reconciles business entities across systems rather than simply copying records. This does not establish the proposed intervention. The governing principle here is: Master-data matching must reflect the real-world entity granularity needed by the business. Apply it by: Define business identity rules that include product variant, pack size, and commercial attributes.
Question 674A global insurer publishes a central country-code table but does not maintain retired codes or effective dates. Which data-management action most directly corrects the identified problem? Version reference data with validity periods and controlled code retirement Govern reference-code retirement with contract tests and communicated transition dates Create governed reference-value definitions, owners, and approved code translations Model and master distinct address roles with effective dates and provenance ExplanationCorrect Answer A:Version reference data with validity periods and controlled code retirement. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: Reference values change over time; consumers need the version applicable to their business event. Practical verification is: Historical policy tests interpret country codes using the correct effective dates.Incorrect Answers B:Reference data is a controlled dependency whose changes affect many consuming systems. That is relevant to a different intervention. For the stated situation, the required action is: Version reference data with validity periods and controlled code retirement. The governing reason is: Reference values change over time; consumers need the version applicable to their business event. C:Reference data standardizes permitted categories and interpretation across business processes. That is relevant to a different intervention. For the stated situation, the required action is: Version reference data with validity periods and controlled code retirement. The governing reason is: Reference values change over time; consumers need the version applicable to their business event. D:Master attributes must reflect business meaning; one entity may legitimately have multiple related attributes. That is relevant to a different intervention. For the stated situation, the required action is: Version reference data with validity periods and controlled code retirement. The governing reason is: Reference values change over time; consumers need the version applicable to their business event.
Question 675A telecommunications group calls its database administrator the business owner of marketing consent because the administrator runs the platform. Which data-management action most directly corrects the identified problem? Assign business accountability to the appropriate domain owner and technical custody to the administrator Create a data-issue workflow that assigns domain owners, technical partners, root causes, and due dates Assign executive sponsorship, material-risk reporting thresholds, and board-level oversight Retain accountable business ownership and specify supplier controls, reporting, and audit rights ExplanationCorrect Answer A:Assign business accountability to the appropriate domain owner and technical custody to the administrator. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: A data owner makes business decisions while a data custodian implements technical safeguards and operations. Practical verification is: The responsibility matrix separates approved consent rules from database access and backup duties.Incorrect Answers B:Issue management needs joint business-technical ownership aligned with the cause of the data problem. That is relevant to a different intervention. For the stated situation, the required action is: Assign business accountability to the appropriate domain owner and technical custody to the administrator. The governing reason is: A data owner makes business decisions while a data custodian implements technical safeguards and operations. C:Data risk is an enterprise business accountability rather than exclusively an IT operational issue. That is relevant to a different intervention. For the stated situation, the required action is: Assign business accountability to the appropriate domain owner and technical custody to the administrator. The governing reason is: A data owner makes business decisions while a data custodian implements technical safeguards and operations. D:Delegating processing or custody does not remove the organization's accountability for its information. That is relevant to a different intervention. For the stated situation, the required action is: Assign business accountability to the appropriate domain owner and technical custody to the administrator. The governing reason is: A data owner makes business decisions while a data custodian implements technical safeguards and operations.
Question 676A charity adds a required donor phone column to a shared table without testing historical records or downstream forms. After the proposed change—Manage model evolution with compatibility analysis, migrations, and contract testing—which observation best verifies that this specific weakness has been addressed? Migration tests pass for old rows and all supported clients before production release Benchmark queries and integrity tests justify selected indexes without changing logical meaning Plan change history reconstructs the active plan at each invoice event Queries can join each order to its individual items without string parsing ExplanationCorrect Answer A:Migration tests pass for old rows and all supported clients before production release. This is specific evidence for the intervention: Manage model evolution with compatibility analysis, migrations, and contract testing. The underlying principle is: Logical schema changes affect existing data and dependent applications beyond new DDL syntax.Incorrect Answers B:Physical optimization should support validated business structure and observed workload needs. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Migration tests pass for old rows and all supported clients before production release. C:Relational models should make changing cardinality and time-dependent associations explicit. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Migration tests pass for old rows and all supported clients before production release. D:Repeating values in one field impede first normal form and reliable relational operations. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Migration tests pass for old rows and all supported clients before production release.
Question 677A payments warehouse has adequate storage but dashboard queries scan massive raw event tables for each refresh. Which data-management action most directly corrects the identified problem? Design aggregate tables with drill-through to the supported detail grain Define the fact grain precisely and test relationship cardinality before aggregating measures Use appropriate dimensional structures, preaggregation, partitions, or incremental materialization based on query plans Add finance-approved control totals, reconciliation thresholds, and ownership to the warehouse pipeline ExplanationCorrect Answer C:Use appropriate dimensional structures, preaggregation, partitions, or incremental materialization based on query plans. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: Warehouse performance depends on physical design matched to analytical workload and query patterns. Practical verification is: Query plans and refresh times improve while detailed totals still reconcile.Incorrect Answers A:Aggregations accelerate queries but must preserve required analytical granularity. That is relevant to a different intervention. For the stated situation, the required action is: Use appropriate dimensional structures, preaggregation, partitions, or incremental materialization based on query plans. The governing reason is: Warehouse performance depends on physical design matched to analytical workload and query patterns. B:Dimensional modeling depends on one declared event or snapshot grain for each fact row. That is relevant to a different intervention. For the stated situation, the required action is: Use appropriate dimensional structures, preaggregation, partitions, or incremental materialization based on query plans. The governing reason is: Warehouse performance depends on physical design matched to analytical workload and query patterns. D:Analytical trust requires evidence that transformed facts reconcile to authoritative business systems. That is relevant to a different intervention. For the stated situation, the required action is: Use appropriate dimensional structures, preaggregation, partitions, or incremental materialization based on query plans. The governing reason is: Warehouse performance depends on physical design matched to analytical workload and query patterns.
Question 678An insurer stores many policyholders and many policies in one table with repeated combinations and no bridge entity. If this weakness continues, what is the most directly associated business or data risk? Billing may apply an obsolete or contradictory subscription plan Reporting can loop indefinitely or double-count balances in cyclic hierarchies Coverage ownership can become ambiguous or impossible to change safely Orphan loan records may bypass product pricing and regulatory logic ExplanationCorrect Answer C:Coverage ownership can become ambiguous or impossible to change safely. This follows from the unresolved case facts. The preventive intervention is: Model the many-to-many relationship with an associative entity and defined business attributes. The reason is: Many-to-many relationships usually require an explicit association in relational implementation.Incorrect Answers A:Relational models should make changing cardinality and time-dependent associations explicit. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Coverage ownership can become ambiguous or impossible to change safely. B:Recursive relationships require business rules to prevent impossible self-referential structures. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Coverage ownership can become ambiguous or impossible to change safely. D:Foreign keys express relationships and prevent references to nonexistent parents where enforced. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Coverage ownership can become ambiguous or impossible to change safely.
Question 679An insurer's finance ledger and claims mart disagree because two integration paths apply different currency conversions. After the proposed change—Establish cross-system consistency rules and reconcile amounts using common effective rates—which observation best verifies that this specific weakness has been addressed? A reviewed set of identity candidates has controlled merges and falling duplicate rates Sample ledger and mart totals reconcile within documented rounding tolerances Decision-time tests show the latest relevant status within an approved freshness threshold Invalid aircraft references trigger traceable exceptions and valid flights reconcile to the fleet master ExplanationCorrect Answer B:Sample ledger and mart totals reconcile within documented rounding tolerances. This is specific evidence for the intervention: Establish cross-system consistency rules and reconcile amounts using common effective rates. The underlying principle is: Consistency evaluates agreement among related representations under defined semantics.Incorrect Answers A:Uniqueness evaluates whether real-world entities or records are represented without unacceptable duplication. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Sample ledger and mart totals reconcile within documented rounding tolerances. C:Currency concerns whether data is sufficiently up to date for a purpose and may differ from delivery punctuality alone. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Sample ledger and mart totals reconcile within documented rounding tolerances. D:Integrity concerns relationships and constraints among related data, not just value formatting. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Sample ledger and mart totals reconcile within documented rounding tolerances.
Question 680A finance team replaces monthly batch extracts with streaming updates but fails to assess dependent reconciliations and cutoff controls. A reviewer proposes: Evaluate transition impacts on downstream reporting cadence, controls, and reconciliation semantics. Which data-management principle best supports that choice? Architecture changes must preserve required business capabilities and observable data behavior across consumers Data architecture describes how enterprise information assets and relationships fit across business capabilities and systems Transition architecture requires a credible current state to identify change impact and migration constraints Architecture standards should reduce unnecessary technology lock-in and enable reliable information exchange ExplanationCorrect Answer A:Architecture changes must preserve required business capabilities and observable data behavior across consumers. This is why the recommended action fits the given facts: A finance team replaces monthly batch extracts with streaming updates but fails to assess dependent reconciliations and cutoff controls. Verification would show: Parallel-run evidence reconciles reporting periods, late entries, and settlement totals.Incorrect Answers B:Data architecture describes how enterprise information assets and relationships fit across business capabilities and systems. This does not establish the proposed intervention. The governing principle here is: Architecture changes must preserve required business capabilities and observable data behavior across consumers. Apply it by: Evaluate transition impacts on downstream reporting cadence, controls, and reconciliation semantics. C:Transition architecture requires a credible current state to identify change impact and migration constraints. This does not establish the proposed intervention. The governing principle here is: Architecture changes must preserve required business capabilities and observable data behavior across consumers. Apply it by: Evaluate transition impacts on downstream reporting cadence, controls, and reconciliation semantics. D:Architecture standards should reduce unnecessary technology lock-in and enable reliable information exchange. This does not establish the proposed intervention. The governing principle here is: Architecture changes must preserve required business capabilities and observable data behavior across consumers. Apply it by: Evaluate transition impacts on downstream reporting cadence, controls, and reconciliation semantics.