ISTQB CTAL-TM Practice Test - Questions Answers, Page 2

An iterative/incremental lifecycle model is a type of software development lifecycle that divides the project into smaller iterations or increments, each delivering a part of the functionality and undergoing its own planning, analysis, design, implementation, and testing phases1.This model is suitable for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it allows for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement2. Therefore, option B is the correct answer.Option A is incorrect because a spiral model is a type of iterative/incremental model that adds risk analysis and prototyping activities to each iteration3.While this model can also handle unclear requirements, new technologies, and high quality expectations, it may not be the best choice for projects that have aggressive schedules and distributed teams, as it requires more time and communication for risk assessment and prototyping4.Option C is incorrect because a V-model is a type of sequential model that maps each development phase to a corresponding testing phase in a V-shaped diagram5. This model is suitable for projects that have clear and stable requirements, well-known technologies, co-located teams, and moderate quality expectations, as it allows for early verification, traceability, and defect prevention. However, this model may not be the best choice for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it does not allow for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement. Option D is incorrect because a waterfall model is a type of sequential model that follows a linear sequence of phases from requirements to deployment. This model is suitable for projects that have simple and fixed requirements, well-known technologies, co-located teams, and low quality expectations, as it allows for easy planning, management, and documentation.However, this model may not be the best choice for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it does not allow for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement.Reference:1: ISTQB Glossary, Iterative/incremental lifecycle model2: ISTQB Advanced Level Test Manager Syllabus, Section 1.2.13: ISTQB Glossary, Spiral model4: ISTQB Advanced Level Test Manager Syllabus, Section 1.2.15: ISTQB Glossary, V-model : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Glossary, Waterfall model : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1

Performance testing is the process of determining the speed, responsiveness, and stability of a system under a given workload1.Performance testing should be started as early as possible in the software development lifecycle, preferably during unit and integration testing, to identify and resolve performance issues before they become costly or risky2.Starting performance testing early can also help to validate the performance requirements, design, and architecture of the system, as well as to optimize the performance testing strategy and scope3. Therefore, option A is the correct answer.Option B is incorrect because deferring the start of performance testing until all functional defects have been resolved can delay the detection and resolution of performance issues, increase the cost and effort of performance testing, and reduce the confidence and quality of the system4. Option C is incorrect because leveraging end users to do unit-level performance testing and automated tools for system-level performance testing can introduce inconsistency, bias, and inefficiency in the performance testing process, as well as compromise the reliability and validity of the performance test results.Option D is incorrect because requiring all performance tests to pass before starting functional testing can create unrealistic or unnecessary expectations, as well as hinder the progress and feedback of the functional testing activities.Reference:1: ISTQB Glossary, Performance Testing2: ISTQB Certified Tester - Performance Testing (CT-PT)33: ISTQB Performance Testing - TesterYou44:Performance Testing - ISTQB not-for-profit association:ISTQB - PERFORMANCE TESTING:Performance Testing - ISTQB not-for-profit association

Product risk analysis is the process of identifying and assessing the product risks that may affect the quality or functionality of the software under test1. Product risk analysis involves two primary activities: risk identification and risk assessment.Risk identification is the activity of finding, naming, and describing the risks that might affect the software under test2.Risk assessment is the activity of estimating the impact and probability of occurrence (likelihood) of the identified risks, and prioritizing them based on these factors3. Therefore, option B is the correct answer. Option A is incorrect because risk testing and risk management are not primary activities of product risk analysis, but rather activities that follow or use the results of product risk analysis.Risk testing is the activity of designing, implementing, and executing tests based on the product risk levels to reduce the level of product risks and inform stakeholders of their status4.Risk management is the activity of planning, monitoring, and controlling the risks and the risk mitigation actions in the software project5. Option C is incorrect because risk identification and risk testing are not primary activities of product risk analysis, but rather activities that are part of product risk analysis and risk-based testing respectively.Option D is incorrect because risk management and risk assessment are not primary activities of product risk analysis, but rather activities that are part of risk management and product risk analysis respectively.Reference:1: ISTQB Glossary, Product Risk Analysis2: ISTQB Glossary, Risk Identification3: ISTQB Glossary, Risk Assessment4: ISTQB Glossary, Risk-Based Testing5: ISTQB Glossary, Risk Management :Product Risk Analysis (PRA) | TMap:Risk-Based Testing | ISTQB Glossary:Risk Analysis | ISTQB Glossary

Fault Tree Analysis (FTA) is a technique used to analyze the causes of faults (defects).The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose1.FTA can help to determine the root cause of observed and potential failures by tracing back the fault events to their initiating causes and identifying the combinations of events that can lead to the fault occurrence2. Therefore, option A is the correct answer. Option B is incorrect because FTA is not used to select the pairs of items to be used in pairwise testing, which is a technique to generate test cases based on the combinations of two input parameters. Option C is incorrect because FTA is not a formal technique used to identify the likely effects of risks, which are uncertain events or conditions that may have a positive or negative impact on the project objectives.Option D is incorrect because FTA is not used to target defect-based testing, which is a testing technique that uses information about the types, causes, and locations of defects discovered in previous projects to guide the selection, creation, and prioritization of test cases.Reference:1: Fault Tree Analysis | ISTQB Glossary2:Fault Tree Analysis (FTA) - Software Testing Genius: ISTQB Glossary, Pairwise Testing : ISTQB Glossary, Risk : ISTQB Glossary, Defect-Based Test Technique :Fault Tree Analysis (FTA) - Software Testing Genius:Fault Tree Analysis | ISTQB Glossary

A model-based testing strategy is a testing strategy that uses models to represent the desired behavior and structure of the system under test, and to derive test cases, test data, test procedures, and test oracles1. A model-based testing strategy requires an activity to select an appropriate quality standard, such as ISO 9126, to be used to guide the testing.A quality standard is a set of criteria, guidelines, or characteristics that define the quality attributes of a software product, such as functionality, reliability, usability, efficiency, maintainability, and portability2.A quality standard can help to define the quality requirements, objectives, and measures for the system under test, and to evaluate the quality of the test results and the test process3. Therefore, option C is the correct answer. Option A is incorrect because conducting a quality risk analysis with all affected stakeholders is not an activity specific to a model-based testing strategy, but rather a general testing activity that can be applied to any testing strategy.A quality risk analysis is a process of identifying and assessing the quality risks that may affect the system under test, and prioritizing them based on their impact and likelihood4. Option B is incorrect because conducting operational profiling to determine the expected usage of the system is not an activity specific to a model-based testing strategy, but rather an activity related to a usage-based testing strategy. An operational profile is a statistical representation of the relative frequencies of the inputs, operations, and operating conditions of a system in its operational environment. Option D is incorrect because creating the test charters for the exploratory testing sessions is not an activity specific to a model-based testing strategy, but rather an activity related to an exploratory testing strategy.A test charter is a document that defines the scope, objective, and approach of an exploratory testing session.Reference:1: ISTQB Glossary, Model-Based Testing2: ISTQB Glossary, Quality Standard3: ISTQB Advanced Level Test Manager Syllabus, Section 1.3.14: ISTQB Glossary, Quality Risk Analysis : ISTQB Glossary, Operational Profile : ISTQB Glossary, Test Charter :Model-Based Tester - ISTQB not-for-profit association:ISTQB Model-Based Testing Certification - ISTQB Exams Worldwide - ISTQB ...:ISTQB - ABOUT MODEL-BASED TESTER EXT.:ISTQB Certified Tester -- Model-Based Tester (CT-MBT)

A test estimate is an approximation of the amount of effort, time, and resources required to perform testing activities for a software project1.A test estimate can be influenced by various factors, such as the size, complexity, and quality of the software, the scope, objectives, and approach of the testing, the skills, experience, and availability of the test team, the tools, methods, and standards used for testing, and the constraints, risks, and assumptions related to the project2. One of the factors that is likely to increase the test estimate is the use of a new technology.A new technology is a technology that is unfamiliar or unproven to the test team or the organization, such as a new programming language, framework, platform, or tool3. The use of a new technology can increase the test estimate because it may require more time and effort to learn, understand, and apply the technology, as well as to deal with potential issues, challenges, or limitations that may arise from the technology. Therefore, option A is the correct answer. Option B is incorrect because a requirement for high level test documentation is not a factor that is likely to increase the test estimate, but rather a factor that is likely to increase the test documentation effort. Test documentation is the set of documents that describe the test basis, test objectives, test design, test procedures, test results, and test evaluation of a software project. A requirement for high level test documentation means that the test documents need to be detailed, comprehensive, and consistent, which may require more time and effort to produce, review, and maintain. However, this does not necessarily affect the test estimate, as the test documentation effort can be considered as a separate or parallel activity to the test execution effort. Option C is incorrect because assigned personnel who are experienced on working with similar projects in similar environments is not a factor that is likely to increase the test estimate, but rather a factor that is likely to decrease the test estimate. Experienced personnel are personnel who have the relevant knowledge, skills, and abilities to perform the testing activities for a software project. Assigned personnel who are experienced on working with similar projects in similar environments can decrease the test estimate because they may require less time and effort to understand, design, implement, and execute the tests, as well as to deal with potential issues, challenges, or limitations that may arise from the project. Option D is incorrect because static test data is not a factor that is likely to increase the test estimate, but rather a factor that is likely to decrease the test estimate. Test data is the data that is used as input or output for the tests. Static test data is test data that is fixed and predefined, and does not change during the test execution.Static test data can decrease the test estimate because it may require less time and effort to create, manage, and maintain, as well as to ensure the validity, reliability, and traceability of the test data.Reference:1: ISTQB Glossary, Test Estimate2: ISTQB Advanced Level Test Manager Syllabus, Section 3.1.13:What is New Technology? - Definition from Techopedia:The Impact of New Technologies on Software Testing: ISTQB Glossary, Test Documentation : ISTQB Glossary, Experienced-Based Test Technique : ISTQB Glossary, Test Data : ISTQB Glossary, Static Test Data :Test Manager - ISTQB not-for-profit association: [ISTQB Foundation Level #38 -- Test Estimation Techniques - Software Testing Mentor] : [What are the estimation techniques in software testing?]

Defect density is a testing metric that measures the number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g., lines-of-code, number of classes or function points)1.Defect density is a product metric, as it evaluates the quality or reliability of a software product2. Therefore, option B is the correct answer.Option A is incorrect because project metrics are metrics that measure the characteristics of the software project, such as cost, schedule, effort, scope, or resources3. Option C is incorrect because process metrics are metrics that measure the characteristics of the software process, such as effectiveness, efficiency, productivity, or maturity.Option D is incorrect because people metrics are metrics that measure the characteristics of the software personnel, such as skills, experience, motivation, or satisfaction.Reference:1: Defect Density | ISTQB Glossary2:Software Testing Metrics: What is, Types & Example3: [Project Metrics - Software Testing Fundamentals] : [Process Metrics - Software Testing Fundamentals] : [People Metrics - Software Testing Fundamentals]

A distributed model for testing is a testing model that involves testers working in different locations, time zones, or organizations, such as onshore, offshore, or nearshore1.The primary factor that you should consider with this model is the alignment of methodologies, which means that the testers follow the same or compatible testing processes, standards, tools, and techniques, regardless of their location, time zone, or organization2.The alignment of methodologies can help to ensure the consistency, quality, and efficiency of the testing activities, as well as to facilitate the communication, coordination, and collaboration among the testers3. Therefore, option A is the correct answer. Option B is incorrect because co-location of test team is not a factor that you should consider with a distributed model for testing, but rather a factor that is contrary to a distributed model for testing.Co-location of test team means that the testers work in the same physical location, which can have some advantages, such as easier communication, faster feedback, and stronger team spirit, but also some disadvantages, such as higher costs, limited resources, and less diversity4. Option C is incorrect because provision of growth opportunities for the individual testers is not a factor that you should consider with a distributed model for testing, but rather a factor that is relevant to any testing model. Provision of growth opportunities for the individual testers means that the testers are given the chance to learn new skills, gain new experiences, and advance their careers, which can have some benefits, such as increased motivation, productivity, and retention of the testers. Option D is incorrect because planned vs. actual hours is not a factor that you should consider with a distributed model for testing, but rather a factor that is relevant to any testing model. Planned vs.actual hours is a testing metric that compares the estimated and the actual effort spent on the testing activities, which can help to measure the accuracy of the test estimation, the efficiency of the test execution, and the variance of the test schedule.Reference:1: ISTQB Glossary, Distributed Testing2:Distributed Testing - Software Testing Fundamentals3: ISTQB Advanced Level Test Manager Syllabus, Section 3.2.14:Co-located vs. Distributed Teams: What's the Difference?:How to Provide Growth Opportunities for Employees:Software Testing Metrics: What is, Types & Example

An analytical test strategy is a test strategy that is based on the analysis of the factors that affect the quality of the software under test, such as the requirements, the risks, the complexity, or the criticality1.An analytical test strategy uses these factors to define the test objectives, scope, approach, and techniques, as well as to prioritize and allocate the test resources2. Reporting the test results as ''Requirements tested, passed, and failed'' implies that the testing is driven by the requirements, which are the specifications of the desired features and functions of the software under test. Testing based on the requirements is an example of an analytical test strategy, as it uses the requirements as the main factor to guide the testing activities. Therefore, option C is the correct answer. Option A is incorrect because a model-based test strategy is a test strategy that uses models to represent the desired behavior and structure of the software under test, and to derive test cases, test data, test procedures, and test oracles. A model-based test strategy does not necessarily report the test results as ''Requirements tested, passed, and failed'', as it may use other types of models, such as state diagrams, data flow diagrams, or decision tables, to generate and execute the tests. Option B is incorrect because an exploratory test strategy is a test strategy that uses the tester's knowledge, skills, and creativity to design and execute tests dynamically, without predefined test cases or test procedures. An exploratory test strategy does not report the test results as ''Requirements tested, passed, and failed'', as it does not follow a formal or structured testing process, but rather relies on the tester's intuition, experience, and feedback. Option D is incorrect because a reactive test strategy is a test strategy that uses the actual behavior and results of the software under test to design and execute tests, without prior knowledge or documentation of the software.A reactive test strategy does not report the test results as ''Requirements tested, passed, and failed'', as it does not have any requirements or specifications to compare the software against, but rather uses the software itself as the test basis.Reference:1: ISTQB Glossary, Analytical Test Strategy2: ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : ISTQB Glossary, Requirement : ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : ISTQB Glossary, Model-Based Testing : ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : ISTQB Glossary, Exploratory Testing : ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : ISTQB Glossary, Reactive Test Strategy : ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 :Test Strategy | ISTQB Glossary:Test Strategy - ISTQB not-for-profit association