DevOps helps this organization primarily by improving its ability to deliver technology change quickly, safely, and sustainably. The scenario describes several classic symptoms of a non-DevOps operating model: slow feature delivery, unstable releases, production incidents, excessive operational toil, and inability to focus on strategic risk such as cybersecurity because teams are trapped in reactive firefighting. Option B is the most complete answer because DevOps is not merely automation, experimentation, or shifting support responsibility to developers. Those may be practices within a broader transformation, but the leadership objective is improved flow, reliability, feedback, resilience, and value delivery.
By adopting DevOps principles, the organization can reduce deployment risk through smaller batch sizes, better collaboration between development, operations, security, and business stakeholders, automated testing, continuous integration, continuous delivery, monitoring, and learning from incidents. Security concerns can also be addressed earlier through DevSecOps practices, integrating security controls into the delivery lifecycle rather than treating them as separate emergency work. This supports both business agility and operational stability.
Specific Study Guide alignment: Becoming a DevOps Organization; Measuring to Improve; Measuring to Learn; DevOps and Transformational Leadership.
