What does the 'Require approval on code changes' setting do in GitLab merge request approvals?

It resets existing approvals when new commits are pushed to the merge request

It requires that all code changes be reviewed by at least two different groups

It automatically approves the merge request when code changes are pushed

It prevents any code changes from being made after an approval is given

Where can a user view the current approval status of a merge request in GitLab?

In the project's CI/CD pipeline settings

In the user's personal profile settings

In the repository's file browser

On the merge request page itself

In GitLab, what does an approval rule define for a merge request?

The maximum file size allowed in the repository

The list of CI/CD jobs that must run before merging

The number of approvals required and who can provide them

The order in which commits must be pushed to the branch

When might a user need to override an approval rule for a specific merge request in GitLab?

When the merge request is created by a group member

When the normal approval requirements are not appropriate for that particular merge request

When the merge request has no code changes

A project has a rule requiring approval from the `Security` group for all merge requests. An emergency fix is needed, and the only `Security` group member available is on vacation. The project manager wants to allow a temporary exception for this one merge request, but does not want to change the project-wide rule or grant long-term access. What is the best approach?

Change the project-wide rule to require approval from a different group, then change it back after the merge.

Use the per-merge-request override to change the required approvers to a different group for this MR.

Ask a project owner to merge the MR without approval.

Add a temporary user to the `Security` group, have them approve, then remove them.

GitLabCertified Security Associate

Domain 4Objective 2

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

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

16questions here

4free pages

6concepts

Questions 6–10

6foundation · easy
What does the 'Require approval on code changes' setting do in GitLab merge request approvals?
Select an answer first
7foundation · easy
Where can a user view the current approval status of a merge request in GitLab?
Select an answer first
8foundation · easy
In GitLab, what does an approval rule define for a merge request?
Select an answer first
9foundation · easy
When might a user need to override an approval rule for a specific merge request in GitLab?
Select an answer first
10expert · medium
A project has a rule requiring approval from the `Security` group for all merge requests. An emergency fix is needed, and the only `Security` group member available is on vacation. The project manager wants to allow a temporary exception for this one merge request, but does not want to change the project-wide rule or grant long-term access. What is the best approach?
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.