CI/CD Interview Questions

1. What is CI/CD and what problems does it solve in software delivery?

2. What is the difference between continuous integration, continuous delivery, and continuous deployment?

3. What is a CI/CD pipeline and what are its typical stages?

4. What is Jenkins and how does it fit into a CI/CD workflow?

5. What is the difference between a Jenkins freestyle project and a pipeline?

6. What is a Jenkinsfile and what is pipeline as code?

7. What is the difference between a declarative and a scripted Jenkins pipeline?

8. What are Jenkins agents (nodes) and how does distributed builds work?

9. How do Jenkins stages, steps, and post conditions work?

10. What is GitHub Actions and how do workflows, jobs, and steps work?

11. What is a GitHub Actions runner and what is the difference between hosted and self-hosted runners?

12. What are GitHub Actions secrets and how do you manage them securely?

13. What is GitLab CI and how does the .gitlab-ci.yml file work?

14. What is the difference between a build artifact and a cache in CI/CD?

15. How do you handle secrets and credentials in a CI/CD pipeline?

16. What is a build matrix in CI/CD and why is it useful?

17. What is the difference between blue-green deployment and canary deployment?

18. What is a rolling deployment and how does it minimize downtime?

19. How do you implement automated testing in a CI/CD pipeline?

20. What is the difference between a smoke test and a full regression test in CI/CD?

21. How do you handle rollbacks in a CI/CD pipeline?

22. What is trunk-based development and how does it relate to CI/CD?

23. What is the difference between a webhook trigger and a scheduled trigger in CI/CD?

24. How do you speed up a slow CI/CD pipeline?

25. What is a deployment environment (dev, staging, production) and how do promotions work?

26. What is infrastructure as code's role in CI/CD?

27. How do you enforce quality gates in a CI/CD pipeline?

28. What is the difference between a self-hosted and a cloud-hosted CI/CD system?

29. How do you monitor and observe a CI/CD pipeline?

30. What are common security best practices for CI/CD pipelines?

31. How do you triage and eliminate flaky tests in a CI pipeline?

32. How do you design CI caching keys and prevent cache poisoning?

33. How do you promote one immutable artifact across environments instead of rebuilding per stage?

34. How do you give CI runners cloud access without long-lived static credentials?

35. How do you establish build provenance and protect the CI supply chain?

36. How do rollback mechanics differ between blue-green and canary deployments in practice?

37. How do you build only the affected projects in a monorepo pipeline?

38. How do you isolate and harden self-hosted CI runners?

39. How do you instrument a CI/CD pipeline so you can debug it like a production system?

40. How do you run database migrations safely in a continuous deployment pipeline?

41. How does a merge queue keep a busy main branch green, and where does it break down?

42. How do you version, test and safely roll out shared reusable pipeline components?

43. A build passes locally but fails in CI. How do you diagnose and permanently fix that class of problem?

44. How do you make container image builds both fast and reproducible inside CI?

45. How do you implement auditable change approvals in a pipeline without reverting to manual releases?

46. How do you split testing between pre-merge and post-merge stages when the full suite is too slow to gate every change?

47. How do you manage feature flags in a continuous deployment pipeline, including retiring them?

48. Developers say CI is slow but job durations are unchanged. How do you diagnose and fix runner capacity problems?

49. How do you automate version numbering and release notes without letting the pipeline publish the wrong thing?

50. How does GitOps pull-based delivery differ from pipeline-push deployment, and when would you choose each?

51. How do you automate dependency updates without letting the automation become a supply-chain weak point?

52. A CI job intermittently fails with an out-of-memory kill or no space left on device. How do you debug and fix it?

53. How do you run a flaky-test quarantine policy without quietly losing coverage?

54. Why must a pull request from a fork never receive your pipeline secrets?

55. How do you make a build reproducible bit-for-bit, and why does it matter for release integrity?

56. How does progressive delivery with automated analysis work, and what makes the rollout abort correctly?

57. How do you roll back a deployment when the database migration cannot be undone?

58. How do you measure lead time for changes and change failure rate honestly?

59. Trunk-based development or long-lived branches — which actually delivers faster, and why?

60. How do you decide what to cache versus rebuild in CI, and when does caching make things worse?

61. How do you debug tests that pass individually but fail when the suite runs in parallel in CI?