An organization has merged datasets from several legacy applications, and analysts keep encountering different field labels for the same customer attributes, leading to reporting errors. To avoid future mismatched references, which governance measure will most effectively promote uniform field names across all systems?
Create a data dictionary to standardize field names and periodically review compliance
Use a data glossary without enforcing consistent naming rules
Permit developers to name fields based on individual preferences to ensure code is readable in the context which it was written
Allow departments to create their own local naming conventions
Developing a data dictionary fosters consistent usage and reduces confusion. Creating a shared repository for field names makes it simpler to keep systems aligned. Allowing departments to establish their own data definitions or relying on informal conventions can lead to inconsistencies. Promoting ad hoc approaches to field naming may undermine standardization efforts.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a data dictionary and why is it important?
Open an interactive chat with Bash
How is a data dictionary different from a data glossary?
Open an interactive chat with Bash
What are the best practices for maintaining a data dictionary?