Free iSQI CTFL-AT Practice Exam with Questions & Answers

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 5.1 and 5.3:

"Testers, like all team members, participate in retrospectives and are encouraged to suggest improvements to team processes and product quality."

SoOption Ais correct. Testersactively engagein retrospectives andsuggest improvementsbased on their testing experience.

Option BandCrefer toScrum Master responsibilities.

Option Dis the responsibility of theProduct Owner.

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 1.2Fundamentals of Agile Software Development, it states:

"Kanban is a lean approach that uses visualization (typically via a task board) to manage work in progress and improve workflow. Unlike Scrum, iterations in Kanban are optional."

Thus,Option C (Kanban)is correct. It emphasizesvisualizationand doesnot require fixed-length iterations.

Option A (Scrum)is iteration-based.

Option B (Continuous integration)is a practice, not a development approach.

Option D (Slack)is a communication tool, not a methodology.

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.

 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.

Comprehensive and Detailed Explanation From Exact Extract:

From theCTFL-AT Syllabus v4.0, Section 4.2Continuous Integration, it states:

"Continuous integration involves integrating code into a shared repository several times a day. Each integration is verified by an automated build and automated tests."

Hence,Option D—at least once a day— correctly reflects best practice in continuous integration.

Option A(once per iteration) andB,Care far too infrequent to meet the goals of CI.

The objective is to detect integration issuesearly and often, which is only achievable throughdaily (or more frequent)integrations.

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 5.4Progress Tracking, it explains:

"Burndown charts track completed story points, which are only counted when the entire user story is 'done'."

SinceT3 and T4 are not complete, and the user story is only complete whenall its tasks are done, thestory points are not yet burned. So,Option Cis correct.

Option Ais incorrect —partial completiondoes not burn partial story points.

Option Bmisrepresents the chart’s purpose —story pointsremain the unit.

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 2.4Testing 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 Dis correct — Agile promotesparallel testing, while traditional projects (e.g., V-model) followsequential phases.

Option Ais incorrect — Agile projectsdo perform system testing, but it's integrated within iterations.

Option Bis misleading — while Agile emphasizeslower-level test automation, traditional projects also use automation at various levels.

Option Cis partially correct but oversimplifies the process —risks are reassessed iteratively, not just once during release planning.

Comprehensive and Detailed Explanation From Exact Extract:

FromISTQB 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 Dis the formal and accurate definition ofConfiguration Management.

Option Adescribestest control, not configuration management.

Option Brefers tosession-based testing, unrelated to configuration management.

Option Crefers tocombinatorial test design, not configuration control.

The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development approach12. The four values of the Agile Manifesto are12:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

These values emphasize the importance of human collaboration, working product, customer feedback, and adaptability over rigid processes, extensive documentation, fixed contracts, and predefined plans. The values do not imply that the items on the right are not important, but rather that the items on the left are more important and should be prioritized.

Therefore, the statement that is NOT a value from the Agile Manifesto is B, as it contradicts the first value of the Agile Manifesto. The correct statement should be “Individuals and interactions over processes and tools”. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 1.

Acceptance test criteria are the conditions that a user story must satisfy to be accepted by the customer or the stakeholder. They are usually derived from the user story and its acceptance scenarios, and they should cover the functional and non-functional requirements of the user story. Acceptance test criteria should be clear, concise, testable, and agreed upon by the team and the customer or the stakeholder.

In this case, the user story describes the business rule for approving a loan request based on the customer’s income, repayment history, and loan amount. The user story also specifies the roles of the customer assistant and the bank manager in the process. Therefore, the acceptance test criteria should verify that the user story is implemented correctly and that the system behaves as expected for different scenarios and inputs.

The following test cases can be treated as acceptance test criteria for the above user story:

As a customer assistant I can log in to the system and check the history of the customer account for the last year. This test case verifies that the customer assistant can access the system and view the customer’s income information, which is one of the factors for approving the loan request.

As a customer assistant I can log in to the system and check the history of the customer debts and repayments. This test case verifies that the customer assistant can access the system and view the customer’s repayment history, which is another factor for approving the loan request.

As a bank manager I can log in to the system and receive the information of all requests waiting for approval. This test case verifies that the bank manager can access the system and see the list of loan requests that have been prepared by the customer assistant, and that the system provides the necessary information for each request.

As a bank manager I can log in to the system and decide whether to approve a loan for a customer. This test case verifies that the bank manager can access the system and perform the approval action for a loan request, and that the system applies the business rule correctly and updates the status of the request accordingly.

The following test cases cannot be treated as acceptance test criteria for the above user story:

As a customer assistant I can log in to the system and change my password. This test case is not related to the user story, as it does not verify any of the functional or non-functional requirements of the user story. It is a generic test case that applies to any user of the system, not specific to the customer assistant role or the loan approval process.

As a bank manager I can log in to the system within 10 seconds. This test case is not related to the user story, as it does not verify any of the functional or non-functional requirements of the user story. It is a performance test case that applies to any user of the system, not specific to the bank manager role or the loan approval process.