Last Updated On
Welcome to the CI/CD Quiz!
This article delves into the essential concepts and features of CI/CD.
1. What does CI stand for?
a) Continuous Integration
b) Code Inspection
c) Continuous Improvement
d) Configuration Integration
Answer 1
a) Continuous Integration
CI stands for Continuous Integration in CI/CD
2. What does CD stand for in CI/CD?
a) Continuous Delivery
b) Continuous Deployment
c) Both A and B
d) Continuous Development
Answer 2
c) Both A and B
3. What is the difference between Continuous Delivery and Continuous Deployment?
a) Continuous Delivery involves testing only while Continuous Deployment skips testing
b) Continuous Deployment goes one step further by automating releases to production
c) Continuous Delivery is faster
d) There is no difference
Answer 3
b) Continuous Deployment goes one step further by automating releases to production
4. What is Continuous Integration (CI)?
a) Merging code changes less frequently
b) Automatically building and testing code with every change
c) Only integrating code after deployment
d) Debugging code after production release
Answer 4
b) Automatically building and testing code with every change
Continuous Integration involves frequently integrating code changes into a shared repository and automating builds and tests to detect issues early.
5. What is the main goal of Continuous Deployment (CD)?
a) Automatically deploying tested code to production
b) Writing deployment scripts manually
c) Delaying code releases until complete testing
d) Revisiting code changes after deployment
Answer 5
a) Automatically deploying tested code to production
Continuous Deployment refers to automating the release pipeline to deploy code changes directly to production once testing is successful.
6. What tool is commonly used for CI/CD pipelines?
a) Jenkins
b) Microsoft Excel
c) IntelliJ IDEA
d) Photoshop
Answer 6
a) Jenkins
Jenkins is a widely-used tool for automating CI/CD processes with flexible pipelines.
7. What is a pipeline in CI/CD?
a) A network connection between servers
b) A series of automated tasks for building, testing, and deploying code
c) A manual checklist for deployment
d) A file containing configuration settings
Answer 7
b) A series of automated tasks for building, testing, and deploying code.
A CI/CD pipeline automates the entire lifecycle, from code integration to deployment.
8. What is version control in the context of CI/CD?
a) Tracking deployment errors
b) Managing changes to source code over time
c) Debugging production code
d) Scaling pipeline performance
Answer 8
b) Managing changes to source code over time
Version control systems like Git help developers track changes, collaborate effectively, and integrate code frequently.
9. Why are automated tests crucial in CI/CD pipelines?
a) They save time by eliminating manual testing
b) They can identify code quality issues immediately
c) They ensure that changes do not break existing functionality
d) All of the above
Answer 9
d) All of the above
10. What is the main purpose of unit tests in CI/CD?
a) Test user interfaces
b) Validate individual components of the code
c) Test system performance under stress
d) Ensure browser compatibility
Answer 10
b) Validate individual components of the code
11. What is version control in CI/CD?
a) Tracking deployment failures
b) A system to manage changes to source code over time
c) A method of scaling applications
d) Reviewing team member’s work manually
Answer 11
b) A system to manage changes to source code over time
12. What is Git often used for in CI/CD?
a) Writing scripts
b) Containerization
c) Version control and collaboration
d) Performance testing
Answer 12
c) Version control and collaboration
13. What is “artifact management” in CI/CD?
Choose one option
a) Debugging failed builds
b) Storing deployable binaries or files for later use
c) Reducing deployment risk
d) Automating version control
Answer 13
b) Storing deployable binaries or files for later use
Artifact management ensures that outputs (e.g., built binaries) are preserved and available for consistency and traceability.
14. Which of the following is a cloud-based CI/CD tool?
Choose one option
a) GitHub Actions
b) IntelliJ IDEA
c) Blender
d) Visual Studio Code
Answer 14
a) GitHub Actions
GitHub Actions provides built-in support for CI/CD hosted on GitHub’s cloud infrastructure.
15. Which practice helps detect integration problems earlier?
Choose one option
a) Integrate once per quarter
b) Merge frequently and run automated tests on each merge
c) Keep features in private forks forever
d) Only run tests before major releases
Answer 15
b) Merge frequently and run automated tests on each merge
Frequent merges with automated tests reduce integration risk and surface conflicts sooner.
16. What is an artifact in CI/CD?
Choose one option
a) A bug report
b) A build output (e.g., binary, jar, container image) produced by the pipeline
c) A test failure
d) A commit message
Answer 16
b) A build output (e.g., binary, jar, container image) produced by the pipeline
Artifacts are versioned build outputs stored for deployment or distribution.
17. Why use an artifact repository (e.g., Nexus, Artifactory)?
a) To store test scripts only
b) To store and manage built artifacts reliably, with versioning and access control
c) To replace version control
d) To host CI servers
Answer 17
b) To store and manage built artifacts reliably, with versioning and access control
Artifact repos centralize build outputs and support dependency management and reproducibility.
18. Which of these is a common trigger for CI pipelines?
a) A code commit or push to the repository
b) A power outage
c) Opening the IDE
d) Editing local files only
Answer 18
a) A code commit or push to the repository
Commits/pushes and pull requests commonly trigger CI pipelines via webhooks.
19. What is a build failure in CI usually an indicator of?
a) A harmless warning
b) A compile error, failing tests, or misconfigured pipeline that needs attention
c) Successful release
d) Improved performance
Answer 19
b) A compile error, failing tests, or misconfigured pipeline that needs attention
Build failures indicate problems that prevent successful integration and must be fixed.
20. Which of the following is a good first step when adopting CI/CD for a project?
Choose one option
a) Rewrite the entire codebase
b) Start by automating the build and unit tests and run them on commits
c) Disable version control
d) Deploy without tests immediately
Answer 20
b) Start by automating the build and unit tests and run them on commits
Automating builds and tests provides immediate value and is a foundational step for CI/CD adoption.
We would love to hear from you! Please leave your comments and share your scores in the section below
QA Automation Expert 