PMI Certified Associate in Project Management CAPM Exam Questions

Answer : B

Based on the principles of Earned Value Management (EVM) found in the PMBOK Guide, the Cost Variance (CV) is a measure of cost performance on a project.

Formula: $CV = EV - AC$

Calculation: Given the metrics:

Earned Value ($EV$) = $\$20,000$

Actual Cost ($AC$) = $\$22,000$

$CV = 20,000 - 22,000 = -2,000$

Interpretation:

A negative CV ($-2,000$ in this case) indicates that the project is over budget. It means the actual cost spent to date is higher than the value of the work performed.

A positive CV would indicate that the project is under budget.

A CV of zero would indicate that the project is exactly on budget.

Note: The Planned Value ($PV$) of $\$28,000$ is used for calculating Schedule Variance ($SV = EV - PV$), but it is not used in the calculation for Cost Variance.

Answer : B

According to the PMBOK Guide, the Project Management Process Groups are not one-time, linear events that happen in isolation. Instead, they are highly interrelated and the links between them are iterative.

The Nature of Iteration: Project management is a 'progressive elaboration' of the project management plan. This means that as more information or better estimates become available, the project team must often return to previous process groups to refine the project's direction.

Process Links: The output of one process generally becomes an input to another process or is a deliverable of the project. For example:

The Planning group provides the Executing group with the project management plan.

As work is executed, Work Performance Data is generated and sent to the Monitoring and Controlling group.

If the controlling processes identify a significant variance, the team may need to trigger the Planning group again to update the schedule or budget.

Cyclical Interaction: This iterative nature ensures that the project remains aligned with business objectives. It allows for continuous improvement and adjustment throughout the project life cycle until the final objectives are met in the Closing process group.

Comparison with other options:

A . Intuitive: While experienced project managers develop intuition, the formal framework of the PMBOK Guide is based on structured, documented processes rather than 'gut feeling.'

C . Measured: While performance within the process groups is measured (specifically in Monitoring and Controlling), 'measured' does not describe the link or relationship between the groups themselves.

D . Monitored: Monitoring is a specific process group (Monitoring and Controlling), but it is not the term used to describe the fundamental, repetitive, and refining relationship that exists between all the groups.

Answer : C

According to the PMBOK Guide, projects are initiated in response to factors that influence an organization. These factors are generally categorized into four primary areas of project initiation context.

Meet Regulatory, Legal, or Social Requirements (Choice C): A change in a company's tax classification is a formal legal and financial status update mandated by government or tax authorities. To remain compliant with the law, the company may need to initiate a project to update its financial systems, reporting structures, and accounting processes. This is a classic example of a project triggered by the need to adhere to external regulations.

Change Business or Technological Strategies (Choice A): This usually refers to a project initiated because the company wants to move in a new direction---such as launching a new product line or moving to a cloud-based infrastructure---rather than reacting to a mandatory tax change.

Improve Processes and Services (Choice B): While the tax change might involve changing a process, the reason for the project is the legal requirement itself. 'Improvement' implies a choice to make something better or more efficient for the sake of performance, rather than a mandatory compliance task.

Satisfy Stakeholder Requests (Choice D): While an accountant is a stakeholder, their notification is regarding a structural/legal change. Stakeholder requests as a project trigger usually refer to specific desired features or changes requested by customers or internal executives that are not necessarily legally mandated.

By initiating a project to address Regulatory and Legal Requirements, the organization avoids penalties, fines, and legal complications, ensuring that its operations remain sustainable and legitimate under the new tax classification.

Answer : A

According to the PMBOK Guide, Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.

Change Requests: This is a primary output of the Control Scope process. When the actual scope performance deviates from the scope baseline (detected via variance analysis), change requests are generated. These may include preventive or corrective actions, defect repairs, or enhancement requests, and they are processed for review and disposition through the Perform Integrated Change Control process.

Other Key Outputs:

Work performance information.

Project management plan updates (specifically scope baseline and other baseline updates).

Project documents updates.

Analysis of Other Options:

B . Variance analysis: This is a tool and technique used within the Control Scope process to determine the cause and degree of difference between the baseline and actual performance; it is not an output.

C . Accepted deliverables: This is the primary output of the Validate Scope (formerly Verify Scope) process, where the customer formally signs off on completed deliverables.

D . Requirements documentation: This is a key input to the Control Scope process, used as a reference to ensure that all defined requirements are being met and no 'gold plating' is occurring.

Answer : C

According to the PMBOK Guide (Project Management Body of Knowledge), specifically within the Project Integration Management knowledge area, the Close Project or Phase process is the process of finalizing all activities for the project, phase, or contract. The standard tools and techniques for this process are:

Expert Judgment (Option C): This is required to ensure the closure meets organizational and legal standards. Experts provide insight on administrative closure, final lessons learned, and the transfer of the product to operations.

Analytical Techniques (Option C): In the context of closure, analytical techniques are used to perform regression analysis, trend analysis, and variance analysis to verify that the project met its objectives and to document the final project performance.

Meetings (Option B and D): While meetings are used in nearly every process (including closure for lessons learned or wrap-up sessions), they are often paired with other specific tools.

Reserve Analysis (Option A): This is a tool used in Cost Management and Risk Management to determine if the remaining contingency and management reserves are sufficient. It is not a primary tool for the formal administrative closure of a project.

Performance Reviews (Option D): These are typically part of Control Schedule, Control Costs, or Manage Team to compare actual performance against the baseline. While relevant to the final report, the PMBOK specifically highlights 'Analytical Techniques' as the broader category for closure.

In the PMI framework, the combination of Expert Judgment, Analytical Techniques, and Meetings represents the standard toolkit for ensuring a project is legally, financially, and administratively finalized.

Answer : C

According to the PMBOK Guide, specifically within the Perform Qualitative Risk Analysis process, the risk rating (also known as the Risk Score) is determined by the combination of a risk's probability of occurrence and its impact on the project objectives if it does occur.

The Risk Formula: The standard formula used to calculate the risk rating is:

$$\text{Risk Rating} = \text{Probability} \times \text{Impact}$$

The Calculation:

Given Risk Rating = $0.56$

Given Impact = $0.80$ (Very High)

To find the Probability ($P$):

$$0.56 = P \times 0.80$$

$$P = \frac{0.56}{0.80}$$

$$P = 0.70$$

Application: This mathematical approach allows project managers to prioritize risks on a numerical scale. In a Probability and Impact Matrix, a risk with a probability of $0.70$ and an impact of $0.80$ would typically fall into the 'High Risk' (red) zone, requiring aggressive response strategies and proactive monitoring.

Comparison with other options:

A . 0.45: This value is incorrect. Multiplying $0.45$ by $0.80$ would result in a risk rating of $0.36$.

B . 0.56: This is the risk rating itself, not the probability.

D . 1.36: This value is mathematically incorrect and impossible for a probability. In project management risk scales, probability is always expressed as a value between $0.0$ and $1.0$ (or $0\%$ to $100\%$). A value of $1.36$ would imply a likelihood greater than $100\%$.

Answer : D

According to the PMBOK Guide (Project Management Body of Knowledge), specifically within the sections on the Role of the Project Manager and Project Communications Management:

Communicating (Option D): It is a well-established principle in the PMI framework that project managers spend the vast majority of their time---frequently cited as 75% to 90%---communicating. This includes formal and informal communication with the team, stakeholders, sponsors, and customers. Because a Project Manager acts as the central link between the strategy and the execution, their primary 'tool' is the exchange of information to ensure alignment, resolve conflict, and manage expectations.

Estimating (Option A): This is a specific activity within the Project Cost and Project Schedule management areas. While critical during the planning phase and during change control, it is a task-oriented activity that does not consume the bulk of a Project Manager's daily schedule.

Scheduling (Option B): Developing and maintaining the project schedule is a core function, but in many modern project environments, much of the data entry and logic is handled by scheduling software or project coordinators. The Project Manager focuses more on the implications of the schedule, which requires communication.

Controlling (Option C): Controlling involves monitoring project performance and implementing changes. While it is a continuous process throughout the project life cycle, 'controlling' is often executed through communication (meetings, reports, and negotiations).

In the PMI framework, Project Communications Management is often considered the 'oil' that keeps the project engine running. A Project Manager who communicates effectively can often overcome technical or resource deficiencies, whereas a Project Manager with poor communication skills will likely struggle even with a perfect plan and unlimited resources. Success is heavily dependent on the ability to manage the Communications Management Plan effectively.