Which of the following can be done to control the size of the Project Board on a project that involves multiple users and suppliers?
Suggested Answer: C
Get Premium PRINCE2-Foundation Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
RY
Ryan
1 year ago
Definitely agree with C, user and supplier groups streamline communication.
PE
Pearlie
1 year ago
Wait, appointing corporate quality assurance? Sounds risky!
CA
Carin
1 year ago
C is a solid choice, keeps things organized!
TW
Twana
1 year ago
I disagree, B could lead to confusion with too many boards.
CO
Corrinne
1 year ago
I think option A makes sense for managing suppliers.
BR
Broderick
1 year ago
Appointing corporate quality assurance for Project Assurance seems like a good idea, but I’m not clear on how that impacts the size of the board itself.
SH
Shelton
1 year ago
Creating user and supplier groups sounds familiar, but I wonder if that would actually reduce the size of the Project Board effectively.
LO
Louis
1 year ago
I remember a practice question about having multiple boards for different stages, but I can't recall if that was the best approach.
QU
Quiana
1 year ago
I think creating separate Project Boards could help manage complexity, but I'm not sure if that would really address all the user and supplier needs.
NO
Noble
1 year ago
This question is testing our understanding of how performance measures like ROI and Residual Income are affected by new investment decisions. I'm confident I can work through the calculations and identify the correct answer.
AL
Allene
1 year ago
Okay, let me see if I can work this out. Gigabit Ethernet can support larger frame sizes, and NAS/SAN traffic often uses jumbo frames to improve performance. I believe the typical MTU size for this scenario is 9000 bytes, but I'll double-check my notes to be sure.
LA
Laquanda
1 year ago
Ah, I see what's going on here. The key is to understand how EIGRP split-horizon works and how to disable it on the tunnel interface. Option A looks like the right choice to fix the routing problem.