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

SAP Exam C_S4PPM_2021 Topic 2 Question 28 Discussion

Actual exam question for SAP's C_S4PPM_2021 exam
Question #: 28
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

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Contribute your Thoughts:

Elvis
3 months ago
Releasing a phase, of course the predecessor phases get locked. Otherwise, what's the point? A and D are definitely the right answers here.
upvoted 0 times
...
Delila
3 months ago
Haha, I bet the developers who came up with this question were just trying to trip us up with that 'B' option. Nice try, but I'm too smart for that!
upvoted 0 times
...
Paz
3 months ago
Hmm, I'm not sure about B. Releasing lower-level tasks and checklists doesn't seem like a direct consequence of just releasing the phase itself.
upvoted 0 times
Wilda
2 months ago
D) The phase type is set to read-only
upvoted 0 times
...
Cyril
2 months ago
C) Additional tasks cannot be added to the phase
upvoted 0 times
...
Vilma
2 months ago
B) Lower-level tasks and checklist are release
upvoted 0 times
...
Darci
2 months ago
A) Predecessor phases are assigned the status locked
upvoted 0 times
...
...
Elliott
3 months ago
I think C and D are incorrect because additional tasks can still be added to the phase and the phase type is not necessarily set to read-only.
upvoted 0 times
...
Vannessa
3 months ago
I agree, A and D are the correct answers. Locking the predecessor phases and making the phase read-only are clear results of releasing a phase.
upvoted 0 times
...
Jaime
3 months ago
I'm not sure about C and D, they don't seem like consequences of releasing a phase to me.
upvoted 0 times
...
Gregoria
3 months ago
A and D seem like the most logical consequences of releasing a phase. Can't add new tasks and the phase becomes read-only, that makes sense.
upvoted 0 times
Eun
3 months ago
D) The phase type is set to read-only
upvoted 0 times
...
Marcos
3 months ago
A) Predecessor phases are assigned the status locked
upvoted 0 times
...
...
Tanja
4 months ago
Haha, good thing I remembered that from the training. This is an easy one - A and D for sure. No more monkeying around once a phase is released!
upvoted 0 times
...
Sharen
4 months ago
I think B and C are also correct. Lower-level tasks and checklists are released, and new tasks can't be added to the phase.
upvoted 0 times
Alise
2 months ago
D) The phase type is set to read-only
upvoted 0 times
...
Darell
2 months ago
C) Additional tasks cannot be added to the phase
upvoted 0 times
...
Glendora
3 months ago
B) Lower-level tasks and checklist are release
upvoted 0 times
...
Bernardo
3 months ago
A) Predecessor phases are assigned the status locked
upvoted 0 times
...
...
Sylvia
4 months ago
I agree with Karl, A and B make sense because they are consequences of releasing a phase.
upvoted 0 times
...
Xochitl
4 months ago
Definitely A and D. Releasing a phase locks down the predecessor phases and makes the phase read-only. No more changes allowed!
upvoted 0 times
Fernanda
3 months ago
That's right, releasing a phase locks down the predecessor phases and makes the phase read-only.
upvoted 0 times
...
Franchesca
3 months ago
I agree, A and D are the correct consequences of releasing a phase.
upvoted 0 times
...
...
Karl
4 months ago
I think A and B are the correct answers.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77