ISTQB-CTFL-KR 문제 101
테스트 엔지니어가 테스트하는 동안 결함을 발견했습니다. 개발자가 결함을 수정한 후 테스트 엔지니어는 테스트의 전체 섹션을 다시 실행하기로 결정했습니다. 다음 중 어느 것이 맞습니까?
정답: C
The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix. This is also known as regression testing, which is a type of testing that verifies that previously tested software still performs correctly after a change. Regression testing helps to detect any side effects or unintended consequences of a fix or a modification. The other options are incorrect reasons for re-running the tests. The test engineer should not re-run the tests, as they have already been run, and results recorded, because this ignores the possibility of new defects caused by the fix. The test engineer should not re-run the tests, they should be part of the developer tests, because this assumes that developer tests are sufficient and reliable, which may not be true. The test engineer should not re-run the tests, because the defect shows that the test cases need to be updated, because this does not address the impact of the fix on other test cases or functionalities. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 41.
ISTQB-CTFL-KR 문제 102
어떤 유형의 테스트는 테스트에서 실행된 코드 줄을 추적하여 효과를 측정합니까?
정답: B
Structural testing is a type of testing that measures its effectiveness by tracking which lines of code were executed by the tests. Structural testing, also known as white-box testing or glass-box testing, is based on the internal structure, design, or implementation of the software. Structural testing aims to verify that the software meets the specified quality attributes, such as performance, security, reliability, or maintainability, by exercising the code paths, branches, statements, conditions, or data flows. Structural testing uses various coverage metrics, such as function coverage, line coverage, branch coverage, or statement coverage, to determine how much of the code has been tested and to identify any untested or unreachable parts of the code.
Structural testing can be applied at any level of testing, such as unit testing, integration testing, system testing, or acceptance testing, but it is more commonly used at lower levels, where the testers have access to the source code.
The other options are not correct because they are not types of testing that measure their effectiveness by tracking which lines of code were executed by the tests. Acceptance testing is a type of testing that verifies that the software meets the acceptance criteria and the user requirements. Acceptance testing is usually performed by the end-users or customers, who may not have access to the source code or the technical details of the software. Acceptance testing is more concerned with the functionality, usability, or suitability of the software, rather than its internal structure or implementation. Integration testing is a type of testing that verifies that the software components or subsystems work together as expected. Integration testing is usually performed by the developers or testers, who may use both structural and functional testing techniques to check the interfaces, interactions, or dependencies between the components or subsystems. Integration testing is more concerned with the integration logic, data flow, or communication of the software, rather than its individual lines of code. Exploratory testing is a type of testing that involves simultaneous learning, test design, and test execution. Exploratory testing is usually performed by the testers, who use their creativity, intuition, or experience to explore the software and discover any defects, risks, or opportunities for improvement. Exploratory testing is more concerned with the behavior, quality, or value of the software, rather than its internal structure or implementation. References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54; Chapter 1: Fundamentals of Testing, Section 1.4: Testing Throughout the Software Development Lifecycle, Pages 11-13; Chapter 3: Static Testing, Section 3.4: Exploratory Testing, Pages 40-41.
Structural testing can be applied at any level of testing, such as unit testing, integration testing, system testing, or acceptance testing, but it is more commonly used at lower levels, where the testers have access to the source code.
The other options are not correct because they are not types of testing that measure their effectiveness by tracking which lines of code were executed by the tests. Acceptance testing is a type of testing that verifies that the software meets the acceptance criteria and the user requirements. Acceptance testing is usually performed by the end-users or customers, who may not have access to the source code or the technical details of the software. Acceptance testing is more concerned with the functionality, usability, or suitability of the software, rather than its internal structure or implementation. Integration testing is a type of testing that verifies that the software components or subsystems work together as expected. Integration testing is usually performed by the developers or testers, who may use both structural and functional testing techniques to check the interfaces, interactions, or dependencies between the components or subsystems. Integration testing is more concerned with the integration logic, data flow, or communication of the software, rather than its individual lines of code. Exploratory testing is a type of testing that involves simultaneous learning, test design, and test execution. Exploratory testing is usually performed by the testers, who use their creativity, intuition, or experience to explore the software and discover any defects, risks, or opportunities for improvement. Exploratory testing is more concerned with the behavior, quality, or value of the software, rather than its internal structure or implementation. References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54; Chapter 1: Fundamentals of Testing, Section 1.4: Testing Throughout the Software Development Lifecycle, Pages 11-13; Chapter 3: Static Testing, Section 3.4: Exploratory Testing, Pages 40-41.
ISTQB-CTFL-KR 문제 103
다음 중 일반적으로 테스트 진행 보고서에 포함되지 않는 요소는 무엇입니까?
정답: B
Comprehensive and Detailed In-Depth Explanation:
A test progress report provides an overview of testing activities, metrics, and identified risks. It focuses on tracking testing progress rather than evaluating overall product quality (B), which is typically included in a test summary report after testing is completed.
* (A) is correct because obstacles (challenges) are reported to ensure test execution stays on track.
* (C) is correct as test metrics help stakeholders track execution progress.
* (D) is correct because new or changed risks impact test focus and priorities.
A test progress report tracks execution and informs stakeholders about ongoing testing activities.
Reference: ISTQB CTFL v4.0 Syllabus, Section 5.3 - Test Monitoring and Control
A test progress report provides an overview of testing activities, metrics, and identified risks. It focuses on tracking testing progress rather than evaluating overall product quality (B), which is typically included in a test summary report after testing is completed.
* (A) is correct because obstacles (challenges) are reported to ensure test execution stays on track.
* (C) is correct as test metrics help stakeholders track execution progress.
* (D) is correct because new or changed risks impact test focus and priorities.
A test progress report tracks execution and informs stakeholders about ongoing testing activities.
Reference: ISTQB CTFL v4.0 Syllabus, Section 5.3 - Test Monitoring and Control
ISTQB-CTFL-KR 문제 104
다음 옵션 중 비기능 테스트의 주요 특징을 가장 잘 설명하는 것은 무엇입니까?
정답: A
Comprehensive and Detailed In-Depth Explanation:
Non-functional testing evaluates attributes like performance, security, and usability, which are typically assessed at the system test level or higher (A). It is not restricted to acceptance testing (B), goes beyond security and performance testing (C), and covers more than just user experience (D).
Reference: ISTQB CTFL v4.0 Syllabus, Section 2.2.2 - Non-functional Testing
Non-functional testing evaluates attributes like performance, security, and usability, which are typically assessed at the system test level or higher (A). It is not restricted to acceptance testing (B), goes beyond security and performance testing (C), and covers more than just user experience (D).
Reference: ISTQB CTFL v4.0 Syllabus, Section 2.2.2 - Non-functional Testing
ISTQB-CTFL-KR 문제 105
올바른 문장을 표시하세요:
* 결함은 환경 조건의 결과이며 "실패"라고도 합니다.
* 인간의 실수로 인해 결함이 발생할 수 있습니다.
* 시스템에 오류가 발생하면 시스템이 제대로 작동하지 않게 됩니다.
* 시스템에 결함이 존재하면 실패가 발생할 수 있습니다.
* 결함은 기술 변화로 인해 발생합니다.
* 결함은 환경 조건의 결과이며 "실패"라고도 합니다.
* 인간의 실수로 인해 결함이 발생할 수 있습니다.
* 시스템에 오류가 발생하면 시스템이 제대로 작동하지 않게 됩니다.
* 시스템에 결함이 존재하면 실패가 발생할 수 있습니다.
* 결함은 기술 변화로 인해 발생합니다.
정답: A
* 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.
:
1: ISTQB Glossary of Testing Terms 4.0, 2023, available at ISTQB) and ASTQB).
* 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.
:
1: ISTQB Glossary of Testing Terms 4.0, 2023, available at ISTQB) and ASTQB).
- 다른 버전
- 1373ISTQB.ISTQB-CTFL-KR.v2026-03-16.q188
- 1870ISTQB.ISTQB-CTFL-KR.v2026-01-17.q183
- 1306ISTQB.ISTQB-CTFL-KR.v2025-04-09.q132
- 1393ISTQB.ISTQB-CTFL-KR.v2025-03-01.q124
- 최근 업로드
- 171Cisco.500-420.v2026-09-09.q50
- 155WGU.Introduction-to-IT.v2026-09-09.q52
- 196GARP.2016-FRR.v2026-09-08.q268
- 137Oracle.1Z0-1051-26.v2026-09-08.q15
- 151DAMA.MD-1220.v2026-09-08.q48
- 143Saviynt.SCAIP.v2026-09-07.q20
- 357ISC.CCSP-KR.v2026-09-07.q424
- 147Oracle.1Z0-1032-26.v2026-09-07.q23
- 166Nursing.PMHN-BC.v2026-09-07.q38
- 279Cisco.300-430.v2026-09-07.q266
[×]
PDF 파일 다운로드
메일 주소를 입력하시고 다운로드 하세요. ISTQB.ISTQB-CTFL-KR.v2026-01-22.q147 모의시험 시험자료를 다운 받으세요.