Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ISTQB CTAL-TM Exam - Topic 3 Question 18 Discussion

Your last project was released three months ago and used a risk-based approach. In production, a number of serious failures in low risk areas have occurred.What is the most important lesson to be learned from this information? [2]
B) A broader cross-functional team should contribute to the risk analysis.
A) The 'lessons learned' session should have been conducted prior to deployment.
C) The project manager should have set stakeholder expectations for serious failures.
D) Future projects should test the lower risk areas first.

ISTQB CTAL-TM Exam - Topic 3 Question 18 Discussion

Actual exam question for ISTQB's CTAL-TM exam
Question #: 18
Topic #: 3
[All CTAL-TM Questions]

Your last project was released three months ago and used a risk-based approach. In production, a number of serious failures in low risk areas have occurred.

What is the most important lesson to be learned from this information? [2]

Show Suggested Answer Hide Answer
Suggested Answer: B

The most important lesson to be learned from this information is that a broader cross-functional team should contribute to the risk analysis. This is because the risk analysis is the process of identifying, assessing, and prioritizing the risks that may affect the quality of the system, and allocating testing resources accordingly. A broader cross-functional team can provide different perspectives, expertise, and experience to the risk analysis, and help to identify and evaluate the risks more accurately and comprehensively. This can reduce the likelihood of overlooking or underestimating some risks, and improve the effectiveness and efficiency of the risk-based testing approach.Risk Analysis - ISTQB not-for-profit associationReference:Certified Tester Advanced Level Test Manager (CTAL-TM) - ISTQB not-for-profit association,ISTQB Test Manager Certification - ISTQB Exams Worldwide - ISTQB Official Registration,Risk Analysis - ISTQB not-for-profit association


by Cherri at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium CTAL-TM Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Charlette
2 months ago
D could help. Testing low-risk areas first might prevent failures.
upvoted 0 times
...
Pete
2 months ago
C makes sense. Stakeholders need to know potential issues.
upvoted 0 times
...
Mireya
3 months ago
I feel A is crucial. We should learn before going live.
upvoted 0 times
...
Mignon
3 months ago
I think B is key. More perspectives can catch risks.
upvoted 0 times
...
Trinidad
3 months ago
Lessons learned should happen after, not before!
upvoted 0 times
...
Ashleigh
3 months ago
Testing lower risk areas first seems like a no-brainer.
upvoted 0 times
...
Erinn
3 months ago
Surprised that low-risk areas failed so badly!
upvoted 0 times
...
Beata
3 months ago
I think setting stakeholder expectations is key here.
upvoted 0 times
...
Yaeko
4 months ago
Definitely need a broader team for risk analysis.
upvoted 0 times
...
Shonda
4 months ago
I bet the risk analysis team was just a bunch of coin-flippers.
upvoted 0 times
...
Cherelle
4 months ago
Haha, the project manager should have just used a crystal ball to predict the future!
upvoted 0 times
...
Earnestine
5 months ago
C) The project manager should have set stakeholder expectations for serious failures.
upvoted 0 times
...
Leonida
5 months ago
D) Future projects should test the lower risk areas first.
upvoted 0 times
...
Kanisha
5 months ago
B) A broader cross-functional team should contribute to the risk analysis.
upvoted 0 times
...
Arlean
5 months ago
I feel like C is important too, but setting expectations might not directly address the failures we saw. I wish we had more examples to clarify this.
upvoted 0 times
...
Beckie
5 months ago
I’m a bit confused; I thought the lessons learned session was crucial, so A might be the answer. But then again, it could be too late to do that after deployment.
upvoted 0 times
...
Hoa
5 months ago
I think D makes sense because testing lower risk areas first could prevent serious failures. I feel like we practiced a similar question on prioritizing testing.
upvoted 0 times
...
Noble
6 months ago
I remember discussing how risk analysis should involve more perspectives, so B seems relevant. But I'm not entirely sure if that's the most important lesson.
upvoted 0 times
...
Lorean
6 months ago
I think the answer is B. A broader cross-functional team could have provided more diverse perspectives and caught those low-risk failures during the risk analysis. The other options don't seem to address the core issue as directly.
upvoted 0 times
...
Sheron
6 months ago
I'm a bit confused. Why would testing the lower risk areas first be the solution? Wouldn't that just delay addressing the actual issues? I'm stuck between B and C, but I'm not sure which one is the best answer.
upvoted 0 times
...
Ernie
6 months ago
I feel pretty confident about this one. The most important lesson is that the project manager should have set better stakeholder expectations. The failures in low-risk areas show that the risk analysis was flawed.
upvoted 0 times
...
Meghan
6 months ago
Okay, let's think this through. The key seems to be that serious failures occurred in low-risk areas, even though a risk-based approach was used. I'm leaning towards option B - a broader team could have helped identify more risks.
upvoted 0 times
...
Elizabeth
7 months ago
Hmm, this is a tricky one. I'm not sure if I fully understand the question. Maybe I should re-read it a few times to make sure I'm not missing anything.
upvoted 0 times
Lou
11 days ago
I agree, a broader team could help spot issues earlier.
upvoted 0 times
...
Adelle
16 days ago
Yeah, low risk doesn't mean no risk!
upvoted 0 times
...
Carline
2 months ago
This really makes you think about risk assessment.
upvoted 0 times
...
...

Save Cancel