Your team is working on a large Databricks project with multiple concurrent features. You need to ensure that the main branch is always deployable and that features are isolated until they are ready. Which branching strategy best meets these requirements?

Use a single branch where all developers commit directly.

Use feature branches with pull requests to main, and require CI checks to pass before merging.

Use tags on main to mark releases and allow direct commits to main.

Use a long-lived development branch and merge to main at the end of each sprint.

Microsoft Certified:Azure Databricks Data Engineer Associate

Domain 4Objective 3

Implement Development Lifecycle Processes in Azure Databricks DP-750 Practice Questions (Page 8)

Part of the Deploy and maintain data pipelines and workloads domain, which accounts for 30–35% of the DP-750 exam. Microsoft does not publish an official question count, but from its 120-minute exam (~50–80 total, ~15–28 in this domain), expect 4–7 from this objective — we provide 36 practice questions to prepare you well beyond it. (estimate)

36questions here

8free pages

12concepts

30–35%of the exam

Questions 36–36

36expert · hard
Your team is working on a large Databricks project with multiple concurrent features. You need to ensure that the main branch is always deployable and that features are isolated until they are ready. Which branching strategy best meets these requirements?
Select an answer first

Finished these 1 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to DP-750

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 Microsoft. “DP-750” is a trademark of its owner, used for identification only.

Implement Development Lifecycle Processes in Azure Databricks DP-750 Practice Questions (Page 8)

Questions 36–36

Your team is working on a large Databricks project with multiple concurrent features. You need to ensure that the main branch is always deployable and that features are isolated until they are ready. Which branching strategy best meets these requirements?

Keep studying — Deploy and maintain data pipelines and workloads