Data Analyst Associate · Domain 1: Understanding of Databricks Data Intelligence Platform (Lakehouse Platform) · 11% of the exam
Task 1.2: Understand catalogs, schemas, managed and external tables, access controls, views, certified tables, metric views, and lineage within the Catalog Explorer interface
The catalog and schema hierarchy, managed versus external tables, views and metric views, certified and deprecated flags, ownership and grants, and the lineage graph as Catalog Explorer shows them.
Study it
Catalog Explorer: catalogs, schemas, managed and external tables, views and metric views
Lesson coming
Certified tables, access controls and lineage in Catalog Explorer
Lesson coming
Sample questions
Try each one before opening the answer. Every option is explained, with the Databricks documentation page that proves it.
Question 1 · choose 1
A notebook reads main.raw.orders into a temporary table, cleans it there, and writes the result to the permanent table main.gold.daily_orders. An analyst opens the lineage graph of main.gold.daily_orders in Catalog Explorer. What does it show upstream of the table?
AThe temporary table, with main.raw.orders upstream of it
BNo upstream tables, because the data passed through a temporary table
Cmain.raw.orders, connected directly to main.gold.daily_orders
Dmain.raw.orders, but only after the temporary table has been dropped
Show the answer and why
AThe temporary table, with main.raw.orders upstream of it
Incorrect
Temporary tables don't appear in lineage; the graph does not show a node for it.
BNo upstream tables, because the data passed through a temporary table
Incorrect
The temporary table does not break lineage; the permanent tables on each side are connected.
Cmain.raw.orders, connected directly to main.gold.daily_orders
Correct
When a temporary table sits between permanent tables, lineage connects the permanent upstream table directly to the permanent downstream table.
Dmain.raw.orders, but only after the temporary table has been dropped
Incorrect
The direct connection is recorded when the lineage is captured; it does not wait for the temporary table to be dropped.
Unity Catalog captures lineage for queries run on Databricks. Temporary tables don't appear in lineage: when one sits between permanent tables, lineage connects the permanent upstream tables directly to the permanent downstream table, at both the table and column level, and the connection stays after the temporary table is gone.
In the schema main.sales, the customers table has a primary key on customer_id, and the orders table has a foreign key on customer_id that references it; customers itself has no foreign key. A new analyst wants to see in Catalog Explorer which tables are related by these key constraints, with the key columns marked. Which view should she open?
AThe lineage graph on the Lineage tab of main.sales.orders
BThe Entity Relationship Diagram, opened from main.sales.customers
CThe Insights tab of main.sales.orders, with its frequent queries and joins
DThe Entity Relationship Diagram, opened from main.sales.orders
Show the answer and why
AThe lineage graph on the Lineage tab of main.sales.orders
Incorrect
The lineage graph shows how tables connect through query data flow, not through declared constraints.
BThe Entity Relationship Diagram, opened from main.sales.customers
Incorrect
The ERD is reached from a table that contains a foreign key constraint; customers holds only the primary key.
CThe Insights tab of main.sales.orders, with its frequent queries and joins
Incorrect
Table insights show frequent queries, users and joined tables from usage, not declared key constraints with the key columns marked.
DThe Entity Relationship Diagram, opened from main.sales.orders
Correct
The ERD shows primary key and foreign key relationships between tables in a graph, and it opens from a table with a foreign key, which orders has.
The Entity Relationship Diagram in Catalog Explorer shows the primary key and foreign key relationships between tables, with icons next to key columns. It is available when viewing a table that contains a foreign key constraint, so it opens from the referencing table. To explore how tables connect through query data flow instead, use the lineage graph.
An analyst wants a view that combines main.sales.orders with finance.ref.fx_rates, a table in another catalog. What does the documentation say about views in Unity Catalog?
AA view can reference only tables in its own schema
BA view can reference other schemas but not other catalogs
CA view stores a copy of the joined rows and must be refreshed
DIt can read tables and views in other schemas and catalogs
Show the answer and why
AA view can reference only tables in its own schema
Incorrect
Views can be created from tables and views in multiple schemas.
BA view can reference other schemas but not other catalogs
Incorrect
Views can also use tables and views in other catalogs.
CA view stores a copy of the joined rows and must be refreshed
Incorrect
A view is the read-only result of a query; it does not store a copy to refresh.
DIt can read tables and views in other schemas and catalogs
Correct
You can create a view from tables and from other views in multiple schemas and catalogs.
A view is a read-only object that is the result of a query over one or more tables and views in a Unity Catalog metastore, and it can draw on tables and views in multiple schemas and catalogs.
An analyst wants to create a metric view but has never written a metric view YAML definition. Where can she build one interactively?
AOnly in a notebook, by writing the YAML definition in Python
BIn the Catalog Explorer UI editor, without writing any YAML
CIn the dashboard canvas, by dragging a table onto a page
DIn the SQL warehouse settings, under Advanced options
Show the answer and why
AOnly in a notebook, by writing the YAML definition in Python
Incorrect
Catalog Explorer has a UI editor, so writing YAML is not required.
BIn the Catalog Explorer UI editor, without writing any YAML
Correct
Catalog Explorer provides a visual interface for creating metric views without writing a YAML definition.
CIn the dashboard canvas, by dragging a table onto a page
Incorrect
Unity Catalog metric views are created in Catalog Explorer or with SQL or YAML, not by placing a table on a canvas.
DIn the SQL warehouse settings, under Advanced options
Incorrect
Warehouse settings configure compute; metric views are not defined there.
Catalog Explorer provides a visual interface for creating metric views: on the UI tab you define fields and measures interactively, and a YAML editor is also available for those who want to edit the definition directly.
A team renamed the table main.sales.orders_v1 to main.sales.orders. Analysts then notice that Catalog Explorer shows main.sales.orders without any of the lineage that was recorded before the change. Why?
ALineage is kept only for views, not for tables
BLineage appears only after the renamed table is optimized
CLineage is not preserved when an object is renamed
DLineage is stored for 24 hours and then removed
Show the answer and why
ALineage is kept only for views, not for tables
Incorrect
Unity Catalog lineage covers tables, views, columns and more.
BLineage appears only after the renamed table is optimized
Incorrect
Lineage does not depend on table maintenance.
CLineage is not preserved when an object is renamed
Correct
The lineage page lists this limitation: renamed objects do not keep their lineage.
DLineage is stored for 24 hours and then removed
Incorrect
Lineage shown in Catalog Explorer is retained indefinitely.
Unity Catalog captures lineage automatically and Catalog Explorer retains it indefinitely, but lineage is not preserved for renamed catalogs, schemas, tables, views or columns.
An analyst wants to create a view in the schema main.reports. She already holds USE CATALOG on main and USE SCHEMA on main.reports, and SELECT on the tables the view reads. Which privilege on the schema does she still need?
ACREATE VIEW
BCREATE TABLE
CMODIFY
DREAD VOLUME
Show the answer and why
ACREATE VIEW
Incorrect
The documented privilege for creating a view in a schema is CREATE TABLE.
BCREATE TABLE
Correct
Creating a view needs USE CATALOG on the catalog and USE SCHEMA and CREATE TABLE on the schema.
CMODIFY
Incorrect
MODIFY concerns changing data in tables; it is not the privilege for creating views.
DREAD VOLUME
Incorrect
READ VOLUME is for files in volumes.
To create a view you need USE CATALOG on the parent catalog and USE SCHEMA and CREATE TABLE on the parent schema, plus access to the objects the view reads.