A team is refining a user story: 'As a user, I want to reset my password so I can regain access.' The product owner believes this is ready for development. The tester notes that the story lacks specifics about the reset method, time limits, and validation rules. Which action best aligns with shift-left principles?

Proceed with development and design the tests after the feature is implemented to avoid delaying the sprint.

Ask the product owner to add measurable acceptance criteria covering the reset method, expiry window, and input validation before the story enters the sprint.

Create a generic test plan that covers all possible password reset scenarios without further clarification.

Ask the developer to make reasonable assumptions about the reset process and document them in the code comments.

A team is developing a mobile app for a bank. The product owner has provided a list of features, but the testers are unsure about the security requirements. Which collaborative technique would best clarify these requirements?

Wait for the security audit to be performed after the app is developed.

Have the testers research common security vulnerabilities and create test cases without consulting the product owner.

Conduct a brainstorming session with the product owner, testers, and a security expert to identify potential security risks and define requirements.

Ask the product owner to provide a list of security features from a competitor's app.

Which practice is an example of providing continuous feedback on requirements?

Waiting for user feedback after release

Writing a detailed requirements document at the start of the project

Conducting a retrospective at the end of each sprint

Holding regular backlog refinement sessions to discuss and clarify requirements

What is the purpose of requirements traceability in agile testing?

To ensure that every requirement has at least one test and every test is linked to a requirement

To track the progress of developers in implementing requirements

To prioritize requirements for the next sprint

To document the history of requirement changes

A team notices that several user stories are being rejected during sprint reviews because they do not meet stakeholder expectations. The testers want to provide feedback on requirements earlier in the process. What mechanism would be most effective?

Wait until the sprint review to present test results and let stakeholders decide on changes.

Ask the product owner to review the test cases after development is complete.

Create a detailed requirements document at the start of the project and avoid changes.

Introduce a structured feedback loop during backlog refinement where testers share their concerns about requirement clarity and testability.

Certified Tester Advanced Level Agile Tester

Domain 4Objective 2

Shift Left and Requirements Engineering CTAL-AT Practice Questions (Page 5)

Part of the Shift Left domain, which makes up ~13% of our current practice bank. ISTQB does not publish an official question count, but from its 90-minute exam (~35–60 total, ~5–8 in this domain), expect 3–4 from this objective — we provide 33 practice questions to prepare you well beyond it. (estimate)

33questions here

7free pages

10concepts

Questions 21–25

21application · medium
A team is refining a user story: 'As a user, I want to reset my password so I can regain access.' The product owner believes this is ready for development. The tester notes that the story lacks specifics about the reset method, time limits, and validation rules. Which action best aligns with shift-left principles?
Select an answer first
22application · medium
A team is developing a mobile app for a bank. The product owner has provided a list of features, but the testers are unsure about the security requirements. Which collaborative technique would best clarify these requirements?
Select an answer first
23foundation · easy
Which practice is an example of providing continuous feedback on requirements?
Select an answer first
24foundation · easy
What is the purpose of requirements traceability in agile testing?
Select an answer first
25application · medium
A team notices that several user stories are being rejected during sprint reviews because they do not meet stakeholder expectations. The testers want to provide feedback on requirements earlier in the process. What mechanism would be most effective?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-AT

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. “CTAL-AT” is a trademark of its owner, used for identification only.