CTFL_Syll2018トレーニング最新認定問題をゲットISQI CTFL2018合格目指せ2024年08月28日
認定トレーニングCTFL_Syll2018試験問題集テストエンジン
質問 # 212
A company purchased a new system which deals with all financial transactions in the company Which test
types call for involvement of an expert from the financial department?
- A. System tests
- B. Maintenance testing
- C. Component testing
- D. Acceptance tests
正解：A
質問 # 213
Which of the following is a role of a formal review? [K1]
- A. Moderator
- B. Corrector
- C. Adjudicator
- D. Governor
正解：A
解説：
A role of a formal review is B. Moderator. A formal review is a type of static technique that involves a structured process of examining code or other software artifacts by a team of reviewers who follow predefined roles and rules. A formal review has four main phases: planning, preparation, meeting, and follow-up. A formal review has five main roles: author (the person who created the code or other software artifact under review), moderator (the person who leads and facilitates the review process), reviewer (the person who examines the code or other software artifact under review and provides feedback), scribe (the person who records the issues and outcomes of the review meeting), and manager (the person who monitors and controls the review process). A moderator is a key role in a formal review because he or she is responsible for planning, organizing, conducting, and reporting the review activities and ensuring that the review objectives are met. A detailed explanation of formal reviews can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 35-37.
質問 # 214
Which of the following would be LEAST appropriate as part of an incident report covering the observation of a failure during testing?
- A. The expected result for the list friends response time was less than 10 seconds, whereas the average response time obtained was 13 seconds.
- B. SQL injection into the username entry field allowed a variety of SQL commands to be executed by the application without the appropriate authority
- C. The updates made as part of the add new member' function did not reflect the expected change as the name was written into the address field.
- D. The user interface was complicated and confusing and I found it quite difficult to follow the test script.
正解：D
解説：
The user interface being complicated and confusing is not an appropriate part of an incident report covering the observation of a failure during testing, as it is a subjective opinion and not a factual description of the failure. An incident report should include objective and relevant information that can help to identify, reproduce, and resolve the failure3 defines an incident report as follows:
An incident report is a document that records the occurrence of an abnormal or unexpected event during testing, such as a deviation from expected results, a defect in the system under test, or a problem in the test environment. An incident report typically includes the following information:
* Identifier: A unique identifier for the incident report.
* Summary: A brief description of the incident.
* Incident details: A detailed description of the incident, including the inputs, expected results, actual results, environment, date and time, severity, priority, and any other relevant information.
* Steps to reproduce: A sequence of steps that can be followed to reproduce the incident.
* Attachments: Any screenshots, logs, files, or other artifacts that can help to understand or reproduce the incident.
質問 # 215
When a test case is created based on a Use Case, what type of test is created?
- A. Functional Test
- B. Structural Test
- C. Performance test
- D. Regression Test
正解：A
解説：
Functional test is the type of test that is created when a test case is based on a use case. A use case is a description of how a system interacts with one or more actors (users or other systems) to achieve a specific goal or function. A functional test is a test that verifies that a system or software component performs its specified functions according to its requirements. Functional tests can be derived from use cases by identifying test scenarios and test cases that cover the main flow and alternative flows of each use case2 explains this as follows:
Use cases are one of the most commonly used techniques for analyzing and modeling functional requirements for a system. A use case describes how an actor interacts with a system to accomplish a specific goal.
Functional Testing is a type of software testing whereby the system is tested against the functional requirements/specifications. Functions are tested by feeding them input and examining the output.
Use cases can be used as a source for deriving functional tests by identifying test scenarios and test cases that cover the main flow and alternative flows of each use case.
A, C, and D are incorrect answers. Structural test, performance test, and regression test are not types of tests that are created when a test case is based on a use case. Structural test is a type of test that is based on the internal structure and logic of the code rather than the functionality or requirements. Performance test is a type of test that measures the speed, responsiveness, scalability, or stability of a system under various workloads or conditions. Regression test is a type of test that verifies that previously working functionality still works after changes are made to the system or its environment.
質問 # 216
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 III. 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, III. V
- C. II,1V
- D. II, III. V
正解：D
解説：
II, III, and V are true statements about test reports. Test reports shall give stakeholders information as basis for decisions (II), as they provide an overview of the test results, the test coverage, the remaining risks, and the recommendations for the next steps. Test reports shall summarize what happened through a period of testing (III), as they describe the test activities, the test objectives, the test methods, the test environment, and the test incidents. Test reports shall include information about remaining risks (V), as they identify the areas of uncertainty or potential failure that may affect the quality or performance of the system under test1 defines a test report as follows:
A test report is a document that summarizes and communicates the outcomes of testing to stakeholders. A test report typically includes the following information:
* Test summary: A brief overview of the testing process, including the scope, objectives, approach, and results.
* Test evaluation: An evaluation of the testing process against the exit criteria and quality standards, including the test coverage, defect status, and risk assessment.
* Test conclusion: A conclusion on the suitability of the system under test for release or deployment, based on the test results and evaluation.
* Test recommendations: A recommendation on the actions to be taken after testing, such as fixing defects, conducting further testing, or implementing improvements.
I and IV are false statements about test reports. Test reports shall not be approved by the test team (I), as they are usually approved by a higher authority or a designated stakeholder who has the responsibility and authority to make decisions based on the test report. Test reports shall not be approved by the development team, the test team and the customer (IV), as this may cause conflicts of interest or delays in decision making.
質問 # 217
Which of the following statements contradicts the general principles of testing?
- A. How testing is done, is based on the situation in a particular project.
- B. Most defects are found in a small subset of a system's modules
- 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
解説：
The general principles of testing state that testing can show the presence of defects, but not their absence.
Running the same test set more often will not increase the likelihood of finding new defects, unless the system or its environment changes. Therefore, statement A contradicts the general principles of testing. Statement B is true, as testing is context-dependent and should be tailored to the specific situation of a project. Statement C is also true, as early testing can help prevent defects and reduce rework. Statement D is true, as it reflects the Pareto principle or the 80/20 rule, which states that most defects are found in a small subset of a system's modules.
References: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 1.2
質問 # 218
What is static analysis?
- A. It is a testing technique used during system testing.
- B. Executing software to validate the most common path through the code.
- C. A technique to find defects in software source code and software models, performed without executing code.
- D. The decision between using white or black box test techniques.
正解：C
質問 # 219
Which of the following is an appropriate reason for maintenance testing?
- A. Bugs found during system testing
- B. Bugs found during integration testing
- C. Bugs found in the field after upgrading the operation system
- D. Bugs found during unit testing
正解：C
質問 # 220
Test objectives for systems testing of a safety critical system include completion of all outstanding defect correction. Regression testing is required following defect correction at all test levels. Which TWO of the following metrics would be MOST suitable for determining whether the test objective has been met? [K2] a. Regression tests run and passed in systems testing b. Incidents closed in systems testing c. Planned tests run and passed in system testing d. Planned tests run and passed at all levels of testing e. Incidents raised and closed at all levels of testing
- A. b and c
- B. a and b
- C. d and e
- D. a and e
正解：D
質問 # 221
Why is measurement of code coverage Important?
- A. Because code coverage can ensure that all decisions are correctly implemented in the code
- B. Because 100% code coverage guarantees that there are no coding errors
- C. Because 100% code coverage implies 100% coverage of requirements
- D. Because code coverage can be used to ensure that all code is exercised by tests
正解：D
解説：
Explanation
Code coverage can be used to ensure that all code is exercised by tests, because it measures how much of the code or functionality of the software under test has been exercised by the test cases . Code coverage can help to identify untested or dead code, improve test design, and assess test quality . The other options are not true statements about code coverage. Option A is false, because 100% code coverage does not imply 100% coverage of requirements, as there may be defects or gaps in the requirements or in the mapping between requirements and code . Option B is false, because 100% code coverage does not guarantee that there are no coding errors, as there may be logical or functional errors that are not detected by code coverage . Option D is false, because code coverage does not ensure that all decisions are correctly implemented in the code, as it only measures whether the decisions are executed or not, but not whether they produce the correct results .
質問 # 222
Testing should provide sufficient information to stakeholders to make informed decisions about the release of the software or system being tested. At which of the following fundamental test process activity the sufficiency of the testing and the resulting information are assessed?
- A. Evaluating exit criteria and reporting.
- B. Analysis and design
- C. Implementation and execution
- D. Requirements specification
正解：A
解説：
Explanation
The fundamental test process activity where the sufficiency of testing and resulting information are assessed is Evaluating exit criteria and reporting. This activity involves checking whether the test objectives have been met and whether there are any unresolved issues or risks that could affect the release or deployment decision.
This activity also involves preparing and communicating a test summary report that summarizes the test activities and results and provides recommendations and feedback for improvement. You can find more information about Evaluating exit criteria and reporting in [A Study Guide to the ISTQB Foundation Level
2018 Syllabus], Chapter 3, Section 3.5.
質問 # 223
Which of the following is a typical characteristic of the WALKTHROUGH review type?
- A. Metrics are gathered throughout.
- B. Entry and exit criteria are defined.
- C. The meeting is led by the author.
- D. Attendees must prepare before the meeting.
正解：C
解説：
A typical characteristic of the walkthrough review type is that the meeting is led by the author. A walkthrough is a type of informal review that involves a presentation of a work product by the author to peers and other stakeholders for feedback and comments. The author leads the meeting and explains the work product to the participants, who can ask questions and make suggestions for improvement. The author may also record any issues or action items during the meeting. A walkthrough does not require formal preparation or follow-up by the participants, nor does it have defined entry and exit criteria.
References: Certified Tester Foundation Level Syllabus, Section 3.2.2
質問 # 224
Refer to the exhibit
Given the following State Transition diagram, match the test cases below with the relevant set of state transitions.
(i)X-Z-V-W
(ii)W-Y-U-U
- A. (i) = S2 - S3 - S4 - S2 - S2 and (ii) = S4 - S2 - S4 - S4 - S4
- B. (i) = S1 - S2 - S3 - S4 - S4 and (ii) = S2 -S4 - S4 - S4 - S2
- C. (i) = S2 - S3 - S4 - S4 - S2 and (ii) = S2 -S3 - S4 -S4 - S4
- D. (i) = S1 - S2 - S3 - S4 - S2 and (ii) = S4 - S2 - S4 - S4 - S4
正解：D
解説：
State transition testing is a technique that uses state transition diagrams as a test basis to derive test cases2. A state transition diagram shows the states of a system and the transitions between them triggered by events or conditions2. A test case can cover one or more state transitions, depending on the test objective and coverage criterion2. In this question, the test cases (i) and (ii) cover different sets of state transitions, as shown below:
Test Case
State Transitions
(i) X-Z-V-W
S1 - S2 - S3 - S4 - S2
(ii) W-Y-U-U
S4 - S2 - S4 - S4 - S4
質問 # 225
Which of the following is NOT an example of a typical risk-based testing activity?
- A. The focus of testing is shifted to an area in the system where tests find with more defects than expected
- B. Tests are prioritized to ensure that those associated with critical parts of the system are executed earlier
- C. The evaluation of a risk-management tools to decide which tool to use for future projects
- D. Brainstorming sessions are held with a wide variety of stakeholders to identify possible failures in the system
正解：A
質問 # 226
Consider the following pseudo code
1. Begin
2. Read Gender
3. __Print "Dear"
4. If Gender = 'female'
5. Print ("Ms")
6. Else
7. __Print ( "Mr")
8. Endif
9. End
How many test cases are needed to achieve 100 per cent decision coverage?
- A. 0
- B. 1
- C. 2
- D. 3
正解：A
解説：
Decision coverage is a structure-based test technique that involves testing every decision point in the code by testing all possible outcomes or branches of each decision point. Decision coverage requires some knowledge of the internal structure or implementation of the software system; it focuses on how the system does what it does rather than what it does.
The pseudo code given in the question has one decision point at line 4, where the value of Gender is compared to 'female'. This decision point has two possible outcomes or branches:
* True branch: If Gender = 'female', then print "Ms" at line 5.
* False branch: If Gender != 'female', then print "Mr" at line 7.
To achieve 100 per cent decision coverage, we need to test both outcomes or branches of the decision point at least once. Therefore, we need two test cases that cover both scenarios:
* TC1: Gender = 'female' -> Print "Dear Ms"
* TC2: Gender = 'male' -> Print "Dear Mr"
The other options are not correct because they do not provide enough or too many test cases to achieve 100 per cent decision coverage. For example:
* A. 1: This option is not enough because it only provides one test case that covers one outcome or branch of the decision point, but not the other.
* C. 3: This option is too many because it provides three test cases that cover both outcomes or branches of the decision point, but one of them is redundant or unnecessary.
* D. 4: This option is too many because it provides four test cases that cover both outcomes or branches of the decision point, but two of them are redundant or unnecessary.
You can find more information about decision coverage and structure-based testing in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.3.
質問 # 227
Which defect below is MOST likely to be found by a review during static testing?
- A. Broken links to web addresses.
- B. Old versions of software in use.
- C. Performance bottlenecks.
- D. Incorrect interface specifications.
正解：D
解説：
Explanation
Incorrect interface specifications are most likely to be found by a review during static testing. A review is a type of static testing technique that involves a manual examination of a work product by one or more individuals who follow a defined process. A review can be applied to any work product, such as requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. A review can help find defects and improve the quality of any work product at any stage of the software development lifecycle.
Incorrect interface specifications are defects that affect the definition and communication of the interfaces between components or systems. These defects can be detected by reviewing the interface specifications document and comparing it with the requirements and design specifications.
References: Certified Tester Foundation Level Syllabus, Section 3.2.1
質問 # 228
A Software was re-deployed because the backend database was changed from one vendor to another.
The Test Manager decided to perform some functional tests on the redeployed system.
This is an example of test of which test type?
- A. Non-functional tests
- B. Unit tests
- C. Structural tests
- D. Regression tests
正解：D
解説：
Regression testing is a type of testing that is performed after a software system has been changed or modified to verify that the changes have not introduced any new defects or adversely affected the existing functionality of the system. Regression testing can be performed when the software system undergoes different types of changes, such as:
* Corrective changes: Changes that fix defects or errors in the software system
* Adaptive changes: Changes that adapt the software system to new platforms or environments
* Perfective changes: Changes that improve the performance or usability of the software system
* Preventive changes: Changes that avoid potential problems or issues in the software system In this case, the software system was re-deployed because the backend database was changed from one vendor to another, which is an example of an adaptive change. Therefore, the test manager decided to perform some functional tests on the re-deployed system to ensure that the change did not affect the functionality of the system. This is an example of regression testing.
The other types of testing mentioned in the question are not relevant for this scenario. For example:
* Non-functional testing: This type of testing verifies the non-functional aspects of the software system, such as reliability, performance, security, usability, etc.
* Structural testing: This type of testing verifies the internal structure or implementation of the software system, such as code, architecture, design, etc.
* Unit testing: This type of testing verifies individual components or units of software in isolation from other components or systems.
You can find more information about regression testing in [A Study Guide to the ISTQB Foundation Level
2018 Syllabus], Chapter 2, Section 2.4.
質問 # 229
Which of the following statements regarding incidents is NOT true?
- A. The discrepancies between actual and expected outcomes need to be logged as incidents
- B. Incidents may be raised during development, review, testing or use of a software product
- C. Incidents should be tracked from discovery and classification to correction and confirmation of the solution.
- D. Since incidents are the discrepancies between actual and expected outcomes they cannot be raised during development
正解：D
解説：
Explanation
The statement that incidents cannot be raised during development is not true, because incidents can be raised during any stage of software development life cycle where deviations from expected or desired behaviour are observed . Incidents can be raised during development, review, testing or use of a software product . The other options are true statements about incidents.
質問 # 230
A garden irrigation system allows the user to specify 2 inputs:
1. Frequency - The number of times the system should be automatically switched on per day; minimum once per day, maximum 5 times
2. Duration - The duration of operation, in whole minutes, each time it is switched on; ranging from 1 to 60 Applying 2-value boundary value analysis which of the following options has the correct test set of valid and invalid boundary values?
- A. Frequency 1, 5; Duration 1, 60
- B. Frequency 0, 1, 5, 6; Duration 0, 1, 30, 60, 61
- C. Frequency 0, 1, 2, 5, 6; Duration 0, 1, 30, 60, 61
- D. Frequency 0, 1, 5, 6; Duration 59 seconds, 1 minute, 60 minutes, 60 minutes 1 second
正解：B
解説：
Explanation
Frequency 0, 1, 5, 6; Duration 0, 1, 30, 60, 61 is the correct test set of valid and invalid boundary values applying 2-value boundary value analysis1 . Boundary value analysis is a technique that tests the values at and near the boundaries of an input domain or output range1 . A 2-value boundary value analysis tests two values for each boundary: one valid value and one invalid value1 . For Frequency, the valid boundaries are 1 and 5, so the test set should include one valid value (1 or 5) and one invalid value (0 or 6) for each boundary. For Duration, the valid boundaries are 1 and 60, so the test set should include one valid value (1 or 60) and one invalid value (0 or 61) for each boundary. The other options are incorrect test sets of valid and invalid boundary values applying 2-value boundary value analysis. Option A only includes valid values for each boundary, but not invalid values. Option B includes invalid values that are not adjacent to the boundaries (59 seconds and 60 minutes 1 second). Option D includes more than two values for each boundary (0, 1, 2 for Frequency; 0, 1, 30 for Duration).
質問 # 231
......
ISQI CTFL_Syll2018（ISTQB Certified Tester Foundation Level（Syllabus 2018））試験は、ソフトウェアテストのキャリアを追求する個人を対象とした認定試験です。この試験は、グローバルに認知され、ソフトウェアテスターにとって最も重要な認定資格の1つと考えられています。テスト設計、実行、および管理を含む、ソフトウェアテストに関連する幅広いトピックをカバーしています。
合格確定、ガイドで準備CTFL_Syll2018試験：https://jp.fast2test.com/CTFL_Syll2018-premium-file.html