GET 65% Discount on All Products Coupon code: "bigdisc65"
Which of the following is NOT a typical IT constraint?
Security assessments
Loosely coupled architectures
Bureaucratic processes
Development delays
Loosely coupled architecturesare 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.
How do you define Wait Time?
Lead time minus cycle time
Cycle time minus lead time
Lead time plus cycle time
Cycle time multiplied by lead time
Wait Timeis 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.
“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.
TESTED 31 Jul 2025
