Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

iSQI Exam CTAL-TM_Syll2012 Topic 1 Question 58 Discussion

Actual exam question for iSQI's CTAL-TM_Syll2012 exam
Question #: 58
Topic #: 1
[All CTAL-TM_Syll2012 Questions]

Assume that you are the Test Manager for a small insurance application development project. You have decided to adopt a risk-based testing strategy: 5 product risks (R1, R2, R3, R4, R5)

have been identified and their levels of risk have been assessed. 10 test cases (T1, ..., T10) have been designed to cover all the product risks.

The following table shows the risk level and the test cases associated to the identified product risks (higher risk level means higher risk):

You are not confident with the assessment of the risk level and you suspect that it will be possible to find high-priority bugs in low-risk areas.

Furthermore the period for test execution is very short. Your goal is to test all the product risks in a risk-based way, while assuring that each product risk gets at least some amount of testing. Which of the following answers describes the best test execution schedule in this scenario? K3 2 credits

Show Suggested Answer Hide Answer
Suggested Answer: C, E

Contribute your Thoughts:

Holley
1 months ago
Wait, are we sure the test manager isn't just trying to trick us? Maybe they're actually a secret agent testing our risk-assessment skills. Better keep my wits about me!
upvoted 0 times
Lore
13 days ago
I think we should go with option A) T1, T2, T3, T4, T5, T6, T7, T8, T9, T10. It covers all the test cases and ensures each product risk gets some testing.
upvoted 0 times
...
...
Alfred
2 months ago
Alright, let's do this! Time to put on my risk-based testing hat and come up with the best schedule. I bet the test manager is hoping we don't drop the ball on this one.
upvoted 0 times
Roosevelt
4 days ago
D) T10, T8, T6, T4, T2, T9, T7, T5, T3, T1
upvoted 0 times
...
Sherman
5 days ago
B) T1, T3, T5, T7, T9, T2, T4, T6, T8, T10
upvoted 0 times
...
Yvonne
19 days ago
D) T10, T8, T6, T4, T2, T9, T7, T5, T3, T1
upvoted 0 times
...
Jess
25 days ago
B) T1, T3, T5, T7, T9, T2, T4, T6, T8, T10
upvoted 0 times
...
Ettie
26 days ago
A) T1, T2, T3, T4, T5, T6, T7, T8, T9, T10
upvoted 0 times
...
Nettie
1 months ago
A) T1, T2, T3, T4, T5, T6, T7, T8, T9, T10
upvoted 0 times
...
...
Ramonita
2 months ago
Hold on, are we sure the risk assessments are accurate? What if the low-risk areas are actually hiding some high-priority bugs? This could be a sneaky one, gotta keep an open mind.
upvoted 0 times
...
Catherin
2 months ago
Wow, this seems like a challenging scenario. I'll need to strike a balance between covering the highest-risk areas and still giving some attention to the lower-risk ones. Tough call!
upvoted 0 times
...
Celestina
2 months ago
Hmm, this is a tricky one. I need to consider the risk levels and ensure that each risk gets some coverage, even if it's not the most optimal. Let me think this through carefully.
upvoted 0 times
Bernadine
5 days ago
That sounds like a good approach. We need to balance coverage with risk levels.
upvoted 0 times
...
Cherry
16 days ago
Maybe we can start with the higher risk test cases and then move on to the lower risk ones.
upvoted 0 times
...
Trinidad
24 days ago
But we also need to make sure that all product risks get some testing.
upvoted 0 times
...
Teddy
1 months ago
I think we should prioritize testing the higher risk areas first.
upvoted 0 times
...
...
Lindsey
2 months ago
I believe the best test execution schedule would be option A.
upvoted 0 times
...
Annamae
2 months ago
I agree. We need to make sure we cover all the product risks.
upvoted 0 times
...
Rikki
2 months ago
I think we should prioritize testing based on the risk level.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77