DevOps-Foundation Exam Questions & Answers

Deployment frequency is not a culture metric.

It's a process metric, indicating how often code is released.

Culture metrics focus on engagement, morale, retention, psychological safety, and NPS.

Why not the others?

Employee NPS: Measures employee satisfaction and willingness to recommend.

Engagement/morale: Direct indicators of cultural health.

Retention: How well an org keeps talented people, reflecting culture.

Extract-style reference: ''Measuring DevOps culture relies on employee engagement, morale, and retention, not on delivery metrics like deployment frequency.'' --- State of DevOps Report PeopleCert DevOps Foundation v3.6: Culture metrics focus on people, not just process.

Loosely coupled architectures are not typical IT constraints; in fact, they are often a solution to constraints. Typical IT constraints include:

Security assessments (slow approvals)

Bureaucratic processes (excessive paperwork or approvals)

Development delays (resource or tool bottlenecks)

Extract-style reference: ''Loosely coupled architectures enable teams to work independently, reducing constraints imposed by tightly integrated systems.'' --- Accelerate: The Science of Lean Software and DevOps DevOps Foundation v3.6 lists constraints as blockers to fast flow and highlights architectural decoupling as a DevOps enabler.

A fast flow of unplanned work into production is not a characteristic of DevOps. In fact, DevOps practices strive to minimize unplanned work (like emergency changes or outages) through automation, testing, collaboration, and rigorous change control. The other options---ensuring organizational success, working toward a common goal, and world-class stability/reliability---are all key DevOps characteristics. Reference: DevOps Foundation v3.6 syllabus section 1.4; State of DevOps Report.

DevOps is not simply a team, methodology, or standard. The PeopleCert DevOps Foundation v3.6 materials define DevOps as a ''cultural and professional movement'' that stresses communication, collaboration, integration, and automation to improve workflow between software developers and IT operations professionals. The cultural transformation is fundamental, emphasizing shared responsibilities, breaking down silos, and fostering continuous improvement. Reference: DevOps Foundation v3.6 syllabus section 1.1; State of DevOps Report; 'The Phoenix Project'.

Manufacturing is not a 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.