Important DevOps Practices CT-ATLAS Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   How does Continuous Delivery (CD) enable reliable, rapid releases to production?

   • ABy requiring a large batch of features to be completed before a release is considered, reducing the frequency of deployments.
   • BBy using a fully automated pipeline that builds, tests, and packages the software, ensuring it is always in a release-ready state.
   • CBy ensuring that every change is automatically deployed to production, eliminating the need for a release process.
   • DBy performing all testing in production to ensure the software works in the real environment before release.
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   How does shift-left testing integrate testing earlier in the development lifecycle?

   • ABy delaying all testing until the code is fully integrated and deployed to a staging environment.
   • BBy running automated tests in production and using the results to improve future development.
   • CBy involving testers in requirements reviews and design discussions, and writing test cases before code is written.
   • DBy using a separate team to test the software after the development team has finished all coding.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A team wants to use shift-right testing to improve quality. They have deployed a new feature and want to detect issues that only appear under real user conditions. Which approach best supports this?

   • APerform load testing in a staging environment that mirrors production.
   • BRun a full regression suite in production after each release.
   • CCollect user feedback through a survey after each release.
   • DMonitor production metrics and user behavior, and use canary releases to validate new features.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   How does shift-right testing use production monitoring and feedback to improve quality?

   • ABy disabling all monitoring in production to ensure the software runs without interference.
   • BBy relying solely on user bug reports to identify issues, as monitoring is not reliable.
   • CBy running all tests in production before the software is released to the public.
   • DBy using production data to identify usage patterns and defects that were not caught in pre-production testing, feeding this information back to the development team.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A team is adopting CI and wants to shift testing left. They currently run a large end-to-end test suite in a separate nightly job. Which approach best aligns with the test pyramid and shift-left principles?

   • AMove the end-to-end suite to run on every commit in the CI pipeline.
   • BKeep the nightly end-to-end suite unchanged and add a few smoke tests to the CI pipeline.
   • CReplace all end-to-end tests with unit tests to speed up the pipeline.
   • DAdd a fast unit test layer to run on every commit, keep a smaller end-to-end suite for nightly or release candidates.
   Reveal Solution Discussion Select an answer first