ISTQB-CTFL Exam - Topic 2 Question 23 Discussion

Actual exam question for ISTQB's ISTQB-CTFL exam

Question #: 23
Topic #: 2

[All ISTQB-CTFL Questions]

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

What type of testing should you do?

ADecision-based testing.

BChecklist-based testing.

CError guessing.

DExploratory testing.

Show Suggested Answer

Suggested Answer: D

Component integration tests are designed to verify the interactions and interfaces between integrated components. These tests should be carried out after component testing (where individual components are tested in isolation) but before system testing (where the entire system is tested as a whole). This ensures that any issues arising from the integration of components are identified and resolved early in the testing process, making option D the correct answer.

by Eugene at Jun 20, 2024, 12:09 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Francene

7 months ago

Decision-based testing might be a good approach, but I'm not sure.

upvoted 0 times

...

Isaiah

8 months ago

Wait, error guessing? That sounds risky!

upvoted 0 times

...

Novella

8 months ago

Checklist-based testing could work too, right?

upvoted 0 times

...

Miss

8 months ago

Definitely agree with that!

upvoted 0 times

...

Yuriko

8 months ago

I think exploratory testing is key here.

upvoted 0 times

...

Daniela

9 months ago

Decision-based testing sounds like it could work, but I’m not entirely clear on how to prioritize the tests without complete requirements.

upvoted 0 times

...

Willie

9 months ago

I feel like error guessing could be effective too, especially under pressure, but I wonder if it’s too random for a deployment.

upvoted 0 times

...

Kiera

9 months ago

I think checklist-based testing could help ensure we cover the basics, but it might not be flexible enough for this situation.

upvoted 0 times

...

Yoko

9 months ago

I remember we discussed that exploratory testing is useful when requirements are incomplete, but I'm not sure if it's the best choice here.

upvoted 0 times

...

Adelle

9 months ago

Checklist-based testing could be a good starting point, but with incomplete requirements, I'm worried I might miss important stuff. Error guessing might be worth a try too, but it feels a bit risky.

upvoted 0 times

...

Elise

9 months ago

Exploratory testing is definitely the way to go here. It'll let me dig into the system and find issues the business didn't even know about. Gotta be quick and thorough though.

upvoted 0 times

...

Franchesca

9 months ago

Hmm, I'm not sure. Decision-based testing could work, but with the lack of requirements, that might be challenging. I'll have to think this through carefully.

upvoted 0 times

...

Kaitlyn

9 months ago

This is a tricky one. With incomplete requirements and pressure to deploy, I'd probably go with exploratory testing to uncover as many issues as I can quickly.

upvoted 0 times

...

Cheryl

9 months ago

Okay, I've got a strategy for this. The key is to focus on the goal - the designer needs to conduct an independent audit of the current website. So the activity that best aligns with that is an expert review.

upvoted 0 times

...

Nell

9 months ago

Creating a baseline from Enterprise Console sounds like it could work, but I'm not as familiar with that tool. I'll have to double-check the differences between the consoles and which one is best for capturing the state of the decision service.

upvoted 0 times

...

An

9 months ago

I recall that configuring the IP address of the DHCP server is crucial too, but I can't remember if it's the main action for forwarding packets.

upvoted 0 times

...

Herminia

10 months ago

I'm not entirely sure, but I feel like we've discussed similar questions where one service's failure impacts others.

upvoted 0 times

...

Jamie

1 year ago

D) Exploratory testing. Incomplete requirements? Sounds like a job for Captain Improvisation!

upvoted 0 times

...

Miesha

1 year ago

A) Decision-based testing. I'll just flip a coin and hope for the best. What could go wrong?

upvoted 0 times

Lashaunda

1 year ago

C) Error guessing. Let's try to anticipate where errors might occur and test those areas.

upvoted 0 times

...

Kimberely

1 year ago

D) Exploratory testing. We should explore the system and find any unexpected issues.

upvoted 0 times

...

Maira

1 year ago

B) Checklist-based testing. We need to make sure we cover all possible scenarios.

upvoted 0 times

...

Marti

1 year ago

C) Error guessing. Incomplete requirements? Time to channel my inner Sherlock Holmes and predict all the things that could go wrong!

upvoted 0 times

Rolland

1 year ago

D) Exploratory testing.

upvoted 0 times

...

Leontine

1 year ago

B) Checklist-based testing.

upvoted 0 times

...

Lavera

1 year ago

D) Exploratory testing.

upvoted 0 times

...

Leontine

1 year ago

C) Error guessing.

upvoted 0 times

...

Glory

1 year ago

B) Checklist-based testing.

upvoted 0 times

...

Leah

1 year ago

A) Decision-based testing.

upvoted 0 times

...

Arleen

1 year ago

A) Decision-based testing.

upvoted 0 times

...

Margurite

1 year ago

B) Checklist-based testing. Gotta cover all the bases, even if the requirements are sketchy.

upvoted 0 times

Vallie

1 year ago

C) Error guessing.

upvoted 0 times

...

Antione

1 year ago

B) Checklist-based testing.

upvoted 0 times

...

Keith

1 year ago

D) Exploratory testing.

upvoted 0 times

...

Andra

1 year ago

A) Decision-based testing.

upvoted 0 times

...

Jesusa

1 year ago

D) Exploratory testing. With incomplete requirements, I need a flexible approach to uncover issues quickly.

upvoted 0 times

Marcos

1 year ago

A) Decision-based testing might not be as effective with incomplete requirements.

upvoted 0 times

...

Charlette

1 year ago

D) Exploratory testing is definitely the way to go in this situation.

upvoted 0 times

...

Melynda

1 year ago

But what about error guessing? It could help us uncover unexpected issues.

upvoted 0 times

...

Evangelina

1 year ago

I agree, exploratory testing allows us to adapt to the changing requirements.

upvoted 0 times

...

Paris

1 year ago

I think we should do exploratory testing.

upvoted 0 times

...