PMI CAPM PMI-100 Questions & Answers

• Question 341:

  Whose approval may be required for change requests after change control board (CCB) approval?

  A. Functional managers

  B. Business partners

  C. Customers or sponsors

  D. Subject matter experts

  Correct Answer: C

  Explanation:

  Change Control Board (CCB). A formally chartered group responsible for reviewing, evaluating,

  approving, delaying, or rejecting changes to the project, and for recording and communicating such

  decisions.

• Question 342:

  The most appropriate project life cycle model for an environment with a high level of change and extensive stakeholder involvement in projects is:

  A. adaptive

  B. reflexive

  C. predictive

  D. iterative

  Correct Answer: A

  Explanation:

  2.4.2.4 Adaptive Life Cycles Adaptive life cycles (also known as change-driven or agile methods) are intended to respond to high levels of change and ongoing stakeholder involvement. Adaptive methods are also iterative and incremental, but differ in that iterations are very rapid (usually with a duration of 2 to 4 weeks) and are fixed in time and cost. Adaptive projects generally perform several processes in each iteration, although early iterations may concentrate more on planning activities. The overall scope of the project will be decomposed into a set of requirements and work to be performed, sometimes referred to as a product backlog. At the beginning of an iteration, the team will work to determine how many of the highest priority items on the backlog list can be delivered within the next iteration. At the end of each iteration, the product should be ready for review by the customer. This does not mean that the customer is required to accept delivery, just that the product should not include unfinished, incomplete, or unusable features. The sponsor and customer representatives should be continuously engaged with the project to provide feedback on deliverables as they are created and to ensure that the product backlog reflects their current needs. Adaptive methods are generally preferred when dealing with a rapidly changing environment, when requirements and scope are difficult to define in advance, and when it is possible to define small incremental improvements that will deliver value to stakeholders.

• Question 343:

  Correlated and contextualized information on how closely the scope is being maintained relative to the scope baseline is contained within:

  A. project documents updates.

  B. project management plan updates.

  C. change requests.

  D. work performance information.

  Correct Answer: D

  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.

  5.4.3.1 Scope Baseline

  The scope baseline is the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison. It is a component of the project management plan. Components of the scope baseline include:

  Project scope statement. The project scope statement includes the description of the project scope, major deliverables, assumptions, and constraints.

  WBS. The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. Each descending level of the WBS represents an increasingly detailed definition of the project work. The WBS is finalized by assigning each work package to a control account and establishing a unique identifier for that work package from a code of accounts. These identifiers provide a structure for hierarchical summation of costs, schedule, and resource information. A control account is a management control point where scope, budget, actual cost, and schedule are integrated and compared to the earned value for performance measurement. Control accounts are placed at selected management points in the WBS. Each control account may include one or more work packages, but each of the work packages should be associated with only one control account. A control account may include one or more planning packages. A planning package is a work breakdown structure component below the control account with known work content but without detailed schedule activities.

  WBS dictionary. The WBS dictionary is a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS. The WBS dictionary is a document that supports the WBS. Information in the WBS dictionary may include, but is not limited to:

  ○

  Code of account identifier,

  ○

  Description of work,

  ○

  Assumptions and constraints,

  ○

  Responsible organization,

  ○

  Schedule milestones,

  ○

  Associated schedule activities,

  ○

  Resources required,

  ○

  Cost estimates,

  ○

  Quality requirements,

  ○

  Acceptance criteria,

  ○

  Technical references, and

  ○

  Agreement information

• Question 344:

  Every project creates a unique product, service, or result that may be:

  A. tangible

  B. targeted

  C. organized

  D. variable

  Correct Answer: A

• Question 345:

  The following is a network diagram for a project.

  

  The free float for Activity H is how many days?

  A. 4

  B. 5

  C. 10

  D. 11

  Correct Answer: A

• Question 346:

  The following is a network diagram for a project.

  

  How many possible paths are identified for this project?

  A. 3

  B. 4

  C. 6

  D. 7

  Correct Answer: B

• Question 347:

  Which element does a project charter contain?

  A. Management reserves

  B. Work breakdown structure

  C. Stakeholder list

  D. Stakeholder register

  Correct Answer: C

• Question 348:

  The following is a network diagram for a project.

  

  What is the critical path for the project?

  A. A-B-C-F-G-I

  B. A-B-C-F-H-I

  C. A-D-E-F-G-I

  D. A-D-E-F-H-I

  Correct Answer: A

• Question 349:

  Stakeholder communication requirements should be included as a component of:

  A. enterprise environmental factors

  B. organizational process assets

  C. the project management plan

  D. the stakeholder register

  Correct Answer: C

• Question 350:

  In the Plan Procurement Management process, which source selection criteria analyzes if the seller's proposed technical methodologies, techniques, solutions, and services meet the procurement documents requirements?

  A. Technical approach

  B. Technical capability

  C. Business size and type

  D. Production capacity and interest

  Correct Answer: A

  Explanation:

  12.1.3.3 Procurement Documents

  Procurement documents are used to solicit proposals from prospective sellers. Terms such as bid, tender, or quotation are generally used when the seller selection decision will be based on price (as when buying commercial or standard items), while a term such as proposal is generally used when other considerations, such as technical capability or technical approach are paramount. Common terms are in use for different types of procurement documents and may include request for information (RFI), invitation for bid (IFB), request for proposal (RFP), request for quotation (RFQ), tender notice, invitation for negotiation, and invitation for seller's initial response. Specific procurement terminology used may vary by industry and location of the procurement. The buyer structures procurement documents to facilitate an accurate and complete response from each prospective seller and to facilitate easy evaluation of the responses. These documents include a description of the desired form of the response, the relevant procurement statement of work (SOW) and any required contractual provisions. With government contracting, some or all of the content and structure of procurement documents may be defined by regulation. The complexity and level of detail of the procurement documents should be consistent with the value of, and risks associated with, the planned procurement. Procurement documents are required to be sufficient to ensure consistent, appropriate responses, but flexible enough to allow consideration of any seller suggestions for better ways to satisfy the same requirements. Issuing a procurement request to potential sellers to submit a proposal or bid is normally done in accordance with the policies of the buyer's organization, which can include publication of the request in public newspapers, in trade journals, in public registries, or on the internet.

  Process: 12.1 Plan Procurement ManagementDefinition: The process of documenting project procurement decisions, specifying the approach, and identifying potential sellers. Key Benefit: The key benefit of this process is that it determines whether to acquire outside support, and if so, what to acquire, how to acquire it, how much is needed, and when to acquire it.

  Inputs

  1.

  Project management plan

  2.

  Requirements documentation

  3.

  Risk register

  4.

  Activity resource requirements

  5.

  Project schedule

  6.

  Activity cost estimates

  7.

  Stakeholder register

  8.

  Enterprise environmental factors

  9.

  Organizational process assets

  Tools and Techniques

  1.

  Make-or-buy analysis

  2.

  Expert judgment

  3.

  Market research

  4.

  Meetings

  Outputs

  1.

  Procurement management plan

  2.

  Procurement statement of work

  3.

  Procurement documents

  4.

  Source selection criteria

  5.

  Make-or-buy decisions

  6.

  Change requests

  7.

  Project documents updates