PeopleCert Updated DevOps-Foundation Exam Questions and Answers by kaya

Manufacturingisnota type of IT work in DevOps.

DevOps classifies IT work as:

Business projects:New value-creating work.

Planned work:Routine, repeatable tasks (maintenance, upgrades).

Unplanned work:Incidents, emergencies, support.

Extract-style reference:

“IT work includes business projects, planned work, and unplanned work. Manufacturing is an analogy for flow, but not a category of IT work itself.”

—The Phoenix Project

PeopleCert DevOps Foundation v3.6:Recognizes these three categories to manage and improve IT workloads.

TheThomas-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

Command(authoritarianism) is not a crucial ingredient for leading digital transformation.

The key ingredients:

Collaboration

Curiosity

Courage

DevOps leadership is about empowering teams, experimenting, and driving change,notcommand-and-control.

Extract-style reference:

“Digital transformation leaders embrace collaboration, curiosity, and courage, fostering an environment where experimentation and learning drive change.”

—Accelerate,DevOps Handbook

PeopleCert DevOps Foundation v3.6:Advocates servant and transformational leadership, not command/control.

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,withoutmanual intervention.

Why is D (“Continuous Deployment requires a manual push button”) NOT TRUE?

BecauseContinuous Deploymentis aboutno 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.6distinguishes between Continuous Delivery (manual trigger) and Continuous Deployment (fully automated).