SAP Exam C_S4PPM_2021 Topic 2 Question 24 Discussion

Actual exam question for SAP's C_S4PPM_2021 exam

Question #: 24
Topic #: 2

[All C_S4PPM_2021 Questions]

Which of the following are consequence of releasing a phase?

NOTE: There are 2 correct answers to this question

APredecessor phases are assigned the status locked

BLower-level tasks and checklist are release

CAdditional tasks cannot be added to the phase

DThe phase type is set to read-only

Show Suggested Answer

Suggested Answer: B, D

by Tasia at May 09, 2024, 11:34 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Mitzie

1 years ago

Yeah, I agree with Ryann. A and D seem like the obvious consequences of releasing a phase. Gotta lock things down and prevent any changes.

upvoted 0 times

Lorriane

1 years ago

Yeah, those are the consequences of releasing a phase. Can't make any changes once it's done.

upvoted 0 times

...

Paris

1 years ago

I agree, A and D make sense. Locking the predecessor phases and setting the phase type to read-only.

upvoted 0 times

...

Rasheeda

1 years ago

Ha! I bet the project manager would love to prevent any additional tasks from being added to a released phase. That would make their lives so much easier!

upvoted 0 times

Mitzie

1 years ago

Definitely, it helps with managing expectations and timelines.

upvoted 0 times

...

Lucy

1 years ago

I agree, it's important to have a clear boundary for each phase.

upvoted 0 times

...

Mari

1 years ago

Yeah, it would definitely help with keeping things on track.

upvoted 0 times

...

Crista

1 years ago

Yeah, C seems right. But I'm still confused about the second option. Maybe A is correct too?

upvoted 0 times

...

Carline

1 years ago

Hmm, I'm not sure about B. I don't think lower-level tasks and checklists are automatically released just by releasing a phase.

upvoted 0 times

...

Ryann

1 years ago

I think the correct answers are A and D. Releasing a phase definitely locks the predecessor phases and makes the phase read-only.

upvoted 0 times

Lashanda

1 years ago

Yes, releasing a phase locks the predecessor phases and makes the phase read-only.

upvoted 0 times

...

Art

1 years ago

And it also makes the phase read-only.

upvoted 0 times

...

Natalya

1 years ago

Yes, releasing a phase locks the predecessor phases.

upvoted 0 times

...

Keena

1 years ago

I think the correct answers are A and D.

upvoted 0 times

...

Annamaria

1 years ago

I agree, A and D are the correct answers.

upvoted 0 times

...

Gail

1 years ago

Yes, releasing a phase locks the predecessor phases and makes the phase read-only.

upvoted 0 times

...

In

1 years ago

I agree, A and D are the correct answers.

upvoted 0 times

...

Lorean

1 years ago

I agree with C. If additional tasks cannot be added, it makes sense logically.

upvoted 0 times

...

Thad

1 years ago

I'm leaning towards A. Shouldn't predecessor phases be assigned as locked?

upvoted 0 times

...

Stephaine

1 years ago

I think it's C and D. Additional tasks cannot be added and the phase type is set to read-only.

upvoted 0 times

...

Crista

1 years ago

Yeah, it's tricky. What do you think are the correct answers?

upvoted 0 times

...

Thad

1 years ago

Have you seen the question about the consequence of releasing a phase?

upvoted 0 times

...