Databricks Machine Learning Associate Question 21
Single answerYou are working on a Databricks notebook and need to save your changes to an external Git repository. Before pushing your changes, you decide to create a new branch to isolate your work. What is the correct sequence of actions to create a new branch and commit your changes to the external Git provider from within Databricks?
- A
Open the Git integration tab, select 'Create New Branch', make your changes in the notebook, and click 'Commit & Push'.
- B
Open the notebook, make your changes, navigate to the Git integration tab, create a new branch, and click 'Commit & Push'.
- C
Make changes in the notebook, navigate to the Git integration tab, create a new branch, add a commit message, and click 'Commit & Push'.
- D
Create a new branch in the external Git provider manually, make changes in the notebook, and push the changes from Databricks.
Show answer and explanation
Correct answer: C
Explanation
To commit changes to an external Git provider while using Databricks, it's crucial to follow the proper sequence within the Databricks Git integration interface. After making changes in the notebook, you should create a new branch within Databricks, add a commit message, and use the 'Commit & Push' functionality. This ensures the changes are linked to the correct branch and version control is properly maintained.
- A. Incorrect.
This option is incorrect because you need to make your changes first, then create the new branch and commit. The order described here is not accurate.
- B. Incorrect.
This option is incorrect because you must create the new branch after making changes, but this sequence inaccurately places 'create new branch' before saving your changes.
- C. Correct.
This is the correct answer. The correct sequence is to first make changes in the notebook, then navigate to the Git integration tab, create a new branch, add a commit message, and click 'Commit & Push', which ensures the changes are properly associated with the new branch.
- D. Incorrect.
This option is incorrect because creating a branch directly in the external Git provider manually bypasses the Databricks Git integration workflow, which is part of the certification scope.