ISTQB-CTFL Exam - Topic 1 Question 15 Discussion

Actual exam question for ISTQB's ISTQB-CTFL exam

Question #: 15
Topic #: 1

[All ISTQB-CTFL Questions]

Which of the following is a typical product risk?

APoor usability of the software

BA problem in the code developed by a 3rd party

CLow quality of the configuration data, test data and tests

DProblem in defining the right requirements

Show Suggested Answer

Suggested Answer: A

A typical product risk involves issues directly related to the software product's functionality, performance, usability, reliability, etc. Option A, 'Poor usability of the software,' directly impacts the end-user's interaction with the software and is a quality attribute of the product itself, making it a product risk. Options B, 'A problem in the code developed by a 3rd party,' C, 'Low quality of the configuration data, test data and tests,' and D, 'Problem in defining the right requirements,' can be considered either product or project risks depending on the context, but option A is the most directly associated with a typical product risk concerning the quality and usability of the software.

by Pete at Mar 08, 2024, 07:13 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

My

3 months ago

Totally agree, usability issues can ruin user experience!

upvoted 0 times

...

Lili

3 months ago

Wait, are we sure defining the right requirements is a typical risk? Seems basic.

upvoted 0 times

...

Nana

3 months ago

Low quality of test data? That's a big red flag!

upvoted 0 times

...

Aaron

4 months ago

I think a problem in the code from a 3rd party can be a huge risk too.

upvoted 0 times

...

Hubert

4 months ago

Poor usability is definitely a product risk!

upvoted 0 times

...

Levi

4 months ago

Defining the right requirements seems crucial, but I wonder if it fits the definition of a typical product risk.

upvoted 0 times

...

Kerry

4 months ago

Low quality of configuration and test data sounds like a risk, but I can't recall if it's considered a product risk specifically.

upvoted 0 times

...

Pok

4 months ago

I remember a practice question about risks related to third-party code. That one feels relevant here too.

upvoted 0 times

...

Dick

5 months ago

I think poor usability of the software could definitely be a product risk, but I'm not sure if it's the most typical one.

upvoted 0 times

...

Nichelle

5 months ago

Okay, let me think this through. A problem in the code from a third-party, low-quality data and tests, or issues with requirements - these all seem like plausible product risks. I'll have to weigh the options carefully.

upvoted 0 times

...

Maynard

5 months ago

Ah, I know this one! Poor usability is definitely a common product risk that can impact the overall success of the software. I'm confident that's the right answer.

upvoted 0 times

...

Magda

5 months ago

Hmm, I'm not entirely sure about this one. Product risks could cover a wide range of issues, so I'll need to think carefully about which of these options is the most representative.

upvoted 0 times

...

Lottie

5 months ago

This seems like a straightforward question about product risks. I'll carefully review the options and choose the one that best fits the description of a typical product risk.

upvoted 0 times

...

Tamala

5 months ago

Hmm, I'm a bit unsure about this one. I know work lists and work queues are used to distribute tasks, but I'm not sure which one would be the better option here. I'll have to think this through carefully.

upvoted 0 times

...

Arlette

5 months ago

Okay, I think I've got a handle on this. The key is understanding how the internal and external business environment impacts compensation and rewards. Strong business acumen allows you to navigate those complexities.

upvoted 0 times

...