Flashcards · CI/CD · Free
CI/CD flashcards, generated for you.
Example CI/CD study cards to learn from right now — then generate a full set from your own notes (plus a practice quiz) and export to Quizlet or Anki. Free, no account needed.
Example CI/CD flashcards
What does CI/CD stand for and what is its core purpose?
CI/CD = Continuous Integration/Continuous Deployment. Core purpose: automate code testing, building, and deployment to reduce manual errors and speed up release cycles from weeks to hours/minutes.
What is the difference between Continuous Integration and Continuous Deployment?
CI: automatically test and merge code changes multiple times per day. CD: automatically deploy validated code to production. CI catches bugs early; CD eliminates manual release steps.
Name 3 popular CI/CD platforms and when you'd use each.
Jenkins: self-hosted, highly customizable, mature. GitLab CI/CD: git-native, built-in, good for DevOps. GitHub Actions: lightweight, free for public repos, best for GitHub-native teams.
What is a pipeline in CI/CD and what are its typical stages?
A pipeline is an automated workflow triggered by code changes. Typical stages: Source (git push) → Build (compile, unit tests) → Test (integration, security scans) → Deploy (staging) → Release (production).
What command do you use in most CI/CD platforms to run tests, and why is it critical?
`npm test`, `pytest`, `mvn test`, or `./gradlew test` (language-dependent). Critical because failing tests automatically block merges/deployments, preventing broken code from reaching production.
Explain what a webhook is in CI/CD context and provide a real-world example.
A webhook is an HTTP callback that triggers a pipeline when an event occurs. Example: pushing to main branch triggers GitHub webhook → GitHub Actions pipeline → runs tests → deploys to staging if passing.
What is the difference between push-based and pull-based deployment patterns?
Push-based: CI/CD actively deploys to servers (Jenkins pushes to K8s). Pull-based: servers pull config/updates (ArgoCD watches git repo, servers pull desired state). Pull-based is more secure and GitOps-native.
Name 3 critical security practices in CI/CD pipelines.
1) Scan dependencies for vulnerabilities (Snyk, Dependabot). 2) Use secrets management (HashiCorp Vault, GitHub Secrets), never hardcode credentials. 3) Sign container images and verify signatures before deployment.
What is a blue-green deployment and why is it used in CD?
Two identical production environments: Blue (current) and Green (new version). Traffic switches from Blue→Green after validation. Allows instant rollback if issues occur, zero-downtime deployments, and easy A/B testing.
How do you implement CD for microservices at scale (3+ services)? Describe the pattern.
Monorepo or multi-repo with shared pipelines. Each service has own Dockerfile. Use container registry (Docker Hub, ECR). Deploy to Kubernetes with GitOps (ArgoCD/Flux) watching git. Coordinate deployments via Helm charts or Kustomize overlays. Canary/blue-green for risky services.
Make your own CI/CD study set
Flashcards for related topics
Studying CI/CD to build with AI? MindloomHQ turns it into real skills — structured courses, agent projects, and certificates.
Explore MindloomHQ →