Design and Implement Branching Strategies for the Source Code AZ-400 Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   Which statement best describes trunk-based development?

   • AA separate branch is created for every environment, and code is promoted through them sequentially.
   • BDevelopers work on long-lived feature branches and merge them only at the end of a release cycle.
   • CEach developer maintains a personal fork and periodically syncs with the main repository.
   • DAll developers integrate their changes into a single shared branch, often multiple times per day.
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Which branch policy can be configured to require that code changes compile and pass tests before merging?

   • AWork item linking
   • BBuild validation
   • CComment resolution
   • DBranch naming convention
   Reveal Solution Discussion Select an answer first
4. 18expert · hard

   A team wants to enforce that all pull requests to the main branch have a successful build and at least one approval. They also want to prevent the 'squash merge' option from being used, because they want to preserve the commit history. However, some developers prefer squash merges for cleaner history. What is the best way to enforce this?

   • AAsk developers to manually avoid using squash merge and rely on code review.
   • BUse a pre-receive hook to reject squash merges on the server.
   • CAllow developers to choose the merge type, but require a build validation policy.
   • DConfigure the branch policy on main to require build validation and a minimum number of reviewers, and set the repository setting to disable squash merge for pull requests targeting main.
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A team has a release branch for version 1.0 and a main branch for version 2.0 development. They want to ensure that bug fixes made to the release branch are also applied to the main branch, but they do not want to merge the entire release branch into main because it contains version-specific changes. What is the best approach?

   • AMerge the entire release branch into main and resolve any conflicts.
   • BUse cherry-pick to apply the specific bug fix commits from the release branch to the main branch.
   • CRecreate the bug fix directly on the main branch without referencing the release branch.
   • DUse a branch policy to automatically merge all changes from the release branch to main.
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A large organization wants to adopt trunk-based development but has a compliance requirement that every change to the main branch must be reviewed by a security specialist. They also want to maintain a high velocity of integration. They are concerned that requiring a security review on every pull request will slow down the process. What is the best approach to balance compliance and velocity?

   • ARequire a security specialist on every pull request regardless of the change, to ensure full compliance.
   • BUse a branch policy that requires a security specialist as a reviewer only for changes that modify files in security-sensitive directories, using path-based branch policies.
   • CUse a separate security review branch where all changes are merged before going to main.
   • DSkip security reviews and rely on automated security scanning in the CI pipeline.
   Reveal Solution Discussion Select an answer first