Amazon
Avaya
Checkpoint
Cisco®
CompTIA
CrowdStrike
EC-Council
EXIN
Fortinet
Google
ISC
ISC2
ITIL®
Juniper
Microsoft
Okta
Palo Alto Networks
Salesforce
All Vendors
  1. Home
  2. PMI
  3. CAPM

PMI CAPM Exam (page: 22)
PMI Certified Associate in Project Management (-100)
Updated on: 02-Jan-2026

Viewing Page 22 of 222
CAPM PDF 1305 Questions

The basis of identification for current or potential problems to support later claims or new procurements is provided by:

  1. A risk urgency assessment.
  2. The scope baseline.
  3. Work performance information.
  4. Procurement audits.

Answer(s): C

Explanation:

4.4.1.5 Work Performance Information
Work performance information is the performance data collected from various controlling processes, analyzed in context, and integrated based on relationships across areas. Thus work performance data has been transformed into work performance information. Data in itself cannot be used in the decision-making process as it has only out-of-context meaning. Work performance information, however, is correlated and contextualized, and provides a sound foundation for project decisions.
Work performance information is circulated through communication processes. Examples of performance information are status of deliverables, implementation status for change requests, and forecasted estimates to complete.



Which Collect Requirements output links the product requirements to the deliverables that satisfy them?

  1. Requirements documentation
  2. Requirements traceability matrix
  3. Project management plan updates
  4. Project documents updates

Answer(s): B

Explanation:

5.2.3.2 Requirements Traceability Matrix
The requirements traceability matrix is a grid that links product requirements from their origin to the deliverables that satisfy them. The implementation of a requirements traceability matrix helps ensure that each requirement adds business value by linking it to the business and project objectives. It provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project. Finally, it provides a structure for managing changes to the product scope.
Tracing includes, but is not limited to, tracing requirements for the following:

Business needs, opportunities, goals, and objectives; Project objectives;
Project scope/WBS deliverables; Product design;
Product development;
Test strategy and test scenarios; and
High-level requirements to more detailed requirements.
Attributes associated with each requirement can be recorded in the requirements traceability matrix. These attributes help to define key information about the requirement. Typical attributes used in the requirements traceability matrix may include: a unique identifier, a textual description of the requirement, the rationale for inclusion, owner, source, priority, version, current status (such as active, cancelled, deferred, added, approved, assigned, completed), and status date. Additional attributes to ensure that the requirement has met stakeholders’ satisfaction may include stability, complexity, and acceptance criteria.

Process: 5.2 Collect Requirements
Definition: The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Key Benefit: The key benefit of this process is that it provides the basis for defining and managing the project scope including product scope.
Inputs
1. Scope management plan

2. Requirements management plan
3. Stakeholder management plan
4. Project charter
5. Stakeholder register

Tools & Techniques
1. Interviews
2. Focus groups
3. Facilitated workshops
4. Group creativity techniques
5. Group decision-making techniques
6. Questionnaires and surveys
7. Observations
8. Prototypes
9. Benchmarking
10. Context diagrams
11. Document analysis

Outputs
1. Requirements documentation
2. Requirements traceability matrix



Units of measure, level of precision, level of accuracy, control thresholds, and rules of performance measurement are examples of items that are established in the:

  1. Cost management plan.
  2. Work performance information.
  3. Quality management plan.
  4. Work breakdown structure.

Answer(s): A



Which type of dependency is established based on knowledge of best practices within a particular application area or some unusual aspect of the project in which a specific sequence is desired, even though there may be other acceptable sequences?

  1. External
  2. Internal
  3. Mandatory
  4. Discretionary

Answer(s): D

Explanation:

6.3.2.2 Dependency Determination
Dependencies may be characterized by the following attributes: mandatory or discretionary, internal or external, as described below. Dependency has four attributes, but two can be applicable at the same time in following ways: mandatory external dependencies, mandatory internal dependencies, discretionary external dependencies, or discretionary internal dependencies.

Mandatory dependencies. Mandatory dependencies are those that are legally or contractually required or inherent in the nature of the work. Mandatory dependencies often involve physical limitations, such as on a construction project, where it is impossible to erect the superstructure until after the foundation has been built, or on an electronics project, where a prototype has to be built before it can be tested.

Mandatory dependencies are also sometimes referred to as hard logic or hard dependencies. Technical dependencies may not be mandatory. The project team determines which dependencies are mandatory during the process of sequencing the activities. Mandatory dependencies should not be confused with assigning schedule constraints in the scheduling tool.

Discretionary dependencies. Discretionary dependencies are sometimes referred to as preferred logic, preferential logic, or soft logic. Discretionary dependencies are established based on knowledge of best practices within a particular application area or some unusual aspect of the project where a specific sequence is desired, even though there may be other acceptable sequences. Discretionary dependencies should be fully documented since they can create arbitrary total float values and can limit later scheduling options. When fast tracking techniques are employed, these discretionary dependencies should be reviewed and considered for modification or removal. The project team determines which dependencies are discretionary during the process of sequencing the activities.
External dependencies. External dependencies involve a relationship between project activities and non- project activities. These dependencies are usually outside the project team’s control. For example, the testing activity in a software project may be dependent on the delivery of hardware from an external source, or governmental environmental hearings may need to be held before site preparation can begin on a construction project. The project management team determines which dependencies are external during the process of sequencing the activities.
Internal dependencies. Internal dependencies involve a precedence relationship between project activities and are generally inside the project team’s control. For example, if the team cannot test a machine until they assemble it, this is an internal mandatory dependency. The project management team determines which dependencies are internal during the process of sequencing the activities.



Sensitivity analysis is typically displayed as a/an:

  1. Decision tree diagram.
  2. Tornado diagram.
  3. Pareto diagram.
  4. Ishikawa diagram.

Answer(s): B

Explanation:

11.4.2.2 Quantitative Risk Analysis and Modeling Techniques
• Sensitivity analysis. Sensitivity analysis helps to determine which risks have the most potential impact on the project. It helps to understand how the variations in project’s objectives correlate with variations in different uncertainties. Conversely, it examines the extent to which the uncertainty of each project element affects the objective being studied when all other uncertain elements are held at their baseline values. One typical display of sensitivity analysis is the tornado diagram (Figure 11-15), which is useful for comparing relative importance and impact of variables that have a high degree of uncertainty to those that are more stable. The Tornado diagram is also helpful in analyzing risk-taking scenarios enabled on specific risks whose quantitative analysis highlights possible benefits greater than corresponding identified negative impacts. A tornado diagram is a special type of bar chart used in sensitivity analysis for comparing the relative importance of the variables. In a tornado diagram, the Y-axis contains each type of uncertainty at base values, and the X-axis contains the spread or correlation of the uncertainty to the studied output. In this fgure, each uncertainty contains a horizontal bar and is ordered vertically to show uncertainties with a decreasing spread from the base values.



Viewing Page 22 of 222



Share your comments for PMI CAPM exam with other users:

Priyo 11/14/2023 2:23:00 AM

i used this site since 2000, still great to support my career
INDONESIA