Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ASTQB Exam CTFL Topic 2 Question 41 Discussion

Actual exam question for ASTQB's CTFL exam
Question #: 41
Topic #: 2
[All CTFL Questions]

As a result of the RAD based development approach, the test manager has decided to change the risk mitigation approach. Which test technique might be most appropriate to use? 2 credits

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Justa
2 months ago
I'm going to guess... Error Guessing! Because that's the only way I'm passing this exam.
upvoted 0 times
Leandro
3 days ago
D) Exploratory Testing
upvoted 0 times
...
Rupert
4 days ago
C) Error Guessing
upvoted 0 times
...
Kanisha
13 days ago
B) Boundary Value Analysis
upvoted 0 times
...
Yvette
1 months ago
A) Decision Table Testing
upvoted 0 times
...
...
Tammi
2 months ago
Decision Table Testing? What is this, the 90s? Gotta go with the more agile Exploratory approach.
upvoted 0 times
Malcom
9 hours ago
I agree, Exploratory Testing is definitely more agile.
upvoted 0 times
...
Nan
2 days ago
I think we should go with Exploratory Testing for this project.
upvoted 0 times
...
Glen
5 days ago
Exploratory Testing allows for more flexibility.
upvoted 0 times
...
Stephen
9 days ago
Yeah, Decision Table Testing seems outdated.
upvoted 0 times
...
Melynda
1 months ago
I agree, Exploratory Testing is definitely more agile.
upvoted 0 times
...
...
Markus
2 months ago
I prefer Error Guessing, as it helps uncover unexpected defects.
upvoted 0 times
...
Luis
2 months ago
I agree with Bulah, Exploratory Testing allows for flexibility and adaptability.
upvoted 0 times
...
Rosita
2 months ago
Error Guessing? More like Error Hoping! But seriously, Exploratory Testing is the way to play this one.
upvoted 0 times
Moon
25 days ago
I agree, Exploratory Testing allows for flexibility and adaptability in testing.
upvoted 0 times
...
Samira
26 days ago
Exploratory Testing is definitely the way to go in this situation.
upvoted 0 times
...
Xuan
30 days ago
D) Exploratory Testing
upvoted 0 times
...
Cherri
1 months ago
C) Error Guessing
upvoted 0 times
...
Tarra
1 months ago
B) Boundary Value Analysis
upvoted 0 times
...
Tiera
1 months ago
A) Decision Table Testing
upvoted 0 times
...
...
Precious
2 months ago
I'm leaning towards Boundary Value Analysis. Seems like a good fit to identify edge cases in the changing requirements.
upvoted 0 times
...
Bulah
2 months ago
I think Exploratory Testing would be most appropriate.
upvoted 0 times
...
Paz
2 months ago
Hmm, Exploratory Testing seems like the way to go here. It's perfect for the iterative nature of RAD development.
upvoted 0 times
Maurine
11 days ago
I think we should go with Exploratory Testing for this scenario.
upvoted 0 times
...
Staci
13 days ago
D) Exploratory Testing is definitely the best choice for RAD projects.
upvoted 0 times
...
Glendora
14 days ago
I agree, Exploratory Testing allows for flexibility and adaptability in RAD development.
upvoted 0 times
...
Detra
14 days ago
D) Exploratory Testing
upvoted 0 times
...
Sharita
21 days ago
C) Error Guessing
upvoted 0 times
...
Joni
22 days ago
B) Boundary Value Analysis
upvoted 0 times
...
Margret
1 months ago
A) Decision Table Testing
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77