Learn deployment gates vocabulary: quality gates, staging gates, manual approval gates, automated compliance checks, deployment blocked by failing gate — the language of controlled software delivery.
0 / 5 completed
1 / 5
The pipeline configuration states: 'The staging gate requires 100% test pass rate.' What is a deployment gate?
A deployment gate is a condition that must be satisfied before the pipeline can advance to the next stage. Gates can be automated (e.g., all tests must pass, code coverage must exceed 80%, no critical vulnerabilities) or manual (a human must approve). Gates prevent bad code from reaching higher environments or production.
2 / 5
The CI/CD system reports: 'The deployment is blocked by a failing quality gate.' What does 'blocked by a failing quality gate' mean?
When a deployment is 'blocked by a failing quality gate', it means the pipeline ran an automated check (SonarQube quality gate, test coverage threshold, security scan) and the result did not meet the defined criteria. The pipeline stops and does not proceed to the next stage until the issue is fixed and the gate passes. This is a core quality enforcement mechanism in mature CI/CD pipelines.
3 / 5
The release process document states: 'We have a manual approval gate before production.' What is the purpose of a manual approval gate?
A manual approval gate pauses the pipeline at a specific point and waits for a human to review and approve before proceeding. It is common before production deployments, giving release managers, product owners, or security teams the opportunity to verify readiness. In GitHub Actions, this is implemented with 'environment protection rules' requiring reviewer approval.
4 / 5
The release manager explains: 'The gate checks for open P1 bugs before allowing deployment to production.' What is the benefit of an automated P1 bug check gate?
An automated gate that checks for open P1 (critical/highest severity) bugs prevents deployments that could worsen an existing production incident or introduce additional risk when the team is already managing a critical issue. It is a safeguard that can be defined in the pipeline to query the issue tracker (e.g., Jira) and block the deployment if any P1 issues are open.
5 / 5
The security team requests: 'Add an automated compliance check gate to the pipeline.' What would an automated compliance check gate verify?
An automated compliance check gate validates that the artefact or deployment meets mandatory security or regulatory requirements before proceeding. Examples include: no critical CVEs in container images (Trivy/Snyk), SAST scan with no high-severity findings (SonarQube), required sign-offs captured, or licence compliance checks passed. In regulated industries (finance, healthcare), these gates are often mandatory.