I85PREP
⌘ K
DevOps Foundation study materials
DevOps Foundation study resources

DevOps Foundation practice questions

One question at a time. Build your DevOps Foundation understanding.

First 50 of 200 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 Introduction and Purpose

Which description best captures DevOps as it is generally defined?

  1. A culture and set of practices that speed delivery through collaboration and automation Correct answer.
  2. A job title for engineers who are responsible for both writing code and operating production systems
  3. A software product that automatically provisions servers, networks, and storage for development teams
  4. A compliance framework that audits every IT change before it can be released to customers

Explanation

DevOps is best understood as a cultural and professional movement that combines practices and tools to improve delivery speed and reliability. It is not a product, a single job title, or an audit framework.

Question 2DevOps Introduction and Purpose

What is the primary purpose of adopting DevOps?

  1. To remove the operations function so that developers can manage production without specialized skills
  2. To maximize the number of features shipped regardless of stability, security, or customer impact
  3. To replace agile planning with a single annual release process controlled by change managers
  4. To deliver software faster and more reliably through collaboration and automation Correct answer.

Explanation

The core purpose is to improve the flow of value from development to operations and customers. Faster delivery must be paired with reliability, quality, and feedback rather than volume alone.

Question 3DevOps Introduction and Purpose

In the term DevOps, what do Dev and Ops most directly represent?

  1. The design and optimization phases of a project, before any code is written or deployed
  2. Software development and IT operations across the service lifecycle Correct answer.
  3. Devices and operating systems that are listed in an infrastructure inventory
  4. Development and operations as two separate departments that must remain independent of each other

Explanation

DevOps combines software development and IT operations work across the service lifecycle. The term highlights collaboration between these functions rather than keeping them as isolated departments.

Question 4DevOps Introduction and Purpose

The CALMS model is often used to describe the main dimensions of DevOps adoption. What does CALMS stand for?

  1. Culture, automation, lean, measurement, and sharing Correct answer.
  2. Culture, agility, lean, measurement, and systems thinking
  3. Culture, automation, leadership, metrics, and security
  4. Collaboration, automation, lean, monitoring, and scaling

Explanation

CALMS is a commonly used summary of DevOps adoption dimensions: culture, automation, lean, measurement, and sharing. It emphasizes that DevOps is broader than tooling alone.

Question 5DevOps Introduction and Purpose

Why does DevOps emphasize breaking down silos between development and operations?

  1. Silos guarantee that security controls are applied consistently across every team and service
  2. Silos reduce the need for automated testing by separating quality responsibilities
  3. Silos create handoff delays and conflicting goals that reduce flow Correct answer.
  4. Silos make it easier to hide production incidents from customers and auditors

Explanation

Silos create queues, handoffs, and local goals that can conflict with end-to-end delivery. DevOps seeks shared responsibility and smoother flow across the lifecycle.

Question 6DevOps Introduction and Purpose

Which practice is most closely associated with DevOps and involves integrating code changes frequently into a shared mainline?

  1. Continuous integration Correct answer.
  2. Outsourcing operations to a vendor
  3. Manual quarterly release approval
  4. Freezing all code changes after testing

Explanation

Continuous integration is the practice of frequently merging code changes into a shared mainline and validating them with automated builds and tests. It helps teams detect integration problems early.

Question 7DevOps Introduction and Purpose

What is the main purpose of a blameless postmortem?

  1. To satisfy auditors by documenting that no production changes occurred during the outage
  2. To identify and punish the individual who made the mistake so that others avoid similar actions
  3. To prove that the incident was caused by operations rather than by development decisions
  4. To learn from an incident by focusing on systemic causes and preventing recurrence Correct answer.

Explanation

A blameless postmortem examines systemic causes such as process gaps, tooling, and safeguards. The goal is organizational learning and prevention, not punishment.

Question 8DevOps Introduction and Purpose

Which statement best reflects the relationship between DevOps and tools?

  1. DevOps requires replacing all existing tools with open-source alternatives before any other change
  2. Tools are irrelevant to DevOps and should not be discussed when planning a transformation
  3. Tools enable DevOps practices, but culture and process change are also essential Correct answer.
  4. Adopting a modern CI/CD tool is sufficient for an organization to become a DevOps organization

Explanation

Tools support automation and consistency, but DevOps also depends on culture, collaboration, and process improvement. Tool adoption alone does not change how teams work together.

Question 9DevOps Introduction and Purpose

The Three Ways are a set of principles often used to explain DevOps. What are they?

  1. Speed, cost, and quality as the three balanced delivery outcomes
  2. Culture, automation, and measurement as the three DevOps pillars
  3. Flow, feedback, and continual learning and experimentation Correct answer.
  4. Planning, building, and running software in separate organizational stages

Explanation

The Three Ways describe flow from development to operations, amplified feedback loops, and a culture of continual experimentation and learning. They are principles for improving delivery systems.

Question 10DevOps Introduction and Purpose

A team reduces batch sizes and limits work in progress so changes move smoothly from development to operations. Which of the Three Ways does this most directly reflect?

  1. The Third Way, because it encourages continual experimentation and learning
  2. The First Way, because it optimizes flow from left to right Correct answer.
  3. The Second Way, because it amplifies feedback from operations back to development
  4. None of the Three Ways, because it concerns only project planning and budgeting

Explanation

The First Way focuses on systems thinking and optimizing flow from left to right across the value stream. Reducing batch sizes and limiting work in progress support that flow.

Question 11DevOps Introduction and Purpose

Shortening feedback loops so developers learn quickly about production issues is an example of which principle?

  1. The First Way, because it increases deployment batch size and utilization
  2. The Second Way, because it amplifies feedback from right to left Correct answer.
  3. The CALMS principle of sharing, because it transfers ownership to customers
  4. The Third Way, because it removes all process documentation and controls

Explanation

The Second Way is about amplifying feedback from right to left so problems are detected and corrected quickly. Shorter feedback loops let development respond to production signals.

Question 12DevOps Introduction and Purpose

What does the Third Way emphasize?

  1. A culture of continual experimentation, learning, and improvement Correct answer.
  2. Maximizing utilization of every individual and team to one hundred percent
  3. Standardizing one toolchain across the entire organization and all product teams
  4. Creating a single operations team that approves every change before release

Explanation

The Third Way emphasizes continual experimentation, learning from experience, and improving both the work and the way work is done. It supports resilience and innovation.

Question 13DevOps Introduction and Purpose

Why is automation a core element of DevOps?

  1. It guarantees that security vulnerabilities will never reach production environments
  2. It reduces manual error and makes repetitive delivery steps faster and more consistent Correct answer.
  3. It allows teams to skip testing because automated machines are always correct
  4. It removes the need for any human decision-making in software delivery and operations

Explanation

Automation improves speed, repeatability, and consistency while reducing manual errors in repetitive tasks. It frees people to focus on judgment and improvement.

Question 14DevOps Introduction and Purpose

What is the main purpose of value stream mapping in a DevOps context?

  1. To visualize work flow and find delays from idea to customer Correct answer.
  2. To document the organizational chart for compliance and audit purposes
  3. To replace all automated pipelines with manual approval steps
  4. To assign blame for delivery delays to the department that caused them

Explanation

Value stream mapping visualizes the steps and wait times from idea to customer. It helps teams find bottlenecks, waste, and opportunities to improve flow.

Question 15DevOps Introduction and Purpose

How does DevOps relate to Agile?

  1. DevOps and Agile are unrelated because Agile is only suitable for small startups
  2. DevOps extends Agile principles into delivery and operations for end-to-end flow Correct answer.
  3. DevOps is a subset of Agile that applies only to automated software testing activities
  4. DevOps replaces Agile by removing planning ceremonies and iterative development practices

Explanation

Agile emphasizes iterative development and customer feedback, while DevOps extends those ideas into delivery, operations, and end-to-end flow. The two are complementary rather than competing.

Question 16DevOps Introduction and Purpose

What does shift-left mean in a DevOps context?

  1. Performing testing, security, and quality checks earlier in the lifecycle Correct answer.
  2. Delaying testing until after deployment so teams can gather real user feedback
  3. Moving all production servers to the left side of the data center for efficiency
  4. Transferring operations work to developers without providing training or support

Explanation

Shift-left means moving quality, security, and testing activities earlier in the lifecycle. Finding problems earlier usually reduces cost and rework.

Question 17DevOps Introduction and Purpose

Which set of measures is commonly used to assess software delivery performance in DevOps research?

  1. Deployment frequency, lead time for changes, change failure rate, and time to restore Correct answer.
  2. Lines of code, number of servers, ticket volume, meeting hours, and office utilization
  3. Story points, velocity, burn-down rate, sprint count, and planning poker scores
  4. Employee utilization, budget variance, office space, headcount, and manager span

Explanation

The DORA research identifies four key delivery measures: deployment frequency, lead time for changes, change failure rate, and time to restore service. These balance speed with stability.

Question 18DevOps Introduction and Purpose

A business wants faster response to customer needs and fewer failed releases. How does DevOps primarily contribute?

  1. By preventing developers from communicating with operations to reduce conflicting requests
  2. By standardizing on a single vendor for all software and infrastructure purchases
  3. By improving collaboration and automation so changes reach customers faster Correct answer.
  4. By increasing the number of approval gates that each release must pass before deployment

Explanation

DevOps improves collaboration and automation across the delivery lifecycle, which helps changes reach customers faster and with fewer failures. That supports responsiveness to customer needs.

Question 19DevOps Introduction and Purpose

Which statement is a common misconception about DevOps?

  1. DevOps encourages continuous improvement through feedback and learning
  2. DevOps involves collaboration between development and operations teams
  3. DevOps uses automation to improve the speed and consistency of delivery
  4. DevOps means eliminating the operations function entirely Correct answer.

Explanation

A common misconception is that DevOps removes operations or makes developers do all operations work. In practice, operations skills remain valuable and often evolve into platform, reliability, or SRE roles.

Question 20DevOps Introduction and Purpose

Why do cross-functional product teams support DevOps goals?

  1. They ensure that each function works in isolation on separate goals and priorities
  2. They remove the need for shared standards, platforms, or common engineering practices
  3. They make it easier to hand off work sequentially between specialized departments
  4. They bring together skills to build and run a service with shared ownership Correct answer.

Explanation

Cross-functional teams bring development, operations, and related skills together around a service. Shared ownership helps teams build, run, and improve the service with end-to-end accountability.

Question 21DevOps Introduction and Purpose

How does Conway's Law help explain why DevOps transformations often include organizational change?

  1. Systems mirror organizational communication structures, so silos tend to produce fragmented systems Correct answer.
  2. Software architecture determines team structure, so teams cannot change until systems are rewritten
  3. Communication structures are irrelevant to software design quality and delivery performance
  4. Organizations always adopt the newest tools before changing team structure or communication paths

Explanation

Conway's Law observes that systems tend to reflect the communication structures of the organization that builds them. Siloed teams can therefore produce fragmented architectures and slow handoffs, which is why DevOps efforts often include team topology changes.

Question 22DevOps Introduction and Purpose

How is DevOps different from continuous delivery?

  1. Continuous delivery is a cultural movement, while DevOps is only an automated deployment pipeline
  2. DevOps applies only to operations, while continuous delivery applies only to development teams
  3. Continuous delivery keeps software releasable; DevOps is a broader lifecycle culture and practice Correct answer.
  4. They are identical terms with no meaningful difference in scope, culture, or practice

Explanation

Continuous delivery is a practice discipline for keeping software in a releasable state through automated build, test, and deployment pipelines. DevOps is broader, encompassing culture, collaboration, measurement, and operations across the lifecycle.

Question 23DevOps Introduction and Purpose

Why is DevOps often treated as an enabler of digital transformation?

  1. It focuses exclusively on reducing software licensing costs across the enterprise
  2. It replaces the need for business strategy with automated tooling and pipelines
  3. It helps organizations deliver digital services faster and more reliably Correct answer.
  4. It guarantees that every digital initiative will succeed without risk or failure

Explanation

DevOps supports digital transformation by improving how quickly and reliably organizations can deliver digital services and learn from customer feedback. It is an enabler, not a guarantee of business success.

Question 24DevOps Introduction and Purpose

An organization installs a modern CI/CD pipeline but keeps separate development and operations teams with blame-based incident reviews. What is the most likely outcome?

  1. Incident reviews will become blameless because the pipeline records detailed logs
  2. The pipeline will automatically create cross-team collaboration and shared ownership
  3. Local delivery may improve, but silos and blame will limit flow and learning Correct answer.
  4. The organization will achieve DevOps maturity because tooling is the main requirement

Explanation

Tooling can improve local deployment mechanics, but DevOps outcomes depend on collaboration, shared ownership, and learning. A blame culture and persistent silos will still constrain flow and feedback.

Question 25DevOps Introduction and Purpose

Why is deployment frequency alone an incomplete measure of DevOps success?

  1. It is only relevant to organizations that do not use automation or CI/CD pipelines
  2. It directly measures customer satisfaction and revenue generation for the business
  3. It may encourage speed over stability unless balanced with quality measures Correct answer.
  4. It is impossible to measure accurately in any software organization of any size

Explanation

Deployment frequency measures speed, but high frequency without stability can harm customers. A balanced view includes lead time, change failure rate, and recovery time.

Question 26DevOps Introduction and Purpose

The modern DevOps movement is generally traced to which of the following origins?

  1. The signing of the Agile Manifesto by seventeen practitioners in 2001
  2. The publication of the ITIL service management framework in 2007
  3. A practitioner-organized conference held in Ghent, Belgium, in 2009 Correct answer.
  4. A vendor white paper on agile software development published in 2001

Explanation

DevOps as a named movement grew out of DevOpsDays, a practitioner conference held in Ghent, Belgium, in 2009 and organized by Patrick Debois, where the term gained wide currency. It emerged from practitioner experience of friction between development and operations rather than from a formal standard or vendor publication.

Question 27DevOps Introduction and Purpose

The acronym CALMS is often used to summarize the foundations of DevOps. Which expansion is correct?

  1. Culture, Automation, Lean, Measurement, Sharing Correct answer.
  2. Culture, Agile, Lean, Metrics, Scrum
  3. Culture, Automation, Lean, Monitoring, Security
  4. Collaboration, Automation, Lean, Measurement, Standardization

Explanation

CALMS stands for Culture, Automation, Lean, Measurement and Sharing, and is used as a checklist of the cultural and organizational pillars that support DevOps adoption. The framework deliberately places culture first, reflecting that tooling alone does not produce the required change.

Question 28DevOps Introduction and Purpose

Which phrase captures the DevOps ownership model in which the team that writes a service is also accountable for running it in production?

  1. Throw it over the wall
  2. Design for operations
  3. You build it, you run it Correct answer.
  4. Run to failure

Explanation

The phrase 'you build it, you run it', popularized at Amazon, expresses shared ownership: the team that develops a service also carries operational responsibility for it. This aligns development decisions with production outcomes and shortens the feedback path after release.

Question 29DevOps Introduction and Purpose

In a traditional setup, developers are rewarded for delivering changes quickly while operations staff are rewarded for keeping systems stable. What is the most likely result of this arrangement?

  1. Conflicting goals that push changes back and forth across the team boundary Correct answer.
  2. Operations gains more influence over design decisions than development
  3. Deployment frequency rises without any trade-off in reliability
  4. Both groups naturally converge on the same release priorities

Explanation

When one group is measured on speed of change and the other on stability, each is rationally motivated to block the other's objectives, producing the friction often called the wall of confusion. DevOps addresses this by aligning measures and ownership so both speed and stability are shared outcomes.

Question 30DevOps Introduction and Purpose

A product group wants each of its services to be deployable on its own schedule without coordinating a release window across the whole system. Which architectural property matters most?

  1. A monolithic build that compiles all components together
  2. Loose coupling between services with well-defined interfaces Correct answer.
  3. A single shared database owned collectively by every service
  4. A fixed quarterly release train covering the entire platform

Explanation

Independent deployability depends on loose coupling: services interact through stable, well-defined contracts so a change to one does not force coordinated release of others. Tightly shared state or a single build artifact reintroduces the coupling that forces synchronized releases.

Question 31DevOps Introduction and Purpose

What is the primary purpose of an internal platform team in a DevOps-aligned organization?

  1. To provide self-service capabilities that lower the cognitive load on product teams Correct answer.
  2. To take over all deployment and release work so that product teams can stay focused purely on writing code
  3. To enforce manual approval gates before every production change is allowed to proceed
  4. To centralize all operational incident response into a single specialist group

Explanation

A platform team treats internal developers as customers and offers self-service build, deployment and observability capabilities, so product teams can deliver and operate their own services without becoming infrastructure specialists. The goal is to reduce cognitive load while keeping ownership with the product team.

Question 32DevOps Introduction and Purpose

In a regulated enterprise, a change advisory board reviews every production deployment manually, which delays releases by days. Which approach best aligns with DevOps while keeping appropriate control?

  1. Automate low-risk standard changes with logged evidence and keep manual review for high-risk changes Correct answer.
  2. Move the board's reviews to after deployment so that releases are never blocked by the approval process
  3. Route every deployment through the full change board but require developers to submit their requests much further in advance
  4. Eliminate the change process entirely and rely on the professional judgement of the developers involved

Explanation

DevOps-compatible governance classifies changes by risk: standard, low-risk changes are pre-approved and executed automatically with an auditable trail, while high-risk changes retain manual scrutiny. This preserves control and evidence while removing queues from the majority of routine deployments.

Question 33DevOps Introduction and Purpose

How does DevOps extend the value stream beyond the moment code is deployed?

  1. It extends only as far as documenting the release in the change log
  2. It stops at deployment because operations takes ownership from that point onward
  3. It continues through to the customer's use of the service and the resulting feedback Correct answer.
  4. It replaces customer feedback with internal service-level targets

Explanation

DevOps treats the value stream as running from an idea through to the customer's actual experience, so post-deployment usage and feedback are part of the system being optimized. Feedback from real use informs the next change, closing the loop rather than ending it at release.

Question 34DevOps Introduction and Purpose

Why do long-running DevOps transformations often require changes to an organization's funding model?

  1. Project-based funding produces short-lived teams and handoffs that undermine durable product ownership Correct answer.
  2. Funding models determine which continuous integration tools an organization is permitted to purchase and support
  3. Annual budgets remove the need for product managers to prioritize work across teams
  4. Central budgets make it impossible to measure deployment frequency or lead time for changes

Explanation

Project-based funding creates temporary teams that disband at the end of a project, forcing knowledge transfer, rebuilds and handoffs. Sustained DevOps performance depends on long-lived teams that keep ownership of a service and improve it continuously, which generally requires funding products rather than projects.

Question 35Culture and Behavior

What is the primary purpose of a blameless postmortem?

  1. To record which engineer was on call when the failure began
  2. To learn how the system allowed the failure to happen Correct answer.
  3. To document the outage cost for the finance team
  4. To assign ownership of the remediation budget

Explanation

A blameless postmortem treats a failure as a property of the system - its tooling, safeguards, and processes - rather than of an individual, so the team can find and fix the conditions that allowed it. It assumes people act with good intent given the information available to them at the time.

Question 36Culture and Behavior

Ron Westrum classified organizational cultures into three types. Which trio is correct?

  1. Generative, bureaucratic, and pathological Correct answer.
  2. Agile, waterfall, and hybrid
  3. Open, closed, and matrixed
  4. Innovative, stable, and reactive

Explanation

Westrum's research on information flow in safety-critical industries described pathological (power-oriented), bureaucratic (rule-oriented), and generative (performance-oriented) cultures. Generative cultures respond well to bad news and are associated with stronger software delivery performance.

Question 37Culture and Behavior

In the CAMS model often used to describe DevOps, what does the 'C' represent?

  1. Continuous integration
  2. Collaboration
  3. Compliance
  4. Culture Correct answer.

Explanation

CAMS stands for Culture, Automation, Measurement, and Sharing. It is a reminder that DevOps outcomes depend first on how people work together, with automation and metrics supporting that culture rather than replacing it.

Question 38Culture and Behavior

A team with high psychological safety is one where members can:

  1. operate without any management supervision or performance reviews
  2. be shielded from any responsibility for their own mistakes
  3. speak up and admit mistakes without fear of punishment Correct answer.
  4. avoid disagreement by keeping their opinions private

Explanation

Psychological safety is a shared belief that interpersonal risk-taking - asking questions, admitting error, challenging a decision - will not lead to humiliation or punishment. It is about how people expect to be treated when they speak up, not about the absence of management or standards.

Question 39Culture and Behavior

What does the principle 'you build it, you run it' imply?

  1. Every engineer must be available on call at all times
  2. Developers hand their code to a separate operations group
  3. Operations engineers write the application code
  4. The team that builds a service also operates it in production Correct answer.

Explanation

The principle gives the producing team operational responsibility for its service, so feedback from production reaches the people able to change the design. It does not require round-the-clock individual availability, which is managed through sustainable, shared on-call rotas.

Question 40Culture and Behavior

Which silo is DevOps culture most directly concerned with breaking down?

  1. The boundary between the company and its customers
  2. The separation between permanent and contract staff
  3. The divide between development and operations teams Correct answer.
  4. The gap between junior and senior engineers

Explanation

DevOps emerged partly in response to the wall of confusion between development, rewarded for change, and operations, rewarded for stability. Shared goals, cross-functional teams, and joint ownership of production reduce that divide.

Question 41Culture and Behavior

Why do DevOps organizations favor documentation kept in a shared, searchable place?

  1. It keeps knowledge from being locked inside individuals Correct answer.
  2. It removes the need for any verbal communication
  3. It replaces the need for code review and testing
  4. It lets managers audit how each engineer spends time

Explanation

Shared, searchable documentation makes knowledge a team asset rather than a personal one, which speeds onboarding, reduces bus factor, and lets people solve problems without waiting for one expert. It supplements conversation and engineering controls; it does not replace them.

Question 42Culture and Behavior

In site reliability practice, 'toil' refers to work that is:

  1. highly creative and performed only once
  2. carried out exclusively by automated tooling
  3. manual, repetitive, and without lasting value Correct answer.
  4. reserved for senior engineers during incidents

Explanation

Toil is manual, repetitive, automatable work that scales linearly with service growth and produces no enduring improvement. Many SRE teams cap toil at roughly half of an engineer's time so that engineering work on reliability continues.

Question 43Culture and Behavior

An incident review opens with a manager asking, 'Who pushed the bad change?' What is the most useful facilitation response?

  1. Postpone the review until the manager has left
  2. Answer the question so the meeting can proceed
  3. Add the engineer's name to the action items
  4. Redirect to how the change reached production Correct answer.

Explanation

Blameless reviews ask how the system allowed an action to cause harm rather than who performed it, because naming individuals stops people volunteering the detail needed to find causes. The facilitator should steer toward conditions, safeguards, and detection gaps.

Question 44Culture and Behavior

Which pattern of behavior is typical of a pathological culture?

  1. Messengers who bring bad news are punished or ignored Correct answer.
  2. Teams cooperate across boundaries and share bad news early
  3. New ideas are welcomed and tested with small experiments
  4. Rules are followed carefully and every deviation is documented

Explanation

Pathological cultures are power-oriented: information is withheld for political advantage and people who report problems are blamed, so leaders lose sight of risk. Westrum found this pattern predicts poorer safety and delivery outcomes.

Question 45Culture and Behavior

Which leader behavior most reliably raises psychological safety during incident reviews?

  1. Reviewing the recording of the incident call with the team
  2. Admitting their own mistakes and inviting challenge openly Correct answer.
  3. Setting a target of zero incidents for the coming quarter
  4. Announcing that nobody will be disciplined whatever happened

Explanation

Psychological safety grows when people observe that speaking up is safe in practice, and leaders modeling fallibility is the strongest signal of that norm. Declarations matter less than demonstrated behavior, and zero-incident targets tend to suppress reporting.

Question 46Culture and Behavior

A leader wants a cross-functional product team to act autonomously. What is the best action?

  1. Assign tasks daily so priorities stay aligned
  2. Agree on clear outcomes and let the team choose the how Correct answer.
  3. Approve each deployment the team wants to make
  4. Keep decision rights with the platform architecture group

Explanation

Autonomy means the team owns decisions about how to reach an agreed outcome, while leaders set direction and guardrails. Approval bottlenecks and daily task assignment recreate the dependency that autonomy was meant to remove.

Question 47Culture and Behavior

A department rewards teams that report zero production incidents. What is the likely effect?

  1. Incident counts fall because teams fix problems early
  2. Postmortems become more candid and frequent
  3. Engineers gain more time for automation work
  4. Failures are concealed and learning is lost Correct answer.

Explanation

Rewarding the absence of reported incidents rewards silence rather than safety, so people delay or hide disclosure and the organization loses the data it needs to improve. It is better to reward fast detection, honest reporting, and effective learning.

Question 48Culture and Behavior

An organization wants to adopt DevOps culture and is planning its first step. Which step is most likely to succeed?

  1. Run a volunteer pilot with visible leadership support Correct answer.
  2. Buy a CI/CD tool suite and require all teams to use it
  3. Rewrite the process handbook before any team changes
  4. Announce a reorganization of development and operations

Explanation

Culture changes through visible, low-risk experiments that generate evidence and local ownership, then spread through peer influence. Tool mandates and top-down restructuring without changed day-to-day behavior tend to produce compliance rather than new norms.

Question 49Culture and Behavior

Which change most shortens the feedback loop between a service and its development team?

  1. Move from weekly to monthly release meetings
  2. Add a change advisory board to review each deploy
  3. Give the team production dashboards and direct alerts Correct answer.
  4. Route all production alerts to a central service desk

Explanation

The team learns fastest when production signals reach the people who can act on them, without intermediaries or delay. Centralized routing and extra approval layers add latency between the event and the response.

Question 50Culture and Behavior

How does a blameless culture relate to individual accountability?

  1. It asks for honesty and learning, not a fault-free record Correct answer.
  2. It holds individuals accountable only when errors are repeated
  3. It removes accountability because outcomes are always systemic
  4. It assigns accountability to the manager of the on-call engineer

Explanation

Blamelessness concerns how the organization responds to error, not whether people are responsible for their work; just-culture models distinguish human error, at-risk behavior, and recklessness. The aim is to remove fear while keeping accountability for learning, disclosure, and safe practice.