Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 5.1 and 5.3:

"Testers, like all team members, participate in retrospectives and are encouraged to suggest improvements to team processes and product quality."

So Option A is correct. Testers actively engage in retrospectives and suggest improvements based on their testing experience.

Option B and C refer to Scrum Master responsibilities .

Option D is the responsibility of the Product Owner .

Comprehensive and Detailed Explanation From Exact Extract:

From the ISTQB CTFL-AT Syllabus v4.0 , Section 1.1 Agile Software Development and the Agile Manifesto , the Agile approach is described as:

"Agile software development uses iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing and cross-functional teams."

Option C reflects this exact concept, highlighting both the iterative-incremental lifecycle and the collaborative nature of Agile teams.

Option A refers specifically to pair programming , a practice used in Extreme Programming (XP) , but it’s not a definition of Agile as a whole.

Option B mistakenly describes a sequential (Waterfall-like) iteration structure where testing is delayed.

Option D describes a hybrid or phased approach , not consistent with core Agile principles.

Comprehensive and Detailed Explanation From Exact Extract:

From ISTQB Glossary (also referenced in CTFL-AT) :

"Configuration management is a discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance."

Thus, Option D is the formal and accurate definition of Configuration Management .

Option A describes test control , not configuration management.

Option B refers to session-based testing , unrelated to configuration management.

Option C refers to combinatorial test design , not configuration control.

 Scrum is an agile development approach that incorporates the following practices:

a project is divided into iterations called sprints, which are typically 2-4 weeks long

each sprint starts with a planning meeting, where the team selects a subset of user stories from the product backlog to work on

each sprint ends with a review meeting, where the team demonstrates the potentially releasable/shippable product increment to the stakeholders and collects feedback

each sprint also includes a retrospective meeting, where the team reflects on the process and identifies areas for improvement 1 2 3   References :  1 : ISTQB® Foundation Level Agile Tester Syllabus, Section 2.1, Agile Software Development 1 ;  2 : ASTQB Agile Tester Certification Resources, Section 2.1, Agile Software Development 2 ;  3 : What is Agile?  | Atlassian 3

According to the ISTQB Tester Foundation Level Agile Tester syllabus, acceptance criteria are a set of conditions that a user story must satisfy to be accepted by the customer or stakeholder. Acceptance criteria should be  testable , meaning that they can be verified by objective measurements or observations. Testable acceptance criteria should be  clear ,  unambiguous ,  complete , and  consistent . Therefore, option A is the best example for testable acceptance criteria, as it specifies a clear and measurable condition for the input value of the ID field. Option B is not a good example for testable acceptance criteria, as it is vague and does not define any specific condition or expectation for the interface to External System. Option C is not a good example for testable acceptance criteria, as it is incomplete and does not specify what the specific authorization level is or how it is determined. Option D is not a good example for testable acceptance criteria, as it is subjective and not measurable. What is clear and attractive for one user may not be for another.  References : ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.1, page 7; ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.2, page 8; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.1, page 23; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.2, page 24.

3of30

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 1.2 Fundamentals of Agile Software Development , it states:

"Kanban is a lean approach that uses visualization (typically via a task board) to manage work in progress and improve workflow. Unlike Scrum, iterations in Kanban are optional."

Thus, Option C (Kanban) is correct. It emphasizes visualization and does not require fixed-length iterations .

Option A (Scrum) is iteration-based.

Option B (Continuous integration) is a practice, not a development approach.

Option D (Slack) is a communication tool, not a methodology.

 Release planning is a process of defining the scope and timeline for an iterative or incremental product development project.  It is used in agile or hybrid projects where a mid- to long-term planning of the product or system development or integration is required 1 2 . Release planning involves the following activities:

Identifying testable user stories with acceptance criteria. User stories are short descriptions of the features or functionalities that the customer or user wants from the product. Acceptance criteria are the conditions that must be met for the user story to be considered done and acceptable.  Identifying testable user stories with acceptance criteria helps to define the scope and quality of the release 1 3 .

Prioritizing the user stories. User stories are prioritized based on the value they deliver to the customer or user, as well as the dependencies, risks, and costs associated with them.  Prioritizing the user stories helps to determine the order and frequency of the releases 1 3 .

Performing high level estimation for the release. High level estimation is a technique to estimate the effort, time, and resources needed to complete the user stories in the release. High level estimation can be done using various methods, such as analogy, expert judgment, planning poker, etc.  Performing high level estimation for the release helps to set realistic and achievable goals and deadlines 1 3 .

Therefore, activities 1, 3 and 6 are done in release planning.  Activities 2, 4 and 5 are done in iteration planning, which is a more detailed and short-term planning of the work to be done in each iteration or sprint 1 3 .  References :  1 : ISTQB® Foundation Level Agile Tester Syllabus, Section 2.2, Fundamental Agile Testing Principles, Practices and Processes 1 ;  2 : Agile Release Planning in Hybrid and Agile Projects 4 ;  3 : How to Create an Agile Release Plan 5

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 2.2 Quality Risk Analysis :

"The whole team contributes to quality risk analysis. While the Product Owner may identify business risks, the team collectively assesses risk levels based on impact and likelihood."

Thus, Option A is correct — collaborative assessment ensures accurate risk-driven testing and planning.

Option B is wrong — poor user stories should be addressed , not ignored.

Option C is incorrect — risk level , not item count, determines depth of testing.

Option D is false — effort estimation considers multiple factors , not just risk.

The best black box test design technique for verifying the accuracy of this user story is  equivalence partitioning . Equivalence partitioning is a technique that divides the input domain of a system into classes or groups that are expected to behave similarly. By testing one value from each class, the tester can reduce the number of test cases while still achieving good coverage. In this case, the input domain of the system is the amount of income, which can be divided into classes based on the tax percentage applied to different income ranges. For example, if the tax percentage is 10% for income below 10,000, 20% for income between 10,000 and 20,000, and 30% for income above 20,000, then the equivalence classes are: low income ( < 10,000), medium income (10,000-20,000), and high income ( > 20,000). By testing one value from each class, such as 5,000, 15,000, and 25,000, the tester can verify that the system calculates the correct tax percentage for each income range.  This technique is more efficient and effective than testing all possible values of income, or testing only one value of income, or testing the states of income entry, or testing the statements in income calculation.  References:  ISTQB Foundation Level Agile Tester Syllabus 1 , Section 2.3.1, page 19; ISTQB Foundation Level Agile Tester Extension Sample Exam Questions 2 , Question 5, page 6.

 Business-oriented work products are those that describe what is needed (e.g., requirements specifications) and how to use it (e.g., user documentation). A user manual is an example of a business-oriented work product, as it provides instructions and guidance on how to use the product from the user’s perspective. A user manual may also contain information about the product’s features, benefits, and limitations. A user manual is typically written by technical writers, who may collaborate with developers, testers, and business analysts to ensure the accuracy and clarity of the content.  A user manual may be delivered in various formats, such as printed, online, or interactive.  References : ISTQB® Foundation Level Agile Tester Syllabus 1 , Section 1.2.1, page 10; ASTQB Agile Tester Certification Resources 2 , Section 1.2.1, page 10.