PMI Updated CAPM Exam Questions and Answers by elyza

According to the PMBOK® Guide, a Verified Deliverable is a specific output of the Control Quality process. The term " verified " refers to the internal technical assessment of the work performed by the project team.

Internal Validation: Verification is the process of evaluating a product, service, or result to determine whether it complies with the quality requirements and specifications. It is essentially an internal check to ensure the correctness of the work.

Prevention of Errors: The goal of creating verified deliverables is to ensure that any defects or nonconformities are identified and corrected internally before the deliverable is presented to the customer or sponsor.

The Path to Acceptance: A verified deliverable is a mandatory input for the Validate Scope process. Only after a deliverable is verified (internally checked for correctness) can it be submitted for formal customer acceptance.

Why other options are incorrect:

Option B: The completeness of a deliverable: While a deliverable must be complete to be verified, " completeness " is only one aspect of quality. Verification focuses specifically on whether the item was built correctly according to the standards.

Option C: The deliverable requirements: Requirements are the criteria used to perform the verification, but they do not define what the " verified " status itself represents.

Option D: The customer acceptance of a deliverable: This is a common point of confusion. Customer acceptance results in an Accepted Deliverable, which occurs during the Validate Scope process. Verification happens before acceptance and is performed by the project team/Quality department, not the customer.

According to the PMBOK® Guide, specifically within the Develop Project Management Plan and Define Activities processes, requirements stipulated in a contract are considered Project Constraints.

Contractual Obligations: A contract is a legally binding document. If the contract specifies a final completion date (one year) and a specific interim deadline (foundation in 30 days), these are classified as Milestones.

Milestones vs. Activities: A milestone is a significant point or event in a project. Unlike activities, milestones have zero duration. Because these specific dates are " Hard " constraints dictated by the contract, they must be incorporated into the Milestone List and the Project Management Plan.

Mandatory Nature: The project manager does not have the discretion to ignore these dates. They form the basis of the Schedule Baseline. Once these milestones are added to the plan, the project manager will then sequence the necessary activities to ensure these deadlines are met.

Analysis of other options:

Option A: While the tight timeline represents a risk, milestones are primarily schedule components. You would record the risk of missing the deadline in the register, but you must first put the actual dates into the project plan to manage them.

Option C: This is a technical distractor. Milestones, by definition, have zero duration. They represent a point in time (the completion of the foundation), so there is no duration to calculate for the milestone itself—only for the activities leading up to it.

Option D: " Starting as soon as possible " is a proactive sentiment, but it is not a formal project management procedure. Proper planning (adding the constraints to the plan) must occur to ensure the " fast start " is actually directed toward the correct goals.

Per PMI standards, any date or requirement explicitly mentioned in a legal contract is a Constraint that must be documented in the Project Management Plan and tracked as a milestone to ensure compliance.

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, specifically the Develop Project Charter process, 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.

Content of the Project Charter: The charter contains high-level information because it is created during the Initiating phase when detailed data is not yet available. Key components include:

Project purpose or justification.

Measurable project objectives and related success criteria.

High-level requirements.

High-level risks.

Summary milestone schedule and summary budget.

Purpose of High-Level Risks: Identifying risks at this stage helps the sponsor and the project manager understand the major threats or opportunities that could affect the project ' s feasibility before a significant investment is made. These are later refined into detailed risks during the Identify Risks process in the Planning phase.

Comparison with other options:

A. Business case: While it provides the economic justification and may mention very high-level constraints, the formal project document that lists " high-level risks " as a required element is the project charter.

B. Risk breakdown structure (RBS): This is a tool/representation used to categorize risks by their sources (e.g., Technical, External, Organizational). it is a framework for identification, not a document that lists the risks themselves.

D. Risk register: This document is the primary output of the Identify Risks process. It contains detailed individual project risks, their root causes, and potential responses. It is much more granular than the high-level risks found in the charter.