[2023年11月] を試そう！リアルISTQB-CTFL問題集で100%無料ISTQB-CTFL試験問題集
ISTQB-CTFLのPDF問題集試験問題 有効なISTQB-CTFL問題集
質問 # 32
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. Analyze the product modules containing maximum defects, and get them thoroughly tested and defects fixed as a one-time activity
- B. 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
- C. 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
- D. 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
解説：
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 Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 2, page 19; Chapter 4, page 45.
質問 # 33
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, II
- B. II, Ill
- C. I, IV
- D. III, IV
正解：C
解説：
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
質問 # 34
Which of the following should be included in a test status report?
I Estimation details
II Total number of open and closed defects
III Actual effort spent
IV Defect reports
V Number of executed, failed, blocked tests
- A. III.V
- B. II, III
- C. I. II. IV
- D. II, III.V
正解：D
解説：
The following should be included in a test status report: total number of open and closed defects, actual effort spent, and number of executed, failed, and blocked tests. A test status report is a document that provides information on the results and status of testing activities for a given period or phase. A test status report should include information that is relevant, accurate, and timely for the intended audience and purpose. Some of the information that should be included in a test status report are: total number of open and closed defects, which can indicate the defect trend and defect density of the software product; actual effort spent, which can indicate the productivity and efficiency of the testing process; number of executed, failed, and blocked tests, which can indicate the test progress and test coverage of the software product. The following should not be included in a test status report: estimation details, defect reports, and impact analysis. Estimation details are not part of a test status report, but rather part of a test plan or a test estimation document. Estimation details provide information on the expected time, resources, and costs for testing activities, not on the actual results or status of testing activities. Defect reports are not part of a test status report, but rather separate documents that provide detailed information on individual defects found during testing. Defect reports include information such as defect description, defect severity, defect priority, defect status, defect resolution, etc. Defect reports can be referenced or summarized in a test status report, but not included in full. Impact analysis is not part of a test status report, but rather part of a risk assessment or prioritization process. Impact analysis provides information on the potential effects or consequences of a change or a defect on the software product or project. Impact analysis can be used to evaluate the amount or scope of testing to be performed, but not to report the results or status of testing activities. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 141.
質問 # 35
A test manager defined the following test levels in her test plan; Component, System and Acceptance.
Which Software Development lifecycle is the Test Manager most likely following?
- A. V-Model
- B. Prototyping
- C. Agile
- D. Waterfall
正解：A
解説：
The test manager is most likely following the V-model for software development. The V-model is a software development model that defines four testing levels that correspond to four development phases: component testing corresponds to component design, integration testing corresponds to architectural design, system testing corresponds to system requirements specification, and acceptance testing corresponds to user requirements specification. The V-model also defines the test planning and test execution activities for each testing level. Agile is a software development model that follows an iterative and incremental approach, where testing is integrated into each iteration and adapts to changing requirements and feedback. Waterfall is a software development model that follows a sequential and linear approach, where testing is performed after the development phase is completed. Prototyping is a software development model that involves creating a simplified version of the software to elicit user feedback and validate requirements before developing the final product. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 18.
質問 # 36
Which of the following statements about Experience Based Techniques (EBT) is correct?
- A. EBT is done as a second stage of testing, after non-experienced-based testing took place.
- B. EBT use tests derived from the test engineers' previous experience with similar technologies.
- C. EBT is based on the ability of the test engineer to implement various testing techniques.
- D. EBT require broad and deep knowledge in testing but not necessarily in the application or technological domain.
正解：B
解説：
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.
質問 # 37
Which of the following is NOT a common objective of testing?
- A. Debugging the software to find the reason for defects
- B. Preventing defects
- C. Providing information on the status of the system
- D. Finding defects in the software
正解：A
解説：
Debugging the software to find the reason for defects is not a common objective of testing, but rather a task of development or maintenance. Debugging is a process of locating and fixing errors in the software code, while testing is a process of finding and reporting defects in the software behavior or quality. Testing does not aim to fix defects, but rather to provide information on their existence and impact. The other options are common objectives of testing. Finding defects in the software is one of the main objectives of testing, as it helps to improve the quality and reliability of the software. Preventing defects is another objective of testing, as it helps to avoid rework and reduce costs and risks. Providing information on the status of the system is another objective of testing, as it helps to support decision making and risk management. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 3.
質問 # 38
Which of the following is NOT a product risk?
- A. Software does not perform the intended functions
- B. Problems in defining the right requirements
- C. Failure-prone software is delivered
- D. Poor software usability
正解：B
解説：
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, such as 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 Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 12.
質問 # 39
Which statement about use case testing is true?
- A. The lest cases are designed to find defects in the data flew.
- B. The test cases are designed to be used by real users, not by professional testers
- C. The test cases are always designed by customers or end users.
- D. The test cases are designed to find defects in the process flow.
正解：D
解説：
Use case testing is a technique that helps identify test cases that exercise the whole system on a transaction by transaction basis from start to finish. Use cases are descriptions of how users interact with the system to achieve a specific goal. Use case testing is not focused on data flow, but rather on process flow. Use case testing can be performed by professional testers, customers or end users, depending on the context. Use case testing does not require the test cases to be designed by customers or end users, but rather by anyone who has access to the use case specifications. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 4, page 36.
質問 # 40
Which of the following would be the LEAST likely to be used as the basis for a test exit criteria?
- A. Number of unfixed defects
- B. Test schedules
- C. Cost of testing performed so far
- D. Confidence of testers in tested code
正解：B
解説：
Test exit criteria are the conditions or requirements that must be met before testing can be concluded. Test exit criteria are usually defined in the test plan and agreed by the stakeholders. Test exit criteria can be based on various factors, such as test coverage, defect status, quality level, risk level, etc. Test schedules would be the least likely to be used as the basis for test exit criteria, because test schedules are not directly related to the quality or performance of the software product, but rather to the time or resources allocated for testing. Test schedules can be used as the basis for test entry criteria, which are the conditions or requirements that must be met before testing can start. The other options are more likely to be used as the basis for test exit criteria. Cost of testing performed so far can be used as a basis for test exit criteria, because it can indicate the return on investment or the cost-benefit ratio of testing. Confidence of testers in tested code can be used as a basis for test exit criteria, because it can reflect the level of satisfaction or assurance of the testers about the quality or reliability of the software product. Number of unfixed defects can be used as a basis for test exit criteria, because it can indicate the level of risk or impact of the remaining defects on the software product. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 13.
質問 # 41
Which of the following options cover the test types performed during typical system testing phase:
I Usability
II Requirements based scenarios
III Testing parts of the code in isolation
IV Correct order of parameters in API calls
- A. I. II
- B. III. IV
- C. II. IV
- D. I, Ill
正解：A
解説：
System testing is a level of testing performed to evaluate the behavior and quality of a whole software product or system. System testing can include various types of testing, such as:
I) Usability testing: A type of testing that evaluates how easy, efficient and satisfying it is to use the software product or system from the user's perspective.
II) Requirements based scenarios testing: A type of testing that verifies that the software product or system meets its specified requirements or user stories by executing realistic scenarios or workflows. System testing does not include the following types of testing, as they are more suitable for lower levels of testing, such as unit testing or integration testing:
III) Testing parts of the code in isolation: A type of testing that verifies the functionality and quality of individual software components or units by isolating them from other components or units.
IV) Correct order of parameters in API calls: A type of testing that verifies the functionality and quality of software components or units that communicate with each other through application programming interfaces (APIs) by checking the correct order and format of parameters in API calls. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 2, page 20-21; Chapter 4, page 34-35.
質問 # 42
Which of the following statements is LEAST likely to be describing component testing?
- A. It identifies defects in modules and classes.
- B. It mainly tests interfaces and interaction between components.
- C. It may be applied using a test-first approach.
- D. Simulators and stubs may be required.
正解：B
解説：
Component testing (also known as unit testing or module testing) is a level of testing that focuses on verifying the functionality and quality of individual software components (such as modules, classes, functions, methods, etc.). Component testing mainly tests interfaces and interaction between components, as well as internal logic and data structures of the components. Component testing may be applied using a test-first approach (such as test-driven development or behavior-driven development), where tests are written before the code is implemented. Component testing does not identify defects in modules and classes, as this is a result of component testing, not an objective. Simulators and stubs may be required for component testing, as they can simulate or replace missing or incomplete components or external systems that are needed for testing. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 19.
質問 # 43
Which of the following is true about Oracles?
- A. Oracles are derived from the design
- B. Oracles can be generated automatically using data generators
- C. Sometimes old version of a product can be used as an Oracle
- D. Oracles help in reproducing the irreproducible bugs
正解：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.
質問 # 44
Which are the MAIN goals of risk management in a software project?
- A. To increase focus on preventative processes and to increase satisfaction for the testers.
- B. To increase the success probability for the project regardless of costs.
- C. To control contractual problems and minimize the impacts of company policies.
- D. To reduce the probability of undesired situations and to reduce the effect of potential impact.
正解：D
解説：
Risk management is a process that identifies, analyzes, evaluates and mitigates risks in a software project. Risks are factors that may negatively affect the quality, schedule, budget or scope of a software project. The main goals of risk management in a software project are to reduce the probability of undesired situations and to reduce the effect of potential impact. This can be achieved by applying various strategies, such as avoidance, transfer, reduction or acceptance. Risk management does not aim to increase the success probability for the project regardless of costs, as this may not be feasible or realistic. Risk management does not aim to increase focus on preventative processes and to increase satisfaction for the testers, as these are secondary or indirect outcomes. Risk management does not aim to control contractual problems and minimize the impacts of company policies, as these are specific types of risks that may not apply to all projects. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 2, page 14-15.
質問 # 45
A software calculates the annual car tax using three inputs:
- E; the emission level of the vehicle
- P: the power of the vehicle
-T the type of the vehicle
The input value for P can be integer positive values between 15 and 350.
Which of the following answers contains a correct list of a boundary values for the P input?
- A. 15,350
- B. 14,351
- C. 14,15,350,351
- D. 5.175.500
正解：C
解説：
A correct list of boundary values for the P input should include the minimum and maximum values of the valid range (15 and 350), as well as the values just below and above the boundaries (14 and 351). Boundary value analysis is a test design technique that involves testing the values at or near the boundaries of an input domain or output range, as these values are more likely to cause errors than values in the middle. Option B satisfies this condition, as it has all four boundary values (14, 15, 350, 351). Option A has only two boundary values (14 and 351), option C has only two boundary values (15 and 350), and option D has no boundary values at all. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 34.
質問 # 46
How can testing contribute to higher quality?
- A. Testing help to measure the quality of software.
- B. Testing eliminates the risk with software.
- C. Testing ensures that remaining defects are documented.
- D. Testing removes errors in the software.
正解：A
解説：
Testing can contribute to higher quality by helping to measure the quality of software. Quality is defined as the degree to which a component or system satisfies specified requirements and customer or user needs and expectations. Testing is a process of evaluating a component or system by applying inputs and observing outputs, and comparing them with expected results. Testing can help to measure the quality of software by providing information on its functionality, performance, usability, security, reliability, etc. Testing can also help to identify and report defects in software, which can lead to improvement actions and quality assurance activities. The other options are not accurate descriptions of how testing can contribute to higher quality. Testing does not ensure that remaining defects are documented, but rather that detected defects are reported. Testing does not remove errors in software, but rather finds defects in software behavior or quality. Testing does not eliminate the risk with software, but rather assesses and manages the risk with software. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 3.
質問 # 47
Which of the following are valid testing principles?
I) Exhaustive testing is in general impossible.
II) Exhaustive testing should be executed for code intended to be reused.
III) Testing may guarantee that a program is correct.
IV) Testing cannot guarantee that a program is correct.
V) Defects cluster together in certain areas of the product.
- A. I, IV, V
- B. I, V
- C. II, Iv
- D. I, Ill
正解：A
解説：
Statements I, IV and V are valid testing principles according to the ISTQB syllabus. Statement I states that exhaustive testing is in general impossible, because it would require testing all possible inputs, outputs and combinations of states, which is usually impractical or impossible. Statement IV states that testing cannot guarantee that a program is correct, because testing can only show the presence of defects, not their absence. Statement V states that defects cluster together in certain areas of the product, which means that some modules or functions are more likely to contain defects than others. Statements II and III are invalid testing principles. Statement II states that exhaustive testing should be executed for code intended to be reused, which contradicts statement I. Statement III states that testing may guarantee that a program is correct, which contradicts statement IV. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, pages 4-5.
質問 # 48
Which type of software development product can undergo static testing?
- A. Static tests should be performed on the installation and user guide documents as these documents are used by the end user.
- 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. Any software development product can undergo static testing, including requirements specifications, design specifications and code.
- D. Static testing is done only on the requirements You need to execute the software in order to find defects in the code.
正解：C
解説：
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 Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 7.
質問 # 49
Which of the following is a correct reason to apply test automation?
- A. When a new test automation tool is launched
- B. When there are a lot of repetitive testing tasks
- C. When it is cheap to buy test automation tools
- D. When it is easy to automate
正解：B
解説：
A correct reason to apply test automation is when there are a lot of repetitive testing tasks. Test automation is the use of software tools or scripts to perform or support testing activities, such as test case execution, test result comparison, test data generation, etc. Test automation can be beneficial when there are a lot of repetitive testing tasks that need to be performed frequently or consistently, such as regression testing, performance testing, load testing, etc. Test automation can help to save time and effort, increase reliability and accuracy, and improve coverage and efficiency of testing. The other options are not correct reasons to apply test automation. When a new test automation tool is launched is not a reason to apply test automation, but rather a factor for choosing a test automation tool. When it is easy to automate is not a reason to apply test automation, but rather a factor for evaluating the feasibility of test automation. When it is cheap to buy test automation tools is not a reason to apply test automation, but rather a factor for estimating the cost and benefit of test automation. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 10.
質問 # 50
Consider the following testing levels:
1) Component Testing
2) Integration Testing
3) System Testing
4) Acceptance Testing
Which of the following statements is true?
- A. Acceptance testing is applicable for all software development models.
Component and system testing are applicable only for the V-model. - B. All the testing levels are applicable to V-model for software development.
Only acceptance testing is applicable for iterative models. - C. All testing levels are applicable, independent of which software development life-cycle process (V-model. iterative, incremental) is used.
- D. Integration and system testing are applicable when V-model is used.
Component and acceptance testing are applicable when iterative development models are used.
正解：C
解説：
All testing levels are applicable, independent of which software development life-cycle process (V-model, iterative, incremental) is used. Testing levels are defined based on the scope and objectives of testing, not on the software development model. Component testing, integration testing, system testing and acceptance testing are common testing levels that can be applied to any software development model, as long as they are planned and executed properly. The V-model is a software development model that emphasizes the relationship between each development phase and its corresponding testing phase. Iterative and incremental models are software development models that divide the development process into smaller cycles or iterations, where each iteration produces a working version of the software that can be tested and evaluated. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 18.
質問 # 51
Which of the following statements about test reports are TRUE?
I Test reports shall be approved by the test team.
II Test reports shall give stakeholders information as basis for decisions.
Ill Test reports shall summarize what happened through a period of testing.
IV Test reports shall be approved by the development team, the test team and the customer V Test reports shall include information about remaining risks.
- A. II, III, IV
- B. I, II, IV
- C. II, III, V
- D. I, III, v
正解：C
解説：
Statements II, III and V are true about test reports. Test reports are documents that provide information on the results and status of testing activities for a given period or phase. Test reports should give stakeholders information as basis for decisions, such as whether to release the software product, whether to continue testing, whether to change the scope or priorities of testing, etc. Test reports should summarize what happened through a period of testing, such as what test cases were executed, what defects were found, what risks were identified, what issues were encountered, what achievements were made, etc. Test reports should include information about remaining risks, such as what defects are still open, what test cases are still pending, what functionalities are still untested, what uncertainties are still unresolved, etc. Statements I and IV are not true about test reports. Test reports do not need to be approved by the test team, the development team, or the customer, unless it is specified by the test policy or the test plan. Test reports only need to be reviewed and verified by the test leader or the test manager before being distributed to the intended recipients. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 141.
質問 # 52
Manager responsibilities in formal review includes ad except one of the following:
- A. Determines if the review objectives have been met
- B. Decide on the execution of reviews
- C. Allocate time for review
- D. Planning the review
正解：A
解説：
A formal review is a type of review that follows a defined process with formal entry and exit criteria and roles and responsibilities for participants. A formal review can have various roles involved, such as manager, moderator, author, reviewer and scribe. The manager responsibilities in formal review include all except one of the following:
Planning the review (correct responsibility)
Determines if the review objectives have been met (incorrect responsibility) Decide on the execution of reviews (correct responsibility) Allocate time for review (correct responsibility) The responsibility of determining if the review objectives have been met belongs to the moderator role, not to the manager role. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 3, page 28-29.
質問 # 53
A test engineer finds a defect while testing. After the developer has fixed the defect, the test engineer decides to re-run a complete section of the tests. Which of the following is correct?
- A. The test engineer should re-run the tests, because the defect shows that the test cases need to be updated.
- B. The test engineer should not re-run the tests, they should be part of the developer tests.
- C. The lest engineer should not re-run the tests, as they have already been run, and results recorded.
- D. The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix.
正解：D
解説：
The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix. This is also known as regression testing, which is a type of testing that verifies that previously tested software still performs correctly after a change. Regression testing helps to detect any side effects or unintended consequences of a fix or a modification. The other options are incorrect reasons for re-running the tests. The test engineer should not re-run the tests, as they have already been run, and results recorded, because this ignores the possibility of new defects caused by the fix. The test engineer should not re-run the tests, they should be part of the developer tests, because this assumes that developer tests are sufficient and reliable, which may not be true. The test engineer should not re-run the tests, because the defect shows that the test cases need to be updated, because this does not address the impact of the fix on other test cases or functionalities. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 41.
質問 # 54
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 - VI
Integration - IV
System -1
Acceptance - 111 - B. Component-I
Integration - V
System - II
Acceptance - IV - C. Component - V
Integration - II
System - IV
Acceptance - VI - D. Component - IV
Integration -1
System - VI
Acceptance - V
正解：C
解説：
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.
質問 # 55
......
究極のISTQB-CTFL無料準備ガイド最新のISTQB練習テスト問題集：https://jp.fast2test.com/ISTQB-CTFL-premium-file.html
今すぐゲットせよ！高評価ISTQB ISTQB-CTFL試験問題集：https://drive.google.com/open?id=1DwLrzdEhEajMhoRsmnBK1YwD7N6phNm4