オンラインISTQB-CTFLテストブレーン問題集とテストエンジン [Q89-Q105]

Share

オンラインISTQB-CTFLテストブレーン問題集とテストエンジン

リアルISTQB ISTQB-CTFL試験問題集には正解170問題と解答があります

質問 # 89
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. negative numbers. 1 through 15. above 15
  • B. Less than 0.1 through 14. 15 and more
  • 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.


質問 # 90
What is test oracle?

  • A. The source of lest objectives
  • B. The source for the actual results
  • C. The source of expected results
  • D. The source of input conditions

正解:C

解説:
A test oracle is a mechanism or principle that can be used to determine whether the observed behavior or output of a system under test is correct or not1. A test oracle can be based on various sources of expected results, such as specifications, user expectations, previous versions, comparable systems, etc2. References:
ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Section 1.2.1, Page 91; ISTQB Glossary of Testing Terms, Version 4.0, Page 332.


質問 # 91
Which type of software development product can undergo static testing?

  • A. Static testing is done only on the code as part of the "code review" sessions Other documents are reviewed, but not by static testing.
  • B. Static testing is done only on the requirements You need to execute the software in order to find defects in the code.
  • C. Static tests should be performed on the installation and user guide documents as these documents are used by the end user.
  • D. Any software development product can undergo static testing, including requirements specifications, design specifications and code.

正解:D

解説:
Static testing is a form of testing that does not involve executing the software, but rather analyzing it for defects, errors, or violations of standards. Static testing can be applied to any software development product, including requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. Static testing can be done by using various techniques such as reviews, inspections, walkthroughs, checklists, static analysis tools, etc. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 7.


質問 # 92
Which statement best describes the key difference between a mindset for test activities and a mindset for development activities?

  • A. A tester is concerned with finding defects while a developer is interested in designing solutions
  • B. A tester is concerned with verifying the product while a developer possesses professional pessimism
  • C. A tester is interested in building solutions while a developer is concerned with verifying the product
  • D. A tester possesses professional pessimism while a developer is concerned with validating the product

正解:A

解説:
The key difference between the mindsets for test activities and development activities lies in the objectives: a tester is primarily concerned with finding defects to ensure product quality, while a developer focuses on designing and building solutions. This distinct focus helps ensure thorough quality checks and balances within the software development life cycle (ISTQB not-for-profit association).References:
* ISTQB Certified Tester Foundation Level Syllabus v4.0:
https://istqb-main-web-prod.s3.amazonaws.com/media/documents/ISTQB_CTFL_Syllabus-v4.0.pdf


質問 # 93
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. II, IV, V
  • D. I, IV

正解: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 References = 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


質問 # 94
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. The description is not highlighting the source of the problem
  • B. The Priority, the Correction description and the Developer name are missing
  • C. There is no link to the applicable requirement (traceability)
  • D. The version of the application is missing

正解:D

解説:
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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 140.


質問 # 95
You are testing a room upgrade system for a hotel. The system accepts three differed types of room (increasing order of luxury): Platinum. Silver and Gold Luxury. ONLY a Preferred Guest Card holder s eligible for an upgrade.
Below you can find the decision table defining the upgrade eligibility:

What is the expected result for each of the following test cases?
Customer A: Preference Guest Card holder, holding a Silver room
Customer B: Non Preferred Guest Card holder, holding a Platinum room

  • A. Customer A; doesn't offer any upgrade; Customer B: offers upgrade to Gold luxury room
  • B. Customer A: offers upgrade to Gold Luxury room; Customer B: doesn't offer any upgrade
  • C. Customer A: offers upgrade to Silver room; Customer B: offers upgrade to Silver room.
  • D. Customer A: doesn't offer any upgrade; Customer B: doesn't offer any upgrade.

正解:B

解説:
According to the decision table in the image, a Preferred Guest Card holder with a Silver room is eligible for an upgrade to Gold Luxury (YES), while a non-Preferred Guest Card holder, regardless of room type, is not eligible for any upgrade (NO). Therefore, Customer A (a Preferred Guest Card holder with a Silver room) would be offered an upgrade to Gold Luxury, and Customer B (a non-Preferred Guest Card holder with a Platinum room) would not be offered any upgrade. References = The answer is derived directly from the decision table provided in the image; specific ISTQB Certified Tester Foundation Level (CTFL) v4.0 documents are not referenced.


質問 # 96
Which of the following statements is the BEST example of non-functional testing?

  • A. Tests based on the internal structure of a component or system
  • B. Tests related to "what" the system should do
  • C. Tests which capture the time it takes to save a file
  • D. Tests which calculate overtime pay for those employees entitled to such

正解:C

解説:
Non-functional testing refers to testing aspects that do not relate to specific behaviors or functions of the software but to attributes such as performance, usability, reliability, etc. Tests that capture the time it takes to save a file directly relate to the performance of the system, thus falling under non-functional testing.References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 1.2.5 "Functional and Non-functional Testing".


質問 # 97
Which of the following does MOT describe a reason why testing is necessary?

  • A. For avionics and pharmaceutical systems software testing is mandated by standards
  • B. The acquisition of test automation tools was based on the assumption that it will be used m all projects
  • C. The risks associated with delivering the system are far higher than the cost of testing
  • D. The customer decided that 100% branch coverage shall be achieved

正解:B

解説:
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 andimpact 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 References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 1, page 5-6.


質問 # 98
A company runs a pilot project for evaluation of a test automation tool. Which of the following is NOT a valid object of this pilot project?

  • A. Get familiar with the functionality and options of the tool
  • B. Decide upon standards for tool implementation
  • C. Train all testers on using the tool
  • D. Check haw the tool fits to the existing test processes

正解:C

解説:
A pilot project is a small-scale experiment or trial that is conducted to evaluate the feasibility, effectiveness, and suitability of a test automation tool before implementing it on a larger scale1.
The objectives of a pilot project may vary depending on the context and scope of the test automation initiative, but some common ones are2:
To get familiar with the functionality and options of the tool
To check how the tool fits to the existing test processes and environment To assess the benefits and challenges of using the tool To decide upon standards and guidelines for tool implementation and usage To estimate the costs and resources required for tool deployment and maintenance Therefore, option C is not a valid objective of a pilot project, as it is not necessary to train all testers on using the tool at this stage. Training all testers on using the tool would be more appropriate after the tool has been selected and approved for full-scale implementation, and after the standards and guidelines have been established. Training all testers on using the tool during the pilot project would be inefficient, costly, and premature, as the tool may not be suitable or effective for the intended purpose, or may be replaced by another tool later.
Reference:
1: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 82
2: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 83
3: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 84
4: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 85


質問 # 99
Which of the following statements contradicts the general principles of testing?

  • A. Most defects are found in a small subset of a system's modules.
  • B. How testing is done, is based on the situation in a particular project.
  • C. Testing is better if it starts at the beginning of a project.
  • D. If new defects are to be found we should run the same test set more often.

正解:D

解説:
Statement B contradicts the general principles of testing, because running the same test set more often will not increase the chances of finding new defects, unless there are some changes in the system or environment that affect the test results. Running different test sets with different inputs, outputs or conditions would be more effective in finding new defects. Statements A, C and D are consistent with the general principles of testing. Statement A states that most defects are found in a small subset of a system's modules, which is true according to the defect clustering principle. Statement C states that testing is better if it starts at the beginning of a project, which is true according to the early testing principle. Statement D states that how testing is done, is based on the situation in a particular project, which is true according to the context-dependent testing principle. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, pages 4-6.


質問 # 100
You are testing a room upgrade system for a hotel. The system accepts three differed types of room (increasing order of luxury): Platinum. Silver and Gold Luxury. ONLY a Preferred Guest Card holder s eligible for an upgrade.
Below you can find the decision table defining the upgrade eligibility:

What is the expected result for each of the following test cases?
Customer A: Preference Guest Card holder, holding a Silver room
Customer B: Non Preferred Guest Card holder, holding a Platinum room

  • A. Customer A; doesn't offer any upgrade; Customer B: offers upgrade to Gold luxury room
  • B. Customer A: offers upgrade to Gold Luxury room; Customer B: doesn't offer any upgrade
  • C. Customer A: offers upgrade to Silver room; Customer B: offers upgrade to Silver room.
  • D. Customer A: doesn't offer any upgrade; Customer B: doesn't offer any upgrade.

正解:B

解説:
According to the decision table in the image, a Preferred Guest Card holder with a Silver room is eligible for an upgrade to Gold Luxury (YES), while a non-Preferred Guest Card holder, regardless of room type, is not eligible for any upgrade (NO). Therefore, Customer A (a Preferred Guest Card holder with a Silver room) would be offered an upgrade to Gold Luxury, and Customer B (a non-Preferred Guest Card holder with a Platinum room) would not be offered any upgrade. Reference = The answer is derived directly from the decision table provided in the image; specific ISTQB Certified Tester Foundation Level (CTFL) v4.0 documents are not referenced.


質問 # 101
Which are the MAIN goals of risk management in a software project?

  • A. To increase the success probability for the project regardless of costs.
  • B. To increase focus on preventative processes and to increase satisfaction for the testers.
  • 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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 2, page
14-15.


質問 # 102
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.


質問 # 103
A test manager decided to skip static testing since he believes bugs can be found easily by doing dynamic testing. Was this decision right or wrong?

  • A. The decision was right. Most of the bugs are easier to identify during the dynamic testing.
  • B. The decision was wrong. Ensuring quality mandates that static testing is performed after performing the dynamic testing.
  • C. The decision was right. Static testing is usually redundant if a product is planned to go through a full-cycle of dynamic testing.
  • D. The decision was wrong. Static testing can find defects early in the development process, reducing the overall cost of testing and development

正解:D

解説:
Static testing is a form of testing that does not involve executing the software or system under test. It includes activities such as reviews, inspections, walkthroughs, and analysis of documents, code, and models. Static testing can find defects early in the development process, before they become more expensive and difficult to fix in later stages. Static testing can also improve the quality of the software or system by preventing defects from being introduced in the first place. Static testing can complement dynamic testing, which involves executing the software or system under test and checking the results against expected outcomes. Dynamic testing can find defects that static testing may miss, such as performance, usability, or integration issues. However, dynamic testing alone is not sufficient to ensure quality, as it may not cover all possible scenarios, inputs, or paths. Therefore, a test manager who decides to skip static testing is making a wrong decision, as he or she is ignoring the benefits of static testing and relying solely on dynamic testing, which may not be effective or efficient enough to find and prevent defects. Reference = ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.1.1, page 14; ISTQB Glossary of Testing Terms, Version 4.0, 2018, page 36; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 3, page 9.


質問 # 104
Which of the types of test tools noted below BEST describes tools that support reviews?

  • A. Tools to assess data quality
  • B. Tools to support usability testing
  • C. Tools to support specialized testing needs
  • D. Tools to support static testing

正解:D

解説:
Static testing refers to testing that doesn't involve executing code. It includes activities like reviews, inspections, and static analysis. Tools that support static testing help with activities such as analyzing source code, checking coding standards, and aiding in document reviews. These tools can automate or facilitate various aspects of static testing processes, such as highlighting potential issues in code or documents without executing the software.References:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 6.1.1.


質問 # 105
......

有効なISTQB-CTFLテスト解答とISTQB ISTQB-CTFL試験PDF:https://www.jpntest.com/shiken/ISTQB-CTFL-mondaishu

ISTQB ISTQB-CTFL認定リアル2024年最新の模擬試験:https://drive.google.com/open?id=165ck2eAuNe3vGZSy9zNIJ96Dx127l0nJ

弊社を連絡する

我々は12時間以内ですべてのお問い合わせを答えます。

オンラインサポート時間:( UTC+9 ) 9:00-24:00
月曜日から土曜日まで

サポート:現在連絡