Which DevOps practice most directly supports rapid feedback loops?

• A. Automated testing and continuous integration
• B. Waterfall planning
• C. Manual testing without automation
• D. Isolated development and no monitoring

Answer: (D)

Rapid feedback loops come from automatically validating changes as soon as they’re made. Automated testing and continuous integration deliver that immediacy by running tests, building the code, and signaling results whenever a developer commits changes. This keeps issues visible early, so fixes are found and addressed quickly, shortening the time from code change to actionable feedback and deployment readiness.

Other approaches slow or remove feedback. Waterfall planning follows a linear path that delays feedback until late in the cycle, making it harder to adjust quickly. Manual testing without automation introduces delays and inconsistency, so failures take longer to surface. Isolated development with no monitoring breaks visibility into how software behaves in production, so feedback from real usage isn’t received promptly.