Consider the following examples of risks identified in different software development projects: [I]. It may not be possible to generate the expected workloads to run performance tests, due to the poor hardware equipment of the machines (load injectors) that should generate these workloads [II]. A user's session on a web application is not invalidated after a certain period of inactivity (configured by the system administrator) of the user [III]. The test team will not have an adequate requirements specification (since many requirements will still be missing) by the time test design and analysis activities should begin according to the test plan [IV]. Following a failure, the system is unable to continue to maintain its pre-failure operation and some data becomes corrupted Which of the following statements is true?
Correct Answer: A
Product Risks: Relate to the quality of the software product itself, such as functionality, performance, security, and user experience. * II: A session management issue affects the product's security and functionality. * IV: Inability to maintain operation and data corruption directly affects the product's reliability and data integrity. Project Risks: Relate to the circumstances and activities within the project, such as schedule, resources, and planning. * I: Poor hardware equipment for performance testing impacts the project's ability to conduct performance tests. * III: Inadequate requirement specifications affect the project timeline and the ability to design tests.
Question 107
As a result of the joint evaluation of a product version with the customer, it has been concluded that it would be appropriate to retrieve an earlier version of the product and carry out a benchmark. Depending on the result, further development will be carried out based on the current version or the retrieved version. Which mechanism, process, and/or technique will allow the specific version (including the testing work products) of a given software product to be restored?
Correct Answer: B
Configuration management (B)ensures thatversions of software and test artifactsare properly tracked, stored, and retrievable. It allows teams to: * Restoreearlier versions of software and test work products * Maintaintraceability between requirements, tests, and code * Avoid discrepancies due tomismanaged versions * (A) is incorrectbecause defect managementtracks issues but does not restore versions. * (C) is incorrectbecause change managementcontrols changes but does not track past versions. * (D) is incorrectbecause risk managementassesses risks but does not manage software versions. Effective configuration management ensures the ability to roll back changesand maintain system stability. Reference:ISTQB CTFL v4.0 Syllabus, Section 5.4 - Configuration Management
Question 108
Which of the following statements best describes how configuration management supports testing?
Correct Answer: D
This answer is correct because configuration management is a process of establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. Configuration management helps ensure that all relevant project documentation and software items are uniquely identified in all their versions and therefore can be unambiguously referenced in test documentation. This supports testing by providing traceability, consistency, and control over the test artifacts and the software under test. Reference: : ISTQB Glossary of Testing Terms v4.0, : ISTQB Foundation Level Syllabus v4.0, Section 2.2.2.2
Question 109
Which of the following is not an example of a typical content of a test completion report for a test project?
Correct Answer: D
Explanation This answer is correct because the test procedures of all test cases that have been executed are not a typical content of a test completion report for a test project. A test completion report is a document that summarizes the test activities and results at the end of a test project. It usually includes information such as the test objectives, scope, approach, resources, schedule, results, deviations, issues, risks, lessons learned, and recommendations for improvement. The test procedures of all test cases that have been executed are part of the test documentation, but they are not relevant for the test completion report, as they do not provide a high-level overview of the test project outcomes and performance. References: ISTQB Foundation Level Syllabus v4.0, Section 2.5.3.2
Question 110
Which ONE of the following options is a practice that does NOT TYPICALLY correspond to a shift left approach?
Correct Answer: D
Comprehensive and Detailed Explanation From Exact Extract: Theshift-left approachfocuses on executing testing activitiesas early as possiblein the software development lifecycle, including static testing, unit tests, and early reviews. Activities like writing tests before code (test- first) and continuous integration are central to this principle. However, performingnon-functional testing at the system test levelhappenslaterin the lifecycle and doesnot align with the shift-left philosophy. "The shift-left approach involves the adoption of practices to move tasks related to testing (e.g., reviews, test design) to earlier stages in the lifecycle." (ISTQB CTFL v4.0 Syllabus, Section 2.1.5 - Shift-Left Approach) "Non-functional testing is often performed at the system test level, but the shift-left approach aims to begin such testing earlier, possibly at integration or even unit levels." (ISTQB CTFL v4.0 Syllabus, Section 2.2.2 - Test Types) Therefore,Option Ddoes not correspond to shift-left practices and is the correct answer.
