ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 71:

  Which ONE of the following is an example of a typical Business-oriented work product?

  A. The released product.
  B. Acceptance testing entry criteria.
  C. A user manual.
  D. Usability testing test results.
  C. A user manual.

  ---

  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 Syllabus1, Section 1.2.1, page 10; ASTQB Agile Tester Certification Resources2, Section 1.2.1, page 10.

• Question 72:

  Which two of the following statements are CORRECT with regards to test automation on agile projects?

  1) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

  2) It would be very difficult to ensure high quality in an agile project without test automation.

  3) Automated acceptance tests are run regularly as part of the continuous integration full system build.

  4) Automated regression suites are only run for the final release of code.

  5) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

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

  ---

  Test automation is essential for agile projects, as it enables fast and frequent feedback on the quality of the product. Without test automation, it would be very difficult to ensure high quality in an agile project, as manual testing would be too slow and costly to keep up with the pace of development. Automated acceptance tests are one of the key types of test automation on agile projects, as they verify that the user stories are implemented correctly and that the product meets the customer's expectations. Automated acceptance tests are run regularly as part of the continuous integration full system build, and the results provide feedback on the overall product quality. Therefore, statements 2 and 5 are correct with regards to test automation on agile projects.

  References:

  1: ISTQB. Foundation Level Agile Tester Syllabus, Section 3.3.1, Test Automation;

  2: ASTQB Agile Tester Certification Resources, Section 3.3.1, Test Automation

• Question 73:

  Which of the following is the best example of a testable acceptance criterion for test-related activities?

  A. The web application shall provide a response time lower than one second for 95% of the webpages when 100 concurrent users are working on it
  B. 100% of the source code must be statically analyzed against some of the known major security vulnerabilities and no errors/warnings must be reported
  C. The application's user interface for the checkout process shall be clear and intuitive to the users
  D. The application shall calculate the volume of the solid shapes (cones, pyramids) with reasonable accuracy
  A. The web application shall provide a response time lower than one second for 95% of the webpages when 100 concurrent users are working on it

  ---

  From CTFL-AT Syllabus v4.0, Section 2.1:

  "Acceptance criteria should be testable, meaning they should define expected behavior or measurable outcomes that can be verified."

  Option A is testable because it includes specific, measurable conditions: response time, user load, and percentage of pages.

  Option B is vague about which vulnerabilities and how errors are defined.

  Option C uses subjective language ("clear and intuitive").

  Option D is vague about what "reasonable accuracy" means.

  References:

  CTFL-AT Syllabus v4.0, Section 2.1 Learning Objective (K2) . Identify examples of testable vs. non-testable acceptance criteria

• Question 74:

  Which of the following statements is true?

  A. Early and frequent feedback in Agile projects helps maintain a uniform distribution of defects through the code and thus avoid defect clustering
  B. Early and frequent feedback in Agile projects allows the team to find a greater number of defects at the unit test level than in non-Agile projects
  C. Early and frequent feedback in Agile projects provides earlier information about the stability of the software product but not about its quality
  D. Early and frequent feedback in Agile projects allows the team to provide customers with products that better meet their requirements sooner
  D. Early and frequent feedback in Agile projects allows the team to provide customers with products that better meet their requirements sooner

  ---

  From the CTFL-AT Syllabus v4.0, Section 2.3 The Role of Feedback, it explains: "Agile development promotes early and continuous feedback, which leads to the development of a product that better meets customer needs and expectations."

  Also: "Frequent feedback loops support the team in identifying and resolving issues earlier, improving both the product quality and customer satisfaction."

  Therefore, Option D is the most accurate reflection of the true benefit of early and frequent feedback in Agile environments.

  Option A incorrectly implies Agile feedback redistributes defect clustering, which is not a recognized principle.

  Option B makes an unverifiable claim about defect volume at the unit level. Agile encourages unit testing, but this comparison is not substantiated in the syllabus.

  Option C is incorrect because feedback provides both stability and quality indicators early on.

  References:

  CTFL-AT Syllabus v4.0, Section 2.3 Learning Objective (K2) . Understand the role of feedback in Agile projects

• Question 75:

  Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?

  A. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
  B. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
  C. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
  D. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
  D. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.

  ---

  The Agile processes promote early and frequent feedback from the customers, users, testers, developers, and other stakeholders involved in the project. This feedback helps to ensure that the product meets the expectations and needs of the customers and users, and that the development process is continuously improved and adapted to the changing requirements and environment. However, increasing the frequency of feedback and communication does not eliminate all communication problems, as there may still be issues such as misunderstandings, misinterpretations, conflicts, or cultural differences that need to be resolved. Therefore, the statement D is not true, as it implies that communication problems are completely avoided by the Agile processes.

  References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9;

• Question 76:

  Which of the following activities would you expect most likely to be performed during daily stand-up meetings?

  A. Discussing what did not work well during the previous iteration
  B. Highlighting blocking issues that are impeding the test progress
  C. Identifying specific quality risks associated with the next iteration
  D. Creating acceptance tests for the user stories selected for the current iteration
  B. Highlighting blocking issues that are impeding the test progress

  ---

  From the CTFL-AT Syllabus v4.0, Section 5.2 Daily Stand-Ups, it states:

  “The daily stand-up is a short meeting used to discuss progress, plans for the day, and any impediments that are blocking progress.”

  Therefore, Option B is correct. Highlighting impediments/blockers is a key goal of the daily stand-up.

  Option A is a retrospective activity.

  Option C is done during planning or risk assessment, not the daily meeting.

  Option D is part of iteration planning, not the stand-up.

  References:

  CTFL-AT Syllabus v4.0, Section 5.2, Learning Objective (K1): Recall daily stand-up purpose and format.

• Question 77:

  In Agile projects, which of the following approaches would result in the best compromise for preserving independence of testers and for allowing testers to have a good understanding of the product as well as good relationships with other team members?

  A. Having independent separate test teams where testers are assigned to Agile teams on-demand during the final days of each iteration
  B. Having independent separate test teams where testers are assigned to Agile teams on a long-term basis, at the beginning of an Agile project
  C. Having only Agile teams where testers are integral parts and where they perform many of the testing tasks, without having an independent test team
  D. Having independent separate test teams where all of the testers work separately from developers without being assigned to Agile teams
  B. Having independent separate test teams where testers are assigned to Agile teams on a long-term basis, at the beginning of an Agile project

  ---

  From CTFL-AT Syllabus v4.0, Section 2.5 Testers and Independence, it states: "Testers may be assigned to Agile teams on a permanent or rotating basis. While full independence is compromised, this setup allows for better collaboration and understanding of the product, while still maintaining some degree of independence."

  Thus, Option B is the most accurate long-term embedded testers support Agile collaboration while preservingpartial independence.

  Option A leads to late involvement, which contradicts Agile principles.

  Option C sacrifices independence entirely.

  Option D is traditional and contrary to Agile values of collaboration.

  References:

  CTFL-AT Syllabus v4.0, Section 2.5 Learning Objective (K2) . Understand approaches to preserving test independence in Agile

• Question 78:

  During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?

  A. The build process was slow and this often caused delays waiting for the build to complete.
  B. For the last sprint the estimated and actual effort were much higher than the team capacity.
  C. The automation tests failed frequently without any logs to help in debugging the failure reason.
  D. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
  D. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.

  ---

  According to the ISTQB Tester Foundation Level Agile Tester syllabus, a retrospective is a meeting held at the end of each iteration or release, where the agile team reflects on what went well and what can be improved in their processes, practices, and interactions. The purpose of a retrospective is to identify and implement actions for continuous improvement, and to foster a culture of learning and collaboration. Therefore, the items that would be the most effective to generate discussions on process

  improvement are those that are related to the team's performance, challenges, feedback, and suggestions.

  Option D is the least effective item to generate discussions on process improvement, as it is a personal attack on one of the team members, and it does not offer any constructive feedback or solution. This kind of item can create a negative and hostile atmosphere in the retrospective, and damage the trust and respect among the team members.

  Option A is an effective item to generate discussions on process improvement, as it identifies a problem with the build process that affects the team's efficiency and quality, and it can lead to finding ways to optimize the build process or to mitigate the delays.

  Option B is also an effective item to generate discussions on process improvement, as it reveals a discrepancy between the team's estimation and actual effort, and it can lead to analyzing the root causes of the deviation and to improving the estimation techniques or the team's capacity.

  Option C is also an effective item to generate discussions on process improvement, as it highlights a weakness in the automation tests that hinders the team's ability to debug and fix the failures, and it can lead to enhancing the automation tests with better logging mechanisms or to reviewing the automation strategy.

  References:

  ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.1, page 14; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.2, page 15; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.1, page 16; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.2, page 17.

• Question 79:

  Which statement about an Agile task board is CORRECT?

  A. It provides detailed visual representation of the whole team's status.
  B. It is updated once at the end of each iteration.
  C. Only in progress tasks are shown on the task board.
  D. It is a detailed visual representation of the status of testing.
  A. It provides detailed visual representation of the whole team's status.

  ---

  An Agile task board is a visual framework to display and sync up on the tasks moving between production steps. It is usually applied to the two most popular Agile development frameworks Kanban and Scrum. Used by software developers and project managers, an Agile board helps manage workloads in a flexible, transparent, and iterative way. An Agile task board provides a detailed visual representation of the whole team's status, showing which tasks remain to be started, which are in progress, and which are done. It also helps to track the progress of the current sprint, identify bottlenecks, and facilitate collaboration and communication among team members.

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

• Question 80:

  Which of the following BEST describes the relationship between TDD and code quality?

  A. TDD decreases code quality because it increases development time
  B. TDD increases code quality by enforcing small, testable units
  C. TDD prevents refactoring entirely
  D. TDD ensures full system-level test coverage
  B. TDD increases code quality by enforcing small, testable units

  ---

  CTFL-AT Section 3.2 describes TDD as enabling cleaner design, small units, and frequent refactoring, improving code quality.

  Option A is incorrect; quality increases long-term.

  Option C is false; refactoring is integral.

  Option D is incorrect; TDD focuses on unit tests.

  References:

  CTFL-AT Syllabus v4.0, Section 3.2