Skills for Quality Assistance CT-ATLAS Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   Which characteristic is most important when selecting a quality metric?

   • AIt is approved by management
   • BIt provides actionable information that helps the team improve quality
   • CIt is comparable to industry benchmarks
   • DIt is easy to calculate and automate
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   What is the primary purpose of facilitating a quality risk analysis workshop?

   • ATo assign testing tasks to individual team members
   • BTo demonstrate the use of test management tools
   • CTo review the team's testing progress against the plan
   • DTo identify and prioritize quality risks to focus testing efforts
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   What is a key outcome of a well-facilitated retrospective workshop?

   • AA list of defects found during the last sprint
   • BA commitment to increase test automation coverage
   • CA detailed test plan for the next release
   • DActionable improvements to the team's process and collaboration
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   Which statement best reflects the principle of shared responsibility for quality in a quality assistance approach?

   • AEach team member contributes to quality by performing their own testing activities independently
   • BQuality is primarily the responsibility of the test team, who must ensure the product meets standards
   • CThe product owner is responsible for quality because they define the requirements
   • DQuality is a collective responsibility of the entire agile team, including testers, developers, and business stakeholders
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A team's retrospective identified that the team often discovers integration issues late in the sprint. The tester wants to drive continuous improvement. The team is already using three amigos and pair testing, but integration issues persist. What systemic change is most likely to address the root cause?

   • AAsk developers to manually coordinate integration efforts more carefully.
   • BCreate a checklist for integration testing and require the team to complete it before the sprint review.
   • CAdd more integration testing at the end of the sprint to catch issues before release.
   • DIntroduce continuous integration with automated integration tests that run on every commit, and review the results in the daily stand-up.
   Reveal Solution Discussion Select an answer first