New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB CTFL-Foundation Exam - Topic 1 Question 7 Discussion

Actual exam question for ISTQB's CTFL-Foundation exam
Question #: 7
Topic #: 1
[All CTFL-Foundation Questions]

Which of the following would be a good test technique to use when under severe time pressure?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Nadine
3 months ago
Use case testing can also be quick if you know the scenarios well.
upvoted 0 times
...
Frederica
3 months ago
Wait, is exploratory really the best option? Sounds risky!
upvoted 0 times
...
Lino
3 months ago
Not so sure about that, structure based testing has its merits too.
upvoted 0 times
...
Dino
4 months ago
Totally agree, it’s all about speed and flexibility!
upvoted 0 times
...
Zoila
4 months ago
I think exploratory testing is the way to go when time is tight.
upvoted 0 times
...
Louvenia
4 months ago
Use case testing seems like it could help focus on critical paths, but I wonder if it’s too rigid when we need to be flexible.
upvoted 0 times
...
Adell
4 months ago
I think specification-based testing could work too, but it might require more detailed documentation, which we might not have time for.
upvoted 0 times
...
Salome
4 months ago
I'm not so sure about that. I thought structure-based testing was more systematic, but maybe it takes too long under pressure?
upvoted 0 times
...
Vincent
5 months ago
I remember we discussed exploratory testing as a quick way to find issues when time is tight. It feels like a good fit here.
upvoted 0 times
...
Glory
5 months ago
Structure-based testing might be the way to go. It ensures I hit all the core functionality, even if I can't do an exhaustive test.
upvoted 0 times
...
Alysa
5 months ago
Use case testing could be a good option. It focuses on the key user scenarios, which is probably the most important thing to cover in a time crunch.
upvoted 0 times
...
Tamar
5 months ago
Hmm, I'm not sure. Exploratory testing seems a bit risky under severe time pressure. Maybe specification-based testing would be more reliable?
upvoted 0 times
...
Winfred
5 months ago
I think exploratory testing would be the best approach here. It allows me to quickly test the system without getting bogged down in detailed test cases.
upvoted 0 times
...
Ariel
5 months ago
This one looks straightforward. I think the answer is D - the Process Owner would be responsible for the Documentation Plan after the Belt completes it.
upvoted 0 times
...
Percy
5 months ago
I think the health screening should be done before any physical activity, like option B. It makes sense to know the client's health status first.
upvoted 0 times
...
Felicia
5 months ago
I'm not sure about the legacy user interface option. That seems like it could just be a workaround rather than addressing the root cause of the performance problem.
upvoted 0 times
...
Latonia
5 months ago
Definitely Graph. Tracking how changes in one part of the network affect other components is all about understanding the connections, and that's exactly what Graph databases excel at. This seems like a straightforward choice to me.
upvoted 0 times
...
Alita
2 years ago
Specification based testing could save time by focusing on specific requirements.
upvoted 0 times
...
Kelvin
2 years ago
I believe using specification based testing would be more efficient.
upvoted 0 times
...
Tiara
2 years ago
But exploratory testing allows for flexibility and quick adaptation.
upvoted 0 times
...
Alita
2 years ago
I prefer structure based testing for quick results.
upvoted 0 times
...
Tiara
2 years ago
I think exploratory testing would be good under time pressure.
upvoted 0 times
...

Save Cancel