Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ASTQB Exam - Topic 1 Question 63 Discussion

Posted by Valentine on Mar 16, 2024 at 08:42 PM

In a project that is feature-rich but time-poor, which is the most reasonable approach to risk analysis?

Suggested Answer: B

Get Premium ASTQB Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
36 comments · newest first
RO
Ronna 11 months ago
Surprised anyone would consider skipping risk analysis altogether!
WY
Wynell 11 months ago
D? Really? That sounds risky to me.
GI
Gianna 12 months ago
C is a bit reckless, right?
MA
Marget 12 months ago
I disagree, A is necessary for thoroughness.
RA
Rasheeda 1 year ago
B seems like the best option, gotta be efficient!
GE
German 1 year ago
I’m leaning towards option A, but it seems like it might be overkill for a time-poor project. I just can’t decide!
AM
Amos 1 year ago
I remember a practice question where we had to prioritize risks quickly. I feel like using a lightweight approach is similar to that.
ON
Onita 1 year ago
I’m not sure about skipping the risk analysis entirely like in option C. That could lead to bigger issues later on.
CO
Corinne 1 year ago
I think option B makes the most sense since we’re short on time. A full risk analysis could take too long.
JE
Jenise 1 year ago
I'm leaning towards option B. In a feature-rich but time-poor project, we need to focus on the most critical risks rather than getting bogged down in a full analysis.
TA
Talia 1 year ago
Hmm, I'm not sure. Skipping the risk analysis step entirely seems risky, even with the time pressure. I'd want to at least do a quick assessment of the key risks.
NA
Nana 1 year ago
I think the lightweight approach of assigning relative importance to each risk item is the most reasonable here. With the time constraints, a full risk analysis might take too long.
DE
Denise 1 year ago
Option D doesn't seem relevant to the question. The focus is on risk analysis, not on functional vs. physical testing. I'd rule that one out.
IE
Iesha 1 year ago
This looks like a pretty straightforward question. I think the key is to find a way to externalize the endpoint and credentials so they can be easily changed without modifying the code.
AN
Annett 1 year ago
Cascading delete seems like the most straightforward solution to avoid those orphan records. I'll double-check the details, but that's my initial thought.
LE
Leonida 1 year ago
I feel pretty confident about this one. The send-flush-on-failure feature is designed to help the VPLS network recover more quickly when there's a failure on an active pseudowire. By flushing the local forwarding database, it allows the standby pseudowire to take over without having to wait for the FDB to converge. Option C seems to describe that process the best.
KA
Karol 1 year ago
Haha, D sounds like something my grandparents would suggest. 'Just focus on the important stuff, the rest will figure itself out!'
CE
Cecil 1 year ago
↳ replying to Karol
Haha, D sounds like something my grandparents would suggest. 'Just focus on the important stuff, the rest will figure itself out!'
ER
Erick 1 year ago
↳ replying to Karol
B) Use a lightweight approach and assign relative importance of each identified item
CR
Crissy 1 year ago
↳ replying to Karol
A) Conduct a full risk analysis, including weighted likelihood and impact ratings for each item
MI
Michael 2 years ago
D is a bit concerning. Disregarding the physical capabilities of the device could lead to serious issues down the line.
AR
Argelia 1 year ago
↳ replying to Michael
D) I think we should definitely consider the physical capabilities, skipping that step could be risky
DO
Dottie 1 year ago
↳ replying to Michael
B) I agree, assigning relative importance seems like a practical approach in this situation
CH
Chaya 1 year ago
↳ replying to Michael
A) Conduct a full risk analysis, including weighted likelihood and impact ratings for each item
NI
Nikita 2 years ago
C is definitely not the way to go. Skipping risk analysis is a recipe for disaster, no matter how experienced the team is.
FE
Felix 1 year ago
↳ replying to Nikita
C is definitely not the way to go. Skipping risk analysis is a recipe for disaster, no matter how experienced the team is.
CH
Chun 1 year ago
↳ replying to Nikita
B) Use a lightweight approach and assign relative importance of each identified item
AR
Arthur 1 year ago
↳ replying to Nikita
A) Conduct a full risk analysis, including weighted likelihood and impact ratings for each item
CH
Chara 2 years ago
I see both points, but I think skipping risk analysis like option C is too risky. We should at least consider some form of analysis.
AN
Angelica 2 years ago
I disagree, I believe option B is better. We can prioritize risks based on their relative importance.
EL
Elli 2 years ago
I think B is the most reasonable approach. A full risk analysis can be time-consuming, and we need to focus on the most important items given the time constraints.
GI
Gilberto 1 year ago
↳ replying to Elli
I think focusing on the most critical items is key in a time-sensitive project.
GI
Giovanna 1 year ago
↳ replying to Elli
True, we can't ignore the importance of identifying and prioritizing risks.
MA
Marshall 1 year ago
↳ replying to Elli
But wouldn't it be risky to skip the risk analysis step altogether?
LE
Lettie 2 years ago
↳ replying to Elli
I agree, a lightweight approach would be more practical in this situation.
FR
France 2 years ago
I think option A is the most reasonable approach. We need to assess the likelihood and impact of each risk.
0/2000 characters

Save Cancel