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. Processes required to ensure timely and appropriate generation - collection - distribution - storage - retrieval - and ultimate disposition of project information
program
project communications management (Knowledge Area)
logical relationship
backward pass

2. Processes and activities of the performing organization that determine quality policies - objectives and responsibilities so that the project will satisfy the needs for which it was undertaken
risk register (Output/Input)
project quality management (Knowledge Area)
pareto chart (Tool)
Monte Carlo analysis

3. Hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units
organizational breakdown structure (OBS) (Tool)
trend analysis (Technique)
variance analysis (Technique)
scope management plan(Output/Input)

4. Hierarchal structure of resources by resource category and resource type used in resource leveling schedules and to develop resource limited schedules and which may be used to identify and analyze project human resource management
resource breakdown structure
earned value (EV)
projectized organization
initiating processes (Process Group)

5. Defining how to conduct risk management activities for a project
risk category
plan risk management (Process)
finish date
project human resource management (Knowledge Area)

6. Authorized budget assigned to the scheduled work to be accomplished for a schedule activity or work breakdown structure component
verification
trend analysis (Technique)
planned value (PV)
develop schedule (Process)

7. Performed to defined a new project or a new phase of an existing project by obtaining authorization to start the project or phase
staffing management plan
budget
performance measurement baseline
initiating processes (Process Group)

8. 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
parametric estimating (Technique)
risk register (Output/Input)
manage project team (Process)
BCWS

9. Dependency between two project schedule activities or between project schedule activity and schedule milestone.
project scope statement (Output/Input)
work breakdown structure (WBS) (Output/Input)
logical relationship
path convergence

10. The merging or joining of parallel schedule network paths into the same node in a project schedule network diagram. characterized by a schedule activity with more than one predecessor activity
path convergence
sub network
claim
monitor and control risks (Process)

11. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed.
regulation
expert judgment (Technique)
methodology
conduct procurements (Process)

12. The time in calendar units between the actual start date of the schedule activity and either the data date of the project schedule if the schedule activity is in progress or the actual finish date if the schedule activity is complete
actual duration
work performance information
strengths - weaknesses - opportunities - threats analysis (SWOT)
closing processes (Process Group)

13. Analyzing activity sequences - durations - resource requirements and schedule constraints to create the project schedule
lag (Technique)
develop schedule (Process)
requested change(Output/Input)
project time management (Knowledge Area)

14. One of the defining points of a schedule network; a junction point joined to some or all of the other dependency lines
role
node
work package
template

15. Communicating and working with stakeholders to meet their needs and address issues as they occur
report performance (Process)
rework
estimate activity durations (Process)
manage stakeholder expectations (Process)

16. Those processes performed to finalize all activities across all project management process groups to formally close the project or phase
closing processes (Process Group)
statement of work (SOW)
network path
projectized organization

17. Aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline
determine budget (Process)
flowcharting (Technique)
schedule management plan (Output/Input)
earned value (EV)

18. A short unique numeric or text identification assigned to each schedule activity to differentiate that project activity from other project activities. typically unique within any one project schedule network diagram
define scope (Process)
fast tracking (Technique)
activity identifier
plan risk response (Process)

19. An artifact that is produced - is quantifiable and can be either an end item in itself or a component item
project time management (Knowledge Area)
product
regulation
schedule network analysis (Technique)

20. Identifying all people or organizations impacted by the project and documenting relevant information regarding their interest - involvement and impact on project success
risk
defect repair
three point estimate (Technique)
identify stakeholders (Process)

21. The process of defining and documenting stakeholder needs to meet project objectives
sub network
scope management plan(Output/Input)
collect requirements (Process)
performance reports (Output/Input)

22. Group of potential causes of risk. such as technical - external - organizational - environmental - project management. a category may include subcategories
resource calendar
milestone
risk category
deliverable (Output/Input)

23. Risk response planning technique that indicates the project team has decided not to change the project management plan to deal with a risk - or is unable to identify any other suitable response strategy
material
risk acceptance (Technique)
lead (Technique)
risk breakdown structure (RBS)

24. Collection of projects or programs and other work that are grouped together to facilitate effective management of that work to meet strategic business objectives
risk breakdown structure (RBS)
portfolio
analogous estimating (Technique)
develop project charter (Process)

25. Total number of work periods required to complete a schedule activity or work breakdown structure component.
duration (DU or DUR)
project organization chart (Output/Input)
project scope management (Knowledge Area)
milestone

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
brainstorming (Technique)
defect
resource
close procurements (Process)

27. Defined function to be performed by a project team member
project life cycle
role
initiating processes (Process Group)
finish to start (FS)

28. Graphical representation of situations showing causal influences - time ordering of events and other relationships among variables and outcomes
risk
perform quality assurance (Process)
identify risks (Process)
influence diagram (Tool)

29. An entry in the work breakdown structure that can be at any level
work breakdown structure component
resource histogram
verify scope (Process)
closing processes (Process Group)

30. Documents and data on prior project including project files - records - correspondence - closed contracts - and closed projects
scope management plan(Output/Input)
historical information
start date
time scaled schedule network diagram (Tool)

31. 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
estimate (Output/Input)
backward pass
risk register (Output/Input)
portfolio management (Technique)

32. Extending or generating parallel schedule network paths from the same node in a project schedule network diagram. characterized by schedule activity with more than one successor activity
perform integrated change control (Process)
earned value management (EV
path divergence
total float

33. Summary level schedule that identifies the major schedule milestone
scope creep
program management
milestone schedule (Tool)
role

34. Cost - time - quality - technical or resource value used as a parameter and which may be included in product specification. crossing the threshold should trigger some action.
monitor
threshold
project initiation management (Knowledge Area)
requirement

35. The person assigned by the performing organization to achieve the project objectives
analogous estimating (Technique)
project manager
activity
forward pass

36. Document describing how roles and responsibilities - reporting relationships and staffing management will be addressed and structured for the project
milestone
node
validation
human resource plan

37. A formal approved document that defines how the project is executed - monitored - and controlled.
change control system (Tool)
project management plan (Output/Input)
preventative action
develop project management plan (Process)

38. Directing - managing - performing and accomplishing the project work - providing the deliverables and providing work performance information
variance
execute
resource leveling (Technique)
sensitivity analysis

39. The calculation of late finish dates and late start dates for uncompleted portions of all schedule activities. determined by working backward through the schedule network logic from the projects end date
tool
change requests
actual cost (AC)
backward pass

40. Term used in precedence diagramming method for a logical relationship in current usage. precedence relationship - logical relationship and dependency are interchangeably used
early finish date (EF)
precedence relationship
fast tracking (Technique)
project life cycle

41. 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.
organizational breakdown structure (OBS) (Tool)
workaround
total float
s-curve

42. Measure of schedule efficiency on a project. ratio of earned value (EV) and the planned value (PV). SV = EV minus PV.
float
performance measurement baseline
schedule performance index (SPI)
triggers

43. A formally constituted group of stakeholders responsible for reviewing - evaluating - approving - delaying or rejecting changes to a project - with all the decisions and recommendations being recorded
float
change control board (CCB)
path convergence
report performance (Process)

44. Implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks and evaluating risk process throughout the project
scope
milestone schedule (Tool)
monitor and control risks (Process)
estimate (Output/Input)

45. Smaller portion of the overall project created when a project is subdivided by their logical relationship
activity list (Output/Input)
subproject
node
program evaluation and review technique (PERT)

46. A technique that explores the accuracy of assumptions and identifies risks to the project from inaccuracy - inconsistency - or incompleteness of assumptions
assumptions analysis (Technique)
strengths - weaknesses - opportunities - threats analysis (SWOT)
parametric estimating (Technique)
project scope

47. Examining or measuring to verify whether an activity - component - product - result of service conforms to specified requirements.
special cause
inspection (Technique)
lessons learned knowledge base
contingency reserve(Output/Input)

48. Analytical technique used to determine basic underlying reason that causes a variance or defect or risk
activity code
root cause analysis (Technique)
project schedule network diagram (Output/Input)
activity duration

49. Condition or situation unfavorable to the project - a negative set of circumstances - a negative set of events - a risk that will have a negative impact on a project objective if it occurs - or a possibility for negative changes
close procurements (Process)
threat
sub network
common cause

50. The expected total cost of a schedule activity - a work breakdown structure component or the project when the defined scope of work will be completed. Calculated based on performance to date or estimated by the project team based on other factors
estimate at completion (EAC)(Output/Input)
sponsor
parametric estimating (Technique)
functional manager