iSQI CTFL_Syll2018 ISTQB Certified Tester Foundation Level Exam Practice Test

Answer : C

Priority is an important item of information that is missing from the incident report. Priority indicates the importance or urgency of resolving the incident, based on the business needs and the impact on the stakeholders. Priority is usually assigned by the project manager or the customer, and it helps to determine the order in which incidents should be addressed. Priority may differ from severity, which indicates the degree of impact of the incident on the system or the component under test. Severity is usually assigned by the tester or the developer, and it helps to assess the risk of the incident. For example, an incident may have a high severity but a low priority, if it affects a critical function but only occurs in a rare situation. Conversely, an incident may have a low severity but a high priority, if it affects a minor function but occurs frequently or affects many users. Therefore, both priority and severity are useful information for incident management and resolution.

The other options are not essential information for the incident report, although they may be helpful or desirable in some cases. Recommendations are suggestions or proposals for resolving the incident, which may be provided by the tester, the developer, or other stakeholders. However, recommendations are not mandatory, and they may not be feasible or acceptable in some situations. Name of tester is the identifier of the person who reported the incident, which may be useful for communication or accountability purposes. However, name of tester is not critical, and it may be replaced by other identifiers, such as email address, employee number, or role. Change history is the record of the changes made to the incident report, such as status, resolution, or comments. Change history is valuable for tracking and auditing purposes, but it is not part of the initial incident report, rather it is updated as the incident progresses.

Answer : A

The correct answer is A, as it provides the highest level of boundary coverage using two-point boundary value analysis.Boundary value analysis is a black-box test technique that focuses on the boundaries of input and output partitions1.Two-point boundary value analysis is a variation of boundary value analysis that uses only two values for each boundary: one just below the boundary and one just above the boundary1. In this case, the boundaries are the balance ranges that correspond to different interest rates. Option A covers all four boundaries using two values for each boundary: $100.00 and $100.01 for the first boundary, $500.00 and $500.01 for the second boundary, $1,000.00 and $1,000.01 for the third boundary, and $5.00 as an invalid value below the lowest boundary. Option B covers only three boundaries using one value for each boundary: $100.00 for the first boundary, $500.00 for the second boundary, and $1,000.00 and $1,000.01 for the third boundary. Option C covers only two boundaries using three values for each boundary: $100.00, $100.01, and $100.02 for the first boundary, and $500.00 and $999.99 for the second boundary.Option D covers only two boundaries using one value for each boundary: $100.00 for the first boundary, and $1,000.01 for the third boundary, and $5.00 as an invalid value below the lowest boundary. Reference:1, Section 4.2.3

Answer : B

This scenario is using a walkthrough review type and a perspective-based review technique. A walkthrough is a type of review that is relatively informal and led by the author of the work product. A perspective-based review technique is a technique that involves reviewing the work product from different viewpoints or perspectives of various stakeholders. The scenario matches these descriptions, as it involves an informal approach, a meeting leader who is the author of the requirements document, and a goal of improving the software application's usability and accessibility by considering the various stakeholders' viewpoints. Option A is incorrect, as a pair review is a type of review that involves only two people, usually the author and another team member. Option C is incorrect, as a checklist-based review technique is a technique that involves reviewing the work product against a predefined list of items or criteria. Option D is incorrect, as it combines the incorrect descriptions of options A and C.

Answer : C

The correct matching of the review types with the review characteristics is as follows:

Pair review: Informal (2)

Walkthrough: Purpose includes gaining consensus (3)

Technical review: Purposes include improving the software product and training the review participants (4)

Inspection: Formal (1)

Therefore, option C is the correct answer. Options A, B, and D are incorrect, as they do not match the review types with the review characteristics correctly.

Answer : B

The correct roles and responsibilities in a formal review are as follows1:

Review Leader - Plans and leads the review process

Scribe - Documents all issues raised during the review meeting

Author - Creates the work product under review

Facilitator - Supports the review leader in conducting the review process

Reviewers - Identify potential defects in the work product under review

Therefore, option B is the correct answer, as it correctly matches the role of scribe with the responsibility of collating potential defects found during the individual review activity.Options A, C, and D are incorrect, as they do not match the roles and responsibilities correctly. Reference:1, Section 3.2.3

Answer : A

Maintenance testing is triggered by changes, such as migration, retirement, or enhancement of a system1. Therefore, option A is the best example of a trigger for maintenance testing.Options B, C, and D are examples of triggers for development testing, not maintenance testing1. Reference:1, Section 2.3.2

Answer : C

According to the syllabus, regression testing is a type of software testing that verifies that previously developed and tested software still performs as expected after a change. A change can be any modification in the software product or system, such as bug fixes, enhancements, configuration changes, etc. Regression testing helps to ensure that the change does not introduce new defects or affect existing functionality. Confirmation testing is a type of software testing that verifies that a specific defect has been fixed after a change. Confirmation testing is also known as re-testing. Confirmation testing helps to ensure that the change has resolved the defect and does not introduce new defects. The answer C is correct because it best matches the type of testing with the testing scenario. Testing to ensure the application of a new version of the operating system does not have any unintended side-effects on the system (1) is an example of regression testing, as it verifies that the change in the operating system does not affect the functionality of the system. Testing due to the application of a security patch (2) is also an example of regression testing, as it verifies that the change in the security patch does not affect the functionality of the system. Testing due to the application of a new version of the database management system (3) is another example of regression testing, as it verifies that the change in the database management system does not affect the functionality of the system. Testing to ensure the fix to the payroll system truly works (4) is an example of confirmation testing, as it verifies that the change in the payroll system has fixed a specific defect. The other answers are incorrect because they do not match the type of testing with the testing scenario correctly.