ISQI CTFL-AT - Questions & Answers

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

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

From CTFL-AT Syllabus v4.0, Section 2.4 Testing and Iterations, it states: "In Agile projects, testing activities are conducted in parallel with development activities within an iteration, unlike traditional models where testing is done after development."
Therefore, Option D is correct, Agile promotes parallel testing, while traditional projects (e.g., V-model) follows equential phases.
Option A is incorrect Agile projects do perform system testing, but it's integrated within iterations.
Option B is misleading while Agile emphasizes lower-level test automation, traditional projects also use automation at various levels.
Option C is partially correct but oversimplifies the process risks are reassessed iteratively, not just once during release planning.

References:
CTFL-AT Syllabus v4.0, Section 2.4 Learning Objective (K2) . Compare Agile vs traditional testing activities

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.

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.

From CTFL-AT Syllabus v4.0, Section 2.1 Acceptance Criteria and Testability, it states: "Tests should directly address the acceptance criteria defined for a user story. Testers evaluate if the implemented feature meets the criteria, often using quantitative data like number of steps, time taken, or interaction patterns."
The acceptance criterion specifically refers to minimizing steps during checkout, so Option D is most directly aligned with what needs to be tested.
Options A, B, and Care unrelated to the acceptance criterion's goal of reducing abandonment due to complex checkout.

References:
CTFL-AT Syllabus v4.0, Section 2.1 Learning Objective (K2) . Understand testability of acceptance criteria

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

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.

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

Scrum is an agile development approach that incorporates the following practices: a project is divided into iterations called sprints, which are typically 2-4 weeks long each sprint starts with a planning meeting, where the team selects a subset of user stories from the product backlog to work on each sprint ends with a review meeting, where the team demonstrates the potentially releasable /shippable product increment to the stakeholders and collects feedback each sprint also includes a retrospective meeting, where the team reflects on the process and identifies areas for improvement.

References:
1: ISTQB® Foundation Level Agile Tester Syllabus, Section 2.1, Agile Software Development
2: ASTQB Agile Tester Certification Resources, Section 2.1, Agile Software Development
3: What is Agile? | Atlassian