Unity Catalog Naming Conventions: 10 practice questions

Question 1 of 10

Which primary identifier style is recommended for readable Unity Catalog object names?

1. AUppercase words separated by forward slashes
2. BPascalCase words separated by periods
3. CLowercase words separated by underscores
4. DNames containing spaces without backticks

Question 2 of 10

Which catalog naming pattern represents both business domain and lifecycle environment?

1. Asales/prod
2. Bsales_prod
3. Csales.prod
4. DSales Prod

Question 3 of 10

Which name most clearly signals that a catalog is intended for an external audience?

1. Asales_final_report_v1_updated
2. Binternal_sales_raw_data
3. Ccustomer_analytics_shared
4. Dtmp_import_staging

Question 4 of 10

How does Unity Catalog handle the object names `SalesData` and `salesdata`?

1. AIt converts each uppercase letter into an underscore
2. BIt preserves both forms as separate case-sensitive objects
3. CIt stores them in lowercase and resolves them as the same object name
4. DIt rejects the lowercase form but accepts the PascalCase form

Question 5 of 10

Which structure provides the strongest named boundary between development and production data?

1. AOne catalog with table names ending in `_dev` and `_prod`
2. BOne shared catalog whose comments identify the environment
3. CSeparate `sales_dev` and `sales_prod` catalogs
4. DOne schema with mixed development and production objects

Question 6 of 10

What do bronze, silver, and gold schema names communicate in a medallion pattern?

1. ADevelopment, testing, and production workspaces
2. BPublic, internal, and externally shared access levels
3. CRaw, cleaned and validated, and aggregated business-level data
4. DCPU, memory, and storage optimization tiers

Question 7 of 10

Which enforcement mechanism catches invalid names before automated deployment creates objects?

1. AChanging every identifier to PascalCase
2. BAdding version history to each object name
3. CGranting SELECT on all catalogs
4. DNaming validation in the CI/CD pipeline

Question 8 of 10

A company has sales and finance domains in development and production. It needs catalog-level permissions for each domain-environment pair and names that expose both dimensions. Which pattern best fits?

1. A`sales_dev`, `sales_prod`, `finance_dev`, and `finance_prod`
2. B`sales.finance` and `dev.prod` as paired catalog names
3. C`dev`, `prod`, `sales`, and `finance` as four unrelated catalogs
4. DOne `company_data` catalog with all four groups of objects

Question 9 of 10

An external partner will browse a shared analytics catalog. The name must reveal its purpose and sharing status but must not expose the internal department code `d47`. Which choice is best?

1. A`d47_customer_analytics_external`
2. B`Customer Analytics Shared`
3. C`internal_customer_raw_data`
4. D`customer_analytics_shared`

Question 10 of 10

Developers must never modify production data, and auditors want the environment obvious while browsing. Which design satisfies both the communication and enforcement requirements?

1. AAdd `_prod` to table names but grant developers access to the shared catalog
2. BUse `Dev` and `DEV` as separate catalogs with different grants
3. CUse separate `dev` and `prod` catalogs and grant catalog permissions by role
4. DDocument production objects in comments and keep identical permissions