[Apr-2024] Use Real CTFL_Syll2018 Dumps - 100% Free CTFL_Syll2018 Exam Dumps
CTFL_Syll2018 PDF Dumps Exam Questions – Valid CTFL_Syll2018 Dumps
NEW QUESTION # 194
Which of the following BEST defines static techniques? [K1]
- A. Executing the software work product
- B. Automated analysis of the code or project documentation
- C. Manually examining the code or project documentation
- D. Manual examination and automated analysis of code or project documentation
Answer: D
Explanation:
The statement that best defines static techniques is D.
Manual examination and automated analysis of code or project documentation. Static techniques are techniques that analyze the code or other software artifacts (such as requirements, specifications, designs, models, test cases, etc.) without executing them, and provide information about their quality, defects, complexity, maintainability, etc. Static techniques can be performed manually or automatically by using tools or methods such as reviews, inspections, walkthroughs, checklists, standards, guidelines, static analysis tools, code metrics tools, etc. Static techniques can help to improve the quality and consistency of code or other software artifacts throughout the software development life cycle and reduce the cost and effort of testing and debugging. A detailed explanation of static techniques can be found in
[A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 27-34.
NEW QUESTION # 195
Which of the following sentences is correct?
- A. Functional and Structural test levels can be performed for all test types
- B. Functional tests can be performed at Integration and System test levels, while Structural tests can be
performed at Unit test level - C. Functional and Structural tests can be performed at all test levels
- D. Functional tests can be performed at Unit and Integration test levels, while Structural tests can be
performed at System test level
Answer: B
NEW QUESTION # 196
Which TWO of the following test tools would be classified as test execution tools? [K2] a. Test data preparation tools b. Test harness c. Review tools d. Test comparators e. Configuration management tools
- A. a and b
- B. c and e
- C. b and d
- D. c and d
Answer: C
NEW QUESTION # 197
Which of the following statements about decision tables are TRUE?
I. Generally, decision tables are generated for low risk test items
II. Test cases derived from decision tables can be used for component tests.
III. Several test cases can be selected for each column of the decision table.
IV. The conditions in the decision table represent negative tests generally.
- A. I, IV
- B. II, Ill
- C. II, IV
- D. I, Ill
Answer: B
Explanation:
Explanation
A decision table is a specification-based test technique that involves creating a table that shows the combinations of inputs and outputs for a system under test based on certain conditions and rules. A decision table can be used to design test cases that cover all possible scenarios and outcomes for a system under test.
Some statements about decision tables are:
I). Generally, decision tables are generated for low risk test items: This statement is false because decision tables can be generated for any level of risk test items depending on the complexity and variability of the system under test. Decision tables are especially useful for testing systems that have many inputs, outputs, conditions, and rules that affect their behavior or performance.
II). Test cases derived from decision tables can be used for component tests: This statement is true because decision tables can be used to design test cases for any level or type of testing, including component tests. Component tests are tests that verify individual components or units of software in isolation from other components or systems.
III). Several test cases can be selected for each column of the decision table: This statement is true because each column of the decision table represents a unique combination of inputs and outputs for the system under test based on certain conditions and rules. Therefore, each column can be used as a basis for selecting one or more test cases that cover that combination.
IV). The conditions in the decision table represent negative tests generally: This statement is false because the conditions in the decision table can represent both positive and negative tests depending on the requirements and expectations of the system under test. Positive tests are tests that verify that the system under test behaves as expected under valid or normal inputs or conditions. Negative tests are tests that verify that the system under test handles errors or exceptions gracefully under invalid or abnormal inputs or conditions.
You can find more information about decision tables in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.2.
NEW QUESTION # 198
Which of the following is a defect that is more likely to be found by a static analysis tool than by other testing
techniques?
- A. Omission of a major requirement
- B. Component memory leakage
- C. Inadequate decision coverage
- D. Variables that are not used improperly declared
Answer: D
NEW QUESTION # 199
Which of the following represents good testing practice for testers, irrespective of the software lifecycle model used?
- A. They should ensure that the same test objectives apply to each test level
- B. They should be involved in reviewing requirements or user stories as soon as drafts are available
- C. They should minimize the ratio of development levels to test levels to reduce project costs
- D. They should start test analysis when the corresponding development level is complete
Answer: B
Explanation:
Explanation
They should be involved in reviewing requirements or user stories as soon as drafts are available is the option that represents good testing practice for testers, irrespective of the software lifecycle model used, because it allows testers to provide early feedback, identify potential defects, and clarify test objectives and scope1 . Early involvement of testers in reviewing requirements or user stories can improve the quality and testability of the software and reduce the cost and effort of testing1 . The other options do not represent good testing practice for testers, irrespective of the software lifecycle model used. Option A is not a good option, because they should start test analysis as early as possible, not when the corresponding development level is complete, to avoid delays and inefficiencies in testing1 . Option C is not a good option, because they should ensure that different test objectives apply to each test level, not the same test objectives, to avoid redundancy and gaps in testing1 . Option D is not a good option, because they should minimize the ratio of development levels to test levels to reduce project costs, but rather balance the development and test levels according to the project needs and risks1 .
NEW QUESTION # 200
Testing and Debugging are key activities in the software development lifecycle.
Which of the following are DEBUGGING activities?
a) Designing tests to find failures.
b) Locating the cause of failures.
c) Analysing and fixing the defects.
d) Executing tests to show failures.
- A. b and c.
- B. c and d.
- C. a and d.
- D. a and b.
Answer: A
Explanation:
Explanation
Testing and debugging are two different activities that are related to finding and removing defects and failures in software. Testing is the process of evaluating software by applying test cases to find failures and provide information on its quality. Debugging is the process of finding, analyzing, and removing the causes of failures in software. Designing tests to find failures and executing tests to show failures are testing activities. Locating the cause of failures and analyzing and fixing the defects are debugging activities.
References: Certified Tester Foundation Level Syllabus, Section 1.2.1
NEW QUESTION # 201
Which of the following statements is the best explanation why software failures can be caused by environmental conditions?
- A. Environmental conditions only affect the hardware - not the software
- B. If the hardware on which the software application is running under ambient temperature and humidity, no failures can be linked to environmental conditions
- C. Extreme heat and vibrations exerted on storage media can cause errors in algorithms and program flows
- D. Factors like magnetism, radiation and even pollution can affect electronic devices and the performance of their embedded real time software
Answer: A
Explanation:
The statement that environmental conditions only affect the hardware - not the software is not a good explanation why software failures can be caused by environmental conditions. Environmental conditions can affect both the hardware and the software, as they can influence the performance, reliability, and functionality of the system. For example, factors like magnetism, radiation, pollution, heat, humidity, vibration, etc. can affect electronic devices and the embedded software that runs on them. Software failures caused by environmental conditions can have serious consequences, especially for safety-critical systems.
References: Certified Tester Foundation Level Syllabus, Section 1.2.2
NEW QUESTION # 202
What of the following statements regarding walkthrough are NOT true?
- A. Pre-meeting preparation, documentation and distribution of results are optional for a walkthrough
- B. A walkthrough may take the form of scenarios, dry runs and peer group review
- C. A walkthrough is lead by a moderator and requires pre-meeting preparation and post meeting follow up
- D. The purpose of a walkthrough is to establish common understanding of a document and to find possible defects in it
Answer: C
NEW QUESTION # 203
Which of the following statements is NOT correct?
- A. A test team with high level of independence, may suffer from lower familiarity with the product
- B. Tests designed by a person from different group in the organization is the highest independence level
- C. Tests designed by a person in the development team other than the person who wrote the code is the lowest level of independence
- D. Development team may find many defects since they are familiar with the code
Answer: C
Explanation:
Explanation
Tests designed by a person in the development team other than the person who wrote the code is not the lowest level of independence. The lowest level of independence is tests designed by the person who wrote the code, as this may introduce bias or blind spots in testing. Tests designed by another person in the development team is one level higher than tests designed by the person who wrote the code, as this may provide a different perspective or expertise in testing. defines the levels of independence as follows:
The level of independence of testing is related to the degree of separation between those who are responsible for developing software and those who are responsible for testing software.
The following levels of independence can be distinguished:
Level 0: No independent testing; tests are designed by the same person who wrote the code.
Level 1: Tests are designed by another person in the development team; e.g., another programmer or software designer.
Level 2: Tests are designed by a person from a different group within the organization; e.g., an independent test team or group.
Level 3: Tests are designed by a person from a different organization or company; e.g., an outsourcing partner or contractor.
A, B, and C are correct statements. A test team with high level of independence may suffer from lower familiarity with the product (A), as they may not have access to all the information or knowledge about the system under test. Development team may find many defects since they are familiar with the code (B), as they may have more insight into how the system works internally and where potential problems may occur. Tests designed by a person from different group in the organization is the highest level of independence within an organization, as this provides maximum separation between development and testing activities.
NEW QUESTION # 204
A tester thinks of a likely cause for a specific bug Should the tester make a comment about this in the bug report?
- A. Yes Observations that may help correct a bug should be included in the bug report
- B. No. A bug r^&ort must only include factual information, and not unsupported hypothesis
- C. No. Such addition may bias the developers' attitude when they attempt to fix the bug
- D. Yes It will reduce the risk that the bug fix will cause a regression
Answer: A
Explanation:
A bug report is a document that records the details of a defect or failure found during testing, such as the steps to reproduce, the expected and actual results, the severity and priority, etc. A bug report should also include any observations or suggestions that may help correct the bug, such as the possible cause, the affected components, the related requirements, etc. This information can help the developers to locate and fix the bug more efficiently and effectively. Therefore, if a tester thinks of a likely cause for a specific bug, they should make a comment about it in the bug report.
References: Certified Tester Foundation Level Syllabus, Section 6.
NEW QUESTION # 205
A software company decided to buy a commercial application for its accounting operations. As part of the
evaluation process, the company decided to assemble a team to test a number of candidate applications.
Which team would be the most suitable for this goal?
- A. A team with a mix of software testers and experts from the accounting department
- B. A team from an outsourcing company which specializes in testing accounting software
- C. A team from the company's testing team, due to their experience in testing software
- D. A team of users from the accounting department that will need to use the application on dairy basis
Answer: C
NEW QUESTION # 206
The ISTQB fundamental test process consists of 5 main activities To which of these belongs the task
"Identifying necessary test data"?
- A. Evaluating test criteria and reporting
- B. Test implementation and execution
- C. Test planning and control
- D. Test analysis and design
Answer: C
NEW QUESTION # 207
Test objectives for systems testing of a safety critical system include completion of all outstanding defect correction. Regression testing is required following defect correction at all test levels. Which TWO of the following metrics would be MOST suitable for determining whether the test objective has been met? [K2] a. Regression tests run and passed in systems testing b. Incidents closed in systems testing c. Planned tests run and passed in system testing d. Planned tests run and passed at all levels of testing e. Incidents raised and closed at all levels of testing
- A. b and c
- B. a and b
- C. d and e
- D. a and e
Answer: D
Explanation:
Explanation
Test objectives are specific goals or targets that define what testing activities should achieve or accomplish1.
Test objectives for systems testing of a safety critical system include completion of all outstanding defect correction. Regression testing is required following defect correction at all test levels. Therefore, to determine whether this test objective has been met, two metrics that would be most suitable are:
Regression tests run and passed in systems testing: This metric measures how many regression tests have been executed and passed in systems testing1. Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes or defect corrections1. This metric can indicate whether all outstanding defect corrections have been completed and verified in systems testing.
Incidents raised and closed at all levels of testing: This metric measures how many incidents have been reported and resolved at all levels of testing1. An incident is any event occurring during testing that requires investigation1. This metric can indicate whether all defects have been identified and corrected at all levels of testing.
NEW QUESTION # 208
System testing is:
- A. Concerned with the behavior of a whole system/product as defined by the scope of a development project.
- B. Used to search for defects in software modules that are separately testable.
- C. The responsibility of the users of a system.
- D. Triggered by modifications, migration or retirement of the software system.
Answer: A
NEW QUESTION # 209
What is a peer review?
- A. A review done by colleagues at the same organizational level
- B. An informal review without moderator
- C. A review done by developers and testers together
- D. A review done by developers only
Answer: D
NEW QUESTION # 210
Which of the following statements about independent testing is WRONG?
- A. A certain degree of independence makes the tester more effective at finding defects
- B. Independent testing is necessary because developers don't know any testing
- C. Independent test teams may find other types of defects than developers who are familiar with the system's structure.
- D. Independent testing is best suited for the system test level
Answer: B
Explanation:
The statement that independent testing is necessary because developers don't know any testing is wrong.
Developers do know some testing, as they perform unit testing and component testing on their own code.
However, independent testing is beneficial because it can provide a different perspective and a higher degree of objectivity than testing done by developers. Independent testers may have different skills, knowledge, experience, and expectations than developers, which can help them find different types of defects and improve the quality of the system.
References: Certified Tester Foundation Level Syllabus, Section 2.2
NEW QUESTION # 211
Which of the following accurately defines the integration testing test level? [K2]
- A. Test basis includes business processes, test objects include system configuration and configuration data,
and tests concentrate on establishing confidence in the system - B. Test basis includes component requirements, test objects include database modules, and tests
concentrate on the behaviour of the system as a whole. - C. Test basis includes software and system design, test objects include interfaces, and tests concentrate on
the interactions between different parts of a system - D. Test basis includes use cases, test objects include user procedures and tests concentrate on a high level
model of system behaviour
Answer: C
NEW QUESTION # 212
"Statement Testing" is part of;
- A. Specification Based testing
- B. Structured based testing
- C. Decision Testing
- D. Experience based testing
Answer: B
Explanation:
Statement testing is part of structure-based testing, which is a type of testing that verifies the internal structure or implementation of a software system, such as code, architecture, design, etc. Statement testing is a structure-based test technique that involves testing every statement in the code at least once to ensure that there are no syntax errors, logical errors, or hidden defects in the code. Statement testing requires some knowledge of the internal structure or implementation of the software system; it focuses on how the system does what it does rather than what it does.
The other types of testing mentioned in the question are not related to statement testing because they do not verify the internal structure or implementation of a software system. For example:
* A. Experience-based testing: This type of testing relies on the skills, knowledge, intuition, and creativity of testers to design and execute test cases based on their experience with similar systems or situations.
* B. Decision testing: This type of testing verifies every decision point in the code by testing all possible outcomes or branches of each decision point to ensure that there are no logical errors or hidden defects in the code.
* C. Specification-based testing: This type of testing verifies the external behavior or functionality of a software system based on its requirements, specifications, design documents, or other sources of information.
You can find more information about statement testing and structure-based testing in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.3.
NEW QUESTION # 213
Which of the following statements BEST describes how test cases are derived from a use case?
- A. Test cases are created using white-box test techniques to execute scenarios of use cases
- B. Test cases are designed to cover various user behaviors, including basic, exceptional or alternative and error behaviors associated with human users or systems
- C. Test cases are derived based on non-functional requirements such as usability
- D. Test cases are derived based on pair testing between a user and a tester to find defects
Answer: B
Explanation:
It describes how test cases are derived from a use case. A use case is a description of a set of sequences of actions, including variants, that a system performs to yield an observable result of value to an actor1. An actor can be a human user or another system. Test cases are designed to cover various user behaviors, including basic, exceptional or alternative and error behaviors associated with each use case1. Option A is incorrect, as test cases derived from a use case are not based on non-functional requirements such as usability, but on functional requirements that describe what the system does1. Option C is incorrect, as test cases derived from a use case are not created using white-box test techniques, but using black-box test techniques that focus on the inputs and outputs of the system1. Option D is incorrect, as test cases derived from a use case are not based on pair testing, which is a technique that involves two testers working together to find defects1. References: 1, Section 4.2.4
NEW QUESTION # 214
You are testing an e-commerce system The system accepts four different types of Credit Cards; each card has
its own rules for valid and invalid numbers. The following is a portion of the Decision Table for Order
Management.:
The combination of the conditions Valid Card Number (NO) + Purchase Approved (YES) is not feasible.
You wish to perform a test which completely covers all the combinations of equivalence partitioning tor the
different types of credit card, according to the rules shown in the above Decision Table
How many test cases do you need?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: A
NEW QUESTION # 215
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. 29. 2500
30, 1500 - B. 30. 1500
31, 2500 - C. 29.4000
30. 2500 - D. 29,1500
30. 2500
Answer: B
NEW QUESTION # 216
Which statement correctly describes debugging? [K2]
- A. Developers identify defects, testers locate defects, developers correct and confirm the correction has cleared the original defect
- B. Testers identify defects, developers locate and correct defects, testers confirm the correction has cleared the original defect
- C. Developers identify, locate and correct defects, testers confirm the correction has cleared the original defect
- D. Testers identify and locate defects, developers correct defects and confirm the correction has cleared the original defect
Answer: B
Explanation:
Explanation
Testers identify defects, developers locate and correct defects, testers confirm the correction has cleared the original defect. Debugging is the process of finding and fixing defects in a software product by analyzing its code or behavior. Debugging is usually performed by developers who have access to and knowledge of the code or structure of the software product. Debugging involves locating and correcting defects identified by testers during testing activities, and verifying that the correction has cleared the original defect without introducing new defects. Testers can also participate in debugging by providing information about how to reproduce defects, what are the expected results, what are the actual results, etc., and by confirming that defects have been fixed after debugging. A detailed explanation of debugging can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], page 6.
NEW QUESTION # 217
Which of the following describes a task performed as part of the Test Implementation and Execution' activity?
- A. Evaluating the testability of the test basis and test objects
- B. Selecting metrics for monitoring test execution and defect resolution
- C. Assessing if the specified exit criteria should be changed
- D. Logging the outcome of test execution and reporting bugs
Answer: D
Explanation:
Logging the outcome of test execution and reporting bugs is an activity that is performed as part of the Test Implementation and Execution activity, because it involves recording and communicating any deviations from the expected results or behaviour of the software under test1 . Test Implementation and Execution is the process of running the test cases or procedures on the software under test and comparing the actual results with the expected results1 . The other options are not activities that are performed as part of the Test Implementation and Execution activity, but rather as part of other activities. Option B is an activity that is performed as part of the Test Analysis activity, because it involves evaluating the testability of the test basis and test objects to identify test conditions1 . Option C is an activity that is performed as part of the Test Closure activity, because it involves assessing if the specified exit criteria should be changed to determine when to stop testing1 . Option D is an activity that is performed as part of the Test Planning activity, because it involves selecting metrics for monitoring test execution and defect resolution to measure the progress and quality of testing1 .
NEW QUESTION # 218
What is basic idea of structure-based testing techniques?
- A. To gain time, since structure-based techniques are easier to implement than specification-based
techniques. - B. To do better testing, since the specifications are not needed.
- C. The more details of the source code are executed, the more faults can be found.
- D. To allow developers to have their own testing technique.
Answer: C
NEW QUESTION # 219
......
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.
Ultimate CTFL_Syll2018 Guide to Prepare Free Latest ISQI Practice Tests Dumps: https://pass4sure.troytecdumps.com/CTFL_Syll2018-troytec-exam-dumps.html