ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 81:

  Which of the following would you expect most likely to be an advantage of the whole-team approach?

  A. Providing constant availability of executable software throughout the iteration for testing, demonstration, or education purposes
  B. Improved quality of the requirements specification (through examples and automatable tests) when adopting the Acceptance Test-Driven Development practice
  C. Improved code quality produced as the result of the refactoring step performed as part of the test-driven.development technique
  D. Eliminating the schedule risks associated with big-bang integration
  A. Providing constant availability of executable software throughout the iteration for testing, demonstration, or education purposes

  ---

  From the CTFL-AT Syllabus v4.0, Section 1.3 The Whole-Team Approach, the benefit of the whole-team approach is:

  "All team members, including testers, work together in all project phases. This encourages collaboration and shared responsibility, which leads to the availability of working software and immediate feedback on changes."

  Specifically, it is noted:

  "One benefit of the whole-team approach is the continuous availability of working, executable software, which can be tested at any point in the iteration."

  This makes Option A the correct answer. Let's analyze the others:

  Option B relates to Acceptance Test-Driven Development (ATDD), not the whole-team approach specifically.

  Option C is a benefit of TDD, not of the whole-team approach.

  Option D refers to continuous integration, not directly tied to the whole-team concept.

  References:

  CTFL-AT Syllabus v4.0, Section 1.3 Learning Objective (K2) . Understand benefits of the whole-team approach in Agile

• Question 82:

  Consider an Agile project aimed at developing a test management tool. This tool allows Test Managers to generate progress reports for test analysis, test design and test execution phases in traditional projects. Consider the following user story of this Agile project:

  "As a Test Manager who is looking at a progress report, I want to be able to print this progress report, so that I can keep a hard copy for my daily records."

  For this user story the following acceptance criterion is defined:

  "Given that I am a Test Manager looking at a progress report, When I click the 'Print' button, Then the progress report should be printed"

  Based only on the given information, which of the following would you expect most likely to be true?

  A. Both the user story and the acceptance criterion are expressed in adequate form, but the user story is not testable
  B. Both the user story and the acceptance criterion are expressed in adequate form, but the user story does not describe functionality that is valuable to the user
  C. During the conversation, the acceptance criterion should not be discussed since it is described using the Given-When-Then template
  D. During the conversation, the need to update the acceptance criterion by specifying that a date stamp be visible on the printout could emerge
  D. During the conversation, the need to update the acceptance criterion by specifying that a date stamp be visible on the printout could emerge

  ---

  From the CTFL-AT Syllabus v4.0, Section 2.1 User Stories and Acceptance Criteria, it states: "Acceptance criteria are defined collaboratively and refined during the conversation to ensure mutual understanding. They may be added or updated as new insights emerge."

  This supports Option D, which reflects how acceptance criteria evolveduring conversations a key component of the"Card, Conversation, Confirmation"model.

  Option A is incorrect, the user story is testable, especially with the acceptance criterion.

  Option B is false, the story provides clear user value (printed hard copy for daily records).

  Option C is misleading, the Given-When-Then format supports discussions; it doesnt replace them.

  References:

  CTFL-AT Syllabus v4.0, Section 2.1 Learning Objective (K2) . Understand how acceptance criteria support collaboration and testability

• Question 83:

  Why is regression of software a high risk in agile projects?

  A. Test-driven development means that existing functionality is not considered.
  B. Test automation can cause regression of software in the test environment.
  C. Regression is built into software as a safeguard against unexpected failures.
  D. There is code churn due to change in business needs over several sprints.
  D. There is code churn due to change in business needs over several sprints.

  ---

  Regression of software is the risk that a change in one part of the software causes a defect in another part of the software that was previously working correctly. Regression of software is a high risk in agile projects because there is code churn due to change in business needs over several sprints. Code churn is the amount of code that is added, modified, or deleted in a software project over time. Code churn can indicate the volatility and complexity of the software, and the frequency and magnitude of the

  changes. In agile projects, code churn can be high because the business needs and the user requirements can change rapidly and frequently over several sprints, which are short iterations of development and testing. This means that the software is constantly evolving and adapting to the changing needs, and that the existing functionality and quality may be affected by the new or modified code. Therefore, regression of software is a high risk in agile projects, and it requires effective testing strategies and

  techniques to prevent, detect, and fix the regression defects.

  References:

  ISTQB. Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB. Glossary of Testing Terms2, version 4.0, pages 36 and 55

• Question 84:

  Which of the following statements about user stories is CORRECT?

  A. User stories should include detailed solution design
  B. User stories should represent value to the user or customer
  C. User stories must contain technical acceptance tests only
  D. User stories always replace requirement documents entirely
  B. User stories should represent value to the user or customer

  ---

  From CTFL-AT Section 2.1, user stories are short descriptions of features delivering value to users.

  Option B reflects this purpose.

  Option A contradicts Agile's avoidance of technical detail in stories.

  Option C is incorrect - acceptance criteria vary.

  Option D exaggerates; other documents may exist depending on context.

  References:

  CTFL-AT Syllabus v4.0, Section 2.1

• Question 85:

  A Scrum project is aimed at developing an online travel website based on an IBE (Internet Booking Engine), to provide booking of flights. The website will allow customers to specify their travel requirements, and once these requirements are received, the website will offer a list of available flights which customers can book. A single Scrum team will work on this project and the project will start with a Sprint Zero. Which of the following statements best describes how a tester on the Scrum team should contribute during the Sprint Zero?

  A. The tester should work together with the rest of the team to identify the product backlog and create an initial system architecture and high-level prototypes
  B. The tester should individually produce the list of the product backlog items that the team will commit to deliver at the end of the first regular sprint
  C. The tester should work together with the rest of the team to produce the list of the product backlog items that the team will commit to deliver at the end of the first regular sprint
  D. While the other team members are working on the project plan, the tester should individually create an initial test strategy for all test levels
  A. The tester should work together with the rest of the team to identify the product backlog and create an initial system architecture and high-level prototypes

  ---

  From CTFL-AT Syllabus v4.0, Section 2.2 Release and Iteration Planning: "During early phases like Sprint Zero, testers collaborate with the team to identify the product backlog, define high-level test strategies, and contribute to the overall planning and architecture discussions."

  Therefore, Option A is correct testers collaborate from the beginning, not as isolated contributors.

  Option B and D suggest individual work, which is against Agile principles.

  Option C is incorrect the backlog items committed for Sprint 1 are determined during Sprint Planning, not in Sprint Zero.

  References:

  CTFL-AT Syllabus v4.0, Section 2.2 Learning Objective (K2) . Understand tester contributions during early Agile planning

• Question 86:

  Which of the following statements about a test charter are CORRECT?

  1) It is used mainly in exploratory tests.

  2) It is used to monitor a test process.

  3) It may make reference to user stories.

  4) It contains notes taken during a test session.

  5) It is used to outline the company test policy.

  A. 1, 2, 5
  B. 2, 3, 4
  C. 2, 4, 5
  D. 1, 3, 4
  D. 1, 3, 4

  ---

  A test charter is a document that describes the scope, objective, and approach of an exploratory testing session. It is used mainly in exploratory tests to guide the tester's actions and record the findings. A test charter may make reference to user stories, requirements, risks, or other sources of information that are relevant to the testing mission. A test charter also contains notes taken during a test session, such as test ideas, test results, bugs, issues, and observations. A test charter is not used to monitor a

  test process, as it is not a formal metric or report. It is also not used to outline the company test policy, as it is specific to a particular test session and context.

  References:

  ISTQB. Foundation Level Agile Tester Syllabus, Section 2.2.3, page 18; ASTQB Agile Tester Certification Resources, Section 2.2.3, page 18; How to Write an Exploratory Test Charter, Creating an Exploratory Testing Charter, What is Exploratory Testing?.

• Question 87:

  Which of the following is NOT a typical task performed by the tester within an Agile team?

  A. Ensuring all project status meetings are held according to the plan.
  B. Ensuring the appropriate testing tasks are scheduled during iteration planning.
  C. Suggesting improvements in team retrospectives.
  D. Working with business stakeholders to clarify requirements.
  A. Ensuring all project status meetings are held according to the plan.

  ---

  The tester within an Agile team is not responsible for ensuring all project status meetings are held according to the plan. This is typically a task for the Scrum Master, who facilitates the meetings and ensures that the team follows the Agile principles and practices. The tester within an Agile team is responsible for ensuring the appropriate testing tasks are scheduled during iteration planning, suggesting improvements in team retrospectives, and working with business stakeholders to clarify requirements. These are all tasks that contribute to the quality of the software and the testing process, as well as the collaboration and communication within the team and with the customers.

  References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.1, page 171;

• Question 88:

  A Scrum team is performing quality risk analysis during planning for the first iteration. User stories have associated risk items with levels determined by impact and likelihood. For multiple risk items, the user story's risk is the average of individual risk levels. Which of the following statements would you expect most likely to be true?

  A. While the identification of the risk items should be performed by the Product Owner, the assessment of the risk levels should be performed by the whole team
  B. Potential issues with poorly written user stories should not be raised during risk analysis because they could influence how the risk level is determined
  C. Regardless of the risk level, more thorough test techniques should be selected for US-004 since it isthe user story with most associated risk items
  D. An estimation session after the risk analysis should consider only the risk level for effort estimation
  A. While the identification of the risk items should be performed by the Product Owner, the assessment of the risk levels should be performed by the whole team

  ---

  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.

  References:

  CTFL-AT Syllabus v4.0, Section 2.2 Learning Objective (K2) . Understand risk-based testing in Agile

• Question 89:

  Which of the following is NOT a statement of value from the Agile Manifes to?

  A. Working software over comprehensive documentation
  B. Processes and tools over individuals and interactions.
  C. Responding to change over following a plan.
  D. Customer collaboration over contract negotiation.
  B. Processes and tools over individuals and interactions.

  ---

  The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development approach. The four values of the Agile Manifesto are:

  Individuals and interactions over processes and tools

  Working software over comprehensive documentation

  Customer collaboration over contract negotiation

  Responding to change over following a plan

  These values emphasize the importance of human collaboration, working product, customer feedback, and adaptability over rigid processes, extensive documentation, fixed contracts, and predefined plans. The values do not imply that the items on the right are not important, but rather that the items on the left are more important and should be prioritized.

  Therefore, the statement that is NOT a value from the Agile Manifesto is B, as it contradicts the first value of the Agile Manifesto. The correct statement should be Individuals and interactions over processes and tools.

  References:

  ISTQB Foundation Level Agile Tester Extension Syllabus, page 10; ISTQB Agile Tester Sample Exam.

• Question 90:

  Which of the following is an Agile software development approach in which transparency of content and progress of tasks is usually obtained with the visualization of the active tasks and in which iterations are optional?

  A. Scrum
  B. Continuous integration
  C. Kanban
  D. Slack
  C. Kanban

  ---

  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.

  References:

  CTFL-AT Syllabus v4.0, Section 1.2 Learning Objective (K1) . Recognize Agile development approaches