[Apr 24, 2024] Latest ISQI CTFL2018 CTFL_Syll2018 Actual Free Exam Questions
ISQI CTFL2018 CTFL_Syll2018 Dumps Updated Practice Test and 365 unique questions
The CTFL_Syll2018 certification exam covers a wide range of topics related to software testing, including software development processes, testing methodologies, test design techniques, test management, and quality assurance. It is designed to test the candidate's knowledge and understanding of these topics, as well as their ability to apply this knowledge in practical testing scenarios. CTFL_Syll2018 exam consists of 40 multiple-choice questions and candidates have 60 minutes to complete it.
NEW QUESTION # 148 
The decision table above reflects a golf club's pricing structure for green fees and buggy/cart hire.
What is the expected result (actions) for each of the following two test cases (TC1 and TC2)?
* TC 1 - Paul is not a full member, is a Loyalty Card holder and requests to play 18 holes with a buggy/cart
* TC 2 - Cheryl is not at full member, doesn't have a Loyalty Card and requests to play 9 holes with a buggy/cart
- A. TC1 - £23 total charges including buggy hire; TC2 - £16 total charge but no buggy allowed
- B. TC1 - £23 total charges including buggy hire; TC2 - £21 total charge including buggy hire
- C. TC1 - £17 total charges but no buggy allowed; TC2 - £21 total charge including buggy hire
- D. TC1 - £18 total charges including buggy hire; TC2 - £16 total charge but no buggy allowed
Answer: A
Explanation:
TC1 - £23 total charges including buggy hire; TC2 - £16 total charge but no buggy allowed. This answer can be derived from the decision table by matching the conditions of each test case with the corresponding rules and actions. For TC1, the conditions are: Loyalty Card holder = Y, 18 Holes = Y, Buggy/Cart Request = Y.
These conditions match Rule 1, which has the actions: Green Fee = £18, Buggy Hire = £5, Total Charge = £23.
For TC2, the conditions are: Loyalty Card holder = N, 18 Holes = N, Buggy/Cart Request = Y. These conditions match Rule 3, which has the actions: Green Fee = £16, Buggy Hire = Not Allowed, Total Charge = £16
NEW QUESTION # 149
Which of the following is NOT a valid use of decision coverage?
- A. Checking that all decisions have been exercised in a business process.
- B. Checking that all decisions are based on a numeric value.
- C. Checking that all decisions have been exercised in a single program.
- D. Checking that at least 100% decision coverage has been achieved, as this guarantees 100% statement coverage.
Answer: B
Explanation:
Explanation
According to the syllabus, decision coverage is a technique that measures the percentage of decision outcomes that have been exercised by a test suite. A decision outcome is the result of evaluating a boolean expression in a control structure, such as an if statement or a switch statement. The goal of decision coverage testing is to cover and validate all the accessible source code by checking and ensuring that each branch of every possible decision point is executed at least once. The answer C is incorrect because it is not a valid use of decision coverage testing. Decision coverage testing does not check that all decisions are based on a numeric value, as there can be other types of values involved in boolean expressions, such as strings or booleans. The other answers are correct because they are valid uses of decision coverage testing. Checking that all decisions have been exercised in a single program or a business process can help to identify defects or missing functionality in the code or process logic. Checking that at least 100% decision coverage has been achieved can help to ensure that all reachable code has been executed and that 100% statement coverage has been achieved as well.
References: Certified Tester Foundation Level Syllabus, Section 4.2.3, page 42-43.
NEW QUESTION # 150
Refer to the exhibit
Given the following State Transition diagram, match the test cases below with the relevant set of state transitions.
(i)X-Z-V-W
(ii)W-Y-U-U
- A. (i) = S1 - S2 - S3 - S4 - S2 and (ii) = S4 - S2 - S4 - S4 - S4
- B. (i) = S1 - S2 - S3 - S4 - S4 and (ii) = S2 -S4 - S4 - S4 - S2
- C. (i) = S2 - S3 - S4 - S2 - S2 and (ii) = S4 - S2 - S4 - S4 - S4
- D. (i) = S2 - S3 - S4 - S4 - S2 and (ii) = S2 -S3 - S4 -S4 - S4
Answer: A
Explanation:
Explanation
State transition testing is a technique that uses state transition diagrams as a test basis to derive test cases2. A state transition diagram shows the states of a system and the transitions between them triggered by events or conditions2. A test case can cover one or more state transitions, depending on the test objective and coverage criterion2. In this question, the test cases (i) and (ii) cover different sets of state transitions, as shown below:
Test Case
State Transitions
(i) X-Z-V-W
S1 - S2 - S3 - S4 - S2
(ii) W-Y-U-U
S4 - S2 - S4 - S4 - S4
NEW QUESTION # 151
What is a defect density?
- A. The deviation rate of the system from its expected behavior
- B. The number of defects identified in the system under test divided by the size of the system
- C. The ratio of the defects identified in these system over the expected number of total defects
- D. The percentage of defects identified over the total number of test cases
Answer: B
Explanation:
Defect density is a metric that measures the number of defects identified in the system under test divided by the size of the system. The size of the system can be measured in different ways, such as lines of code, function points, or modules. Defect density can be used to compare the quality of different systems or different versions of the same system.
References: [Certified Tester Foundation Level Syllabus], Section 8.3.1
NEW QUESTION # 152
What is the main reason for using a pilot project to introduce a testing tool into an organization? [K1]
- A. To make a selection between alternative tools
- B. To assess whether the tool will be cost- effective
- C. To identify the requirements for using a tool
- D. To ensure the tools fits existing processes without change
Answer: B
NEW QUESTION # 153
Consider the following pseudo code:
1. Begin
2. Input X, Y
3. If X > Y
4. __Print (X, 'is greater than', Y)
5. Else
6. __Print (Y, is greater than or equal to', X)
7. EndIf
8. End
What is the minimum number of test cases required to guarantee both 100% statement coverage and 100%
decision coverage?
- A. Statement coverage = 2, Decision coverage = 2
- B. Statement coverage = 2, Decision coverage = 1
- C. Statement coverage = 1, Decision coverage = 2
- D. Statement coverage = 3, Decision coverage = 3
Answer: A
NEW QUESTION # 154
Which of the following apply to System Testing?
a) May satisfy legal requirements.
b) Can use system specifications as a test basis.
c) Often the responsibility of business users.
d) Main goal is to establish confidence.
e) Should focus on the communication between systems.
- A. c and e.
- B. b and d.
- C. a and c.
- D. a and b.
Answer: B
NEW QUESTION # 155
Which of the following would be appropriate test objectives for user acceptance testing of the first release of a
new software product aimed at a general market and built using Agile methods? [K2]
a. To identify as many defects as possible
b. To maximise code coverage
c. To ensure the product works as expected
d. To assess the overall quality of the product
e. To determine the reliability of the product
- A. b and e
- B. b and c
- C. a and d
- D. c and d
Answer: D
NEW QUESTION # 156
Consider the following excerpt from a defect report:
To recreate the failure we used test file TST_01_TC_16.dat which is available in the common shared folder''.
Which incident report objective does this excerpt satisfy?
- A. Provides test leaders with information to report test progress
- B. Provides ideas for test process improvement
- C. Provides developers with information to isolate the failure
- D. Does not belong in an incident report.
Answer: C
Explanation:
Explanation
Providing developers with information to isolate the failure is the incident report objective that this excerpt satisfies. The excerpt provides the name and location of the test file that was used to recreate the failure, which can help developers to reproduce and debug the failure in their own environment. defines this objective as follows:
One of the objectives of an incident report is to provide developers with information to isolate the failure. This means providing enough details and evidence for developers to understand what caused the failure and how to fix it. This may include information such as:
Steps to reproduce: A sequence of steps that can be followed to recreate the failure.
Test data: The inputs that were used to execute the test case that caused the failure.
Test environment: The configuration and settings of the hardware and software that were used to execute the test case that caused the failure.
Attachments: Any screenshots, logs, files, or other artifacts that can help to demonstrate or explain the failure.
B, C, and D are incorrect answers. Providing ideas for test process improvement (B) is not an incident report objective that this excerpt satisfies, as it does not provide any suggestions or feedback on how to improve the test process or prevent similar failures in the future. Not belonging in an incident report is not true, as this excerpt belongs in an incident report as part of the incident details section. Providing test leaders with information to report test progress (D) is not an incident report objective that this excerpt satisfies, as it does not provide any metrics or indicators on how much testing has been done or how many failures have been found.
NEW QUESTION # 157
A Software was re-deployed because the backend database was changed from one vendor to another The Test Manager decided to perform some functional tests on the redeployed system. This is an example of test of which test type?
- A. Unit tests
- B. Structural tests
- C. Regression tests
- D. Non-functional tests
Answer: C
Explanation:
Explanation
Regression testing is a type of testing that is performed after a software system has been changed or modified to verify that the changes have not introduced any new defects or adversely affected the existing functionality of the system. Regression testing can be performed when the software system undergoes different types of changes, such as:
Corrective changes: Changes that fix defects or errors in the software system Adaptive changes: Changes that adapt the software system to new platforms or environments Perfective changes: Changes that improve the performance or usability of the software system Preventive changes: Changes that avoid potential problems or issues in the software system In this case, the software system was re-deployed because the backend database was changed from one vendor to another, which is an example of an adaptive change. Therefore, the test manager decided to perform some functional tests on the re-deployed system to ensure that the change did not affect the functionality of the system. This is an example of regression testing.
The other types of testing mentioned in the question are not relevant for this scenario. For example:
Non-functional testing: This type of testing verifies the non-functional aspects of the software system, such as reliability, performance, security, usability, etc.
Structural testing: This type of testing verifies the internal structure or implementation of the software system, such as code, architecture, design, etc.
Unit testing: This type of testing verifies individual components or units of software in isolation from other components or systems.
You can find more information about regression testing in [A Study Guide to the ISTQB Foundation Level
2018 Syllabus], Chapter 2, Section 2.4.
NEW QUESTION # 158
What is the value of static code analysis?
- A. Detection of failures not easily found by other types of testing
- B. Early defect detection
- C. Detection of suspicious operations caused by deviations from regulations
- D. Detect deviations in standards by executing the source code
Answer: B
Explanation:
Static code analysis is a technique that examines the source code or other software artifacts without executing them, and can detect defects, vulnerabilities, code smells, and deviations from standards early in the development process1. According to the ISTQB syllabus, one of the benefits of static testing is early defect detection2, which can reduce the cost and effort of fixing them later.
NEW QUESTION # 159
Consider the following code
int premium=2500;
if <age<30)
{
premium = premium +1500:
}
Which options suits for a correct combination of Boundary value and expected result. Assume first number as
boundary followed by expected result.
- A. 30. 1500
31, 2500 - B. 29,1500
30. 2500 - C. 29.4000
30. 2500 - D. 29. 2500
30, 1500
Answer: A
NEW QUESTION # 160
What is the ideal number of regression test cycles?
- A. Until the quality requirements are met
- B. 0
- C. As many as time and budget allow
- D. 1
Answer: C
Explanation:
The ideal number of regression test cycles is as many as time and budget allow, because regression testing is done to ensure that no new defects have been introduced by changes or fixes in the software, and that all previously fixed defects are still fixed. Therefore, more regression test cycles can increase the confidence in the software quality and reliability.
Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus1, Chapter 5, Section 5.4.2, page
133.
NEW QUESTION # 161
Which of the following BEST describes a Test Case?
- A. A description of the test objectives to be achieved and the means and the schedule for achieving them.
- B. A set of preconditions, inputs, actions, expected results and postconditions developed based on test
conditions. - C. A statement about "what to test" in terms of measurable coverage criteria from analysis of the test basis.
- D. A source to determine expected results to compare with the actual result of the system under test.
Answer: B
NEW QUESTION # 162
Which of the following statements contradicts the general principles of testing?
- A. Testing is better if it starts at the beginning of a project
- B. If new defects are to be found, we should run the same test set more often
- C. Most defects are found in a small subset of a system's modules
- D. How testing is done, is based on the situation in a particular project.
Answer: B
Explanation:
Explanation
The general principles of testing state that testing can show the presence of defects, but not their absence.
Running the same test set more often will not increase the likelihood of finding new defects, unless the system or its environment changes. Therefore, statement A contradicts the general principles of testing. Statement B is true, as testing is context-dependent and should be tailored to the specific situation of a project. Statement C is also true, as early testing can help prevent defects and reduce rework. Statement D is true, as it reflects the Pareto principle or the 80/20 rule, which states that most defects are found in a small subset of a system's modules.
References: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 1.2
NEW QUESTION # 163
Which of the following test execution outcomes are likely to increase the overall quality of the software:
I) A test case passes
II) A test case fails, defect gets logged which subsequently gets fixed III) Some tests are deferred because test environment is not available IV) A bug is found but there is no corresponding test case
- A. I and II
- B. I and IV
- C. I, II and III
- D. I, II and IV
Answer: A
NEW QUESTION # 164
What other details should be included in the following incident report when it is first submitted?
Date of Issue: 23/11/05
Severity: P1
Build: Version15.6
Details: Expected field to be limited to 15 chars, able to enter 27
- A. History, related defects and expected fix time.
- B. Suggested solution, priority and number of defects assigned to this developer.
- C. Line of code, number of defects found, time of day.
- D. Status of the incident, degree of impact, Test Case Number.
Answer: D
Explanation:
Explanation
The other details that should be included in the incident report when it is first submitted are B. Status of the incident, degree of impact, Test Case Number. These details are important to provide information about the current state of the incident, the severity of its effect on the system or user, and the test case that detected the incident. Other details, such as suggested solution, priority, history, related defects, expected fix time, line of code, etc., can be added later during the incident management process. A detailed explanation of incident report can be found in A Study Guide to the ISTQB Foundation Level 2018 Syllabus, pages 99-1001.
NEW QUESTION # 165
The four test levels used in ISTQB syllabus are:
Component (unit) testing
2 Integration testing
3. System testing
4 Acceptance testing
An organization wants to do away with integration testing but otherwise follow V-model.
Which of the following statements is correct?
- A. It is not allowed because integration testing is a very important test level and ignoring it means definite poor product quality
- B. It is allowed because integration testing is not an important test level and can be dispensed with
- C. It is not allowed as organizations can't change the test levels as these are chosen on the basis of the SDLC (software development life cycle) model
- D. It is allowed as organizations can decide on which test levels to do depending on the context of the system under test
Answer: C
Explanation:
Explanation
It is not allowed as organizations can't change the test levels as these are chosen on the basis of the SDLC (software development life cycle) model. The V-model is a type of SDLC model that defines four test levels:
component testing, integration testing, system testing, and acceptance testing. Each test level corresponds to a development phase in a parallel manner. Integration testing is an essential part of the V-model, as it verifies that the components work together correctly and consistently2 explains this as follows:
The V-model is a graphical representation of a systems development lifecycle. It is used to produce rigorous development lifecycle models and project management models. The V-model falls into three broad categories, the German V-Modell, a general testing model and the US government standard.
The V-model summarizes the main steps to be taken in conjunction with the corresponding deliverables within project execution and delivery. It describes software development activities from requirements specification to maintenance.
The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing.
A, C, and D are incorrect answers. A implies that integration testing is not an important test level and can be dispensed with, which is not true as integration testing ensures that the system functions as a whole and meets its requirements. C implies that organizations can decide on which test levels to do depending on the context of the system under test, which is not true as test levels are determined by the chosen SDLC model and its objectives. D implies that integration testing is a very important test level and ignoring it means definite poor product quality, which is true but not relevant to why it is not allowed to do away with integration testing in a V-model.
NEW QUESTION # 166
An organization is working on updating test cases for a particular module of their software.
Sam updated a set of test cases yesterday and saved the new version on his PC.
Unfortunately, the hard disk of his PC crashed, and his work was lost.
The IT department of the organization restored the contents of his hard disk with the last available back-up -
from the previous morning However the changes made by him yesterday were lost forever
Which of the following tools, had it been used, would have prevented the loss of Sam's updates?
- A. Configuration Management Tool
- B. Backup tool
- C. Test Execution tool
- D. Incident Management Tool
Answer: D
NEW QUESTION # 167
Which of the following are correct tasks during "Test analysis and design"?
I. Designing and prioritizing test cases
II Identifying any required infrastructure and tools
III. Reviewing the test basis
IV Creating test data and preparing test harnesses
V. Writing automated test scripts
- A. I, ll
- B. I, II. Ill
- C. l, III IV
- D. II, III, IV, V
Answer: B
Explanation:
Test analysis and design is the phase of the test process where test cases and test data are designed and prioritized, based on the test basis and test objectives. Therefore, option C is correct, as it includes tasks I, II, and III. Option A is incorrect, as it includes tasks IV and V, which are part of test implementation and execution phase. Option B is incorrect, as it includes task IV, which is part of test implementation and execution phase. Option D is incorrect, as it does not include task III, which is part of test analysis and design phase.
References: [Certified Tester Foundation Level Syllabus], Section 2.2
NEW QUESTION # 168
Which of the following is a typical characteristic of the WALKTHROUGH review type?
- A. The meeting is led by the author.
- B. Attendees must prepare before the meeting.
- C. Metrics are gathered throughout.
- D. Entry and exit criteria are defined.
Answer: A
NEW QUESTION # 169
While reporting a defect, which of the following indicates the level of business importance assigned to the defect?
- A. Difficulty
- B. Priority
- C. Severity
- D. Urgency
Answer: B
Explanation:
Explanation of Correct Answer: Priority indicates the level of business importance assigned to the defect, while severity indicates the degree of impact that a defect has on the development or operation of a component or system. Urgency is not a standard term used in defect reporting, and difficulty refers to the effort required to fix the defect.
References: Section 1.4.3.2, Section 5.3.2
NEW QUESTION # 170
The following test cases for a Library Management System are available to test changes made to the functions and data structures associated with borrowers
1. Add a new borrower to the system
2. Update a borrower's data
3. Remove a borrower from the system
4. Loan a book to a borrower
5. Return a book from a borrower
6. Reserve a book for a borrower
7. Send "reservation ready" message to a borrower
Which of the following test sequences represents a possible use case? (a test sequence always start with test #1)
- A. 1-6-4-7-5-3-2
- B. 1-2-6-7-4-5-3
- C. 1-4-2-7-5-6-3
- D. 1-6-2-5-7-4-3
Answer: B
Explanation:
Explanation
A use case is a description of how a user interacts with a system to achieve a goal or perform a task. A use case typically consists of a sequence of steps or actions that the user and the system perform to complete the goal or task. A use case can be used as a basis for designing test cases that verify the functionality and usability of the system under test. A test sequence that represents a possible use case should follow the logical order and flow of the user-system interaction and cover the main scenario and possible variations or exceptions. For example, based on the test cases given for a Library Management System, we can identify the following use cases:
UC1: Add a new borrower to the system
UC2: Update a borrower's data
UC3: Remove a borrower from the system
UC4: Loan a book to a borrower
UC5: Return a book from a borrower
UC6: Reserve a book for a borrower
UC7: Send "reservation ready" message to a borrower
The test sequence that represents a possible use case is D. 1-2-6-7-4-5-3. This test sequence follows the logical order and flow of the user-system interaction and covers the main scenario and possible variations or exceptions. For example:
TC1: Add a new borrower to the system -> This is the first step of the use case, where the user registers as a new borrower in the system.
TC2: Update a borrower's data -> This is a possible variation of the use case, where the user updates their personal or contact information in the system.
TC6: Reserve a book for a borrower -> This is the second step of the use case, where the user reserves a book that they want to borrow from the library.
TC7: Send "reservation ready" message to a borrower -> This is the third step of the use case, where the system sends a message to the user informing them that their reserved book is ready for pickup.
TC4: Loan a book to a borrower -> This is the fourth step of the use case, where the user picks up their reserved book from the library and loans it from the system.
TC5: Return a book from a borrower -> This is the fifth step of the use case, where the user returns their borrowed book to the library and returns it to the system.
TC3: Remove a borrower from the system -> This is a possible exception of the use case, where the user decides to cancel their membership and remove their account from the system.
The other test sequences do not represent possible use cases because they do not follow the logical order and flow of the user-system interaction or they do not cover the main scenario and possible variations or exceptions. For example:
A). 1-4-2-7-5-6-3 -> This test sequence does not follow the logical order and flow of the user-system interaction because it performs some steps before or after they are supposed to happen. For example, it performs TC4 (Loan a book to a borrower) before TC6 (Reserve a book for a borrower), which does not make sense because the user cannot loan a book that they have not reserved yet.
B). 1-6-2-5-7-4-3 -> This test sequence does not follow the logical order and flow of the user-system interaction because it performs some steps before or after they are supposed to happen. For example, it performs TC5 (Return a book from a borrower) before TC4 (Loan a book to a borrower), which does not make sense because the user cannot return a book that they have not loaned yet.
C). 1-6-4-7-5-3-2 -> This test sequence does not cover the main scenario and possible variations or exceptions because it omits some steps that are essential for completing or terminating the use case. For example, it omits TC2 (Update a borrower's data), which is a possible variation of the use case that allows the user to change their personal or contact information in the system.
You can find more information about use cases and test sequences in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.2.
NEW QUESTION # 171
Consider the following pseudo-code
How many minimum test cases are required to cover 100% Statement coverage and Decision coverage?
- A. 5 for Statement, 5 for Decision
- B. 8 for Statement, 6 for Decision
- C. 6 for Statement, 8 for Decision
- D. 4 for Statement, 5 for Decision
Answer: B
NEW QUESTION # 172
......
ISQI CTFL_Syll2018 exam is a comprehensive exam that covers a wide range of topics related to software testing. CTFL_Syll2018 exam is designed to test your knowledge and understanding of the key concepts and techniques used in software testing. CTFL_Syll2018 exam consists of 40 multiple-choice questions and is 60 minutes long. To pass the exam, you need to score at least 65% of the total marks.
Verified CTFL_Syll2018 dumps Q&As - 100% Pass from ActualVCE: https://www.actualvce.com/ISQI/CTFL_Syll2018-valid-vce-dumps.html
Latest 100% Exam Passing Ratio - CTFL_Syll2018 Dumps PDF: https://drive.google.com/open?id=13oad5IL5I5Qknv4BGCO294CCeFJH-GPe