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

Questions 11–15

1. 11foundation · easy

   What is the purpose of branch protection rules in a source control system like GitHub?

   • ATo create a backup of the branch on a separate server.
   • BTo automatically merge all pull requests without review.
   • CTo prevent direct pushes to critical branches and require changes to go through pull requests.
   • DTo rename the branch to follow a naming convention.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   Which component is commonly integrated into a pull request workflow to enforce code quality?

   • AA script that renames the branch after every merge.
   • BBranch policies that require a minimum number of reviewers and successful builds.
   • CA manual process where developers email their changes to the team lead for approval.
   • DA scheduled task that deletes merged branches automatically.
   Reveal Solution Discussion Select an answer first
4. 13expert · hard

   A team manages a release branch for a critical product. They want to allow only the release manager to merge changes into the release branch, but they also want to allow developers to create pull requests targeting the release branch for review. They want to prevent developers from directly pushing to the release branch. What is the best way to achieve this?

   • ACreate a separate branch for each release and merge them to main only after release.
   • BSet the release branch as read-only for all users, and have the release manager manually apply changes from pull requests.
   • CAllow all developers to push to the release branch but require a build validation policy.
   • DConfigure branch permissions on the release branch to allow only the release manager to push, and set up a branch policy that requires the release manager as a reviewer for all pull requests.
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   A team uses a feature branch strategy. They have a requirement that feature branches must be merged to main within 3 days of creation to avoid long-lived branches. They also want to ensure that no feature branch is merged without passing the full test suite. However, some features take longer than 3 days to complete. What is the best way to handle this conflict?

   • AUse feature toggles to merge incomplete features behind a flag, allowing the branch to be merged within 3 days while keeping the feature disabled in production.
   • BExtend the merge deadline to 2 weeks for all features.
   • CAllow feature branches to exist indefinitely as long as they are rebased regularly.
   • DMerge feature branches to main only when the feature is fully complete, regardless of time.
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   What is the primary purpose of a pull request in a source control workflow?

   • ATo synchronize a local repository with the latest changes from the remote repository.
   • BTo create a backup of the repository on a remote server.
   • CTo automatically deploy code to production without any human intervention.
   • DTo propose changes from a branch and request that they be reviewed and merged into another branch.
   Reveal Solution Discussion Select an answer first