A pipeline has `build`, `test`, and `deploy` stages. The `deploy` job is manual and must run after `test`. The team also has a `security_scan` job in the `test` stage that is allowed to fail. They want `deploy` to be available only after `test` succeeds, regardless of the `security_scan` result. Which configuration achieves this?

Add `when: on_success` to the deploy job and `allow_failure: true` on the `security_scan` job.

Add `needs: [test]` to the deploy job and set `allow_failure: true` on the `security_scan` job.

Add `needs: [test, security_scan]` to the deploy job.

Add `needs: [security_scan]` to the deploy job.

What is the purpose of using `when: manual` on a deploy job in a production pipeline?

To require a human to explicitly start the deployment, providing a control point before production release

To ensure the deploy job runs automatically after tests pass

To run the deploy job in a separate pipeline

To skip the deploy job if tests fail

A team deploys a review app for every MR. When the MR is merged, they want the review environment to be automatically torn down. Which configuration achieves this without manual intervention?

Set `auto_stop_in: 1 day` on the review job and rely on the timer to stop the environment.

Use a Kubernetes CronJob to delete the review namespace every hour.

Define a stop job with `environment:action: stop` and reference it from the review job using `on_stop`.

Define a cleanup job that runs on the default branch and deletes the review environment by name.

A team has a production deploy job that is `when: manual`. They want to require two different people to approve the deployment before it runs. Which GitLab feature supports this requirement?

Use a single manual job and rely on the project's approval settings to require two approvals.

Use a single manual job with `when: manual` and set the job's `timeout` to require a second click.

Use a single manual job and add a `needs` dependency on a test job that is also manual.

Use two sequential manual jobs, each requiring a different user to click play, with the second job depending on the first.

GitLabCertified CI/CD Associate

Domain 4Objective 1

Objective: Scaffold Review and Deploy Stages of a Pipeline GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 2)

Part of the Domain 4: Continuous Deployment domain, which makes up ~16% of our current practice bank.

14questions here

3free pages

6concepts

Questions 6–10

6expert · medium
A pipeline has `build`, `test`, and `deploy` stages. The `deploy` job is manual and must run after `test`. The team also has a `security_scan` job in the `test` stage that is allowed to fail. They want `deploy` to be available only after `test` succeeds, regardless of the `security_scan` result. Which configuration achieves this?
Select an answer first
7foundation · easy
What is the purpose of using `when: manual` on a deploy job in a production pipeline?
Select an answer first
8application · medium
A team deploys a review app for every MR. When the MR is merged, they want the review environment to be automatically torn down. Which configuration achieves this without manual intervention?
Select an answer first
9expert · medium
A team has a production deploy job that is `when: manual`. They want to require two different people to approve the deployment before it runs. Which GitLab feature supports this requirement?
Select an answer first
10foundation · easy
In a GitLab CI/CD pipeline, what is the default order of stages if you define them as `stages: [build, test, review, deploy]`?
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.