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

PMI-RMP Exam - Topic 8 Question 108 Discussion

Actual exam question for PMI's PMI-RMP exam
Question #: 108
Topic #: 8
[All PMI-RMP Questions]

An experienced and the only developer on a software implementation project will be on leave for several weeks. The risk of this critical resource's availability was added to the risk register. Contingencies were made for a support developer to job shadow this resource, depending on how things go prior to their leave. The project team was pleased with the backup plan and the new resource was able to shadow for a few weeks.

What should the risk manager do next?

Show Suggested Answer Hide Answer
Suggested Answer: B

Once the contingency plan has been executed (e.g., the backup resource has shadowed the experienced developer), it is crucial to continuously monitor and manage any residual or secondary risks that may arise. These risks could include the backup resource's ability to perform effectively or the potential impact of the original developer's absence on project timelines. By updating the risk register and maintaining communication with the project team, the risk manager ensures that the project remains on track and that any new risks are promptly addressed, in alignment with PMI's best practices for ongoing risk management.


Contribute your Thoughts:

0/2000 characters
Annamae
9 hours ago
Surprised they didn't hire someone permanent right away!
upvoted 0 times
...
Gladys
6 days ago
A seems too quick. The risk isn't fully resolved yet.
upvoted 0 times
...
Kris
11 days ago
I think B is the best option. Continuous monitoring is key!
upvoted 0 times
...
Clarinda
16 days ago
Haha, the experienced dev better not take a vacation to the Bahamas!
upvoted 0 times
...
Cassie
21 days ago
B is the way to go. Gotta keep an eye on those residual risks.
upvoted 0 times
...
Dick
26 days ago
D is a good option too. Hiring another developer as a contingency plan is smart.
upvoted 0 times
...
Lisandra
1 month ago
B is the correct answer. Continuously monitoring the backup resource is crucial.
upvoted 0 times
...
Vanesa
1 month ago
I’m not confident about this, but I think option D might be too reactive. Shouldn't we focus on the backup resource first before hiring someone else?
upvoted 0 times
...
Ettie
1 month ago
I’m leaning towards option C because hiring a permanent developer could provide long-term stability, but I wonder if that’s overkill for just a few weeks.
upvoted 0 times
...
Gianna
2 months ago
I think we practiced a similar question where we had to decide on risk management strategies. I feel like updating the risk register is important, but I’m torn between A and B.
upvoted 0 times
...
Carmelina
2 months ago
I'm a little unsure on this one. Do we really need to hire another permanent developer? That seems like overkill if the experienced developer is just going to be out for a few weeks. I'm torn between options B and D.
upvoted 0 times
...
Kristofer
2 months ago
I feel pretty confident about this one. The risk has already occurred, so I think the best approach is to update the risk register and closely monitor the backup resource to address any secondary risks that come up.
upvoted 0 times
...
Willow
2 months ago
I remember we discussed the importance of monitoring residual risks, so option B seems like a good choice, but I'm not entirely sure if we should close the risk just yet.
upvoted 0 times
...
Patti
3 months ago
I’m leaning towards B too. Communication is crucial for project success.
upvoted 0 times
...
Eun
3 months ago
Okay, let's think this through step-by-step. The risk has already materialized, so we need to update the register. Then, we should continuously monitor the backup resource and communicate any residual or secondary risks. Hiring another permanent developer doesn't seem necessary based on the information provided.
upvoted 0 times
...
Helga
3 months ago
Okay, let's see here. The key seems to be managing the risk and ensuring the project is covered during the experienced developer's absence. I'm leaning towards option B, but I'll need to think it through a bit more.
upvoted 0 times
...
Brittney
3 months ago
Hmm, this seems like a tricky one. I'll need to carefully consider the options and think through the potential implications of each approach.
upvoted 0 times
Shad
2 months ago
Agreed! We can't just assume everything will be fine.
upvoted 0 times
...
Pearline
2 months ago
I think option B is the best. Continuous monitoring is key.
upvoted 0 times
...
...

Save Cancel