I85PREP
⌘ K
DOF study materials
DOF study resources

DOF practice questions

One question at a time. Build your DOF understanding.

First 50 of 190 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1DevOps adoption, culture and delivery flow

What is the primary goal of DevOps?

  1. To replace all manual processes with automation
  2. To enable faster, more reliable delivery of value to customers Correct answer.
  3. To eliminate the operations team
  4. To reduce software development costs

Explanation

DevOps aims to enable organizations to deliver value to customers faster and more reliably by breaking down silos between development and operations teams.

Question 2DevOps adoption, culture and delivery flow

What does the First Way of DevOps focus on?

  1. Amplifying feedback loops
  2. Fast flow from development to operations to customer Correct answer.
  3. Continuous experimentation and learning
  4. Blameless postmortems

Explanation

The First Way emphasizes fast and smooth flow of work from Development through Operations to the customer, minimizing handoff delays and optimizing the whole system.

Question 3DevOps adoption, culture and delivery flow

What does the Second Way of DevOps emphasize?

  1. Optimizing global flow
  2. Amplifying feedback loops Correct answer.
  3. Continuous learning and experimentation
  4. Reducing batch size

Explanation

The Second Way focuses on amplifying feedback loops so that problems are detected and corrected quickly at every stage of the value stream.

Question 4DevOps adoption, culture and delivery flow

What does the Third Way of DevOps address?

  1. Flow from development to operations
  2. Feedback from operations to development
  3. Continuous experimentation and learning from failures Correct answer.
  4. Automation of deployment pipelines

Explanation

The Third Way cultivates a culture of continual experimentation, taking risks and learning from failure, and understanding that repetition and practice build mastery.

Question 5DevOps adoption, culture and delivery flow

What does the acronym CALMS stand for in DevOps?

  1. Culture, Automation, Lean, Measurement, Sharing Correct answer.
  2. Collaboration, Agility, Lean, Metrics, Speed
  3. Culture, Agility, Learning, Management, Sharing
  4. Continuous, Automation, Lean, Metrics, Synchronization

Explanation

CALMS stands for Culture, Automation, Lean, Measurement, and Sharing - a framework used to assess and guide DevOps transformation.

Question 6DevOps adoption, culture and delivery flow

Which CALMS pillar focuses on eliminating manual, error-prone repetitive tasks?

  1. Culture
  2. Automation Correct answer.
  3. Lean
  4. Sharing

Explanation

Automation in CALMS refers to replacing manual, repetitive tasks with automated processes to reduce errors and accelerate delivery.

Question 7DevOps adoption, culture and delivery flow

In the CALMS framework, what does the 'L' (Lean) pillar emphasize?

  1. Limiting work in progress and eliminating waste Correct answer.
  2. Automating the software delivery pipeline
  3. Sharing knowledge between teams
  4. Measuring key business metrics

Explanation

Lean in CALMS emphasizes applying Lean principles such as reducing waste, limiting work-in-progress, and improving flow through the value stream.

Question 8DevOps adoption, culture and delivery flow

What is the purpose of the 'Measurement' pillar in CALMS?

  1. To automate data collection only
  2. To use data to understand the current state and drive improvement decisions Correct answer.
  3. To measure individual developer productivity
  4. To track only production uptime

Explanation

Measurement in CALMS means collecting and analyzing data about the system and processes to understand the current state and make evidence-based improvement decisions.

Question 9DevOps adoption, culture and delivery flow

What does the 'Sharing' pillar of CALMS promote?

  1. Sharing source code with competitors
  2. Open communication, shared tools, and knowledge transfer across teams Correct answer.
  3. Sharing infrastructure costs with cloud providers
  4. Distributing work evenly among team members

Explanation

Sharing in CALMS promotes open communication, collaborative culture, shared tooling, and knowledge transfer between development, operations, and other teams.

Question 10DevOps adoption, culture and delivery flow

What is a blameless postmortem?

  1. A review that identifies the employee responsible for an incident
  2. A process to analyze incidents focusing on systemic causes without assigning personal blame Correct answer.
  3. A legal document released after a service outage
  4. A performance review triggered by production failures

Explanation

A blameless postmortem is an incident review process that focuses on identifying systemic causes and improving processes, rather than blaming individuals.

Question 11DevOps adoption, culture and delivery flow

Why are blameless postmortems important in a DevOps culture?

  1. They protect engineers from disciplinary action for all errors
  2. They encourage transparency and learning from failures without fear Correct answer.
  3. They eliminate all future incidents
  4. They are required for compliance with ISO standards

Explanation

Blameless postmortems create psychological safety, encouraging engineers to be transparent about failures so that the whole organization can learn and prevent recurrence.

Question 12DevOps adoption, culture and delivery flow

What is the concept of 'shift left' in DevOps?

  1. Moving teams from the right side of the office to the left side
  2. Integrating testing and security earlier in the development process Correct answer.
  3. Migrating workloads from on-premises to the cloud
  4. Moving deployment activities from operations to developers

Explanation

'Shift left' means moving quality, testing, and security practices earlier (to the left) in the development pipeline so that defects and vulnerabilities are caught sooner and cost less to fix.

Question 13DevOps adoption, culture and delivery flow

What is 'technical debt' in software development?

  1. The financial cost of software licenses
  2. The accumulated cost of shortcuts and quick fixes that make future development harder Correct answer.
  3. The time developers spend on administrative tasks
  4. The backlog of unresolved bugs

Explanation

Technical debt represents the implied future cost of rework caused by choosing a quick, suboptimal solution now instead of a better approach that would take longer.

Question 14DevOps adoption, culture and delivery flow

What is the concept of 'fail fast' in DevOps?

  1. Deploying software faster even if it has bugs
  2. Detecting and surfacing failures as early as possible so they can be fixed quickly Correct answer.
  3. Automating rollback within milliseconds
  4. Releasing software without testing to gather real-world feedback

Explanation

'Fail fast' means designing systems and processes to detect failures early (e.g., in CI) so they can be corrected quickly before they propagate and become more expensive to fix.

Question 15DevOps adoption, culture and delivery flow

What is the relationship between DevOps and Agile?

  1. DevOps replaces Agile entirely
  2. DevOps extends Agile principles beyond software development to include operations and delivery Correct answer.
  3. Agile is a subset of DevOps practices
  4. They are completely independent methodologies with no overlap

Explanation

DevOps builds on Agile's iterative development principles and extends collaboration and rapid delivery into operations, testing, security, and the full software delivery lifecycle.

Question 16DevOps adoption, culture and delivery flow

What is a 'feedback loop' in DevOps?

  1. A code review process
  2. A mechanism that provides information about the system state back to those who can act on it Correct answer.
  3. A recurring meeting cadence
  4. A loop in automated test scripts

Explanation

A feedback loop is any mechanism that returns information about the current system state - such as monitoring alerts, test results, or customer usage data - to teams who can use it to improve.

Question 17DevOps adoption, culture and delivery flow

What is 'monitoring' in a DevOps context?

  1. Reviewing employee performance
  2. Collecting and analyzing data about systems to detect problems and understand behavior Correct answer.
  3. Monitoring competitor software releases
  4. Reviewing code for security vulnerabilities

Explanation

Monitoring collects and analyzes system metrics, logs, and traces in real time to detect anomalies, understand performance, and enable fast incident response.

Question 18DevOps adoption, culture and delivery flow

What is 'observability' and how does it differ from monitoring?

  1. Observability and monitoring are identical concepts
  2. Monitoring checks known failure modes; observability allows understanding of any system state from external outputs Correct answer.
  3. Observability is monitoring only for cloud-native applications
  4. Observability replaces the need for logging

Explanation

Monitoring tracks known metrics and alerts on predefined thresholds; observability is the degree to which the internal state of a system can be inferred from its external outputs, enabling exploration of unknown unknowns.

Question 19DevOps adoption, culture and delivery flow

What is 'ChatOps'?

  1. Using AI chatbots to replace customer service agents
  2. Integrating tools, automation, and communication into a shared chat platform to enable collaborative operations Correct answer.
  3. A social media strategy for DevOps teams
  4. A method of using chat logs to audit deployments

Explanation

ChatOps brings tools, bots, and automation into a shared messaging platform (e.g., Slack), enabling teams to trigger deployments, view alerts, and collaborate in a shared context.

Question 20DevOps adoption, culture and delivery flow

What is 'site reliability engineering' (SRE)?

  1. A hardware reliability testing methodology
  2. A software engineering approach to operations that applies engineering principles to manage large-scale systems reliably Correct answer.
  3. A certification for network engineers
  4. A process for managing data center physical reliability

Explanation

SRE, pioneered by Google, applies software engineering practices to operations work - using code to automate operational tasks and maintain reliability at scale through objectives like SLOs.

Question 21DevOps adoption, culture and delivery flow

What is a 'service level objective' (SLO)?

  1. A contract with a cloud provider
  2. A measurable target for service reliability, such as 99.9% availability Correct answer.
  3. The maximum acceptable downtime per year
  4. An agreement between development and operations teams on deployment frequency

Explanation

An SLO is a specific measurable reliability target (e.g., 99.9% uptime, <200ms latency at p99) that defines what 'good enough' looks like for a service.

Question 22DevOps adoption, culture and delivery flow

What is an 'error budget' in SRE?

  1. The financial cost allocated for fixing production bugs
  2. The allowed amount of unreliability remaining before an SLO is breached Correct answer.
  3. The number of bugs a team is allowed per sprint
  4. A budget line item for disaster recovery testing

Explanation

An error budget is the acceptable amount of unreliability (1 minus the SLO) over a time window. When the error budget is consumed, new risky deployments stop until reliability is restored.

Question 23DevOps adoption, culture and delivery flow

What is a 'microservices architecture'?

  1. An architecture where one large service handles all application functions
  2. An approach where an application is built as a collection of small, independently deployable services Correct answer.
  3. A method for breaking down monolithic databases
  4. A network architecture using micro data centers

Explanation

Microservices architecture decomposes an application into small, loosely coupled services that can be developed, deployed, and scaled independently.

Question 24DevOps adoption, culture and delivery flow

What is 'shift right' testing in DevOps?

  1. Moving all testing to the end of the pipeline
  2. Testing in production environments to observe real user behavior and system performance Correct answer.
  3. Delaying test automation until after deployment
  4. Outsourcing testing to an external team

Explanation

Shift right testing performs testing in or near production (e.g., chaos engineering, A/B tests, synthetic monitoring) to validate real-world behavior and catch issues that only emerge under real traffic.

Question 25DevOps adoption, culture and delivery flow

What is 'chaos engineering'?

  1. Disorganized project management
  2. Intentionally injecting failures into a system to test its resilience and identify weaknesses Correct answer.
  3. Randomly deploying code without review
  4. A technique for generating randomized test data

Explanation

Chaos engineering deliberately introduces failures (e.g., killing servers, injecting latency) in a controlled way to discover system weaknesses before they cause unplanned outages.

Question 26DevOps adoption, culture and delivery flow

What is 'DevSecOps'?

  1. A security-only version of DevOps for compliance teams
  2. Integrating security practices and tools throughout the DevOps pipeline rather than treating security as a final gate Correct answer.
  3. A framework for securing DevOps tooling from external attacks
  4. A certification program for security engineers

Explanation

DevSecOps integrates security into every stage of the CI/CD pipeline - from code analysis to deployment - making security a shared responsibility rather than a final approval gate.

Question 27DevOps adoption, culture and delivery flow

In DevOps, what is a 'runbook'?

  1. A formal project plan document
  2. A documented set of procedures for operating and troubleshooting a system Correct answer.
  3. A code review checklist
  4. A sprint planning guide

Explanation

A runbook is an operational document containing step-by-step procedures for routine operations, incident response, and troubleshooting of a specific system.

Question 28DevOps adoption, culture and delivery flow

What does 'toil' mean in SRE and DevOps?

  1. All operational work performed by engineers
  2. Manual, repetitive, automatable work that scales linearly with service growth and provides no lasting value Correct answer.
  3. Complex engineering problems that require expert analysis
  4. Work completed during on-call rotations

Explanation

Toil is manual, repetitive, automatable work that scales with the service - if left unaddressed, it grows until it consumes all capacity. SRE teams aim to keep toil below 50% of work time.

Question 29DevOps adoption, culture and delivery flow

What is a 'post-incident review' (PIR)?

  1. A report submitted to regulatory authorities after a security breach
  2. A structured meeting after an incident to analyze what happened, why, and how to prevent recurrence Correct answer.
  3. A performance review triggered by SLA violations
  4. A customer satisfaction survey after a service disruption

Explanation

A post-incident review (synonymous with postmortem) is a structured analysis held after an incident to understand the timeline, contributing factors, and systemic improvements.

Question 30DevOps adoption, culture and delivery flow

What does 'shift left on security' mean in DevSecOps?

  1. Moving the security team's desk to the left side of the office
  2. Integrating security testing and reviews earlier in the software development lifecycle Correct answer.
  3. Reducing the security team's budget
  4. Making developers solely responsible for all security decisions

Explanation

Shifting security left means introducing security practices (static analysis, dependency scanning, threat modeling) early in development rather than at the end, catching vulnerabilities when they are cheapest to fix.

Question 31DevOps adoption, culture and delivery flow

What is 'environment parity' in DevOps?

  1. Having equal numbers of developers and operations staff
  2. Keeping development, staging, and production environments as similar as possible Correct answer.
  3. Ensuring all developers use the same programming language
  4. Running the same number of tests in each environment

Explanation

Environment parity means making development, staging, and production environments as identical as possible, so that software behaves consistently across all stages and 'works on my machine' problems are eliminated.

Question 32DevOps adoption, culture and delivery flow

What is the 'DevOps loop' (infinity loop) diagram meant to represent?

  1. An infinite loop bug in DevOps tooling
  2. The continuous, cyclical relationship between development and operations activities across plan, code, build, test, deploy, operate, monitor, and back to plan Correct answer.
  3. The number of deployment cycles per year
  4. A circular hiring pipeline for DevOps engineers

Explanation

The DevOps infinity loop visually represents the continuous cycle of Dev activities (plan, code, build, test) and Ops activities (deploy, operate, monitor) feeding back into each other continuously.

Question 33DevOps adoption, culture and delivery flow

What is 'observability' composed of (the three pillars)?

  1. Alerts, dashboards, and SLOs
  2. Metrics, logs, and traces Correct answer.
  3. Uptime, throughput, and latency
  4. CI, CD, and monitoring

Explanation

The three pillars of observability are metrics (numeric time-series data), logs (timestamped event records), and traces (request flows across distributed services).

Question 34DevOps adoption, culture and delivery flow

What is a 'service mesh' in microservices architectures?

  1. A spreadsheet tracking all services in a system
  2. A dedicated infrastructure layer that handles service-to-service communication, providing discovery, load balancing, and observability Correct answer.
  3. A mesh network topology for data centers
  4. A testing framework for microservices

Explanation

A service mesh (e.g., Istio, Linkerd) provides a transparent infrastructure layer for inter-service communication - handling load balancing, service discovery, retries, timeouts, and telemetry without changing application code.

Question 35DevOps adoption, culture and delivery flow

What is 'shift right' and how does it complement 'shift left'?

  1. They are opposite strategies that cannot be used together
  2. Shift left catches defects early in development; shift right validates real-world behavior in production - together they provide end-to-end quality coverage Correct answer.
  3. Shift right means moving releases to the right of the calendar
  4. Shift right applies only to security testing

Explanation

Shift left catches issues early through pre-production testing; shift right validates real-world behavior through production testing and monitoring - together they provide comprehensive quality assurance across the full lifecycle.

Question 36DevOps adoption, culture and delivery flow

What is 'continuous improvement' in the context of DevOps?

  1. Increasing the frequency of software releases indefinitely
  2. An ongoing commitment to regularly identify and eliminate waste, inefficiencies, and defects through iterative retrospective cycles Correct answer.
  3. Improving only the deployment pipeline automation
  4. A one-time process improvement initiative after a major incident

Explanation

Continuous improvement (rooted in Kaizen and the Third Way) is a sustained commitment to regularly reflect on and improve processes, tools, and culture in small, incremental steps.

Question 37Automation and safe delivery technology

What is Continuous Delivery (CD)?

  1. Automatically deploying every change to production
  2. Ensuring software can be released to production at any time with manual approval Correct answer.
  3. Running continuous performance testing
  4. Eliminating all manual testing from the pipeline

Explanation

Continuous Delivery ensures that software is always in a releasable state, with deployments to production requiring a deliberate manual approval step.

Question 38Automation and safe delivery technology

What distinguishes Continuous Deployment from Continuous Delivery?

  1. Continuous Deployment requires more manual testing
  2. Continuous Deployment automatically releases every passing build to production Correct answer.
  3. Continuous Delivery is faster than Continuous Deployment
  4. Continuous Deployment only applies to mobile applications

Explanation

In Continuous Deployment, every change that passes automated tests is automatically released to production with no manual approval gate, whereas Continuous Delivery retains a manual approval step.

Question 39Automation and safe delivery technology

What is a deployment pipeline?

  1. A Kubernetes networking configuration
  2. An automated sequence of stages that builds, tests, and deploys software Correct answer.
  3. A project management tool for tracking feature requests
  4. A monitoring dashboard for production systems

Explanation

A deployment pipeline is an automated sequence of stages - build, test, deploy - that takes software from version control to production in a repeatable, reliable way.

Question 40Automation and safe delivery technology

What is the primary goal of automating the deployment pipeline?

  1. To replace all developers with robots
  2. To make releases repeatable, fast, and reliable while reducing manual errors Correct answer.
  3. To avoid the need for software testing
  4. To eliminate the need for version control

Explanation

Automating the deployment pipeline makes releases consistent, faster, and less error-prone by removing manual steps that introduce variability and mistakes.

Question 41Automation and safe delivery technology

What is a 'canary release' deployment strategy?

  1. Releasing software only during off-peak hours
  2. Gradually rolling out a change to a small subset of users before full deployment Correct answer.
  3. Releasing to a replica environment before production
  4. A release strategy used exclusively in financial applications

Explanation

A canary release incrementally exposes a new version to a small percentage of users first, monitoring for issues before gradually expanding to all users.

Question 42Automation and safe delivery technology

What is a 'blue/green deployment'?

  1. Using blue and green teams for security testing
  2. Running two identical production environments and switching traffic between them Correct answer.
  3. Deploying to blue (development) and green (production) environments sequentially
  4. A color-coded incident severity system

Explanation

Blue/green deployment maintains two identical production environments; traffic is switched from the current (blue) to the new (green) version, allowing instant rollback if needed.

Question 43Automation and safe delivery technology

What is 'feature flags' (also called feature toggles)?

  1. Git branch naming conventions for new features
  2. Switches in code that enable or disable features without deploying new code Correct answer.
  3. Metadata tags for features in a product backlog
  4. A/B test configurations stored in a database

Explanation

Feature flags are conditional code switches that allow features to be enabled or disabled at runtime without a new deployment, enabling dark launches, gradual rollouts, and A/B testing.

Question 44Automation and safe delivery technology

What is 'trunk-based development'?

  1. A Git workflow with many long-lived feature branches
  2. A development practice where developers merge small, frequent changes directly to a shared main branch Correct answer.
  3. A release strategy that uses a single production server
  4. A branching model with separate branches for each environment

Explanation

Trunk-based development has all developers committing small, frequent changes directly to a single main branch (trunk), minimizing merge conflicts and enabling continuous integration.

Question 45Automation and safe delivery technology

What is the purpose of automated testing in DevOps?

  1. To eliminate the need for human QA engineers permanently
  2. To provide fast, reliable feedback on code quality with every change Correct answer.
  3. To generate test reports for compliance purposes only
  4. To test only the final production release before launch

Explanation

Automated testing provides rapid, repeatable feedback on whether each code change breaks existing functionality, enabling teams to catch and fix defects early and continuously.

Question 46Automation and safe delivery technology

What is 'continuous testing' in a DevOps pipeline?

  1. Running all tests manually before each release
  2. Executing automated tests at every stage of the pipeline to provide immediate feedback Correct answer.
  3. Testing software only after deployment to production
  4. Performing load tests on a quarterly schedule

Explanation

Continuous testing integrates automated tests at every pipeline stage - unit, integration, acceptance, performance - so every change receives immediate quality feedback.

Question 47Automation and safe delivery technology

What is the main benefit of short-lived feature branches in DevOps?

  1. Developers can work in isolation longer without interference
  2. Shorter branches reduce merge conflicts and integration issues, enabling faster CI Correct answer.
  3. Short branches prevent unauthorized code changes
  4. They allow multiple teams to release independently at any time

Explanation

Short-lived branches are merged frequently, reducing the divergence between branches and minimizing painful merge conflicts - a key enabler of effective continuous integration.

Question 48Automation and safe delivery technology

What is a 'deployment freeze' and when is it used?

  1. A CI/CD pipeline stage that prevents unauthorized deployments
  2. A period during which no changes are deployed to production, typically around high-risk business events Correct answer.
  3. A Docker container isolation technique
  4. A configuration management rollback procedure

Explanation

A deployment freeze (or change freeze) is a deliberate period when deployments to production are halted, typically around major business events (holiday peaks, major launches) to minimize risk.

Question 49Automation and safe delivery technology

What is 'pull request' (PR) and its role in DevOps?

  1. A customer request to pull new features into production
  2. A mechanism for developers to propose, review, and discuss code changes before merging them Correct answer.
  3. A marketing request to pull a software product from the market
  4. A pipeline trigger that pulls the latest build for testing

Explanation

A pull request is a code review mechanism where a developer proposes changes, reviewers inspect and discuss them, and the team decides whether to merge - supporting quality and knowledge sharing.

Question 50Automation and safe delivery technology

What is 'release management' in DevOps?

  1. Managing the marketing campaign for a product release
  2. Planning, scheduling, and coordinating the movement of software releases through deployment environments Correct answer.
  3. Managing release notes and changelogs
  4. Assigning developers to release sprints

Explanation

Release management oversees planning, scheduling, and coordinating the build, test, and deployment of software through environments, ensuring releases are delivered on time and with quality.