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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

PMI-RMP Exam - Topic 4 Question 47 Discussion

Adrian is a project manager for a new project using a technology that has recently been released and there's relatively little information about the technology. Initial testing of the technology makes the use of it look promising, but there's still uncertainty as to the longevity and reliability of the technology. Adrian wants to consider the technology factors a risk for her project. Where should she document the risks associated with this technology so she can track the risk status and responses?
A) Risk register
B) Risk low-level watch list
C) Project scope statement
D) Project charter

PMI-RMP Exam - Topic 4 Question 47 Discussion

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

Adrian is a project manager for a new project using a technology that has recently been released and there's relatively little information about the technology. Initial testing of the technology makes the use of it look promising, but there's still uncertainty as to the longevity and reliability of the technology. Adrian wants to consider the technology factors a risk for her project. Where should she document the risks associated with this technology so she can track the risk status and responses?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Lai at May 06, 2022, 01:38 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Roosevelt
9 months ago
I’d say the risk low-level watch list is too informal for tracking risks.
upvoted 0 times
...
Tegan
9 months ago
Wait, is there really enough info to even assess the risks properly?
upvoted 0 times
...
Cortney
9 months ago
I disagree, the project scope statement is more about deliverables, not risks.
upvoted 0 times
...
Jolene
9 months ago
I think the project charter could work too, but not as detailed.
upvoted 0 times
...
Joanne
9 months ago
Definitely the risk register! That's where all risks should go.
upvoted 0 times
...
Goldie
10 months ago
The project charter seems too high-level for this. I remember it’s more about the overall project goals and stakeholders, not specific risks. Risk register feels like the best option.
upvoted 0 times
...
Junita
10 months ago
I practiced a question similar to this, and I believe the project scope statement is more about defining the project rather than tracking risks. So, I think it’s not the right choice.
upvoted 0 times
...
Sophia
10 months ago
I’m not so sure about that. I remember something about a low-level watch list, but I can't recall if that's for risks or something else.
upvoted 0 times
...
Sabina
10 months ago
I think the risk register is definitely the right place for Adrian to document those risks. It’s where we track all identified risks and their responses, right?
upvoted 0 times
...
Selene
10 months ago
I'm feeling a little confused by the context and the specific requirements here. Let me re-read the question carefully and make sure I understand exactly what I need to do before I start typing anything.
upvoted 0 times
...
Alisha
10 months ago
My gut says "Overlapped" scheduling isn't the right answer, but I can't pinpoint why. It feels like something we went over.
upvoted 0 times
...
Lenna
10 months ago
I'm not entirely sure about this one. The question mentions something about the Live Media and the system's graphics card, but I'm not sure how that relates to the systems needing to be on the same subnet. I'll have to think this through carefully.
upvoted 0 times
...

Save Cancel