CTAL-TA_Syll2019 iSQI ISTQB Certified Tester Advanced Level - Test Analyst (Syllabus 2019) Free Practice Exam Questions (2025 Updated)

A decision table is a technique that shows the possible combinations of conditions and actions for a given problem. A decision table that is not collapsed has one test case for each combination of conditions, regardless of whether the actions are the same or different. The tax system specification has three conditions: salary less than €20,000, married, and number of children between three and four. Each condition has two possible values: true or false. Therefore, the number of test cases for a non-collapsed decision table is 2^3 = 8. References =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2

Decision tables - IBM2, section “Decision table overview”

Equivalence partitioning is a technique that divides the input domain into classes of data that are expected to behave similarly. The test sets should cover one value from each equivalence class, as well as the boundary values between them. The equivalence classes for the metro fare system are:

Before 9:30 am (full fare)

Between 9:30 am and 5:00 pm (saver ticket)

Between 5:00 pm and 7:00 pm (full fare)

After 7:00 pm (saver ticket)

The boundary values are 9:30 am, 5:00 pm, and 7:00 pm. Therefore, the test set that provides the best equivalence partitioning coverage is the one that includes one value from each equivalence class and the boundary values, which is option D. References =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2

Boundary Value Analysis and Equivalence Partitioning Testing2, section “Equivalence Partitioning”

Equivalence Partitioning Method3, section “Example 1: Equivalence and Boundary Value”

The correct answer isA.It can be used to anonymize production data.

It can be used to anonymize production data

A test data preparation tool is a type of test tool that allows data to be selected from an existing database or created, generated, manipulated and edited for use in tests.One of the capabilities of such a tool is to anonymize production data, which means to mask or replace sensitive or confidential information with fictitious or random data, to protect the privacy and security of the data and comply with the regulations1.

References=

What is Test data preparation tools in software testing?2

Top 14 BEST Test Data Management Tools In 20233

Test Data Preparation Tools: 5 Must-Have Features4

The test execution phase involves running the test cases and comparing the actual results with the expected results. The test analyst is responsible for analysing any anomalies or deviations from the expected results and determining their root causes. This task helps to identify defects, report them, and track their resolution. References =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2

STLC (Software Testing Life Cycle) Phases, Entry, Exit Criteria2, section “Test Execution Phase”

Test Execution Tutorial: Detailed Guide With Best Practices3, section “Activities of Test Execution”

The correct answer isA.Functional correctness testing.

Functional correctness testing

Functional correctness testing is the type of testing that measures the degree of accuracy in a mortgage rate calculation module of the software you are testing. It verifies that the module produces the correct results for different inputs and scenarios, such as different interest rates, loan terms, payment frequencies, etc.It also checks that the module complies with the specifications and requirements of the mortgage rate calculation1.

References=

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, Section 3.2.2 Functionality

ISTQB Certified Tester Advanced Level Syllabus Test Analyst3, Section 3.2.2 Functionality

ISTQB Test Analyst Syllabus and Study Guide4, Section 3.2.2 Functionality

Pairwise testing is a technique that tests all possible discrete combinations of each pair of input parameters. In this case, there are two main categories: Colour and Shape. Under Colour, there are three subcategories: Red, Blue, and Green. Under Shape, there are two subcategories: Triangle and Circle. There is an additional category under Triangle labeled Size of triangle, with two subcategories: Small and Large. To test all pairs of these parameters, we need to use a tool or an algorithm that can generate the optimal test cases. One such tool is Pairwise.org, which can produce the following test cases:

Table

Colour

Shape

Size of triangle

Red

Triangle

Small

Blue

Circle

-

Green

Triangle

Large

Red

Circle

-

Blue

Triangle

Small

Green

Circle

-

Red

Triangle

Large

Blue

Triangle

Large

These eight test cases cover all pairs of parameters, such as Red-Triangle, Red-Small, Blue-Circle, etc. Therefore, the answer is B. 8. References = Pairwise Testing or All-Pairs Testing Tutorial with Tools and Examples, Pairwise Testing - What It Is, When & How to Perform?, All-pairs testing - Wikiwand, ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 3.2.3)

The correct answer isC.Conduct pre-test interviews to give instructions to the users, and post-test interviews to get their feedback.

Pre-test and post-test interviews

Pre-test and post-test interviews are methods of usability testing that involve communicating with the business users before and after they test the application. Pre-test interviews can help to explain the purpose and scope of the test, provide instructions and guidance, and establish rapport with the users.Post-test interviews can help to collect feedback, opinions, and suggestions from the users, as well as identify any issues or problems they encountered during the test1.

References=

ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Usability

ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Usability

Usability Testing 101: A Guide for Businesses4, Section 5. How to Conduct a Usability Test

 System integration testing (SIT) is a type of testing that verifies the interactions and functionality of different components or systems within a larger system. The developers, who are responsible for developing and integrating the components or systems, need to understand the tests to review them for accuracy, completeness, and feasibility. The auditors, who are responsible for ensuring the compliance and quality of the system, need to understand the tests to approve them for execution and reporting. References =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2

System Integration Testing: A Complete Guide2, section “Who Performs System Integration Testing?”

System Testing vs Integration Testing: Key Differences3, section “What is System Integration Testing?”

Functional correctness testing is a type of testing that verifies whether the system or software performs its intended functions correctly and accurately, according to the specified requirements. It can detect defects such as non-compliance to requirements, calculations that produce incorrect results, and improper handling of data or situations. References = Functional Testing: What Is It, Types, Best Practices, Tools (Section 1.1), ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 3.1.1)

The correct answer isB.The acceptance criteria are not testable.

The acceptance criteria are not testable

The acceptance criteria are not testable because they are vague and subjective. They do not specify any measurable or observable outcomes or conditions that can be verified by the test analyst.For example, what does “as fast as possible” or “easily” mean in terms of performance and usability? How can the test analyst determine if the user does not leave during the transaction or if they log in easily? The acceptance criteria should be rewritten to include clear and quantifiable criteria, such as response time, error rate, user satisfaction, etc1.

References=

ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 2.1.1 Test Analyst Tasks in the Test Process

ISTQB Test Analyst Syllabus and Study Guide3, Section 2.1.1 Test Analyst Tasks in the Test Process

What is User Story and Acceptance Criteria (Examples)4, Section 2. What is Acceptance Criteria?

The correct answer isA.Functional testing.

Functional testing

Functional testing is the type of testing that focuses on completeness, appropriateness, and correctness characteristics of the application under test. Completeness means that all the functions and features of the application are tested. Appropriateness means that the functions and features are suitable for the intended purpose and meet the user’sneeds.Correctness means that the functions and features produce the expected results and do not contain any errors or defects1.

References=

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, Section 3.2.2 Functionality

ISTQB Certified Tester Advanced Level Syllabus Test Analyst3, Section 3.2.2 Functionality

ISTQB Test Analyst Syllabus and Study Guide4, Section 3.2.2 Functionality

Incident logging and reporting is an important part of incident management, as it helps to document the incident details, communicate the incident status, and analyze the incident causes and impacts1. One of the steps in incident logging and reporting is to identify and log any new risks that have surfaced as a result of the incident2. This helps to assess the severity and priority of the incident, as well as to plan for risk mitigation and contingency actions3. Debugging the code and updating the test automation are not part of incident logging and reporting, but rather part of incident resolution and recovery4. None is not a valid answer, as there is always room for improvement in incident management5.

References = 1: 5 Steps to Create an Effective Incident Reporting Procedure 2: 12 Things To Include In An Incident Report Log (Full Guide) 3: Incident reporting procedure example and flow chart 4: What is incident management? Steps, tips, and best practices 5: Incident Management: Process, System, & Tools

A test design tool is a tool that helps testers create test cases, or at least test inputs, based on the requirements and specifications of the software. It can use various techniques, such as equivalence partitioning, boundary value analysis, decision tables, state transition diagrams, etc., to generate test inputs that cover different aspects of the software functionality and quality. A test design tool does not validate models of the software, execute tests automatically, or trace tests to requirements, although these may be features of other types of testing tools. References = What Is Test Design : Tools and Best Practices; Test Design in Software Testing - A Comprehensive Guide; ISTQB Advanced Level Test Analyst Syllabus 2019, section 3.2.1.

Exhibit B is the only state transition diagram that matches the text description of Acme’s elevator door rules. It shows that the doors can transition between four states: Opened, Closing, Closed, and Opening. The transitions are triggered by either commands (open or close) or sensors (opened or closed). The diagram also shows that the open command can reverse the closing state, and the close command can reverse the opening state, as specified in the text. The other exhibits do not show the correct transitions or conditions for the elevator door system. References =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 2

State Transition Testing Technique with Diagrams, section “State Transition Diagram”

State Transition Testing - Tutorialspoint, section “State Transition Diagram”

The level of detail and documentation required for test cases in the project depends on the type of application under test, the standards followed by the organization, and the maturity of the development process. For a medical domain application that is undergoing frequent changes, it is advisable to use low-level test cases that provide more details and specifications for each feature. Low-level test cases can support both the external audit and the new junior testers by ensuring traceability between the requirements and the test scenarios, as well as by facilitating future changes or enhancements. Low-level test cases can also be reviewed and updated by both experienced domain-based testers and junior testers who have extensive knowledge of the medical domain. References =

ISTQB Certified Tester Advanced Level Overview of Syllabi1, page 10

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, page 2

Healthcare Domain Testing: 60 Sample Test Case Examples3, section “Testing Types for Healthcare Applications”

Experience-based testing is a technique that relies on the tester’s intuition, skills, and past experiences to create test scenarios. However, this approach makes it challenging to measure and assess the test coverage, as there is no clear criteria or method to determine which areas of the software have been tested and which have not. This can lead to gaps in the testing process and potential risks of missing defects1

References =

ISTQB Advanced Level Test Analyst Syllabus 2019, Section 3.2.3.1, page 462

Experience Based Testing: What It Is and Why It Matters?3

Experience based testing technique - ToolsQA4

Classification trees are a visual way of identifying test objects and data, and pairwise testing is a technique of generating test cases that cover all possible pairs of values from different classifications. Classification trees support pairwise testing by:

Helping to identify inputs to be used by the pairwise test technique, as each class represents a possible value for a test parameter.

Showing the combinations needed to cover all-pairs, as each test case is a selection of one class from each classification.

Helping to identify particular combinations of interest, as the test engineer can use the tree structure to group or prioritize classes based on their relevance or risk. References = ISTQB Advanced Level Test Analyst Syllabus 2019, section 3.2.3; Smarter Test Design with Classification Trees and Pairwise Techniques, slides 6-12.

Risk mitigation is the process of implementing actions to reduce the probability and/or impact of risks1. When you execute the tests in priority order based on the risk ratings, you are performing risk mitigation, as you are trying to prevent or minimize the potential failures and defects in the system2. Risk planning, identification, and assessment are the previous steps in the risk management process, which help to prepare for risk mitigation3.

References = 1: Risk Mitigation – Planning, Implementing, and Monitoring 2: Risk Based Testing Approach for Agile Teams 3: The Ultimate Guide to Risk Based Testing: Risk Management in Software Testing