合格させるISTQB ISTQB-CTFLテスト問題でテストエンジンとPDFを提供中
あなたをお手軽にISTQB-CTFL試験合格させるリアルISTQB-CTFL練習問題集で更新されたのは2024年12月14日
質問 # 100
A calculator software is used to calculate the result for 5+6.
The user noticed that the result given is 6.
This is an example of;
- A. Fault
- B. Error
- C. Failure
- D. Mistake
正解：C
解説：
According to the ISTQB Glossary of Testing Terms, Version 4.0, 2018, page 18, a failure is "an event in which a component or system does not perform a required function within specified limits". In this case, the calculator software does not perform the required function of calculating the correct result for 5+6 within the specified limits of accuracy and precision. Therefore, this is an example of a failure.
The other options are incorrect because:
* A mistake is "a human action that produces an incorrect result" (page 25). A mistake is not an event, but an action, and it may or may not lead to a failure. For example, a mistake could be a typo in the code, a wrong assumption in the design, or a misunderstanding of the requirement.
* A fault is "a defect in a component or system that can cause the component or system to fail to perform its required function" (page 16). A fault is not an event, but a defect, and it may or may not cause a failure. For example, a fault could be a logical error in the code, a missing specification in the design, or a contradiction in the requirement.
* An error is "the difference between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition" (page 15). An error is not an event, but a
* difference, and it may or may not result in a failure. For example, an error could be a rounding error in the calculation, a measurement error in the observation, or a deviation error in the condition.
References = ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 15-18, 25; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 96, page 34.
質問 # 101
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 which calculate overtime pay for those employees entitled to such
- C. Tests related to "what" the system should do
- D. Tests which capture the time it takes to save a file
正解：D
解説：
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".
質問 # 102
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. There is no link to the applicable requirement (traceability)
- C. The Priority, the Correction description and the Developer name are missing
- 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 Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 140.
質問 # 103
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. I. II. IV
- B. III.V
- C. II, III
- 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.
質問 # 104
Which TWO of the following are benefits of continuous integration?
I. Allows earlier detection and easier root cause analysis of integration problems and conflicting changes.
II. Removes the need for manual test analysis, design and execution.
Hi. Removes the dependency on automated regression packs when integrating larger systems, or components.
iv. Gives the development team regular feedback on whether the code is working.
Select the correct answer:
- A. i and iii
- B. iii and iv
- C. i and iv
- D. i and ii
正解：C
解説：
The benefits of continuous integration include: i. Allows earlier detection and easier root cause analysis of integration problems and conflicting changes. iv. Gives the development team regular feedback on whether the code is working. These benefits help in maintaining the stability and quality of the codebase by integrating and testing changes frequently and providing quick feedback to developers.
質問 # 105
Which statement is true regarding confirmation testing and regression testing?
- A. Confirmation testing confirms the quality of the test being run while regression testing ensures that the software still works after a change has been made.
- B. Testers' involvement is essential whilst running retesting and regression testing.
- C. Confirmation testing aims to verify that a defect has been resolved and regression testing ensuring that existing functionality still works after a change.
- D. TESTER Involvement is essential whilst running retesting and regression testing.
- E. Confirmation testing is an optional activity whilst regression testing is not negotiable.
正解：C
解説：
Confirmation testing, also known as retesting, is conducted to verify that specific defects have been fixed.
Regression testing, on the other hand, is performed to ensure that recent changes have not adversely affected existing features of the software. Both types of testing are crucial for maintaining the integrity and quality of the software after modifications.
質問 # 106
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. IV, V
- C. II, III, IV
- D. II, IV
正解：D
解説：
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.
Reference:
1: ISTQB Glossary of Testing Terms 4.0, 2023, available at ISTQB) and ASTQB).
質問 # 107
Which of the following is true about Oracles?
- A. Oracles are derived from the design
- B. Oracles can be generated automatically using data generators
- C. Sometimes old version of a product can be used as an Oracle
- D. Oracles help in reproducing the irreproducible bugs
正解：C
解説：
An oracle is a mechanism or source that can provide the expected result for a given test input or situation. Sometimes old version of a product can be used as an oracle, if it is assumed that the old version behaves correctly for the test cases that are executed on the new version. This is also known as back-to-back testing. Oracles do not help in reproducing the irreproducible bugs, as they only provide the expected results, not the actual results. Oracles are not derived from the design, but from the requirements or specifications. Oracles cannot be generated automatically using data generators, as data generators only provide test inputs, not test outputs. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 9.
質問 # 108
Given the following requirement:
Requirement ID: 2 8
Requirement Description Additional Entrance Fee
Detailed Description
An additional fee of S3 is charged during the weekend, but
1) Visitors aged under 7 are not charged.
2) Visitors aged 7 to 13 inclusive get a 20% discount off the additional fee.
3) Visitors aged greater than 65 get a 50% discount off the additional fee.
Age should be an integer of 0 or above.
Weekend means Friday to Sunday inclusive.
Which of the following statements isNOTcorrect?
- A. $3.01 is a valid output boundary value.
- B. 7 and 13 are boundary values for the equivalence partition including age 10.
- C. A minimum of 6 valid test cases are derived from boundary value analysis based on input age.
- D. Thursday is a valid input boundary value.
正解：D
解説：
Boundary value analysis is a technique that tests boundary values between partitions of equivalent data.
Boundary values are values at the edge of an equivalence partition or at the smallest incremental distance on either side of an edge. Boundary value analysis can be applied to both input and output values. Based on the given requirement, we can identify two input values: age and weekend. Age should be an integer of 0 or above, and weekend means Friday to Sunday inclusive. The following statement is not correct:
* A) Thursday is a valid input boundary value. This statement is not correct, as Thursday is not a boundary value for the input weekend. The boundary values for the input weekend are Friday and Sunday, as they are at the edge of the equivalence partition that represents weekend days. The following statements are correct:
* B) A minimum of 6 valid test cases are derived from boundary value analysis based on input age. This statement is correct, as we can derive six valid test cases based on input age by using the minimum and maximum values for each equivalence partition defined by the requirement. The equivalence partitions for input age are: under 7 (0 to 6), 7 to 13 inclusive (7 to 13), and greater than 65 (66 and above). The minimum and maximum values for each partition are: 0 and 6, 7 and 13, and 66 and any value above it.
* C) $3.01 is a valid output boundary value. This statement is correct, as $3.01 is a boundary value for the output additional fee. The additional fee can have four possible values depending on the input age: $0 (for visitors aged under 7), $2.40 (for visitors aged 7 to 13 inclusive with a 20% discount), $1.50 (for visitors aged greater than 65 with a 50% discount), and $3 (for visitors aged between 14 and 65). The boundary values for the output additional fee are $0 and $3, as they are at the edge of an equivalence partition or at the smallest incremental distance on either side of an edge. Therefore, $3.01 is a valid output boundary value, as it is at the smallest incremental distance above $3.
* D) 7 and 13 are boundary values for the equivalence partition including age 10. This statement is correct, as 7 and 13 are boundary values for the equivalence partition that represents visitors aged 7 to
13 inclusive. This partition includes age 10, which is an internal value within the partition. Verified References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 4, page 37-38.
質問 # 109
Which of the following issues cannot be identified by static analysis tools?
- A. Very low MTBF (Mean Time Between failure)
- B. Potentially endless loops
- C. Referencing a variable with an undefined value
- D. Security vulnerabilities
正解：A
解説：
Static analysis tools are software tools that examine the source code of a program without executing it. They can detect various types of issues, such as syntax errors, coding standards violations, security vulnerabilities, and potential bugs12. However, static analysis tools cannot identify issues that depend on the runtime behavior or performance of the program, such as very low MTBF (Mean Time Between failure)3. MTBF is a measure of the reliability of a system or component. It is calculated by dividing the total operating time by the number of failures. MTBF reflects how often a system or component fails during its expected lifetime. Static analysis tools cannot measure MTBF because they do not run the program or observe its failures. MTBF can only be estimated by dynamic testing, which involves executing the program under various conditions and collecting data on its failures4. Therefore, very low MTBF is anissue that cannot be identified by static analysis tools.
The other options, such as potentially endless loops, referencing a variable with an undefined value, and security vulnerabilities, are issues that can be identified by static analysis tools. Static analysis tools can detect potentially endless loops by analyzing the control flow and data flow of the program and checking for conditions that may never become false5. Static analysis tools can detect referencing a variable with an undefined value by checking the scope and initialization of variables and reporting any use of uninitialized variables6. Static analysis tools can detect security vulnerabilities by checking for common patterns of insecure code, such as buffer overflows, SQL injections, cross-site scripting, and weak encryption. References = What Is Static Analysis? Static Code Analysis Tools - Perforce Software, How Static Code Analysis Works | Perforce, Static Code Analysis: Techniques, Top 5 Benefits & 3 Challenges, What is MTBF? Mean Time Between Failures Explained | Perforce, Static analysis tools - Software Testing MCQs - CareerRide, ISTQB_Chapter3 | Quizizz, [Static Code Analysis for Security Vulnerabilities | Perforce].
質問 # 110
4 equivalence classes are given for integer values:
0 < x <100
100<= x <= 200
200 < x < 500
x >= 500
Which of the following options represent correct set of data for valid equivalence class partitions?
- A. 50; 100; 250; 1000
- B. 50; 100; 200. 1000
- C. 0. 1.99, 100.200,201.499, 500;
- D. 0.50; 100; 150.200.350.500;
正解：D
解説：
The correct set of data for valid equivalence class partitions should include one value from each equivalence class, and no value from outside the range. Option C satisfies this condition, as it has one value from each of the four equivalence classes (50, 100, 250, 500). Option A has two values from the same equivalence class (100 and 200), option B has values outside the range (0 and 0.99), and option D has two values from the same equivalence class (1000 and 500). Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 35.
質問 # 111
Which of the following options cover the test types performed during typical system testing phase:
I Usability
II Requirements based scenarios
III Testing parts of the code in isolation
IV Correct order of parameters in API calls
- A. I, Ill
- B. II. IV
- C. III. IV
- 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 Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 2, page 20-21; Chapter 4, page 34-35.
質問 # 112
Which of the following coverage criteria results in the highest coverage for state transition based test cases?
- A. Covering all states at least once
- B. Covering only start and end states
- C. Can't be determined
- D. Covering all transitions at least once
正解：D
解説：
Covering all transitions at least once is the highest coverage criterion for state transition based test cases, because it ensures that every possible change of state is tested at least once. This means that all the events that trigger the transitions, as well as the actions and outputs that result from the transitions, are verified. Covering all transitions at least once also implies covering all states at least once, but not vice versa. Therefore, option D is not the highest coverage criterion. Option C is the lowest coverage criterion, because it only tests the initial and final states of the system or component, without checking the intermediate states or transitions. Option A is incorrect, because the coverage criteria for state transition based test cases can be determined and compared based on the number of transitions and states covered. Reference = CTFL 4.0 Syllabus, Section 4.2.3, page 49-50.
質問 # 113
Which of the following is NOT a common objective of testing?
- A. Debugging the software to find the reason for defects
- B. Finding defects in the software
- C. Providing information on the status of the system
- D. Preventing defects
正解：A
解説：
Debugging the software to find the reason for defects is not a common objective of testing, but rather a task of development or maintenance. Debugging is a process of locating and fixing errors in the software code, while testing is a process of finding and reporting defects in the software behavior or quality. Testing does not aim to fix defects, but rather to provide information on their existence and impact. The other options are common objectives of testing. Finding defects in the software is one of the main objectives of testing, as it helps to improve the quality and reliability of the software. Preventing defects is another objective of testing, as it helps to avoid rework and reduce costs and risks. Providing information on the status of the system is another objective of testing, as it helps to support decision making and risk management. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 3.
質問 # 114
An alphanumeric password must be between 4 and 7 characters long and must contain at least one numeric character, one capital (uppercase) letter and one lowercase letter of the alphabet.
Which one of the following sets of test cases represents the correct outcome of a two-value boundary value analysis applied to the password length? (Note: test cases are separated by a semicolon)
- A. 1xA;aB11;Pq1ZZab;7iDD0a1x
- B. aB11;99rSp:5NnN10;7iDD0a1x
- C. 1xB: aB11: 99rSp: 5NnN10; 4NnN10T; 44ghWn19
- D. 1RhT;rSp53;3N3e10;8sBdby
正解：D
解説：
The correct outcome of a two-value boundary value analysis applied to the password length is the set of test cases represented by option D. Boundary value analysis is a test design technique that focuses on the values at the boundaries of an equivalence partition, such as the minimum and maximum values, or the values just above and below the boundaries. A two-value boundary value analysis uses two values for each boundary, one representing the valid value and one representing the invalid value. For example, if the valid range of values is from 4 to 7, then the two values for the lower boundary are 3 and 4, and the two values for the upper boundary are 7 and 8. The test cases in option D use these values for the password length, while also satisfying the other requirements of the password, such as containing at least one numeric character, one capital letter, and one lowercase letter. The test cases in option D are:
* 1RhT: a 4-character password that is valid
* rSp53: a 5-character password that is valid
* 3N3e10: a 6-character password that is valid
* 8sBdby: an 8-character password that is invalid The test cases in the other options are incorrect, because they either use values that are not at the boundaries of the password length, or they do not meet the other requirements of the password. For example, the test cases in option A are:
* 1xA: a 3-character password that is invalid, but it does not contain a capital letter
* aB11: a 4-character password that is valid
* Pq1ZZab: a 7-character password that is valid
* 7iDD0a1x: an 8-character password that is invalid References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.1, Black-box Test Design Techniques1
* ISTQB Glossary of Testing Terms v4.0, Boundary Value Analysis, Equivalence Partition2
質問 # 115
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: offers upgrade to Gold Luxury room; Customer B: doesn't offer any upgrade
- B. Customer A: offers upgrade to Silver room; Customer B: offers upgrade to Silver room.
- C. Customer A; doesn't offer any upgrade; Customer B: offers upgrade to Gold luxury room
- D. Customer A: doesn't offer any upgrade; Customer B: doesn't offer any upgrade.
正解：A
解説：
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.
質問 # 116
Which of the following is an example of black-box dynamic testing?
- A. Coverage analysis
- B. Code inspection
- C. Checking memory leaks for a program by executing it
- D. Functional Testing
正解：D
質問 # 117
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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 10.
質問 # 118
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 y = 3.
X = y=z; - B. int x = 1.
Int y = 2.
Int z = 3.
Z = x +y - C. int x = 1.
int y = 2.
int z = 3.
X = z-y - D. int y = 2
Int z = 3.
Y = z+y
正解：A
解説：
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.
質問 # 119
......
ISTQB-CTFLリアル無料試験問題と解答：https://www.jpntest.com/shiken/ISTQB-CTFL-mondaishu
2024年最新の実際に出る検証済みの無料ISTQB ISTQB-CTFL試験問題：https://drive.google.com/open?id=175GWNNpsvhR5xKQ7sm6YCq5m9m5CXwNm