Free PeopleCert DEVOPS Institute DevOps Foundation v3.6 Exam DevOps-Foundation Exam Questions

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.

When developers practice agile but operations is slow to deploy, it means IT Operations have not kept pace---classic ''left behind'' scenario. DevOps aims to align development and operations, breaking down barriers and enabling faster, safer, and more frequent deployments. DevOps is not only about development (B is incorrect), does not break cadence but instead aligns it (C is incorrect), and is not the same as agile but complements it (D is incorrect). Reference: DevOps Foundation v3.6 syllabus section 1.5; The Phoenix Project; Accelerate.

Wait Time is the time work spends waiting between process steps---wasted, non-value-added time.

Mathematically, Wait Time = Lead Time -- Cycle Time

Lead Time: Time from work request to delivery.

Cycle Time: Time spent actively working on the item.

Why is this important in DevOps? Identifying and reducing wait time (waste) is central to Lean/DevOps, directly improving flow and reducing delays.

Extract-style reference: ''Wait time is calculated as the difference between lead time and cycle time---highlighting bottlenecks in the value stream.'' --- DevOps Handbook PeopleCert DevOps Foundation v3.6: Wait time is a core Lean concept for optimizing flow.

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.

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.

The Thomas-Kilmann Conflict Mode Instrument (TKI) is a psychometric tool that measures an individual's behavior in conflict situations---specifically, how they handle disagreement with colleagues.

It classifies responses into five modes: Competing, Collaborating, Compromising, Avoiding, and Accommodating.

Why not the others?

Kubler Ross Change Curve: Describes emotional responses to change, not conflict styles.

Westrum's Typology: Categorizes organizational culture (pathological, bureaucratic, generative) but doesn't measure individual behavior.

Value Stream Mapping: A process improvement tool, not a behavioral assessment.

Reference/Extract: ''The Thomas-Kilmann instrument helps teams understand how individuals approach conflict and collaboration, enabling better resolution strategies---a key aspect of high-performing DevOps teams.'' --- DevOps Handbook; PeopleCert DevOps Foundation v3.6 Section 3.7