ISTQB-CTFL-KR 문제 96
다음 중 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.
ISTQB-CTFL-KR 문제 97
다음 중 어느 진술이 사실입니까?
정답: B
Non-functional testing includes testing of both technical and non-technical quality characteristics.
Non-functional testing is the process of testing the quality attributes of a system, such as performance, usability, security, reliability, etc. Non-functional testing can be applied at any test level and can use both black-box and white-box test techniques. Non-functional testing can cover both technical aspects, such as response time, throughput, resource consumption, etc., and non-technical aspects, such as user satisfaction, accessibility, compliance, etc. Therefore, option B is the correct answer.
References: ISTQB Certified Tester Foundation Level Syllabus v4.01, Section 1.3.1, page 13; ISTQB Glossary v4.02, page 40.
Non-functional testing is the process of testing the quality attributes of a system, such as performance, usability, security, reliability, etc. Non-functional testing can be applied at any test level and can use both black-box and white-box test techniques. Non-functional testing can cover both technical aspects, such as response time, throughput, resource consumption, etc., and non-technical aspects, such as user satisfaction, accessibility, compliance, etc. Therefore, option B is the correct answer.
References: ISTQB Certified Tester Foundation Level Syllabus v4.01, Section 1.3.1, page 13; ISTQB Glossary v4.02, page 40.
ISTQB-CTFL-KR 문제 98
은행의 ATM(자동화 현금인출기) 시스템에서 거래에 대한 결정 테이블 테스트를 수행하고 있습니다. 규칙 1과 4에 대한 두 가지 테스트 사례가 이미 생성되었으며, 아래에 나와 있습니다.
첨부 1 참조
다음과 같은 추가 테스트 사례가 주어졌습니다.
첨부 2 참조
규칙 1과 4에 대해 이미 생성된 테스트 사례와 결합할 때, 추가 테스트 사례 중 어떤 두 가지가 전체 결정 테이블을 완벽하게 포괄할 수 있을까요?
첨부 1 참조
다음과 같은 추가 테스트 사례가 주어졌습니다.
첨부 2 참조
규칙 1과 4에 대해 이미 생성된 테스트 사례와 결합할 때, 추가 테스트 사례 중 어떤 두 가지가 전체 결정 테이블을 완벽하게 포괄할 수 있을까요?
정답: C
Decision table testing is used to analyze combinations of inputs to determine the appropriate outputs, often based on specific rules or conditions.
For the problem statement:
* Rule 1: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = True, Correct PIN = True)
* Outcome: Transaction = Approved
* Rule 4: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = True, Correct PIN = False)
* Outcome: Transaction = Declined
The additional test cases are:
* DT1: (Withdrawal = Allowed, Balance = Insufficient, Fast Cash = True, Correct PIN = True)
* Outcome: Transaction = Declined
* DT2: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = False, Correct PIN = True)
* Outcome: Transaction = Approved
* DT3: (Withdrawal = Allowed, Balance = Insufficient, Fast Cash = True, Correct PIN = False)
* Outcome: Transaction = Declined
* DT4: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = False, Correct PIN = False)
* Outcome: Transaction = Declined
From the given test cases, DT2 covers the scenario where Fast Cash is False, which is not covered in the initial cases. DT3 covers the case where Balance is Insufficient and PIN is incorrect.
Combining Rules 1 and 4 with DT2 and DT3 covers all the scenarios.
References:
* Certified Tester Foundation Level v4.0
* 10 Sample Exams ISTQB Foundation Level (CTFL) v4.0
For the problem statement:
* Rule 1: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = True, Correct PIN = True)
* Outcome: Transaction = Approved
* Rule 4: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = True, Correct PIN = False)
* Outcome: Transaction = Declined
The additional test cases are:
* DT1: (Withdrawal = Allowed, Balance = Insufficient, Fast Cash = True, Correct PIN = True)
* Outcome: Transaction = Declined
* DT2: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = False, Correct PIN = True)
* Outcome: Transaction = Approved
* DT3: (Withdrawal = Allowed, Balance = Insufficient, Fast Cash = True, Correct PIN = False)
* Outcome: Transaction = Declined
* DT4: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = False, Correct PIN = False)
* Outcome: Transaction = Declined
From the given test cases, DT2 covers the scenario where Fast Cash is False, which is not covered in the initial cases. DT3 covers the case where Balance is Insufficient and PIN is incorrect.
Combining Rules 1 and 4 with DT2 and DT3 covers all the scenarios.
References:
* Certified Tester Foundation Level v4.0
* 10 Sample Exams ISTQB Foundation Level (CTFL) v4.0
ISTQB-CTFL-KR 문제 99
영숫자 비밀번호는 4~7자 길이여야 하며, 숫자 1자 이상, 대문자 1자, 알파벳 소문자 1자를 각각 1자 이상 포함해야 합니다.
다음 테스트 사례 세트 중 어느 것이 비밀번호 길이에 적용된 2값 경계 값 분석의 올바른 결과를 나타냅니까? (참고: 테스트 사례는 세미콜론으로 구분)
다음 테스트 사례 세트 중 어느 것이 비밀번호 길이에 적용된 2값 경계 값 분석의 올바른 결과를 나타냅니까? (참고: 테스트 사례는 세미콜론으로 구분)
정답: 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
* 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
ISTQB-CTFL-KR 문제 100
다음 중 블랙박스 동적 테스트의 예는 무엇입니까?
정답: A
Functional testing is an example of black-box dynamic testing. Black-box testing (also known as specification-based testing) is a type of testing that does not consider the internal structure or implementation of the system under test, but rather its external behavior or functionality. Dynamic testing is a type of testing that involves executing the system under test with various inputs and observing its outputs. Functional testing is a type of black-box dynamic testing that verifies that the system under test performs its intended functions according to its requirements or specifications. Functional testing can be performed at various levels and scopes depending on the objectives and criteria of testing. The other options are not examples of black-box dynamic testing. Code inspection is an example of white-box static testing. White-box testing (also known as structure-based testing) is a type of testing that considers the internal structure or implementation of the system under test. Static testing is a type of testing that does not involve executing the system under test, but rather analyzing it for defects, errors, or violations of standards. Code inspection is a type of white-box static testing that involves examining the source code of the system under test for quality, readability, maintainability, etc.
Checking memory leaks for a program by executing it is an example of white-box dynamic testing. Memory leaks are defects that occur when a program fails to release memory that it has allocated but no longer needs.
Checking memory leaks for a program by executing it requires knowledge and access to the internal structure or implementation of the program, such as memory allocation and deallocation mechanisms, pointers, references, etc. Coverage analysis is an example of white-box static testing. Coverage analysis is a technique that measures how much of the code or structure of the system under test has been exercised by a test suite.
Coverage analysis requires knowledge and access to the internal structure or implementation of the system under test, such as statements, branches, paths, conditions, etc. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 7.
Checking memory leaks for a program by executing it is an example of white-box dynamic testing. Memory leaks are defects that occur when a program fails to release memory that it has allocated but no longer needs.
Checking memory leaks for a program by executing it requires knowledge and access to the internal structure or implementation of the program, such as memory allocation and deallocation mechanisms, pointers, references, etc. Coverage analysis is an example of white-box static testing. Coverage analysis is a technique that measures how much of the code or structure of the system under test has been exercised by a test suite.
Coverage analysis requires knowledge and access to the internal structure or implementation of the system under test, such as statements, branches, paths, conditions, etc. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 7.
- 다른 버전
- 1349ISTQB.ISTQB-CTFL-KR.v2026-03-16.q188
- 1779ISTQB.ISTQB-CTFL-KR.v2026-01-22.q147
- 1848ISTQB.ISTQB-CTFL-KR.v2026-01-17.q183
- 1289ISTQB.ISTQB-CTFL-KR.v2025-04-09.q132
- 최근 업로드
- 175Oracle.1Z1-171.v2026-09-06.q38
- 180SAP.C_S4TM.v2026-09-06.q71
- 178Oracle.1Z0-1054-26.v2026-09-06.q65
- 231Huawei.H12-831_V1.0.v2026-09-06.q231
- 152Salesforce.Plat-Arch-205.v2026-09-06.q28
- 179Salesforce.Plat-Arch-203.v2026-09-06.q90
- 145Oracle.1Z0-1050-26.v2026-09-05.q19
- 231Salesforce.Manufacturing-Cloud-Professional.v2026-09-05.q111
- 254EXIN.ITILFND_V4.v2026-09-05.q129
- 265Citrix.1Y0-312.v2026-09-05.q182
[×]
PDF 파일 다운로드
메일 주소를 입력하시고 다운로드 하세요. ISTQB.ISTQB-CTFL-KR.v2025-03-01.q124 모의시험 시험자료를 다운 받으세요.