DOF study guide
DOF · Work through your exam, one topic at a time.
This independent study page provides practice for DOF. Its editorial learning areas include DevOps adoption, culture and delivery flow; Automation and safe delivery technology; Measurement, reliability and learning signals; Feedback and continuous improvement. The questions develop subject knowledge and application through worked reasoning, distinctions between competing answers, and practical scenarios. Study the relevant guide before attempting a mixed set, then explain the evidence or calculation that supports each answer. Topics on this exam: DevOps adoption, culture and delivery flow, Automation and safe delivery technology, Measurement, reliability and learning signals, and Feedback and continuous improvement. The DOF study guide has 4 sections and about 2,355 words.
01DevOps adoption, culture and delivery flow
DevOps is a cultural and professional movement that combines people, process and technology so an organisation can shorten the time between committing a change and running it safely in production, while improving quality and reliability. It emerged because Development and Operations had conflicting incentives: Dev optimised for change, Ops optimised for stability. The result was long handoffs, late discovery of problems and blame when a release failed. The term was popularised around 2009, alongside early "10+ deploys per day" talks that showed high performance and stability were compatible.
1,069 words, about 5 min02Automation and safe delivery technology
Automation is one pillar of DevOps, not the whole of it. Its purpose is to make the right thing the easy thing: repeatable, fast and low-risk. Automating a broken process simply produces failures faster, so simplify first, then automate. Version control as the single source of truth for code, configuration and documentation; reviewable source definitions should be traceable.
399 words, about 2 min03Measurement, reliability and learning signals
Measurement exists to support decisions, expose bottlenecks and verify improvement. Metrics used to rank or punish individuals get gamed and destroyed - Goodhart's Law: when a measure becomes a target, it ceases to be a good measure. Prefer small sets of outcome-oriented, transparent metrics shared openly across teams. Delivery metrics and their version : the historical four-key model described deployment frequency, change lead time, change failure rate and service restoration.
497 words, about 2 min04Feedback and continuous improvement
Sharing, feedback and continuous improvement are the learning half of DevOps. The second way amplifies feedback from right to left - from production, customers and monitoring back to development - so problems are found and fixed quickly. The third way builds a culture of continual experimentation, where taking risks and learning from failure is expected, and where knowledge is deliberately pushed into the organisation. Feedback loops : automated test results, monitoring and alerting, user telemetry, incident reviews, customer feedback, and short release cycles that make feedback cheap.
390 words, about 2 min