In the PMBOK Guide, particularly within the Manage Project Knowledge process, a clear distinction is made between two types of knowledge: Explicit and Tacit.
* Tacit Knowledge (Choice C): This is personal knowledge that is difficult to express or formalize. It includes Expert Judgment, insights, experience, " know-how, " and beliefs. It is often shared through interpersonal interaction, mentoring, and social connection. Because it is embedded in the individual ' s mind and influenced by their unique context, it cannot be easily written down or stored in a database.
* Explicit Knowledge (Choice A, B, and D): This is knowledge that can be codified using symbols such as words, numbers, and pictures. It can be easily documented and shared.
* Risk Register (Choice A): A formal document containing identified risks and their characteristics.
* Project Requirements (Choice B): Documented needs or conditions that must be met.
* Make-or-buy Analysis (Choice D): A documented technique and result used to determine whether work should be performed internally or purchased from outside sources.
The goal of the Manage Project Knowledge process is to use existing organizational knowledge and create new knowledge to achieve the project ' s objectives. While explicit knowledge is managed via Information Management, tacit knowledge is managed through Knowledge Management (e.g., networking and communities of practice) because it resides within the experts themselves.

According to the PMBOKGuide, the Collect Requirements process is the stage where the project team determines, documents, and manages stakeholder needs and requirements. Because requirements can often be difficult for stakeholders to articulate, specific tools are used to extract this information.
* Prototypes: This is a key Tool and Technique of the Collect Requirements process. A prototype is a working model of the expected product before actually building it. It allows stakeholders to interact with a " mock-up " of the final product, which helps them identify missing requirements, clarify expectations, and uncover potential risks early in the project life cycle.
* Progressive Elaboration: Prototyping supports the concept of progressive elaboration because it follows an iterative cycle of mock-up creation, user review, feedback generation, and prototype revision.
* Visual Confirmation: For many stakeholders, seeing a visual representation (like a wireframe for software or a small-scale model for a building) is much more effective than reading a technical document. This ensures that the final " Requirement Documentation " is accurate and agreed upon.
Why other options are incorrect:
* Option A: Inspection: This is a tool and technique used in Validate Scope and Control Quality. It involves examining a work product to determine if it conforms to standards. It happens after the work is done, not during the collection of requirements.
* Option B: Decomposition: This is a tool and technique used in the Create WBS process. It involves breaking down the project scope and project deliverables into smaller, more manageable components.
* Option C: Product analysis: This is a tool and technique used in Define Scope. It is used to translate high-level product descriptions into meaningful deliverables by asking questions about the product ' s function and purpose.

According to the PMBOKGuide, specifically the Earned Value Management (EVM) section in the Control Costs process, we analyze project performance by comparing Earned Value (EV), Actual Cost (AC), and Planned Value (PV).
1. Cost Analysis (Efficiency and Variance):
* Cost Variance (CV) formula: $CV = EV - AC$
* Calculation: $100 - 120 = -20$
* Interpretation: A negative CV ($-20$) indicates that the project is over budget or experiencing a cost overrun. The project has spent 120 workdays of effort to achieve only 100 workdays ' worth of work.
2. Schedule Analysis (Efficiency and Variance):
* Schedule Variance (SV) formula: $SV = EV - PV$
* Calculation: $100 - 80 = +20$
* Interpretation: A positive SV ($+20$) indicates that the project is ahead of schedule.
Analysis of Options:
* A. There is a cost underrun: Incorrect. A cost underrun occurs when CV is positive (EV > AC).
* B. There is a cost overrun: Correct. As calculated, the project has spent more than the value of the work performed ($AC > EV$).
* C. The project may not meet the deadline: Incorrect. Based on the data, the project is ahead of schedule ($EV > PV$), meaning it is currently likely to meet or beat the deadline.
* D. The project is 20 days behind schedule: Incorrect. The project is actually 20 days ahead of schedule ($SV = +20$).

According to the PMBOKGuide, specifically the Develop Schedule process within the Project Schedule Management knowledge area, the project duration is determined by the total length of the Critical Path.
* Understanding Parallel Activities: When two activities (B and C) are performed in " parallel, " they occur simultaneously. The total time required for this parallel segment is determined by the activity with the longest duration.
* Duration of B = 3 days.
* Duration of C = 2 days.
* Time for parallel block = $\max(3, 2) = 3$ days.
* Calculating Activity A: The project is stated to have a total duration of 10 days. Assuming A is the sequential component of the project (either preceding or following the parallel block), we use the following formula:
* $\text{Total Project Duration} = \text{Duration of A} + \text{Duration of Parallel Block (B and C)}$
* $10 \text{ days} = \text{Duration of A} + 3 \text{ days}$
* $\text{Duration of A} = 10 - 3 = 7$ days.
Why other options are incorrect:
* Option A: 3 days: This is the duration of the parallel segment. If A were 3 days, the total project duration would only be 6 days (3 for A + 3 for the block).
* Option B: 5 days: This would be the result if you added the durations of B and C together ($3 + 2$).
However, the question specifies they are in parallel, not in sequence (series).
* Option D: 10 days: If A were 10 days, the total project duration would be at least 13 days (10 for A + 3 for the block), which contradicts the " 10-day project " constraint given in the prompt.

According to the PMBOKGuide, the Project Charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
* Key Elements of a Project Charter: The charter contains high-level information including the project purpose, measurable objectives, high-level requirements, high-level project description, overall project risk, summary milestone schedule, and preapproved financial resources. Crucially, it includes a Key Stakeholder List.
* Stakeholder List vs. Register: At the time the charter is being developed (during the Develop Project Charter process), the project manager identifies the main stakeholders involved in or influenced by the project. This initial list is a high-level component of the charter. The formal, detailed Stakeholder Register is actually an output of the Identify Stakeholders process, which typically occurs immediately after the charter is signed.
Comparison with other options:
* A. Management reserves: These are part of the project ' s total budget but are determined during the Determine Budget process (Planning Phase), not during the initiation phase when the charter is created.
* B. Work breakdown structure (WBS): The WBS is a detailed decomposition of the project scope created during the Create WBS process in the Planning Phase. It is far too granular for the high-level Project Charter.
* D. Stakeholder register: While similar to a stakeholder list, the Stakeholder Register is a specific, detailed project document that is an output of the Identify Stakeholders process. The Charter contains the initial list used to kickstart the identification process.