Free Preparation Discussions
MENU
PECB ISO 21502 Lead Project Manager Exam Questions
- Topic 1: Fundamental principles and concepts of project management: Covers the core principles, concepts, and foundational elements of project management based on ISO 21502, providing the basis for effective project execution.
- Topic 2: Integrated project management practices: Focuses on applying integrated project management practices to coordinate project activities, resources, governance, and stakeholder engagement throughout the project lifecycle.
- Topic 3: Individual management practices for a project: Explains the key management practices used to plan, monitor, control, and deliver individual project components in alignment with ISO 21502 guidance.
Free PECB ISO 21502 Lead Project Manager Exam Actual Questions
Note: Premium Questions for ISO 21502 Lead Project Manager were last updated On Jun. 29, 2026 (see below)
Scenario:
Leute is a low-cost airline, headquartered in Wien, Austri
a. The company aims to offer passengers optimal options regarding its services and gain the lead role among other competitors in the airline industry. Recently, Leute experienced a major drop in revenue due to negative reviews from customers in various online platforms. To increase its profit and enhance customer satisfaction, the company decided to expand its in-flight services by offering entertainment, such as movies, audio books, and games, food for purchase in economy and full meals in premium cabins, and comforts, such as blankets and pillows. For the implementation of this project and future projects of the airline, the CEO of Leute, Michaele Wagner, decided to follow the guidelines of ISO 21502 on project management.
Initially, Allison, the project manager, created a short document in which she justified and summarized all project aspects, including: the nature and purpose of the project, the objectives of the project, key milestones of the project and the time needed to complete the project, and the audience that the project targets.
Afterward, Allison held a meeting with Michaele during which she presented this document and briefly explained each of its points. After a considerable amount of analysis and discussions, the project initiation was approved by Michaele. In addition, a team of eighteen members was authorized to start with the project activities.
While undertaking the project activities, Allison ensured that each work package takes longer than 8 hours, but less than 80 hours, so that they would be completed in 1 to 10 working days. In addition, during this phase, several changes were made in the predefined aspects of the project, which were approved by Nick Todd, the project sponsor. For instance, initially, the project delivery was set to be completed after six months. However, considering how the project was implemented and the time required for the completion of each phase, the deadline for the project completion was postponed for another two months. These changes were also reflected in the business case, which was updated accordingly.
A month after the project execution began, Allison conducted an earned value analysis to measure the progress of the project up to that stage. She measured how efficiently the work was being performed with regard to its budgeted cost, after which she concluded that it was going according to the plan. Moreover, she organized a meeting with relevant project stakeholders in order to communicate the progress report to them.
Based on scenario 3, Allison ensured that the size of each work package was longer than 8 hours, but less than 80 hours in order to complete them in 1 to 10 working days. What rule did Allison follow in this case?
The correct answer is B. The 8/80 rule. This rule is used when decomposing work into work packages or activities. It states that a work package should generally require no less than 8 hours and no more than 80 hours of effort. In practical terms, this means the work package should be large enough to avoid excessive administrative fragmentation, but small enough to be estimated, assigned, monitored, and controlled effectively. In Allison's case, she ensured that each work package took longer than 8 hours but less than 80 hours and could be completed within 1 to 10 working days. That is a direct application of the 8/80 rule. The 1/10 rule is related but expressed differently: work packages should usually represent between 1% and 10% of the project duration or effort, depending on the planning method. The reporting period rule links work package size to the frequency of performance reporting. The scenario specifically refers to the 8-hour and 80-hour thresholds, so the correct rule is unmistakably the 8/80 rule.
Reference topics: work breakdown structure, work package sizing, 8/80 rule, activity planning, scope decomposition.
Scenario:
Oakniture is a furniture manufacturer located in Bristol, England. It is known for its kitchen tables made out of different types of wood, such as chestnut, walnut, and oak. In early 2022, Lana, one of the senior researchers of the company, conducted a feasibility study to determine if there is a market for oak wood coffee tables, which indicated that the demand for oak wood coffee tables is relatively high. As such, Lana prepared a project brief and presented it to the top management of the company. The project brief included information on the project context and project objectives. After several discussions, the top management agreed that the project should be undertaken, but lastly, they asked Lana about the project duration. Lana claimed that the project duration cannot be determined and such information was not provided in the project brief; however, she added that the project duration will mainly depend on the competencies of the project team and on Oakniture's suppliers of wood.
Following that, the top management initiated the project and assigned Tom, the operations director, as the project manager, and Lana as the project sponsor. To manage the project, they decided to use the guidelines of ISO 21502.
Initially, Tom defined the governance and management framework alone, and then he mobilized the team and assigned the roles and responsibilities to each team member. In addition, Tom and the project team identified the stakeholders and developed the project plan. To ensure effective management of each project phase, Tom used a work breakdown structure (WBS) to organize project activities. Tom presented the project activities in the WBS by linking task dependencies and showing project milestones. In addition, Tom calculated the duration of each work package by determining the early start and early finish dates. Regarding the relationship between work packages, Tom required the project team to perform tasks in the predetermined order, regardless of any resource shortages they might experience.
A week after the project implementation began, Tom collected and analyzed data regarding the progress of the project. To keep everyone up to date, he held a meeting with Lana and project stakeholders.
Lana did not provide any information regarding the project duration in the project brief. Is this acceptable?
The correct answer is B. The project brief should include information about project duration, at least at a high level or as an initial estimate. A project brief is used to summarize the proposed project so that decision-makers can evaluate whether it should be initiated. It should provide enough information to understand the project context, objectives, rationale, high-level scope, target outcomes, key milestones, time frame, and major assumptions or constraints. Duration is especially important because it affects resource planning, cost estimation, feasibility, supplier coordination, governance decisions, and expected benefit timing. Lana included project context and objectives, but omitted duration and stated that it could not be determined. While exact duration may not be fully known at the brief stage, a preliminary time frame, assumption-based estimate, or duration range should still be provided. Her verbal statement during discussions does not replace properly documenting the duration in the project brief. A decision to initiate the project should be based on recorded information, not only informal explanation. Therefore, the omission was not acceptable. The source scenario explicitly states that duration was missing from the project brief and asks whether that omission is acceptable.
Reference topics: project brief, project duration, pre-project activities, project initiation, high-level planning, feasibility.
According to ISO 21502, what does a project plan include, among others?
The correct answer is C. Both A and B. A project plan should include, among other elements, the project scope, risks, assumptions, and constraints. The project plan is the integrated reference document that describes how the project will be executed, monitored, controlled, and closed. Scope defines what the project is expected to deliver and the boundaries of the work. Risks identify uncertain events or conditions that could affect project objectives. Assumptions describe factors considered true for planning purposes, even though they may later require validation. Constraints define limiting conditions, such as fixed deadlines, budget ceilings, regulatory obligations, resource limits, contractual requirements, or technology restrictions. These elements are interconnected: assumptions and constraints influence scope, risk exposure, schedule, cost, quality, and resource planning. A project plan that includes only scope and risks would omit the planning logic behind them. A plan that includes only assumptions and constraints would not adequately define the deliverables or uncertainty profile. Therefore, both sets of information are necessary for sound integrated project management.
Reference topics: project plan, scope, risks, assumptions, constraints, integrated planning.
According to ISO 21502, what should the process of controlling risks involve?
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.
Scenario:
Headquartered in Geneva, Switzerland, DND is one of the largest worldwide automakers. It first gained global recognition after introducing a sports car, which quickly became highly demanded by sports car lovers around the world. Alec Law, the CEO of DND, and his management team recently decided to embark on a new project, i.e., the production of alternative fuel cars, which would use an alternative fuel source instead of traditional petroleum fuels, as the other cars of the company do, in order to promote sustainable and low-carbon transportation. For the implementation of this project, the company decided to follow the guidelines of ISO 21502 on project management.
During the development of the project governance framework, the company took into account several factors, including, among others, the legal context of stakeholders. In the project governance, the company also included oversights on the management frameworks and the project life cycle. In order to determine the project life cycle, the external environment was considered, including information on studies that related to similar projects. In addition, the company decided to separate this project governance from its overall governance.
Moreover, the company developed a project organization, where the roles, responsibilities, and authorities in the project were defined. In addition, the responsibilities of the project office and project assurance, among others, were defined. The project organization also included a customer representative. Once the project organization was developed and approved by the project board, it was communicated only to the project team.
As the project was entering its design stage, the project board made a change in the structure of the project organization since one of the work package leaders had resigned from the project in order to be involved in another project of the company.
During the development of the project governance framework, DND considered the legal context of stakeholders. Is this acceptable?
Yes. Considering the legal context of stakeholders is acceptable when developing a project governance framework. Governance establishes how a project is authorized, directed, monitored, controlled, escalated, and aligned with the sponsoring organization's objectives. Because projects operate within a wider environment, governance cannot be based only on the organization's internal legal position. It must also reflect stakeholder-related legal, regulatory, contractual, ethical, safety, environmental, and compliance conditions. In DND's case, the production of alternative fuel cars may involve vehicle safety regulations, environmental standards, emissions requirements, supplier contracts, customer protection obligations, and approval requirements from public authorities. Stakeholders such as regulators, customers, suppliers, investors, communities, and environmental bodies may all impose legal expectations that directly affect the project's scope, risks, requirements, acceptance criteria, and decision-making controls. Therefore, including stakeholder legal context strengthens governance and reduces exposure to non-compliance, rework, delay, and reputational damage. The PMBOK definition of project governance also supports this logic by describing governance as the framework, functions, and processes that guide project management activities to create a unique product, service, or result that meets organizational strategic and operational goals.
Reference topics: project governance framework, stakeholder context, legal environment, external factors, governance alignment.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Currently there are no comments in this discussion, be the first to comment!