A DevOps professional needs:

Business skills: Understanding the business context and value.

Technical skills: Automation, coding, cloud, infrastructure.

Core (soft) skills: Collaboration, communication, empathy, learning.

Self-management: Time, priorities, feedback.

Other options miss the full blend or focus too much on tech or process.

Extract-style reference:

“DevOps success requires a blend of business, technical, and core (soft) skills, as well as the ability to self-manage and continuously learn.”

— DevOps Handbook; Accelerate

PeopleCert DevOps Foundation v3.6: Holistic skillsets are emphasized for cross-functional teams.

The Third Way in DevOps emphasizes continual learning and experimentation . One of the most effective resilience-building practices in this category is chaos engineering or deliberate fault injection. This involves introducing controlled failures into systems—such as shutting down services, simulating network latency, or exhausting resources—to test the organization’s recovery capability in realistic scenarios.

By practicing recovery under controlled conditions, teams identify weaknesses in monitoring, automation, documentation, and communication before a real incident occurs. This improves Mean Time to Recovery (MTTR) and overall system resilience.

Option A (constraint analysis) relates to the First Way (flow optimization). Option C focuses on feedback loops ( Second Way ). Option D (adding redundancy) is a possible improvement but does not inherently practice and improve operational recovery skills in the same way as deliberate fault injection.

Therefore, B is the most appropriate Third Way principle for improving resilience in this scenario.

Coercive communication (using force or threat) is not a transformational leadership dimension.

Transformational leaders:

Inspire vision

Recognize contributions

Stimulate new ideas (intellectual stimulation)

Foster intrinsic motivation

Extract-style reference:

“Transformational leadership builds trust, motivates by vision, provides intellectual stimulation, and recognizes individuals—not by coercion, but by inspiration.”

— Transformational Leadership (James Burns), PeopleCert DevOps Foundation v3.6

According to PeopleCert DevOps Foundation v3.6, the five primary values that guide successful DevOps adoption are summarized in the CALMS framework: Culture, Automation, Lean, Measurement, and Sharing .

Culture focuses on breaking down silos, encouraging trust, and promoting collaboration between development, operations, security, QA, and business teams.

Automation is essential for speeding up delivery, reducing manual errors, and ensuring repeatability across the software delivery lifecycle.

Lean emphasizes the elimination of waste, limiting work in progress (WIP), and improving flow.

Measurement means using metrics and data to inform decisions, identify bottlenecks, and drive continuous improvement.

Sharing fosters transparency, knowledge transfer, and a unified approach to goals and problem-solving.

Option A replaces automation and lean principles with softer collaboration aspects, which are important but not recognized as the formal value set. Option C replaces “Measurement” with “Metrics,” which is only a part of measurement. Option D substitutes “Accountability” for “Automation,” which is not part of the CALMS model.

Therefore, the official correct set of values per the DevOps Foundation syllabus is B .

The “Three Ways” are foundational principles in DevOps:

The First Way focuses on increasing the flow of work from left (development) to right (operations). It is about optimizing the entire system for fast delivery, limiting bottlenecks, and enabling a rapid flow of features and fixes to customers.

The Second Way is about amplifying feedback loops so corrections can be made early.

The Third Way emphasizes continual learning and experimentation.

Extract-style reference:

“The First Way emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department. The goal is to maximize the flow of work (value) from Development to Operations to the customer.”

— Gene Kim, The Phoenix Project / DevOps Handbook

PeopleCert DevOps Foundation v3.6 highlights this in the section on "Principles and Practices," emphasizing The First Way as critical to accelerating flow.

Epics delivered is a software/process metric , not a business performance metric.

Business performance metrics include financial and market indicators: earnings, cashflow, market share, revenue growth.

Why not the others?

Earnings, Cashflow, Marketshare: Directly tied to business health.

Extract-style reference:

“Business performance metrics focus on outcomes such as earnings, cashflow, and marketshare. Agile metrics like epics delivered measure team output, not business value.”

— Project to Product , Mik Kersten

PeopleCert DevOps Foundation v3.6: Distinguishes business impact from process metrics.

One of the core DevOps values is aligning IT efforts with business objectives—understanding the business “why.” The Foundation syllabus highlights the need for IT to understand the organization's purpose, cause, and belief. Without this, IT can’t effectively support value delivery or drive digital transformation. Understanding the organizational “why” connects daily activities to strategic objectives, a key DevOps mindset.

Change fatigue occurs when employees experience too many changes without clear purpose or connection to business value. The most effective way to reduce resistance is to ensure that DevOps adoption is aligned with strategic business goals and clearly demonstrates how it supports organizational priorities.

When teams see the direct business impact of their work—such as improved customer experience, faster delivery of products, or increased competitiveness—they are more likely to embrace change.

Options A , B , and C may have short-term benefits but do not address the underlying need for strategic alignment and purpose.

Thus, D is the most effective way to minimize change fatigue during DevOps introduction.

According to PeopleCert DevOps Foundation v3.6, the Second Way of DevOps focuses on creating and amplifying feedback loops . The primary purpose of shortening these loops is to accelerate the flow of work and information between all stages of the delivery pipeline, especially between Development and Operations.

When feedback loops are short, defects, performance issues, and risks can be identified and resolved earlier in the process, preventing costly delays and large-scale rework. This supports faster, safer releases and improves the organization’s responsiveness to customer needs.

While A (learning) and D (knowledge sharing) are important benefits of feedback loops, they are secondary outcomes. The main, direct effect is improving flow efficiency —ensuring that handoffs between Dev and Ops happen smoothly, quickly, and with higher quality.

Option C (value stream mapping) is a useful Lean practice to identify delays and bottlenecks, but it is a diagnostic tool , not the primary improvement gained from shortening feedback loops.

Thus, the correct answer is B —shortened feedback loops primarily improve IT performance by ensuring faster flow between Development and Operations.

Lean tools and practices are foundational to DevOps because they help organizations systematically identify and eliminate waste, optimize value delivery, and continuously improve processes.

Lean thinking focuses on value stream mapping, reducing delays, bottlenecks, over-processing, handoffs, rework, and unnecessary tasks—core to making DevOps successful.

Option D, “They help identify waste and assist in the creation of improvement practices,” perfectly captures this focus.

Extract-style reference:

“Lean enables teams to identify value and non-value-added activities and to use continuous improvement techniques such as Kaizen, value stream mapping, and removing waste.”

— DevOps Handbook

PeopleCert DevOps Foundation v3.6 : Lean tools like Value Stream Mapping, 5S, and Kaizen are cited as critical enablers for optimizing the flow and improving IT and business alignment.