Unity Catalog Tables, Views, and Materialized Views: 10 practice questions

Question 1 of 10

Which object type is the default table type in Unity Catalog?

1. AA managed table
2. BA view object
3. CA materialized view
4. DA dynamic view

Question 2 of 10

How does a standard view produce its result?

1. AIt runs its defining query whenever the view is accessed
2. BIt reads a cached Delta result until a scheduled refresh
3. CIt persists copied source rows in managed table storage
4. DIt applies user-dependent masks without executing its defining query

Question 3 of 10

What does a materialized view store?

1. AOnly primary-key metadata for a managed source table
2. BA precomputed query result stored as a Delta table
3. CA query definition with no stored result
4. DA row-filter definition with no precomputed query result

Question 4 of 10

How can a table be addressed after its catalog and schema context have been set?

1. ABy its storage path after `USE MATERIALIZED VIEW`
2. BBy its short table name after `USE CATALOG` and `USE SCHEMA`
3. CBy a schema name alone after `USE TABLE`
4. DBy a two-level catalog and table name that omits the required schema level

Question 5 of 10

How do Unity Catalog primary-key and foreign-key constraints behave?

1. AThey cache joined rows for later materialized-view refreshes
2. BThey mask key columns according to the querying user
3. CThey document relationships but do not enforce referential integrity
4. DThey reject every write that violates any referenced primary or foreign key value

Question 6 of 10

Which view capability can return different rows or masked columns according to the querying user?

1. AA materialized view with one daily cached result shared unchanged by all account groups
2. BA managed table with an informational foreign key
3. CA standard view with an unconditional projection
4. DA dynamic view with conditional filters and masks

Question 7 of 10

What must source tables provide to support incremental refresh of a materialized view?

1. ADelta tables with row tracking enabled
2. BManaged tables with foreign keys enforced
3. CMasked views
4. DDelta tables with informational primary keys but row tracking disabled

Question 8 of 10

A dashboard repeatedly runs an expensive aggregation, many users issue the same query, and results may lag behind source changes until a scheduled update. Which object best fits?

1. AA standard view
2. BA dynamic view that masks columns by account group
3. CA managed table recreated for every dashboard request
4. DA materialized view refreshed on a schedule

Question 9 of 10

Analysts need current sales rows, auditors must see email addresses, other users must see redacted values, and the team will not maintain separate copies. Which object should be created?

1. AA standard view that returns the email column unchanged
2. BA managed table containing a separate row for each audience
3. COne cached view
4. DA dynamic view with a user-aware column mask

Question 10 of 10

A new dataset must persist as primary stored data, Azure Databricks must manage its files, and removing the object must also remove those files. Which object meets all requirements?

1. AA standard view created over an existing table
2. BA managed table created with column definitions
3. CA materialized view refreshed from a source query
4. DA dynamic view containing user-dependent filters