Question 780A university validates a student age field only as an integer, allowing negative ages through admissions forms. After the proposed change—Define business-valid age ranges and enforce them at relevant capture points—which observation best verifies that this specific weakness has been addressed? Quality tests flag known placeholders and demonstrate improved usable contact coverage Boundary tests reject invalid ages while valid applicants proceed successfully A test set of future and implausible birth dates is rejected or routed for approved review Source-specific completeness rates expose the failing partner and improve after remediation ExplanationCorrect Answer B:Boundary tests reject invalid ages while valid applicants proceed successfully. This is specific evidence for the intervention: Define business-valid age ranges and enforce them at relevant capture points. The underlying principle is: Syntactic type correctness does not ensure a value satisfies domain rules.Incorrect Answers A:A nonblank value can still be semantically missing or invalid for its declared purpose. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Boundary tests reject invalid ages while valid applicants proceed successfully. C:Validity assesses whether values conform to specified business and format rules, not merely whether they are present. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Boundary tests reject invalid ages while valid applicants proceed successfully. D:Completeness describes the presence of required data, not its correctness or timely arrival. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Boundary tests reject invalid ages while valid applicants proceed successfully.
Question 781An online lending platform changes authorization roles without testing whether analysts gained permission to export identity documents. If this weakness continues, what is the most directly associated business or data risk? Personal payroll information may be exposed through lower-security test systems A routine role update may open a new exfiltration route Insider misuse or accidental disclosure of patient information becomes more likely Payment credentials could be captured or altered in transit ExplanationCorrect Answer B:A routine role update may open a new exfiltration route. This follows from the unresolved case facts. The preventive intervention is: Test access-control changes against approved entitlements before release and monitor privileged changes. The reason is: Authorization changes can unintentionally expand the reach of sensitive data.Incorrect Answers A:Production confidentiality requirements continue when sensitive data is copied into development and testing. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A routine role update may open a new exfiltration route. C:Access rights should reflect approved duties and data sensitivity rather than broad team membership. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A routine role update may open a new exfiltration route. D:Internal network placement does not eliminate interception or impersonation risk. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A routine role update may open a new exfiltration route.
Question 782A bank reports a data table is certified but no one records the certification criteria, reviewer, or review date. Which data-management action most directly corrects the identified problem? Version metadata and retain effective dates, reviewer, and change history Maintain an auditable metadata change log with ownership, approval, and effective-date history Publish certification metadata with decision rules, evidence, approver, and validity period Propagate sensitivity classifications and authorized-use metadata to catalog search ExplanationCorrect Answer C:Publish certification metadata with decision rules, evidence, approver, and validity period. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: Trust labels are meaningful only when supported by explicit governance and auditable qualification. Practical verification is: Certified assets display approval evidence and expired certifications are withdrawn or renewed.Incorrect Answers A:Metadata changes can alter interpretation of historical datasets and must be auditable. That is relevant to a different intervention. For the stated situation, the required action is: Publish certification metadata with decision rules, evidence, approver, and validity period. The governing reason is: Trust labels are meaningful only when supported by explicit governance and auditable qualification. B:Metadata governance supports accountability by recording who changed meanings and when. That is relevant to a different intervention. For the stated situation, the required action is: Publish certification metadata with decision rules, evidence, approver, and validity period. The governing reason is: Trust labels are meaningful only when supported by explicit governance and auditable qualification. D:Metadata about security and permitted use must survive harvesting and downstream catalog distribution. That is relevant to a different intervention. For the stated situation, the required action is: Publish certification metadata with decision rules, evidence, approver, and validity period. The governing reason is: Trust labels are meaningful only when supported by explicit governance and auditable qualification.
Question 783A bank keeps a product code in a loan table without a relationship constraint to the approved product catalog. A reviewer proposes: Model the product relationship and implement suitable referential integrity. Which data-management principle best supports that choice? Recursive relationships require business rules to prevent impossible self-referential structures Many-to-many relationships usually require an explicit association in relational implementation Repeating values in one field impede first normal form and reliable relational operations Foreign keys express relationships and prevent references to nonexistent parents where enforced ExplanationCorrect Answer D:Foreign keys express relationships and prevent references to nonexistent parents where enforced. This is why the recommended action fits the given facts: A bank keeps a product code in a loan table without a relationship constraint to the approved product catalog. Verification would show: Invalid product codes fail validation and valid loans join to existing product records.Incorrect Answers A:Recursive relationships require business rules to prevent impossible self-referential structures. This does not establish the proposed intervention. The governing principle here is: Foreign keys express relationships and prevent references to nonexistent parents where enforced. Apply it by: Model the product relationship and implement suitable referential integrity. B:Many-to-many relationships usually require an explicit association in relational implementation. This does not establish the proposed intervention. The governing principle here is: Foreign keys express relationships and prevent references to nonexistent parents where enforced. Apply it by: Model the product relationship and implement suitable referential integrity. C:Repeating values in one field impede first normal form and reliable relational operations. This does not establish the proposed intervention. The governing principle here is: Foreign keys express relationships and prevent references to nonexistent parents where enforced. Apply it by: Model the product relationship and implement suitable referential integrity.
Question 784A transportation platform patches its database engine in production without validating driver compatibility or rollback procedures. A reviewer proposes: Test patches against dependent applications and use a governed backup and rollback plan. Which data-management principle best supports that choice? Database operations must control changes that can affect service compatibility and recoverability RTO concerns elapsed service restoration time and includes dependencies beyond the file restore Concurrent database operations can block or deadlock when transaction lock order conflicts Replication can faithfully copy corruption or deletion; it is not a substitute for recoverable backups ExplanationCorrect Answer A:Database operations must control changes that can affect service compatibility and recoverability. This is why the recommended action fits the given facts: A transportation platform patches its database engine in production without validating driver compatibility or rollback procedures. Verification would show: Preproduction integration tests pass and a rollback rehearsal meets service targets.Incorrect Answers B:RTO concerns elapsed service restoration time and includes dependencies beyond the file restore. This does not establish the proposed intervention. The governing principle here is: Database operations must control changes that can affect service compatibility and recoverability. Apply it by: Test patches against dependent applications and use a governed backup and rollback plan. C:Concurrent database operations can block or deadlock when transaction lock order conflicts. This does not establish the proposed intervention. The governing principle here is: Database operations must control changes that can affect service compatibility and recoverability. Apply it by: Test patches against dependent applications and use a governed backup and rollback plan. D:Replication can faithfully copy corruption or deletion; it is not a substitute for recoverable backups. This does not establish the proposed intervention. The governing principle here is: Database operations must control changes that can affect service compatibility and recoverability. Apply it by: Test patches against dependent applications and use a governed backup and rollback plan.
Question 785A regulator's casework repository permits users to replace signed decisions without preserving earlier versions. A reviewer proposes: Use immutable or controlled record preservation, audit histories, and authorized amendment workflows. Which data-management principle best supports that choice? Authenticity and integrity are essential recordkeeping properties beyond simple document accessibility A visible signature image alone does not demonstrate authenticated approval of a fixed record Digital preservation requires maintaining significant properties and context, not merely changing file formats Content management must distinguish authoritative controlled records from working drafts ExplanationCorrect Answer A:Authenticity and integrity are essential recordkeeping properties beyond simple document accessibility. This is why the recommended action fits the given facts: A regulator's casework repository permits users to replace signed decisions without preserving earlier versions. Verification would show: A reviewer can reconstruct the original decision and each authorized correction with timestamps.Incorrect Answers B:A visible signature image alone does not demonstrate authenticated approval of a fixed record. This does not establish the proposed intervention. The governing principle here is: Authenticity and integrity are essential recordkeeping properties beyond simple document accessibility. Apply it by: Use immutable or controlled record preservation, audit histories, and authorized amendment workflows. C:Digital preservation requires maintaining significant properties and context, not merely changing file formats. This does not establish the proposed intervention. The governing principle here is: Authenticity and integrity are essential recordkeeping properties beyond simple document accessibility. Apply it by: Use immutable or controlled record preservation, audit histories, and authorized amendment workflows. D:Content management must distinguish authoritative controlled records from working drafts. This does not establish the proposed intervention. The governing principle here is: Authenticity and integrity are essential recordkeeping properties beyond simple document accessibility. Apply it by: Use immutable or controlled record preservation, audit histories, and authorized amendment workflows.
Question 786A public agency uses a zero value to encode both 'no income' and 'income unknown'. Which data-management action most directly corrects the identified problem? Separate stable customer attributes from transactional shipments and reference customer keys Model the many-to-many relationship with an associative entity and defined business attributes Represent contract-plan relationships with explicit validity periods and constraints Define explicit nullable or status attributes that distinguish missing from zero ExplanationCorrect Answer D:Define explicit nullable or status attributes that distinguish missing from zero. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: A missing value has different semantics from a valid numerical zero. Practical verification is: Validation distinguishes true zero incomes, unavailable evidence, and not-applicable cases.Incorrect Answers A:Normalization reduces update anomalies when attributes belong to different entities. That is relevant to a different intervention. For the stated situation, the required action is: Define explicit nullable or status attributes that distinguish missing from zero. The governing reason is: A missing value has different semantics from a valid numerical zero. B:Many-to-many relationships usually require an explicit association in relational implementation. That is relevant to a different intervention. For the stated situation, the required action is: Define explicit nullable or status attributes that distinguish missing from zero. The governing reason is: A missing value has different semantics from a valid numerical zero. C:Relational models should make changing cardinality and time-dependent associations explicit. That is relevant to a different intervention. For the stated situation, the required action is: Define explicit nullable or status attributes that distinguish missing from zero. The governing reason is: A missing value has different semantics from a valid numerical zero.
Question 787A monthly inventory report mixes beginning-of-month balances with end-of-month quantities in one fact table. After the proposed change—Use an explicit periodic snapshot grain and consistent observation dates—which observation best verifies that this specific weakness has been addressed? Current inventory can be reconstructed or directly observed according to a documented snapshot policy Inventory balances are reproducible for each period and comparable across warehouses A sample order reconciles line totals without duplicating revenue after joins A stated freshness warning and approved faster decision feed prevent stale-limit decisions ExplanationCorrect Answer B:Inventory balances are reproducible for each period and comparable across warehouses. This is specific evidence for the intervention: Use an explicit periodic snapshot grain and consistent observation dates. The underlying principle is: Snapshot facts represent measured state at defined intervals and cannot be casually mixed with transactions.Incorrect Answers A:Transactional facts and snapshot facts represent fundamentally different observation grains. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Inventory balances are reproducible for each period and comparable across warehouses. C:Dimensional modeling depends on one declared event or snapshot grain for each fact row. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Inventory balances are reproducible for each period and comparable across warehouses. D:A warehouse optimized for periodic reporting may not satisfy operational real-time use cases. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Inventory balances are reproducible for each period and comparable across warehouses.
Question 788A warehouse team stores a customer name only in every shipment line and repeatedly updates thousands of lines when the name changes. Which data-management action most directly corrects the identified problem? Normalize order-line relationships into separate rows and enforce appropriate keys Separate transactional write models from dimensional analytical representations Separate stable customer attributes from transactional shipments and reference customer keys Separate entities that have different identities, lifecycles, and legal meanings ExplanationCorrect Answer C:Separate stable customer attributes from transactional shipments and reference customer keys. This intervention addresses the scenario rather than a neighboring data concern. The governing concept is: Normalization reduces update anomalies when attributes belong to different entities. Practical verification is: A customer rename requires one controlled master change and existing shipments remain linked.Incorrect Answers A:Repeating values in one field impede first normal form and reliable relational operations. That is relevant to a different intervention. For the stated situation, the required action is: Separate stable customer attributes from transactional shipments and reference customer keys. The governing reason is: Normalization reduces update anomalies when attributes belong to different entities. B:Dimensional models optimize analytical measurement and are not automatically authoritative transaction stores. That is relevant to a different intervention. For the stated situation, the required action is: Separate stable customer attributes from transactional shipments and reference customer keys. The governing reason is: Normalization reduces update anomalies when attributes belong to different entities. D:Distinct business objects should not be collapsed merely because a workflow commonly links them. That is relevant to a different intervention. For the stated situation, the required action is: Separate stable customer attributes from transactional shipments and reference customer keys. The governing reason is: Normalization reduces update anomalies when attributes belong to different entities.
Question 789A shared patient identity service uses one global identifier but never records when source hospital identifiers are merged or separated. If this weakness continues, what is the most directly associated business or data risk? Contradictory customer identities can spread through analytics and operational decisions Premature physical choices can obscure business meaning and weaken interoperability Performance metrics may be wrong when delayed data is treated as on-time events A mistaken merge can contaminate clinical information across institutions ExplanationCorrect Answer D:A mistaken merge can contaminate clinical information across institutions. This follows from the unresolved case facts. The preventive intervention is: Model identity relationships and provenance explicitly and maintain reversible crosswalk decisions. The reason is: Enterprise identity architecture needs traceable identity resolution rather than assuming one unchanging source key.Incorrect Answers A:Data architecture describes how enterprise information assets and relationships fit across business capabilities and systems. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A mistaken merge can contaminate clinical information across institutions. B:Conceptual, logical, and physical representations answer different architecture and modeling questions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A mistaken merge can contaminate clinical information across institutions. C:Temporal meaning must be explicit when distributed data describes when things happened versus when systems learned of them. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A mistaken merge can contaminate clinical information across institutions.
Question 790A manufacturer discards thousands of supplier records when a mandatory field is blank instead of assessing business impact. If this weakness continues, what is the most directly associated business or data risk? Quality dashboards can accumulate warnings without improving real data Blanket rejection may interrupt operations unnecessarily or hide root causes High-impact billing errors may go unresolved behind low-risk cleanup work Critical financial-crime gaps may be invisible behind healthy enterprise averages ExplanationCorrect Answer B:Blanket rejection may interrupt operations unnecessarily or hide root causes. This follows from the unresolved case facts. The preventive intervention is: Classify quality exceptions by severity and route them through proportionate remediation workflows. The reason is: Data quality management balances fitness for purpose, consequence, and cost rather than demanding zero defects universally.Incorrect Answers A:Data-quality measurement only helps when linked to accountable decisions and corrective action. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Blanket rejection may interrupt operations unnecessarily or hide root causes. C:Quality tolerances should reflect consequences and fitness for business purpose. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Blanket rejection may interrupt operations unnecessarily or hide root causes. D:Aggregate quality scores can hide concentrated risks that matter to specific controls. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Blanket rejection may interrupt operations unnecessarily or hide root causes.