What is the purpose of approval rules in a GitLab merge request?

To require a certain number of approvals before the merge request can be merged

To prevent any changes to the source branch

To assign the merge request to a specific developer

To automatically merge the request when tests pass

A project has an approval rule that requires two approvals from members of the 'Backend' group. A developer has just pushed a new commit to the merge request. What happens to the existing approvals on this merge request?

The existing approvals remain valid.

The approvals are only valid if the new commit is a merge commit.

The approvals are automatically updated to reflect the new commit.

The existing approvals are reset and must be obtained again.

A project has an approval rule that requires one approval from a specific user, Alice. Alice has approved the merge request. Later, the MR author pushes a new commit that only updates a documentation file. What is the status of Alice's approval?

The approval is automatically transferred to the new commit.

The approval is reset because the change is not code.

The approval is reset because a new commit was pushed.

GitLabCertified Fundamentals Associate

Domain 3Objective 1

Create and Review Merge Requests GITLAB-CERTIFIED-GIT-ASSOCIATE Practice Questions (Page 3)

Part of the Merge Requests and Issues domain, which makes up ~20% of our current practice bank.

18questions here

4free pages

6concepts

Questions 11–15

11foundation · easy
What is the purpose of approval rules in a GitLab merge request?
Select an answer first
12application · medium
A developer has a merge request with 15 commits, many of which are small fix-ups like 'typo' and 'fix formatting'. The project maintainer prefers a clean history on the main branch. Which merge method should the developer choose to integrate these changes?
Select an answer first
13application · medium
A project has an approval rule that requires two approvals from members of the 'Backend' group. A developer has just pushed a new commit to the merge request. What happens to the existing approvals on this merge request?
Select an answer first
14foundation · easy
Which GitLab merge method combines all commits from the source branch into a single commit on the target branch?
Select an answer first
15application · medium
A project has an approval rule that requires one approval from a specific user, Alice. Alice has approved the merge request. Later, the MR author pushes a new commit that only updates a documentation file. What is the status of Alice's approval?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-GIT-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 GitLab. “GITLAB-CERTIFIED-GIT-ASSOCIATE” is a trademark of its owner, used for identification only.

Create and Review Merge Requests GITLAB-CERTIFIED-GIT-ASSOCIATE Practice Questions (Page 3)

Questions 11–15

What is the purpose of approval rules in a GitLab merge request?

A developer has a merge request with 15 commits, many of which are small fix-ups like 'typo' and 'fix formatting'. The project maintainer prefers a clean history on the main branch. Which merge method should the developer choose to integrate these changes?

A project has an approval rule that requires two approvals from members of the 'Backend' group. A developer has just pushed a new commit to the merge request. What happens to the existing approvals on this merge request?

Which GitLab merge method combines all commits from the source branch into a single commit on the target branch?

A project has an approval rule that requires one approval from a specific user, Alice. Alice has approved the merge request. Later, the MR author pushes a new commit that only updates a documentation file. What is the status of Alice's approval?

Keep studying — Merge Requests and Issues