Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB-CTFL Exam - Topic 1 Question 49 Discussion

Posted by Lawana on Aug 18, 2025 at 11:56 AM

The acceptance criteria associated with a user story:

Suggested Answer: C

The acceptance criteria associated with a user story are the conditions that must be met for the user story to be considered done and to deliver the expected value to the user. They are often written in different formats, such as rule-oriented, scenario-oriented, or table-oriented, depending on the nature and complexity of the user story. They represent an aspect of a user story referred to as confirmation, which is one of the so called ''3 C's'' of user stories. The other two aspects are card and conversation. Card refers to the concise and informal description of the user story, usually following the template: ''As a [role], I want [feature], so that I can [benefit]''. Conversation refers to the ongoing dialogue between the stakeholders and the team members to clarify and refine the user story and its acceptance criteria. Therefore, option C is the correct answer.


Get Premium ISTQB-CTFL Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
20 comments · newest first
CH
Chauncey 9 months ago
Not sure about the '3 C's' thing... sounds a bit confusing.
AF
Afton 10 months ago
I agree with A, but B has its merits as well.
JO
Johnetta 10 months ago
Wait, are you saying D is a must? That seems strict!
OD
Odelia 10 months ago
I think C is spot on, too.
ED
Edda 11 months ago
A is definitely the most common format!
CA
Carin 11 months ago
I vaguely recall that acceptance criteria can be in different formats, but I thought they had to follow a specific structure like scenario-oriented or rule-oriented.
RA
Raul 11 months ago
I feel like I've seen the 'As a [role], I want [feature]' format used a lot, but I'm not sure if that's specifically for acceptance criteria.
MA
Ma 11 months ago
I remember practicing a question that mentioned the 3 C's, and I think confirmation is part of that, so maybe option C is correct?
MO
Mozelle 12 months ago
I think the acceptance criteria are usually written in the Given/When/Then format, but I'm not completely sure if that's the only way to do it.
FE
Fernanda 12 months ago
I remember learning that the acceptance criteria are often documented following a rule-oriented format, like 'As a [role], I want [feature], so that I can [benefit]'. So I'm going to go with option B.
LO
Loise 12 months ago
The acceptance criteria represent the 'confirmation' part of the 3 C's for user stories, so I think option C is the best answer. I've seen them written in different formats, but the 'Given/When/Then' template is a common one.
TA
Tamera 1 year ago
Hmm, I'm a bit confused on this one. I know the acceptance criteria are related to the user story, but I'm not sure about the specific format. I might have to think this through a bit more.
AS
Ashlyn 1 year ago
I'm pretty sure the acceptance criteria are often written in a rule-oriented format using the 'Given/When/Then' template, so I'll go with option A.
IN
Ines 1 year ago
I agree with Annamae, that format helps to clearly define the conditions and expected outcomes.
AN
Annamae 1 year ago
I think the acceptance criteria are often written in a rule-oriented format using the template 'Given/When/Then'.
TO
Tomoko 1 year ago
I think the correct answer is C. The acceptance criteria can be written in different formats, and they represent the 'confirmation' aspect of the 3 C's (Card, Conversation, Confirmation).
GE
Gennie 9 months ago
↳ replying to Tomoko
Exactly! Flexibility in formats helps teams adapt better.
AP
Apolonia 9 months ago
↳ replying to Tomoko
C highlights the importance of confirmation in user stories.
SO
Sophia 10 months ago
↳ replying to Tomoko
Yeah, different formats are essential for clarity.
AR
Ardella 10 months ago
↳ replying to Tomoko
I agree with you, C makes the most sense.
0/2000 characters

Save Cancel