매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
ISTQB Certified Tester Foundation Level (CTFL) 온라인 연습
최종 업데이트 시간: 2026년02월14일
당신은 온라인 연습 문제를 통해 ISTQB CTFL_SYLL_4.0 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 CTFL_SYLL_4.0 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 40개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Test-Driven Development (TDD) includes refactoring as a key practice. After writing tests and the code to satisfy those tests, refactoring is performed to improve the code and test quality without changing the functionality. This continuous process helps maintain clean, efficient, and manageable code.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 2.1.3, page 25: TDD, ATDD, and BDD Practices
정답:
Explanation:
Good testing practices that apply to all software development lifecycles include having specific test objectives for each test level that align with the phase of the software development lifecycle and the type of activities being addressed. This approach ensures that testing activities are relevant and appropriate for the specific stage of development, enhancing the effectiveness and efficiency of the testing process.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 2.1.2, page 24: Software Development Lifecycle and Good Testing Practices
정답:
Explanation:
One of the generic skills required for the role of a tester is the ability to use tools to make the execution of repetitive testing tasks more efficient. This includes using various test automation tools to streamline the testing process, reduce manual effort, and improve the consistency and accuracy of test results. Testers should be proficient in leveraging these tools to enhance productivity and ensure comprehensive test coverage.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 1.5.1, page 20: General Skills Required for Testing
정답:
Explanation:
Traceability is an essential aspect of software testing that ensures each test case can be traced back to its corresponding test basis items, such as requirements, design documents, or user stories. This linkage helps in determining which test basis items have been covered by executed test cases, identifying the impact of changes, and maintaining overall test documentation. However, the statement that traceability enables experience-based test techniques to be applied is false, as experience-based test techniques, such as exploratory testing, rely on the tester's skills and experience rather than documented traceability.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 1.4.4, page 19: Importance of Traceability
정답:
Explanation:
The document that describes the test procedures, including the order in which test cases are to be executed according to dependencies described by preconditions and postconditions, is typically produced during the test implementation phase. During this phase, detailed test procedures and scripts are developed, organized, and prioritized for execution. The main goal of test implementation is to ensure that all test cases are prepared and structured in a way that supports efficient and effective test execution.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 5.1.6, page 49: Test Implementation
정답:
Explanation:
Test planning is a critical phase in the software testing life cycle where the schedule for each testing activity and test milestones for a test project are determined. This involves using activity estimates, available resources, and other constraints to outline a comprehensive plan for the entire testing process. The main objective of test planning is to ensure that all testing activities are well-coordinated and that the testing process is efficient and effective. This phase sets the foundation for subsequent phases such as test analysis, test design, and test execution by providing a clear roadmap and allocation of resources.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 5.1, page 47: Test Planning
정답:
Explanation:
The absence-of-errors fallacy is one of the seven testing principles mentioned in the ISTQB syllabus. This principle states that even if no defects are found in the software, it does not guarantee that the software is usable and meets the user needs and expectations. By involving users early in the development process through practices like prototyping, the team can gather feedback to ensure that the software aligns with user expectations, thereby addressing the risk of this fallacy.
정답:
Explanation:
In the ISTQB terminology:
A defect (also known as a bug or fault) is an issue in the code that can cause a failure.
A failure is the observable incorrect behavior or output of the software due to a defect.
In this scenario, the memory leak is the defect in the application code that causes the application not to release dynamically allocated memory properly. The observable effect of this defect, which is the slowdown in response time, is considered a failure because it is the manifestation of the defect that prevents the application from meeting its performance requirements.
정답:
Explanation:
The "whole team approach" in Agile methodologies emphasizes collaboration and communication
among all team members, including developers, testers, and business representatives. This approach fosters better relationships and effective collaboration, which ultimately benefits the project by leveraging diverse skills and perspectives. It helps ensure that everyone is aligned with the project's goals and quality standards, thus improving the overall effectiveness and efficiency of the team.
정답:
Explanation:
In the ISTQB CTFL Syllabus, it is stated that a key objective of testing is to verify that the test object meets regulatory requirements. This is crucial as compliance with regulatory standards ensures that the software adheres to necessary laws, guidelines, and safety standards which are often mandatory in various industries such as healthcare, finance, and aviation. Ensuring regulatory compliance helps prevent legal issues and promotes user safety and trust.
정답:
Explanation:
Cost can be regarded as an exit criterion for testing, because it is a factor that affects the profitability and feasibility of the software product. Testing is an investment that aims to improve the quality and reliability of the software product, but it also consumes resources, such as time, money, and human effort. Therefore, testing should be planned and executed in a way that balances the cost and benefit of testing activities. Having cost as an exit criterion helps to avoid spending too much money on testing, which may result in an unprofitable product or a loss of competitive advantage. Cost can also help to prioritize and focus the testing efforts on the most critical and valuable features and functions of the software product. However, cost should not be the only exit criterion for testing, as it may not reflect the true quality and risk level of the software product. Other exit criteria, such as defect rate, test coverage, user satisfaction, etc., should also be considered and defined in the test plan.
The other options are incorrect, because they either deny the importance of cost as an exit criterion, or they make false or unrealistic assumptions about the cost of testing.
Option B is incorrect, because the financial value of product quality can be estimated, for example, by using cost-benefit analysis, return on investment, or cost of quality models.
Option C is incorrect, because going by cost as an exit criterion does not necessarily constrain the testing project or help achieve the desired quality level. Cost is a relative and variable factor that depends on the scope, complexity, and context of the software product and the testing project.
Option D is incorrect, because the cost of testing can be measured effectively, for example, by using metrics, such as test effort, test resources, test tools, test environment, etc.
정답:
Explanation:
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).
정답:
Explanation:
Statement coverage is a structural coverage metric that measures the percentage of executable statements in the source code that are executed by a test suite1. Decision coverage is another structural coverage metric that measures the percentage of decision outcomes (such as branches or conditions) in the source code that are executed by a test suite1. Decision coverage is a stronger metric than statement coverage, because it requires that every possible outcome of each decision is tested, while statement coverage only requires that every statement is executed at least once2. Therefore, if a test suite achieves 100% decision coverage, it also implies that it achieves 100% statement coverage, because every statement in every branch or condition must have been
executed. However, the converse is not true: 100% statement coverage does not guarantee 100% decision coverage, because some branches or conditions may have multiple outcomes that are not tested by the test suite2.
For example, consider the following pseudocode:
if (x > 0) then print(“Positive”) else print(“Non-positive”) end if
A test suite that executes this code with x = 1 and x = -1 will achieve 100% statement coverage, because both print statements are executed. However, it will not achieve 100% decision coverage, because the condition x > 0 has only been tested with two outcomes: true and false. The third possible outcome, x = 0, has not been tested by the test suite. Therefore, the test suite may miss a potential bug or error in the condition or the branch.
The other options, such as stale transition coverage, equivalence class coverage, and boundary value coverage, are not guaranteed to be 100% by achieving 100% decision coverage. Stale transition coverage is a structural coverage metric that measures the percentage of transitions between states in a state machine that are executed by a test suite3. Equivalence class coverage is a functional coverage metric that measures the percentage of equivalence classes (or partitions) of input or output values that are tested by a test suite4. Boundary value coverage is another functional coverage metric that measures the percentage of boundary values (or extreme values) of input or output ranges that are tested by a test suite4. These metrics are independent of decision coverage, because they are based on different aspects of the system under test, such as its behavior, functionality, or specification. Therefore, achieving 100% decision coverage does not imply achieving 100% of any of these metrics, and vice versa. Reference = ISTQB® Certified Tester Foundation Level Syllabus v4.0, Test Coverage in Software Testing - Guru99, Structural Coverage Metrics - MATLAB & Simulink - MathWorks India, Test Design Coverage in Software Testing - GeeksforGeeks.
정답:
Explanation:
The V-model is a software development life cycle model that defines four test levels that correspond to four development phases: component (unit) testing with component design, integration testing with architectural design, system testing with system requirements, and acceptance testing with user requirements. The V-model emphasizes the importance of verifying and validating each phase of development with a corresponding level of testing, and ensuring that the test objectives, test basis, and test artifacts are aligned and consistent across the test levels. Therefore, an organization that wants to follow the V-model cannot do away with integration testing, as it would break the symmetry and completeness of the V-model, and compromise the quality and reliability of the software or system under test. Integration testing is a test level that aims to test the interactions and interfaces between components or subsystems, and to detect any defects or inconsistencies that may arise from the integration of different parts of the software or system. Integration testing is essential for ensuring the functionality, performance, and compatibility of the software or system as a whole, and for identifying and resolving any integration issues early in the development process. Skipping integration testing would increase the risk of finding serious defects later in the test process, or worse, in the production environment, which would be more costly and difficult to fix, and could damage the reputation and credibility of the organization. Therefore, the correct answer is D.
The other options are incorrect because:
A. It is not allowed as organizations can decide on the test levels to do depending on the context of the system under test. While it is true that the choice and scope of test levels may vary depending on the context of the system under test, such as the size, complexity, criticality, and risk level of the system, the organization cannot simply ignore or skip a test level that is defined and required by the chosen software development life cycle model. The organization must follow the principles and guidelines of the software development life cycle model, and ensure that the test levels are consistent and coherent with the development phases. If the organization wants to have more flexibility and adaptability in choosing the test levels, it should consider using a different software development life cycle model, such as an agile or iterative model, that allows for more dynamic and incremental testing approaches.
B. It is not allowed because integration testing is not an important test level and can be dispensed with. This statement is false and misleading, as integration testing is a very important test level that cannot be dispensed with. Integration testing is vital for testing the interactions and interfaces between components or subsystems, and for ensuring the functionality, performance, and compatibility of the software or system as a whole. Integration testing can reveal defects or inconsistencies that may not be detected by component (unit) testing alone, such as interface errors, data flow errors, integration logic errors, or performance degradation. Integration testing can also help to verify and validate the architectural design and the integration strategy of the software or system, and to ensure that the software or system meets the specified and expected quality attributes, such as reliability, usability, security, and maintainability. Integration testing can also provide feedback and confidence to the developers and stakeholders about the progress and quality of the software or system development. Therefore, integration testing is a crucial and indispensable test level that should not be skipped or omitted.
C. It is not allowed because integration testing is a very important test level and ignoring it means
definite poor product quality. This statement is partially true, as integration testing is a very important test level that should not be ignored, and skipping it could result in poor product quality. However, this statement is too strong and absolute, as it implies that integration testing is the only factor that determines the product quality, and that ignoring it would guarantee a poor product quality. This is not necessarily the case, as there may be other factors that affect the product quality, such as the quality of the requirements, design, code, and other test levels, the effectiveness and efficiency of the test techniques and tools, the competence and experience of the developers and testers, the availability and adequacy of the resources and environment, the management and communication of the project, and the expectations and satisfaction of the customers and users. Therefore, while integration testing is a very important test level that should not be skipped, it is not the only test level that matters, and skipping it does not necessarily mean definite poor product quality, but rather a higher risk and likelihood of poor product quality.
Reference = ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.3, pages 16-18; ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 38-39; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 104, page 36.
정답:
Explanation:
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.