Get Your CertOtherPlayCompete
‹ Other

CI/CD & DevOps Practices

1 test · 10 questions
Browse all 10 questions ›
Your progress
Test 110 questions

Study guides

Terraform Associate certification (004): exam and costTerraform Associate certification (004): what the one-hour exam tests, its US$70.50 cost, renewal, next steps, and a study plan.
AZ-400 exam guide: DevOps Engineer Expert in 2026AZ-400 exam guide: the DevOps Engineer Expert prerequisites now that AZ-204 is retired, the five skill areas, price, renewal and a study plan.
Best DevOps certification: AWS, Azure, Google or CKAThe best DevOps certification for your stack: AWS DOP-C02, Azure AZ-400, Google Cloud DevOps Engineer and CKA compared on cost, level and prerequisites.
DevOps interview questions: what gets asked, by levelDevOps interview questions by topic: Linux, Git, CI/CD, Docker, Kubernetes, Terraform and cloud, with what a strong answer covers at each level.

About these CI/CD and DevOps questions

This is a practice topic, not a vendor exam. The questions cover the delivery practices behind DevOps, independent of any tool: how code gets from a commit to production safely, quickly and repeatably. They suit developers and operations engineers preparing for DevOps, platform or SRE interviews, and people studying for a cloud DevOps certification who want the underlying ideas clear before learning a vendor's pipeline service.

The questions draw on DORA's research into software delivery performance and on widely used references on continuous delivery, trunk-based development and deployment patterns. Most are scenarios: a team's releases keep breaking, a rollback would lose data, or secrets end up in build logs, and you choose the practice that actually fixes it. The wrong options are often popular habits, such as long-lived branches or rebuilding for each environment, that make delivery slower or riskier.

What the questions cover

There is one 10-question test so far. It covers:

  • CI/CD fundamentals. The difference between continuous delivery and continuous deployment.
  • Branching strategy. Why trunk-based development with short-lived branches reduces painful merges.
  • Feature flags and progressive delivery. Using release toggles to separate deploying code from releasing a feature.
  • Deployment strategies. When a canary release suits better than blue/green, and the expand-and-contract pattern for schema changes that keeps rollback possible.
  • DORA metrics. What change fail rate measures and how it fits with the other delivery measures DORA tracks: change lead time, deployment frequency, failed deployment recovery time and deployment rework rate.
  • Pipeline design. Building an artifact once and promoting the same artifact through each environment.
  • Infrastructure as code. How immutable servers prevent configuration drift.
  • Testing in pipelines. Why the test pyramid puts fast unit tests at the base for quick feedback.
  • Pipeline security. Keeping secrets out of source and logs, and scoping what each job can reach.

How to use them

  • Think about the failure each practice prevents. Feature flags, canaries and expand-and-contract all exist because of something that went wrong without them.
  • Build a small pipeline yourself with whatever CI service you can access. Making one artifact, promoting it and rolling it back teaches more than any diagram.
  • Treat the DORA metrics as a set. A team that deploys often but breaks things isn't doing well, and the questions expect you to weigh speed and stability together.
  • Read the explanations for the wrong options. They show why a fix that sounds reasonable, like restoring a backup to roll back, can lose data or slow the team down.
  • Come back to these when studying a cloud DevOps exam. Its pipeline and deployment services implement the same patterns under vendor names.

These questions are original, written from DORA's public research and other open references on continuous delivery. They are not taken from any exam or interview question bank.