DevOps Culture, Fundamentals, and Maturity Models ECDE Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A traditional IT organization has separate teams for development, testing, and operations. Releases are infrequent, and each team has its own priorities. The organization wants to adopt DevOps practices to increase deployment frequency and reduce failure rates. Which change is most aligned with DevOps fundamentals?

   • AImplement continuous integration and continuous delivery pipelines that automate build, test, and deployment stages.
   • BMove all testing to a separate quality assurance team that reports directly to the CIO.
   • CIncrease the frequency of manual regression testing before each release.
   • DCreate a new project management office to coordinate between the siloed teams.
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A DevSecOps team is conducting a maturity assessment. They find that security is integrated into the CI pipeline, but the operations team is not involved in the design of the deployment process, and there is no feedback loop from production back to development. Which cultural practice would most improve their maturity?

   • ACreate a joint design review where developers, operations, and security collaborate on the deployment architecture and review production incidents together.
   • BHave the operations team write a deployment runbook that developers must follow.
   • CAdd more automated security scans to the CI pipeline.
   • DLet the security team define the deployment process to ensure it is secure.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A software company is moving from a traditional model where security performs a penetration test just before release. They want to adopt DevSecOps. Which change best reflects the DevSecOps cultural shift?

   • AIncrease the frequency of penetration tests to once per month, just before each release.
   • BMove the penetration test to after production deployment so that the release is not delayed.
   • CEmbed security tools into the CI/CD pipeline so that developers and operations see security results in their normal workflow.
   • DCreate a dedicated security team that reviews every code commit before it is merged.
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   A traditional IT organization has a release process that takes two weeks because of manual handoffs between development, QA, and operations. They want to adopt DevOps practices to reduce the time to market. Which change would have the most direct impact on reducing handoff delays?

   • AHire more QA engineers to speed up the testing phase.
   • BCreate a detailed handoff document for each stage to reduce errors.
   • CAutomate the build, test, and deployment pipeline so that code moves through stages without manual handoffs.
   • DIncrease the frequency of team meetings to improve communication between the teams.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A company wants to implement DevSecOps but the security team is worried that automated security tools will produce too many false positives, slowing down development. Which approach best addresses this concern while maintaining a DevSecOps culture?

   • ATurn off all automated security scanning and rely on manual penetration tests before release.
   • BRun security scans only on the final release candidate, not on every commit.
   • CLet the security team define all rules without developer input to ensure accuracy.
   • DStart with a small set of high-signal security rules, and have developers and security engineers jointly tune the rules based on feedback.
   Reveal Solution Discussion Select an answer first