CTAL-TM
Free CTAL-TM practice questions
10 questions from our CTAL-TM practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Managing the Test Activities
An organisation's test policy states that testing must provide independent, objective information about product quality. A project manager proposes that developers perform all testing, including acceptance testing, to save cost. What should the test manager do FIRST?
- AEscalate immediately to senior management and suspend test planning until the project manager withdraws the proposal
- BAgree, but ask developers to swap modules with each other so that every developer reviews code they did not write
- CPoint out the conflict with the test policy and propose a strategy that keeps suitable independence at the higher test levels Correct answer
- DAccept the proposal, because test independence only matters in safety-critical projects and the test policy is guidance rather than binding
Answer and explanation: The project test strategy must align with the organisation's test policy, so the test manager should show the conflict and propose a strategy with suitable independence, for example independent testers for system and acceptance testing. Treating the policy as optional ignores the organisational level that governs projects. Escalating and halting planning skips the first step of discussing the conflict. Swapping modules between developers adds a little independence but still conflicts with the policy for acceptance testing.
Question 2 of 10, Managing the Test Activities
A test manager on a regulated medical-device project must show auditors that every safety requirement has been covered by at least one executed test and that each failed test is linked to a defect report. Which test management practice BEST provides this evidence?
- ARunning an exploratory testing session per safety requirement and archiving the signed session sheets in the project repository afterwards
- BPublishing a weekly test progress report that lists the percentage of test cases passed per test level
- CAdopting a regression-averse test strategy so that all safety tests are re-executed in every build
- DMaintaining bidirectional traceability between the test basis, test cases, test results and defect reports Correct answer
Answer and explanation: Bidirectional traceability links requirements to tests, results and defects, so coverage of each safety requirement and the defect behind each failure can be demonstrated in both directions. A pass-rate report shows progress but not per-requirement coverage. Session sheets document exploration but do not systematically prove coverage of every requirement. A regression-averse strategy addresses re-execution, not the audit link between requirements, results and defects.
Question 3 of 10, Managing the Test Activities
A product team moves from a yearly sequential release cycle to two-week iterations with continuous integration. Which change to test management is MOST appropriate?
- AKeeping a single master test plan approved at project start and running one system test phase before every yearly release
- BReplacing exit criteria with a fixed number of exploratory testing hours that is negotiated separately for each sprint
- CPlanning per iteration under a lightweight release test plan, with automated regression tests in the CI pipeline Correct answer
- DMoving all test analysis and design to a separate test team that starts after the final iteration has been completed
Answer and explanation: In iterative development, test planning is done at release and iteration level, and fast feedback relies on automated regression tests in the CI pipeline. A single upfront master plan with one final system test phase reflects the sequential model being abandoned. Starting test work after the last iteration delays feedback and contradicts iterative delivery. Exploratory hours can complement, but they do not replace a definition of done or exit criteria.
Question 4 of 10, Managing the Test Activities
A test manager wants an improvement approach that compares the organisation's test process with a predefined set of maturity levels and key process areas, so that the organisation can be certified at a level. Which approach fits BEST?
- AA retrospective held at the end of each iteration
- BA process reference model such as TMMi Correct answer
- CThe Goal-Question-Metric approach applied to testing
- DCausal analysis of defects found in production
Answer and explanation: TMMi is a process reference model with staged maturity levels and process areas, and organisations can be formally assessed against it. Causal analysis is an analytical approach that improves based on the organisation's own problems rather than a reference model. Retrospectives provide team-level lessons learned but no maturity levels. GQM defines measurements for goals and is also an analytical approach without maturity levels.
Question 5 of 10, Managing the Test Activities
A test manager is preparing a product risk workshop for a new online banking feature. Which participant group is MOST important to include so that the impact of failures is assessed realistically?
- AOnly the test analysts, because they will design the tests that mitigate the identified risks
- BExternal auditors, because they will review the risk register after the release is complete
- COnly the developers who wrote the code, because they know where the code is most complex
- DBusiness representatives and users who understand the consequences of failures for customers Correct answer
Answer and explanation: Impact is a business consequence, so business stakeholders and users are essential for assessing it, while technical staff mainly contribute to likelihood. Developers alone know complexity, which is a likelihood factor, but miss business impact. Test analysts alone lack the business perspective. Auditors may review the process later but are not the best source for assessing the impact of failures.
Question 6 of 10, Managing the Product
Two components of similar size were tested with similar effort. Component A had 12 defects in system testing and 1 in production; component B had 3 in system testing and 9 in production. What does this data MOST likely indicate?
- AB has fewer defects overall, so its quality is clearly higher than that of A
- BTesting of B was much less effective, so its test approach should be analysed Correct answer
- CBoth components were tested equally well, since the effort spent was the same
- DA has more defects, so it needs a higher share of the next testing budget
Answer and explanation: A's testing detected about 92% of its known defects before release (12 of 13), B's only 25% (3 of 12), so testing of B was much less effective and its approach should be analysed. B's total of 12 known defects is similar to A's 13, so B is not clearly of higher quality, and most of its defects reached users. Giving more budget to A ignores where defects are escaping. Equal effort does not mean equal effectiveness.
Question 7 of 10, Managing the Product
A tester reports a defect, a developer rejects it as 'works as designed', and the requirement turns out to be ambiguous. What should the defect management process ensure in this case?
- AThe tester reopens the defect repeatedly until the developer changes the code to match the tester's own interpretation
- BThe defect is closed as rejected, because the developer decides whether behaviour is correct for the code they implemented
- CThe report goes to the requirement owner, who clarifies the expected behaviour before the defect is closed or fixed Correct answer
- DThe defect is deleted from the tool so that the defect metrics for the iteration are not distorted by invalid reports
Answer and explanation: When disagreement stems from an ambiguous requirement, the owner of the test basis must clarify the expected result, and the defect state then follows from that decision. Letting the developer decide alone removes the business perspective. Repeated reopening escalates a conflict without resolving the ambiguity. Deleting reports destroys information that is valuable for process improvement and the audit trail.
Question 8 of 10, Managing the Product
A test manager estimated 40 days for system testing based on 200 test cases. Halfway through, 100 test cases have taken 28 days because the test environment was unstable. The environment is now fixed. What is the BEST revised estimate for the remaining work?
- ANo estimate is possible until all test cases have been executed and the actual effort is known
- BAbout 20 days, assuming the planned rate is achievable now that the environment is fixed, while monitoring the actual rate Correct answer
- CAbout 12 days, because the team should make up the delay by working faster on the second half
- DAbout 28 days, because extrapolating from the actual rate measured so far is always the most accurate basis for the remaining estimate
Answer and explanation: The planned rate was 0.2 days per test case; since the cause of the slower rate has been removed, about 20 days is reasonable for the remaining 100 tests, while monitoring confirms the assumption. Pure extrapolation would carry over a cause that no longer applies. Expecting faster-than-planned work to recover the delay is not based on evidence. Estimates are needed during the project for control decisions.
Question 9 of 10, Managing the Team
A company's support costs for production failures in a customer portal have doubled. The test manager proposes investing in requirements reviews and earlier testing. In cost of quality terms, what is the proposal intended to do?
- AIncrease internal failure costs to reduce prevention costs
- BReduce appraisal costs by shifting all testing to the users after release
- CReduce prevention costs so that more budget is available for support
- DIncrease prevention and appraisal costs to reduce external failure costs Correct answer
Answer and explanation: Reviews and early testing are prevention and appraisal (detection) investments that aim to reduce the much higher cost of failures found by customers, which are external failure costs. Raising internal failure costs is a consequence of finding more defects before release, not the goal. Shifting testing to users after release increases external failure costs. Cutting prevention would worsen the problem.
Question 10 of 10, Managing the Team
A test manager must report to several stakeholders: the project sponsor, the development lead and the test team. Which approach to test reporting is MOST appropriate?
- AReport only to the project sponsor, who is then responsible for passing the relevant information on to the other stakeholders
- BReport only when exit criteria are met, so that stakeholders are not confused by incomplete or preliminary test information
- CTailor content and detail to each audience, such as release readiness and risk for the sponsor and defect details for development Correct answer
- DSend the same detailed technical report to all stakeholders so that everyone has identical information about every defect and test case
Answer and explanation: Effective communication adapts content and detail to each audience's needs: sponsors need risk and readiness, while development leads need defect specifics. A single detailed report overwhelms some readers and buries key information. Relying on the sponsor to relay information is slow and loses detail. Reporting only at completion denies stakeholders timely information for decisions.