Which statement best describes DevOps in terms of team structure?

Which statement best describes DevOps in terms of team structure?

• A. Keeping development and operations separated
• B. Focusing only on hardware maintenance
• C. Replacing ITIL in governance
• D. Uniting infrastructure and application teams to deliver and troubleshoot holistic services

Answer: (D)

DevOps is about breaking down barriers between the people who build software and those who run it, so teams own the end-to-end service. In practice, this means forming cross-functional groups that include both infrastructure and application responsibilities, collaborating to plan, build, deploy, monitor, and troubleshoot a holistic service. The goal is shared accountability and faster, more reliable delivery through automation and continuous feedback. That’s why uniting infrastructure and application teams to deliver and troubleshoot holistic services best describes DevOps. The other options describe keeping teams separate, focusing only on hardware, or replacing governance frameworks, which don’t capture the collaborative, end-to-end approach DevOps promotes.

DevOps is about breaking down barriers between the people who build software and those who run it, so teams own the end-to-end service. In practice, this means forming cross-functional groups that include both infrastructure and application responsibilities, collaborating to plan, build, deploy, monitor, and troubleshoot a holistic service. The goal is shared accountability and faster, more reliable delivery through automation and continuous feedback. That’s why uniting infrastructure and application teams to deliver and troubleshoot holistic services best describes DevOps. The other options describe keeping teams separate, focusing only on hardware, or replacing governance frameworks, which don’t capture the collaborative, end-to-end approach DevOps promotes.