Which of the following are triggers for Maintenance testing?
a) System migration from one platform to another.
b) Retirement of a system.
c) Preparation for an audit of a system.
d) Modifications to a system.
e) Development of a whole new system.
Answer : A
Maintenance testing is a type of testing that is done on an existing system after modifications or migration, or to prevent deterioration or obsolescence. Maintenance testing can be triggered by various events or situations, such as:
System migration from one platform to another, which can affect the functionality, performance, or compatibility of the system.
Preparation for an audit of a system, which can require verifying the compliance of the system with standards or regulations.
Modifications to a system, which can introduce new defects or affect existing ones.
Therefore, statements a, c, and d are correct.
Which of the following can be a common objective of testing?
Answer : A
Gaining confidence about the level of the system's quality can be a common objective of testing, because testing can provide information about how well the system meets its specified requirements and user expectations, and how many defects have been found and fixed in the system.
Which of the following statements is true?
Answer : D
A requirements management tool may be considered as a test support tool because it can help support or enhance some aspects of testing activities or processes. A requirements management tool is a tool that allows users to manage and trace the requirements of a software system. A requirements management tool can help support or enhance testing activities or processes by:
Providing a clear and consistent definition of what needs to be tested based on user needs and expectations
Enabling traceability between requirements and test cases to ensure adequate and complete test coverage
Supporting change management and impact analysis by identifying and tracking changes in requirements and their effects on testing activities and results
Which of the following BEST defines risk level?
Answer : B
The correct answer is B, as it defines risk level correctly.Risk level is determined by the likelihood of an event happening and the impact or harm from that event4.Likelihood is the probability or frequency of the event occurring4.Impact is the severity or consequence of the event occurring4.Risk level can be calculated by multiplying likelihood and impact, or by using a risk matrix that assigns risk levels based on different combinations of likelihood and impact4. Option A is incorrect, as it does not define risk level correctly.Risk level is not calculated by adding the probabilities of all planned risks to a project, but by assessing the likelihood and impact of each individual risk4. Option C is incorrect, as it does not define risk level correctly.Risk level is not calculated by dividing the sum of all known risks by the sum of all unknown risks, but by assessing the likelihood and impact of each individual risk4. Option D is incorrect, as it does not define risk level correctly.Risk level is not determined by calculating the absolute value of the sum of all potential issues that may occur on the project, but by assessing the likelihood and impact of each individual risk4. Reference:4, Section 2.8
Consider the following excerpt from a test report 'We tested the module AX45T and we got only 1 failure. To recreate the failure, we used test file PR624_DR78_TCB0022 pkr, available under the PR624_DR78 repository in the CK01 server".
Which incident report objective does this excerpt satisfy?
Answer : A
Which of the following defect types are LEAST likely to be discovered when using static analysis tools?
Answer : C
Static analysis tools are tools that examine the code or design of a software system without executing it. Static analysis tools can be used to find defects, measure complexity, check compliance, or improve quality. Some examples of defect types that can be found by static analysis tools are:
Variables that are never used: This defect type occurs when a variable is declared but not referenced or assigned in the code, which indicates a waste of memory or a logic error.
Coding standard violations: This defect type occurs when the code does not follow the predefined rules or conventions for formatting, naming, commenting, etc., which affects the readability and maintainability of the code.
Uncalled functions and procedures: This defect type occurs when a function or procedure is defined but not called or invoked in the code, which indicates a waste of resources or a missing functionality.
Memory leaks are defect types that are least likely to be found by static analysis tools because they are related to the dynamic behavior and performance of the software system. Memory leaks occur when a program does not release memory that it has allocated, causing the system to run out of memory and slow down or crash. Memory leaks can only be detected by dynamic analysis tools that monitor the memory usage of the program during execution. You can find more information about static analysis tools in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 6, Section 6.3.
Refer to the exhibit

Given the following State Transition diagram, match the test cases below with the relevant set of state transitions.
(i) X-Z-V-W
(ii) W-Y-U-U
Answer : A
State transition testing is a technique that uses state transition diagrams as a test basis to derive test cases2.A state transition diagram shows the states of a system and the transitions between them triggered by events or conditions2.A test case can cover one or more state transitions, depending on the test objective and coverage criterion2. In this question, the test cases (i) and (ii) cover different sets of state transitions, as shown below:
Test Case
State Transitions
(i) X-Z-V-W
S1 -- S2 -- S3 -- S4 -- S2
(ii) W-Y-U-U
S4 -- S2 -- S4 -- S4 -- S4