Which of the following is NOT a typical IT constraint?

In DevOps and IT service management, constraints are factors that limit throughput, create bottlenecks, and delay the flow of value from development to production. Typical IT constraints include lengthy security assessments, rigid bureaucratic approval processes (such as change advisory boards), and development delays. Conversely, loosely coupled architectures—such as microservices or modular system designs—are architectural enablers designed specifically to eliminate dependencies and reduce deployment constraints. By allowing components to be developed, tested, and deployed independently without disrupting other systems, loosely coupled architectures increase flow efficiency and delivery velocity. Therefore, loosely coupled architecture represents a solution to constraints rather than an IT constraint itself.

A. Security assessments performed manually or late in the lifecycle create major compliance bottlenecks and slow down deployment pipelines, making them typical IT constraints.
C. Bureaucratic processes, such as heavy change approvals, add administrative overhead and slow down work flow, acting as major organizational constraints.
D. Development delays caused by technical debt, resource limitations, or poor requirements stall the flow of work, serving as common development constraints.

Kim, G., Humble, J., Debois, P., & Willis, J. (2016). The DevOps Handbook. IT Revolution Press. Part IV: Enable Loose Coupling for Architecture, pp. 165-176.

Humble, J., & Farley, D. (2010). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Addison-Wesley Professional. Chapter 11: Managing Infrastructure and Applications.