CI/CD Integration - Quiz

Trigger a CI pipeline in GitLab by pushing a new commit to the main branch

Fetch the latest pipeline configuration and code from the default remote before a deployment

Stage changes to a GitHub Actions workflow file so they are included in the next commit

Create a new branch for experimenting with a different deployment strategy

Switch to the Jenkins integration branch before editing the Jenkinsfile

In a CI/CD pipeline, what is the primary purpose of the 'build' stage?

In GitHub Actions, what file location is used to define workflows?

What triggers a GitLab CI pipeline by default when using .gitlab-ci.yml?

In a CI pipeline focused on automated testing, which tests typically run first?

Which deployment strategy minimizes downtime by switching traffic between two identical environments?

Order the steps to add a GitHub Actions workflow that runs tests on each push.

Drag and drop to reorder, or use the arrows.

Order the steps to run a full CI pipeline in GitLab after updating tests.

Drag and drop to reorder, or use the arrows.

Order the steps to integrate a Jenkins pipeline with a Git repository.

Drag and drop to reorder, or use the arrows.

Order the steps for a canary deployment using a CI/CD pipeline.

Drag and drop to reorder, or use the arrows.

You are on branch feature/github-actions. What does this command print?

1git branch --show-current

The last commit you made was 'Add GitLab CI config'. What does this show?

1git log -1 --pretty=%s

Your HEAD is at tag v2.0.0 used for a production deployment. What does this print?

1git describe --tags --exact-match

You created a branch named jenkins-ci earlier and are currently on it. What is printed?

1git rev-parse --abbrev-ref HEAD

Find the incorrect command in this GitHub Actions workflow update sequence.

Click on the line(s) that contain the bug.

git checkout main

git pull origin main

git checkout -b ci-update

nano .github/workflows/ci.yml

git add .github/workflows/ci.yml

git commit "Update CI workflow"

git push origin ci-update

Find the incorrect command in this GitLab CI configuration commit workflow.

Click on the line(s) that contain the bug.

git checkout -b gitlab-ci-setup

nano .gitlab-ci.yml

git add .gitlab-ci.yml

git commit -m "Add GitLab CI"

git push origin .gitlab-ci.yml

Find the incorrect command in this Jenkinsfile change workflow.

Click on the line(s) that contain the bug.

git checkout main

git pull origin main

git checkout -b jenkins-pipeline

nano Jenkinsfile

git add Jenkinsfile

git commit -m "Update Jenkins pipeline"

git push jenkins-pipeline origin

Match each CI/CD concept with its primary purpose.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match each CI platform with its configuration file location.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match each automated test type with what it primarily validates.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Complete the commands to prepare and share a blue-green deployment branch.

Complete the commands to rebase a feature branch with updated CI tests.

Complete the commands to commit and push an updated Jenkinsfile.

Click the line that shows the current branch used for the main CI pipeline.

Click on the line to select.

  canary-release

* main

  blue-green

  jenkins-experiments

Click the line that indicates a modified GitHub Actions workflow file.

Click on the line to select.

 M .github/workflows/ci.yml

 M src/app.js

?? scripts/deploy.sh

Click the line showing the commit that added automated tests.

Click on the line to select.

commit a1b2c3d4

Author: Dev <dev@example.com>

Date:   ...

    Initial project setup

commit e5f6a7b8

Author: Dev <dev@example.com>

Date:   ...

    Add automated tests