IT and Tech Certifications
30 flashcards
~15 min
DevOps and CI/CD Fundamentals
Learn the core concepts behind continuous integration, continuous delivery, containerization, and infrastructure automation. This deck of 30 flashcards covers the tools, terminology, and practices that power modern DevOps pipelines — from Jenkins and Docker to...
About this deck
Learn the core concepts behind continuous integration, continuous delivery, containerization, and infrastructure automation. This deck of 30 flashcards covers the tools, terminology, and practices that power modern DevOps pipelines — from Jenkins and Docker to Terraform and SRE metrics.
Ready to test yourself?
Flip through all 30 cards in interactive study mode.
All flashcards
Click any question to reveal the answer.
A combination of "Development" and "Operations," describing a culture and set of practices that unify software development and IT operations.
The practice of frequently merging code changes into a shared repository, with each merge automatically built and tested.
A practice where code changes are automatically prepared for a release to production, but the final deployment step requires manual approval.
An extension of continuous delivery where every change that passes automated tests is automatically deployed to production without manual approval.
An automated sequence of stages (build, test, deploy) that code changes pass through from commit to production release.
A dedicated server or service that automatically compiles code, runs tests, and produces build artifacts whenever changes are pushed.
Jenkins and GitHub Actions (GitLab CI, CircleCI, and Travis CI are also common).
Defining CI/CD pipeline steps in a version-controlled configuration file (e.g., YAML) rather than through manual GUI setup.
Packaging an application with all its dependencies into a lightweight, portable unit called a container, ensuring consistent behavior across environments.
A platform for building, running, and sharing containerized applications.
A read-only template containing the application code, libraries, and dependencies used to create containers.
The automated management of container deployment, scaling, networking, and availability across a cluster of machines.
An open-source container orchestration platform used to automate deployment, scaling, and management of containerized applications.
The smallest deployable unit in Kubernetes, consisting of one or more containers that share storage and network resources.
Managing and provisioning infrastructure through machine-readable configuration files instead of manual hardware configuration.
Terraform (Ansible, Pulumi, and AWS CloudFormation are also common).
The practice of automatically maintaining systems in a consistent, desired state, often using tools like Ansible, Chef, or Puppet.
An approach where servers are never modified after deployment; instead, changes are made by replacing them with new instances built from a fresh image.
A deployment strategy that gradually replaces old application instances with new ones, minimizing downtime.
A release strategy that runs two identical environments (blue and green); traffic is switched to the new version once it's verified, enabling instant rollback.
A strategy where a new version is released to a small subset of users first, before rolling it out to everyone.
Reverting an application or system to a previous stable version after a failed or problematic deployment.
A technique that allows developers to enable or disable features at runtime without deploying new code.
A storage system (e.g., Nexus, Artifactory) used to manage and version build outputs like binaries, packages, and container images.
Site Reliability Engineering — a discipline that applies software engineering principles to infrastructure and operations to improve reliability.
Mean Time To Recovery — the average time it takes to restore a system after a failure.
Moving testing activities earlier in the development process to catch bugs sooner and reduce cost of fixing them.
Culture, Automation, Lean, Measurement, and Sharing — five pillars often used to describe DevOps principles.
The continuous collection and analysis of system metrics and logs to detect issues and measure application health.
Prometheus and Grafana (Datadog and the ELK Stack are also common).