1. What does CI stand for?
A. Continuous Integration
B. Continuous Improvement
C. Code Integration
D. Continuous Inspection
Answer: A
2. What does CD usually stand for in DevOps?
A. Code Delivery
B. Continuous Deployment
C. Continuous Delivery
D. Both B and C
Answer: D
3. Jenkins is best described as:
A. A version control system
B. A CI/CD automation server
C. A container runtime
D. A cloud provider
Answer: B
4. Which Jenkins feature enables CI?
A. Manual build triggers
B. Automated builds on code changes
C. Blue Ocean UI
D. Jenkins themes
Answer: B
5. What typically triggers a CI pipeline in Jenkins?
A. Server reboot
B. Code commit or pull request
C. User login
D. Plugin update
Answer: B
6. CI focuses primarily on:
A. Deploying to production
B. Integrating code frequently
C. Scaling infrastructure
D. Monitoring servers
Answer: B
7. Which stage is mandatory for CI?
A. Deployment
B. Unit testing
C. Manual approval
D. Monitoring
Answer: B
8. CD focuses on:
A. Writing code
B. Building binaries
C. Releasing software automatically or semi-automatically
D. Code reviews
Answer: C
9. Jenkins supports CD by:
A. Writing application code
B. Automating deployment pipelines
C. Hosting applications
D. Managing databases
Answer: B
10. What is a Jenkins pipeline?
A. A Jenkins plugin
B. A sequence of automated steps
C. A Docker image
D. A Git branch
Answer: B
11. Which file defines a Jenkins pipeline?
A. docker-compose.yml
B. Jenkins.yaml
C. Jenkinsfile
D. pipeline.xml
Answer: C
12. CI pipelines usually stop if:
A. Deployment fails
B. Unit tests fail
C. Server restarts
D. Monitoring alerts trigger
Answer: B
13. Which stage is more CD-focused?
A. Compile
B. Unit test
C. Deploy to production
D. Code linting
Answer: C
14. Jenkins itself:
A. Decides business logic
B. Automates workflows
C. Writes tests
D. Fixes bugs
Answer: B
15. Continuous Delivery means:
A. Every change is deployed automatically
B. Every change is deployable
C. No testing is required
D. Manual builds only
Answer: B
16. Continuous Deployment means:
A. Manual approval before prod
B. Code is always deployed automatically
C. Only weekly releases
D. No CI
Answer: B
17. Jenkins supports both CI and CD by:
A. Being a source control system
B. Orchestrating tools and scripts
C. Hosting cloud resources
D. Running production traffic
Answer: B
18. What Jenkins feature helps with CD approvals?
A. Webhooks
B. Credentials
C. Input step
D. SCM polling
Answer: C
19. Which tool is commonly integrated with Jenkins for CI?
A. Git
B. Kubernetes
C. Prometheus
D. Terraform
Answer: A
20. Which tool is commonly integrated for CD?
A. Git
B. Docker / Kubernetes
C. SonarLint
D. Jira
Answer: B
21. Jenkins CI pipelines usually run on:
A. Production servers
B. Jenkins agents
C. Developer laptops
D. Load balancers
Answer: B
22. What happens if CI fails?
A. Code is deleted
B. Pipeline stops
C. Deployment continues
D. Jenkins crashes
Answer: B
23. Jenkins enables CI by:
A. Enforcing coding standards
B. Running automated builds and tests
C. Managing Git repositories
D. Writing documentation
Answer: B
24. Which stage is optional in CD?
A. Build
B. Test
C. Production deployment
D. Artifact creation
Answer: C
25. Jenkins does NOT:
A. Trigger pipelines
B. Run scripts
C. Host your application
D. Integrate tools
Answer: C
26. What is an artifact in CI/CD?
A. Log file
B. Compiled output or package
C. Jenkins plugin
D. Source code
Answer: B
27. CI helps developers by:
A. Reducing merge conflicts
B. Increasing manual work
C. Delaying feedback
D. Removing testing
Answer: A
28. CD helps businesses by:
A. Slowing releases
B. Increasing deployment risk
C. Releasing faster and safer
D. Eliminating QA
Answer: C
29. Jenkins pipelines can be:
A. Only scripted
B. Only declarative
C. Scripted or declarative
D. YAML only
Answer: C
30. Which Jenkins concept isolates build environments?
A. Master node
B. Executor
C. Agent
D. Job view
Answer: C
31. CI usually runs on:
A. Every commit
B. Every deployment
C. Every alert
D. Every login
Answer: A
32. CD pipelines often include:
A. Monitoring
B. Alerting
C. Rollback logic
D. All of the above
Answer: D
33. Jenkins can deploy to production:
A. Only manually
B. Using scripts and tools
C. Without permissions
D. Without pipelines
Answer: B
34. What ensures CI quality?
A. Fast builds
B. Automated testing
C. Manual reviews
D. Documentation
Answer: B
35. Jenkins + GitHub webhook enables:
A. Manual builds
B. Scheduled builds
C. Event-driven CI
D. Monitoring
Answer: C
36. CD failures should:
A. Be ignored
B. Trigger rollback or alerts
C. Delete pipelines
D. Restart Jenkins
Answer: B
37. Jenkins is considered:
A. A CI tool only
B. A CD tool only
C. A CI/CD orchestration tool
D. A cloud service
Answer: C
38. CI is mainly for:
A. Ops teams
B. Developers
C. Marketing
D. Customers
Answer: B
39. CD is mainly for:
A. Designers
B. Sales
C. DevOps & Ops
D. Legal teams
Answer: C
40. Jenkins can integrate with:
A. Docker
B. Kubernetes
C. AWS
D. All of the above
Answer: D
41. CI failures are cheapest when found:
A. In production
B. During testing
C. During integration
D. After release
Answer: C
42. Jenkins pipelines are stored:
A. In Jenkins UI only
B. In source control
C. On developer machines
D. In databases only
Answer: B
43. CD reduces risk by:
A. Bigger releases
B. Smaller, frequent releases
C. Manual deployments
D. No testing
Answer: B
44. Jenkins itself does not:
A. Replace Git
B. Trigger builds
C. Run scripts
D. Manage pipelines
Answer: A
45. CI without CD means:
A. No automation
B. Automated testing but manual release
C. Automatic production deploys
D. No Jenkins
Answer: B
46. CD without CI is:
A. Recommended
B. Risky
C. Faster
D. Impossible
Answer: B
47. Jenkins credentials are used for:
A. UI themes
B. Secure access to systems
C. Faster builds
D. Logging
Answer: B
48. Jenkins helps enforce CI/CD by:
A. Automating repeatable processes
B. Writing code
C. Hosting apps
D. Monitoring users
Answer: A
49. The biggest benefit of CI/CD with Jenkins is:
A. More tools
B. Faster feedback and releases
C. Less testing
D. Less automation
Answer: B
50. Jenkins is most effective when:
A. Used alone
B. Integrated into a DevOps toolchain
C. Run manually
D. Avoiding pipelines
Answer: B
Conclusion.
Understanding the difference between Continuous Integration (CI) and Continuous Delivery/Deployment (CD) is key to using Jenkins effectively. Jenkins itself doesn’t write code, test applications, or deploy software on its own it orchestrates the entire CI/CD process, connecting your tools, scripts, and environments into a reliable automation pipeline.
CI ensures that code is frequently integrated, built, and tested, helping teams catch issues early. CD takes things further by making every successful build ready for release, whether deployments are manual or fully automated. Together, CI and CD reduce risk, speed up feedback, and enable faster, more confident releases.
If you scored high on this quiz, you already understand how Jenkins fits into modern DevOps workflows. If not, that’s the point of CI/CD continuous improvement. Mastering Jenkins is less about memorizing features and more about knowing when and why to automate each step of your software delivery lifecycle.
- For more information about CICD, visit Jeevi’s page to explore detailed guides and resources.
