Free ISTQB CTFL-AT_D Exam Questions

Become ISTQB Certified with updated CTFL-AT_D exam questions and correct answers

Page: 1 / 64

Total 317 Questions | Updated On: Aug 19, 2026

Add To Cart

Question 1

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

A : The “ID” field must accept input value of a length between 2 and 10 characters.

B : The interface to External System shall be specified.

C : Action “Reopen” must be available only for a user with a specific authorization level.

D : The program-s icon should be clear and attractive.

Answer: A

Question 2

Which of the following statements about Agile retrospectives is CORRECT?

A : During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities

B : In an Agile retrospective the moderator can encourage and make sure that good practices are kept by the team, by asking what the team is doing well.

C : Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging

D : Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities

Answer: B

Question 3

Which of the following statements about Agile retrospectives is CORRECT?

A : During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities

B : In an Agile retrospective the moderator can encourage and make sure that good practices are kept by the team, by asking what the team is doing well.

C : Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging

D : Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities

Answer: B

Question 4

Which of the following are testers' role during release planning?

i. Defining testable user stories, including acceptance criteria

ii. Breakdown user stories into tasks (particularly testing tasks)

iii. Defining the necessary test levels.

iv. Identify functional and non-functional characteristics of the system to be tested.

v. Create acceptance criteria for the stories.

A : i, ii, v

B : i, ii, iii

C : ii, iv

D : iii

Answer: D

Question 5