リリースISTQB ISTQB-CTFL更新された問題PDF
ISTQB-CTFL問題集と練習テスト（132試験問題)
質問 # 67
During system testing phase of a word processor, a tester finds that on opening a file from a particular set of files, which are part of a critical workflow, the word processor crashes. Which of the following is the next step the tester should take poor to recording the deviation?
- A. Try to recreate the incident before reporting
- B. Report the incident as is without any further action
- C. Try to identify the code fragment causing the problem
- D. Send an email to the developer and not report the bug
正解：A
解説：
An incident is any event that occurs during testing that requires investigation. An incident report is a document that records the details of an incident. The next step the tester should take prior to recording the deviation is to try to recreate the incident before reporting. This can help confirm that the incident is reproducible and not caused by a random or external factor. This can also help gather more information about the incident, such as the steps to reproduce it, the expected and actual results, the severity and priority of the incident, or any screenshots or logs that can illustrate the incident. Trying to identify the code fragment causing the problem is not the next step the tester should take prior to recording the deviation, as this is a debugging activity that is usually performed by developers after receiving the incident report. Sending an email to the developer and not reporting the bug is not the next step the tester should take prior to recording the deviation, as this is an informal and unstructured way of communicating incidents that can lead to confusion, inconsistency or loss of information. Reporting the incident as is without any further action is not the next step the tester should take prior to recording the deviation, as this can result in incomplete or inaccurate incident reports that can hamper the investigation and resolution of incidents. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 32-33.
質問 # 68
Which of the following statements about reviews are TRUE?
I In walkthroughs the review meeting is typically led by the author.
II Inspection is characterized by an open-ended review meeting
III Preparation before the review meeting is part of informal reviews
IV Management rarely participates in technical review meetings
- A. I, IV
- B. I, II
- C. III, IV
- D. II, Ill
正解：A
解説：
The following statements about reviews are true:
I) In walkthroughs the review meeting is typically led by the author. A walkthrough is a type of review that has a predefined objective and agenda but no formal process or roles. A walkthrough is typically led by the author of the work product under review, who guides the participants through a scenario and solicits feedback.
IV) Management rarely participates in technical review meetings. A technical review is a type of review that has a predefined objective and agenda but no formal process or roles. A technical review is typically performed by peers with technical expertise in order to evaluate technical aspects of a work product. Management rarely participates in technical review meetings, as they may not have sufficient technical knowledge or skills to contribute effectively. The following statements about reviews are false:
II) Inspection is characterized by an open-ended review meeting. An inspection is a type of review that follows a defined process with formal entry and exit criteria and roles and responsibilities for participants. An inspection is characterized by a structured review meeting with a fixed duration and agenda.
III) Preparation before the review meeting is part of informal reviews. Preparation before the review meeting is part of formal reviews, such as inspections or technical reviews. Preparation involves checking
質問 # 69
Which of the following statements about Experience Based Techniques (EBT) is correct?
- A. EBT require broad and deep knowledge in testing but not necessarily in the application or technological domain.
- B. EBT is done as a second stage of testing, after non-experienced-based testing took place.
- C. EBT use tests derived from the test engineers' previous experience with similar technologies.
- D. EBT is based on the ability of the test engineer to implement various testing techniques.
正解：C
解説：
Experience based techniques (EBT) are techniques that use the knowledge, intuition and skills of the test engineers to design and execute tests. EBT use tests derived from the test engineers' previous experience with similar technologies, domains, applications or systems. EBT are not based on the ability of the test engineer to implement various testing techniques, but rather on their personal judgment and creativity. EBT are not done as a second stage of testing, after non-experience-based testing took place, but rather as a complementary or alternative approach to other techniques. EBT require broad and deep knowledge in both testing and the application or technological domain, as this can help the test engineer identify potential risks, scenarios or defects. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 5, page 48-49.
質問 # 70
You need to test the login page of a web site. The page contains fields for user name and password. Which test design techniques are most appropriate for this case?
- A. Decision table testing, state transition testing.
- B. Exploratory testing, statement coverage.
- C. Equivalence partitioning, Boundary value analysis.
- D. Decision coverage, fault attack.
正解：C
解説：
Equivalence partitioning and boundary value analysis are test design techniques that are most appropriate for testing the login page of a web site. The page contains fields for user name and password, which are input values that can be divided into partitions of equivalent data. Equivalence partitioning is a technique that divides the input data and output results of a software component into partitions of equivalent data. Each partition should contain data that is treated in the same way by the component. Equivalence partitioning can be used to reduce the number of test cases by selecting one representative value from each partition. Boundary value analysis is a technique that tests boundary values between partitions of equivalent data. Boundary values are values at the edge of an equivalence partition or at the smallest incremental distance on either side of an edge. Boundary value analysis can be used to detect defects caused by incorrect handling of boundary conditions. For example, for testing the user name field, we can identify two equivalence partitions: valid user name (existing and correct) and invalid user name (non-existing or incorrect). The boundary values for these partitions are the minimum and maximum length of user name allowed by the system.
Decision table testing and state transition testing are not suitable for testing the login page of a web site, as they are more applicable for testing components that have multiple inputs and outputs that depend on logical combinations of conditions or events. Decision table testing is a technique that shows combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects). State transition testing is a technique that models how a system transitions from one state to another depending on events or conditions.
Exploratory testing and statement coverage are not suitable for testing the login page of a web site, as they are more applicable for testing components that require learning, creativity and intuition or structural analysis. Exploratory testing is an approach to testing that emphasizes learning, test design and test execution at the same time. Exploratory testing relies on the tester's skills, creativity and intuition to explore the software under test and discover defects. Statement coverage is a type of structural testing that measures how many statements in a program have been executed by a test suite. Statement coverage can be used to assess the adequacy or completeness of a test suite.
Decision coverage and fault attack are not suitable for testing the login page of a web site, as they are more applicable for testing components that have complex logic or potential errors. Decision coverage is a type of structural testing that measures how many decision outcomes in a program have been executed by a test suite. Decision coverage can be used to assess the adequacy or completeness of a test suite. Fault attack is a type of functional testing that deliberately introduces faults into a system in order to provoke failures or errors. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 4, page 34-46; Chapter 5, page 47-48.
質問 # 71
Which of the following statements about testware are correct?
I When closing the test activities, all the testware resources can be uninstalled and released II All the testware should be subject to Configuration Management III. The testware. at the end of the project, should be transferred to the organization responsible for maintenance IV The developers are responsible for the correct installation of the testware
- A. II, Ill
- B. I, IV
- C. I, Ill
- D. II, IV
正解：A
解説：
Testware is a term that refers to all artifacts produced during the testing process, such as test plans, test cases, test scripts, test data, test results, defect reports, etc. The following statements about testware are correct:
* II) All the testware should be subject to Configuration Management. Configuration management is a process that establishes and maintains consistency among work products throughout their life cycle.
Configuration management applies to all testware, as it helps ensure their quality and consistency, track their changes and defects, control their versions and access rights, and link them to other artifacts.
* III) The testware at the end of the project should be transferred to the organization responsible for maintenance. Maintenance testing is testing performed on a software product after delivery to correct defects or improve performance or other attributes. Maintenance testing requires testware from previous testing activities or phases, such as test cases, test data, test results, etc. Therefore, the testware at the end of the project should be transferred to theorganization responsible for maintenance testing, such as support team or maintenance team. The following statements about testware are incorrect:
* I) When closing the test activities, all the testware resources can be uninstalled and released. This statement is incorrect, as some testware resources may still be needed for future testing activities or phases, such as maintenance testing or regression testing. Therefore, when closing the test activities, some testware resources should be archived and stored for future use, while others can be uninstalled and released.
* IV) The developers are responsible for the correct installation of the testware. This statement is
* incorrect, as the testers are responsible for the correct installation of the testware. The testers should ensure that they have access to all necessary testware resources and that they are installed and configured properly before starting the test execution. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 6, page 58-61.
質問 # 72
The testers in company A were part of the development team. Due to an organizational change they moved to be part of the support team.
What are the advantages and the disadvantages of this change?
- A. Advantage: More independence in deciding what and how to test,
Disadvantage: Isolation from me development team knowledge - B. Advantage: increased chances to move a tester to development;
Disadvantage: pulled to support tasks and having less time for testing - C. Advantage: being closer to customer perspective,
Disadvantage less independence in perspectives - D. Advantage: pulled to support tasks and having less time for testing, Disadvantage less chances to move a tester to development
正解：C
解説：
Being part of the support team means that the testers are closer to the customer perspective, which is an advantage for testing, as they can better understand the user needs and expectations, and identify more realistic scenarios and risks. However, being part of the support team also means that they have less independence in deciding what and how to test, as they may be influenced by the customer's preferences or requests, which could compromise the objectivity and effectiveness of testing. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 6.
質問 # 73
Which sequence of state transition stated in the answer choices is correct in accordance with the following figure depicting me life-cycle of a defect?
- A. S0->S1->S2->S3->S5->S3->S4
- B. S0->S1->S2->S3->S5^>S1
- C. S0->S1->S2->S3->S5->S1->S2->S3
- D. S0->S1->S2->S3->S4
正解：C
解説：
The figure depicts the life-cycle of a defect using state transition testing. State transition testing is a technique that models how a system transitions from one state to another depending on events or conditions. The figure shows six states (S0 to S5) and seven transitions (T0 to T6). The correct sequence of state transitions that follows the figure is S0->S1->S2->S3->S5->S1->S2->S3. This sequence represents the following scenario:
* S0: The defect is not yet detected (initial state).
* T0: The defect is detected by testing (event).
* S1: The defect is reported and registered (state).
* T1: The defect is assigned to a developer for fixing (event).
* S2: The defect is being fixed by the developer (state).
* T2: The developer fixes the defect and delivers a new version (event).
* S3: The defect is verified by testing (state).
* T5: The testing fails to confirm that the defect is fixed (event).
* S5: The defect is rejected by testing (state).
* T6: The defect is reassigned to a developer for fixing (event).
* S1: The defect is reported and registered (state).
* T1: The defect is assigned to a developer for fixing (event).
* S2: The defect is being fixed by the developer (state).
* T2: The developer fixes the defect and delivers a new version (event).
* S3: The defect is verified by testing (state). The other sequences are incorrect, as they do not follow the transitions shown in the figure. Verified References: [A Study Guide to the ISTQB Foundation Level
2018 Syllabus - Springer], Chapter 4, page 40-41.
質問 # 74
Why is it important to select a test technique?
- A. Selecting the right test technique in a given situation Increases the effectiveness of the test process Oy creating tests with higher chance of finding bugs.
- B. The only way to test a software application is by using well proven test techniques.
- C. There are usually loo many test cases that may be run on a system. Test techniques help reduce the number of tests.
- D. Test techniques define the number of regression cycles, which in turn impact the project schedule.
正解：A
解説：
Selecting the right test technique is crucial because different techniques are suited to different types of testing and can significantly increase the effectiveness of the testing process by creating tests that are more likely to find defects. While reducing the number of tests (A) and defining the number of regression cycles (D) are considerations in the testing process, they are not the primary reasons for selecting a test technique. The assertion that the only way to test a software application is by using well-proven test techniques (B) is too restrictive and does not acknowledge the adaptability required in testing to suit different contexts and objectives. Therefore, option C is the most comprehensive reason, as it focuses on the effectiveness and efficiency of testing, leading to the creation of high-quality tests that have a higher chance of finding bugs.
質問 # 75
Which of the following definitions is NOT true?
- A. Test Management tools monitor and report on how a system behaves during the testing activities.
- B. Test comparators determine differences between files, databases or test results.
- C. Test data preparation tools fill databases, create files or data transmissions to set up test data to be used during the execution of tests.
- D. Test execution tools execute test objects using automated test scripts.
正解：A
解説：
Test Management tools are designed to support the planning, execution, and monitoring of the testing process. They provide features for managing test cases, test runs, tracking defects, and reporting on testing activities. However, the statement in option C describes Test Management tools as monitoring and reporting on the system's behavior during testing activities, which is not accurate. Test Management tools focus on the testing process itself rather than on the behavior of the system under test.
Test data preparation tools (A) indeed create and manage test data for use during test execution.
Test execution tools (B) automate the execution of test cases and the comparison of actual outcomes against expected results.
Test comparators (D) are tools that compare actual outcomes with expected outcomes, highlighting discrepancies.
Therefore, option C is the correct answer as it inaccurately describes the function of Test Management tools.
質問 # 76
Which of the following is true about Oracles?
- A. Oracles are derived from the design
- B. Oracles help in reproducing the irreproducible bugs
- C. Sometimes old version of a product can be used as an Oracle
- D. Oracles can be generated automatically using data generators
正解：C
解説：
An oracle is a mechanism or source that can provide the expected result for a given test input or situation. Sometimes old version of a product can be used as an oracle, if it is assumed that the old version behaves correctly for the test cases that are executed on the new version. This is also known as back-to-back testing. Oracles do not help in reproducing the irreproducible bugs, as they only provide the expected results, not the actual results. Oracles are not derived from the design, but from the requirements or specifications. Oracles cannot be generated automatically using data generators, as data generators only provide test inputs, not test outputs. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 9.
質問 # 77
Which type of software development product can undergo static testing?
- A. Static testing is done only on the requirements You need to execute the software in order to find defects in the code.
- B. Static testing is done only on the code as part of the "code review" sessions Other documents are reviewed, but not by static testing.
- C. Static tests should be performed on the installation and user guide documents as these documents are used by the end user.
- D. Any software development product can undergo static testing, including requirements specifications, design specifications and code.
正解：D
解説：
Static testing is a form of testing that does not involve executing the software, but rather analyzing it for defects, errors, or violations of standards. Static testing can be applied to any software development product, including requirements specifications, design specifications, code, test cases, test plans, user manuals, etc.
Static testing can be done by using various techniques such as reviews, inspections, walkthroughs, checklists, static analysis tools, etc. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus
- Springer, page 7.
質問 # 78
A Test Manager conducts risk assessment for a project. One of the identified risks is: The sub-contractor may fail to meet his commitment". If this risk materializes. it will lead to delay in completion of testing required for the current cycle.
Which of the following sentences correctly describes the risk?
- A. It is no longer a risk for the Test Manager since an independent party (the sub-contractor) is now managing it
- B. It is a object risk since successful completion of the object depends on successful and timely completion of the tests
- C. It is a product risk since default on part of the sub-contractor may lead to delay in release of the product
- D. It is a product risk since any risk associated with development timeline is a product risk.
正解：C
解説：
* A product risk is a risk that affects the quality or timeliness of the software product being developed or tested1. Product risks are related to the requirements, design, implementation, verification, and maintenance of the software product2.
* The risk of the sub-contractor failing to meet his commitment is a product risk, as it could cause a delay in the completion of the testing required for the current cycle, which in turn could affect the release date of the product. The release date is an important aspect of the product quality, as it reflects the customer satisfaction and the market competitiveness of the product3.
* The other options are not correct because:
* A. It is not true that any risk associated with development timeline is a product risk. Some risks could be project risks, which are risks that affect the management or control of the software project, such as budget, resources, schedule, or communication1. For example, a risk of losing a key project stakeholder is a project risk, not a product risk.
* B. It is not true that the risk is no longer a risk for the Test Manager since an independent party is managing it. The Test Manager is still responsible for ensuring that the testing activities are completed according to the test plan and the quality objectives4. The Test Manager should monitor and control the sub-contractor's performance and communicate with him regularly to identify and mitigate any potential issues or deviations5.
* C. It is not clear what is meant by "object" in this option, but it could be interpreted as the software system under test or the test object6. In any case, the risk is not an object risk, as it does not affect the successful completion of the object, but rather the successful completion of the testing of the object. An object risk could be a risk that affects the functionality, reliability, usability, efficiency, maintainability, or portability of the software system under test2. For example, a risk of the software system having a high complexity or a low testability is an object risk, not a product risk.
References =
* 1 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97
* 2 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98
* 3 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 99
* 4 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 100
* 5 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 101
* 6 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 102
質問 # 79
The ISTOB glossary defines Quality Assurance as: "Pail or quality management focused on providing confidence that quality requirements will be fulfilled. Which of the following Is not one of the Quality Assurance activity?
- A. Performance Testing
- B. Functional Testing
- C. Defect analysis
- D. Requirements elicitation
正解：B
解説：
Quality Assurance (QA) activities are focused on providing confidence that quality requirements will be fulfilled through planned and systematic processes. These activities are preventive in nature, aimed at ensuring quality is built into the product from the beginning.
Requirements elicitation (A) is part of the requirements engineering process and is concerned with gathering the needs and conditions to meet for a new or altered product.
Defect analysis (B) can be part of QA activities as it involves analyzing defects to prevent them in future development cycles.
Functional Testing (C) and Performance Testing (D) are types of dynamic testing, which are actually Quality Control activities rather than Quality Assurance. They are concerned with the identification of defects in the product, not with the processes to prevent defects.
Since the question asks for an activity that is NOT part of Quality Assurance, options A and B are incorrect because they can be part of QA activities. Between C and D, while both are dynamic testing activities, Functional Testing (C) is more directly related to verifying the functionality against specified requirements, which is more aligned with Quality Control. Therefore, C is the best answer.
質問 # 80
Which of the following isNOTa product risk?
- A. Poor software usability
- B. Software does not perform the intended functions
- C. Failure-prone software is delivered
- D. Problems in defining the right requirements
正解：D
解説：
Problems in defining the right requirements is not a product risk, but rather a project risk. A product risk is a risk that affects the quality or performance of the software product itself, such as poor usability, failure-prone functionality, security vulnerabilities, compatibility issues, etc. A project risk is a risk that affects the management or delivery of the software project itself, suchas unrealistic schedule, insufficient resources, unclear scope, changing requirements, etc. The other options are examples of product risks, as they relate to the software product's characteristics or features. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 12.
質問 # 81
In what way do Configuration Management effects testing?
- A. Proper configuration management ensures that testers can uniquely identity the tested item
- B. Without proper configuration management, test planning cannot proceed.
- C. Configuration management is important for developers, not for testers
- D. There is very little influence of configuration management practices on the test project.
正解：A
解説：
Configuration management is a process that establishes and maintains consistency among work products throughout their life cycle. Configuration management affects testing in various ways, such as:
Proper configuration management ensures that testers can uniquely identify the tested item, which can help traceability, reproducibility and accountability.
Proper configuration management ensures that testers have access to consistent versions of software components and testware, which can help reliability, compatibility and efficiency.
Proper configuration management ensures that testers can track changes and defects in software components and testware, which can help verification, validation and reporting.
Proper configuration management ensures that testers can control the configuration of the test environment, which can help stability, security and performance. Configuration management is not a prerequisite for test planning, as test planning can proceed without configuration management, although it may be less effective or accurate. Configuration management is not important for developers only, but for testers as well, as it affects the quality and consistency of the testing process and products. Configuration management has a significant influence on the test project, as it affects various aspects of testing, such as traceability, reproducibility, reliability, compatibility, efficiency, verification, validation, reporting, stability, security and performance. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 6, page 60-61.
質問 # 82
During component testing of a program if 100% decision coverage is achieved, which of the following coverage criteria is also guaranteed to be 100%?
- A. 100% Stale transition coverage
- B. 100% Statement coverage
- C. 100% Equivalence class coverage
- D. 100% Boundary value coverage
正解：B
解説：
Statement coverage is a structural coverage metric that measures the percentage of executable statements in the source code that are executed by a test suite1. Decision coverage is another structural coverage metric that measures the percentage of decision outcomes (such as branches or conditions) in the source code that are executed by a test suite1. Decision coverage is a stronger metric than statement coverage, because it requires that every possible outcome of each decision is tested, while statement coverage only requires that every statement is executed at least once2. Therefore, if a test suite achieves 100% decision coverage, it also implies that it achieves 100% statement coverage, because every statement in every branch or condition must have been executed. However, the converse is not true: 100% statement coverage does not guarantee 100% decision coverage, because some branches or conditions may have multiple outcomes that are not tested by the test suite2. For example, consider the following pseudocode:
if (x > 0) then print("Positive") else print("Non-positive") end if
A test suite that executes this code with x = 1 and x = -1 will achieve 100% statement coverage, because both print statements are executed. However, it will not achieve 100% decision coverage, because the condition x > 0 has only been tested with two outcomes: true and false. The third possible outcome, x = 0, has not been tested by the test suite. Therefore, the test suite may miss a potential bug or error in the condition or the branch.
The other options, such as stale transition coverage, equivalence class coverage, and boundary value coverage, are not guaranteed to be 100% by achieving 100% decision coverage. Stale transition coverage is a structural coverage metric that measures the percentage of transitions between states in a state machine that are executed by a test suite3. Equivalence class coverage is a functional coverage metric that measures the percentage of equivalence classes (or partitions) of input or output values that are tested by a test suite4. Boundary value coverage is another functional coverage metric that measures the percentage of boundary values (or extreme values) of input or output ranges that are tested by a test suite4. These metrics are independent of decision coverage, because they are based on different aspects of the system under test, such as its behavior, functionality, or specification. Therefore, achieving 100% decision coverage does not imply achieving 100% of any of these metrics, and vice versa. Reference = ISTQB Certified Tester Foundation Level Syllabus v4.0, Test Coverage in Software Testing - Guru99, Structural Coverage Metrics - MATLAB & Simulink - MathWorks India, Test Design Coverage in Software Testing - GeeksforGeeks.
質問 # 83
Which of the following BEST matches the attributes with a level of testing?
I Stubs and drivers are often used
II The lest environment should correspond to the production environment III Finding defects is not the main focus IV Testing can be based on use cases V Testing is normally performed by testers VI Testing for functional and non-functional characteristics
- A. Component - IV
Integration -1
System - VI
Acceptance - V - B. Component-I
Integration - V
System - II
Acceptance - IV - C. Component - VI
Integration - IV
System -1
Acceptance - 111 - D. Component - V
Integration - II
System - IV
Acceptance - VI
正解：D
解説：
The relationship between impact analysis and regression testing in maintenance testing is that impact analysis is used to evaluate the amount of regression testing to be performed. Maintenance testing is a type of testing that is performed on an existing software product after it has been delivered or deployed, in order to ensure that it still meets its requirements and functions correctly after a change or a modification. Maintenance testing can be triggered by various reasons, such as corrective maintenance (fixing defects), adaptive maintenance (adapting to new environments), perfective maintenance (improving performance), preventive maintenance (avoiding future problems), etc. Impact analysis is a technique that is used to assess the extent and nature of changes introduced by maintenance activities on the software product or project. Impact analysis helps to identify which parts of the software product are affected by the changes, which parts need to be modified or updated accordingly, which parts need to be retested or verified for correctness or compatibility, etc. Regression testing is a type of testing that verifies that previously tested software still performs correctly after a change or a modification. Regression testing helps to detect any side effects or unintended consequences of maintenance activities on the software product's functionality or quality. Regression testing can be performed at various levels and scopes depending on the impact analysis results. Therefore, in maintenance testing, impact analysis is used to evaluate the amount of regression testing to be performed. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 20.
質問 # 84
A mid-size software product development company has analyzed data related to defects detected in its product and found out that detects fixed in earlier builds are getting re-opened after a few months.
The company management now seeks your advice in order to reverse this trend and prevent re-opening of defects fixed earlier.
What would be your FIRST recommendation to the company?
- A. Verify existing regression test suite are adequate, and augment it, if required, in order to ensure that defects fixed earlier get re-tested in each subsequent build
- B. Automate existing test suits so that lesser time is spent on execution of each test, and more tests can be executed m the available time thus leading to a lower probability of defects slipping by
- C. If required, tram the teams responsible for development and testing of the modules containing maximum number of defects, and if this does not help, replace them with more knowledgeable people
- D. Analyze the product modules containing maximum defects, and get them thoroughly tested and defects fixed as a one-time activity
正解：A
解説：
Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes. Regression testing can help prevent re-opening of defects fixed earlier by ensuring that they do not cause any new failures or side effects. The first recommendation to the company is to verify existing regression test suite are adequate, and augment it, if required, in order to ensure that defects fixed earlier get re-tested in each subsequent build. This can help improve the coverage and effectiveness of regression testing and detect any regression defects as soon as possible. Automating existing test suites may also help reduce the time and effort required for regression testing, but this is not the first recommendation, as automation may not be feasible or cost-effective for all test cases. Analyzing the product modules containing maximum defects and getting them thoroughly tested and defects fixed as a one-time activity may also help reduce the defect density and improve the quality of those modules, but this is not the first recommendation, as it does not address the root cause of re-opening defects fixed earlier. Training or replacing the teams responsible for development and testing of the modules containing maximum number of defects may also help improve their skills or performance, but this is not the first recommendation, as it may not be necessary or appropriate for all teams.
Verified References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 2, page 19; Chapter 4, page 45.
質問 # 85
Which of the following statements about testware are correct?
I When closing the test activities, all the testware resources can be uninstalled and released II All the testware should be subject to Configuration Management III. The testware. at the end of the project, should be transferred to the organization responsible for maintenance IV The developers are responsible for the correct installation of the testware
- A. II, Ill
- B. I, IV
- C. I, Ill
- D. II, IV
正解：A
解説：
Testware is a term that refers to all artifacts produced during the testing process, such as test plans, test cases, test scripts, test data, test results, defect reports, etc. The following statements about testware are correct:
II) All the testware should be subject to Configuration Management. Configuration management is a process that establishes and maintains consistency among work products throughout their life cycle. Configuration management applies to all testware, as it helps ensure their quality and consistency, track their changes and defects, control their versions and access rights, and link them to other artifacts.
III) The testware at the end of the project should be transferred to the organization responsible for maintenance. Maintenance testing is testing performed on a software product after delivery to correct defects or improve performance or other attributes. Maintenance testing requires testware from previous testing activities or phases, such as test cases, test data, test results, etc. Therefore, the testware at the end of the project should be transferred to the organization responsible for maintenance testing, such as support team or maintenance team. The following statements about testware are incorrect:
I) When closing the test activities, all the testware resources can be uninstalled and released. This statement is incorrect, as some testware resources may still be needed for future testing activities or phases, such as maintenance testing or regression testing. Therefore, when closing the test activities, some testware resources should be archived and stored for future use, while others can be uninstalled and released.
IV) The developers are responsible for the correct installation of the testware. This statement is incorrect, as the testers are responsible for the correct installation of the testware. The testers should ensure that they have access to all necessary testware resources and that they are installed and configured properly before starting the test execution. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 6, page 58-61.
質問 # 86
A software module to be used in a mission critical application incorporates an algorithm for secure transmission of dat a.
Which review type is most appropriate to ensure high quality and technical correctness of the algorithm?
- A. Management Review
- B. Technical Review
- C. Informal Review
- D. Walkthrough
正解：B
解説：
A technical review is a type of formal review that involves a team of technical experts who evaluate a software product against a set of predefined quality criteria. A technical review is suitable for ensuring high quality and technical correctness of complex or critical software components, such as algorithms, architectures or designs. A technical review is not a walkthrough, which is an informal review led by the author of the work product. A technical review is not an informal review, which is a review that does not follow a defined process and has no formal entry or exit criteria. A technical review is not a management review, which is a type of formal review that focuses on business aspects and project progress. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 29-30.
質問 # 87
A calculator software is used to calculate the result for 5+6.
The user noticed that the result given is 6.
This is an example of;
- A. Error
- B. Fault
- C. Failure
- D. Mistake
正解：C
解説：
According to the ISTQB Glossary of Testing Terms, Version 4.0, 2018, page 18, a failure is "an event in which a component or system does not perform a required function within specified limits". In this case, the calculator software does not perform the required function of calculating the correct result for 5+6 within the specified limits of accuracy and precision. Therefore, this is an example of a failure.
The other options are incorrect because:
A mistake is "a human action that produces an incorrect result" (page 25). A mistake is not an event, but an action, and it may or may not lead to a failure. For example, a mistake could be a typo in the code, a wrong assumption in the design, or a misunderstanding of the requirement.
A fault is "a defect in a component or system that can cause the component or system to fail to perform its required function" (page 16). A fault is not an event, but a defect, and it may or may not cause a failure. For example, a fault could be a logical error in the code, a missing specification in the design, or a contradiction in the requirement.
An error is "the difference between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition" (page 15). An error is not an event, but a difference, and it may or may not result in a failure. For example, an error could be a rounding error in the calculation, a measurement error in the observation, or a deviation error in the condition.
Reference = ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 15-18, 25; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 96, page 34.
質問 # 88
Which of the following s the most correct statement about state testing techniques?
- A. Static techniques find more detects then dynamic techniques.
- B. Static techniques can be used before all code is ready for execution
- C. Static techniques can be used by inexperienced users.
- D. Static techniques are always cheaper than dynamic techniques.
正解：B
解説：
State testing techniques are a type of dynamic testing techniques that are based on the behavior of the system under test for different input conditions and events. Dynamic testing techniques require the system to be executed with test cases, whereas static testing techniques do not. Static testing techniques can be applied before the code is ready for execution, such as reviews, inspections, walkthroughs, and static analysis. Static testing techniques can help find defects early in the development process, improve the quality of the code, and reduce the cost and effort of dynamic testing. References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Chapter 4, Section 4.2.1, Page 281; ISTQB Glossary of Testing Terms v4.0, Page 292
質問 # 89
4 equivalence classes are given for integer values:
0 < x <100
100<= x <= 200
200 < x < 500
x >= 500
Which of the following options represent correct set of data for valid equivalence class partitions?
- A. 0.50; 100; 150.200.350.500;
- B. 0. 1.99, 100.200,201.499, 500;
- C. 50; 100; 200. 1000
- D. 50; 100; 250; 1000
正解：A
解説：
The correct set of data for valid equivalence class partitions should include one value from each equivalence class, and no value from outside the range. Option C satisfies this condition, as it has one value from each of the four equivalence classes (50, 100, 250, 500). Option A has two values from the same equivalence class (100 and 200), option B has values outside the range (0 and 0.99), and option D has two values from the same equivalence class (1000 and 500). Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 35.
質問 # 90
......
ISTQB-CTFL試験問題集合格させるのは更新されたのは2024年年最新の認証済み試験問題：https://www.jpntest.com/shiken/ISTQB-CTFL-mondaishu
ガイド（2024年最新）実際のISTQB ISTQB-CTFL試験問題：https://drive.google.com/open?id=13OLZysEAcjZvWFoZhdl-xvld6sOhM-M3