ISTQB CTFL-Foundation Exam - Topic 2 Question 34 Discussion

Actual exam question for ISTQB's CTFL-Foundation exam

Question #: 34
Topic #: 2

Your company is developing a system with complex business rules and many branches in the structure of its code components. You need to choose one black box technique and one white box technique for test case design.

Which one of the following offers the BEST choice?

AStatement testing and exploratory testing

BDecision testing and equivalence partitioning

CDecision testing and decision table testing

DBoundary value analysis and decision table testing

Show Suggested Answer

Suggested Answer: D

For a system with complex business rules and many branches, decision testing (a white-box technique) is appropriate because it ensures that each decision point (branch) in the code is tested. Equivalence partitioning (a black-box technique) complements this by ensuring that all functional areas (based on different inputs) are adequately tested. This combination provides thorough coverage of both the internal logic and the functional requirements of the system.

by Leatha at Mar 08, 2025, 02:02 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Winfred

4 months ago

Decision testing is definitely a must-have here.

upvoted 0 times

...

Lisbeth

4 months ago

Surprised that no one mentioned D, it’s solid too!

upvoted 0 times

...

Sharen

4 months ago

A is too vague for my liking.

upvoted 0 times

...

Brynn

4 months ago

I disagree, C seems more comprehensive.

upvoted 0 times

...

Lashanda

4 months ago

I think B is the best choice for complex rules.

upvoted 0 times

...

Jennie

5 months ago

I feel like boundary value analysis is useful for edge cases, but I’m not sure if it complements decision table testing as well as decision testing does.

upvoted 0 times

...

Dominga

5 months ago

Decision table testing seems like a solid option since it can handle multiple conditions, but I’m torn between it and equivalence partitioning for the black box technique.

upvoted 0 times

...

Sharan

5 months ago

I think exploratory testing is great for finding unexpected issues, but I’m not confident it’s the right choice alongside statement testing for this scenario.

upvoted 0 times

...

Magnolia

5 months ago

I remember we discussed decision testing being really effective for complex business rules, but I'm not sure if it pairs best with equivalence partitioning or decision table testing.

upvoted 0 times

...

Lorean

5 months ago

Hmm, I'm not sure. Statement testing and exploratory testing (option A) could also be a good approach to explore the system's behavior without getting too deep into the code. I'll have to weigh the pros and cons of each option.

upvoted 0 times

...

Nan

5 months ago

I feel pretty confident about this one. Decision testing and decision table testing (option C) seem like a solid combo to handle the complex business rules and code structure they're describing.

upvoted 0 times

...

Lenita

5 months ago

I'm a bit confused by the wording of the question. What exactly do they mean by "complex business rules" and "many branches in the structure of the code"? That makes me hesitant about some of the options.

upvoted 0 times

...

Jerry

5 months ago

Okay, let's see. The question is asking for the best combination of a black box and a white box technique. I'm leaning towards option D - boundary value analysis and decision table testing.

upvoted 0 times

...

Clorinda

5 months ago

This is a tricky one. I'll need to think carefully about the differences between black box and white box techniques and which ones would work best for this scenario.

upvoted 0 times

...

Xochitl

12 months ago

Hmm, I was leaning towards B, but these other options sound pretty good too. Maybe I should just roll a dice to decide. *chuckles* Nah, just kidding. D it is!

upvoted 0 times

...

Evette

12 months ago

I think exploratory testing can also be useful to uncover hidden issues.

upvoted 0 times

...

Carlee

12 months ago

I was thinking option C, but after Deonna and Kayleigh's comments, D does seem like the strongest choice. Gotta cover all the bases, you know?

upvoted 0 times

Edwin

10 months ago

I was leaning towards option C, but now I see the benefits of option D.

upvoted 0 times

...

Graciela

11 months ago

I agree with you, option B seems more appropriate.

upvoted 0 times

...

Fredric

11 months ago

I think option A is the way to go.

upvoted 0 times

...

Joanna

12 months ago

I prefer boundary value analysis and decision table testing, it helps in identifying edge cases.

upvoted 0 times

...

Kayleigh

12 months ago

Yeah, I agree with Deonna. Decision table testing is crucial for handling those complex business rules. And boundary value analysis is a must for finding any potential issues at the limits of the system.

upvoted 0 times

Dorothy

11 months ago

Decision testing and decision table testing seem like the best options for this scenario.

upvoted 0 times

...

Willard

11 months ago

I agree, and boundary value analysis is important for testing the limits of the system.

upvoted 0 times

...

Marisha

11 months ago

I think decision table testing is a good choice for handling complex business rules.

upvoted 0 times

...

Alica

1 year ago

I agree with Phuong, decision testing can help cover all possible outcomes.

upvoted 0 times

...

Phuong

1 year ago

I think the best choice is decision testing and decision table testing.

upvoted 0 times

...

Deonna

1 year ago

For a complex system with many code branches, I think option D is the best choice. Boundary value analysis and decision table testing can really help cover all the edge cases.

upvoted 0 times

Werner

1 year ago

Yes, boundary value analysis and decision table testing can really help ensure thorough coverage of the system's functionality.

upvoted 0 times

...

Ronny

1 year ago

I agree, option D seems like the most comprehensive choice for testing.

upvoted 0 times

...