CI/CD Pipelines Flashcards
6 cards from real DevOps practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 CI/CD Pipelines flashcards as text
What does CI stand for in the context of DevOps?
Answer: Continuous Integration
CI stands for Continuous Integration, the practice of frequently merging code changes into a shared repository with automated builds and tests.
Which of the following is the primary goal of Continuous Delivery (CD)?
Answer: Ensure software can be released to production at any time
Continuous Delivery ensures the software is always in a deployable state so it can be released to production at any time with a manual approval step.
In a Jenkins pipeline, what file defines the pipeline-as-code configuration?
Answer: Jenkinsfile
A Jenkinsfile is a text file stored in the repository that defines the Jenkins pipeline using either Declarative or Scripted pipeline syntax.
What is a 'blue-green deployment' strategy?
Answer: Running two identical production environments and switching traffic between them
Blue-green deployment maintains two identical production environments where one is live (blue) and the other receives the new deployment (green), then traffic is switched.
Which Git branching strategy is most commonly associated with CI/CD pipelines?
Answer: Trunk-based development
Trunk-based development, where all developers commit to a single main branch frequently, best supports CI/CD by reducing merge conflicts and enabling rapid integration.
What is the purpose of a 'pipeline artifact' in CI/CD?
Answer: A built output (binary, JAR, Docker image) produced by one stage and consumed by another
Pipeline artifacts are built outputs like binaries or container images produced by one stage and passed downstream to subsequent stages such as testing or deployment.