CI/CD Pipeline Stages — Vocabulary and Language
Learn the vocabulary of CI/CD pipeline stages: lint, test, build, scan, deploy, and verify.
0 / 25 completed
1 / 25
What is the 'build' stage in a CI/CD pipeline?
The build stage compiles source code into a deployable artefact: a compiled binary (Go, Java), a container image (Docker), a JS bundle (webpack/esbuild), or a package (npm, pip). Build artefacts are then promoted through environments.
2 / 25
What is the 'lint' stage in a CI/CD pipeline?
Linting runs tools (ESLint, flake8, golangci-lint, rubocop) that check code style, formatting, and common mistakes statically — without running the code. Fast feedback before the more expensive test and build stages.
3 / 25
What is 'SAST' in a CI/CD security scan stage?
SAST (Static Application Security Testing) scans source code for security issues (SQL injection patterns, hardcoded secrets, insecure API usage) without executing the code. Tools: Semgrep, SonarQube, CodeQL, Bandit.
4 / 25
What is the 'verify' or 'smoke test' stage after deployment?
Post-deployment verification confirms the deployment succeeded: health endpoint checks, smoke tests of critical user journeys, and synthetic monitoring — triggering automatic rollback if checks fail.
5 / 25
What is 'pipeline as code' in CI/CD vocabulary?
Pipeline as code defines CI/CD pipelines in version-controlled files (GitHub Actions YAML, Jenkinsfile, .gitlab-ci.yml, Buildkite YAML). Changes are reviewed, tested, and audited like any other code change.
6 / 25
Sarah from QA just posted this comment on the pull request for the new user authentication service:
"@John, I've run a basic smoke test and it's failing. It takes about 30 seconds to register a new user, which is significantly longer than the 5-second SLA we agreed on. Can you investigate?"This scenario highlights the role of the 'verification' or 'smoke test' stage. The question isn't about a general CI/CD concept; it's about Sarah identifying a problem *after* deployment. The correct answer reflects that the smoke test is failing to meet expectations – specifically, the registration time exceeds the agreed-upon Service Level Agreement (SLA). Options A and D are misdirected, focusing on broader pipeline stages or infrastructure issues instead of the specific failure reported.
7 / 25
David in the standup update said: 'The deployment to staging just finished. We ran our automated tests and everything *passed*, but I'm still seeing a yellow status on the Jenkins dashboard – it says 'Integration Test Failure'. It's been running for 15 minutes now, and nothing has changed.'
Which of the following best describes what David is likely encountering during the CI/CD pipeline?David is describing a common situation where an integration test fails after a deployment. The 'Integration Test' stage specifically focuses on verifying that the deployed application works correctly with its supporting infrastructure – databases, message queues, external APIs, etc. A yellow status in Jenkins often indicates a problem *within* this stage, suggesting the application isn't connecting or interacting as expected during testing. Options A and C are too broad; option D is incorrect because Jenkins should automatically trigger pipeline stages based on defined events.8 / 25
David in the standup update is likely experiencing a problem within the integration testing stage of his CI/CD pipeline. The Jenkins dashboard's 'Integration Test Failure' status suggests that tests designed to verify interactions between different components of the system – perhaps database connections or external API calls – are failing, but not triggering an immediate build failure or notification. This often happens when a test is flaky, or requires specific conditions that aren't consistently met during the run.
Consider which stage David's situation points to.
David's issue directly relates to 'integration testing,' which specifically focuses on verifying how different parts of a system work together. The Jenkins dashboard status indicates a failure within this stage – not deployment, code review, or security scanning. Flaky tests are a common cause of integration test failures in CI/CD pipelines.
9 / 25
John sent this Slack message after a failed deployment:
"Hey team, we just deployed the new payment gateway. The initial tests are green, but I'm seeing intermittent errors in our monitoring dashboard – specifically, transaction IDs are sometimes missing. It's happening about 10% of the time."David is encountering an issue related to the verification or monitoring stage after deployment. The Slack message indicates intermittent errors detected *after* the initial green tests, suggesting that the automated verification process isn't robust enough to catch these sporadic problems – a common cause of 'yellow' statuses on dashboards. This highlights the importance of defining appropriate error rates and thresholds within your pipeline's verification stages rather than solely relying on passing basic smoke tests.
10 / 25
Mark from Development just posted this comment on a pull request for the new recommendation engine API:
'I've pushed the changes through to the staging environment. The initial build completed successfully and deployed to staging, but I'm seeing a 'Deployment Failed' status in our pipeline dashboard. It mentions 'Resource Exhaustion – High CPU Usage'. This is unusual; we haven't had issues with CPU before.'
Which stage of the CI/CD pipeline is Mark most likely encountering problems within?
Mark's message points to issues during the *deployment* stage. 'Resource Exhaustion – High CPU Usage' indicates that the pipeline isn't correctly provisioning or scaling resources for the application to run properly in staging. This could be due to misconfigured infrastructure, insufficient server capacity, or a deployment process that doesn't account for resource needs. The build and testing stages wouldn't typically directly report high CPU usage; they would flag code issues or failing tests respectively.
11 / 25
Sarah from QA just posted this comment on the pull request for the new user authentication service:
"@John, I've run a basic smoke test and it's failing. It takes about 30 seconds to register a new user, which is significantly longer than the 5-second SLA we agreed on. Can you investigate?"This scenario highlights the role of the 'verification' or 'smoke test' stage. The question isn't about a general CI/CD concept; it's about Sarah identifying a problem *after* deployment. The correct answer reflects that the smoke test is failing to meet expectations – specifically, the registration time exceeds the agreed-upon Service Level Agreement (SLA). Options A and D are misdirected, focusing on broader pipeline stages or infrastructure issues instead of the specific failure reported.
12 / 25
David in the standup update said: 'The deployment to staging just finished. We ran our automated tests and everything *passed*, but I'm still seeing a yellow status on the Jenkins dashboard – it says 'Integration Test Failure'. It's been running for 15 minutes now, and nothing has changed.'
Which of the following best describes what David is likely encountering during the CI/CD pipeline?David is describing a common situation where an integration test fails after a deployment. The 'Integration Test' stage specifically focuses on verifying that the deployed application works correctly with its supporting infrastructure – databases, message queues, external APIs, etc. A yellow status in Jenkins often indicates a problem *within* this stage, suggesting the application isn't connecting or interacting as expected during testing. Options A and C are too broad; option D is incorrect because Jenkins should automatically trigger pipeline stages based on defined events.13 / 25
David in the standup update is likely experiencing a problem within the integration testing stage of his CI/CD pipeline. The Jenkins dashboard's 'Integration Test Failure' status suggests that tests designed to verify interactions between different components of the system – perhaps database connections or external API calls – are failing, but not triggering an immediate build failure or notification. This often happens when a test is flaky, or requires specific conditions that aren't consistently met during the run.
Consider which stage David's situation points to.
David's issue directly relates to 'integration testing,' which specifically focuses on verifying how different parts of a system work together. The Jenkins dashboard status indicates a failure within this stage – not deployment, code review, or security scanning. Flaky tests are a common cause of integration test failures in CI/CD pipelines.
14 / 25
John sent this Slack message after a failed deployment:
"Hey team, we just deployed the new payment gateway. The initial tests are green, but I'm seeing intermittent errors in our monitoring dashboard – specifically, transaction IDs are sometimes missing. It's happening about 10% of the time."David is encountering an issue related to the verification or monitoring stage after deployment. The Slack message indicates intermittent errors detected *after* the initial green tests, suggesting that the automated verification process isn't robust enough to catch these sporadic problems – a common cause of 'yellow' statuses on dashboards. This highlights the importance of defining appropriate error rates and thresholds within your pipeline's verification stages rather than solely relying on passing basic smoke tests.
15 / 25
Mark from Development just posted this comment on a pull request for the new recommendation engine API:
'I've pushed the changes through to the staging environment. The initial build completed successfully and deployed to staging, but I'm seeing a 'Deployment Failed' status in our pipeline dashboard. It mentions 'Resource Exhaustion – High CPU Usage'. This is unusual; we haven't had issues with CPU before.'
Which stage of the CI/CD pipeline is Mark most likely encountering problems within?
Mark's message points to issues during the *deployment* stage. 'Resource Exhaustion – High CPU Usage' indicates that the pipeline isn't correctly provisioning or scaling resources for the application to run properly in staging. This could be due to misconfigured infrastructure, insufficient server capacity, or a deployment process that doesn't account for resource needs. The build and testing stages wouldn't typically directly report high CPU usage; they would flag code issues or failing tests respectively.
16 / 25
Sarah from QA just posted this comment on the pull request for the new user authentication service:
"@John, I've run a basic smoke test and it's failing. It takes about 30 seconds to register a new user, which is significantly longer than the 5-second SLA we agreed on. Can you investigate?"This scenario highlights the role of the 'verification' or 'smoke test' stage. The question isn't about a general CI/CD concept; it's about Sarah identifying a problem *after* deployment. The correct answer reflects that the smoke test is failing to meet expectations – specifically, the registration time exceeds the agreed-upon Service Level Agreement (SLA). Options A and D are misdirected, focusing on broader pipeline stages or infrastructure issues instead of the specific failure reported.
17 / 25
David in the standup update said: 'The deployment to staging just finished. We ran our automated tests and everything *passed*, but I'm still seeing a yellow status on the Jenkins dashboard – it says 'Integration Test Failure'. It's been running for 15 minutes now, and nothing has changed.'
Which of the following best describes what David is likely encountering during the CI/CD pipeline?David is describing a common situation where an integration test fails after a deployment. The 'Integration Test' stage specifically focuses on verifying that the deployed application works correctly with its supporting infrastructure – databases, message queues, external APIs, etc. A yellow status in Jenkins often indicates a problem *within* this stage, suggesting the application isn't connecting or interacting as expected during testing. Options A and C are too broad; option D is incorrect because Jenkins should automatically trigger pipeline stages based on defined events.18 / 25
David in the standup update is likely experiencing a problem within the integration testing stage of his CI/CD pipeline. The Jenkins dashboard's 'Integration Test Failure' status suggests that tests designed to verify interactions between different components of the system – perhaps database connections or external API calls – are failing, but not triggering an immediate build failure or notification. This often happens when a test is flaky, or requires specific conditions that aren't consistently met during the run.
Consider which stage David's situation points to.
David's issue directly relates to 'integration testing,' which specifically focuses on verifying how different parts of a system work together. The Jenkins dashboard status indicates a failure within this stage – not deployment, code review, or security scanning. Flaky tests are a common cause of integration test failures in CI/CD pipelines.
19 / 25
John sent this Slack message after a failed deployment:
"Hey team, we just deployed the new payment gateway. The initial tests are green, but I'm seeing intermittent errors in our monitoring dashboard – specifically, transaction IDs are sometimes missing. It's happening about 10% of the time."David is encountering an issue related to the verification or monitoring stage after deployment. The Slack message indicates intermittent errors detected *after* the initial green tests, suggesting that the automated verification process isn't robust enough to catch these sporadic problems – a common cause of 'yellow' statuses on dashboards. This highlights the importance of defining appropriate error rates and thresholds within your pipeline's verification stages rather than solely relying on passing basic smoke tests.
20 / 25
Mark from Development just posted this comment on a pull request for the new recommendation engine API:
'I've pushed the changes through to the staging environment. The initial build completed successfully and deployed to staging, but I'm seeing a 'Deployment Failed' status in our pipeline dashboard. It mentions 'Resource Exhaustion – High CPU Usage'. This is unusual; we haven't had issues with CPU before.'
Which stage of the CI/CD pipeline is Mark most likely encountering problems within?
Mark's message points to issues during the *deployment* stage. 'Resource Exhaustion – High CPU Usage' indicates that the pipeline isn't correctly provisioning or scaling resources for the application to run properly in staging. This could be due to misconfigured infrastructure, insufficient server capacity, or a deployment process that doesn't account for resource needs. The build and testing stages wouldn't typically directly report high CPU usage; they would flag code issues or failing tests respectively.
21 / 25
Sarah from QA just posted this comment on the pull request for the new user authentication service:
"@John, I've run a basic smoke test and it's failing. It takes about 30 seconds to register a new user, which is significantly longer than the 5-second SLA we agreed on. Can you investigate?"This scenario highlights the role of the 'verification' or 'smoke test' stage. The question isn't about a general CI/CD concept; it's about Sarah identifying a problem *after* deployment. The correct answer reflects that the smoke test is failing to meet expectations – specifically, the registration time exceeds the agreed-upon Service Level Agreement (SLA). Options A and D are misdirected, focusing on broader pipeline stages or infrastructure issues instead of the specific failure reported.
22 / 25
David in the standup update said: 'The deployment to staging just finished. We ran our automated tests and everything *passed*, but I'm still seeing a yellow status on the Jenkins dashboard – it says 'Integration Test Failure'. It's been running for 15 minutes now, and nothing has changed.'
Which of the following best describes what David is likely encountering during the CI/CD pipeline?David is describing a common situation where an integration test fails after a deployment. The 'Integration Test' stage specifically focuses on verifying that the deployed application works correctly with its supporting infrastructure – databases, message queues, external APIs, etc. A yellow status in Jenkins often indicates a problem *within* this stage, suggesting the application isn't connecting or interacting as expected during testing. Options A and C are too broad; option D is incorrect because Jenkins should automatically trigger pipeline stages based on defined events.23 / 25
David in the standup update is likely experiencing a problem within the integration testing stage of his CI/CD pipeline. The Jenkins dashboard's 'Integration Test Failure' status suggests that tests designed to verify interactions between different components of the system – perhaps database connections or external API calls – are failing, but not triggering an immediate build failure or notification. This often happens when a test is flaky, or requires specific conditions that aren't consistently met during the run.
Consider which stage David's situation points to.
David's issue directly relates to 'integration testing,' which specifically focuses on verifying how different parts of a system work together. The Jenkins dashboard status indicates a failure within this stage – not deployment, code review, or security scanning. Flaky tests are a common cause of integration test failures in CI/CD pipelines.
24 / 25
John sent this Slack message after a failed deployment:
"Hey team, we just deployed the new payment gateway. The initial tests are green, but I'm seeing intermittent errors in our monitoring dashboard – specifically, transaction IDs are sometimes missing. It's happening about 10% of the time."David is encountering an issue related to the verification or monitoring stage after deployment. The Slack message indicates intermittent errors detected *after* the initial green tests, suggesting that the automated verification process isn't robust enough to catch these sporadic problems – a common cause of 'yellow' statuses on dashboards. This highlights the importance of defining appropriate error rates and thresholds within your pipeline's verification stages rather than solely relying on passing basic smoke tests.
25 / 25
Mark from Development just posted this comment on a pull request for the new recommendation engine API:
'I've pushed the changes through to the staging environment. The initial build completed successfully and deployed to staging, but I'm seeing a 'Deployment Failed' status in our pipeline dashboard. It mentions 'Resource Exhaustion – High CPU Usage'. This is unusual; we haven't had issues with CPU before.'
Which stage of the CI/CD pipeline is Mark most likely encountering problems within?
Mark's message points to issues during the *deployment* stage. 'Resource Exhaustion – High CPU Usage' indicates that the pipeline isn't correctly provisioning or scaling resources for the application to run properly in staging. This could be due to misconfigured infrastructure, insufficient server capacity, or a deployment process that doesn't account for resource needs. The build and testing stages wouldn't typically directly report high CPU usage; they would flag code issues or failing tests respectively.
Frequently Asked Questions
What will I practice in "CI/CD Pipeline Stages — Vocabulary and Language"?
This is a CI/CD Pipeline Language exercise set. It walks through 25 scenario-based multiple-choice questions built around real usage of CI/CD Pipeline Language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 25 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the CI/CD Pipeline Language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more CI/CD Pipeline Language exercises?
See the CI/CD Pipeline Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — CI/CD Pipeline Language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.