New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

iSQI CTAL-TM_Syll2012 Exam - 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:

0/2000 characters
Sharika
3 months ago
SMS systems can be tricky too, don’t underestimate them!
upvoted 0 times
...
Raymon
3 months ago
Risk weighting is key, but it can be misleading if not interpreted correctly.
upvoted 0 times
...
Elin
3 months ago
Wait, are we sure about that? I thought BRM would be higher risk.
upvoted 0 times
...
Peggie
4 months ago
Totally agree, CRM systems usually have a lot of moving parts.
upvoted 0 times
...
Tracey
4 months ago
Looks like the CRM is the riskiest based on the scores!
upvoted 0 times
...
Buck
4 months ago
I vaguely remember that the BRM system had a lot of critical bugs in our last practice, so it could be a contender for the highest risk, but I'm not entirely confident.
upvoted 0 times
...
Tawny
4 months ago
I feel like the SOA middleware might be the riskiest based on its central role, but I need to double-check the risk scores in the table.
upvoted 0 times
...
Youlanda
4 months ago
I think we practiced a similar question where the CRM system had the most issues, but I can't recall the exact scores from that exercise.
upvoted 0 times
...
Azalee
5 months ago
I remember we discussed how risk weighting can change the perspective on test results, but I'm not sure which subsystem had the highest risk score.
upvoted 0 times
...
Fallon
5 months ago
Based on the information provided, the subsystem with the highest risk score is the riskiest. So I'd say the answer is the subsystem with the risk score closest to 1.
upvoted 0 times
...
Dominic
5 months ago
I'm a bit confused by the risk weighting. Does that mean the higher the score, the riskier the subsystem? Or is it the other way around?
upvoted 0 times
...
Judy
5 months ago
Okay, let's think this through step-by-step. The table shows the risk scores for each subsystem, with the highest risk at 1 and the lowest at 0.04. We just need to identify which subsystem has the highest risk score.
upvoted 0 times
...
Tenesha
5 months ago
This question seems straightforward, but I want to make sure I understand the risk weighting concept correctly before answering.
upvoted 0 times
...
Devorah
9 months ago
Wait, is this a trick question? What if the riskiest subsystem is the one that's not even listed?
upvoted 0 times
Reuben
8 months ago
D) SMS
upvoted 0 times
...
Danica
8 months ago
C) BRM
upvoted 0 times
...
Lashaun
9 months ago
B) CRM
upvoted 0 times
...
Tamekia
9 months ago
A) SOA
upvoted 0 times
...
...
Marjory
10 months ago
I hope the correct answer isn't 'All of the above'. That would be a real SOA-p opera!
upvoted 0 times
Lorean
8 months ago
C: Actually, the SMS system has the highest risk score according to the table.
upvoted 0 times
...
Deja
8 months ago
B: I think it's the BRM system that poses the highest risk.
upvoted 0 times
...
Felicitas
9 months ago
A: The most risky subsystem based on the risk scores is the CRM system.
upvoted 0 times
...
...
Franchesca
10 months ago
This is a tricky one. I'll need to analyze that table carefully to find the riskiest subsystem.
upvoted 0 times
Felicitas
8 months ago
D) SMS
upvoted 0 times
...
Marica
9 months ago
C) BRM
upvoted 0 times
...
Edison
9 months ago
D) SMS
upvoted 0 times
...
Jodi
9 months ago
C) BRM
upvoted 0 times
...
Elli
9 months ago
B) CRM
upvoted 0 times
...
Lizbeth
10 months ago
A) SOA
upvoted 0 times
...
Rory
10 months ago
B) CRM
upvoted 0 times
...
Han
10 months ago
A) SOA
upvoted 0 times
...
...
Olga
10 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
10 months ago
Why do you think BRM is the most risky?
upvoted 0 times
...
Ardella
11 months ago
I disagree, I believe the most risky subsystem is the BRM.
upvoted 0 times
...
Raul
11 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
9 months ago
D) SMS
upvoted 0 times
...
Verlene
9 months ago
Interesting perspectives, it's important to carefully consider all subsystems when assessing risk in testing.
upvoted 0 times
...
Torie
9 months ago
C) BRM
upvoted 0 times
...
Kimberlie
9 months ago
B) CRM
upvoted 0 times
...
Twana
9 months ago
I see your point, but I still think the SOA middleware poses the highest risk in this scenario.
upvoted 0 times
...
Chun
9 months ago
A) SOA
upvoted 0 times
...
Delmy
10 months ago
I disagree, I believe the BRM system is the most risky based on the risk scores.
upvoted 0 times
...
Viva
10 months ago
I think based on the risk scores, the CRM system seems to be the most risky.
upvoted 0 times
...
...
Erick
11 months ago
I think the most risky subsystem is the CRM.
upvoted 0 times
...

Save Cancel