iSQI CTFL-AT Practice Test Questions Answers

Comprehensive and Detailed Explanation From Exact Extract:

From theISTQB CTFL-AT Syllabus v4.0, Section 1.2The Fundamentals of Agile Software Development, Kanban is explained as:

"In Kanban, work is visualized using a board that shows tasks in various states of progress. The transparency of the workflow helps teams identify bottlenecks, improve flow, and collaborate effectively."

This directly supportsOption C, whereKanban boardsare used for visualizing active tasks — increasingtransparencyandprogress visibility.

Let’s clarify the other options:

Option A: The five values listed —communication, simplicity, feedback, courage, and respect— are associated withExtreme Programming (XP), not Kanban.

Option B: Scrumdoes not prescribe specific testing techniques, but italso does not dictate how development must be done, which makes this atrick answerthat’s partially true butnot complete or precise enoughto be correct.

Option D: The roles areincorrectly named. The correct Scrum roles are:

Product Owner,

Scrum Master,

Developers (Development Team is no longer a formal term post-2020 Scrum Guide)

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 2.2Release and Iteration Planning, it describes Planning Poker as:

"Planning Poker involves group discussion, especially from the highest and lowest estimators, to ensure that different perspectives and assumptions are aligned, which leads to more accurate and shared understanding of the effort involved."

Thus,Option Cis correct — Team B usesdiscussion-based estimation, which is a corebenefitof Planning Poker.

Option Ais speculative — we cannot know the actual effort difference.

Option Bis incorrect — convergence without discussion may indicatelack of engagement or pressure to agree.

Option Dis false — Planning Poker isnot based on averaging, but onconsensus.

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 2.4Testing and Iterations, it states:

"In Agile projects, testing activities are conducted in parallel with development activities within an iteration, unlike traditional models where testing is done after development."

Therefore,Option Dis correct — Agile promotesparallel testing, while traditional projects (e.g., V-model) followsequential phases.

Option Ais incorrect — Agile projectsdo perform system testing, but it's integrated within iterations.

Option Bis misleading — while Agile emphasizeslower-level test automation, traditional projects also use automation at various levels.

Option Cis partially correct but oversimplifies the process —risks are reassessed iteratively, not just once during release planning.

Comprehensive and Detailed Explanation From Exact Extract:

From theCTFL-AT Syllabus v4.0, Section 2.2Release and Iteration Planning, testers actively contribute during release planning:

"During release planning, testers collaborate with the team to understand the scope of the release and help identify any high-level test considerations. They also participate in quality risk analysis and help in estimating test effort."

Furthermore, it is noted:

"Testers are involved in defining and refining user stories and acceptance criteria, and contribute to quality risk assessments."

Therefore,Option Cis accurate as it reflects the tester's involvement inprioritizing user storiesand conductingquality risk analysisduring release planning.

Option Ais incorrect because defining and redefining the product backlog is primarily the role of theProduct Owner, and the test approach isiteration-specific, not fixed for the full release.

Option Bis inaccurate — breaking down stories into tasks is generally part ofiteration (Sprint) planning, not release planning.

Option Dis incorrect —release plans can changein Agile to accommodate changing business needs.

Independence in testing is the degree of separation between the person who tests something and the person who developed it. Independence can help to reduce bias, increase objectivity, and provide different viewpoints. However, independence also has some drawbacks, such as increased communication overhead, reduced collaboration, and delayed feedback. In agile projects, testers are usually embedded in the agile teams to perform many of the testing tasks, such as unit testing, integration testing, acceptance testing, etc. This provides a high level of collaboration and fast feedback, but also reduces the independence of the testers. Testers from an independent test team who do not get involved with the agile team, but are assigned to do System Testing once all sprints are completed, would provide the most independence for testers working with agile teams. However, this would also introduce many disadvantages, such as lack of alignment with the agile principles, loss of context and domain knowledge, delayed defect detection and resolution, and increased risk of missing customer expectations. References: ISTQB® Foundation Level Agile Tester Syllabus, Section 1.1.2, page 8; ASTQB Agile Tester Certification Resources, Section 1.1.2, page 8.