Databricks-DE-Pro Debugging and Deploying Practice Question
A data engineer is automating the deployment of Databricks assets using CI/CD. The pipeline fails because the 'databricks-cli' command cannot find the workspace. What is the most likely cause?
⚠ Common exam trap
Candidates frequently assume CI/CD deployment failures are caused by syntax errors in configuration files rather than missing runtime environment variables.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The runner does not have the DATABRICKS_HOST and DATABRICKS_TOKEN environment variables set.
Deployment failures in CI/CD often stem from authentication or environment variable misconfiguration. The Databricks CLI requires a properly configured profile or environment variables containing the host URL and token. When these are missing, the CLI fails to authenticate or locate the workspace, preventing the deployment of code. Ensuring that the runner has access to these secure variables is foundational for a reliable DevOps lifecycle for Databricks infrastructure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The Databricks CLI version on the build agent is incompatible with the server.
Why it's wrong here
While CLI versioning can cause issues, the 'cannot find workspace' error specifically points to a connection or authentication failure. Incompatibility errors typically result in command-specific error messages or warnings about deprecated API calls, rather than a failure to locate the workspace itself during the authentication phase.
- ✓
The runner does not have the DATABRICKS_HOST and DATABRICKS_TOKEN environment variables set.
Why this is correct
The Databricks CLI looks for these specific environment variables to authenticate with the workspace. If they are absent, the CLI cannot establish a connection, leading to an error indicating that it cannot reach or find the workspace. This is the most common cause of failures in automated pipelines.
- ✗
The workspace API is currently disabled for security reasons.
Why it's wrong here
If the API were disabled, the error would specifically return a '403 Forbidden' or '401 Unauthorized' response from the server. The CLI indicates it cannot find the workspace, which usually implies that the client-side configuration lacks the necessary endpoint information to even attempt the initial connection.
- ✗
The CI/CD runner is missing the required library dependencies like PySpark.
Why it's wrong here
The Databricks CLI is a standalone binary that does not depend on PySpark for its execution or workspace connection. Missing libraries would only become an issue later if the pipeline attempted to execute Spark code, not during the initial authentication and workspace discovery phase of the deployment.
About these practice questions
One of 267 original Databricks-DE-Pro practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Pro practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Pro exam.