How can coordination and communication issues among distributed agile teams impact testing activities?

They have no impact because testing is a local team activity

They are easily resolved by using automated test tools

They can lead to duplicated test efforts and gaps in test coverage

They only affect test execution speed, not test quality

Which factor can hinder rapid feedback loops in a scaled agile environment?

Teams receive feedback immediately after each code commit

Dependencies between teams can cause delays in test execution and result sharing

Continuous testing is not affected by team coordination

Test results are shared in real-time across all teams

Why is it challenging to keep testing aligned with business value when multiple teams work on different product aspects?

Business value is always clearly communicated to all teams

Teams may focus on testing features they own rather than those that deliver the most customer value

Testing alignment with business value is not a concern in scaled agile

Each team naturally prioritizes the most valuable features for testing

What is a consequence of ambiguous quality ownership in scaled agile?

Teams collaborate more to ensure quality

Quality issues may be left unaddressed because no team claims responsibility

Quality improves because each team focuses on its own area

Quality ownership is automatically assigned by the agile framework

A software company has adopted continuous delivery with 14 teams. Each team runs its own CI pipeline, but the full end-to-end regression suite takes 12 hours to run and is only executed nightly. The test leadership wants to provide faster feedback to teams. What is the most effective improvement?

Increase the frequency of the full regression suite to run after every merge.

Ask teams to run the full regression suite locally before merging.

Implement a test impact analysis to run only the tests affected by the code changes.

Move the full regression suite to a cloud-based infrastructure to run it faster.

Certified Tester Agile Test Leadership at Scale

Domain 5Objective 1

Testing Challenges in Agile at Scale Product Development CT-ATLAS Practice Questions (Page 5)

Part of the Test Processes in a Value-Driven Organization domain, which makes up ~25% of our current practice bank. ISTQB does not publish an official question count, but from its 120-minute exam (~50–80 total, ~13–20 in this domain), expect 3–4 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

8concepts

8 Concepts in This Objective

Agile at Scale Product Development Challenges
Coordination and Communication Challenges
Integration and System-Level Testing Challenges
Test Environment and Infrastructure Challenges
Test Automation and Tooling Challenges
Quality Ownership and Accountability Challenges
Alignment with Business and Customer Value
Continuous Testing and Feedback Challenges

Questions 21–25

21foundation · easy
How can coordination and communication issues among distributed agile teams impact testing activities?
Select an answer first
22foundation · easy
Which factor can hinder rapid feedback loops in a scaled agile environment?
Select an answer first
23foundation · easy
Why is it challenging to keep testing aligned with business value when multiple teams work on different product aspects?
Select an answer first
24foundation · easy
What is a consequence of ambiguous quality ownership in scaled agile?
Select an answer first
25application · medium
A software company has adopted continuous delivery with 14 teams. Each team runs its own CI pipeline, but the full end-to-end regression suite takes 12 hours to run and is only executed nightly. The test leadership wants to provide faster feedback to teams. What is the most effective improvement?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-ATLAS

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CT-ATLAS” is a trademark of its owner, used for identification only.