PMP · Question #1400
A project manager who is new to an organization is given data that include information related to both project team members and stakeholders. Among other items, this information includes each stakehol
The correct answer is C. Stakeholder analysis. The project manager should use information related to stakeholder roles, projects, and organizational influence in a stakeholder analysis.
Question
A project manager who is new to an organization is given data that include information related to both project team members and stakeholders. Among other items, this information includes each stakeholder's current role, previous and current projects in which they participated, and their level of organizational influence. In what type of analysis should the project manager use this information?
Options
- AQualitative risk analysis
- BRegression analysis
- CStakeholder analysis
- DDecision tree analysis
How the community answered
(38 responses)- A3% (1)
- B11% (4)
- C79% (30)
- D8% (3)
Why each option
The project manager should use information related to stakeholder roles, projects, and organizational influence in a stakeholder analysis.
Qualitative risk analysis assesses the probability and impact of identified risks and does not primarily focus on the attributes or influence of stakeholders themselves.
Regression analysis is a statistical technique used to model the relationship between a dependent variable and one or more independent variables, not a method for identifying and characterizing project stakeholders.
Stakeholder analysis is the process of identifying project stakeholders and analyzing their characteristics, interests, influence, and potential impact on the project. The provided information, such as roles, previous projects, and organizational influence, is precisely what is gathered and used during this analysis to develop effective engagement strategies.
Decision tree analysis is a tool used to help make choices under conditions of uncertainty by mapping out possible outcomes and their associated probabilities and values, not for analyzing stakeholder attributes.
Concept tested: Stakeholder management, stakeholder analysis, influence mapping
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
6
Bao N.Jan 10, 2026C is correct, confirmed on multiple practice sets. The stem gives it away with role, project history, and level of organizational influence, which are classic inputs for mapping stakeholders on a power/interest or influence/impact grid. A trips a few people because risk data can sound organizational, but risk analysis does not care about which projects someone worked on before. If you see influence and participation history together, lock in stakeholder analysis and move on.
Mei-Ling H.Feb 4, 2026Leaned toward A because data felt risk related, but role plus influence means stakeholder analysis.
Zlatan X.Feb 5, 2026Agreed, and the program governance angle is that stakeholder analysis at the portfolio level feeds influence mapping across components, not just within a single project risk register.
Zlatan X.Jan 22, 2026C is correct, obviously. The stem almost gives it away by listing role, project history, and influence level, which are the exact inputs for mapping stakeholder engagement and power/interest positioning across the program ecosystem. A is the trap here because people see the word "level" and jump to risk probability scoring, but this data set has nothing to do with uncertainty or threat modeling.
Luis F.Feb 1, 2026C is the right call but honestly the question throws you off with all that project history stuff. I almost went with B because regression analysis uses historical data, but the stakeholder roles and influence level is the dead giveaway for stakeholder analysis.
Orla P.Jan 23, 2026Got C on my exam last spring. The clue is right there in the data they hand you, roles, project history, and influence levels are the bread and butter of stakeholder analysis, so A, B, and D are just distractors.