Databricks Data Engineer Associate · Free practice question 10 of 12
Compute policies for cluster governance
Workspace admins at Yelverton Labs want to limit which instance types and maximum sizes users can choose when they create classic clusters, and to require specific cost-center tags. Which feature is designed for this?
- A.Serverless SQL warehouses
- B.Unity Catalog row filters
- C.Compute (cluster) policies
- D.Databricks Git folders
Show answer and explanation
Correct answer: C. Compute (cluster) policies
Why: Compute policies define rules that constrain cluster configuration, such as allowed instance types, maximum sizes, and required tags, and they can be assigned to users and groups. Serverless SQL warehouses are a type of compute rather than a way to constrain it, row filters restrict table rows, and Git folders provide version control.
More free Databricks Data Engineer Associate questions
- Delta shallow vs deep clone
- Auto Loader schema hints
- Reading notebook task parameters
- collect_set vs collect_list aggregation
- Triggered vs continuous pipeline mode
- Job maximum concurrent runs
- Job task timeout setting
- SHOW GRANTS on Unity Catalog objects
- Transferring object ownership
- ALTER TABLE ADD COLUMNS on Delta
- Spark lazy evaluation transformations vs actions