What are best practices for naming data assets in the Foundry catalog?

• A. Inconsistent naming conventions across assets.
• B. Consistent naming conventions, descriptive names, version suffixes, owner and data domain tags.
• C. Use random strings as names.
• D. Keep names identical to table names in source systems.

Answer: (B)

Naming data assets with consistency and clarity supports discovery, governance, and lifecycle management in Foundry. A well-chosen name communicates what the asset represents, who owns it, and where it fits in the data landscape, so users can find and reuse it confidently as the catalog grows. Consistent naming across assets creates predictable search and filtering behavior, reducing confusion when assets are moved or updated. Descriptive names help users understand the content at a glance, while version suffixes track evolution so current versus earlier iterations aren’t混淆. Including explicit owner information and data domain tags in the asset’s metadata further strengthens accountability and domain alignment. Avoiding inconsistent naming, random strings, or names tied only to source table names prevents search friction, governance ambiguity, and misalignment between the asset’s purpose and its label.