ISTQB ISTQB-CTFLテストエンジン練習テスト問題、試験問題集
100%無料ISTQB-CTFL日常練習試験には78問があります
質問 # 26
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: pulled to support tasks and having less time for testing, Disadvantage less chances to move a tester to development
- B. Advantage: More independence in deciding what and how to test,
Disadvantage: Isolation from me development team knowledge - C. Advantage: increased chances to move a tester to development;Disadvantage: pulled to support tasks and having less time for testing
- D. Advantage: being closer to customer perspective,
Disadvantage less independence in perspectives
正解：D
解説：
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.
質問 # 27
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. Integration and system testing are applicable when V-model is used.
Component and acceptance testing are applicable when iterative development models are used. - D. All testing levels are applicable, independent of which software development life-cycle process (V-model. iterative, incremental) is used.
正解：D
解説：
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.
質問 # 28
Which of the following statements is CORRECT?
- A. Test cases are made up of input values, expected results and actual results developed to cover test objectives
- B. Test cases are sequences of actions for test execution specified during the test implementation activity D. Test cases are derived during the test design activity to cover test objectives or test conditions
- C. Test cases describe items or events to test that are derived from the test basis during the test analysis activity
正解：B
解説：
A test case is a set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition. A test case is a sequence of actions for test execution that can be followed by a tester or a test automation tool. A test case is specified during the test implementation activity, which is the activity that prepares the testware needed for test execution. A test case does not include actual results, as these are obtained during test execution and compared with the expected results. A test case does not describe items or events to test, as these are derived from the test basis during the test analysis activity. A test case is not derived during the test design activity, as this is the activity that specifies the test conditions or objectives that need to be tested. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 3, page 23-24; Chapter 4, page 34.
質問 # 29
Which of the following is NOT a deciding factor m determining the extent of testing required?
- A. Budget to do testing
- B. A particular tester involved in testing
- C. Level of risk of the product or features
- D. Time available to do testing
正解：B
解説：
The extent of testing required for a software product depends on various factors, such as the level of risk, the budget, and the time available. The level of risk reflects the potential impact of failures on the stakeholders and the environment. The budget determines how much resources can be allocated for testing. The time available defines the schedule and deadlines for testing activities. The particular tester involved in testing is not a deciding factor for the extent of testing required, as testing should be based on objective criteria and not on personal preferences or abilities. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 2, page 14-15.
質問 # 30
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. I, IV
- B. II, Ill
- C. I, Ill
- D. II, IV
正解：B
解説：
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.
質問 # 31
The following requirement is given "Set X to be the sum of Y and Z".
All the following four implementations have bugs.
Which one of the following bugs can be caught by Static Analysis?
- A. int x = 1.
int y = 2.
int z = 3.
X = z-y - B. int y = 2
Int z = 3.
Y = z+y - C. int x = 1.
int y = 2.
int y = 3.
X = y=z; - D. int x = 1.
Int y = 2.
Int z = 3.
Z = x +y
正解：C
解説：
Static analysis is a technique that analyzes the source code or other software artifacts without executing them. Static analysis can detect defects such as syntax errors, coding standards violations, potential security vulnerabilities, or logical flaws. Static analysis can catch the bug in the first implementation, as it contains two syntax errors: the variable y is declared twice, and the assignment statement X = y=z is invalid. Static analysis cannot catch the bugs in the other three implementations, as they are logical errors that do not violate any syntax rules, but produce incorrect results. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 3, page 25-26.
質問 # 32
Which of the following does MOT describe a reason why testing is necessary?
- A. The customer decided that 100% branch coverage shall be achieved
- B. The risks associated with delivering the system are far higher than the cost of testing
- C. For avionics and pharmaceutical systems software testing is mandated by standards
- D. The acquisition of test automation tools was based on the assumption that it will be used m all projects
正解：D
解説：
Testing is necessary for various reasons, such as:
To detect defects and failures that may affect the quality, performance, reliability or security of a software product or system To verify that a software product or system meets its specified requirements, expectations and standards To validate that a software product or system fulfills its intended purpose and satisfies its stakeholders' needs To provide information and feedback about the status and risks of a software product or system To comply with regulations or contractual obligations that mandate testing for certain types of software products or systems The following statements describe some reasons why testing is necessary:
A) The customer decided that 100% branch coverage shall be achieved. This is a reason why testing is necessary, as it reflects a contractual obligation or a quality standard that requires testing to measure and achieve a certain level of code coverage.
C) For avionics and pharmaceutical systems software testing is mandated by standards. This is a reason why testing is necessary, as it reflects a regulation or a compliance requirement that mandates testing for certain types of software products or systems that have high safety or security risks.
D) The risks associated with delivering the system are far higher than the cost of testing. This is a reason why testing is necessary, as it reflects a risk-based approach that considers testing as an investment to reduce the probability and impact of potential failures or defects. The following statement does not describe a reason why testing is necessary:
B) The acquisition of test automation tools was based on the assumption that it will be used m all projects. This is not a reason why testing is necessary, as it reflects a business decision or a resource allocation that does not justify the need or purpose of testing. Test automation tools are not always suitable or beneficial for all projects, and testing can be performed with or without test automation tools. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 1, page 5-6.
質問 # 33
Why should you choose a test technique?
- A. Because you need to match the way you test to the content of the product under test
- B. Because choosing a test technique is a common practice in software testing
- C. Because of the time constraints that usually accompany a test project
- D. Because this way you cover the full scope of the product's functionality
正解：A
解説：
You should choose a test technique because you need to match the way you test to the content of the product under test. A test technique is a method or process for deriving and selecting test cases based on some criteria or rules. Different test techniques are suitable for different types of software products, depending on their characteristics, functionalities, requirements, specifications, risks, etc. Choosing a test technique helps to ensure that the test cases are relevant, effective, and efficient for the product under test. The other options are not correct reasons to choose a test technique. Time constraints are not a factor for choosing a test technique, but rather for prioritizing or optimizing testing activities. Covering the full scope of the product's functionality is not a guarantee of choosing a test technique, but rather a goal of testing. Choosing a test technique is not a common practice in software testing, but rather a professional skill and responsibility. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 31.
質問 # 34
Which of the following is a key characteristic of informal reviews?
- A. Individual preparation
- B. Kick-off meeting
- C. Low cost
- D. Metrics analysis
正解：C
解説：
A key characteristic of informal reviews is low cost. Informal reviews are a type of review that does not follow a formal process or have any formal documentation. Informal reviews are usually performed by individuals or small groups of peers or colleagues who have some knowledge or interest in the product under review. Informal reviews can be done at any time and for any purpose, such as checking for errors, clarifying doubts, sharing ideas, etc. Informal reviews have low cost, as they do not require much time, effort, or resources to conduct. The other options are not key characteristics of informal reviews. Kick-off meeting is a characteristic of formal reviews, such as inspections or walkthroughs. Kick-off meeting is a meeting that is held before the review process starts, where the roles and responsibilities of the participants are defined, the objectives and scope of the review are agreed, and the logistics and schedule of the review are planned. Individual preparation is a characteristic of formal reviews, such as inspections or walkthroughs. Individual preparation is an activity that is performed by the reviewers before the review meeting, where they examine the product under review and identify any issues or questions that need to be discussed or resolved during the review meeting. Metrics analysis is a characteristic of formal reviews, such as inspections or walkthroughs. Metrics analysis is an activity that is performed after the review process is completed, where the data and results of the review are collected and analyzed to measure the effectiveness and efficiency of the review, as well as to identify any improvement actions or lessons learned for future reviews. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 9.
質問 # 35
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.
質問 # 36
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->S1->S2->S3
- B. S0->S1->S2->S3->S5->S3->S4
- C. S0->S1->S2->S3->S5^>S1
- D. S0->S1->S2->S3->S4
正解：A
解説：
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 Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 4, page 40-41.
質問 # 37
Which test approach will best fit a new project, with little documentation and high probability for bugs?
- A. Regression testing
- B. Exploratory testing
- C. Requirements based testing
- D. Metric based approach
正解：B
解説：
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. Exploratory testing is suitable for a new project with little documentation and high probability for bugs, as it can help uncover unknown requirements, assumptions and risks. Exploratory testing is not requirements based testing, which is an approach to testing that derives test cases from documented requirements or specifications. Requirements based testing is not feasible for a new project with little documentation, as it requires clear and complete requirements to be available. Exploratory testing is not metric based approach, which is an approach to testing that uses quantitative measures to monitor and control the testing process and evaluate the quality of the software product. Metric based approach is not effective for a new project with high probability for bugs, as it may not capture all aspects of quality and may lead to false confidence or unrealistic expectations. Exploratory testing is not regression testing, which is an approach to testing that verifies that previously tested software still performs correctly after changes. Regression testing is not relevant for a new project with no previous versions or baselines. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 5, page 47-48.
質問 # 38
A software system checks age in order to determine which welcome screen to display. Age groups are:
Group I: 0-12
Group II; 13-18
Group III: over 18
Which of the below represent boundary values?
- A. (0.12.13.18.19)
- B. (-1.0,11.12.13,14,18.19)
- C. (4.5.15.20)
- D. (-1.0.12.13.18,19)
正解：D
解説：
A correct list of boundary values for the age input should include the minimum and maximum values of each age group (0, 12, 13, 18), as well as the values just below and above each boundary (-1, 19). 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 A satisfies this condition, as it has all six boundary values (-1, 0, 12, 13, 18, 19). Option B has two values from the same equivalence class (12 and 13), option C has only four boundary values (0, 12, 18, 19), and option D has no boundary values at all. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 34.
質問 # 39
Which of the following is NOT an objective of testing?
- A. Finding defects
- B. Providing information for decision-making
- C. Gaining confidence about the level of quality of the software
- D. Analyzing and removing the cause of failures
正解：D
解説：
Analyzing and removing the cause of failures is not an objective of testing, but rather a task of development or maintenance. A failure is an event or behavior that deviates from the expected or specified result of a system under test. A failure is caused by an error (also known as a mistake or a fault) in the software code, design, or specification. Analyzing and removing the cause of failures is a process of locating and fixing errors in the software code, design, or specification, which is also known as debugging or defect resolution. Analyzing and removing the cause of failures does not aim to find or report defects, but rather to correct or prevent them. The other options are objectives of testing. Finding defects is one of the main objectives of testing, as it helps to improve the quality and reliability of the software product. Providing information for decision-making is another objective of testing, as it helps to support decision making and risk management. Gaining confidence about the level of quality of the software is another objective of testing, as it helps to assure that the software product meets its requirements and customer or user needs and expectations. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 3.
質問 # 40
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,15,350,351
- C. 14,351
- D. 5.175.500
正解：B
解説：
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.
質問 # 41
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 lest engineer should not re-run the tests, as they have already been run, and results recorded.
- B. The test engineer should re-run the tests, because the defect shows that the test cases need to be updated.
- C. 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 not re-run the tests, they should be part of the developer tests.
正解：C
解説：
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.
質問 # 42
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.
質問 # 43
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. II, Ill
- B. III, IV
- C. I, II
- D. I, IV
正解：D
解説：
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
質問 # 44
Which of the following is a correct reason to apply test automation?
- A. When there are a lot of repetitive testing tasks
- B. When it is easy to automate
- C. When it is cheap to buy test automation tools
- D. When a new test automation tool is launched
正解：A
解説：
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.
質問 # 45
......
有効な問題最新版を試そうISTQB-CTFLテスト解釈ISTQB-CTFL有効な試験ガイド：https://jp.fast2test.com/ISTQB-CTFL-premium-file.html
ISTQB-CTFL試験資料ISTQB学習ガイド：https://drive.google.com/open?id=1hpr4l4Y1WwNFC2yhTYhPG5UFs7jndkw7