Beginner Level (1–20)
1. What does CI stand for?
A. Continuous Improvement
B. Continuous Integration
C. Continuous Inspection
D. Continuous Infrastructure
Answer: B
2. What is the main goal of Continuous Integration?
A. Deploy code to production automatically
B. Integrate code changes frequently
C. Replace testing
D. Eliminate version control
Answer: B
3. Which tool is commonly used for version control in CI/CD?
A. Docker
B. Git
C. Jenkins
D. Kubernetes
Answer: B
4. What usually triggers a CI pipeline?
A. Server reboot
B. Code commit or pull request
C. Manual deployment
D. System crash
Answer: B
5. What is a pipeline?
A. A network cable
B. A sequence of automated steps
C. A database
D. A container
Answer: B
6. Which file often defines a CI pipeline?
A. README.md
B. Dockerfile
C. YAML file
D. package.json
Answer: C
7. What is Continuous Delivery?
A. Code is always deployed to production
B. Code is always production-ready
C. Manual testing only
D. No automation
Answer: B
8. Continuous Deployment means:
A. Manual approval before deploy
B. Automatic deployment to production
C. No testing
D. Weekly releases
Answer: B
9. Which is a popular CI/CD tool?
A. Jenkins
B. Photoshop
C. Excel
D. Slack
Answer: A
10. What is the first step in most CI pipelines?
A. Deployment
B. Build
C. Monitoring
D. Rollback
Answer: B
11. What does “build” usually mean?
A. Writing code
B. Compiling and packaging code
C. Deploying code
D. Monitoring systems
Answer: B
12. Why are automated tests important in CI/CD?
A. They slow down releases
B. They replace developers
C. They catch bugs early
D. They remove documentation
Answer: C
13. Which environment usually comes after development?
A. Production
B. Testing/Staging
C. Disaster recovery
D. Monitoring
Answer: B
14. What is a commit?
A. A deployment
B. A saved change in version control
C. A test failure
D. A rollback
Answer: B
15. What is a pull request (PR)?
A. A server request
B. A code review request
C. A deployment trigger
D. A rollback command
Answer: B
16. Which language is commonly used for CI/CD configs?
A. Java
B. YAML
C. C++
D. HTML
Answer: B
17. What does automation reduce the most?
A. Code quality
B. Human error
C. Costs always
D. Security risks entirely
Answer: B
18. CI/CD mainly supports which practice?
A. Waterfall
B. Agile/DevOps
C. Big Bang releases
D. Manual QA
Answer: B
19. What is a failed pipeline usually a sign of?
A. Success
B. Bug or configuration issue
C. Security breach
D. Hardware failure only
Answer: B
20. CI/CD encourages:
A. Rare releases
B. Frequent small changes
C. No testing
D. Manual deployments
Answer: B
Intermediate Level (21–35)
21. What is a CI runner/agent?
A. A developer
B. A server that executes pipeline jobs
C. A container registry
D. A monitoring tool
Answer: B
22. What is a common CI/CD stage order?
A. Deploy → Test → Build
B. Build → Test → Deploy
C. Test → Build → Monitor
D. Monitor → Deploy → Build
Answer: B
23. What is a Docker image?
A. A VM
B. A running container
C. A packaged application template
D. A pipeline
Answer: C
24. Why use caching in pipelines?
A. Improve security
B. Speed up builds
C. Increase failures
D. Reduce tests
Answer: B
25. What is a staging environment?
A. Developer laptop
B. Production clone for testing
C. Monitoring system
D. Backup server
Answer: B
26. Which practice helps avoid broken main branches?
A. Long-lived feature branches
B. Trunk-based development
C. No testing
D. Manual merges
Answer: B
27. What is artifact storage used for?
A. Logging
B. Storing build outputs
C. Running tests
D. Monitoring metrics
Answer: B
28. What is Infrastructure as Code (IaC)?
A. Manual server setup
B. Infrastructure defined using code
C. Only cloud resources
D. CI documentation
Answer: B
29. Which tool is commonly used for IaC?
A. Terraform
B. Jenkins
C. Git
D. Postman
Answer: A
30. What does “shift left testing” mean?
A. Testing later
B. Testing earlier in the pipeline
C. Removing tests
D. Manual testing only
Answer: B
31. What is a rollback?
A. Forward deployment
B. Reverting to a previous version
C. Restarting a pipeline
D. Scaling infrastructure
Answer: B
32. What is a canary deployment?
A. Deploying everywhere at once
B. Deploying to a small user subset
C. Manual deployment
D. Blue-green switch
Answer: B
33. Why use environment variables in CI/CD?
A. Store secrets and configs
B. Store source code
C. Replace Git
D. Run tests faster
Answer: A
34. What is a pipeline job?
A. Entire workflow
B. Single executable task
C. Deployment only
D. Monitoring tool
Answer: B
35. What usually stops a pipeline?
A. Successful tests
B. Failed stage
C. Fast builds
D. Good documentation
Answer: B
DevOps Wizard Level (36–50)
36. What is blue-green deployment?
A. Two testing environments
B. Switching traffic between two production environments
C. Canary release
D. Manual deployment
Answer: B
37. What is pipeline orchestration?
A. Writing scripts
B. Coordinating multiple pipeline stages/jobs
C. Monitoring servers
D. Code review
Answer: B
38. What is a monorepo challenge in CI/CD?
A. Too many repos
B. Slow pipelines due to shared code
C. No version control
D. No tests
Answer: B
39. What does “immutable infrastructure” mean?
A. Servers are patched manually
B. Servers are replaced, not modified
C. No automation
D. Shared state
Answer: B
40. What is pipeline parallelization used for?
A. Reduce reliability
B. Speed up execution
C. Increase cost
D. Reduce testing
Answer: B
41. What is secret rotation?
A. Renaming variables
B. Regularly changing credentials
C. Encrypting secrets once
D. Storing secrets in Git
Answer: B
42. Which metric best reflects CI pipeline health?
A. Number of commits
B. Build success rate
C. Developer count
D. Server uptime only
Answer: B
43. What is GitOps?
A. Manual deployments
B. Using Git as the source of truth for deployments
C. No CI
D. Monitoring only
Answer: B
44. What causes flaky tests?
A. Stable environments
B. Timing and environment dependencies
C. Good test design
D. Parallel execution always
Answer: B
45. What is a supply chain attack in CI/CD?
A. Network outage
B. Compromised dependencies or tools
C. Server crash
D. Slow builds
Answer: B
46. Why restrict pipeline permissions?
A. Reduce speed
B. Improve security
C. Increase failures
D. Reduce automation
Answer: B
47. What is a self-hosted runner risk?
A. Faster builds
B. Greater attack surface
C. Easier setup
D. Automatic scaling
Answer: B
48. What is deployment frequency a sign of?
A. Poor quality
B. DevOps maturity
C. Security risk
D. Manual processes
Answer: B
49. What is observability used for in CI/CD?
A. Writing pipelines
B. Understanding system behavior
C. Code formatting
D. Testing only
Answer: B
50. Ultimate CI/CD goal is:
A. Zero developers
B. Fast, reliable, secure delivery
C. No testing
D. Manual control
Answer: B
Conclusion.
Whether you landed in Beginner, Intermediate, or full-on DevOps Wizard, this CI/CD quiz is really about awareness, not labels. CI/CD is a journey everyone starts somewhere, and every level has room to grow. Beginners are building the foundation, Intermediates are sharpening and scaling their pipelines, and DevOps Wizards are automating with confidence and intent. Wherever you are, the win is the same: keep experimenting, keep breaking (safely ), and keep improving your pipelines. The best CI/CD setups aren’t static they evolve with you.
- For more information about DevOps, visit Jeevi’s page to explore detailed guides and resources.
