ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 31:

  Consider the following acceptance criterion associated to a user story:

  "A maximum of 0.0002 failures per hour in the specified operational conditions over at least ten days of testing must be achieved."

  Which of the following aspects of testability is best described in this acceptance criterion?

  A. Scenarios
  B. Functional behavior
  C. External interfaces
  D. Quality characteristics
  D. Quality characteristics

  ---

  From CTFL-AT Syllabus v4.0, Section 2.1 Acceptance Criteria and Testability, and Section 3.1:

  "Acceptance criteria may also address non-functional quality characteristics such as reliability, performance, and usability."

  The criterion referencesfailure rate over time, which is areliability attribute, making

  Option D (Quality characteristics) the correct answer.

  Option A (Scenarios) refers to usage paths.

  Option B refers to functional correctness.

  Option C refers to interface interaction points.

  References:

  CTFL-AT Syllabus v4.0, Sections 2.1, 3.1 Learning Objective (K2) . Understand testability related to quality characteristics

• Question 32:

  Which of the following statements about the Planning poker test estimate technique are CORRECT?

  1) Planning poker is a consensus based technique using a deck of cards.

  2) A low test estimate usually means the story should be broken down into multiple smaller stories.

  3) A high test estimate usually means the story should be broken down into multiple smaller stories.

  4) One poker round is played and then consensus has to be reached.

  5) The risk level of each backlog item should be decided before the poker session.

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

  ---

  Planning poker is a consensus-based technique for agile estimation, using a deck of cards with predefined numerical values, usually based on the Fibonacci sequence or a modified version. Therefore, statement 1 is correct. A high test estimate usually means that the user story or task is too complex, ambiguous, or risky, and should be broken down into multiple smaller stories that are easier to understand and estimate. Therefore, statement 3 is correct. The risk level of each backlog item should be decided before the poker session, as it can affect the estimation process and the prioritization of the work. Therefore, statement 5 is correct. Statement 2 is incorrect, as a low test estimate usually means that the user story or task is simple, clear, and well-defined, and does not need to be broken down further. Statement 4 is incorrect, as planning poker can involve multiple rounds of estimation, reveal, and discussion, until the team reaches a consensus or agrees to defer the item.

  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;

  3: Planning Poker: An Agile Estimating and Planning Technique;

  4: Planning poker: The all-in strategy for Agile estimation - Asana

• Question 33:

  Which of the following statements best describes test-driven development?

  A. A way of developing software where the test cases are developed, and often automated, before the software to run those test cases has been written
  B. A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects)
  C. An approach to software development based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams
  D. A way of testing software where test design and test execution occur at the same time, guided by a test charter during time-boxed testing sessions
  A. A way of developing software where the test cases are developed, and often automated, before the software to run those test cases has been written

  ---

  From CTFL-AT Syllabus v4.0, Section 3.2 Test-Driven Development, it states: "Test-Driven Development (TDD) is a practice where test cases are written before the code is developed.

  Typically, these tests are automated, and the code is written to make the tests pass."

  This directly matches

  Option A, making it the correct and complete answer.

  Let's review the other options:

  Option B describes a test strategy, not TDD.

  Option C is a definition of Agile software development, not TDD.

  Option D describes exploratory testing, not TDD.

  References:

  CTFL-AT Syllabus v4.0, Section 3.2 Learning Objective (K2) . Understand the principles of test-driven development

• Question 34:

  You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

  The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

  A User Story for the Operator-Instructions module is as follows:

  "As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

  The following is a list of risks identified for this story, with assigned probability and impact.

  A. Operators will not read the instructions and will try various switches and buttons until something works. Probability: Low. Impact: Low
  B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
  C. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
  D. A small child may try to steam milk. Probability: High. Impact: Low
  B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High

  ---

  Risk-based testing is a technique that prioritizes testing activities based on the level of risk associated with each feature or requirement. The level of risk is usually calculated by multiplying the probability and impact of each risk. The higher the risk level, the more testing effort should be allocated to mitigate the risk.

  In this case, the risk level for each option is as follows: Option A: Risk level = Low × Low = Low Option B: Risk level = Low × High = Medium Option C: Risk level = High × High = High Option D: Risk level = High × Low = Medium

  Therefore, the highest risk level is C, followed by B and D, and then A. The user story for the Operator-Instructions module should be tested according to this risk order, starting with C, then B, then D, and finally A. Hence, the answer is B, as it is the second-highest risk level and should be tested after C.

  References: ISTQB Foundation Level Agile Tester Extension Syllabus, page 16; ISTQB Agile Tester Sample Exam.

• Question 35:

  A tester identifies that acceptance criteria for a user story are ambiguous. What is the BEST next step?

  A. Rewrite the user story alone
  B. Raise the issue during the next retrospective
  C. Collaborate with the Product Owner and team to clarify criteria
  D. Proceed with testing based on assumptions
  C. Collaborate with the Product Owner and team to clarify criteria

  ---

  From CTFL-AT Section 1.2 and 2.1:

  Agile emphasizes collaboration to resolve ambiguities early.

  Option A violates whole-team collaboration.

  Option B delays resolution.

  Option D risks invalid results.

  References:

  CTFL-AT Syllabus v4.0, Sections 1.2–2.1

• Question 36:

  Which of the following statements would you expect least likely to be true?

  A. In Agile projects, where an independent test team works in parallel with Agile teams, the independent test team is usually expected to work on functional testing while Agile teams on non-functional testing
  B. In Agile projects where an independent test team works in parallel with Agile teams, the independent test team can work on long-term and/or non-sprint activities such as developing automated test tools
  C. Having independent test teams working in parallel with Agile teams can be required for Agile projects that have to deal with regulatory compliance requirements and complex domains
  D. Having independent test teams working in parallel with Agile teams can be an option when scaling Agile software development, for example when an independent test team supports multiple Agile teams
  A. In Agile projects, where an independent test team works in parallel with Agile teams, the independent test team is usually expected to work on functional testing while Agile teams on non-functional testing

  ---

  From the CTFL-AT Syllabus v4.0, Section 2.5 Testers and Independence, it explains:

  “An independent test team may be used in parallel to Agile teams to support non-sprint activities such as performance testing, test tool development, or testing in regulated environments.”

  However, assigning functional testing to independent teams while Agile teams handle non-functional work is the opposite of common practice. Agile teams typically focus on functional testing, while specialized non-functional or compliance testing may be handled externally.

  Therefore, Option A is least likely to be true.

  References:

  CTFL-AT Syllabus v4.0, Section 2.5 Learning Objective (K2). Identify roles of independent test teams in Agile contexts

• Question 37:

  Which of the following statements about the whole-team approach would you expect most likely to be true?

  A. The whole-team approach is a consensus-based approach for estimating, mostly used to estimate the relative size of user stories
  B. The whole-team approach helps ensure testers, developers and the business work together to ensure that the desired quality levels are achieved
  C. The whole-team approach is consistent with the "power of three" concept for which a user story is the conjunction of three elements (card, conversation, confirmation)
  D. The whole-team approach tends to advocate the idea of team members being "generalists" without having deep skills in specific disciplines
  B. The whole-team approach helps ensure testers, developers and the business work together to ensure that the desired quality levels are achieved

  ---

  From the CTFL-AT Syllabus v4.0, Section 1.3 The Whole-Team Approach, it states: "The whole-team approach involves all team members (including developers, testers, and business representatives) working together as a team, sharing responsibility for the quality of the product."

  It also says:

  "In Agile projects, the whole-team approach promotes collaboration and communication across roles to achieve common goals, including quality assurance."

  Thus, Option B is correct, as it captures the collaborative nature and shared responsibility that the whole-team approach aims to foster.

  Option A refers to Planning Poker or relative estimation, not directly the whole-team concept.

  Option C describes the"Three Cs" (Card, Conversation, Confirmation) model of user stories, not the whole-team approach specifically.

  Option D misinterprets Agile; while team members are encouraged to be cross-functional, deep expertise is still valued, and "generalist only" is not a requirement of the whole-team approach.

  References:

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

• Question 38:

  A tester is preparing acceptance tests for the following user story:

  “As a registered user, I want to reset my password using a verification code sent to my email.”

  Which of the following acceptance tests is the MOST appropriate?

  A. Verify that users can log in with social media accounts
  B. Verify that users receive a verification code when initiating password reset
  C. Verify that the password policy requires at least two special characters
  D. Verify that the system logs failed login attempts
  B. Verify that users receive a verification code when initiating password reset

  ---

  From CTFL-AT Syllabus v4.0, Section 2.1 on Acceptance Criteria and Testability:

  Acceptance tests must directly validate behavior described in the user story.

  Option B tests the core functionality: sending a verification code for password reset.

  Option A relates to login methods, not password reset.

  Option C tests password policy but is not part of this story.

  Option D concerns security logging, which is unrelated.

  References:

  CTFL-AT Syllabus v4.0, Section 2.1

  Learning Objective (K3) – Derive acceptance tests from user stories

• Question 39:

  Which of the following statements describes Configuration Management?

  A. Configuration management is a test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned
  B. Configuration management represents a method for measuring and managing session-based testing, where a session is an uninterrupted period of testing which could last from 60 to 120 minutes
  C. Configuration management consists of all of the test design techniques in which test cases are designed to execute all possible discrete combinations of any set of a specified number of configuration elements
  D. Configuration management aims to identify and document some characteristics of a configuration item, control changes to those characteristics, and record and report change processing and implementation status
  D. Configuration management aims to identify and document some characteristics of a configuration item, control changes to those characteristics, and record and report change processing and implementation status

  ---

  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.

  References:

  ISTQB Glossary (aligned with CTFL-AT)

  Learning Objective (K1) . Recall basic concepts of configuration management

• Question 40:

  Which of the following sentences related to Risk-based testing is CORRECT?

  A. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
  B. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
  C. Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
  D. Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
  D. Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.

  ---

  Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories. User stories are short descriptions of features or functionalities that are valuable to the customers or users. They help to define the scope and priority of the work in each iteration. By breaking down the work into user stories, the Agile team can identify the potential risks associated with each story, such as technical complexity, business criticality, or user feedback. The team can then prioritize the testing effort based on the risk level of each story, ensuring that the most important and risky features are tested first and thoroughly. Risk-based testing also helps to optimize the testing time and resources, as the team can focus on testing the most relevant aspects of the software, rather than testing everything equally.

  References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 181;