ISTQB-CTFL-KR 문제 11
다음 중 테스트 상태 보고서에 포함되어야 하는 내용은 무엇입니까?
I. 추정 세부 정보
II. 열린 결함과 닫힌 결함의 총 수
III 실제 소요된 노력
IV. 결함 보고
V. 실행된 테스트, 실패한 테스트, 차단된 테스트의 수
I. 추정 세부 정보
II. 열린 결함과 닫힌 결함의 총 수
III 실제 소요된 노력
IV. 결함 보고
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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 141.
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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 141.
ISTQB-CTFL-KR 문제 12
테스트 자동화를 도입할 경우 발생할 수 있는 위험은 다음과 같습니다.
정답: A
One possible risk of introducing test automation is that the selected tool may not be fit-for-purpose. This means that the tool might not meet the specific needs and requirements of the project, leading to inefficiencies and possibly failing to provide the expected benefits. It is crucial to evaluate and select the appropriate tool based on the project's context and objectives. The ISTQB CTFL syllabus highlights the importance of careful tool evaluation and selection to ensure it aligns with the testing goals and the development environment.
References: ISTQB CTFL Syllabus, Section 6.2, "Potential Benefits and Risks of Test Automation."
References: ISTQB CTFL Syllabus, Section 6.2, "Potential Benefits and Risks of Test Automation."
ISTQB-CTFL-KR 문제 13
다음 테스트 문서 중 어느 문서에서 테스트 종료 기준이 설명되어 있을 것으로 예상합니까?
정답: D
Test exit criteria are the conditions that must be fulfilled before concluding a particular testing phase. These criteria act as a checkpoint to assess whether we have achieved the testing objectives and are done with testing1. Test exit criteria are typically defined in the test plan document, which is one of the outputs of the test planning phase. The test plan document describes the scope, approach, resources, and schedule of the testing activities. It also identifies the test items, the features to be tested, the testing tasks, the risks, and the test deliverables2. According to the ISTQB Certified Tester Foundation Level Syllabus v4.0, the test plan document should include the following information related to the test exit criteria3:
* The criteria for evaluating test completion, such as the percentage of test cases executed, the percentage of test coverage achieved, the number and severity of defects found and fixed, the quality and reliability of the software product, and the stakeholder satisfaction.
* The criteria for evaluating test process improvement, such as the adherence to the test strategy, the efficiency and effectiveness of the testing activities, the lessons learned and best practices identified, and the recommendations for future improvements.
Therefore, the test plan document is the most appropriate test document to find the test exit criteria described.
The other options, such as test design specification, project plan, and requirements specification, are not directly related to the test exit criteria. The test design specification describes the test cases and test procedures for a specific test level or test type3. The project plan describes the overall objectives, scope, assumptions, risks, and deliverables of the software project4. The requirements specification describes the functional and non-functional requirements of the software product5. None of these documents specify the conditions for ending the testing process or evaluating the testing outcomes. References = ISTQB Certified Tester Foundation Level Syllabus v4.0, Entry and Exit Criteria in Software Testing | Baeldung on Computer Science, Entry And Exit Criteria In Software Testing - Rishabh Software, Entry and Exit Criteria in Software Testing Life Cycle - STLC [2022 Updated] - Testsigma Blog, ISTQB releases Certified Tester Foundation Level v4.0 (CTFL).
* The criteria for evaluating test completion, such as the percentage of test cases executed, the percentage of test coverage achieved, the number and severity of defects found and fixed, the quality and reliability of the software product, and the stakeholder satisfaction.
* The criteria for evaluating test process improvement, such as the adherence to the test strategy, the efficiency and effectiveness of the testing activities, the lessons learned and best practices identified, and the recommendations for future improvements.
Therefore, the test plan document is the most appropriate test document to find the test exit criteria described.
The other options, such as test design specification, project plan, and requirements specification, are not directly related to the test exit criteria. The test design specification describes the test cases and test procedures for a specific test level or test type3. The project plan describes the overall objectives, scope, assumptions, risks, and deliverables of the software project4. The requirements specification describes the functional and non-functional requirements of the software product5. None of these documents specify the conditions for ending the testing process or evaluating the testing outcomes. References = ISTQB Certified Tester Foundation Level Syllabus v4.0, Entry and Exit Criteria in Software Testing | Baeldung on Computer Science, Entry And Exit Criteria In Software Testing - Rishabh Software, Entry and Exit Criteria in Software Testing Life Cycle - STLC [2022 Updated] - Testsigma Blog, ISTQB releases Certified Tester Foundation Level v4.0 (CTFL).
ISTQB-CTFL-KR 문제 14
다음 도구 유형 중에서 코딩 표준에서 제공하는 지침을 준수하는지 소스 코드를 확인하는 데 가장 적합한 도구는 무엇입니까?
정답: C
A static analysis tool is best suited for determining source code compliance with coding standards. These tools analyze the code without executing it and can check for adherence to coding standards, syntax errors, and other static properties of the code. The ISTQB CTFL syllabus emphasizes the role of static analysis tools in verifying that code meets predefined standards and guidelines.
References: ISTQB CTFL Syllabus, Section on static testing and tools.
References: ISTQB CTFL Syllabus, Section on static testing and tools.
ISTQB-CTFL-KR 문제 15
다음 중 MOT가 테스트가 필요한 이유를 설명하는 것은 무엇입니까?
정답: 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 and impact 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.
* 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 and impact 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.
- 다른 버전
- 1328ISTQB.ISTQB-CTFL-KR.v2026-03-16.q188
- 1845ISTQB.ISTQB-CTFL-KR.v2026-01-17.q183
- 1287ISTQB.ISTQB-CTFL-KR.v2025-04-09.q132
- 1371ISTQB.ISTQB-CTFL-KR.v2025-03-01.q124
- 최근 업로드
- 116Oracle.1Z1-171.v2026-09-06.q38
- 119SAP.C_S4TM.v2026-09-06.q71
- 119Oracle.1Z0-1054-26.v2026-09-06.q65
- 149Huawei.H12-831_V1.0.v2026-09-06.q231
- 114Salesforce.Plat-Arch-205.v2026-09-06.q28
- 107Salesforce.Plat-Arch-203.v2026-09-06.q90
- 134Oracle.1Z0-1050-26.v2026-09-05.q19
- 199Salesforce.Manufacturing-Cloud-Professional.v2026-09-05.q111
- 218EXIN.ITILFND_V4.v2026-09-05.q129
- 236Citrix.1Y0-312.v2026-09-05.q182
[×]
PDF 파일 다운로드
메일 주소를 입력하시고 다운로드 하세요. ISTQB.ISTQB-CTFL-KR.v2026-01-22.q147 모의시험 시험자료를 다운 받으세요.