Top 30 Ci/cd Interview Questions and Answers
30 multiple-choice questions on Ci/cd, drawn from 30 bites out of the 245 tagged Ci/cd on Tezvyn. Answer them here or read straight down. Every question carries the correct option, why it is correct, and a link to the bite it came from.
30 questions. Pick an answer, or open “Show the answer” to read it.
Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.
Question 1 of 30
A team merges into a shared branch daily with automated builds and tests. What is the single most important goal of this Continuous Integration practice?
Show the answer
Answer: c · Keeping the integrated codebase in a workable state at all times
The defining goal of CI is maintaining a workable integrated codebase, not deployment, which is the realm of CD. While automation and bug detection are part of the practice, they are mechanisms and secondary benefits rather than the core objective.
Read the full bite: What is CI, and what is its single most important goal?
Question 2 of 30
What is the primary distinction that makes MLOps necessary beyond traditional DevOps for machine learning systems?
Show the answer
Answer: a · Continuously monitoring model performance and orchestrating retraining on new data.
MLOps uniquely addresses the lifecycle of machine learning models and their underlying data, including continuous monitoring for performance decay and automated retraining. Traditional DevOps focuses primarily on the code lifecycle, which is insufficient for the dynamic nature of ML models.
Read the full bite: MLOps vs. DevOps: More Than Just "DevOps for ML"
Question 3 of 30
Which characteristic is most crucial for an effective build automation process?
Show the answer
Answer: c · It consistently transforms source code into a runnable application, regardless of the environment.
The card emphasizes that build automation makes the process "repeatable, reliable" and ensures "the same result every time, no matter who pushes the 'start' button." Option C directly reflects this core benefit. Option D describes the "it works on my machine" problem that build automation aims to eliminate, not a desired characteristic.
Question 4 of 30
A developer pushes to main, triggering a CI pipeline with build, test, and deploy stages. Which outcome best matches typical execution?
Show the answer
Answer: b · A runner builds the project; then multiple runners execute test jobs in parallel; deployment proceeds only if every test job succeeds.
The card states that runners (not the Git server) execute jobs, that jobs within a stage run in parallel, and that a stage must succeed completely before the next stage begins. Option C is tempting because it correctly mentions sequencing but wrongly assumes everything runs sequentially on one machine and ignores the requirement that all jobs pass.
Read the full bite: Describe the typical CI pipeline sequence from push to deploy
Question 5 of 30
Which scenario would trigger an automated MLOps deployment but typically not a traditional DevOps pipeline?
Show the answer
Answer: b · Production monitoring detecting drift in input data distributions
The card states that MLOps deployments add triggers like data drift detection, unlike DevOps pipelines that react to code commits, dependency patches, or infrastructure changes. The GPU driver update is a tempting distractor because a common misconception is that MLOps is simply DevOps plus GPUs.
Read the full bite: What are the primary differences between traditional DevOps and MLOps?
Question 6 of 30
What is a key advantage of automated testing in modern software development?
Show the answer
Answer: a · It allows for rapid and confident deployment of code changes by detecting regressions early.
The card highlights that automated testing "provides the confidence needed to deploy changes frequently" and is "the foundation for catching regressions." Option B is incorrect because the card explicitly states automated testing is "not suited for exploratory testing... or for assessing subjective user experience."
Read the full bite: Automated Testing: Catch Bugs Before They Ship
Question 7 of 30
A deployed fraud model degrades. Using immutable lineage best practices, what is the most reliable way to isolate data drift from a code bug?
Show the answer
Answer: a · Reproduce the exact training run by combining the manifest's commit SHA, dataset hash, and locked dependencies, then verify the metrics match production logs
Reproducing the full training context from the manifest proves the model still yields the same metrics, confirming that production degradation is due to data drift rather than a code bug. Option B is tempting because it uses the exact dataset, but swapping in the latest code introduces a new variable and breaks the lineage chain needed for a valid comparison.
Read the full bite: Why version code, data, and models in MLOps?
Question 8 of 30
A company automatically deploys its internal tools to production but requires manual sign-off for its customer-facing payment service. What does this mixed strategy best demonstrate?
Show the answer
Answer: d · Different applications may require different pipeline models based on business risk and compliance needs.
The card stresses that the choice between Continuous Delivery and Continuous Deployment is driven by business context, regulatory requirements, and blast radius, and that organizations often run a mixed model. Option A reflects the common misconception that Delivery is just an inferior version of Deployment, while the correct answer captures the intentional, risk-based pipeline design described in the card.
Question 9 of 30
Which scenario best demonstrates the appropriate use of an artifact repository?
Show the answer
Answer: a · Publishing a newly built Java .jar file to be consumed by other internal projects.
An artifact repository is designed to store and share binary outputs like compiled code (.jar files) from a build process for consumption by other systems or teams. Storing source code is for version control systems, while archiving unstructured logs or serving static assets are roles for general file storage or web servers, not artifact repositories.
Read the full bite: Artifact Repository: Your CI/CD's Private Library
Question 10 of 30
An e-commerce company notices prediction accuracy dropping on a model whose serving code hasn't changed. What is the most appropriate first step in a mature MLOps setup?
Show the answer
Answer: a · Trigger the CT pipeline to validate data, train, evaluate against the champion, and promote if blessed
When model performance decays but serving code is unchanged, the CT pipeline should validate data, retrain, and evaluate before promotion. Option D is wrong because it bypasses evaluation gates and data validation, and B is wrong because models are separate deployable units from serving code.
Read the full bite: Explain ML pipelines and typical CI/CD/CT components
Question 11 of 30
Which approach aligns with the 'build once, deploy many' principle when handling environment-specific database URLs?
Show the answer
Answer: d · Build the container image once, then provide the database URL via environment variables at deployment time
The correct answer preserves artifact immutability by externalizing configuration and deploying the same binary everywhere. Option C is tempting because build arguments appear to parameterize deployments cleanly, but they force per-environment rebuilds that can introduce unverified dependency changes.
Read the full bite: What is a build artifact and why build once deploy many crucial?
Question 12 of 30
What is the primary advantage of implementing a Blue-Green deployment strategy?
Show the answer
Answer: d · It ensures continuous service availability and provides immediate rollback capabilities during deployments.
The card states that Blue-Green deployment enables "zero-downtime releases and instant rollbacks," which directly translates to continuous service availability and immediate rollback. Option C is incorrect because this strategy temporarily doubles infrastructure costs.
Read the full bite: Blue-Green Deployment: Zero-Downtime Releases
Question 13 of 30
What is the primary distinction between a canary release and A/B testing?
Show the answer
Answer: a · A canary release primarily validates the technical stability and performance of a new version, whereas A/B testing evaluates user engagement and business outcomes.
The card states that a canary's goal is to quickly validate stability, while an A/B test is a longer-running experiment to test a business hypothesis. Option B describes a feature of canary releases but not its primary distinguishing purpose from A/B testing.
Read the full bite: Canary Release: Test New Code on Real Users, Safely
Question 14 of 30
A platform team notices their pipeline is consistently green, but lead time for changes has grown from hours to days. Which diagnostic approach best aligns with value stream thinking?
Show the answer
Answer: d · Decompose lead time into queue, active pipeline, and post-pipeline release intervals
Decomposing lead time reveals whether waste hides in pre-merge queues, slow green stages, or post-merge deployment friction. Investigating test flakiness is tempting but misguided because a green pipeline rules out build failures as the cause.
Read the full bite: Pipeline is green but lead time grows. Three areas to investigate?
Question 15 of 30
What is the primary distinguishing characteristic of CD4ML compared to traditional CI/CD pipelines?
Show the answer
Answer: a · It explicitly manages and automates changes across code, data, and trained models.
CD4ML's core innovation is extending CI/CD to manage the unique lifecycle of ML systems, which includes versioning and automating changes for code, data, and the trained model. While it does automate deployment (Option C), this is also a feature of traditional CI/CD; the distinction lies in the comprehensive management of data and models as first-class artifacts.
Read the full bite: CD4ML: Automating ML from Data to Deployment
Question 16 of 30
Which is the primary advantage of Pipeline as Code over configuring CI/CD processes via a graphical user interface?
Show the answer
Answer: a · It enables version control, peer review, and auditability of the build and deployment logic.
The core benefit of Pipeline as Code is treating the pipeline definition as a version-controlled file, which allows for reviewable changes and a complete audit history. Option D is incorrect because Pipeline as Code explicitly involves defining the pipeline through code, such as a Jenkinsfile.
Read the full bite: Pipeline as Code: Versioning Your Build Process
Question 17 of 30
Which scenario best illustrates a fundamental CI/CD difference between monoliths and microservices regarding blast radius and artifact indivisibility?
Show the answer
Answer: a · A microservice team deploys a signed container side-by-side with the previous version, while a monolith rollback requires reverting the entire application
This captures the core idea that monoliths produce a single indivisible artifact requiring full rollback, while microservices support independent side-by-side deployments with signed images. Option C reverses these architectures and promotes the shared-pipeline anti-pattern the card explicitly warns destroys team autonomy.
Read the full bite: How does your CI/CD strategy differ between monoliths and microservices?
Question 18 of 30
Which scenario most strongly indicates the necessity of implementing a Continuous Training (CT) pipeline for an ML model?
Show the answer
Answer: c · The model's performance metrics are steadily degrading in production due to shifts in the input data distribution.
Continuous Training (CT) is specifically designed to address model performance decay caused by 'data drift' or non-stationary data patterns in production. Option C directly describes this core problem. Option D refers to traditional CI/CD for code or infrastructure, not CT for model retraining due to data changes.
Read the full bite: Continuous Training: CI/CD for ML Models
Question 19 of 30
A software team implements an Andon Cord for their main branch. Which action indicates a fundamental misunderstanding of its core principle?
Show the answer
Answer: d · The team creates a high-priority ticket for the developer who introduced the bug to fix it by the next stand-up.
The card explicitly states that creating a high-priority ticket, assigning individual blame, or scheduling the fix for later are common mistakes that miss the point of an Andon Cord. The principle requires an immediate, collective, all-hands-on-deck response, not a scheduled, individual task.
Read the full bite: How would you implement an Andon Cord for a software team?
Question 20 of 30
According to the 'cattle, not pets' mental model for immutable infrastructure, which action is characteristic?
Show the answer
Answer: a · Building a new server image with all necessary updates and replacing existing instances.
The 'cattle, not pets' model dictates that servers are replaced, not modified. This means building a new image with updates and deploying new instances from it, then decommissioning the old ones. Modifying running instances, even with configuration management, is characteristic of mutable infrastructure.
Read the full bite: Immutable Infrastructure: Treat Servers Like Cattle, Not Pets
Question 21 of 30
Which characteristic of blue-green deployment most directly enables sub-minute rollback during a failed release?
Show the answer
Answer: c · The blue environment remains fully operational and ready to receive traffic after cutover.
The card states that because the old environment stays warm, rollback is a single traffic switch rather than a redeploy. Option A describes a canary release, which reuses the same infrastructure and gradually shifts traffic, making it a common misconception rather than true blue-green behavior.
Question 22 of 30
A CI pipeline fails on the main branch. According to the Andon Cord principle, what is the most appropriate immediate team response?
Show the answer
Answer: b · The entire team stops current work to swarm on diagnosing and fixing the problem.
The core of the Andon Cord is collective ownership and immediate response. The entire team swarms because build health is everyone's responsibility. While reverting might be the eventual fix, the first step is always to diagnose the root cause as a team.
Read the full bite: How would you implement an Andon Cord for a software team?
Question 23 of 30
A developer's commit breaks the integration test suite on trunk. According to Andon Cord principles, what is the most appropriate immediate response?
Show the answer
Answer: c · Halt the pipeline, block all merges, and have the team swarm to fix the root cause immediately
The correct answer reflects the automatic hard stop, merge blocking, and collective swarm for immediate root cause resolution that defines the software Andon Cord. Option A is tempting because reverting seems like a safe way to keep trunk green, but the card explicitly identifies reverting to fix in a branch later as a red flag that avoids collective ownership and stop-the-line discipline.
Read the full bite: How would you implement a software Andon Cord equivalent?
Question 24 of 30
Which of the following is the primary security benefit of adopting a pull-based GitOps deployment model?
Show the answer
Answer: a · It prevents the exposure of production cluster credentials to external CI/CD pipelines or systems.
The card states that the pull-based model is more secure as it "avoids exposing cluster credentials externally," contrasting it with the push-based model that "requires giving your CI system powerful, high-risk credentials." Option D describes a general benefit of using Git for configuration, not a specific security advantage of the pull-based model.
Read the full bite: GitOps: Your Git Repo is the Single Source of Truth
Question 25 of 30
How does rebasing a feature branch onto main before a PR typically affect CI behavior compared to merging main into that branch?
Show the answer
Answer: b · Rebase generates new commit SHAs, causing CI to treat rebased commits as new pushes and queue multiple builds.
Rebase replays commits onto the target branch, which creates fresh SHAs that CI systems treat as brand-new pushes, burning compute minutes and orphaning prior build results, whereas merge preserves the original SHAs and triggers a single integration build. Option C is tempting because many beginners believe rebase is inherently cleaner or safer, but it actually requires force-push and breaks the one-to-one link between a commit and its CI result.
Read the full bite: Difference between git merge and git rebase before a pull request
Question 26 of 30
Which operation is LEAST suited for an idempotent design in an automation script?
Show the answer
Answer: a · Recording each attempt of a user login into an audit trail.
The card states that "appending a log entry" is an example of an operation where idempotency is the "wrong goal" because you want "each execution to have a distinct effect." The other options describe tasks (package installation, resource provisioning, schema migration) that are explicitly mentioned as scenarios where idempotency is vital for reliable, repeatable automation.
Question 27 of 30
Which statement best describes a core operational principle of a Distributed Version Control System (DVCS)?
Show the answer
Answer: b · Each developer works with a complete, independent copy of the entire project history on their local machine.
A DVCS provides every developer with a full, independent copy of the entire repository and its history, allowing most operations to occur locally. Option D describes a centralized system, where commits are immediately synchronized with a single server.
Read the full bite: Distributed Version Control (DVCS): Everyone Gets a Copy
Question 28 of 30
Which strategy most effectively enforces analytics schema consistency at scale without creating a process bottleneck?
Show the answer
Answer: d · Use a version-controlled schema registry with generated SDKs, CI build failures, and edge validation, plus lightweight self-service governance
Option D is correct because it layers automated prevention, detection, and self-service governance to treat data quality as a systems problem rather than relying on human vigilance. Option A is a tempting distractor because documentation and manual review sound like governance, but the card identifies them as red flags that rot under delivery pressure and create scaling bottlenecks.
Read the full bite: Propose a strategy to enforce a consistent analytics event schema
Question 29 of 30
How does Trunk-Based Development allow a team to continuously deploy an unfinished multi-week feature without exposing it to end users?
Show the answer
Answer: d · Wrap the new code paths in a feature flag that defaults to off in production, allowing the same binary to deploy continuously while keeping the feature hidden.
Feature flags that default to off let teams integrate to main daily and deploy continuously while hiding incomplete behavior from users. The long-lived branch approach in option B contradicts Trunk-Based Development and reintroduces painful merge conflicts.
Read the full bite: How do feature flags enable unfinished work in Trunk-Based Development?
Question 30 of 30
When integrating a 50-commit stale branch that others may have pulled, which strategy best preserves shared history while validating pipeline stability?
Show the answer
Answer: c · Merge main into the feature branch locally, resolve conflicts, run full tests, and open a draft PR before merging
Merging main into the feature branch preserves commit hashes and shared history, while a draft PR exercises the full CI pipeline without spamming reviewers or triggering merge queues prematurely. Rebasing and force-pushing is dangerous because it rewrites public history and breaks every collaborator's local environment.
Read the full bite: How do you safely merge a 50-commit stale branch with conflicts?
Could you explain these out loud?
That is what an interview actually tests. Tezvyn gives you questions like these with what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.