EXIN DevOps Foundation study materials
EXIN DevOps Foundation study resources

EXIN DevOps Foundation study plan

EXIN DevOps Foundation · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

DevOps Basics

  • Define DevOps in your own words and contrast it with traditional waterfall and ITIL-style separation of Dev and Ops.

  • Explain the origin story of DevOps (Agile's spread beyond development, the wall between Dev and Ops, the first DevOpsDays) without looking at notes.

  • Draw a diagram of the software delivery value stream from idea to production and mark where handoffs and wait time occur.

  • List at least six symptoms of dysfunctional Dev/Ops separation (blame culture, long release cycles, environment drift, fear of change) and match each to a DevOps remedy.

  • Build a personal glossary of 20 core terms (CI, CD, pipeline, deployment vs release, feedback loop, CALMS) with one-sentence definitions.

Your checkpoint

A one-page written summary plus hand-drawn value-stream diagram that explains what DevOps is, why it emerged, and which problems it addresses, checked against the syllabus for domain 1.

Week 2

DevOps Principles

  • State the CALMS framework and give a concrete example of each element in a real organization.

  • Explain the Three Ways (flow, feedback, continual learning) and identify which Way a given practice belongs to.

  • Describe the concept of the 'whole team' and how cross-functional, autonomous teams change accountability for production.

  • Compare the roles of a DevOps engineer, SRE, and platform team, and note where they overlap.

  • Write five exam-style multiple-choice questions on principles and justify the correct and incorrect options.

Your checkpoint

A CALMS and Three Ways mapping table in which every practice you have encountered so far is placed under the correct principle, with a short justification for each placement.

Week 3

DevOps Key Practices

  • Trace how a commit moves through build, test, and deployment in a CI/CD pipeline, naming the stage and its purpose at each step.

  • Distinguish continuous integration, continuous delivery, and continuous deployment, and give a scenario where each is appropriate.

  • Explain infrastructure as code and configuration management, including idempotency and why version control matters for infrastructure.

  • Describe automated testing layers (unit, integration, acceptance) and where each belongs in a pipeline.

  • Sketch a pipeline for a small web service with at least six stages and the quality gate at each stage.

Your checkpoint

A labeled CI/CD pipeline diagram for a sample application with each stage, its quality gate, and the failure behavior documented in one page.

Week 4

DevOps Principles & DevOps Key Practices

  • Explain feedback mechanisms such as monitoring, alerting, and telemetry, and connect them to the Second Way.

  • Describe how blameless postmortems and retrospectives support continual learning.

  • Explain trunk-based development and feature toggles, and contrast them with long-lived branches.

  • Identify which practices reduce batch size and which reduce lead time, and explain the mechanism for each.

  • Answer 40 practice questions on principles and practices, then categorize every miss by cause (knowledge gap, misread, guess).

Your checkpoint

A scored practice set of at least 40 questions with a written error log listing each missed item, the correct reasoning, and the domain it belongs to.

Week 5

Practical Application of DevOps

  • Apply the DevOps principles to a concrete case: choose a deployment strategy (blue-green, canary, rolling) for a given risk profile and defend the choice.

  • Explain how to measure flow with lead time, cycle time, deployment frequency, and change failure rate.

  • Describe how security and compliance concerns are integrated into the pipeline rather than bolted on at the end.

  • Outline how to introduce DevOps in an organization with legacy systems and a change-approval process, including first steps and expected resistance.

  • Map three common failure patterns in DevOps adoption (tool-first thinking, no shared ownership, unmeasured outcomes) to countermeasures.

Your checkpoint

A two-page case analysis of a fictional organization that recommends a deployment strategy, a set of flow metrics, and a phased adoption plan, with reasoning tied to domains 2 and 3.

Week 6

Practical Application of DevOps & DevOps Basics

  • Rehearse the definitional and historical material from domain 1 until you can answer without hesitation.

  • Explain the difference between DevOps as a culture movement and as a toolchain, and why both matter to exam questions.

  • Describe how DevOps relates to Agile, Lean, and ITIL, noting where they complement and where they conflict.

  • Practice explaining DevOps to a non-technical stakeholder in under two minutes.

  • Answer 30 mixed questions spanning all four domains under timed conditions.

Your checkpoint

A timed 30-question mixed mock with a recorded score and a one-paragraph reflection on which domain lost you the most points and why.

Week 7

DevOps Basics & DevOps Principles & DevOps Key Practices & Practical Application of DevOps

  • Take two full-length timed mock exams and record scores per domain.

  • Review every incorrect answer and rewrite the underlying fact or principle in your own words.

  • Drill your weakest domain until you can explain its key concepts aloud without notes.

  • Build a one-page memory sheet of definitions, frameworks, and practice-to-principle mappings.

  • Identify any remaining terminology you cannot define confidently and resolve it.

Your checkpoint

Two completed timed mocks with per-domain scores and a finalized one-page memory sheet you can reproduce from memory.

Week 8

DevOps Basics & DevOps Principles & DevOps Key Practices & Practical Application of DevOps

  • Take one final full-length timed mock and target a comfortable pass margin.

  • Review the memory sheet and error log daily, focusing on previously missed items.

  • Practice scenario questions where you must choose among plausible practices and justify the choice.

  • Confirm exam logistics (format, duration, question count, identification requirements) from the official provider.

  • Rest the day before the exam and avoid learning new material in the final 24 hours.

Your checkpoint

A final mock score at or above your target plus a completed exam-readiness checklist covering logistics, memory sheet, and error log review.

Milestones

Week 2: You can explain CALMS and the Three Ways from memory and correctly assign ten practices to their principles.

Week 4: You have scored at least 70% on a 40-question practice set covering domains 2 and 3, with an error log for every miss.

Week 6: You have scored at least 75% on a timed mixed mock across all four domains.

Week 7: Both full-length mocks are complete, and no single domain falls below 70%.

Week 8: Final mock is at or above your target score, and the exam-readiness checklist is complete.