Comptia Project + Project Management MCQs

Comptia Project + Project Management MCQs

Our team has conducted extensive research to compile a set of Comptia Project + Project Management MCQs. We encourage you to test your Comptia Project + Project Management knowledge by answering these 30 multiple-choice questions provided below.
Simply scroll down to begin!

1: Processes required to manage the timely completion of a project

A.   Summary activity

B.   Project life cycle

C.   Project time management (Knowledge Area)

D.   Project management information system (PMIS) (Tool)

2: Identifying - documenting - approving or rejecting and controlling changes to the project baselines

A.   Change control

B.   Perform qualitative analysis (Process)

C.   Influence diagram (Tool)

D.   Root cause analysis (Technique)

3: Analytical technique that uses mathematical models to forecast future outcomes based on historical results. it is a method of determining the variance from a baseline parameter by using prior progress reporting periods data and projecting how much th

A.   Trend analysis (Technique)

B.   Work package

C.   Log

D.   Code of accounts (Tool)

4: Identifying and documenting relationships among project activities

A.   Sequence activities (Process)

B.   Executing processes (Process Group)

C.   Project charter (Output/Input)

D.   Result

5: Deliverable or project work component at the lowest level of each branch of the work breakdown structure

A.   Project team directory

B.   Work package

C.   Delphi technique (Technique)

D.   Practice

6: An estimating technique that uses the values of parameters - such as scope - cost - budget - and duration or measures of scale such as size - weight - and complexity from a previous similar activity as the basis of estimating the same parameter or me

A.   Change control board (CCB)

B.   Analogous estimating (Technique)

C.   Output (Process)

D.   Assumptions

7: Document that describes how procurement processes from developing procurement documentation through contract closure will be managed

A.   Procurement management plan (Output/Input)


C.   Master schedule (Tool)

D.   Verification

8: Identifying early and late start dates as well as early and late finish dates for the uncompleted portions of project schedule activities

A.   Schedule network analysis (Technique)

B.   Quality

C.   Perform quantitative analysis (Process)

D.   Product

9: Condition or capability that must be met or possessed by a system - product - service result or component to satisfy a contract - standard - specification or other formally imposed document.

A.   Monte Carlo analysis

B.   Acquire project team (Process)

C.   Requirement

D.   Milestone schedule (Tool)

10: Determining which risks may affect the project and documenting their characteristics

A.   Identify risks (Process)

B.   Work breakdown structure component

C.   To complete performance index (TCPI)

D.   Requirement

11: The acquirer of products - services or results for an organization

A.   Buyer

B.   Work breakdown structure (WBS) (Output/Input)

C.   Deliverable (Output/Input)

D.   Responsibility assignment matrix (RAM) (Tool)

12: Form of progressive elaboration planning where the work to be accomplished in the near term is planned in detail at a low level of the work breakdown structure - while the work far in the future is planned at a relatively high level of the work break

A.   Functional organization

B.   Rolling wave planning (Technique)

C.   Schedule network analysis (Technique)

D.   Schedule performance index (SPI)

13: Modification of a logical relationship that directs a delay in the successor activity. activity with a 10 day lag - cannot start until 10 days after an activity is finished

A.   Slack

B.   Contingency reserve(Output/Input)

C.   Lag (Technique)

D.   Acceptance criteria

14: Summary level project schedule that identifies the major deliverables and work breakdown structure components and key schedule milestones

A.   Specification limits

B.   Planning package

C.   Time and material contract (T&M)

D.   Master schedule (Tool)

15: The process of defining and documenting stakeholder needs to meet project objectives

A.   Scheduled start date (SS)

B.   Data date

C.   Predecessor activity

D.   Collect requirements (Process)

16: Performed to defined a new project or a new phase of an existing project by obtaining authorization to start the project or phase

A.   Defect repair

B.   Opportunity

C.   Project cost management (Knowledge Area)

D.   Initiating processes (Process Group)

17: Documenting project purchasing decisions - specifying the approach and identifying potential sellers

A.   Plan procurements (Process)

B.   Estimate activity resources (Process)

C.   Develop human resource plan (Process)

D.   Standard

18: Compares technical accomplishments during project execution to the project management plan's schedule of planned technical achievements.

A.   Actual duration

B.   Threshold

C.   Technical performance measurement (Technique)

D.   S-curve

19: A source of variation that is inherent in the system and predictable. on a control chart - it appears as part of the random process variation and is indicated by random pattern of points within the control limits. also referred to as random cause

A.   Common cause

B.   Sequence activities (Process)

C.   Buffer

D.   Contingency reserve(Output/Input)

20: Structure in which the project manager has full authority to assign priorities - apply resources and direct the work of persons assigned to the project

A.   Projectized organization

B.   Fixed price incentive fee contract (FPIF)

C.   Decision tree analysis (Technique)

D.   Pareto chart (Tool)

21: Adding features and functionality (project scope) without addressing the effects on time - costs - and resources or without customer approval

A.   Expert judgment (Technique)

B.   Project scope statement (Output/Input)

C.   Sub network

D.   Scope creep

22: Collection of generally sequential - non overlapping product phases whose name and number are determined by the manufacturing and control needs of the organization.

A.   Risk breakdown structure (RBS)

B.   Product life cycle

C.   Project initiation management (Knowledge Area)

D.   Project

23: An estimating technique that uses a statistical relationship between historical data and other variables (sq. foot in construction - lines of code in software development) to calculate an estimate for activity parameters such as scope - cost - budget

A.   Inspection (Technique)

B.   Administer procurements (Process)

C.   Parametric estimating (Technique)

D.   Project initiation management (Knowledge Area)

24: Process which generates hundreds or thousands of probable performance outcomes based on probability distributions for cost and schedule on individual tasks. the outcomes are used to generate a probability distribution for a project as a whole.

A.   Scheduled finish date (SF)

B.   Closing processes (Process Group)

C.   Delphi technique (Technique)

D.   Monte Carlo simulation

25: Project schedule network diagram drawn in such a way that the position and length of the schedule activity represents its duration. bar chart that includes schedule network logic

A.   Time scaled schedule network diagram (Tool)

B.   Common cause

C.   Float

D.   Project management plan (Output/Input)

26: Those processes performed to finalize all activities across all project management process groups to formally close the project or phase

A.   Path divergence

B.   Closing processes (Process Group)

C.   Portfolio

D.   Risk

27: Logical relationship where initiation of the work of the successor schedule activity depends upon the initiation of the work of the predecessor schedule activity

A.   Identify risks (Process)

B.   Project team directory

C.   Start to start (SS)

D.   Data date

28: Request for proposal - but may have a narrower or more specific meaning

A.   Project schedule (Output/Input)

B.   Network logic

C.   Expert judgment (Technique)

D.   Invitation for bid (IFB)

29: One of the defining points of a schedule network; a junction point joined to some or all of the other dependency lines

A.   Communications management plan (Output/Input)

B.   Node

C.   Network logic

D.   Approved change request (Output/Input)

30: Point in time that work was scheduled to start on a schedule activity. called planned start date.

A.   Scheduled start date (SS)

B.   Planned value (PV)

C.   Plan quality (Process)

D.   Perform qualitative analysis (Process)