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

ISTQB ATM Exam - Topic 2 Question 30 Discussion

Actual exam question for ISTQB's ATM exam
Question #: 30
Topic #: 2
[All ATM Questions]

The main objectives the senior management team wants to achieve are:

- to reduce the costs associated with dynamic testing

- to use reviews to ensure that the project is on course for success and following the plan

- to use reviews as a well-documented and effective bug-removal activity following a formal process with well-defined roles

- to determine the effectiveness of reviews in terms of phase containment

- to improve phase containment effectiveness

Which of the following answers would you expect to describe the best way to achieve these objectives?

K4 3 credits

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Dominque
3 months ago
Wait, are we really analyzing bugs to find out who caused them? That seems intense!
upvoted 0 times
...
Flo
3 months ago
Definitely agree with focusing on phase containment!
upvoted 0 times
...
Art
4 months ago
Isn't it risky to rely too much on formal processes?
upvoted 0 times
...
Thersa
4 months ago
I think lightweight reviews could save time and still be effective.
upvoted 0 times
...
Glenna
4 months ago
Formal exit-phase reviews sound like a solid plan!
upvoted 0 times
...
German
4 months ago
I practiced a similar question where we had to choose between lightweight and formal reviews, and I think formal reviews are generally more effective for ensuring thoroughness.
upvoted 0 times
...
Pamela
4 months ago
I'm a bit confused about whether we should focus more on the process of gathering information or the type of reviews. I feel like both are important.
upvoted 0 times
...
Marge
5 months ago
I think option D sounds familiar because it emphasizes analyzing bugs to find out which phase they were introduced in, which could help with phase containment.
upvoted 0 times
...
Daron
5 months ago
I remember we discussed the importance of formal exit-phase reviews in class, but I'm not sure if they should be lightweight or formal for this scenario.
upvoted 0 times
...
Wynell
5 months ago
This is a good one. I reckon the key benefit is the ability to trigger product-specific scoring and program status changes. That would give Bhaskar a lot more control and flexibility in managing their products.
upvoted 0 times
...
Jaime
5 months ago
Hmm, I'm a little unsure about this one. I know piece rate is based on production, but I can't remember if that's the same as an individual's rate of production. Let me think this through carefully.
upvoted 0 times
...
Sheron
5 months ago
I can't shake the feeling that option C involves a manual approach that might not be the standard method, but it seems like a valid step nonetheless.
upvoted 0 times
...
Renay
5 months ago
I considered using NFS for this, but it might not be the best choice for temporary storage. The /tmp directory seems more straightforward and designed for cases like this.
upvoted 0 times
...
Earleen
5 months ago
Wait, I'm confused. I thought "Feasible" might be the right answer since a requirement has to be achievable to be considered fulfilled. But now I'm second-guessing myself. I need to re-read the question and options more closely.
upvoted 0 times
...
Tarra
9 months ago
I'm going with Option B. Anything that can help 'reduce the costs associated with dynamic testing' is a winner in my book!
upvoted 0 times
Anika
8 months ago
Option B does sound like a practical approach to meet the objectives. It's important to have a well-defined process in place for reviews.
upvoted 0 times
...
Alise
8 months ago
I think Option B is a good choice too. It seems like a solid plan for achieving the objectives set by the senior management team.
upvoted 0 times
...
Caprice
9 months ago
I'm going with Option B. Anything that can help 'reduce the costs associated with dynamic testing' is a winner in my book!
upvoted 0 times
...
...
Darrin
9 months ago
Option B is the way to go, no doubt. Formal reviews and a robust defect analysis process? Sign me up!
upvoted 0 times
...
Irving
9 months ago
Option B is the clear winner here. Formal reviews and a data-driven approach to defect analysis - that's the secret sauce to success!
upvoted 0 times
...
Lillian
9 months ago
Hmm, I'm not so sure. Option D also seems reasonable, as identifying the phase where bugs were introduced could be useful for improving phase containment effectiveness.
upvoted 0 times
Rosalind
8 months ago
Planning for formal exit-phase reviews at the end of each development and testing phase seems like a thorough approach to achieving the objectives.
upvoted 0 times
...
Ira
8 months ago
It's important to have a clear process for analyzing bugs found during testing to determine their origin.
upvoted 0 times
...
Wai
8 months ago
I agree, knowing when the bugs were introduced can definitely help in preventing similar issues in the future.
upvoted 0 times
...
Lamar
9 months ago
Option D seems like a good choice. Identifying the phase where bugs were introduced can help improve phase containment effectiveness.
upvoted 0 times
...
...
Lorean
10 months ago
I agree, Option B is the way to go. It focuses on the right activities like reviews and defect analysis, which align with the management team's objectives.
upvoted 0 times
...
Justine
10 months ago
Option B seems to cover all the key objectives mentioned in the question. Formal exit-phase reviews at the end of each phase, combined with a defect analysis process, would be the best approach to achieve the stated goals.
upvoted 0 times
Carole
8 months ago
C) You should plan for formal exit-phase reviews at the end of each development phase and testing phase, and plan for a process of gathering information from testing to perform an analysis of the bugs found during testing to determine the people responsible for those bugs
upvoted 0 times
...
Tayna
8 months ago
B) You should plan for formal exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis aimed at identifying the larger cluster of defects
upvoted 0 times
...
Jacinta
9 months ago
A) You should plan for lightweight exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis aimed at identifying the larger cluster of defects
upvoted 0 times
...
...
Polly
10 months ago
I'm not sure, but I think option C could also work well in ensuring bug-removal activities are effective.
upvoted 0 times
...
Bernadine
10 months ago
I agree with Georgiann, option D seems to be the most effective in improving phase containment.
upvoted 0 times
...
Georgiann
10 months ago
I think option D would be the best way to achieve the objectives.
upvoted 0 times
...
Ronnie
10 months ago
I'm not sure, but I think option C could also be a good choice. It mentions analyzing bugs found during testing to determine the people responsible for those bugs.
upvoted 0 times
...
Izetta
10 months ago
I agree with Shawnna. Option D seems to focus on identifying when bugs were introduced, which can help improve phase containment effectiveness.
upvoted 0 times
...
Shawnna
10 months ago
I think option D would be the best way to achieve the objectives.
upvoted 0 times
...

Save Cancel