Which of the following is an example of an internal project interface?
Correct Answer: C
The correct answer is C. Review points . Internal project interfaces are points of interaction, coordination, handover, control, or decision-making that occur within the project or sponsoring organization. Review points are internal interfaces because they create structured interaction between project participants, such as the project manager, sponsor, project board, assurance function, work package leaders, technical teams, or governance bodies. At review points, the project may assess progress, risks, issues, quality, readiness, acceptance, or authorization to proceed. Option A, regulatory agencies, is an external interface because regulators sit outside the project organization and impose legal or compliance expectations. Option B, community groups, is also external because communities may be affected by the project but are not normally part of the internal project structure. The distinction matters because internal and external interfaces are managed differently. Internal interfaces often rely on governance processes, internal reporting, coordination meetings, escalation routes, and role clarity. External interfaces require stakeholder engagement, regulatory communication, public consultation, contractual coordination, or external reporting. The source question set lists review points as the example of an internal project interface. Reference topics: internal project interface, review points, governance review, stakeholder interface, external interface.
Question 2
According to ISO 21502, why should the organizational strategy be used?
Correct Answer: B
The correct answer is B because organizational strategy should be used to identify, document, and evaluate opportunities, threats, weaknesses, and strengths that can inform future action. Projects should be connected to the organization's strategic direction, business needs, and intended value. Strategy helps determine why a project should exist, what opportunities it should exploit, what weaknesses it may address, what threats it should respond to, and how it supports organizational objectives. This strategic analysis provides the rationale for selecting, prioritizing, authorizing, and shaping projects. Option A is partially aligned with strategic thinking, but it is incorrect because threats cannot simply be eliminated in most project environments; they must be identified, assessed, treated, monitored, and controlled. Option C is incorrect because ISO 21502 recognizes both tangible and intangible value. A project may produce physical deliverables, digital outputs, capability improvements, customer experience improvements, compliance outcomes, or knowledge-based benefits. Strategy is therefore not used to favor only tangible value. The source question set places this question directly under ISO 21502 project management concepts and presents option B as the complete strategic-use statement. Reference topics: organizational strategy, opportunities, threats, strengths, weaknesses, business needs, project justification.
Question 3
According to ISO 21502, what should be considered in order to avoid the repetition of mistakes from previous projects?
Correct Answer: A
The correct answer is A . To avoid repeating mistakes from previous projects, the organization and project team should utilize lessons learned from previous, relevant projects. Lessons learned capture practical knowledge about what went well, what went wrong, what assumptions failed, what risks occurred, which controls were effective, which stakeholder issues emerged, and what should be improved in future projects. Applying lessons learned strengthens planning, governance, risk management, estimation, stakeholder engagement, procurement, quality control, and delivery execution. Hiring subject-matter experts may be useful in some circumstances, especially where specialist knowledge is required, but it does not directly replace the value of organizational learning. Experts can still repeat past mistakes if the project does not actively review and apply prior lessons. The duplicate subject-matter expert options do not change the correct answer because the principle being tested is knowledge reuse. ISO 21502-aligned practice treats lessons learned as an important input for improving current and future project performance. The uploaded source question specifically asks what should be considered to avoid repetition of previous mistakes and identifies lessons learned from previous, relevant projects as the proper response. Reference topics: lessons learned, organizational knowledge, continuous improvement, previous projects, project planning, risk avoidance.
Question 4
Which of the following statements regarding lessons learned is correct?
Correct Answer: B
The correct answer is B . Lessons learned should be captured, compiled, formalized, and stored. Lessons learned are a structured form of organizational knowledge that helps current and future projects improve performance and avoid repeated mistakes. They should capture what was planned, what actually happened, why variances occurred, what worked well, what failed, what actions were effective, and what recommendations should be reused or avoided. Option A is incorrect because lessons learned should not describe only what happened; they should also compare actual performance against the plan and examine causes, effects, and improvement opportunities. Option C is also incorrect because lessons should not be used only after all project activities are complete. They can and should be captured throughout the project so that the team can apply learning immediately where useful. At closure, they are consolidated and stored for future use. PMBOK recognizes a lessons learned register as a project document that records knowledge gained during a project and supports future performance improvement. The uploaded question set identifies capture, compilation, formalization, and storage as the correct statement. Reference topics: lessons learned, knowledge management, formalization, storage, continuous improvement, project closure.
Question 5
According to ISO 21502, what is the purpose of managing delivery?
Correct Answer: A
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.
