Important PeopleCert DevOps Foundation Exam Questions

Answer: 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.

Answer: 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.

Answer: A

Explanation:

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.

Answer: B

Explanation:

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.

Answer: B

Explanation:

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, not command-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.