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 3 Question 79 Discussion

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

You are managing the system testing for a SOA based system. The integrated system consists of several subsystems:

- A SOA middleware

- A CRM (Customer Relationship Management) system

- A BRM (Billing and Revenue Management) system

- A SMS (Subscriber Management System) system and you performed a risk analysis based on these subsystems.

At the end of the scheduled period for test execution you produce a first classical report based on the traditional metrics of testing. Test pass/fail status and bug status (open/resolved) That table provides you a distorted picture of the quality risk, because there is no indication of the risk level of the failed tests, the tests not run, or the open bugs. Thus, you produce the following table to solve this distortion issue:

In the table above, where you have introduced the concept of risk weighting, the highest risk test or bug report has a score of 1, while the lowest risk test or bug report has a score of 0.04. Which of the following subsystems, based on the risk scores of the table, is most risky? K4 3 credits

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Devorah
1 months ago
Wait, is this a trick question? What if the riskiest subsystem is the one that's not even listed?
upvoted 0 times
Danica
5 days ago
C) BRM
upvoted 0 times
...
Lashaun
10 days ago
B) CRM
upvoted 0 times
...
Tamekia
17 days ago
A) SOA
upvoted 0 times
...
...
Marjory
1 months ago
I hope the correct answer isn't 'All of the above'. That would be a real SOA-p opera!
upvoted 0 times
Deja
4 days ago
B: I think it's the BRM system that poses the highest risk.
upvoted 0 times
...
Felicitas
9 days ago
A: The most risky subsystem based on the risk scores is the CRM system.
upvoted 0 times
...
...
Franchesca
2 months ago
This is a tricky one. I'll need to analyze that table carefully to find the riskiest subsystem.
upvoted 0 times
Felicitas
5 days ago
D) SMS
upvoted 0 times
...
Marica
8 days ago
C) BRM
upvoted 0 times
...
Edison
1 months ago
D) SMS
upvoted 0 times
...
Jodi
1 months ago
C) BRM
upvoted 0 times
...
Elli
1 months ago
B) CRM
upvoted 0 times
...
Lizbeth
1 months ago
A) SOA
upvoted 0 times
...
Rory
1 months ago
B) CRM
upvoted 0 times
...
Han
2 months ago
A) SOA
upvoted 0 times
...
...
Olga
2 months ago
Hmm, the risk weighting table looks interesting. I bet the subsystem with the highest risk score is the culprit.
upvoted 0 times
...
Erick
2 months ago
Why do you think BRM is the most risky?
upvoted 0 times
...
Ardella
2 months ago
I disagree, I believe the most risky subsystem is the BRM.
upvoted 0 times
...
Raul
2 months ago
Alright, time to put my testing knowledge to the test! Let's see what this SOA system has in store for us.
upvoted 0 times
Abel
24 days ago
D) SMS
upvoted 0 times
...
Verlene
25 days ago
Interesting perspectives, it's important to carefully consider all subsystems when assessing risk in testing.
upvoted 0 times
...
Torie
25 days ago
C) BRM
upvoted 0 times
...
Kimberlie
27 days ago
B) CRM
upvoted 0 times
...
Twana
27 days ago
I see your point, but I still think the SOA middleware poses the highest risk in this scenario.
upvoted 0 times
...
Chun
29 days ago
A) SOA
upvoted 0 times
...
Delmy
1 months ago
I disagree, I believe the BRM system is the most risky based on the risk scores.
upvoted 0 times
...
Viva
1 months ago
I think based on the risk scores, the CRM system seems to be the most risky.
upvoted 0 times
...
...
Erick
3 months ago
I think the most risky subsystem is the CRM.
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