The correct answer is C because traditional IT is typically organized by function. Common examples include separate departments for development, testing, infrastructure, security, service desk, operations, architecture, change management, and release management. Each function has its own management structure, priorities, metrics, queues, and operating rhythm. This design can create specialization, but it often introduces delays, fragmented ownership, and handoffs across the delivery lifecycle.

DevOps challenges this model by focusing on end-to-end value streams and cross-functional ownership. Instead of optimizing individual departments, DevOps seeks to optimize the whole system of work. Cross-functional cells or squads are therefore more consistent with a DevOps operating model than a traditional IT structure. Similarly, being optimized for flow and having fewer handoffs are DevOps characteristics because they support faster feedback, smaller batches, clearer accountability, and improved reliability.

Functional organization is a central reason traditional IT often struggles with slow delivery and operational instability. Work must pass between teams, creating queues, misalignment, and limited shared accountability for outcomes. Relevant study guide references: Target Operating Models and Organizational Designs; Becoming a DevOps Organization; Measuring to Improve.

==============