ISO-21502-Lead-Project-Manager PECB ISO 21502 Lead Project Manager Exam Free Practice Exam Questions (2026 Updated)

The correct answer is B. He should keep them satisfied . In a power/interest matrix, stakeholders with high power and low interest should be kept satisfied. They have enough authority or influence to affect the project significantly, but they may not require constant detailed involvement because their level of direct interest is limited. The project manager should provide them with appropriate information, address their concerns, prevent dissatisfaction, and ensure their expectations are managed without overloading them with unnecessary detail. In this scenario, tournament organizers have high power because the project is linked to promotion at a major gaming tournament. They may influence timing, launch conditions, exposure, or acceptance of promotional arrangements. However, because their interest is classified as low, they do not need the intensive engagement used for high-power, high-interest stakeholders. Option A, manage closely, is normally used for stakeholders with both high power and high interest. Option C, monitor, is used for low-power, low-interest stakeholders. The source scenario explicitly classifies tournament organizers as low interest and high power, making “keep them satisfied” the correct stakeholder strategy.

Reference topics: stakeholder engagement, power/interest matrix, high power low interest, stakeholder strategy, communication planning.

The correct answer is C. Project sponsor and project board . The project manager normally reports to the project sponsor and, where established, the project board. These governance roles provide direction, oversight, authorization, and decision-making authority for the project. The sponsor maintains the business link between the project and the sponsoring organization, while the project board may represent broader governance interests, including business, user, supplier, technical, or organizational perspectives. Reporting to these roles enables performance review, escalation, approval of significant changes, risk-based decisions, and continued justification. Option A is too narrow and too rigid because the project manager does not report only to top management in every project. Reporting arrangements depend on the project governance structure. Option B is also too broad because key stakeholders may receive information, but they are not necessarily the formal reporting authority. Stakeholder communications and governance reporting are related but not identical. A project manager may communicate with many stakeholders, but formal accountability reporting is directed to the sponsor and project board. The uploaded source question identifies sponsor and project board as the correct reporting destination.

Reference topics: project manager reporting, project sponsor, project board, governance reporting, accountability, project oversight.

No. The project organization should be communicated to everyone involved in the project, not only to the project team. A project organization defines the roles, responsibilities, authorities, decision rights, reporting relationships, escalation routes, and interfaces needed to direct and manage the project. If this structure is communicated only to the project team, other involved parties may not understand how the project is governed, who has authority, who is accountable for decisions, how issues are escalated, or how coordination should occur. In the DND scenario, the project organization included the project office, project assurance, a customer representative, the project board, and work package leadership. These roles are not limited to the delivery team; they are part of the broader governance and management structure. Therefore, they must understand the organization model and their relationship to it. Communicating the structure only to the team creates ambiguity, weakens accountability, and may disrupt assurance, customer involvement, and governance control. The PMBOK also treats project communications as the processes required to ensure project information is planned, collected, created, distributed, stored, monitored, and disposed of appropriately.

Reference topics: project organization, communication, roles and responsibilities, stakeholder involvement, governance interfaces.

The correct answer is C . Controlling risks involves ensuring that responses to negative risks minimize disruption to the project while responses to positive risks maximize beneficial impact. Risk control is not merely the identification or planning of risks; it is the ongoing activity of tracking risk exposure, monitoring risk response effectiveness, identifying new risks, reassessing existing risks, and ensuring that treatment actions remain suitable. Negative risks, or threats, should be managed so that their probability or impact is reduced, transferred, avoided, or otherwise controlled. Positive risks, or opportunities, should be managed so that their probability or beneficial impact is enhanced, exploited, shared, or accepted where appropriate. Option A refers more to risk categorization or analysis, where common causes can help prioritize treatment. Option B describes risk response planning, where options and actions are developed before implementation. Control focuses on whether those responses are working and whether the project remains within acceptable risk exposure. PMBOK similarly describes risk monitoring as tracking identified risks, identifying and analyzing new risks, and evaluating risk process effectiveness. The uploaded question set records this ISO 21502 risk-control item.

Reference topics: risk control, risk responses, threats, opportunities, disruption minimization, beneficial impact maximization.

The correct answer is C. Coordination . Ross addressed the communication need for coordination when he determined that relationships among project team members needed to be established to ensure productive work. Coordination communication supports collaboration, alignment, sequencing of work, dependency management, issue resolution, and day-to-day interaction among team members. In Mallebare’s project, the team must design and manufacture mousepads within three months for promotion at a major gaming tournament. Such a tight deadline requires team members to understand not only their individual tasks, but also how their work connects with others. Establishing relationships improves responsiveness, trust, information flow, and joint problem-solving. Option A, status, concerns reporting progress, performance, milestones, risks, or completion information. Option B, responsibility, concerns clarifying who is accountable for specific tasks, deliverables, or decisions. Ross’s focus was not merely reporting status or assigning responsibility; it was building working relationships that enable productive collaboration. That is coordination. The source question directly associates the establishment of relationships among team members with the communication need being tested.

Reference topics: communication needs, coordination, team interaction, collaboration, project communication planning.

The correct answer is B. Cost performance index (CPI) . The scenario states that Allison measured how efficiently the work was being performed with regard to its budgeted cost. That wording corresponds directly to CPI, which is an earned value management metric used to assess cost efficiency. CPI compares the value of completed work with the actual cost incurred for that work. In standard earned value terms, CPI is calculated as EV / AC , where EV is earned value and AC is actual cost. A CPI of 1.0 means the project is performing exactly according to the cost plan; a value below 1.0 indicates cost inefficiency, and a value above 1.0 indicates cost efficiency. Cost variance (CV), by contrast, shows the amount of budget surplus or deficit at a point in time, calculated as EV minus AC. Actual cost (AC) is simply the cost incurred for performed work; it does not measure efficiency by itself. PMBOK defines CPI as a measure of cost efficiency expressed as the ratio between earned value and actual cost, reinforcing why CPI is the correct metric.

Reference topics: earned value analysis, cost performance index, cost efficiency, earned value, actual cost, cost control.

The correct answer is A. Informal . The communication methods described in the scenario—ad hoc discussions, notes, and text messages—are informal communication methods. Informal communication is typically flexible, rapid, conversational, and less structured than formal reports, contractual notices, approved minutes, governance submissions, or official project documents. Ross planned ad hoc discussions for complex and personal cases because direct informal interaction allows immediate clarification, natural language, and faster exchange of nuanced information. He also planned notes and text messages for simple and factual information, which supports quick transmission without the structure of formal reporting. Option B is incorrect because the scenario does not describe formal communication mechanisms such as official reports, controlled documents, steering committee papers, signed approvals, or contractual correspondence. Option C is not the best answer because both examples given are informal in nature. The communication plan is still a formal planning artifact, but the communication types selected within it are informal methods. The uploaded source scenario specifically frames the question around ad hoc discussions, notes, and text messages.

Reference topics: communication planning, informal communication, ad hoc discussion, text messages, communication methods, project information flow.

The correct answer is C. Spreadsheets . A work breakdown structure can be presented in several formats, depending on the project’s needs, reporting style, and level of detail. When deliverables, tasks, work packages, identifiers, responsibilities, durations, costs, or status information are arranged in rows and columns, the format is a spreadsheet-based WBS. This approach is practical for tabular decomposition, filtering, sorting, assigning owners, linking estimates, and integrating with cost or schedule information. A list format would normally present deliverables or work packages in an indented hierarchical list without the tabular structure described in the question. A flowchart would show graphical relationships, movement, or process logic, not simply deliverables and tasks arranged in rows and columns. Therefore, the wording “columns and rows” clearly indicates a spreadsheet format. PMBOK also recognizes the WBS dictionary as a document that gives detailed information about deliverables, activities, and planning for each WBS component, which is commonly supported by structured tabular information. The uploaded source question presents “Spreadsheets” as the format associated with rows and columns.

Reference topics: work breakdown structure, WBS formats, spreadsheet WBS, deliverables, tasks, scope decomposition.

The correct answer is A . Project benefits should be maintained by taking corrective, and when required, preventive actions when deviations from planned benefits occur. Maintaining benefits requires active management, not passive observation. If expected benefits are not being achieved, are delayed, or are at risk, the organization should identify the cause of deviation and take action to restore or protect benefit realization. Corrective action addresses an existing deviation, while preventive action reduces the likelihood of future deviation. Option B, collecting performance measurements for each benefit, is important for monitoring, but measurement alone does not maintain benefits. Option C, reporting and communicating benefit status, supports visibility and decision-making, but communication alone does not correct underperformance. Maintaining benefits means acting on benefit information to preserve expected value. This may involve adjusting adoption plans, improving operational readiness, addressing stakeholder resistance, changing processes, providing training, or revising transition arrangements. The emphasis is on ensuring that project outcomes continue to support the desired benefits.

Reference topics: benefits management, corrective action, preventive action, planned benefits, benefit deviation, benefit realization control.

The correct answer is B. Reintroducing a familiar practice . Adaptive change refers to a comparatively low-complexity form of change where people are asked to return to, adjust, or apply something already familiar. It usually does not require a major shift in culture, mindset, technology, or organizational identity. Because the practice is already known, resistance may be lower than with more innovative or transformational changes, although communication, reinforcement, and stakeholder engagement are still required. Option A, introducing a practice new to the practitioners, is more disruptive because the affected people have no direct familiarity with the practice. Option C, introducing a practice that is new to the organization but not the industry, is closer to an innovative or transitional change because the organization must adopt something externally established but internally unfamiliar. Adaptive change is therefore associated with reintroducing or adjusting known practices rather than creating a radically new way of working. In project management, understanding the type of change helps determine communication, training, stakeholder engagement, transition support, and resistance-management needs. The uploaded source lists this question under the ISO 21502 question set and provides these three alternatives.

Reference topics: adaptive change, organizational change, stakeholder readiness, transition management, change complexity.

The correct answer is A . Managing delivery is concerned with defining the required outputs and outcomes, then planning and implementing their delivery so that the project can achieve its intended outcomes and enable benefits realization. Delivery management bridges the gap between project planning and the creation of usable outputs. It ensures that the project’s scope, outputs, acceptance expectations, work packages, resources, dependencies, quality needs, and implementation activities are organized to produce what the project was established to deliver. Option B relates more closely to closure and post-delivery transition, because demobilizing remaining resources and facilities occurs when project work is being concluded. Option C describes continued business justification, governance review, or project control, where the organization verifies whether the project remains relevant, acceptable, and aligned with stakeholder expectations and risk tolerance. Managing delivery is therefore more operational and output-focused: it turns the approved plan and requirements into controlled execution. It also supports benefits indirectly by ensuring that outputs are fit for use and capable of producing intended outcomes. The source question set gives option A as the complete purpose statement for managing delivery.

Reference topics: managing delivery, outputs, outcomes, benefits realization, implementation planning, delivery control.

The correct answer is A . The purpose of reporting is to provide the current status, forecast, and analysis of the project. Reporting converts project management information into useful, structured communication for decision-making and control. It should explain where the project currently stands, what is expected to happen next, what variances or trends exist, and what decisions or actions may be required. Effective reports may cover scope, schedule, cost, quality, resources, risks, issues, changes, stakeholder engagement, benefits, and overall confidence. Option B is related to communication management because project communications should meet stakeholder information needs, but reporting specifically focuses on presenting project status, forecasts, and analysis. Option C is incorrect because reporting is not limited to the end of the project; it occurs throughout the project life cycle. Waiting until completion would prevent timely governance decisions, corrective actions, escalation, and stakeholder alignment. PMBOK also supports this by describing project reporting as collecting performance data, producing performance measures, and reporting and disseminating performance information. The uploaded question set identifies current status, forecast, and analysis as the reporting purpose.

Reference topics: project reporting, current status, forecasting, performance analysis, project control, stakeholder information.

The correct answer is B. Effectiveness of communication channels . Ross selected communication methods according to the nature and complexity of the information being transmitted. He planned ad hoc discussions for complex and personal matters, and notes or text messages for simple and factual information. This reflects the principle that communication channels differ in richness, speed, feedback capability, personal focus, and suitability for the message. Richer channels, such as direct discussion, are more effective when information is ambiguous, sensitive, complex, or requires immediate feedback. Leaner channels, such as notes or text messages, are suitable for simple, factual, routine, or low-risk information. Ross’s explanation that the model allows faster processing of information and uses natural language directly supports the idea of channel effectiveness. Option A is incorrect because the scenario does not focus on cultural interpretation, language barriers, or cross-cultural norms. Option C is also incorrect because the gulf of execution and evaluation concerns user interaction and usability, not the selection of communication media in project communication planning.

Reference topics: communication planning, communication channels, channel effectiveness, information complexity, stakeholder communication.

The correct answer is C . A project interface is the area, point, or zone where different stakeholders, teams, systems, organizations, functions, phases, or work packages meet and interact. Interfaces are important because many project issues arise not inside a single work area, but at the boundaries between areas of responsibility. Examples include the handover between design and construction, coordination between the project team and operations, engagement between supplier and customer, or decision points between project governance and delivery teams. Option A is incorrect because control mechanisms are part of project monitoring and control, not the definition of an interface. Option B is also too narrow because an interface may exist between phases, but it is not simply the transition period between phases. Interfaces can be organizational, technical, contractual, informational, procedural, or stakeholder-based. Effective interface management clarifies responsibilities, communication channels, dependencies, handover criteria, escalation paths, and decision rights. Poorly managed interfaces create ambiguity, delays, rework, conflict, and quality problems. The uploaded source question identifies the interaction zone between stakeholders as the correct definition of project interface.

Reference topics: project interface, stakeholder interaction, coordination, handover, dependencies, interface management.

The correct answer is A because, for a project that exists within a program, the program manager can act as the representative of the sponsoring organization or higher-level authority. A program coordinates related projects to obtain benefits and control that would not be available if the projects were managed separately. Therefore, a project within a program should align with program objectives, governance, benefits, dependencies, and reporting requirements. In that context, the project sponsor may report to, seek direction from, or coordinate with the program manager because the program manager represents the broader governance layer within which the project operates. Option B is incorrect because it reverses the authority relationship: the program manager usually provides higher-level coordination over program components, not subordinate reporting to an individual project sponsor. Option C is too rigid because not every project sponsor must report directly to top management; the reporting relationship depends on the organizational and governance context. PMBOK similarly distinguishes project management from program management and notes that program management seeks benefits and control not available when components are managed individually. The scenario question is recorded in the uploaded source set.

Reference topics: project within a program, program manager, sponsoring organization, project organization structure, governance hierarchy.

Yes. The project office can perform various activities to support the project manager and the project team. A project office is normally established to provide coordination, administrative support, documentation control, information management, reporting support, method guidance, scheduling assistance, and support for governance processes. Its purpose is to improve consistency, visibility, and control across the project. In the Exhibix scenario, the project office assisted the project manager and team by providing administrative support and managing project information. This is consistent with the supporting role of a project office. It does not create a conflict of interest merely because the project office is involved in project activities. The important requirement is that its role, authority, interfaces, and responsibilities are clearly defined within the project organization. The sponsor remains accountable for business direction and continued justification, while the project manager manages day-to-day delivery. The project office supports both governance and delivery by ensuring information is organized, accessible, timely, and controlled. The PMBOK also supports the importance of appropriate project information management as part of project communications management.

Reference topics: project office, project support, administrative support, project information management, project organization.

The correct answer is A . The purpose of benefit management is to assist the sponsoring organization and the customer in realizing the desired benefits of a project from the project’s outcomes. Benefits are not created simply because deliverables have been produced. Deliverables must be used, adopted, integrated, or operated in a way that produces outcomes, and those outcomes must create measurable advantages. Benefit management therefore connects the project’s outputs to organizational value. It identifies expected benefits, defines how they will be measured, assigns ownership, monitors benefit realization, and supports corrective action when benefits are not being achieved. Option B describes continued business justification, which helps determine whether the project remains relevant and beneficial in context, but it is not the full purpose of benefit management. Option C describes review or control of continued alignment, stakeholder expectations, and risk acceptability. Benefit management is specifically focused on realizing desired benefits from outcomes, often extending beyond project closure into operational use.

Reference topics: benefit management, outcomes, benefits realization, sponsoring organization, customer value, project outputs.

The correct answer is C because it is the statement that is not correct. The reporting approach and methods should be planned and documented early enough to guide project communications and control, not at the end of the project. Reporting needs to support decision-making throughout the project life cycle, so the project manager should define what will be reported, to whom, how often, in what format, by which method, and using which project information sources. Option A is correct because reporting should align with current project documentation and be based on analysis of project management information. Reports must reflect reliable data, not informal impressions. Option B is also correct because reporting should be monitored and adjusted as stakeholder needs, governance expectations, project complexity, or information requirements change. Reporting is not static; it must remain useful to recipients. Option C would make reporting ineffective because planning it at the end would remove its value for monitoring, forecasting, escalation, and corrective action during delivery. The uploaded question set frames this as a “NOT correct” reporting question and includes option C as the incorrect reporting practice.

Reference topics: project reporting, reporting approach, project information, communication planning, report recipients, monitoring and adjustment.

The correct answer is C . Proposal requests are procurement documents used to obtain supplier proposals when the buyer needs a proposed solution, approach, technical method, commercial offer, or delivery strategy for the required work. In procurement practice, a request for proposal is appropriate when the buyer knows the business need or desired outcome but wants suppliers to propose how they would meet that need. The evaluation is usually based on more than price; it can include technical quality, methodology, supplier capability, risk, schedule, innovation, compliance, and value. Option A is not correct because the request normally comes from the buyer or customer side, not from the contractor to the supplier as a general definition. Option B describes a price-focused request, closer to a request for quotation or bid, where the solution is already clearly defined and price is the main selection criterion. Proposal requests are especially useful where the scope is complex, the solution is not fully predetermined, or supplier expertise is needed to shape the delivery approach. The uploaded source text shows this question and the partial alternatives, with the concept clearly positioned under procurement practices.

Reference topics: procurement, request for proposal, supplier proposal, procurement documentation, supplier selection.