ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 61:

  Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?

  A. While developers develop automated unit test scripts, testers write automated system level tests.
  B. Testers replace developers in writing unit test automation scripts.
  C. Developers write acceptance criteria and test cases, to gether with testers.
  D. Developers and testers may work as a pair to develop and test a feature.
  B. Testers replace developers in writing unit test automation scripts.

  ---

  Testers replace developers in writing unit test automation scripts. Comprehensive : The integration of development and testing activities in Agile projects is based on the principle of cross-functional teamwork, where all team members collaborate and share their skills and knowledge to achieve a common goal. In the context of testing, this means that testing is not seen as a separate activity or phase, but as an integral part of the development process. Therefore, the following sentences are correct:

  While developers develop automated unit test scripts, testers write automated system level tests. This is an example of how developers and testers can work in parallel and complement each other's testing efforts. Developers can focus on testing the internal quality of the code, while testers can focus on testing the external quality of the product.

  Developers write acceptance criteria and test cases, together with testers. This is an example of how developers and testers can work together to define and verify the user requirements and expectations. Developers can provide their technical expertise and input, while testers can provide their business and user perspective and feedback.

  Developers and testers may work as a pair to develop and test a feature. This is an example of how developers and testers can work closely and interactively to deliver a feature. Developers and testers can exchange ideas, suggestions, and information, and support each other in the coding and testing tasks.

  The following sentence is incorrect:

  Testers replace developers in writing unit test automation scripts. This is not a valid example of the integration of development and testing activities in Agile projects, because it implies that testers take over the responsibility of developers, rather than collaborate with them. Testers should not replace developers in writing unit test automation scripts, because developers have more knowledge and experience in coding and debugging, and because unit testing is an essential part of the development process.

  Testers should instead work with developers to ensure that the unit test automation scripts are adequate, effective, and maintainable.

  References:

  ISTQB. Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB. Glossary of Testing Terms2, version 4.0, pages 16 and 55.

• Question 62:

  Which of the following statements best describes how development and testing activities are integrated in Agile projects?

  A. Testers can start testing a user story only when it is "done", meaning when the coding of that user story is finished
  B. The performances of developers are measured on implemented story points while the performances of testers on executed test cases and defect counts
  C. Agile teams often adopt exploratory testing, where test design and test execution occur at the same time, usually guided by a test charter
  D. Both business stakeholders and testers can test user stories during their development within an iteration to provide fast feedback to the developers
  D. Both business stakeholders and testers can test user stories during their development within an iteration to provide fast feedback to the developers

  ---

  From CTFL-AT Syllabus v4.0, Section 2.4 Testing and Iterations, it states: "In Agile projects, developers and testers work together to ensure the correct functionality is delivered during the iteration. Business representatives and testers may also validate the software during development to provide quick feedback."

  This confirms that Option D is correct collaborative testingby stakeholders and testers during development is a core Agile practice.

  Option A is incorrect testing doesnot waitfor "done"; it occurs concurrently with development.

  Option B misrepresents Agile performance isn't based on metrics like defect counts.

  Option C is true in general, butdoes not directly answer the integration of testing and development activities.

  References:

  CTFL-AT Syllabus v4.0, Section 2.4 Learning Objective (K2) . Understand integration of development and testing in Agile

• Question 63:

  What is the main benefit of the Test Pyramid?

  A. It means testing is involved early in the development cycle.
  B. It helps in evaluating the amount of test cases needed.
  C. It shows complexity of testing activities.
  D. It acts as a metric for testing progress.
  B. It helps in evaluating the amount of test cases needed.

  ---

  The Test Pyramid is a model for organizing tests in a way to make the process of testing faster, efficient and cost-effective. This model focusses on getting maximum functional testing getting covered by faster and less brittle tests like Unit and API tests. The main benefit of the Test Pyramid is that it helps in evaluating the amount of test cases needed for each level of testing. The Test Pyramid suggests that the number of test cases should decrease as we move up the pyramid, from unit tests to integration

  tests to end-to-end tests. This is because unit tests are more granular, isolated, and easy to write and maintain, while end-to-end tests are more complex, dependent, and brittle. The Test Pyramid also helps in balancing the test coverage and the test execution time, as unit tests provide high coverage and low execution time, while end-to-end tests provide low coverage and high execution time. By following the Test Pyramid, teams can optimize their testing efforts and resources, and ensure that they have a

  sufficient and effective test suite for their software.

  References:

  ISTQB. Foundation Level Agile Tester Syllabus, Section 2.2.1, page 16; ASTQB Agile Tester Certification Resources, Section 2.2.1, page 16; What is Test Pyramid : Getting started with Test Automation Pyramid, The Practical Test Pyramid - Martin Fowler, Testing Pyramid: What Is It and How To Use It | Solvd.

• Question 64:

  A tester is participating in quality risk analysis for an upcoming iteration. Which of the following contributes MOST effectively to the analysis?

  A. Defining detailed UI layout requirements
  B. Considering both impact and likelihood of potential failures
  C. Estimating task durations for development
  D. Identifying the number of test cases required per story
  B. Considering both impact and likelihood of potential failures

  ---

  CTFL-AT Section 2.2 defines risk as impact × likelihood.

  Option B directly supports assessing risk levels to guide testing.

  Options A, C, and D do not directly support risk analysis per the syllabus.

  References:

  CTFL-AT Syllabus v4.0, Section 2.2

• Question 65:

  Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan. In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?

  A. Exploratory Testing
  B. Prototype Testing
  C. Performance Testing
  D. Functional Testing
  A. Exploratory Testing

  ---

  Exploratory testing is a type of testing that involves simultaneous learning, test design, and test execution. It is suitable for Quadrant 3 because it is business facing and product critique, meaning that it focuses on the user's perspective and the quality attributes of the product. Exploratory testing can help discover new risks, requirements, and defects that may not be covered by other test levels and test types. It can also provide feedback on the usability, functionality, and reliability of the product.

  References:

  ISTQB. Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB. Glossary of Testing Terms2, version 4.0, page 23.

• Question 66:

  Which of the following statements best describes Agile software development?

  A. Agile software development is a software development approach whereby lines of code (production and /or test) of a component are written by two programmers sitting at a single computer
  B. Agile software development tends to break a project into a number of iterations, where each iteration represents a separate phase of sequential development and thus in which testing is performed during the last iteration
  C. Agile software development tends to adopt an iterative incremental lifecycle, where requirements and solutions evolve through collaboration between self-organizing and cross-functional teams
  D. Agile software development tends to break a project into a series of increments, each of which delivers a portion of functionality through a series of mini-Waterfalls where all phases of the Waterfall are completed before proceeding to the next increment
  C. Agile software development tends to adopt an iterative incremental lifecycle, where requirements and solutions evolve through collaboration between self-organizing and cross-functional teams

  ---

  From the ISTQB CTFL-AT Syllabus v4.0, Section 1.1 Agile Software Development and the Agile Manifes to, 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 asequential (Waterfall-like) iteration structure where testing is delayed.

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

  References:

  CTFL-AT Syllabus v4.0, Section 1.1 Agile Manifes to Principles Learning Objective (K1) . Identify Agile Software Development Approaches

• Question 67:

  What is the definition of agile software development?

  A. Testing carried out informally where no formal test preparation or execution takes place, no recognized test design technique is used and there are no expectations for results.
  B. A group of software development methodologies based on iterative incremental development with self-organizing cross-functional teams who cooperate to define requirements and to implement the solution.
  C. A framework to describe the software development lifecycle activities from requirements specification to maintenance where test planning of the various test levels is done as soon as the test basis is ready
  D. A way of developing software where the test cases are developed, and often automated, before the software under test is developed.
  B. A group of software development methodologies based on iterative incremental development with self-organizing cross-functional teams who cooperate to define requirements and to implement the solution.

  ---

  Agile software development is a term that encompasses a group of software development methodologies that are based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Agile methods promote adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourage rapid and flexible response to change. Some examples of agile methods are Scrum, Extreme Programming (XP), Kanban, and Lean Software Development.

  References: ISTQB. Foundation Level Agile Tester Syllabus, Version 2014, Section 1.1.1 ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 1, Section 1.1.1

• Question 68:

  Which of the following statements about the testing quadrants model is true?

  A. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) represents a different test level (Q1 = Unit, Q2 = Integration, Q3 = System, and Q4 = Acceptance) and describes the different test types that shall be performed by Agile teams in that test level for an Agile project
  B. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants are numbered to describe the order in which the associated test types and test levels shall be performed in an Agile project (Q1 first, Q4 last)
  C. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants can be used by Agile teams and other stakeholders to ensure that all important test types and test levels are included in an Agile project
  D. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants are numbered to describe the risk level associated with the test types (Q1 = least risky, Q4 = most risky)
  C. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants can be used by Agile teams and other stakeholders to ensure that all important test types and test levels are included in an Agile project

  ---

  From CTFL-AT Syllabus v4.0, Section 3.4 The Testing Quadrants, it states: "The Agile testing quadrants are used to ensure that the team considers all important test types and levels during an Agile project. The quadrants categorize tests by their purpose (support development, critique the product) and by the type of feedback (business-facing vs technology-facing)."

  Thus, Option C correctly reflects the use and purpose of the quadrants as aguidance tool, not a fixed sequence or hierarchy.

  Option A and B are incorrect the quadrants are not mapped to strict levels or chronological order.

  Option D is false risk is not the basis for quadrant numbering.

  References:

  CTFL-AT Syllabus v4.0, Section 3.4 Learning Objective (K2) . Understand the Agile testing quadrants

• Question 69:

  Which of the following statements about Agile software development approaches is true?

  A. Communication, simplicity, feedback, courage, and respect are the five fundamental values of Kanban to guide development
  B. Scrum does not provide guidance on how development has to be done in a Scrum project but prescribes the adoption of specific testing techniques
  C. In Kanban, transparency of content and progress of tasks is usually done with the visualization of the active tasks, for example on a public whiteboard
  D. Scrum is an Agile management framework that defines three roles: the Scrum Owner, the Product Master, and the Development Team
  C. In Kanban, transparency of content and progress of tasks is usually done with the visualization of the active tasks, for example on a public whiteboard

  ---

  From the ISTQB CTFL-AT Syllabus v4.0, Section 1.2 The 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 supports Option C, where Kanban boards are used for visualizing active tasks increasing transparency and progress visibility. Let's clarify the other options:

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

  Option B: Scrum does not prescribe specific testing techniques, but it also does not dictate how development must be done, which makes this atrick answer that's partially true but not complete or precise enough to be correct.

  Option D: The roles are incorrectly named. The correct Scrum roles are: Product Owner, Scrum Master, Developers (Development Team is no longer a formal term post-2020 Scrum Guide)

  References:

  CTFL-AT Syllabus v4.0, Section 1.2

  Scrum Guide 2020 . Official Roles

  Learning Objective (K1) . Recognize common Agile development practices

• Question 70:

  Which of the following would provide the MOST independence for testers working with agile teams?

  A. Testers are fully embedded in each Agile team to perform many of the testing tasks.
  B. 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.
  C. Testers from an independent test team are assigned on-demand for the final days of each sprint.
  D. Testers from an independent test team are assigned to the Agile team at the beginning of the project, returning for re-assignment to a new agile team.
  B. 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.

  ---

  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.