Objective: Apply a Feature/topic Branching Workflow GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   In GitLab, which action typically happens BEFORE a merge request can be merged into the main branch?

   • AThe feature branch is renamed to match the main branch.
   • BThe feature branch is deleted from the remote.
   • CThe merge request receives the required approvals from reviewers.
   • DThe main branch is pushed to the remote.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   During a merge, Git reports a conflict in 'config.py'. What does this indicate?

   • AThe file is too large to be merged automatically.
   • BThe file was deleted on both branches.
   • CThe file has changes in both branches that Git cannot automatically combine.
   • DThe file is not tracked by Git.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Which branch name best follows a descriptive and consistent topic-branch naming convention for a task that adds a password reset feature?

   • Anew-branch-1
   • Bfeature/password-reset
   • Cpassword
   • Dfix-123
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   A team has a protected main branch that requires one approval. A developer has created a merge request and received one approval. However, the developer then pushes a new commit to the feature branch to fix a minor typo. What happens to the approval?

   • AThe approval is reset, and the merge request requires a new approval.
   • BThe approval is automatically transferred to the new commit.
   • CThe approval remains valid, but the merge request is blocked until the typo is fixed.
   • DThe approval remains valid, and the merge request can be merged immediately.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   While merging a feature branch 'feature/checkout' into main, GitLab reports a merge conflict in the file 'cart.js'. The developer needs to resolve this conflict. What is the most appropriate first step?

   • AAbandon the merge request and create a new one from a fresh branch.
   • BDelete the file 'cart.js' and recreate it from the main branch.
   • CEdit the file 'cart.js' in the GitLab web IDE to resolve the conflict and commit the changes.
   • DForce push the feature branch to overwrite the main branch.
   Reveal Solution Discussion Select an answer first