According to the PMBOKGuide, when three estimates are provided (Most Likely, Optimistic, and Pessimistic), the expected duration is calculated using Three-Point Estimating. Unless a " Beta " or " PERT " distribution is explicitly mentioned, the standard practice in many exam contexts for a simple " expected duration " is to use the Beta Distribution (PERT) formula, which provides a weighted average.
The formula for the Beta Distribution (PERT) is:
$$E = \frac{O + 4M + P}{6}$$
Where:
O (Optimistic / Best-case) = 2 weeks
* M (Most Likely) = 4 weeks
* P (Pessimistic / Worst-case) = 12 weeks
Calculation:
Multiply the Most Likely estimate by 4: $4 \times 4 = 16$
* Add the Optimistic and Pessimistic estimates: $16 + 2 + 12 = 30$
* Divide the total by 6: $30 / 6 = 5$
Therefore, the expected duration is 5 weeks.
Note on Triangular Distribution:
If the question had required the Triangular Distribution ($E = \frac{O + M + P}{3}$), the result would have been $18 / 3 = 6$ weeks. However, the Beta/PERT distribution is the industry standard for increasing the accuracy of duration estimates by weighting the " Most Likely " scenario more heavily, and " 5 weeks " is the statistically preferred answer in PMI-aligned testing for this specific data set.

According to the PMBOK Guide, specifically the Perform Integrated Change Control (PICC) process, any change to a project baseline (scope, schedule, or cost) must be formally reviewed and processed.
Why Choice A is correct: The SME is suggesting two significant changes: a change in prioritization (Scope
/Resource baseline) and a reduction in the schedule (Schedule baseline). Even though the change is intended to " mitigate " a compliance need, the Project Manager cannot simply update the plan. They must follow the formal change management plan. This involves:
Assessing the impact of the SME ' s suggestion on all project constraints.
Documenting the request in the Change Log.
Presenting the change to the Change Control Board (CCB) or the relevant authority for approval or rejection.
This ensures that the " mitigation " doesn ' t inadvertently introduce new risks or quality issues.
Analysis of other options:
B (Conduct a risk assessment): While assessing risk is a part of analyzing a change request, the question asks how the PM should proceed with the SME ' s claim. The formal procedure for handling modifications to the project plan is Integrated Change Control.
C (Update the schedule): This is " gold plating " or bypasses formal governance. A Project Manager should never update a baseline without an approved change request.
D (Manage Stakeholder Engagement): This is a continuous process of communicating and working with stakeholders. While the PM will engage the SME, the specific action required to handle a change to the project ' s execution logic is Change Control.
In summary, the Project Management Plan defines the " rules of the game. " When a technical expert suggests a shortcut or a pivot, the Project Manager acts as the guardian of the baselines, ensuring every move is vetted through the Perform Integrated Change Control process.

According to the PMBOKGuide, the formal gathering, ritualization, and archiving of lessons learned documentation is a primary activity of the Closing Process Group (specifically within the Close Project or Phase process).
While modern project management encourages the continuous recording of lessons learned throughout the project lifecycle (to the Lessons Learned Register), the formalization of these documents for the benefit of the organization occurs during Closing.
Final Archive: During the Closing phase, the project manager reviews all previous documentation to ensure that all " knowledge gained " is finalized.
* Organizational Process Assets (OPAs): The primary output of this activity is an update to the Corporate Knowledge Base. This ensures that future project managers can benefit from the successes and failures of the current project.
* Administrative Closure: This involves documenting the reasons for any deviations from the original plan and the effectiveness of the risk responses implemented.
A). Planning: This group focuses on defining the course of action. While you might review lessons learned from past projects here, you are not yet gathering them for the current project.
* B. Executing: During execution, the team is performing the work. While the Lessons Learned Register (a project document) is updated during execution, the " Lessons Learned Documentation " as a formal project closure deliverable is a function of the Closing group.
* D. Initiating: This group is for authorizing the project. At this stage, there is no project performance to reflect upon or document.
In the most recent editions of the PMBOKGuide, there is a distinction between:
Lessons Learned Register: An active document used throughout the project (Executing/Monitoring).
* Lessons Learned Repository: The final resting place for the documentation after the project is closed (Closing).
For the purpose of this examination, the act of " gathering " the final documentation for organizational use is strictly tied to the Closing of the project or phase.

According to the PMBOK Guide, this specific phrasing is the formal definition of Project Management.
* The Definition: Project management is the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements. It is accomplished through the appropriate application and integration of the project management processes identified for the project.
* Core Components:
* Knowledge: Understanding of the project management processes and the professional field.
* Skills: Leadership, communication, and technical capabilities.
* Tools and Techniques: Specific methodologies such as the Critical Path Method, Earned Value Management, or Brainstorming.
* The Goal: The ultimate purpose of this application is to satisfy the needs of stakeholders and ensure that the project delivers its intended value or result within the defined constraints of scope, time, cost, and quality.
Analysis of Other Options:
* B. Scope: Scope management is a subset of project management. It focuses specifically on ensuring that the project includes all the work required, and only the work required, to complete the project successfully.
* C. Contract: Contract management (or Procurement Management) is a specific knowledge area focused on the relationship between buyers and sellers. It is not the overarching discipline described by the definition.
* D. Program: A program is defined as a group of related projects, subprograms, and program activities managed in a coordinated way to obtain benefits not available from managing them individually. While it uses similar principles, the specific definition in the question refers to " project activities " and " project requirements. "