Test your basic knowledge |

Comptia Project + Project Management

Subjects : certifications, comptia-project-+, it-skills

Instructions:

Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can study here.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. Buyer pays the seller a set amount (as defined by the contract) and the seller can earn an additional amount if the seller meets defined performance criteria
three point estimate (Technique)
risk category
fixed price incentive fee contract (FPIF)
approved change request (Output/Input)

2. Summary level project schedule that identifies the major deliverables and work breakdown structure components and key schedule milestones
master schedule (Tool)
scheduled finish date (SF)
plan risk management (Process)
enterprise environmental factors (Input/Output)

3. Source of variation that is not inherent in the system - is not predictable - and it intermittent. also referred to as assignable cause.
monitor and control project work (Process)
resource calendar
special cause
template

4. Depiction in a diagram format of the inputs - process actions - and outputs of one or more processes within a system
authority
network path
flowcharting (Technique)
analogous estimating (Technique)

5. Auditing the quality requirements and the results from quality control measurements to ensure appropriate quality standards and operational definitions are used
parametric estimating (Technique)
methodology
perform quality assurance (Process)
external deliverable

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
perform quality assurance (Process)
risk tolerance
analogous estimating (Technique)
template

7. Members of the project team who are directly involved in project management activities
project initiation
plan risk management (Process)
project management team
plan quality (Process)

8. Graphical representation of situations showing causal influences - time ordering of events and other relationships among variables and outcomes
project human resource management (Knowledge Area)
plan procurements (Process)
influence diagram (Tool)
baseline

9. Significant point or event in the project
closing processes (Process Group)
develop project management plan (Process)
milestone
actual cost (AC)

10. A request - demand or assertion of rights by a seller against a buyer or vice versa for consideration - compensation - or payment under the terms of a legally binding contract (such as for a disputed change)
path divergence
claim
free float
scope

11. List of project team members - their project roles and communication information
inspection (Technique)
procurement documents (Output/Input)
project team directory
opportunity

12. Work that must be performed to deliver a product - service or result with the specified features and functions
project scope
identify risks (Process)
influence diagram (Tool)
distribute information (Process)

13. Evaluation of whether or not a product - service - or system complies with a regulation - requirement - specification or imposed condition.
backward pass
verification
risk
estimate to complete (ETC)(Output/Input)

14. The approved estimate for the project or any work breakdown structure component or any schedule activity
budget
scheduled start date (SS)
threat
work breakdown structure component

15. Response to a negative risk that has occurred - workaround is not planned in advance of the occurrence of the risk event
preventative action
workaround
deliverable (Output/Input)
enterprise environmental factors (Input/Output)

16. Common way to determine whether a risk is considered low - moderate - or high by combining the two dimensions of a risk: its probability of occurrence and its impact on objectives if it occurs
standard
performing organization
project communications management (Knowledge Area)
probability and impact matrix (Tool)

17. Technique that computes or iterates the project cost or project schedule many times using input values selected at random from probability distributions of possible costs or durations - to calculate a distribution of total project costs or completion
defect
procurement management plan (Output/Input)
identify risks (Process)
Monte Carlo analysis

18. Subdivision (fragment) of a project schedule network diagram - usually representing a subproject or work package.
preventative action
tool
activity list (Output/Input)
sub network

19. Graphic display of cumulative costs - labor - hours - percentage of work or other quantities - plotted against time. used to depict planned value - earned value and active costs.
product
scope management plan(Output/Input)
configuration management system (Tool)
s-curve

20. Schedule network diagramming technique in which schedule activities are represented by boxes or nodes. schedule activities are graphically linked by one or more logical relationships to show the sequence in which the activities are performed
project management plan (Output/Input)
assumptions
estimate activity resources (Process)
precedence diagramming method (PDM) (Technique)

21. A quantitative assessment of the likely amount or outcome. usually applied to project costs - resources - effort and durations.
virtual team
baseline
product
estimate (Output/Input)

22. Document containing the results of the qualitative risk analysis - quantitative risk analysis and risk response planning. details all identified risks including description - category - cause - probability of occurring - impact on objectives - propos
probability and impact matrix (Tool)
project risk management (Knowledge Area)
risk register (Output/Input)
residual risk

23. Processes and activities needed to identify - define - combine - unify and coordinate the various processes and project management activities within the project management process groups
acquire project team (Process)
performance measurement baseline
project initiation management (Knowledge Area)
backward pass

24. The formally documented identification of a defect in a project component with a recommendation to either repair the defect or completely replace the component
log
variance
defect repair
report performance (Process)

25. Reserve
to complete performance index (TCPI)
portfolio management (Technique)
buffer
assumptions

26. A general data gathering and creativity technique that can be used to identify risks - ideas or solutions to issues by using a group of team members or subject matter experts
defect repair
planned value (PV)
brainstorming (Technique)
late finish date (LF)

27. Estimate of the amount of work that has been completed on an activity or a work breakdown structure component
close procurements (Process)
percent complete
project management team
project management system (Tool)

28. A subsystem of the overall project management system. it is a collection of formal documented procedures used to apply technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a p
specification limits
configuration management system (Tool)
procurement management plan (Output/Input)
residual risk

29. Calculation of the early start and early finish dates for the uncompleted portions of all network activities
responsibility assignment matrix (RAM) (Tool)
perform qualitative analysis (Process)
objective
forward pass

30. Describes how the project management team will implement the performing organizations quality plan.
quality management plan (Output/Input)
total float
external deliverable
risk acceptance (Technique)

31. Hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units
budget
organizational breakdown structure (OBS) (Tool)
produce scope
change requests

32. Documents utilized in bid and proposal activities - which include the buyer's invitation for bid - invitation for negotiations - request for information - request for quotation - request for proposal and sellers responses
risk category
scope creep
procurement documents (Output/Input)
practice

33. Performing the work defined in the project management plan to achieve the project's objectives
activity attributes (Output/Input)
plan communications (Process)
direct and manage project execution (Process)
residual risk

34. A diagram that describes a decision under consideration and the implications of choosing one or another of the available alternatives. it is used when some future scenarios or outcomes of actions are uncertain. it incorporates probabilities and costs
deliverable (Output/Input)
decision tree analysis (Technique)
forward pass
define activities (Process)

35. Requests to expand or reduce the project scope - modify policies - processes - plans or procedures - modify costs or budgets - or revise schedules
probability and impact matrix (Tool)
estimate to complete (ETC)(Output/Input)
project schedule (Output/Input)
change requests

36. A product - result or service generated by a process
output (Process)
estimate activity resources (Process)
planned value (PV)
lead (Technique)

37. Processes required to track - review and regulate the progress and performance of the project - identify any areas in which changes to the plan are required and initiate the corresponding changes.
monitor and controlling processes (Process Group)
Delphi technique (Technique)
functional manager
enterprise environmental factors (Input/Output)

38. Formally documented change request that is submitted for approval to the integrated change control process
requested change(Output/Input)
lessons learned(Output/Input)
finish date
residual risk

39. Term used in precedence diagramming method for a logical relationship in current usage. precedence relationship - logical relationship and dependency are interchangeably used
precedence relationship
triggers
perform integrated change control (Process)
parametric estimating (Technique)

40. Number of labor units required to complete a schedule activity or work breakdown structure component
effort
monitor and controlling processes (Process Group)
schedule performance index (SPI)
schedule model (Tool)

41. A category of projects that have common components significant in such projects - but are not needed or present in all projects. application areas are usually defined in terms of either the product or the type of customer or industry sector
activity duration
activity attributes (Output/Input)
application area
schedule network analysis (Technique)

42. Modification that allows an acceleration of the successor activity.
lead (Technique)
firm fixed price contract (FFP)
buyer
constraint (Input)

43. Processes that organize and manage the project team
project human resource management (Knowledge Area)
Monte Carlo analysis
sub network
planning package

44. Approved specific version of the detailed scope statement - work breakdown structure (WBS) and its associated WBS dictionary
bottom-up estimating (Technique)
scope baseline
firm fixed price contract (FFP)
late start date (LS)

45. Planned dates for performing schedule activities and planned dates for meeting schedule milestones
project schedule network diagram (Output/Input)
forward pass
project schedule (Output/Input)
activity identifier

46. Hybrid contractual arrangement containing aspects of both cost reimbursable and fixed price contracts. time and material contract have no definitive end - can grow. units are preset by the buyer and seller.
time and material contract (T&M)
calendar unit
validation
buffer

47. Learning gained from the process of performing the project
stakeholder
schedule performance index (SPI)
project management information system (PMIS) (Tool)
lessons learned(Output/Input)

48. Document that describes how the project scope will be defined - developed and verified and how the work breakdown structure will be created and defined and that provides guidance on how the project scope will be managed and controlled by the project
sub network
scope management plan(Output/Input)
scheduled finish date (SF)
program management

49. Centralized management of one or more portfolios - which includes identifying - prioritizing - authorizing - managing and controlling projects - programs and related work - to achieve specific strategic business objectives
master schedule (Tool)
portfolio management (Technique)
project quality management (Knowledge Area)
early start date (ES)

50. Shortening the project schedule duration without reducing the project scope
near critical activity
product life cycle
project management office (PMO)
schedule compression