How can Git operations must be performed outside of Databricks Repos?
Select an option, then click Submit answer.
Reference / correct answer:
Most accepted answer: C. Merge
Community votes: C=6, D=5
Selected Answer: D Correct Answer: D. Clone Explanation: In Databricks Repos, you can perform most common Git operations such as: Commit/Pull/Push/Branch switching/Merge (via pull request) directly inside Databricks Repos UI or via Repos APIs. However, there is one Git operation that cannot be done inside Databricks Repos —which is git clone Why “Clone” must be done outside Databricks Repos: You don’t clone manually using git clone in Databricks. Instead, you link a remote Git repository to a Databricks Repo using the Repos UI or REST API — Databricks internally performs the cloning for you. Therefore, the clone operation (as you would perform with git clone on your local machine) is not supported directly inside Databricks Repos. upvoted 5 times
Selected Answer: D Correct answer "D" Clone Note: Other advanced commands like git cherry-pick or git stash are also not natively supported in the UI and typically require using the Databricks web terminal or API. upvoted 1 times
Selected Answer: C If you still need to clone it then it's not a Databricks repo yet. Wording is odd. upvoted 2 times
Selected Answer: D should be D upvoted 1 times
Selected Answer: D Yes, the wording is a bit awkward. A clearer way to phrase the question would be: "Which Git operation cannot be performed inside Databricks Repos and must be done externally?" The intent is to identify the operation that Databricks Repos does not support directly. Among the options: Commit, Pull, Merge → Supported inside Databricks Repos. Clone → Must be done outside, because you need to create the repo first before linking it to Databricks. So the correct answer remains D. Clone, but the question could definitely be rephrased for clarity. upvoted 2 times