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

BCS CTFL4 Exam - Topic 4 Question 3 Discussion

Actual exam question for BCS's CTFL4 exam
Question #: 3
Topic #: 4
[All CTFL4 Questions]

You are an experienced tester on a project with incomplete requirements and under pressure to deploy.

What type of testing should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

When working on a project with incomplete requirements and under pressure to deploy, exploratory testing is particularly suitable. This type of testing allows testers to use their expertise and intuition to explore the system's functionality and identify defects without needing detailed specifications. Exploratory testing is flexible and can quickly adapt to changes and gaps in the requirements.


Contribute your Thoughts:

0/2000 characters
Catalina
2 months ago
Not sure about that, checklist-based testing might be safer.
upvoted 0 times
...
Jospeh
2 months ago
Definitely agree with that!
upvoted 0 times
...
Rebecka
3 months ago
Decision-based testing helps prioritize what to test first.
upvoted 0 times
...
Paola
3 months ago
Wait, can you really rely on error guessing? Sounds risky!
upvoted 0 times
...
Margurite
3 months ago
I think exploratory testing is key in this situation.
upvoted 0 times
...
Rebbecca
3 months ago
Decision-based testing sounds familiar, but I can't recall how it applies in this scenario. I guess it depends on what decisions we need to make.
upvoted 0 times
...
Melvin
4 months ago
I feel like error guessing might be a good approach too, especially since we can anticipate common issues, but it seems a bit risky.
upvoted 0 times
...
Tamesha
4 months ago
I think checklist-based testing could help ensure we cover the basics, but I wonder if it would be enough under pressure.
upvoted 0 times
...
Jackie
4 months ago
I remember we talked about exploratory testing being useful when requirements are incomplete, but I'm not sure if it's the best choice here.
upvoted 0 times
...
Wilda
4 months ago
Exploratory testing is definitely the way to go. We can use our experience to explore the system, identify risks, and test accordingly. That flexibility will be key.
upvoted 0 times
...
Cathern
4 months ago
Error guessing? I don't know, that seems a bit risky, especially with the pressure to deploy. I'd lean more towards a structured approach like checklist-based testing.
upvoted 0 times
...
Ilene
4 months ago
Hmm, I'm not sure. Decision-based testing could work, but it might be tough without clear requirements. I'll have to think this through.
upvoted 0 times
...
Desirae
5 months ago
I think exploratory testing would be the best approach here. With incomplete requirements, we need to be flexible and adaptable in our testing.
upvoted 0 times
...
Harris
5 months ago
Hmm, I'm not sure about this one. I'll have to think it through carefully. Maybe vMotion could work, but I'm not confident that's the right answer.
upvoted 0 times
...
Marica
5 months ago
I've got this! The answer is definitely C - Yes/No. That's the standard boolean datatype used to represent true/false conditions.
upvoted 0 times
...
Jess
5 months ago
I'm a bit confused by the wording here. Is the "bottleneck operation" the one that has to match the output? Or is that something different? I'll have to re-read this a few times to make sure I understand.
upvoted 0 times
...
Jerlene
5 months ago
For dual pricing, I remember it being either market price or marginal cost, and since the market price is $20, that might be what we use. I'm not too sure though.
upvoted 0 times
...

Save Cancel