Manage Your Code Development Workflow Within the Databricks Workspace UI, Including Creating and Switching Between Branches in Databricks Git Folders (formerly Databricks Repos), Committing and Pushing Changes, and Creating Pull Requests Using Databricks Git Integration. DATA-ENGINEER-ASSOCIATE Practice Questions (Page 5)

Questions 21–24

1. 21foundation · easy

   In the Databricks workspace UI, which tab provides access to Git integration features for managing code repositories?

   • ARepos
   • BData
   • CCompute
   • DJobs
   Reveal Solution Discussion Select an answer first
2. 22application · medium

   A data engineer is working on a hotfix in a Git folder. They need to temporarily switch from the 'feature/dashboard' branch to the 'main' branch to check the production code. They have uncommitted changes in the 'feature/dashboard' branch. What should the engineer do in the Databricks workspace UI to switch branches safely?

   • APush the uncommitted changes to the remote 'feature/dashboard' branch, then switch to 'main'.
   • BCommit the uncommitted changes on 'feature/dashboard' first, then use the branch selector to switch to 'main'.
   • CDelete the 'feature/dashboard' branch and recreate it later after checking 'main'.
   • DUse the branch selector to switch to 'main' immediately; Databricks will automatically save the uncommitted changes.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   What is the correct way to switch between existing branches in a Databricks Git folder?

   • ARestart the cluster and reattach the Git folder
   • BChange the remote URL to point to a different repository
   • CDelete the current branch and re-clone the repository
   • DUse the branch selector to choose the desired branch
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   A data engineer is working in a Git folder in the Databricks workspace. They need to develop a new feature in isolation from the main codebase. They have already opened the Git folder and are viewing the current branch in the UI. What should the engineer do first to start working on the new feature?

   • AClick 'Commit' in the Git folder UI, enter a commit message, and commit the current changes to the main branch.
   • BClick 'Push' in the Git folder UI to upload the current branch to the remote repository.
   • CClick 'Pull' in the Git folder UI to fetch the latest changes from the remote repository.
   • DClick the branch selector in the Git folder, click 'Create Branch', enter a name, and select the current branch as the source.
   Reveal Solution Discussion Select an answer first