A data analyst at a retail company wants to confidently use only high-quality, authoritative datasets for their quarterly revenue report. Their Databricks workspace is enabled for Unity Catalog. Which combination of Unity Catalog features and behaviors BEST supports the analyst in discovering trustworthy datasets, confirming their quality status, and querying them alongside internal tables?
Answer & explanation
Correct answer: B
WHY B: Unity Catalog supports discovery through Catalog Explorer and the workspace search bar, where data stewards apply 'Certified' endorsements (also called quality labels or certifications) to tables validated as authoritative and high-quality. The endorsement appears as a visual indicator in Catalog Explorer next to the table's description, owner, tags and documentation, so analysts identify trustworthy datasets without opening data files or reading logs. The table is then queried with the standard three-part namespace (catalog.schema.table), the same syntax as any registered table. Certification is a discoverability and governance feature, not a query restriction: certified tables are queried like uncertified ones and can be joined freely with other Unity Catalog tables in one SQL statement.
WHY NOT A: Parsing the _delta_log directory is not a supported or documented way to identify certified datasets. Delta transaction logs record DML/DDL operations, schema evolution and file statistics and have no concept of a quality certificate entry. The CERTIFIED ONLY keyword does not exist in Databricks SQL.
WHY NOT C: There is no system-provisioned certified_data catalog; certified tables stay in their normal catalog and schema, and the endorsement can be applied to a registered table in any catalog. No cross-catalog certification restriction exists: Unity Catalog allows joining tables across catalogs in a single SQL query with the three-part namespace.
WHY NOT D: Unity Catalog does support quality endorsements and certification labels at the table level, a documented feature available through Catalog Explorer and the REST API. User-defined tags can also be applied, but the 'Certified' endorsement is a distinct, first-class UI feature with dedicated treatment in search and Catalog Explorer, not an arbitrary custom tag.
WHY NOT E: No databricks unity-catalog certify CLI command exists. Certification is managed through the Catalog Explorer UI or the REST API via the table properties endpoint, not through a CLI quality-scan pipeline, and tables are not moved to a system.certified schema on the basis of profiling scores.