A test manager often relies on experience with similar projects to foresee risks related to technical complexity, domain challenges, or previous defects.
Other options listed are less effective for comprehensive risk identification.
Evaluation of Options:
A(Lines of code) andB(Function points) are quantitative measures, not directly tied to risk identification.
Cis correct as past experience is crucial for identifying risks early.
D(Record/playback tools) is irrelevant to risk analysis.
References and Syllabus Alignment:
Risk identification techniques are discussed under "Risk Management" (TM-1.3.1).
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit