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

ASTQB CTFL Exam - 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

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

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Felton
4 months ago
Wait, Error Guessing? Really? That seems risky!
upvoted 0 times
...
Carin
5 months ago
Not sure about Exploratory Testing for this. Seems too random.
upvoted 0 times
...
Lanie
5 months ago
Boundary Value Analysis could also work well here.
upvoted 0 times
...
Ula
5 months ago
Totally agree, it helps in complex scenarios!
upvoted 0 times
...
Terrilyn
5 months ago
I think Decision Table Testing is solid for risk mitigation.
upvoted 0 times
...
Tamesha
5 months ago
Error Guessing seems like it could work too, especially if we want to identify potential issues quickly without formal test cases.
upvoted 0 times
...
Kasandra
5 months ago
I feel like Boundary Value Analysis is more structured and might not align well with the fast-paced nature of RAD.
upvoted 0 times
...
Loren
5 months ago
I'm not entirely sure, but I think Decision Table Testing might be useful for managing complex scenarios in a RAD environment.
upvoted 0 times
...
Barrett
5 months 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.
upvoted 0 times
...
Paris
6 months 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.
upvoted 0 times
...
Earleen
6 months 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.
upvoted 0 times
...
Kanisha
6 months ago
I think Drucker is most closely associated with MBO, but I'm not completely sure.
upvoted 0 times
...
Justa
11 months ago
I'm going to guess... Error Guessing! Because that's the only way I'm passing this exam.
upvoted 0 times
Leandro
9 months ago
D) Exploratory Testing
upvoted 0 times
...
Rupert
9 months ago
C) Error Guessing
upvoted 0 times
...
Kanisha
9 months ago
B) Boundary Value Analysis
upvoted 0 times
...
Yvette
10 months ago
A) Decision Table Testing
upvoted 0 times
...
...
Tammi
11 months ago
Decision Table Testing? What is this, the 90s? Gotta go with the more agile Exploratory approach.
upvoted 0 times
Keva
9 months ago
Exploratory Testing allows for more flexibility and adaptability.
upvoted 0 times
...
Tamar
9 months ago
I think Error Guessing could also be a good option in this case.
upvoted 0 times
...
Eloisa
9 months ago
Yeah, Decision Table Testing seems a bit outdated.
upvoted 0 times
...
Malcom
9 months ago
I agree, Exploratory Testing is definitely more agile.
upvoted 0 times
...
Nan
9 months ago
I think we should go with Exploratory Testing for this project.
upvoted 0 times
...
Glen
9 months ago
Exploratory Testing allows for more flexibility.
upvoted 0 times
...
Stephen
9 months ago
Yeah, Decision Table Testing seems outdated.
upvoted 0 times
...
Melynda
10 months ago
I agree, Exploratory Testing is definitely more agile.
upvoted 0 times
...
...
Markus
11 months ago
I prefer Error Guessing, as it helps uncover unexpected defects.
upvoted 0 times
...
Luis
11 months ago
I agree with Bulah, Exploratory Testing allows for flexibility and adaptability.
upvoted 0 times
...
Rosita
11 months ago
Error Guessing? More like Error Hoping! But seriously, Exploratory Testing is the way to play this one.
upvoted 0 times
Moon
10 months ago
I agree, Exploratory Testing allows for flexibility and adaptability in testing.
upvoted 0 times
...
Samira
10 months ago
Exploratory Testing is definitely the way to go in this situation.
upvoted 0 times
...
Xuan
10 months ago
D) Exploratory Testing
upvoted 0 times
...
Cherri
10 months ago
C) Error Guessing
upvoted 0 times
...
Tarra
10 months ago
B) Boundary Value Analysis
upvoted 0 times
...
Tiera
10 months ago
A) Decision Table Testing
upvoted 0 times
...
...
Precious
11 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
11 months ago
I think Exploratory Testing would be most appropriate.
upvoted 0 times
...
Paz
11 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
9 months ago
I think we should go with Exploratory Testing for this scenario.
upvoted 0 times
...
Staci
9 months ago
D) Exploratory Testing is definitely the best choice for RAD projects.
upvoted 0 times
...
Glendora
9 months ago
I agree, Exploratory Testing allows for flexibility and adaptability in RAD development.
upvoted 0 times
...
Detra
9 months ago
D) Exploratory Testing
upvoted 0 times
...
Sharita
10 months ago
C) Error Guessing
upvoted 0 times
...
Joni
10 months ago
B) Boundary Value Analysis
upvoted 0 times
...
Margret
10 months ago
A) Decision Table Testing
upvoted 0 times
...
...

Save Cancel