A developer has just pushed a new branch named 'feature-login' to GitLab and wants to propose merging it into the 'main' branch. Which action creates a merge request for this change?

Create a new issue and link it to the branch

Use 'git push origin feature-login:main' to automatically open a merge request

Run 'git merge-request' from the local repository

Click 'New merge request' in the GitLab UI and select 'feature-login' as source and 'main' as target

A merge request has a discussion thread that was resolved by the MR author. The reviewer who started the thread disagrees with the resolution and wants to reopen it. The project requires all discussions to be resolved before merging. What should the reviewer do?

Approve the merge request and let it merge.

Leave the discussion as resolved and add a new comment.

Request changes on the MR without interacting with the discussion.

Reopen the discussion by clicking 'Unresolve discussion' and add a comment explaining why.

GitLabCertified Fundamentals Associate

Domain 3Objective 1

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

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

18questions here

4free pages

6concepts

Questions 1–5

1foundation · easy
A developer has just pushed a new branch named 'feature-login' to GitLab and wants to propose merging it into the 'main' branch. Which action creates a merge request for this change?
Select an answer first
2expert · hard
A merge request has a discussion thread that was resolved by the MR author. The reviewer who started the thread disagrees with the resolution and wants to reopen it. The project requires all discussions to be resolved before merging. What should the reviewer do?
Select an answer first
3foundation · easy
A project requires two approvals from senior developers before any merge request can be merged. How is this enforced in GitLab?
Select an answer first
4foundation · easy
When creating a merge request in GitLab, which two branches must be specified?
Select an answer first
5foundation · easy
A reviewer wants to ask a follow-up question on an existing discussion thread in a merge request. What action should they take?
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 1)

Questions 1–5

A developer has just pushed a new branch named 'feature-login' to GitLab and wants to propose merging it into the 'main' branch. Which action creates a merge request for this change?

A merge request has a discussion thread that was resolved by the MR author. The reviewer who started the thread disagrees with the resolution and wants to reopen it. The project requires all discussions to be resolved before merging. What should the reviewer do?

A project requires two approvals from senior developers before any merge request can be merged. How is this enforced in GitLab?

When creating a merge request in GitLab, which two branches must be specified?

A reviewer wants to ask a follow-up question on an existing discussion thread in a merge request. What action should they take?

Keep studying — Merge Requests and Issues