A new data engineer needs to start working with an existing codebase that is stored in a Git repository. They have been told to use Databricks Git Folders. What is the first step the engineer should take in the Databricks workspace UI?

Open the Git Folders section in the sidebar and add the repository URL.

Click 'Create Pull Request' in the workspace to import the repository.

Use the 'Commit' button in the workspace to clone the repository.

Create a new notebook and manually copy all the code from the repository.

What is the purpose of the 'Push' action in a Databricks Git folder?

To create a new branch in the local repository

To upload local commits to the remote repository

To download the latest changes from the remote repository

To merge the current branch with the main branch

A data engineer has committed a fix to a bug on a local feature branch in a Databricks Git folder. The team's CI/CD pipeline only builds from the remote repository. What must the engineer do in the Databricks workspace UI to make the fix available to the pipeline?

Click 'Commit' again with a new message to ensure the change is saved.

Click 'Pull' in the Git folder to sync the remote branch with the local branch.

Click 'Create Pull Request' to merge the change into the main branch automatically.

Click 'Push' in the Git folder to upload the local commit to the remote feature branch.

When committing changes in a Databricks Git folder, what information must a user provide?

A commit message describing the changes

The cluster ID to run the commit on

The target branch for the commit

In the Databricks Git folder UI, how can a user initiate a pull request?

By clicking the 'Create Pull Request' button in the Git folder toolbar

By changing the remote URL in the Git folder settings

By deleting the current branch and re-cloning the repository

By restarting the cluster and reattaching the Git folder

DatabricksCertified Data Engineer Associate

Domain 5Objective 1

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 2)

Part of the Implementing CI/CD domain, which accounts for 10% of the DATA-ENGINEER-ASSOCIATE exam. Databricks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~4–6 in this domain), expect 1–2 from this objective — we provide 24 practice questions to prepare you well beyond it. (estimate)

24questions here

5free pages

6concepts

10%of the exam

Questions 6–10

6application · medium
A new data engineer needs to start working with an existing codebase that is stored in a Git repository. They have been told to use Databricks Git Folders. What is the first step the engineer should take in the Databricks workspace UI?
Select an answer first
7foundation · easy
What is the purpose of the 'Push' action in a Databricks Git folder?
Select an answer first
8application · medium
A data engineer has committed a fix to a bug on a local feature branch in a Databricks Git folder. The team's CI/CD pipeline only builds from the remote repository. What must the engineer do in the Databricks workspace UI to make the fix available to the pipeline?
Select an answer first
9foundation · easy
When committing changes in a Databricks Git folder, what information must a user provide?
Select an answer first
10foundation · easy
In the Databricks Git folder UI, how can a user initiate a pull request?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DATA-ENGINEER-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Databricks. “DATA-ENGINEER-ASSOCIATE” is a trademark of its owner, used for identification only.