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

ASTQB CTFL Exam - Topic 2 Question 41 Discussion

Posted by Virgina on Mar 22, 2023 at 06:52 PM

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

Suggested Answer: B

Get Premium CTFL Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
45 comments · newest first
FE
Felton 12 months ago
Wait, Error Guessing? Really? That seems risky!
CA
Carin 1 year ago
Not sure about Exploratory Testing for this. Seems too random.
LA
Lanie 1 year ago
Boundary Value Analysis could also work well here.
UL
Ula 1 year ago
Totally agree, it helps in complex scenarios!
TE
Terrilyn 1 year ago
I think Decision Table Testing is solid for risk mitigation.
TA
Tamesha 1 year ago
Error Guessing seems like it could work too, especially if we want to identify potential issues quickly without formal test cases.
KA
Kasandra 1 year ago
I feel like Boundary Value Analysis is more structured and might not align well with the fast-paced nature of RAD.
LO
Loren 1 year ago
I'm not entirely sure, but I think Decision Table Testing might be useful for managing complex scenarios in a RAD environment.
BA
Barrett 1 year ago
I remember we discussed how RAD focuses on quick iterations, so maybe Exploratory Testing could be a good fit since it allows for flexibility and quick feedback.
PA
Paris 1 year ago
I'm a bit confused by the different options here. Do we really need to store the PII data separately in a Cloud Storage bucket, as suggested in option B? That seems like an unnecessary complication. I'm leaning towards option A as well, since it seems the most direct way to remove the PII while still processing the data.
EA
Earleen 1 year ago
Ah, I think I've got it! The watch diff command allows you to automatically reissue a CLI command and see the differences from the last time it was run. That sounds really useful for troubleshooting and monitoring.
KA
Kanisha 1 year ago
I think Drucker is most closely associated with MBO, but I'm not completely sure.
JU
Justa 2 years ago
I'm going to guess... Error Guessing! Because that's the only way I'm passing this exam.
LE
Leandro 1 year ago
↳ replying to Justa
D) Exploratory Testing
RU
Rupert 1 year ago
↳ replying to Justa
C) Error Guessing
KA
Kanisha 1 year ago
↳ replying to Justa
B) Boundary Value Analysis
YV
Yvette 1 year ago
↳ replying to Justa
A) Decision Table Testing
TA
Tammi 2 years ago
Decision Table Testing? What is this, the 90s? Gotta go with the more agile Exploratory approach.
KE
Keva 1 year ago
↳ replying to Tammi
Exploratory Testing allows for more flexibility and adaptability.
TA
Tamar 1 year ago
↳ replying to Tammi
I think Error Guessing could also be a good option in this case.
EL
Eloisa 1 year ago
↳ replying to Tammi
Yeah, Decision Table Testing seems a bit outdated.
MA
Malcom 1 year ago
↳ replying to Tammi
I agree, Exploratory Testing is definitely more agile.
NA
Nan 1 year ago
↳ replying to Tammi
I think we should go with Exploratory Testing for this project.
GL
Glen 1 year ago
↳ replying to Tammi
Exploratory Testing allows for more flexibility.
ST
Stephen 1 year ago
↳ replying to Tammi
Yeah, Decision Table Testing seems outdated.
ME
Melynda 1 year ago
↳ replying to Tammi
I agree, Exploratory Testing is definitely more agile.
MA
Markus 2 years ago
I prefer Error Guessing, as it helps uncover unexpected defects.
LU
Luis 2 years ago
I agree with Bulah, Exploratory Testing allows for flexibility and adaptability.
RO
Rosita 2 years ago
Error Guessing? More like Error Hoping! But seriously, Exploratory Testing is the way to play this one.
MO
Moon 1 year ago
↳ replying to Rosita
I agree, Exploratory Testing allows for flexibility and adaptability in testing.
SA
Samira 1 year ago
↳ replying to Rosita
Exploratory Testing is definitely the way to go in this situation.
XU
Xuan 1 year ago
↳ replying to Rosita
D) Exploratory Testing
CH
Cherri 1 year ago
↳ replying to Rosita
C) Error Guessing
TA
Tarra 1 year ago
↳ replying to Rosita
B) Boundary Value Analysis
TI
Tiera 1 year ago
↳ replying to Rosita
A) Decision Table Testing
PR
Precious 2 years ago
I'm leaning towards Boundary Value Analysis. Seems like a good fit to identify edge cases in the changing requirements.
BU
Bulah 2 years ago
I think Exploratory Testing would be most appropriate.
PA
Paz 2 years ago
Hmm, Exploratory Testing seems like the way to go here. It's perfect for the iterative nature of RAD development.
MA
Maurine 1 year ago
↳ replying to Paz
I think we should go with Exploratory Testing for this scenario.
ST
Staci 1 year ago
↳ replying to Paz
D) Exploratory Testing is definitely the best choice for RAD projects.
GL
Glendora 1 year ago
↳ replying to Paz
I agree, Exploratory Testing allows for flexibility and adaptability in RAD development.
DE
Detra 1 year ago
↳ replying to Paz
D) Exploratory Testing
SH
Sharita 1 year ago
↳ replying to Paz
C) Error Guessing
JO
Joni 1 year ago
↳ replying to Paz
B) Boundary Value Analysis
MA
Margret 1 year ago
↳ replying to Paz
A) Decision Table Testing
0/2000 characters

Save Cancel