A new data engineer joins a company whose lakehouse is governed by Unity Catalog. The onboarding documentation consistently refers to tables by fully qualified names such as main.sales.orders, and the engineer asks a senior colleague what the three parts of the name mean. Which explanation is accurate?

1. A. main names the metastore, sales is a database, and orders is a table, following the legacy Hive database.table model with a decorative prefix. 💬 A
2. B. main is the catalog, sales is a schema inside it, and orders is a table in that schema, the three-level namespace Unity Catalog enforces. ✓ B
3. C. main names the workspace, sales is the database inside it, and orders is the table, matching the workspace.database.table convention. 💬 C
4. D. main is the cloud region, sales is a storage bucket in that region, and orders is the table stored under that bucket. 💬 D

Reveal answer

Correct answer: main is the catalog, sales is a schema inside it, and orders is a table in that schema, the three-level namespace Unity Catalog enforces.

Reference: https://docs.databricks.com/aws/en/data-governance/unity-catalog/