PMI Updated CAPM Exam Questions and Answers by leia

According to the PMBOK® Guide, the Estimate Costs process is the process of developing an approximation of the monetary resources needed to complete project work. This process uses a specific set of tools to ensure accuracy and consensus.

Expert Judgment and Decision Making (Choice D): These are both core Tools and Techniques for the Estimate Costs process.

Expert Judgment: Involves consulting individuals or groups with specialized knowledge in similar projects, accounting, or specific technical domains to provide insight into cost variables.

Decision Making: Specifically Voting, is used to reach a consensus among team members or stakeholders regarding the cost estimates, especially in environments where multiple perspectives are needed to finalize an approximation.

Lessons Learned Register and Cost Aggregation (Choice A): The Lessons Learned Register is an Input (specifically a Project Document), not a technique. Cost Aggregation is a tool and technique, but it belongs to the Determine Budget process, where activity cost estimates are summed up to establish a cost baseline.

Project Schedule and Resource Requirements (Choice B): Both of these are Inputs to the Estimate Costs process. The project manager looks at the schedule and resource requirements to understand what needs to be estimated, but they are not the tools used to calculate the costs.

Three-point Estimating and Risk Register (Choice C): While Three-point Estimating is a valid tool for this process, the Risk Register is an Input. The information in the risk register (such as potential threats or opportunities) informs the estimate, but it is not a technique for calculating the cost itself.

By utilizing Expert Judgment and Decision Making, the project manager ensures that the estimates are not just mathematical calculations but are tempered by professional experience and team agreement, leading to a more realistic and defensible project budget.

According to the PMBOK® Guide, the Project Integration Management Knowledge Area includes the processes and activities to identify, define, combine, unify, and coordinate the various processes and project management activities within the Project Management Process Groups.

Direct and Manage Project Work: This is a key process within the Executing Process Group and belongs to the Project Integration Management Knowledge Area. It involves leading and performing the work defined in the project management plan and implementing approved changes to achieve the project ' s objectives.

Role of Integration: Integration management is unique to the project manager. While other knowledge areas (like Scope or Cost) can be managed by specialists, the project manager is solely responsible for integrating all pieces of the project into a cohesive whole.

Other Integration Processes:

Develop Project Charter

Develop Project Management Plan

Manage Project Knowledge

Monitor and Control Project Work

Perform Integrated Change Control

Close Project or Phase

Comparison with other options:

A. Manage Project Team: This process (now often referred to as Manage Team) belongs to the Project Resource Management Knowledge Area. It focuses on tracking team member performance and providing feedback.

B. Collect Requirements: This process belongs to the Project Scope Management Knowledge Area. It is the process of determining, documenting, and managing stakeholder needs and requirements.

C. Sequence Activities: This process belongs to the Project Schedule Management Knowledge Area. It involves identifying and documenting relationships among the project activities.

According to the PMBOK® Guide, specifically within the Perform Qualitative Risk Analysis process, the Risk Probability and Impact Assessment is the primary tool used to evaluate the characteristics of individual project risks.

Risk Probability Assessment: This specific component investigates the likelihood (probability) that each specific risk will occur. It typically uses a scale (e.g., 0.1 to 0.9 or Low to High) to rank the chances of the risk event happening.

Risk Impact Assessment: This investigates the potential effect on a project objective (such as schedule, cost, quality, or performance) if the risk event occurs.

The Probability and Impact Matrix: After assessing both the probability and the impact, the results are often plotted on a matrix to determine the overall risk score (Priority). This allows the project manager to focus on the " High " priority risks that require the most immediate attention and robust response planning.

Data Quality: For this assessment to be effective, the project manager must also perform a Risk Data Quality Assessment to ensure the information being used to judge probability and impact is accurate and reliable.

Comparison with other options:

A. Risk register: This is a document (an output) that contains the results of the risk management processes. While it records the probability and impact, it is the container for the data, not the analytical tool that investigates the likelihood.

B. Risk audits: These are a tool used in the Monitor Risks process. A risk audit is used to consider the effectiveness of the risk management process itself and the effectiveness of the implemented risk responses. It does not primarily investigate the initial likelihood of a risk occurring.

C. Risk urgency assessment: This is a data analysis technique used to identify the timing of a risk. It looks at how soon a risk might happen or how much time is available to implement a response. It does not measure the likelihood of occurrence, but rather the priority based on time.

According to the PMBOK® Guide, specifically within the Sequence Activities process, the Precedence Diagramming Method (PDM) defines four types of logical relationships (dependencies) between activities.

Finish-to-start (FS): This is the most commonly used logical relationship. In this setup, a successor activity cannot start until a predecessor activity has finished.

Application to the Scenario: In construction, you logically cannot begin the " pouring of concrete " (Successor) until the " delivery of concrete materials " (Predecessor) has been completed. The first activity must Finish before the second can Start.

Analysis of Other Options:

A. Start-to-start (SS): A relationship where a successor activity cannot start until a predecessor activity has started. (e.g., leveling concrete can start as soon as pouring starts).

B. Start-to-finish (SF): A rare relationship where a successor activity cannot finish until a predecessor activity has started.

C. Finish-to-finish (FF): A relationship where a successor activity cannot finish until a predecessor activity has finished.