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's the core purpose?
CI/CD = Continuous Integration/Continuous Deployment. CI automates testing & merging code changes; CD automates release to production. Goal: faster, reliable, frequent deployments.
Name 3 popular CI/CD platforms used in production.
Jenkins, GitLab CI/CD, GitHub Actions, CircleCI, ArgoCD. Jenkins is self-hosted; GitHub Actions integrates with repos; GitLab CI is built into GitLab; ArgoCD specializes in GitOps deployment.
What is a pipeline in CI/CD and what are its main stages?
A pipeline is an automated workflow. Typical stages: Trigger (on push/PR) → Build → Test (unit, integration) → Security Scan → Deploy to Staging → Deploy to Prod. Can include manual approval gates.
What's the difference between a webhook and polling in CI/CD?
Webhook: Git repo pushes event to CI server immediately (fast, event-driven). Polling: CI server checks repo periodically for changes (slower, less efficient). Webhooks are preferred.
What does 'infrastructure as code' (IaC) mean in CD context?
IaC = defining infrastructure (servers, networks, databases) via code files (Terraform, CloudFormation, Ansible) versioned in Git. Enables reproducible, audited infrastructure changes alongside application code.
Explain the GitOps pattern and name a tool that implements it.
GitOps: Git repo is source of truth for desired state; CD tool watches repo and syncs actual state to match. Tools: ArgoCD, Flux. Benefits: declarative, auditable, easy rollback via Git revert.
What's the purpose of a staging environment in CD pipelines?
Staging mirrors production config/data to test deployments before production release. Catches environment-specific bugs, validates DB migrations, tests infrastructure changes safely without affecting users.
What are blue-green deployments and canary deployments?
Blue-green: run two identical production environments; switch traffic from blue (old) to green (new) instantly, allowing fast rollback. Canary: gradually route % of traffic to new version, monitor, then shift remaining traffic if healthy.
What does a typical Docker-based CI/CD pipeline do?
Build stage creates Docker image from Dockerfile, tags it with commit hash, pushes to registry (Docker Hub, ECR, GCR). Deploy stage pulls image, runs container on target servers or Kubernetes cluster. Enables reproducible, isolated environments.
Name 3 security best practices in CI/CD pipelines.
1) Scan dependencies & code for vulnerabilities (SonarQube, Snyk, Trivy). 2) Use secrets management (HashiCorp Vault, AWS Secrets Manager) never in code. 3) Require code review & approved commits before merge. 4) Sign images & verify signatures. 5) Limit deployment permissions (least privilege).
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 →