DP-750 — Frequently Asked Questions

Shared compute is interactive and mixes workloads across users, so it cannot guarantee production isolation or per-run autoscaling for scheduled, non-interactive telemetry pipelines.

No. Photon is a performance accelerator; autoscaling comes from running ingestion on an autoscaling job compute cluster instead of a fixed-node all-purpose cluster.

The assets table must be created in finance.procurement, so the session must first switch the current catalog to finance, then set the current schema to procurement.

It is valid fully qualified syntax, but the exhibit provides separate USE CATALOG and USE SCHEMA targets, so the expected drag values are finance, procurement, and assets.

Liquid clustering handles high-cardinality columns and evolving filter patterns without re-partitioning, while partitioning on CustomerId would create too many small files and degrade performance.

Deletion vectors mark rows as deleted without rewriting full Parquet files, so compliance updates and deletes complete faster and with less write amplification.

No. Databricks Runtime ML includes GPU-capable libraries, but GPU acceleration requires a GPU-enabled VM node type; a general purpose node has no GPU to accelerate.

A single-node cluster runs only a driver with no worker nodes, so there are no executors to spread tasks across; distributed training needs a multi-node cluster with workers.

No. dbutils.secrets.get resolves storageKey from kv-secure on each call, so Notebook1 always sees the value the cloud security team last published.

Only read access to the secret (Get). List, write, delete or Secrets Officer roles are not needed for retrieval and violate least privilege.

The hotspot allows only one property; delta.deletedFileRetentionDuration is the one that lets VACUUM reclaim deleted data files. Log retention can be managed separately.

No. VACUUM runs online and readers can query the table; unreferenced files are removed after the retention threshold.

ALL PRIVILEGES includes MANAGE, which allows group1 to grant permissions, violating the 'cannot grant permissions' requirement.

Yes, USE CATALOG on catalog1 is required to access the catalog before using schema1 and creating tables.

No — the connector is the Azure resource that carries the identity. The authentication is the managed identity it uses, which is why that is the credential-free dropdown choice.

READ VOLUME on Volume1 (plus USE CATALOG and USE SCHEMA on its parents). WRITE VOLUME would allow modification and breaks least privilege.

Both sources are file-based in ADLS Gen2 and require schema drift handling; Auto Loader provides incremental ingestion with schema evolution and exactly-once semantics.

The weather data comes from a custom REST API; a Databricks notebook allows custom HTTP calls, while Lakeflow Connect is typically for supported databases and SaaS apps.

The two options conflict. ignoreChanges is the deprecated Delta streaming setting and Databricks raises an error when it is combined with a CDF read; use skipChangeCommits instead.

insert, update_preimage, update_postimage and delete. The preimage/postimage pair lets the downstream pipeline replay each update deterministically.