What happens to existing approvals when a new commit is pushed to a merge request with 'Require approval on code changes' enabled?

The approvals are reset and must be provided again

The approvals are transferred to the new commit author

The merge request is automatically merged

The approvals remain valid for the new commit

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

To restrict which branches can be created in a project

To specify which users or groups must approve a merge request before it can be merged

To define the maximum number of commits allowed in a merge request

To automatically merge a merge request once all tests pass

A project requires two approvals from the `QA` group. A merge request has received one approval from `user1` and one from `user2`. The developer then pushes a new commit that only changes a documentation file. The project manager wants the existing approvals to remain valid for this specific change. What is the most efficient way to achieve this?

Configure the approval rule to reset approvals only when files in the `src/` directory are changed.

Use the per-merge-request override to disable 'Reset approvals on push' for this specific merge request.

Ask the developer to revert the documentation change and push again.

Manually re-approve the merge request after the push.

What is the benefit of assigning an approval rule to a group instead of individual users?

The group automatically merges the merge request

The group must approve in a specific order

The group is notified but cannot approve

Any member of the group can approve the merge request

GitLabCertified Security Associate

Domain 4Objective 2

Configure Merge Request Approval Workflows GITLAB-CERTIFIED-SECURITY-SPECIALIST Practice Questions (Page 1)

Part of the Security Policies and Approvals domain, which makes up ~19% of our current practice bank.

16questions here

4free pages

6concepts

Questions 1–5

1foundation · easy
What happens to existing approvals when a new commit is pushed to a merge request with 'Require approval on code changes' enabled?
Select an answer first
2foundation · easy
In GitLab, which of the following can be assigned to an approval rule to control who can approve a merge request?
Select an answer first
3foundation · easy
What is the primary purpose of defining merge request approval rules in GitLab?
Select an answer first
4expert · medium
A project requires two approvals from the `QA` group. A merge request has received one approval from `user1` and one from `user2`. The developer then pushes a new commit that only changes a documentation file. The project manager wants the existing approvals to remain valid for this specific change. What is the most efficient way to achieve this?
Select an answer first
5foundation · easy
What is the benefit of assigning an approval rule to a group instead of individual users?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-SECURITY-SPECIALIST

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-SECURITY-SPECIALIST” is a trademark of its owner, used for identification only.

Configure Merge Request Approval Workflows GITLAB-CERTIFIED-SECURITY-SPECIALIST Practice Questions (Page 1)

Questions 1–5

What happens to existing approvals when a new commit is pushed to a merge request with 'Require approval on code changes' enabled?

In GitLab, which of the following can be assigned to an approval rule to control who can approve a merge request?

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

What is the benefit of assigning an approval rule to a group instead of individual users?

Keep studying — Security Policies and Approvals