Which statement is NOT TRUE?
D
Explanation:
Let’s clarify what these terms mean in DevOps:
Continuous Integration (CI): Developers integrate code into a shared repository frequently (ideally
daily), with each integration automatically verified by tests.
Continuous Delivery (CD): Ensures software is always in a releasable state. Every change can be
deployed to production, but the deployment itself may be a manual decision.
Continuous Deployment: Every change that passes automated tests is automatically deployed to
production, without manual intervention.
Why is D (“Continuous Deployment requires a manual push button”) NOT TRUE?
Because Continuous Deployment is about no manual intervention—once code passes all tests, it’s
automatically pushed live. Manual deployment is a feature of Continuous Delivery, not Continuous
Deployment.
Extract-style reference:
“Continuous Deployment means that every change goes through the pipeline and is automatically
put into production, resulting in many production deployments every day.”
— Accelerate: The Science of Lean Software and DevOps, Jez Humble & Nicole Forsgren
DevOps Foundation v3.6 distinguishes between Continuous Delivery (manual trigger) and
Continuous Deployment (fully automated).
Which of the following is an example of a "shift left" testing strategy?
C
Explanation:
Shift Left Testing means moving testing earlier in the development process, so defects are found
sooner and fixes are cheaper.
Unit testing as part of CI is the classic “shift left” strategy: automated unit tests run with every code
change, catching errors before code moves further down the pipeline.
Testing in production (A) is “shift right.”
Manual testing (B) is typically late-stage and not automated.
Biannual vulnerability assessments (D) are after-the-fact and far from “shift left.”
Extract-style reference:
“Shift left means performing testing activities earlier, for example by including unit tests in the CI
process, reducing costly late-stage defects.”
— DevOps Handbook
PeopleCert Foundation: “Shift left” is a key DevOps testing principle—find issues fast, fix fast, deploy
safely.
What is one of the PRIMARY benefits of Continuous Delivery?
C
Explanation:
Continuous Delivery’s primary benefit is that it reduces the cost, time, and risk of delivering
incremental changes. By keeping software deployable at all times, teams can ship small, low-risk
releases as needed.
A: Prioritizing features over deployability increases risk.
B: Not all releases are deployed immediately; CD keeps them ready.
D: CD doesn’t automate everything—some manual steps may remain, especially in Continuous
Delivery (vs. Continuous Deployment).
Extract-style reference:
“Continuous Delivery reduces deployment pain by ensuring that code is always in a deployable state,
decreasing the cost, time, and risk associated with releases.”
— Continuous Delivery, Jez Humble & David Farley
PeopleCert Syllabus: Highlights CD as a strategy for safer, more efficient business change.
Which of the following DevOps practices encourages conversation driven development, delivery and
support?
B
Explanation:
ChatOps is the DevOps practice of using chat platforms (like Slack, Teams, Mattermost) as the central
interface for communication, collaboration, and even automated deployment or support tasks.
It encourages “conversation-driven development, delivery, and support,” making processes
transparent and collaborative.
Second Way (A) is about feedback loops, but not specifically conversational platforms.
Communication Platforms (C) is a generic term.
VisOps (D) is not a standard DevOps term.
Extract-style reference:
“ChatOps is a collaboration model that connects people, tools, process, and automation into a
transparent workflow. Teams communicate and execute commands from a central chat client.”
— DevOps Handbook
PeopleCert Foundation v3.6: ChatOps promotes rapid feedback and a culture of sharing.
A team has recently introduced their first Kanban board and are saying that they are finding it hard to
focus and are feeling exhausted from context switching. Additionally, the business is complaining
that nothing is being finished and they are yet to receive any of what they asked for.
What do the team need to do?
C
Explanation:
When Kanban teams feel overwhelmed and nothing is getting finished, it’s a sign that too much work
is in progress (WIP).
Work in Progress (WIP) limits are a key Kanban and Lean practice: they restrict how many tasks can
be active at one time, forcing teams to focus, finish, and deliver before starting new work.
Pushing more work (A) or adding more resources (B) worsens the problem.
Unblocking work (D) is helpful, but the core issue is overload.
Extract-style reference:
“WIP limits encourage teams to finish work before starting new tasks, reducing context switching and
enabling better flow and faster delivery.”
— Kanban: Successful Evolutionary Change for Your Technology Business, David J. Anderson
PeopleCert DevOps Foundation: Limiting WIP is essential for effective flow and sustainable pace.
Why are Lean tools and practices critical to DevOps?
D
Explanation:
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.
Learning organizations understand that not embedding learning into the culture of an organization
creates cultural debt.
Which of the following are characteristics of high performing organizations?
C
Explanation:
High-performing organizations embed learning into their culture, which leads to continuous
improvement, innovation, and adaptability.
Employees and leadership committed to learning (option C) is a proven characteristic of high
performance.
Other options—individualism, mandated training, and disincentivized development—are actually
barriers to DevOps success.
Extract-style reference:
“High-performing organizations deliberately invest in learning and development and have leaders
who model and reward learning behaviors.”
— Accelerate: The Science of Lean Software and DevOps, Nicole Forsgren et al.
PeopleCert DevOps Foundation v3.6: The syllabus highlights that a “culture of learning” and
psychological safety are core characteristics of successful DevOps organizations.
The Deming Cycle (Plan-Do-Check-Act) plays a key role in which Lean practice?
D
Explanation:
The Deming Cycle (Plan-Do-Check-Act) is foundational to continuous improvement in Lean, and is
specifically applied in the Improvement Kata practice:
Improvement Kata: A structured routine for continuous, incremental improvement based on
scientific thinking (PDCA).
Value Stream Mapping and Andon cord are Lean practices, but they don’t directly reference PDCA as
the core mechanism.
Extract-style reference:
“The Improvement Kata incorporates the Deming cycle (Plan-Do-Check-Act) to drive small, rapid
cycles of change, helping teams to experiment, learn, and adjust.”
— Toyota Kata, Mike Rother
PeopleCert DevOps Foundation v3.6: Cites PDCA as integral to continuous improvement and
Lean/DevOps adoption.
What is NOT a feature of Safety Culture?
C
Explanation:
Creating Single Points of Failure (SPOFs) is not a feature of Safety Culture—in fact, it’s the opposite.
Safety Culture in DevOps promotes blameless post-mortems, valuing incidents as learning
opportunities, and thanking contributors for uncovering weaknesses.
SPOFs increase risk and discourage experimentation.
Extract-style reference:
“Safety Culture is built on blamelessness, psychological safety, and learning from failure, not
punishment. SPOFs are an anti-pattern that increases fragility.”
— The DevOps Handbook
PeopleCert DevOps Foundation v3.6: Stresses the importance of a safe, collaborative environment
for innovation.
Agile funding can be______
D
Explanation:
Agile funding is flexible and adapts to the iterative, incremental nature of Agile and DevOps projects.
It can be fixed cost for some work, continuous cost for ongoing value streams, and is reviewed
frequently to align with evolving priorities.
All three characteristics are true, so D (“All of the Above”) is correct.
Extract-style reference:
“Agile funding models support continuous review and adaptation, providing the flexibility required
for digital transformation and DevOps ways of working.”
— Project to Product, Mik Kersten
PeopleCert DevOps Foundation v3.6: Advocates funding models that encourage agility,
experimentation, and rapid value delivery.