CDS Implementation & Configuration 3 — Questions and Answers
Question 1: A company is implementing a business glossary. Which configuration option ensures that term definitions remain consistent across multiple departments that may use different synonyms?
- Enforcing a single preferred term with approved synonym mapping (Correct answer)
- Allowing each department to maintain its own glossary
- Restricting glossary creation to the IT department only
- Using abbreviations instead of full terms
Correct answer: Enforcing a single preferred term with approved synonym mapping
A preferred term with mapped synonyms allows departmental language flexibility while preserving a single authoritative definition in the glossary.
Question 2: When configuring data lineage tracking in an ETL pipeline, which level of granularity provides the most value for root-cause analysis of data quality issues?
- System-level lineage (source system to target system)
- Job-level lineage (ETL job names and schedules)
- Column-level lineage (field-to-field transformations) (Correct answer)
- Table-level lineage (table names only)
Correct answer: Column-level lineage (field-to-field transformations)
Column-level lineage traces exactly how each field is transformed, enabling precise identification of where incorrect values originate.
Question 3: During MDM implementation, a survivorship rule is configured to prefer values from the system with the most recent 'last_updated' timestamp. What is the main risk of this configuration?
- It increases storage costs significantly
- A system with inaccurate but frequently updated records can corrupt the golden record (Correct answer)
- It slows down the matching process
- It violates GDPR by retaining old timestamps
Correct answer: A system with inaccurate but frequently updated records can corrupt the golden record
Recency does not equal accuracy; a high-frequency but low-quality source can overwrite correct data from a slower but more reliable system.
Question 4: A data steward must configure a workflow for handling data exception tickets. Which configuration feature is essential for ensuring timely resolution?
- Color-coded priority labels
- Automatic escalation rules with SLA timers (Correct answer)
- Daily PDF reports emailed to stakeholders
- A public dashboard showing open tickets
Correct answer: Automatic escalation rules with SLA timers
Automatic escalation with SLA timers ensures that unresolved exceptions are escalated to the appropriate owner before deadlines are missed.
Question 5: When implementing a data retention policy in a governance platform, what must be configured alongside the retention period to ensure compliance?
- A data quality score threshold
- Automated deletion or archival actions triggered at policy expiry (Correct answer)
- A user survey to confirm deletion
- A new data classification for expiring records
Correct answer: Automated deletion or archival actions triggered at policy expiry
Retention policies are only enforceable when paired with automated actions (delete or archive) that execute when the retention period expires.
Question 6: Which integration pattern is most appropriate when connecting a data governance catalog to a cloud data warehouse for automated schema discovery?
- Batch file export via SFTP on a nightly schedule
- API-based push from the warehouse on schema change events (Correct answer)
- Manual CSV import by the data steward
- Email notification of schema changes
Correct answer: API-based push from the warehouse on schema change events
Event-driven API integration ensures the catalog is updated in near-real-time whenever schema changes occur, keeping metadata current.
Question 7: A data steward is configuring matching rules in an MDM system to identify duplicate customer records. Which combination of attributes produces the most reliable probabilistic match?
- Name and email address only
- Name, date of birth, address, and phone number with weighted scoring (Correct answer)
- Customer ID across source systems only
- IP address and browser fingerprint
Correct answer: Name, date of birth, address, and phone number with weighted scoring
Probabilistic matching using multiple weighted attributes reduces false positives and false negatives better than any single identifier.
A company is implementing a business glossary.
Which configuration option ensures that term definitions remain consistent across multiple departments that may use different synonyms?