A developer has pushed a feature branch 'feature/export-report' to the remote GitLab repository. The developer wants to propose merging this branch into the main branch and initiate a code review process. What should the developer do next?

Run 'git merge main' locally and then push the result

Delete the remote feature branch to keep the repository clean

Create a merge request from 'feature/export-report' into 'main'

Send an email to the team asking them to review the code directly

During a code review, a reviewer leaves a comment on a merge request suggesting a change. What should the developer do to address the feedback?

Merge the branch immediately without changes

Ignore the comment because the code is already merged

Delete the merge request and start over

Make the requested change, commit it to the feature branch, and push the update

A developer has pushed a new commit to a feature branch with an open merge request. The pipeline on the merge request shows a failed test. The developer needs to understand why the test failed before fixing it. What should the developer do?

Merge the merge request and check the pipeline on main

Open the pipeline details and examine the failed job's logs

Run 'git log' locally to see the commit history

Ask a teammate to run the tests on their machine

What is the primary purpose of creating a feature branch from the default branch in the GitLab workflow?

To store backup copies of the default branch

To permanently delete the default branch

To isolate new feature development from the stable codebase

To directly deploy changes to production

GitLabCertified CI/CD Associate

Domain 1Objective 3

Objective: Verify a New Feature GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 2)

Part of the Domain 1: GitLab Workflow domain, which makes up ~30% of our current practice bank.

25questions here

5free pages

8concepts

Questions 6–10

6application · easy
A developer has pushed a feature branch 'feature/export-report' to the remote GitLab repository. The developer wants to propose merging this branch into the main branch and initiate a code review process. What should the developer do next?
Select an answer first
7foundation · easy
After a feature branch has been successfully merged into the default branch, what is the recommended next step to keep the repository clean?
Select an answer first
8foundation · easy
During a code review, a reviewer leaves a comment on a merge request suggesting a change. What should the developer do to address the feedback?
Select an answer first
9application · easy
A developer has pushed a new commit to a feature branch with an open merge request. The pipeline on the merge request shows a failed test. The developer needs to understand why the test failed before fixing it. What should the developer do?
Select an answer first
10foundation · easy
What is the primary purpose of creating a feature branch from the default branch in the GitLab workflow?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

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