DATABRICKS-DEP Question 9

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A0

  - Correct answer : A — Point the bundle's `whl` library entry at a workspace file or Unity Catalog volume path, since storing library files in the DBFS root is deprecated and disabled by default on Databricks Runtime 15.1 and above. A . Storing library files in the DBFS root is deprecated and disabled by default starting with Databricks Runtime 15.1, so a `whl` entry pointing at a `dbfs:/` path stops resolving on those runtimes. Moving the wheel to a workspace file or Unity Catalog volume path is the supported replacement location. B . There is no `dbfs_root_enabled` cluster spec setting; Databricks Runtime 15.1 disables DBFS root library storage by default rather than gating it behind a flag that jobs can re-enable, so adding this setting would not fix the failure. C . Downgrading the runtime does not address the underlying storage-location problem and abandons current runtime features solely to work around a deprecation; it also misstates which runtimes support wheel installs from arbitrary locations. D . Maven coordinates resolve Java or Scala artifacts from a Maven repository and are not a valid packaging format for a Python wheel, so repackaging the wheel this way does not bypass the DBFS root restriction or make the library installable.