2024年03月25日に更新された最新のFast2test ISTQB-CTFL試験問題リアルISTQB-CTFL問題集で
ISTQB-CTFL別格な問題集で最上級の成績にさせるISTQB-CTFL問題
質問 # 44
Mark the correct sentences:
* Defects are a result of environmental conditions and are also referred to as "Failures"
* A human mistake may produce a defect
* A system mil totally fail to operate correctly when a failure exists in it
* When a defect exists in a system it may result in a failure
* Defects occur only as a result of technology changes
- A. I, II
- B. II, IV
- C. II, III, IV
- D. IV, V
正解：B
解説：
* The question is about marking the correct sentences among the given statements related to defects, failures, and mistakes. According to the ISTQB glossary, the definitions of these terms are1:
* Defect: A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system.
* Failure: An event in which a component or system does not perform a required function within specified limits.
* Mistake: A human action that produces an incorrect result.
* Therefore, out of the five given statements, only two are correct, namely:
* A human mistake may produce a defect: This is true, as a mistake is a source or cause of a defect, e.g. a programmer may make a mistake in writing a code statement, which results in a defect in the software component.
* When a defect exists in a system it may result in a failure: This is true, as a defect is a potential or actual cause of a failure, e.g. a defect in the software component may cause the system to fail to perform a required function when the defect is encountered during execution.
* The other three statements are incorrect, namely:
* Defects are a result of environmental conditions and are also referred to as "Failures": This is false, as defects are not a result of environmental conditions, but of mistakes or other factors, and defects are not the same as failures, but rather the causes of failures.
* A system will totally fail to operate correctly when a failure exists in it: This is false, as a system may not necessarily fail completely or stop operating when a failure occurs, but may continue to operate with reduced functionality or performance, or with incorrect results.
* Defects occur only as a result of technology changes: This is false, as defects can occur due to various reasons, not only technology changes, such as human mistakes, design flaws, requirement changes, hardware failures, etc.
References:
* 1: ISTQB Glossary of Testing Terms 4.0, 2023, available at ISTQB) and ASTQB).
質問 # 45
Which of the following is NOT a product risk?
- A. Problems in defining the right requirements
- B. Software does not perform the intended functions
- C. Failure-prone software is delivered
- D. Poor software usability
正解：A
解説：
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.
質問 # 46
Manager responsibilities in formal review includes ad except one of the following:
- A. Allocate time for review
- B. Decide on the execution of reviews
- C. Planning the review
- D. Determines if the review objectives have been met
正解：D
解説：
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.
質問 # 47
Which of the following lists factors That contribute to PROJECT risks?
- A. skill and staff shortages; software does not perform its intended functions; problems in defining the right requirements.
- B. problems in defining the right requirements; contractual issues; poor software quality characteristics.
- C. skill and staff shortages; problems in defining the right requirements, contractual issues.
- D. poor software quality characteristics; software does not perform its intended functions.
正解：C
解説：
Project risks are the uncertainties or threats that may affect the project objectives, such as scope, schedule, cost, and quality. According to the ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, some of the factors that contribute to project risks are:
* Skill and staff shortages: This factor refers to the lack of adequate or qualified human resources to perform the project tasks. This may result in delays, errors, rework, or low productivity.
* Problems in defining the right requirements: This factor refers to the difficulties or ambiguities in eliciting, analyzing, specifying, validating, or managing the requirements of the project. This may result in misalignment, inconsistencies, gaps, or changes in the requirements, affecting the project scope and quality.
* Contractual issues: This factor refers to the challenges or disputes that may arise from the contractual agreements between the project parties, such as clients, suppliers, vendors, or subcontractors. This may result in legal, financial, or ethical risks, affecting the project delivery and satisfaction.
The other options are not correct because they list factors that contribute to PRODUCT risks, not project risks.
Product risks are the uncertainties or threats that may affect the quality or functionality of the software product or system. Some of the factors that contribute to product risks are:
* Poor software quality characteristics: This factor refers to the lack of adherence or compliance to the quality attributes or criteria of the software product or system, such as reliability, usability, security, performance, or maintainability. This may result in defects, failures, or dissatisfaction of the users or stakeholders.
* Software does not perform its intended functions: This factor refers to the deviation or discrepancy between the expected and actual behavior or output of the software product or system. This may result in errors, faults, or malfunctions of the software product or system.
References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 1: Fundamentals of Testing, Section 1.5: Risks and Testing, Pages 14-16.
質問 # 48
Whichofthe 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. II. IV
- B. III. IV
- C. I, Ill
- D. I. II
正解：D
解説：
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 References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 2, page 20-21; Chapter 4, page 34-35.
質問 # 49
Which of the following statements describes regression testing?
I, Retesting of a fixed defect
II, Testing of an already tested program
III, Testing of new functionality in a program
IV, Regression testing applies only to functional testing
V Tests that do not nave to be repeatable, because They are only used once
- A. II
- B. I, III, IV
- C. I, IV
- D. II, IV, V
正解：A
解説：
Regression testing is the re-running of functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change1 It does not involve retesting of a fixed defect, testing of new functionality, or applying only to functional testing. Tests that are used for regression testing should be repeatable, because they are used to verify the stability of the software after each change2 Reference = ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Chapter 4, Section 4.2.2, Page 291; ISTQB Glossary of Testing Terms v4.0, Page 292
質問 # 50
A QA manager of a start-up company needs to implement within a week a low cost incident management tool. Which of the following is the best option?
- A. Purchase and deploy an incident management tool
- B. Document incidents on a large board in the lab
- C. Manage the incidents through E-mails and phone calls
- D. Manage the incidents in a spreadsheet posted on the intranet
正解：D
解説：
An incident is any event that occurs during testing that requires investigation. An incident management tool is a software tool that supports recording and tracking incidents throughout their life cycle. A QA manager of a start-up company needs to implement within a week a low cost incident management tool. The best option for this case is to manage the incidents in a spreadsheet posted on the intranet. This option has several advantages over other options:
It is low cost, as it does not require purchasing any additional software or hardware.
It is easy to implement within a week, as it does not require installing or configuring any complex software or hardware.
It is accessible and transparent, as it can be viewed and updated by anyone who has access to the intranet.
It is structured and organized, as it can store and display various information about incidents, such as identifier, summary, description, severity, priority, status, resolution, etc. The other options are not suitable for this case, as they have several disadvantages over the chosen option:
Documenting incidents on a large board in the lab is not a good option, as it is not accessible or transparent to anyone who is not physically present in the lab. It is also not structured or organized, as it may not store or display all the necessary information about incidents.
Purchasing and deploying an incident management tool is not a good option, as it is not low cost or easy to implement within a week. It may require spending a significant amount of money and time on acquiring, installing and configuring the software or hardware.
Managing the incidents through emails and phone calls is not a good option, as it is not structured or organized. It may lead to confusion, inconsistency or loss of information about incidents. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 32-33.
質問 # 51
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. Send an email to the developer and not report the bug
- C. Try to identify the code fragment causing the problem
- D. Report the incident as is without any further action
正解：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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 32-33.
質問 # 52
A software module to be used in a mission critical application incorporates an algorithm for secure transmission of data.
Which review type is most appropriate to ensure high quality and technical correctness of the algorithm?
- A. Management Review
- B. Informal Review
- C. Walkthrough
- D. Technical Review
正解：D
解説：
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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 29-30.
質問 # 53
Which or the following is a valid collection of equivalence classes for the following problem: An integer field shall contain values from and including 1 to and including 15.
- A. Less than 0.1 through 14. 15 and more
- B. negative numbers. 1 through 15. above 15
- C. Less than 1.1 through 15. more than 15
- D. Less than 1.1 through 14. more than 15
正解：C
解説：
Equivalence partitioning is a black-box test design technique where inputs to the software or system are divided into groups that are expected to exhibit similar behavior. For an integer field that should accept values from 1 to 15, the valid equivalence class is 1 through 15. The invalid equivalence classes are numbers less than 1 and numbers more than 15. Therefore, option D, "Less than 1, 1 through 15, more than 15," correctly identifies the valid equivalence class along with the two invalid classes, covering all possible input scenarios for the field. Options A, B, and C either do not accurately capture the valid range or incorrectly specify the range boundaries.
質問 # 54
Your manager asked you when testing will be complete. In order to answer this question, you'll most likely use:
- A. Your colleagues advice
- B. A Test Oracle
- C. Test progress reports
- D. A conversion spreadsheet
正解：C
解説：
When a manager asks when testing will be complete, the most appropriate and informative resource to provide an answer is test progress reports (Option A). Test progress reports contain detailed information on the status of testing activities, including what has been accomplished, what remains to be done, the results of the tests conducted, and any issues or risks that might impact the completion of testing. These reports allow for an informed assessment of the testing progress and estimation of when testing might be completed. Options B, C, and D do not provide the structured, detailed, and specific information required to accurately answer the manager's question about the completion of testing.
質問 # 55
For a mandatory input field "ZIP code" the following rules are given:
1 - The valid ZIP code format is 5 numeric digits.
2 - The code has to exist in the post office's official ZIP code list
Using equivalence classes partitioning, how many test cases are required to test this field?
- A. 0
- B. 1
- C. 2
- D. 3
正解：C
解説：
Equivalence classes 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 classes partitioning can be used to reduce the number of test cases by selecting onerepresentative value from each partition. For the ZIP code field, there are four equivalence classes based on the given rules:
* Valid ZIP code format and valid ZIP code value (e.g., 12345)
* Valid ZIP code format and invalid ZIP code value (e.g., 99999)
* Invalid ZIP code format and valid ZIP code value (e.g., 1234)
* Invalid ZIP code format and invalid ZIP code value (e.g., ABCDE) Therefore, four test cases are required to test this field, one for each equivalence class. Verified References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 4, page 37-38.
質問 # 56
As the last stage of a test cycle of an embedded device, you are performing exploratory testing. You observed that some character. (A, X andZ)sent via a serial port to the device do not get registered on the device whereas they should be. You suspect that this could be due to a wrong configuration of the "bit parity" parameter.
Which of the following items of an incident report would you beUNABLEto write down based on this information?
- A. Test case identifier
- B. Test setup details
- C. Expected result
- D. Actual result
正解：A
解説：
An incident report is a document that records the details of an incident. An incident report typically contains the following items:
* Identifier: A unique identifier for the incident report
* Summary: A concise summary of the incident
* Description: A detailed description of the incident, including the steps to reproduce it, the expected and actual results, and any relevant screenshots or logs
* Severity: The degree of impact that the incident has on the system
* Priority: The level of urgency for resolving the incident
* Status: The current state of the incident, such as new, open, resolved, closed, etc.
* Resolution: The action taken to resolve the incident, such as fix, workaround, reject, etc. Based on the information given in the question, the tester would be able to write down all of these items except for the test case identifier. A test case identifier is a unique identifier for a test case that is used to link it to other test artifacts, such as test plans, test scripts, test results or incident reports. However, since the tester is performing exploratory testing, there is no predefined test case that can be associated with the incident. 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 does not use formal test cases or scripts, but rather uses test charters or missions that guide the tester's actions and objectives. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page
32-33; Chapter 5, page 47-48.
質問 # 57
For the following pseudo-code determine number of tests required for 100% statement coverage IF Gender = Boy If Age > 3 AND Age < 5 Shoe Size = 1 ELSE IF Age >=5 AND Age < 7 Shoe Size = 2 ENDIF ELSE IF Age > 3 AND Age < 5 Shoe Size = 0 ELSE IF Age >=5 AND Age < 7 Shoe Size = 1 ENDIF ENDIF
- A. 0
- B. 1
- C. 6
- D. 2
正解：B
解説：
To achieve 100% statement coverage, we need to design test cases that ensure every statement in the given pseudo-code is executed at least once. Analyzing the pseudo-code, we notice that there are conditions based on two variables: Gender and Age. To cover all statements, we need to consider the paths that lead to each assignment of the Shoe Size variable.
Gender = Boy, Age <= 3 (Shoe Size assignment is not reached, but the condition is evaluated) Gender = Boy, Age > 3 AND Age < 5 (Shoe Size = 1) Gender = Boy, Age >= 5 AND Age < 7 (Shoe Size = 2) Gender != Boy, Age <= 3 (Again, Shoe Size assignment is not reached, but the condition is evaluated) Gender != Boy, Age > 3 AND Age < 5 (Shoe Size = 0) Gender != Boy, Age >= 5 AND Age < 7 (Shoe Size = 1) However, upon closer inspection, we see that tests 1 and 4 do not contribute to statement coverage as they do not lead to a Shoe Size assignment. Therefore, we only need 4 test cases to achieve 100% statement coverage, making option B the correct answer.
質問 # 58
Which of the following definitions is NOT true?
- A. Test comparators determine differences between files, databases or test results.
- B. Test data preparation tools fill databases, create files or data transmissions to set up test data to be used during the execution of tests.
- C. Test Management tools monitor and report on how a system behaves during the testing activities.
- D. Test execution tools execute test objects using automated test scripts.
正解：C
解説：
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.
質問 # 59
An Incident Management tool implements the following defect states; Open, Assigned, Solved, Closed Consider the following defect report:
Id T000561
Test Object "Warehouse Management' application
Tester name; John Bishop
Date: 10th. April 2010
Test Case MRT558I
Status OPEN
Severity Serious
Priority
Problem- After inputting the Total Quantity item = 450 in the SV034 screen, the system shows an unexpected Error message=47 Correction:
Developer name:
Closing date:
Which of the following is a valid criticism of this report?
- A. There is no link to the applicable requirement (traceability)
- B. The version of the application is missing
- C. The description is not highlighting the source of the problem
- D. The Priority, the Correction description and the Developer name are missing
正解：B
解説：
A valid criticism of this report is that the version of the application is missing. The version of the application is an important piece of information that should be included in a defect report, as it helps to identify which release or build of the software product contains the defect. The version of the application can also help to reproduce and debug the defect, as different versions may have different behaviors or features. The other options are not valid criticisms of this report. The priority, the correction description and the developer name are not missing, but rather not applicable for this report. The priority is a measure of how urgently a defect needs to be fixed, which can be assigned by the project manager or the defect tracking system, not by the tester who reports the defect. The correction description and the developer name are information that are added after the defect has been resolved, not when it has been reported. There is no link to the applicable requirement (traceability) is not a valid criticism of this report, because traceability is not a mandatory attribute of a defect report, but rather an optional one. Traceability is a relationship between two or more entities (such as requirements, test cases, defects, etc.) that shows how they are related or dependent on each other. Traceability can help to verify that the requirements are met by the test cases and defects, but it is not essential for reporting a defect. The description is not highlighting the source of the problem is not a valid criticism of this report, because highlighting the source of the problem is not a responsibility of the tester who reports the defect, but rather of the developer who fixes the defect. The description should provide enough information to describe what happened when the defect occurred, such as input values, expected results, actual results, error messages, screenshots, etc., but it does not need to explain why or how it happened. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 140.
質問 # 60
Can "cost" be regarded as Exit criteria?
- A. Yes. Spending too much money on test ng will result in an unprofitable product, and having cost as an exit criterion helps avoid this
- B. No. The financial value of product quality cannot be estimated, so it is incorrect to use cost as an exit criterion
- C. No The cost of testing cannot be measured effectively, so it is incorrect to use cost as an exit criterion
- D. Yes. Going by cost as an exit criterion constrains the testing project which will hello achieve the desired quality level defined for the project
正解：A
解説：
Cost can be regarded as an exit criterion for testing, because it is a factor that affects the profitability and feasibility of the software product. Testing is an investment that aims to improve the quality and reliability of the software product, but it also consumes resources, such as time, money, and human effort. Therefore, testing should be planned and executed in a way that balances the cost and benefit of testing activities. Having cost as an exit criterion helps to avoid spending too much money on testing, which may result in an unprofitable product or a loss of competitive advantage. Cost can also help to prioritize and focus the testing efforts on the most critical and valuable features andfunctions of the software product. However, cost should not be the only exit criterion for testing, as it may not reflect the true quality and risk level of the software product. Other exit criteria, such as defect rate, test coverage, user satisfaction, etc., should also be considered and defined in the test plan.
The other options are incorrect, because they either deny the importance of cost as an exit criterion, or they make false or unrealistic assumptions about the cost of testing. Option B is incorrect, because the financial value of product quality can be estimated, for example, by using cost-benefit analysis, return on investment, or cost of quality models. Option C is incorrect, because going by cost as an exit criterion does not necessarily constrain the testing project or help achieve the desired quality level. Cost is a relative and variable factor that depends on the scope, complexity, and context of the software product and the testing project. Option D is incorrect, because the cost of testing can be measured effectively, for example, by using metrics, such as test effort, test resources, test tools, test environment, etc.
質問 # 61
......
ISTQB-CTFL試験問題集でベストISTQB-CTFL試験問題を試そう：https://jp.fast2test.com/ISTQB-CTFL-premium-file.html
手に入れよう！最新ISTQB-CTFL認定有効な試験問題集解答：https://drive.google.com/open?id=1DwLrzdEhEajMhoRsmnBK1YwD7N6phNm4