Discuss ISQI CTFL_Syll2018 Exam Topic 7 Question 105

Which one of the following is an example of how product risk analysis can influence the testing approach?

AThe complex business rules could result in costly failures, so decision table testing will be used for test case design.

BPerformance failures were much lower than expected, so more test analysis will be conducted in this area.

CThere is a lack of automation skills in the test team, so training for the automation tool will be rolled out.

DThere are no product risks recorded around security, so security testing will be given priority as a contingency measure.

Suggested Answer: A

Product risk analysis is an approach to testing that aims to reduce the level of product risks and inform stakeholders of their status, starting in the initial stages of a project1.It involves the identification of product risks and the use of risk levels to guide the test process1.Product risks are uncertain situations that can affect the quality or value of the software product2.One of the factors that can influence the testing approach is the test design technique to be applied3.Test design techniques are methods to derive and select test cases based on the test objectives, test conditions, and test basis2.Decision table testing is a test design technique that is suitable for testing complex business rules that have logical conditions and outcomes2.Therefore, if the product risk analysis identifies that the complex business rules could result in costly failures, then decision table testing will be used for test case design to cover all the possible combinations of conditions and outcomes2.

The other options are not examples of how product risk analysis can influence the testing approach, because they are either not related to product risks or not based on risk levels. They are:

Performance failures were much lower than expected, so more test analysis will be conducted in this area (B).This is not related to product risk analysis, but to test monitoring and control, which is the process of comparing actual progress against the plan and reporting the status2.Test analysis is the activity of analyzing the test basis and defining test objectives2. If the performance failures were much lower than expected, then more test execution or evaluation might be needed, not more test analysis.

There is a lack of automation skills in the test team, so training for the automation tool will be rolled out .This is not related to product risk analysis, but to test management, which is the process of planning, monitoring, and controlling the test activities and resources2.Test automation is the use of software to perform or support test activities2.The lack of automation skills in the test team is a project risk, not a product risk, and it should be addressed by providing adequate training, tools, and resources for the test team2.

There are no product risks recorded around security, so security testing will be given priority as a contingency measure (D). This is not based on risk levels, but on the absence of risk identification, which is a poor practice in product risk analysis.Security testing is a type of testing that determines whether the software protects data and maintains functionality as intended2.Product risk analysis should identify the potential security risks and assign them appropriate risk levels based on their probability and impact1.Security testing should be prioritized based on the risk levels, not on the lack of risk identification, which could lead to overlooking or underestimating the security risks1.

ISTQB Foundation Level 2018 syllabus

Risk in Software Testing

Risk-Based Testing

Test Approach

Get Premium CTFL_Syll2018 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

27 comments · newest first

Elenore 11 months ago

I disagree with D. No risks recorded doesn't mean no risks exist.

Weldon 11 months ago

Lack of automation skills is a real issue. Training is a must!

Wava 11 months ago

Surprised that security testing is a contingency. Shouldn't it be a priority?

Germaine 11 months ago

I think option B makes more sense. More analysis is key.

Elly 11 months ago

Decision table testing is a smart move for complex rules!

Thurman 12 months ago

I recall that training for automation tools is more about team capability than product risk. So, I don't think option C fits the question about testing approaches influenced by product risks.

Roxane 12 months ago

I think we had a practice question about prioritizing testing based on risks. Option D seems off because it mentions no risks recorded, which doesn't sound right for influencing the testing approach.

Emerson 12 months ago

I'm a bit unsure about the differences between performance failures and product risks. I feel like option B might relate to risk analysis, but I'm not completely confident.

Bernadine 1 year ago

I remember we discussed decision table testing in class, especially how it helps with complex business rules. I think option A makes sense.

Emilio 1 year ago

This is a tricky question. I'm not sure if I fully understand the connection between product risk analysis and the testing approach. I might need to review that concept again before answering.

Leonie 1 year ago

I feel pretty confident about this one. Option A seems like the most relevant example - the complex business rules are a key product risk, so using decision table testing to address that risk makes sense.

Lea 1 year ago

Hmm, I'm a bit unsure about this one. I'm not totally clear on how product risk analysis specifically impacts the testing approach. I'll have to think this through carefully.

Tammara 1 year ago

Okay, this question is asking for an example of how product risk analysis can influence the testing approach. I think option A is the best answer - the complex business rules could lead to costly failures, so decision table testing would be a good approach to thoroughly cover those scenarios.

Kasandra 2 years ago

I see your point, maybe I should reconsider my answer.

Josefa 2 years ago

D) There are no product risks recorded around security, so security testing will be given priority as a contingency measure. Uh-oh, someone's playing it safe. Bet they're the type to bring their own snacks to the exam.

Pearlie 2 years ago

B) Performance failures were much lower than expected, so more test analysis will be conducted in this area. Huh, that's a weird choice. I'd have expected them to reduce the testing effort in this area.

Sherell 2 years ago

I agree with Eura, A seems like the most logical choice.

Rashida 2 years ago

C) There is a lack of automation skills in the test team, so training for the automation tool will be rolled out. Good call, addressing the skill gap to tackle the product risk.

Sharika 2 years ago

↳ replying to Rashida

D) There are no product risks recorded around security, so security testing will be given priority as a contingency measure.

Carmelina 2 years ago

↳ replying to Rashida

C) There is a lack of automation skills in the test team, so training for the automation tool will be rolled out.

Aimee 2 years ago

↳ replying to Rashida

A) The complex business rules could result in costly failures, so decision table testing will be used for test case design.

Eura 2 years ago

But A makes sense because complex business rules can lead to costly failures.

Kasandra 2 years ago

I disagree, I believe it's D.

Eura 2 years ago

I think the answer is A.

Gilbert 2 years ago

A) The complex business rules could result in costly failures, so decision table testing will be used for test case design. This makes perfect sense to address the identified product risk.

Kirby 2 years ago

↳ replying to Gilbert

B) There are no product risks recorded around security, so security testing will be given priority as a contingency measure.

Krissy 2 years ago

↳ replying to Gilbert

A) The complex business rules could result in costly failures, so decision table testing will be used for test case design.

iSQI CTFL_Syll2018 Exam - Topic 7 Question 105 Discussion