During a review, the team finds this story: 'As an admin, I want to delete user accounts so that I can remove inactive users.' The team notices that 'inactive' is not defined. What is the best way to resolve this ambiguity?

Ask the product owner to remove the word 'inactive' and just say 'delete any user'.

Split the story into two stories: one for deletion and one for defining inactive.

Assume 'inactive' means users who have not logged in for 6 months and proceed.

Define 'inactive' in the acceptance criteria, e.g., no login for 12 months, and clarify the deletion behavior.

Which approach is commonly used to break down an epic into user stories?

Writing a single story that covers all functionality

Removing all non-functional requirements

Splitting by user role or persona

Assigning the epic to a single team member

Which requirements engineering technique is specifically used to clarify the intended behavior of a system by defining example scenarios that illustrate the acceptance criteria?

Behavior-driven development (BDD) with Given-When-Then scenarios

When decomposing a user story into testable requirements, which action is most aligned with the INVEST criteria?

Combining multiple stories into one large requirement to reduce overhead

Rewriting the story using technical jargon to be more precise

Splitting the story until each resulting requirement is independently testable

Removing acceptance criteria to keep the story simple

What is the primary goal of reviewing user stories for ambiguity and completeness?

To reduce the number of stories in the backlog

To ensure the story is clear and testable

To assign the story to a developer

Certified Tester Advanced Level Agile Technical Tester

Domain 1Objective 1

Analyze User Stories and Epics Using Requirements Engineering Techniques CT-ATT Practice Questions (Page 1)

Part of the Requirements Engineering domain, which makes up ~19% of our current practice bank. ISTQB does not publish an official question count, but from its 90-minute exam (~35–60 total, ~7–11 in this domain), expect 4–6 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

6concepts

Questions 1–5

1application · medium
During a review, the team finds this story: 'As an admin, I want to delete user accounts so that I can remove inactive users.' The team notices that 'inactive' is not defined. What is the best way to resolve this ambiguity?
Select an answer first
2foundation · easy
Which approach is commonly used to break down an epic into user stories?
Select an answer first
3foundation · easy
Which requirements engineering technique is specifically used to clarify the intended behavior of a system by defining example scenarios that illustrate the acceptance criteria?
Select an answer first
4foundation · easy
When decomposing a user story into testable requirements, which action is most aligned with the INVEST criteria?
Select an answer first
5foundation · easy
What is the primary goal of reviewing user stories for ambiguity and completeness?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-ATT

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