PMI-RMP Exam - Topic 6 Question 104 Discussion

Actual exam question for PMI's PMI-RMP exam

Question #: 104
Topic #: 6

A project manager was informed that the testing of the latest component in the project's software update release was not successful. As a result, 1he delivery timelines for the software release wifi be delayed, The project manager did not previously capture this as a risk to the project.

What should the project manager do next to avoid similar risks?

AAdd contingencies to other tasks to mitigate similar risks.

BReassess risks with a new assumptions and constraints analysis.

CReview the risk response plan looking for lessons learned.

DLog the event in the issue log and update the project management plan.

Show Suggested Answer

Suggested Answer: B

The project manager should reassess risks by conducting a new assumptions and constraints analysis. This will help identify any previously overlooked risks and ensure that the risk register is comprehensive and up-to-date.

by Alethea at Jul 12, 2025, 08:39 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Leonora

2 months ago

Totally agree with reviewing the risk response plan!

upvoted 0 times

...

Giuseppe

2 months ago

Not sure if adding contingencies will really help.

upvoted 0 times

...

Rosann

2 months ago

I think logging the event is crucial too.

upvoted 0 times

...

Leatha

3 months ago

Definitely need to reassess risks!

upvoted 0 times

...

Geoffrey

3 months ago

Surprised they didn’t see this coming!

upvoted 0 times

...

King

3 months ago

I practiced a question similar to this, and I think reassessing risks is crucial. Option B really stands out to me.

upvoted 0 times

...

Stephanie

3 months ago

I feel like logging the event is important, but it might not prevent future risks. I wonder if option D is enough on its own.

upvoted 0 times

...

Bambi

4 months ago

I'm not entirely sure, but I think adding contingencies might not address the root cause. Maybe option C could help us learn from this?

upvoted 0 times

...

Heike

4 months ago

I remember we talked about the importance of reassessing risks after a setback, so option B seems like a good choice.

upvoted 0 times

...

Brice

4 months ago

Logging the event and updating the project management plan is probably the most straightforward approach. That way, the team can learn from this experience and be better prepared going forward.

upvoted 0 times

...

Fannie

4 months ago

Reassessing the assumptions and constraints is a smart move. That could help uncover other potential risks that haven't been accounted for yet. I'll make sure to consider that option.

upvoted 0 times

...

Latrice

4 months ago

Hmm, I think the key here is to prevent similar risks from occurring in the future. Adding contingencies to other tasks seems like a good way to build in some extra cushion.

upvoted 0 times

...

Malcolm

5 months ago

I'm a bit confused by this question. Should I be focusing on identifying new risks or addressing the specific risk that caused the delay? I'm not sure which approach would be best.

upvoted 0 times

...

Elza

5 months ago

This seems like a straightforward risk management question. I'd start by reviewing the risk response plan to see if there are any lessons learned that could be applied here.

upvoted 0 times

...

Stephanie

6 months ago

I believe logging the event in the issue log and updating the project management plan is crucial for tracking and managing risks.

upvoted 0 times

...

Owen

7 months ago

Adding contingencies to other tasks could also help mitigate similar risks in the future.

upvoted 0 times

...

Melynda

7 months ago

Haha, this reminds me of that time our team forgot to account for leap year in our software release. Gotta love those 'unexpected' risks, am I right? Definitely going with B on this one.

upvoted 0 times