ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 21:

  Which of the following statements about exploratory testing in Agile is TRUE?

  A. It replaces all scripted testing
  B. It is performed only after automated tests have passed
  C. It helps discover issues not covered by predefined test cases
  D. It must follow strict procedural scripts
  C. It helps discover issues not covered by predefined test cases

  ---

  CTFL-AT Section 3.1 describes exploratory testing as simultaneous learning, test design, and execution. Option C matches this definition.

  Option A is incorrect; scripted tests still exist.

  Option B is not required.

  Option D contradicts the exploratory nature.

  References:

  CTFL-AT Syllabus v4.0, Section 3.1

• Question 22:

  Which of the following statements about test-driven development (TDD) and behavior-driven development (BDD) is true?

  A. Both BDD tests and TDD tests are written primarily at the acceptance level, though these tests may also be written at the integration or system levels
  B. TDD tests are focused on the implementation of the software while BDD tests on the exhibited behavior of the software
  C. TDD tests and BDD tests are written by developers, but TDD tests are generally easier for other team members and stakeholders to understand than BDD tests
  D. Specific BDD frameworks can be used to define acceptance criteria based on the role/feature/benefit template ("As a..., I want..., so that...")
  B. TDD tests are focused on the implementation of the software while BDD tests on the exhibited behavior of the software

  ---

  From CTFL-AT Syllabus v4.0, Section 3.3 Behavior-Driven Development, and 3.2 Test-Driven Development: "TDD focuses on writing unit tests that guide the implementation of code." "BDD focuses on writing scenarios that describe the behavior of the software, often using a language that stakeholders can understand."

  Thus, Option B is accurate TDD targets code implementation, BDD targets behavioral expectations.

  Option A is incorrect TDD is at unit level, while BDD is at the acceptance level.

  Option C is false BDD is more readable and accessible for non-technical stakeholders.

  Option D confuses BDD withuser story formats; BDD uses Given-When-Then, not the "As a... I want..." template.

  References:

  CTFL-AT Syllabus v4.0, Sections 3.2 and 3.3 Learning Objective (K2) . Differentiate TDD and BDD practices

• Question 23:

  Which of the following is a benefit of a whole-team approach?

  A. Enables reduction in test duplication as the testers and test engineers function as a single team.
  B. Enables testers to execute their responsibility for quality for the combined team.
  C. Enables the team to focus on solely their separate areas of expertise and responsibility.
  D. Enables the various skill sets within the team to be leveraged to the benefit of the project.
  D. Enables the various skill sets within the team to be leveraged to the benefit of the project.

  ---

  A whole-team approach is a way of working in agile projects where all team members share the responsibility for delivering high-quality software that meets the customer's needs. This means that testers, developers, business analysts, and other roles collaborate closely throughout the project lifecycle, and use their different skills and perspectives to contribute to the quality of the product. A benefit of this approach is that it enables the team to leverage the various skill sets within the team to the benefit of the project, such as testing skills, coding skills, domain knowledge, user experience, etc. This can lead to faster feedback, better communication, higher productivity, and more innovation.

  References: ISTQB. Foundation Level Agile Tester Syllabus1, Section 1.1.1, page 7; ASTQB Agile Tester Certification Resources, Section 1.1.1, page 7.

• Question 24:

  Which of the following statements about Agile retrospectives is true?

  A. Agile retrospectives should be focused mainly on obstructions and hindrances that are outside the control of the team because these issues are more challenging
  B. Traditional projects require feedback from retrospectives; however, Agile retrospectives do not require follow-up activities
  C. Agile retrospectives should be focused on the team members and business representatives, and other participants should not attend or contribute
  D. Agile retrospectives should also provide feedback to the current iteration planning regarding planning accuracy, contents, and the efficiency of the work in the team
  D. Agile retrospectives should also provide feedback to the current iteration planning regarding planning accuracy, contents, and the efficiency of the work in the team

  ---

  From the CTFL-AT Syllabus v4.0, Section 5.1, it states:

  "The team uses the retrospective to review how they worked during the iteration, including planning accuracy and team collaboration, and to identify actionable improvements."

  Thus, Option D is correct retrospectives help reflect on iteration planning accuracy, team dynamics, and efficiency to improve future iterations.

  Option A is incorrect retrospectives aim to focus on what the team can improve, not just on external hindrances.

  Option B is false Agile retrospectives require follow-up, often in the form of action items tracked in the next iteration.

  Option C is incorrect Product Owner and possibly others may contribute, depending on team context.

  References:

  CTFL-AT Syllabus v4.0, Section 5.1 Learning Objective (K2) . Understand retrospective purpose and follow-up actions

• Question 25:

  You are working in a software development company which, for many years, used a sequential development model and was organized into separate departments for each functional group (e.g. business analysts, developers, testers) located within their own office space. Your organization has recently changed to a SCRUM agile framework. Which of the following is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model?

  A. Resilient testing means that the testing process is capable of dealing with rapid changes throughout the development process with test plans being updated during each iteration.
  B. Credibility means that the tester must share information with the stakeholders about the test process so that they find the selected test strategy and testing activities trustworthy.
  C. Cross-functional teamwork means that all team members contribute to testing in various ways. For example, involving people with the test strategy, test planning and execution as well as test reporting.
  D. Co-located teamwork means that all team members, including developers and testers, must sit together in the same office, so they can quickly communicate face-to-face.
  C. Cross-functional teamwork means that all team members contribute to testing in various ways. For example, involving people with the test strategy, test planning and execution as well as test reporting.

  ---

  Cross-functional teamwork is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model. Cross-functional teamwork means that all team members, regardless of their functional roles, 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. All

  team members contribute to testing in various ways, such as:

  Involving people with the test strategy, test planning and execution as well as test reporting. This can help ensure that the testing activities are aligned with the business objectives, the user needs, and the technical requirements. It can also help improve the test coverage, the test quality, and the test efficiency.

  Sharing the responsibility for testing among the team members. This can help reduce the workload and the dependency on a single tester or a testing team. It can also help increase the feedback and the communication among the team members, and foster a culture of quality and learning.

  Leveraging the diverse skills and perspectives of the team members. This can help enhance the test design and the test execution by applying different techniques, tools, and approaches. It can also help identify and address the risks, the issues, and the opportunities for improvement from various angles.

  References:

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

• Question 26:

  A tester wants to ensure that acceptance criteria for a user story are properly testable. Which of the following characteristics is the MOST important for testability?

  A. Acceptance criteria reference system components
  B. Acceptance criteria include measurable and observable outcomes
  C. Acceptance criteria reference stakeholder names
  D. Acceptance criteria include detailed implementation steps
  B. Acceptance criteria include measurable and observable outcomes

  ---

  Section 2.1 of CTFL-AT emphasizes that acceptance criteria must be specific, measurable, and observable to support testability.

  Option B reflects this requirement.

  Option A is irrelevant to testability.

  Option C does not support objective verification.

  Option D is not Agile-aligned; acceptance criteria should state “what”, not “how”.

  References:

  CTFL-AT Syllabus v4.0, Section 2.1

• Question 27:

  Which of the following is a risk that continuous integration introduces?

  A. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
  B. Testers sometimes have too many builds to test, which reduces the quality of testing.
  C. Teams no longer have the ability to run manual tests, as all tests must be automated.
  D. Developer's workload is increased, which can result in a reduction of output.
  B. Testers sometimes have too many builds to test, which reduces the quality of testing.

  ---

  Continuous integration is a practice of integrating code changes frequently and automatically into a shared repository, and running automated tests to verify the integration. Continuous integration can introduce some risks to the testing process, such as:

  Testers sometimes have too many builds to test, which reduces the quality of testing. This can happen when the code changes are too frequent or too large, and the testers do not have enough time or resources to test each build thoroughly. This can lead to missed defects, incomplete test coverage, and reduced confidence in the product quality.

  Testers sometimes have to deal with unstable or broken builds, which affects the testability of the product. This can happen when the code changes introduce errors or conflicts that cause the build to fail or malfunction. This can waste the testers time and effort, and delay the feedback cycle.

  Testers sometimes have to cope with changing requirements and priorities, which affects the test planning and execution. This can happen when the stakeholders or customers provide new or modified requirements or feedback during the development cycle. This can require the testers to adapt their test strategy, test cases, and test data accordingly, and to balance the testing of new features and regression testing of existing features.

  References:

  ISTQB. Foundation Level Agile Tester Syllabus1, Section 2.2.3, page 14; ISTQB. Glossary of Testing Terms2, version 4.0, page 15.

• Question 28:

  In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

  The user story written on the card is:

  "As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

  By applying the 3C concept, which ONE of the following statements is CORRECT?

  A. Conversation should include the acceptance criteria discussion.
  B. The card should contain requirements not the user story.
  C. Product owner has written a user story and confirmation is not needed.
  D. The conversation is not required and the team should start developing.
  A. Conversation should include the acceptance criteria discussion.

  ---

  The 3C concept of user stories consists of three elements: card, conversation, and confirmation. The card is a written description of the user story that captures the essence of the feature or functionality from the user's perspective. The conversation is a dialogue between the product owner and the development team to clarify the details, assumptions, and expectations of the user story. The confirmation is a set of criteria or tests that verify that the user story is implemented correctly and meets the user's

  needs. Therefore, by applying the 3C concept, the correct statement is A, as the conversation should include the acceptance criteria discussion. This will help the team understand the scope, priority, and value of the user story, as well as the conditions of satisfaction that the product owner expects.

  The other statements are incorrect, as they violate the 3C concept. Statement B is wrong, as the card should contain the user story, not the requirements. The user story is a brief and informal way of expressing the user's goal and benefit, while the requirements are more detailed and specific descriptions of how the software should work. The requirements can be added later as part of the conversation or confirmation.

  Statement C is wrong, as the product owner has written a user story, but confirmation is still needed. The confirmation is a vital part of the 3C concept, as it ensures that the user story is testable, measurable, and verifiable. The confirmation also helps avoid ambiguity, misunderstanding, or disagreement between the product owner and the development team.

  Statement D is wrong, as the conversation is required and the team should not start developing without it. The conversation is an essential part of the 3C concept, as it allows the team to ask questions, share ideas, and collaborate with the product owner to refine the user story and reach a shared understanding. The conversation also helps identify the dependencies, risks, and assumptions that may affect the implementation of the user story.

  References:

  ISTQB Foundation Level Agile Tester Syllabus, Section 2.2.1, pages 16–17; Effective User Stories – 3C's and INVEST Guide, Section “The 3 C's (Card, Conversation, Confirmation) of User Stories.”

• Question 29:

  An Agile team is developing a Pay-TV web portal. In Iteration 3, only PayPal and credit card payments are supported. A new user story in Iteration 4 adds payment using credit from a smartcard. Which of the following would you expect to describe valid and relevant acceptance tests for this user story?

  A. Tests to check that payments with insufficient credit charged on the smartcard are successful
  B. Tests to check that payments with sufficient credit charged on the smartcard are given five percent discount are successful
  C. Tests to check that payments with expired credit cards of supported credit card types are unsuccessful
  D. Tests to check that payments with no credit charged on the smartcard will be unsuccessful
  D. Tests to check that payments with no credit charged on the smartcard will be unsuccessful

  ---

  From CTFL-AT Syllabus v4.0, Section 2.1 Acceptance Criteria and Testability, acceptance tests must be directly related to the new functionality described in the user story.

  Option D is correct, it validates the new feature of paying via smartcard credit, specifically handling edge cases(e.g., zero credit).

  Option A is incorrect, payment should fail with insufficient credit.

  Option B introduces requirements not mentioned in the story.

  Option C tests credit card logic, not the new smartcard functionality.

  References:

  CTFL-AT Syllabus v4.0, Section 2.1 Learning Objective (K3) . Derive acceptance tests from user stories

• Question 30:

  Which ONE of the following best describes an Agile Definition of Done (DoD)?

  A. A checklist that ensures a user story meets agreed quality expectations before it can be considered complete
  B. A document describing the project's long-term testing strategy
  C. A list of all bugs that must be fixed by the end of the release
  D. A statement written by the Scrum Master to approve story completion
  A. A checklist that ensures a user story meets agreed quality expectations before it can be considered complete

  ---

  According to CTFL-AT Syllabus Section 2.3, Definition of Done includes quality tasks, testing activities, and criteria required before work is considered complete.

  Option A reflects this.

  Options B, C, and D do not describe the DoD.

  References:

  CTFL-AT Syllabus v4.0, Section 2.3