Practice Free CTFL_SYLL_4.0 Exam Online Questions
Question #51
Which ONE of the following options corresponds to an activity in the testing process in which testable features are identified?
- A . Test design
- B . Test analysis
- C . Test implementation
- D . Test execution
Correct Answer: B
B
Explanation:
Test analysis involves identifying the features to be tested and deriving test conditions. It is the phase where testers analyze the test basis (e.g., requirements, specifications) to identify testable aspects of the system. Test design (A) focuses on creating test cases, test implementation (C) involves preparing
the test environment, and test execution (D) runs the tests.
Reference: ISTQB CTFL v4.0 Syllabus, Section 1.4.1 C Test Analysis
B
Explanation:
Test analysis involves identifying the features to be tested and deriving test conditions. It is the phase where testers analyze the test basis (e.g., requirements, specifications) to identify testable aspects of the system. Test design (A) focuses on creating test cases, test implementation (C) involves preparing
the test environment, and test execution (D) runs the tests.
Reference: ISTQB CTFL v4.0 Syllabus, Section 1.4.1 C Test Analysis
Question #52
A test manager has started a cycle of testing for an e-commerce application. The reason for testing is the change in the protocol for connecting to the payment gateway because of new regulations.
Which of the following correctly names this type of testing?
- A . Retirement testing
- B . System integration testing
- C . Beta testing
- D . Maintenance testing
Correct Answer: D
D
Explanation:
Maintenance testing is performed to ensure that the application continues to function correctly after changes have been made. These changes can include modifications due to new regulations, bug fixes, enhancements, or any other updates. In this case, the change in the protocol for connecting to the payment gateway due to new regulations falls under maintenance testing, as it involves testing the application to ensure it works correctly after the implementation of the required changes.
Top of Form
Bottom of Form
D
Explanation:
Maintenance testing is performed to ensure that the application continues to function correctly after changes have been made. These changes can include modifications due to new regulations, bug fixes, enhancements, or any other updates. In this case, the change in the protocol for connecting to the payment gateway due to new regulations falls under maintenance testing, as it involves testing the application to ensure it works correctly after the implementation of the required changes.
Top of Form
Bottom of Form
Question #53
Which of the following about typical information found within a test plan is false?
- A . The need to temporarily have additional test personnel available for specific test phases and/or test activities
- B . The conditions that must be met in order for the test execution activities to be considered completed
- C . The list of the product risks which have not been fully mitigated at the end of test execution
- D . The conditions that must be met for part of all the planned activities to be suspended and resumed
Correct Answer: C
C
Explanation:
A test plan is a document detailing the objectives, resources, schedule, and scope of testing activities. It also outlines the test strategy, environment, tools, and criteria for test completion and suspension.
Option A: Correct as it indicates resource planning which is a crucial part of a test plan.
Option B: Correct as it describes exit criteria which are essential for test completion.
Option C: Incorrect because a test plan typically addresses known risks and mitigation strategies but does not list unmitigated risks post-test execution.
Option D: Correct as it mentions suspension criteria which are also a part of a test plan.
Therefore, option C is false as it does not reflect the typical information found within a test plan.
C
Explanation:
A test plan is a document detailing the objectives, resources, schedule, and scope of testing activities. It also outlines the test strategy, environment, tools, and criteria for test completion and suspension.
Option A: Correct as it indicates resource planning which is a crucial part of a test plan.
Option B: Correct as it describes exit criteria which are essential for test completion.
Option C: Incorrect because a test plan typically addresses known risks and mitigation strategies but does not list unmitigated risks post-test execution.
Option D: Correct as it mentions suspension criteria which are also a part of a test plan.
Therefore, option C is false as it does not reflect the typical information found within a test plan.
Question #54
Which of the following statements about impact of DevOps on testing is CORRECT?
- A . DevOps helps bring focus on testing of non-functional characteristics
- B . DevOps helps shift focus of testing people to perform operations testing
- C . DevOps helps shift focus of operations people to functional testing
- D . DevOps helps eliminate manual testing by having focus on continuous automated testing
Correct Answer: A
A
Explanation:
DevOps practices emphasize the importance of testing non-functional characteristics such as performance, security, and reliability. This focus ensures that the system not only meets functional requirements but also performs well under various conditions and is secure. DevOps promotes a continuous testing approach, which includes both functional and non-functional testing integrated into the development and deployment pipelines.
Reference: ISTQB CTFL Syllabus V4.0, Section 2.1.4 on DevOps and testing, which highlights the role of DevOps in emphasizing non-functional characteristics.
A
Explanation:
DevOps practices emphasize the importance of testing non-functional characteristics such as performance, security, and reliability. This focus ensures that the system not only meets functional requirements but also performs well under various conditions and is secure. DevOps promotes a continuous testing approach, which includes both functional and non-functional testing integrated into the development and deployment pipelines.
Reference: ISTQB CTFL Syllabus V4.0, Section 2.1.4 on DevOps and testing, which highlights the role of DevOps in emphasizing non-functional characteristics.
Question #55
In which of the following test documents would you expect to find test exit criteria described9
- A . Test design specification
- B . Project plan
- C . Requirements specification
- D . Test plan
Correct Answer: D
D
Explanation:
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. Reference = ISTQB® Certified TesterFoundation Level Syllabus
v4.0, Entry and Exit Criteria in Software Testing | Baeldung onComputer 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).
D
Explanation:
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. Reference = ISTQB® Certified TesterFoundation Level Syllabus
v4.0, Entry and Exit Criteria in Software Testing | Baeldung onComputer 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).
Question #56
A program is used to control a manufacturing line (turn machines on and off. start and stop conveyer belts, add raw materials to the flow. etc.). Not all actions are possible at all times.
For example, there are certain manufacturing stages that cannot be stopped – unless there is an emergency. A tester attempts to evaluate if all such cases (where a specific action is not allowed) are covered by the tests.
Which coverage metric will provide the needed information for this analysis?
- A . Code coverage
- B . Data flow coverage
- C . Statement coverage
- D . Branch Coverage
Correct Answer: D
D
Explanation:
Branch coverage is a type of structural coverage metric that measures the percentage of branches or decision outcomes that are executed by the test cases. A branch is a point in the code where the control flow can take two or more alternative paths based on a condition.
For example, an if-else statement is a branch that can execute either the if-block or the else-block depending on the evaluation of the condition. Branch coverage ensures that each branch is taken at least once by the test cases, and thus reveals the behavior of the software under different scenarios. Branch coverage is also known as decision coverage or all-edges coverage.
Branch coverage is suitable for testing the cases where a specific action is not allowed, because it can verify that the test cases cover all the possible outcomes of the conditions that determine the action.
For example, if the program has a condition that checks if the manufacturing stage can be stopped, then branch coverage can ensure that the test cases cover both the cases where the stage can be stopped and where it cannot be stopped. This way, branch coverage can help identify any missing or incorrect branches that may lead to undesired or unsafe actions.
The other options are not correct because they are not suitable for testing the cases where a specific action is not allowed. Code coverage is a general term that encompasses various types of coverage metrics, such as statement coverage, branch coverage, data flow coverage, etc. Code coverage does not specify which type of coverage metric is used for the analysis. Data flow coverage is a type of structural coverage metric that measures the percentage of data flow paths that are executed by the test cases. A data flow path is a sequence of statements that define, use, or kill a variable. Data flow coverage is useful for testing the correctness and completeness of the data manipulation in the software, but not for testing the conditions that determine the actions. Statement coverage is a type of structural coverage metric that measures the percentage of statements or lines of code that are executed by the test cases. Statement coverage ensures that each statement is executed at least once by the test cases, but it does not reveal the behavior of the software under different scenarios. Statement coverage is a weaker criterion than branch coverage, because it does not account for the branches or decision outcomes in the code. Reference = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54.
D
Explanation:
Branch coverage is a type of structural coverage metric that measures the percentage of branches or decision outcomes that are executed by the test cases. A branch is a point in the code where the control flow can take two or more alternative paths based on a condition.
For example, an if-else statement is a branch that can execute either the if-block or the else-block depending on the evaluation of the condition. Branch coverage ensures that each branch is taken at least once by the test cases, and thus reveals the behavior of the software under different scenarios. Branch coverage is also known as decision coverage or all-edges coverage.
Branch coverage is suitable for testing the cases where a specific action is not allowed, because it can verify that the test cases cover all the possible outcomes of the conditions that determine the action.
For example, if the program has a condition that checks if the manufacturing stage can be stopped, then branch coverage can ensure that the test cases cover both the cases where the stage can be stopped and where it cannot be stopped. This way, branch coverage can help identify any missing or incorrect branches that may lead to undesired or unsafe actions.
The other options are not correct because they are not suitable for testing the cases where a specific action is not allowed. Code coverage is a general term that encompasses various types of coverage metrics, such as statement coverage, branch coverage, data flow coverage, etc. Code coverage does not specify which type of coverage metric is used for the analysis. Data flow coverage is a type of structural coverage metric that measures the percentage of data flow paths that are executed by the test cases. A data flow path is a sequence of statements that define, use, or kill a variable. Data flow coverage is useful for testing the correctness and completeness of the data manipulation in the software, but not for testing the conditions that determine the actions. Statement coverage is a type of structural coverage metric that measures the percentage of statements or lines of code that are executed by the test cases. Statement coverage ensures that each statement is executed at least once by the test cases, but it does not reveal the behavior of the software under different scenarios. Statement coverage is a weaker criterion than branch coverage, because it does not account for the branches or decision outcomes in the code. Reference = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54.
Question #57
Which ONE of the following statements about the objectives of confirmation and regression testing is the BEST?
- A . Confirmation testing aims to confirm that the observed failure is not a false positive. The regression test aims to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.
- B . The purpose of confirmation testing is to confirm that the defect giving rise to a failure has been successfully fixed. The regression test aims to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.
- C . The purpose of confirmation testing is to confirm that the defect giving rise to a failure has been satisfactorily fixed. The regression test aims to ensure that no defects have been introduced or discovered in modified areas of the software as a result of the changes made.
- D . The purpose of regression testing is to confirm that the defect giving rise to a failure has been satisfactorily resolved. The purpose of the confirmation testing is to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
“Confirmation testing confirms that an original defect has been successfully fixed… Regression testing confirms that no adverse consequences have been caused by a change… These adverse consequences could affect the same component where the change was made, other components in the same system, or even other connected systems.”
(ISTQB CTFL Syllabus v4.0, Section 2.2.3 C Confirmation Testing and Regression Testing, Page 30)
B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
“Confirmation testing confirms that an original defect has been successfully fixed… Regression testing confirms that no adverse consequences have been caused by a change… These adverse consequences could affect the same component where the change was made, other components in the same system, or even other connected systems.”
(ISTQB CTFL Syllabus v4.0, Section 2.2.3 C Confirmation Testing and Regression Testing, Page 30)
Question #58
Test automation allows you to:
- A . demonstrate the absence of defects
- B . produce tests that are less subject to human errors
- C . avoid performing exploratory testing
- D . increase test process efficiency by facilitating management of defects
Correct Answer: B
B
Explanation:
Test automation allows you to produce tests that are less subject to human errors, as they can execute predefined test scripts or test cases with consistent inputs, outputs, and expected results. Test automation can also reduce the manual effort and time required to execute repetitive or tedious tests, such as regression tests, performance tests, or data-driven tests. Test automation does not demonstrate the absence of defects, as it can only verify the expected behavior of the system under test, not the unexpected or unknown behavior. Test automation does not avoid performing exploratory testing, as exploratory testing is a valuable technique to discover new information, risks, or defects that are not covered by automated tests. Test automation does not increase test process efficiency by facilitating management of defects, as defect management is a separate activity that involves reporting, tracking, analyzing,and resolving defects, which may or may not be related to automated tests.
Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 3.3.1, Test Automation1 ISTQB® Glossary of Testing Terms v4.0, Test Automation2
B
Explanation:
Test automation allows you to produce tests that are less subject to human errors, as they can execute predefined test scripts or test cases with consistent inputs, outputs, and expected results. Test automation can also reduce the manual effort and time required to execute repetitive or tedious tests, such as regression tests, performance tests, or data-driven tests. Test automation does not demonstrate the absence of defects, as it can only verify the expected behavior of the system under test, not the unexpected or unknown behavior. Test automation does not avoid performing exploratory testing, as exploratory testing is a valuable technique to discover new information, risks, or defects that are not covered by automated tests. Test automation does not increase test process efficiency by facilitating management of defects, as defect management is a separate activity that involves reporting, tracking, analyzing,and resolving defects, which may or may not be related to automated tests.
Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 3.3.1, Test Automation1 ISTQB® Glossary of Testing Terms v4.0, Test Automation2
Question #59
Which of the following is an advantage of the whole team approach?
- A . It helps avoid the risk of tasks associated with a user story not moving through the Agile task board at an acceptable rate during an iteration
- B . It helps team members understand the current status of an iteration by visualizing the amount of work left to do compared to the time allotted for the iteration
- C . It helps the whole team be more effective in test case design by requiring all team members to master all types of test techniques
- D . It helps team members develop better relationships with each other and make their collaboration more effective for the benefit of the project
Correct Answer: D
D
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.
D
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.
Question #60
A tester created a decision table (DT) given below. While reviewing the DT some of the actions for the given conditions were found to be incorrect.
The user is trying to view the profile, which of the given conditions has CORRECT action(s) listed?
Condition C1 C2 C3 C4
Is the user logged in? Yes Yes No No
Is the user authorized to view the profile? Yes No Yes No
Action
Display the user’s profile Yes No Yes Yes
Display an error message Yes Yes No No
- A . C3
- B . C4
- C . C2
- D . C1
Correct Answer: C
C
Explanation:
The decision table provides conditions and corresponding actions. For C2:
The user is logged in (Yes).
The user is not authorized to view the profile (No).
The correct action should be not to display the profile (No) and to display an error message (Yes).
This matches the actions listed for C2, making it the correct condition with the proper actions.
C
Explanation:
The decision table provides conditions and corresponding actions. For C2:
The user is logged in (Yes).
The user is not authorized to view the profile (No).
The correct action should be not to display the profile (No) and to display an error message (Yes).
This matches the actions listed for C2, making it the correct condition with the proper actions.