DASA DevOps Fundamentals
Every other certification this course covers in depth is, honestly, a certification in something adjacent to DevOps — a cloud vendor's opinion of delivery (AWS DevOps Engineer – Professional), one tool's configuration language (Terraform Associate), one open-source platform's operations (CKA). DASA DevOps Fundamentals is different: it is the one credential on this page actually branded "DevOps," built and owned by a vendor-neutral association whose entire reason for existing is defining what DevOps skill means independent of any cloud, tool, or platform. This page covers what DASA is, the six principles the whole credential is built on, the subject areas the exam actually draws from, real exam logistics, and — since the content brief for this page is explicitly a comparison — how it stacks up against this course's own anchor AWS certification for a reader deciding between a vendor-neutral line on a résumé and a cloud-specific one.
Every other certification on this course's list is a test about one specific workshop's tools — this wrench, this cloud's control panel, this one platform's dashboard. DASA DevOps Fundamentals is a test about the idea of a good workshop itself: why the mechanics and the front-desk staff should talk to each other, why one team should both build the car and drive it around the block afterward, why small fixes beat one giant rebuild. You could pass it having never touched AWS, Kubernetes, or Terraform at all — and plenty of people who work in shops that use none of those three do exactly that.
What DASA DevOps Fundamentals is, and who it's for
☺ Like you're 10: A closed-book, multiple-choice test about DevOps as an idea — culture, principles, team shape — with no cloud console, no terminal, and no single vendor's product anywhere on it.
The DevOps Agile Skills Association (DASA) is a vendor-neutral, member-based association headquartered in the Netherlands, founded in 2015 by a consortium of large enterprises who wanted a portable, hireable definition of DevOps skill that didn't depend on which cloud or toolchain a candidate happened to have used. DASA DevOps Fundamentals is the entry rung of its certification scheme: a closed-book, multiple-choice exam that certifies you understand DevOps as a discipline — its business case, its cultural principles, how teams organize around it, and the shape of the automation and delivery practices underneath it — without testing your ability to operate any specific product. Where the CKA hands you a broken cluster and the AWS DevOps Engineer – Professional asks which AWS service fixes a given scenario, DASA Fundamentals asks whether you can explain why those things are shaped the way they are in the first place.
It targets a wider audience than most of this course's other certifications, precisely because it doesn't require any one technical background. Engineers early in a DevOps transition use it to prove they understand the discipline before diving into tool-specific certs. Product owners, scrum masters, and engineering managers moving into DevOps-adjacent roles use it to gain fluency without needing to write a pipeline. And people at organizations that aren't standardized on AWS, Kubernetes, or any single toolchain use it as a credential that says something true regardless of what their employer runs — a genuinely portable line, in a course otherwise full of certifications tied to one company's product.
| Item | What is generally published |
|---|---|
| Format | Closed-book, multiple choice — no hands-on lab, no terminal, no live environment |
| Question count | Commonly reported around 40 questions — verify the current count at DASA's own page or your training provider's exam guide |
| Duration | Commonly reported around 60 minutes, with standard extra-time accommodation for non-native-language sittings — confirm current timing before you book |
| Passing score | Commonly reported around 65% — treat as directional, not vendor-guaranteed, and verify with your exam provider |
| Prerequisites | None formally required — it is explicitly designed as an entry point |
| Delivery | Through DASA's network of accredited training organizations (ATOs) rather than a single vendor-run testing platform — see the logistics section below |
The six DASA DevOps principles
☺ Like you're 10: Six sentences are the whole backbone of this exam — memorize what each one actually means, in your own words, and you've done most of the real studying.
DASA's own body of knowledge is organized around six DevOps principles, published with no relative weighting between them — unlike the CKA's domain percentages, there is no "this one's worth 30%" here. They read as plain statements, but each one is doing real work resolving a specific organizational failure mode, and the exam expects you to recognize a scenario as an instance of one of the six, not just recite the list.
Wording above is a close, study-oriented paraphrase of DASA's long-published principle names, not a verbatim quote — check DASA's own body-of-knowledge material for exact current phrasing before treating any single word as exam-guaranteed. What's worth noticing structurally: principles 1 and 2 are about why (customer value, the whole lifecycle), 3 and 4 are about who (end-to-end ownership, autonomous teams), and 5 and 6 are about how (continuous improvement, automation). If a scenario question describes a symptom, working out which of those three buckets it falls into is usually faster than trying to recall the exact principle name first.
Principle 3, End-to-End Responsibility, is DASA's own phrasing of the same idea what DevOps is covers as "you build it, you run it" — and Principle 6, Automate Everything You Can, is a restatement of CALMS's Automation pillar. The two frameworks aren't competing; DASA's six principles and Humble and Edwards's CALMS are different vocabularies converging on largely the same underlying discipline. Recognizing that overlap is worth more exam points than memorizing either list in isolation.
What the exam actually tests: six subject areas
☺ Like you're 10: Six topics turn the six principles into testable material — why DevOps exists, the culture underneath it, how teams get organized, what a delivery pipeline actually automates, how architecture has to change to allow any of this, and what automation is actually for.
DASA's syllabus for Fundamentals is commonly organized into six subject areas that translate the six principles above into examinable content. As with the principles, DASA does not publish per-area percentage weights the way the CNCF does for the CKA — treat the list below as complete coverage rather than a prioritization guide, and verify current wording against your training provider's exam guide.
DevOps concepts and value
The elevator-pitch layer: what DevOps is, the business drivers behind adopting it (faster time-to-market, lower change-failure rate, better employee engagement), and its lineage from Agile and Lean thinking. This overlaps heavily with what is DevOps? on this site — the origin story, the wall of confusion, and the "you build it, you run it" fix are exactly this subject area's substance, just told through this course's own cast instead of DASA's material.
DevOps culture
Behaviors and structures: psychological safety, blameless postmortems, learning from failure instead of assigning it, trust between roles that used to be adversarial, and the idea of "T-shaped" people who go deep in one skill but stay broad enough to help across others. Culture & collaboration covers this ground in depth, including the specific mechanics of a blameless postmortem this subject area expects you to recognize.
Organizing for business agility
How teams get structured to actually deliver DevOps-style: cross-functional, autonomous teams (Principle 4) instead of function-based silos, and the tradeoffs in how far that autonomy scales — a five-person team owning one service end-to-end is a very different organizational problem than fifty teams doing the same thing at once, each needing to move independently without becoming fifty accidental variations on the same pipeline. Scaling CI/CD across teams is the closest match on this site for the scaling half of that question.
DevOps and continuous delivery
The pipeline concepts underneath rapid, low-risk releases: build automation, automated testing at multiple stages, deployment automation, and the idea of a deployment pipeline as a single path every change travels down — all covered vendor-neutral, the way CI/CD pipelines covers it on this site, before any specific tool (Jenkins, GitHub Actions, GitLab CI) enters the picture.
Architecting for DevOps
The exam expects you to recognize that team autonomy (Principle 4) is an architecture problem as much as an org-chart problem: a monolith with tightly coupled modules forces cross-team coordination on every release regardless of how the org chart is drawn, while loosely coupled, API-first, independently deployable services (the shape containers & orchestration covers) let autonomous teams actually ship independently. This is the one subject area with a real technical flavor, but it stays at the level of architectural pattern recognition rather than hands-on implementation.
Automation of processes and tools
Not "which tool" — DASA Fundamentals never asks you to choose between Jenkins and GitHub Actions the way a vendor exam would — but "why automate, and what across the toolchain is worth automating first." The DevOps toolchain and infrastructure as code both cover this vendor-neutral automation logic; this subject area is the exam's way of checking you understand automation as a principle (Principle 6) before you've committed to any specific product implementing it.
DASA Fundamentals will not ask you to write a Jenkinsfile, read Terraform HCL, debug a Kubernetes manifest, or name a specific AWS service. If a practice question forces you to know one vendor's console or CLI syntax to answer it, that question is not representative of the real exam — flag the source as suspect. This is also the biggest practical difference from every other certification on this course's list, all of which do exactly that.
DASA Fundamentals vs. this course's anchor cert — AWS DevOps Engineer Professional
☺ Like you're 10: One proves you understand DevOps as an idea, no matter what cloud you use. The other proves you can run production workloads on one specific cloud. A résumé can carry either, or both, and they say completely different things.
This course's own anchor certification, the AWS Certified DevOps Engineer – Professional (DOP-C02), and DASA DevOps Fundamentals sit at opposite ends of two different axes: vendor-specific versus vendor-neutral, and professional-level versus entry-level. Both happen to be knowledge-based, multiple-choice exams with no hands-on lab component — that surface similarity is where the resemblance ends.
| DASA DevOps Fundamentals | AWS DevOps Engineer – Professional | |
|---|---|---|
| Question | Do you understand DevOps as a discipline? | Can you run delivery and operations on AWS specifically? |
| Vendor scope | None — vendor-neutral by design, its entire reason to exist | AWS only — every scenario is an AWS service |
| Level | Entry — no prerequisites, built as a starting point | Professional — AWS recommends 2+ years of hands-on AWS experience |
| Format | Closed-book, multiple choice, ~60 minutes | Multiple-choice and multiple-response, longer and denser |
| What it proves to a hiring manager | You know why the practices exist and can reason about team shape and culture | You can pick the correct AWS service and configuration under a realistic operational scenario |
| Portable across employers? | Fully — the credential means the same thing regardless of what your next employer runs | Only as far as the next employer also runs AWS |
They are not substitutes for each other, and treating either as "the DevOps certification" undersells the other. A reader who already operates AWS in production and wants a credential that proves it should go straight for DOP-C02 — the certifications hub covers it in full, and the DOP-C02 exam guide and study plan are this course's own deep material for it. A reader who wants a vendor-neutral line on a résumé instead — because their employer isn't on AWS, because they're not yet in a role that touches AWS day to day, or simply because they want a credential that reads as "I understand DevOps" rather than "I know one cloud's console" — is better served starting here. And a reader building toward DOP-C02 anyway can still take DASA Fundamentals first: it costs little study time, gives the DOP-C02's Continuous Delivery and Resilient Cloud domains a conceptual floor to stand on, and produces a second, differently-branded line on a résumé for the time DOP-C02 alone spent preparing.
The practical pairing most candidates land on: DASA Fundamentals as the cheap, fast, vendor-neutral floor — good early in a career or a transition into DevOps-adjacent work — and DOP-C02 (or the CKA, if the gap is Kubernetes specifically rather than AWS) as the deep, expensive, technically-verified proof once a specific platform is actually part of the job.
The DASA certification ladder — what comes after Fundamentals
☺ Like you're 10: Fundamentals is the front door. Past it, DASA splits into different rooms depending on whether your job is managing the backlog, writing the code, or leading the change.
Fundamentals is explicitly an entry point, not a terminal credential — DASA's scheme is built to be walked further once it's earned. The general shape, commonly described across DASA's own material: a Product Owner credential for people who manage backlogs and prioritize value in a DevOps team; a Professional-level pair of credentials for hands-on technical practitioners, historically split across two complementary streams (one covering specifying and verifying work, the other covering creating and delivering it); and a Leader-level credential aimed at people driving a DevOps transformation at an organizational level rather than working inside a single team. Exact current names, prerequisites, and whether each requires Fundamentals as a formal gate have shifted over the life of the scheme — confirm the live ladder on DASA's own site before planning a specific next step, rather than treating any specific name above as fixed.
The practical takeaway for this course: Fundamentals is the only DASA rung worth treating as a default recommendation for a general DevOps audience. The rungs above it are role-specific enough that they're worth pursuing only once you know which room you're walking into — product ownership, hands-on technical practice, or organizational leadership — rather than collected in sequence the way someone might work through the CNCF's Kubernetes ladder.
How to prepare using this site
☺ Like you're 10: This course was written around DevOps as a discipline, not around DASA's own material specifically — so most of what this exam tests is already here, just organized under different chapter names.
| Subject area | Study here |
|---|---|
| DevOps concepts and value | What is DevOps? — origins, the wall of confusion, "you build it, you run it," and CALMS |
| DevOps culture | Culture & collaboration — blameless postmortems, shared ownership, trust |
| Organizing for business agility | Scaling CI/CD across teams — what changes once team autonomy has to scale past one team |
| Continuous delivery concepts | CI/CD pipelines · Deployment strategies · Build & artifact management |
| Architecting for DevOps | Containers & orchestration · Infrastructure as code — loosely coupled, independently deployable systems |
| Automation of processes and tools | The DevOps toolchain — vendor-neutral survey of what gets automated and why |
| The DORA/measurement angle (adjacent, not core) | Measuring success: the DORA metrics — not a named DASA subject area, but the evidence base for why Principle 5, Continuous Improvement, works |
| Speed & recall | Flashcards · Glossary · Exam Simulator |
A workable shape for most candidates: two or three passes through What is DevOps? and culture & collaboration until you can restate all six principles from memory in your own words, a single pass through the delivery-pipeline and architecture pages above to ground the more technical-flavored subject areas, and a final run through flashcards and this page's six-principle grid without looking anything up. Because nothing here is hands-on, the highest-value study activity is explaining each principle out loud to someone else — if you can't explain why Cross-Functional Autonomous Teams matters without reading it off a card, that's the gap to close before exam day, not more passive reading.
Illustrative-style question (self-authored, not an actual DASA item):
A platform team ships infrastructure changes for eleven product teams.
Every change to shared infrastructure requires a ticket, a review by the
platform team, and a scheduled maintenance window before it goes live.
Which DASA principle is most directly being violated?
A. Continuous Improvement
B. Cross-Functional Autonomous Teams
C. Create With the End in Mind
D. Automate Everything You Can
(Answer: B — the product teams cannot deliver the change themselves;
they depend on an external team's schedule and approval, which is the
opposite of a cross-functional team holding the authority it needs.)Exam logistics — verify these yourself before you register
☺ Like you're 10: This one works differently from AWS or the CNCF — there's no single vendor store selling a fixed-price exam voucher, so price and even delivery details depend on which training provider you go through.
DASA does not sell exam access directly the way AWS sells a voucher through Pearson VUE or HashiCorp sells one through its own certification portal. Historically, DASA exams have been delivered through its network of accredited training organizations (ATOs) and administered by an accredited exam institute — a role that has moved between examination bodies over the life of the scheme. That structural difference has real practical consequences worth planning around.
| Item | What is generally published |
|---|---|
| Purchase path | Typically bundled with a course from a DASA-accredited training organization, rather than sold as a stand-alone voucher — expect "training + exam" pricing, not an exam-only list price |
| Price | Varies materially by training provider, region, and whether it's bundled with instructor-led training or sold as exam-only — no single authoritative figure to quote here; get a quote from an accredited provider directly |
| Recertification | Commonly reported as not requiring periodic renewal, unlike AWS's 3-year and the CKA's 2-year validity windows — verify current policy on DASA's own site, since certification bodies do revise these terms |
| Permitted resources | Closed-book — no documentation, notes, or reference material during the exam itself |
| Study materials | DASA publishes its own body of knowledge and glossary; most candidates prepare through an accredited training organization's course rather than self-study alone |
Price, question count, duration, pass mark, and recertification policy can all change, and delivery is fragmented across training providers rather than centralized in one vendor portal. This site is independent and unofficial. Confirm current details on DASA's own site before committing to a specific provider or paying for anything, and treat any training organization's marketing page as a sales document first, a syllabus reference second.
Foxy: Every job posting I see says "AWS Certified." Why would I bother with a certification that isn't even about a specific cloud?
Professor Owl: Because DASA Fundamentals proves something DOP-C02 doesn't even try to test, Foxy — that you understand why the practices exist, not just which AWS button implements them.
Ellie the Elephant: And it's vendor-neutral, which matters more than people think. Change jobs to a shop running Azure or bare metal, and your DOP-C02 line reads a little oddly. Your DASA line still means exactly what it meant on day one.
Gizmo: Or just skip the "why" nonsense and go straight for the AWS pro cert. It pays more and nobody asks you to define "cross-functional autonomous team" in an interview. 🤑
Timmy the Turtle: Plenty of interviewers do ask exactly that, Gizmo — especially for anyone moving from a product or Scrum Master role into DevOps. Being able to explain the six principles cold is the whole point, not a detour from it.
Foxy: So it's not instead of the AWS cert. It's underneath it.
Professor Owl: Exactly. One shared vocabulary for why, regardless of which cloud console you end up living in.
1. Name at least four of DASA's six DevOps principles, in your own words. 2. Is DASA DevOps Fundamentals hands-on/performance-based like the CKA, or knowledge-based like the Terraform Associate? 3. What is the single biggest structural difference between DASA DevOps Fundamentals and the AWS DevOps Engineer – Professional exam? 4. Does DASA Fundamentals typically require periodic recertification the way AWS and the CKA do? 5. Name one of the credential tiers that sits above Fundamentals on DASA's ladder. 6. Why might a candidate reasonably take both DASA Fundamentals and DOP-C02, rather than choosing one over the other?
Check your answers
- Any four of: Customer-Centric Action; Create With the End in Mind; End-to-End Responsibility; Cross-Functional Autonomous Teams; Continuous Improvement; Automate Everything You Can.
- Knowledge-based — closed-book, multiple choice, no hands-on lab or live environment, the same style as the Terraform Associate rather than the 100% performance-based CKA.
- Vendor scope: DASA Fundamentals is entirely vendor-neutral and tests DevOps as a discipline (principles, culture, team shape), while DOP-C02 tests knowledge of AWS-specific services and configurations exclusively.
- Generally reported as no — unlike AWS's 3-year and the CKA's 2-year validity windows, DASA's Fundamentals credential is commonly described as not requiring periodic renewal, though this should be verified on DASA's own current site.
- Any one of: a Product Owner credential, a Professional-level technical practitioner credential (historically split across two streams), or a Leader-level credential for organizational transformation.
- They prove different things to different audiences: DASA Fundamentals is the cheap, fast, vendor-neutral proof of understanding the discipline's "why," while DOP-C02 is the expensive, deep, AWS-specific proof of operational competence — pairing them covers both the conceptual floor and the technical depth a hiring manager might be screening for.