Test your CI/CD Best Practices knowledge with a free interactive quiz — 43 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is Continuous Integration (CI)?
In this round
What is Continuous Integration (CI)?
What is the difference between "rolling back" and "rolling forward" as an incident response to a bad deploy?
A pipeline runs build, then unit tests, then integration tests, then deploy to staging, then E2E tests -- all sequentially, taking 45 minutes. What is a common way to speed this up without dropping any checks?
What is the main risk of long-lived feature branches that diverge from main for weeks before merging?
What is the difference between Continuous Delivery and Continuous Deployment?
What is a typical purpose of a dedicated "staging" environment in a pipeline?
A team merges a 3-week-old feature branch into main and CI immediately reports dozens of conflicts and several failing integration tests against changes that landed on main during those 3 weeks. What practice would have most reduced this pain?
Why keep the main branch always in a releasable state?
How do feature flags support trunk-based development?
What is a canary deployment?
Why include monitoring/observability as part of the delivery process?
Why should a rollback plan be decided before a deployment goes out, rather than improvised after something breaks in production?
Gaps to close?
Read the curated CI/CD Best Practices notes — core concepts, patterns, interview prep.