Memory hook: Workspace runs work; catalog governs data.
Must remember
- Choose interactive/classic compute for suitable development, job compute for automated work, SQL warehouses for SQL/BI and supported serverless compute to reduce infrastructure management. Compare isolation, startup time, cost and feature support.
- Configure runtime/Spark version, node type/count, autoscaling, termination and pools to match the workload. Photon accelerates supported execution; it is not a cure for every skewed query or Python UDF bottleneck.
- Install compatible libraries and manage compute permissions separately from data privileges. A user able to attach to compute should not automatically read every catalog.
- Unity Catalog organizes catalog.schema.object names. Tables store/query data; volumes govern files; views define queries; materialized views persist supported results with refresh behavior.
- Managed tables delegate more storage lifecycle to the platform; external tables reference externally managed locations. Foreign catalogs expose supported external systems through governed connections.
- Use naming/environment boundaries, comments and ownership to make assets discoverable. AI/BI Genie instructions can explain trusted metrics and context, but do not replace correct permissions or semantic definitions.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Scheduled production transformation | A job-oriented/serverless option with a pinned supported runtime and scoped identity. |
| Govern non-tabular files | Unity Catalog volumes with appropriate privileges and storage credentials. |
Traps
- A workspace is not the same security object as a catalog.
- An external table does not automatically mean unrestricted access to its storage.
Active recall
1. What is the three-part object name?
Catalog, schema and object.
2. Why pin a runtime?
To control Spark/library behavior and avoid untested changes.
3. What does auto-termination reduce?
Idle compute cost for supported compute types.
4. How does a materialized view differ from a view?
It persists computed results and has supported refresh/maintenance behavior.
5. Why document Genie instructions?
To align natural-language analysis with approved business definitions and context.