A dynamic analysis tool is the most effective tool for detecting memory leaks, which are defects where a code component fails to release memory after it has finished using it.A dynamic analysis tool monitors the behaviour of the software under test during execution and can measure memory usage, identify memory allocation errors, and report memory leaks13. The other options are not relevant tools for detecting memory leaks.A monitoring tool can measure the performance and resource consumption of the software under test, but it cannot identify memory leaks specifically13.A configuration management tool is used to manage the versions and changes of the software under test and its related artefacts, but it has nothing to do with memory leaks1.A coverage measurement tool is used to measure how much of the code or functionality of the software under test has been exercised by the test cases, but it cannot detect memory leaks1.

The level of risk is determined by multiplying the impact of an adverse event by the likelihood of that event occurring1.The impact of an adverse event is the degree of harm or loss that would result from the event, such as financial loss, reputation damage, legal consequences, or safety hazards1.The likelihood of an adverse event is the probability or frequency of the event happening, based on historical data, expert judgement, or statistical analysis1. The other options are not correct formulas for calculating risk. Option A confuses the cost of preventing an adverse event with its impact. Option B confuses the cost of possible legal action with its likelihood. Option D uses two synonyms for likelihood (probability and frequency) instead of combining it with impact.

The percentage of planned test cases designed is not a common metric used for monitoring test preparation and execution, because it does not reflect the quality or completeness of the test cases or their alignment with the test objectives1. The other options are common metrics used for monitoring test preparation and execution.The number of test cases passed and failed indicates the quality and status of the software under test1.The number of test plan review comments indicates the quality and completeness of the test plan document1.The percentage of tasks complete in test environment preparation indicates the progress and readiness of the test environment1.

Test Cases 1, 2 and 3 are all valid, because they cover all the possible combinations of conditions and actions in the decision table. Test Case 1 covers the case where the employee is not a car or motorcycle driver, which leads to the action of not allowing the expense claim. Test Case 2 covers the case where the employee drives a diesel car with an engine size greater than 1600cc, which leads to the action of accepting the expense claim at band C.Test Case 3 covers the case where the employee rides a motorcycle, which leads to the action of accepting the expense claim at band A12.

Providing support for the test team using the tool is a key success factor in tool deployment, because it helps to overcome any resistance or difficulties that the test team may face when using the new tool.Support can include training, coaching, mentoring, troubleshooting, and feedback mechanisms13. The other options are not key success factors in tool deployment, but rather in tool selection or evaluation.Option A is related to tool selection, where a cost-benefit ratio can help to justify the investment in a new tool13.Option B is related to tool evaluation, where a pilot project can help to determine whether the expected benefits of the tool can be achieved at reasonable cost13.Option D is also related to tool evaluation, where an assessment of organisational maturity, strengths and weaknesses can help to identify the suitability and readiness of the organisation for using a new tool13.

The test execution schedule that meets the test plan requirements and logical dependencies is e, a, d, c, b. This schedule follows the order of re-tests first (e), followed by the highest priority tests (a and d), and then creates test data for subsequent tests (c and b).This schedule also respects the logical dependencies, as test case a creates an admin user, which is necessary for test case d to create a standard user, which is necessary for test cases c and b to perform other actions1.

The introduction of a test management tool does not represent one of the three triggers for maintenance testing an operational system, because it does not affect the functionality or performance of the system itself.Maintenance testing is triggered by system modification (such as corrective, adaptive, perfective or preventive changes), data migration (such as moving data from one platform or format to another), or system retirement (such as decommissioning or replacing an old system)1.

Load testing is the type of non-functional testing that would verify these requirements, because it measures how well the system performs under normal or expected load conditions1.Load testing can verify whether up to 100 users can carry out a transaction simultaneously and whether the response time is within 5 seconds1. The other options are not relevant types of non-functional testing for these requirements.Stress testing measures how well the system performs under extreme or abnormal load conditions1.Maintenance testing verifies whether an operational system still works correctly after changes or updates1.Usability testing evaluates how easy and user-friendly the system is for its intended users1.

If the fault in the code is contained in a small area, then it may cause the system to fail under certain circumstances, resulting in a defect1. However, this is not a definite consequence, as it depends on whether the fault is executed or not. The other options are not definite consequences of this mistake either.Option A assumes that the system will always fail because of the fault, which may not be true if the fault is never executed or does not affect critical functionality1.Option C assumes that there will be negative impacts on money, time, or business reputation because of the fault, which may not be true if the defect is minor or does not affect important stakeholders1.Option D assumes that contractual requirements have not been met by testing because of the fault, which may not be true if testing has fulfilled its objectives and scope according to the contract1.