Scaled Agile SAFe-SASM Exam - Topic 4 Question 32 Discussion

Actual exam question for Scaled Agile's SAFe-SASM exam

Question #: 32
Topic #: 4

[All SAFe-SASM Questions]

What is one problem with phase-gate Milestones?

AThey assume a point Solution exists and can be built right the first time

BThey force design decisions too late in the process

CThey account for variability inherent in the process

DThey require the Product Owner to act as gatekeeper or guardian of the process

Show Suggested Answer

Suggested Answer: A

Phase-gate milestones are traditional project management mechanisms that mark the end of one phase and the beginning of another. One major problem with phase-gate milestones is that they assume a point solution exists and can be built correctly the first time. This assumption does not account for the iterative nature of Agile methodologies, where solutions are developed incrementally and iteratively, with feedback loops and continuous improvement. Assuming a point solution can be finalized early often leads to rigidity, lack of adaptability, and higher risks of delivering a product that does not meet the actual needs or expectations.

by Danica at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium SAFe-SASM Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Whitley

8 days ago

Option D is the way to go. The Product Owner should be the gatekeeper to ensure the process is followed properly.

upvoted 0 times

...

Noah

13 days ago

I agree with option B. Forcing design decisions too late in the process can lead to issues down the line.

upvoted 0 times

...

Josefa

19 days ago

Option B is correct. Phase-gate milestones force design decisions too late in the process, which can be problematic.

upvoted 0 times

...

Shonda

24 days ago

I think C is definitely not a problem since phase-gate milestones are supposed to help manage variability, right? So that leaves us with A or B.

upvoted 0 times

...

Nickolas

29 days ago

I feel like I’ve seen practice questions where they mentioned the role of the Product Owner as a gatekeeper. That makes me lean towards D, but I’m not completely confident.

upvoted 0 times

...

Van

1 month ago

I’m not entirely sure, but I think B could be a problem too. If decisions are made too late, it could really impact the project timeline.

upvoted 0 times

...

Junita

1 month ago

I remember discussing how phase-gate milestones can sometimes assume that everything will go perfectly, which might not be realistic. So, A seems like a strong option.

upvoted 0 times

...

Tijuana

1 month ago

Ugh, I'm a bit lost on this. The phase-gate model has its pros and cons, and I'm not sure I fully grasp the nuances here. I'll have to make an educated guess.

upvoted 0 times

...

Cheryl

2 months ago

I feel pretty confident about this one. The phase-gate process can force design decisions too late, which can be a big problem. I'll go with B.

upvoted 0 times

...

Yasuko

2 months ago

Okay, let me see. I know the phase-gate model is meant to provide structure, but it can also introduce some rigidity. I'm leaning towards option B as the main issue.

upvoted 0 times

...

Wenona

2 months ago

Hmm, I think the key here is understanding the tradeoffs of the phase-gate approach. Option B seems like the most likely problem to me, but I'll double-check the others.

upvoted 0 times

...

Malcolm

2 months ago

I'm not totally sure about this one. The phase-gate process seems to have some pros and cons, so I'll need to think it through carefully.

upvoted 0 times

...