Last Updated On
Welcome to the Advance Level of CI/CD Quiz!
This blog post features 20 multiple-choice questions that explore advance concepts of CI/CD.
1. Which pattern best isolates pipeline failures caused by a single team’s changes while allowing other teams to continue deploying?
a) Trunk-based development only
b) Monorepo with centralized pipeline
c) Per-repo pipelines with dependency gating
d) Global pipeline that serially builds all projects
Answer 1
c) Per-repo pipelines with dependency gating
Per-repo pipelines with dependency gating allow individual teams to run and fail their own pipelines; dependency gating prevents downstream breakage while other teams remain unaffected. Monorepo or centralized pipelines can create cross-team coupling and large blast radius.
2. What is blue-green deployment?
a) Using colorful terminals
b) Running two production environments (blue & green) and switching traffic from old to new to enable quick rollback
c) Deploying only on weekends
d) Merging branches manually
Answer 2
b) Running two production environments (blue & green) and switching traffic from old to new to enable quick rollback
Blue-green allows near-instant rollback by switching back to the old environment if issues arise.
3. What is pipeline orchestration?
a) Writing scripts
b) Coordinating multiple pipeline stages/jobs
c) Monitoring servers
d) Code review
Answer 3
b) Coordinating multiple pipeline stages/jobs
Pipeline orchestration is about managing how different parts of a pipeline work together.
4. What does “immutability” of deployment artifacts mean?
a) Artifacts can be changed after deployment
b) Artifacts are versioned and never altered; updates use new versions
c) Artifacts are not stored
d) Artifacts are randomly modified
Answer 4
b) Artifacts are versioned and never altered; updates use new versions
Immutable artifacts improve reproducibility and simplify rollbacks and auditing.
5. 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 5
b) Slow pipelines due to shared code.
In a monorepo (a single repository containing many projects or services), all code lives together. A small change in one part of the repo can trigger builds/tests across many projects
6. What role do linters and static analysis play in CI?
a) They are unrelated to CI
b) They automatically check code quality and catch common issues before runtime
c) They replace unit tests
d) They slow down everything with no benefit
Answer 6
b) They automatically check code quality and catch common issues before runtime
Linters/static analysis help enforce standards and catch bugs early in the CI pipeline.
7. Which CI/CD metric best indicates how quickly a team can deliver changes to production?
a) Mean time to detect (MTTd)
b) Mean time to recovery (MTTR)
c) Lead time for changes
d) Change failure rate
Answer 7
c) Lead time for changes
Lead time for changes measures the time from code committed to code successfully running in production, indicating delivery speed.
8. In a GitOps-based CD approach, what is the single source of truth for the desired system state?
a) The running cluster state
b) A centralized database of deployments
c) The Git repository containing manifests/configs
d) CI server build logs
Answer 8
c) The Git repository containing manifests/configs
GitOps uses Git as the source of truth for declarative system state; the cluster reconciles to match Git.
9. What is the main security risk of storing secrets directly in pipeline YAML files in a CI system?
a) They get compressed and become unreadable
b) Secrets can leak via logs, code reviews, or repository access
c) CI will encrypt them by default
d) No risk if the pipeline is private
Answer 9
b) Secrets can leak via logs, code reviews, or repository access
Storing secrets in YAML can expose them through logs, VCS history, or access control lapses. Use secret managers or encrypted variable stores.
10. When designing pipeline agents (runners) at scale, which strategy improves security and reliability?
a) Use a single shared privileged runner for all jobs
b) Use ephemeral, least-privilege runners that boot per job and run in isolated environments
c) Use permanent runners with root access to improve speed
d) Allow developers to run arbitrary system services on runners
Answer 10
b) Use ephemeral, least-privilege runners that boot per job and run in isolated environments
Ephemeral, least-privilege runners reduce attack surface and avoid state leakage between jobs; isolation improves reliability and reproducibility.
11. In pipelines, why are “shift-left” security practices recommended?
Choose one option
a) They defer security to production
b) They integrate security checks earlier, catching issues sooner and reducing cost of fixes
c) They replace code reviews
d) They focus only on runtime security
Answer 11
b) They integrate security checks earlier, catching issues sooner and reducing cost of fixes
Shift-left integrates security (SAST, dependency scanning) early in the development lifecycle to catch vulnerabilities earlier when remediation is cheaper.
12. Which practice helps prevent configuration drift between dev/staging/prod?
a) Manual configuration changes via SSH in each environment
b) Store configuration declaratively (in Iac) and apply via automated pipelines with drift detection
c) Only document config differences in a wiki
d) Use different tools in each environment for flexibility
Answer 12
b) Store configuration declaratively (in Iac) and apply via automated pipelines with drift detection
Declarative configuration plus automated application and drift detection ensures environments remain consistent.
13. Which rollout method is best when the new version requires a schema migration that is backwards-incompatible?
a) Immediate switch to new version across all nodes
b) Use a multi-step deployment with backward-compatible migration, feature flags, and careful DB migration plan (expand-then-contract)
c) Skip DB migration and let the app handle it
d) Disable monitoring during migration
Answer 13
b) Use a multi-step deployment with backward-compatible migration, feature flags, and careful DB migration plan (expand-then-contract).
Expand-then-contract migrations and feature flags avoid downtime and ensure both old and new code can function, enabling safe transitions.
14. Which is the best way to manage secret injection into containerized workloads at runtime?
a) Bake secrets into container images
b) Integrate runtime secret providers (e.g., secrets mounted via a secure secrets manager with short-lived credentials)
c) Put secrets in plain environment variables in CI logs
d) Commit secrets to the repo in an encrypted file without automated retrieval
Answer 14
b) Integrate runtime secret providers (e.g., secrets mounted via a secure secrets manager with short-lived credentials)
Runtime retrieval via a secrets manager with short-lived credentials minimizes exposure and avoids baking secrets into images or repos.
15. Which metric best measures the reliability of the release process?
a) Number of commits per day
b) Change failure rate (percentage of deployments causing production incidents)
c) Average build time only
d) Code churn
Answer 15
b) Change failure rate (percentage of deployments causing production incidents)
Change failure rate indicates how often deployments lead to failures requiring remediation, reflecting release reliability.
16. What is the best pattern to ensure database schema migrations are rolled forward safely across multiple instances?
a) Run migration on a single instance and rely on replication only
b) Use rolling migrations that coordinate schema changes with backward-compatible code, and apply migrations in a way that supports both versions (expand-then-contract)
c) Apply migrations only when traffic is zero
d) Make destructive changes directly in production without testing
Answer 16
b) Use rolling migrations that coordinate schema changes with backward-compatible code, and apply migrations in a way that supports both versions (expand-then-contract)
Coordinated rolling migrations with backward compatibility reduce downtime and service disruption.
17. Which of the following is true about feature flags in CI/CD?
a) They always replace the need for testing
b) They can decouple deployment from release and allow targeted rollouts and safe rollbacks when used with proper lifecycle management
c) They remove the need for version control
d) They are only useful for UI changes
Answer 17
b) They can decouple deployment from release and allow targeted rollouts and safe rollbacks when used with proper lifecycle management
Feature flags let teams deploy code without exposing features to all users, enabling controlled experiments and quick rollbacks.
18. In multi-cloud CD deployments, which capability ensures consistent delivery across providers?
a) Using distinct CI/CD tools per cloud without abstraction
b) Declarative IaC that targets cloud-agnostic layers or provider-specific modules with a consistent pipeline orchestrator and artifact promotion model
c) Manually executing cloud CLIs per provider
d) Only deploying to one cloud and failing the others
Answer 18
b) Declarative IaC that targets cloud-agnostic layers or provider-specific modules with a consistent pipeline orchestrator and artifact promotion model
19. What is a Docker Registry?
a) A network router
b) A local storage system
c) A virtual machine host
d) A repository for storing and sharing Docker images
Answer 19
d) A repository for storing and sharing Docker images
A Docker Registry is a storage system where you can store, share, and retrieve Docker images. Docker Hub is a popular example.
20. What is the primary purpose of the Docker Engine?
Choose one option
a) To provide a graphical visualization of containers
b) To build and run containers
c) To manage databases inside containers
d) To interface with Kubernetes
Answer 20
b) To build and run containers
We would love to hear from you! Please leave your comments and share your scores in the section below
QA Automation Expert 