Download Certified Associate in Project Management.CAPM.PracticeDumps.2018-08-01.459q.vcex

Vendor: PMI
Exam Code: CAPM
Exam Name: Certified Associate in Project Management
Date: Aug 01, 2018
File Size: 1 MB

How to open VCEX files?

Files with VCEX extension can be opened by ProfExam Simulator.

ProfExam Discount

Demo Questions

Question 1
The ways in which the roles and responsibilities, reporting relationships, and staffing management will be addressed and structured within a project is described in the:
  1. Human resource management plan.
  2. Activity resource requirements.
  3. Personnel assessment tools,
  4. Multi-criteria decision analysis.
Correct answer: A
Explanation:
9.1.3.1 Human Resource Management Plan The human resource management plan, a part of the project management plan, provides guidance on how project human resources should be defined, staffed, managed, and eventually released. The human resource management plan and any subsequent revisions are also inputs into the Develop Project Management Plan process. Process: 9.1 Plan Human Resource ManagementDefinition: The process of identifying and documenting project roles, responsibilities, required skills, reporting relationships, and creating a staffing management plan.Key Benefit: The key benefit of this process is that it establishes project roles and responsibilities, project organization charts, and the staffing management plan including the timetable for staff acquisition and release.Inputs Project management plan Activity resource requirements Enterprise environmental factors Organizational process assets   Tools & Techniques Organization charts and position descriptions Networking Organizational theory Expert judgment Meetings   Outputs 1.Human resource management plan
9.1.3.1 Human Resource Management Plan 
The human resource management plan, a part of the project management plan, provides guidance on how project human resources should be defined, staffed, managed, and eventually released. The human resource management plan and any subsequent revisions are also inputs into the Develop Project Management Plan process. 
Process: 9.1 Plan Human Resource Management
Definition: The process of identifying and documenting project roles, responsibilities, required skills, reporting relationships, and creating a staffing management plan.
Key Benefit: The key benefit of this process is that it establishes project roles and responsibilities, project organization charts, and the staffing management plan including the timetable for staff acquisition and release.
Inputs 
  1. Project management plan 
  2. Activity resource requirements 
  3. Enterprise environmental factors 
  4. Organizational process assets 
  
Tools & Techniques 
  1. Organization charts and position descriptions 
  2. Networking 
  3. Organizational theory 
  4. Expert judgment 
  5. Meetings 
  
Outputs 
1.Human resource management plan
Question 2
The process of identifying and documenting relationships among the project activities is known as:
  1. Control Schedule.
  2. Sequence Activities.
  3. Define Activities.
  4. Develop Schedule.
Correct answer: B
Explanation:
Process: 6.3 Sequence ActivitiesDefinition: The process of identifying and documenting relationships among the project activities.Key Benefit: The key benefit of this process is that it defines the logical sequence of work to obtain the greatest efficiency given all project constraints.Inputs Schedule management plan Activity list Activity attributes Milestone list Project scope statement Enterprise environmental factors Organizational process assets   Tools & Techniques Precedence diagramming method (PDM) Dependency determination Leads and lags   Outputs Project schedule network diagrams Project documents updates
Process: 6.3 Sequence Activities
Definition: The process of identifying and documenting relationships among the project activities.
Key Benefit: The key benefit of this process is that it defines the logical sequence of work to obtain the greatest efficiency given all project constraints.
Inputs 
  1. Schedule management plan 
  2. Activity list 
  3. Activity attributes 
  4. Milestone list 
  5. Project scope statement 
  6. Enterprise environmental factors 
  7. Organizational process assets 
  
Tools & Techniques 
  1. Precedence diagramming method (PDM) 
  2. Dependency determination 
  3. Leads and lags 
  
Outputs 
  1. Project schedule network diagrams 
  2. Project documents updates
Question 3
Conditions that are not under the control of the project team that influence, direct, or constrain a project are called:
  1. Enterprise environmental factors
  2. Work performance reports
  3. Organizational process assets
  4. Context diagrams
Correct answer: A
Explanation:
2.1.5 Enterprise Environmental Factors Enterprise environmental factors refer to conditions, not under the control of the project team, that influence, constrain, or direct the project. Enterprise environmental factors are considered inputs to most planning processes, may enhance or constrain project management options, and may have a positive or negative influence on the outcome. Enterprise environmental factors vary widely in type or nature. Enterprise environmental factors include, but are not limited to:Organizational culture, structure, and governance; Geographic distribution of facilities and resources; Government or industry standards (e.g., regulatory agency regulations, codes of conduct, product standards, quality standards, and workmanship standards); Infrastructure (e.g., existing facilities and capital equipment); Existing human resources (e.g., skills, disciplines, and knowledge, such as design, development, legal, contracting, and  purchasing); Personnel administration (e.g., staffing and retention guidelines, employee performance reviews and training records, reward and overtime policy, and time tracking); Company work authorization systems; Marketplace conditions; Stakeholder risk tolerances; Political climate; Organization’s established communications channels; Commercial databases (e.g., standardized cost estimating data, industry risk study information, and risk databases); and Project management information system (e.g., an automated tool, such as a scheduling software tool, a configuration management system, and Project management information system (e.g., an automated tool, such as a scheduling software tool, a configuration management system, an information collection and distribution system, or web interfaces to other online automated systems). 
2.1.5 Enterprise Environmental Factors 
Enterprise environmental factors refer to conditions, not under the control of the project team, that influence, constrain, or direct the project. Enterprise environmental factors are considered inputs to most planning processes, may enhance or constrain project management options, and may have a positive or negative influence on the outcome. 
Enterprise environmental factors vary widely in type or nature. Enterprise environmental factors include, but are not limited to:
  • Organizational culture, structure, and governance; 
  • Geographic distribution of facilities and resources; 
  • Government or industry standards (e.g., regulatory agency regulations, codes of conduct, product standards, quality standards, and workmanship standards); 
  • Infrastructure (e.g., existing facilities and capital equipment); 
  • Existing human resources (e.g., skills, disciplines, and knowledge, such as design, development, legal, contracting, and  purchasing); 
  • Personnel administration (e.g., staffing and retention guidelines, employee performance reviews and training records, reward and overtime policy, and time tracking); 
  • Company work authorization systems; 
  • Marketplace conditions; 
  • Stakeholder risk tolerances; 
  • Political climate; 
  • Organization’s established communications channels; 
  • Commercial databases (e.g., standardized cost estimating data, industry risk study information, and risk databases); and 
  • Project management information system (e.g., an automated tool, such as a scheduling software tool, a configuration management system, and 
  • Project management information system (e.g., an automated tool, such as a scheduling software tool, a configuration management system, an information collection and distribution system, or web interfaces to other online automated systems). 
Question 4
The organization's perceived balance between risk taking and risk avoidance is reflected in the risk:
  1. Responses
  2. Appetite
  3. Tolerance
  4. Attitude
Correct answer: A
Explanation:
11 PROJECT RISK MANAGEMENT [..] Organizations perceive risk as the effect of uncertainty on projects and organizational objectives. Organizations and stakeholders are willing to accept varying degrees of risk depending on their risk attitude. The risk attitudes of both the organization and the stakeholders may be influenced by a number of factors, which are broadly classifed  into three themes:Risk appetite, which is the degree of uncertainty an entity is willing to take on in anticipation of a reward. Risk tolerance, which is the degree, amount, or volume of risk that an organization or individual will withstand. Risk threshold, which refers to measures along the level of uncertainty or the level of impact at which a stakeholder may have a specific interest. Below that risk threshold, the organization will accept the risk. Above that risk threshold, the organization will not tolerate the risk. For example, an organization’s risk attitude may include its appetite for uncertainty, its threshold for risk levels that are unacceptable, or its risk tolerance at which point the organization may select a different risk response. Positive and negative risks are commonly referred to as opportunities and threats. The project may be accepted if the risks are within tolerances and are in balance with the rewards that may be gained by taking the risks. Positive risks that offer opportunities within the limits of risk tolerances may be pursued in order to generate enhanced value. For example, adopting an aggressive resource optimization technique is a risk taken in anticipation of a reward for using fewer resources.
11 PROJECT RISK MANAGEMENT 
[..] 
Organizations perceive risk as the effect of uncertainty on projects and organizational objectives. Organizations and stakeholders are willing to accept varying degrees of risk depending on their risk attitude. The risk attitudes of both the organization and the stakeholders may be influenced by a number of factors, which are broadly classifed  into three themes:
  • Risk appetite, which is the degree of uncertainty an entity is willing to take on in anticipation of a reward. 
  • Risk tolerance, which is the degree, amount, or volume of risk that an organization or individual will withstand. 
  • Risk threshold, which refers to measures along the level of uncertainty or the level of impact at which a stakeholder may have a specific interest. Below that risk threshold, the organization will accept the risk. Above that risk threshold, the organization will not tolerate the risk. 
For example, an organization’s risk attitude may include its appetite for uncertainty, its threshold for risk levels that are unacceptable, or its risk tolerance at which point the organization may select a different risk response. 
Positive and negative risks are commonly referred to as opportunities and threats. The project may be accepted if the risks are within tolerances and are in balance with the rewards that may be gained by taking the risks. Positive risks that offer opportunities within the limits of risk tolerances may be pursued in order to generate enhanced value. For example, adopting an aggressive resource optimization technique is a risk taken in anticipation of a reward for using fewer resources.
Question 5
An output of the Manage Stakeholder Engagement process is:
  1. change requests
  2. enterprise environmental factors
  3. the stakeholder management plan
  4. the change log
Correct answer: A
Explanation:
13.3 Manage Stakeholder Engagement Definition:  The process of communicating and working with stakeholders to meet their needs/expectations, address issues as they occur, and foster appropriate stakeholder engagement in project activities throughout the project life cycle.Key Benefit: The key benefit of this process is that it allows the project manager to increase support and minimize resistance from stakeholders, significantly increasing the chances to achieve project success.Inputs Stakeholder management plan Communications management plan Change log Organizational process assets   Tools & Techniques Communication methods Interpersonal skills Management skills Outputs Issue log Change requests Project management plan updates Project documents updates Organizational process assets updates
13.3 Manage Stakeholder Engagement 
Definition:  The process of communicating and working with stakeholders to meet their needs/expectations, address issues as they occur, and foster appropriate stakeholder engagement in project activities throughout the project life cycle.
Key Benefit: The key benefit of this process is that it allows the project manager to increase support and minimize resistance from stakeholders, significantly increasing the chances to achieve project success.
Inputs 
  1. Stakeholder management plan 
  2. Communications management plan 
  3. Change log 
  4. Organizational process assets 
  
Tools & Techniques 
  1. Communication methods 
  2. Interpersonal skills 
  3. Management skills 
Outputs 
  1. Issue log 
  2. Change requests 
  3. Project management plan updates 
  4. Project documents updates 
  5. Organizational process assets updates
Question 6
Which process numerically analyzes the effect of identified risks on overall project objectives?
  1. Plan Risk Management
  2. Plan Risk Responses
  3. Perform Quantitative Risk Analysis
  4. Perform Qualitative Risk Analysis
Correct answer: C
Explanation:
Process: 11.4 Perform Quantitative Risk AnalysisDefinition: The process of numerically analyzing the effect of identified risks on overall project objectives.Key Benefit: The key benefit of this process is that it produces quantitative risk information to support decision making in order to reduce project uncertainty.Inputs Risk management plan Cost management plan Schedule management plan Risk register Enterprise environmental factors Organizational process assets   Tools & Techniques Data gathering and representation techniques Quantitative risk analysis and modeling techniques Expert judgment   Outputs Project documents updates
Process: 11.4 Perform Quantitative Risk Analysis
Definition: The process of numerically analyzing the effect of identified risks on overall project objectives.
Key Benefit: The key benefit of this process is that it produces quantitative risk information to support decision making in order to reduce project uncertainty.
Inputs 
  1. Risk management plan 
  2. Cost management plan 
  3. Schedule management plan 
  4. Risk register 
  5. Enterprise environmental factors 
  6. Organizational process assets 
  
Tools & Techniques 
  1. Data gathering and representation techniques 
  2. Quantitative risk analysis and modeling techniques 
  3. Expert judgment 
  
Outputs 
  1. Project documents updates
Question 7
An input to the Plan Procurement Management process is:
  1. Source selection criteria.
  2. Market research.
  3. A stakeholder register.
  4. A records management system.
Correct answer: C
Explanation:
5.2.1.5 Stakeholder Register Described in Section 13.1.3.1. The stakeholder register is used to identify stakeholders who can provide information on the requirements. The stakeholder register also captures major requirements and main expectations stakeholders may have for the project. 13.1.3.1 Stakeholder Register The main output of the Identify Stakeholders process is the stakeholder register. This contains all details related to the identified stakeholders including, but not limited to:Identification information. Name, organizational position, location, role in the project, contact information; Assessment information. Major requirements, main expectations, potential influence in the project, phase in the life cycle with the most interest; and Stakeholder classification. Internal/external, supporter/neutral/resistor, etc.  The stakeholder register should be consulted and updated on a regular basis, as stakeholders may change—or new ones identified—throughout the life cycle of the project. 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 Project management plan Requirements documentation Risk register Activity resource requirements Project schedule Activity cost estimates Stakeholder register Enterprise environmental factors Organizational process assets   Tools & Techniques Make-or-buy analysis Expert judgment Market research Meetings   Outputs Procurement management plan Procurement statement of work Procurement documents Source selection criteria Make-or-buy decisions Change requests Project documents updates
5.2.1.5 Stakeholder Register 
Described in Section 13.1.3.1. The stakeholder register is used to identify stakeholders who can provide information on the requirements. The stakeholder register also captures major requirements and main expectations stakeholders may have for the project. 
13.1.3.1 Stakeholder Register 
The main output of the Identify Stakeholders process is the stakeholder register. This contains all details related to the identified stakeholders including, but not limited to:
  • Identification information. Name, organizational position, location, role in the project, contact information; 
  • Assessment information. Major requirements, main expectations, potential influence in the project, phase in the life cycle with the most interest; and 
  • Stakeholder classification. Internal/external, supporter/neutral/resistor, etc.  
The stakeholder register should be consulted and updated on a regular basis, as stakeholders may change—or new ones identified—throughout the life cycle of the project. 
Process: 12.1 Plan Procurement Management
Definition: 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 & 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
Question 8
Reserve analysis is a tool and technique used in which process?
  1. Plan Risk Management
  2. Plan Risk Responses
  3. Identify Risks
  4. Control Risks
Correct answer: D
Explanation:
11.6.2.5 Reserve Analysis Throughout execution of the project, some risks may occur with positive or negative impacts on budget or schedule contingency reserves. Reserve analysis compares the amount of the contingency reserves remaining to the amount of risk remaining at any time in the project in order to determine if the remaining reserve is adequate. Process: 11.6 Control RisksDefinition: The process of implementing risk response plans, tracking identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness throughout the project.Key Benefit: The key benefit of this process is that it improves efficiency of the risk approach throughout the project life cycle to continuously optimize risk responses.Inputs Project management plan Risk register Work performance data Work performance reports   Tools & Techniques Risk reassessment Risk audits Variance and trend analysis Technical performance measurement Reserve analysis Meetings   Outputs Work performance information Change requests Project management plan updates Project documents updates Organizational process assets updates 5.2.6 Reserve Analysis Duration estimates may include contingency reserves, sometimes referred to as time reserves or buffers, into the project schedule to account for schedule uncertainty. Contingency reserves are the estimated duration within the schedule baseline, which is allocated for identified risks that are accepted and for which contingent or mitigation responses are developed. Contingency reserves are associated with the “known-unknowns,” which may be estimated to account for this unknown amount of rework.  As more precise information about the project becomes available, the contingency reserve may be used, reduced, or eliminated. Contingency should be clearly identified in schedule documentation. [..] Estimates may also be produced for the amount of management reserve of time for the project. Management  reserves are a specified amount of the project duration withheld for management control purposes and are reserved for unforeseen work that is within scope of the project. Management reserves are intended to address the “unknown-unknowns” that can affect a project. Management reserve is not included in the schedule baseline, but it is part of the overall project duration requirements. Depending on contract terms, use of management reserves may require a change to the schedule baseline.
11.6.2.5 Reserve Analysis 
Throughout execution of the project, some risks may occur with positive or negative impacts on budget or schedule contingency reserves. Reserve analysis compares the amount of the contingency reserves remaining to the amount of risk remaining at any time in the project in order to determine if the remaining reserve is adequate. 
Process: 11.6 Control Risks
Definition: The process of implementing risk response plans, tracking identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness throughout the project.
Key Benefit: The key benefit of this process is that it improves efficiency of the risk approach throughout the project life cycle to continuously optimize risk responses.
Inputs 
  1. Project management plan 
  2. Risk register 
  3. Work performance data 
  4. Work performance reports 
  
Tools & Techniques 
  1. Risk reassessment 
  2. Risk audits 
  3. Variance and trend analysis 
  4. Technical performance measurement 
  5. Reserve analysis 
  6. Meetings 
  
Outputs 
  1. Work performance information 
  2. Change requests 
  3. Project management plan updates 
  4. Project documents updates 
  5. Organizational process assets updates 
  6. 5.2.6 Reserve Analysis 
Duration estimates may include contingency reserves, sometimes referred to as time reserves or buffers, into the project schedule to account for schedule uncertainty. Contingency reserves are the estimated duration within the schedule baseline, which is allocated for identified risks that are accepted and for which contingent or mitigation responses are developed. Contingency reserves are associated with the “known-unknowns,” which may be estimated to account for this unknown amount of rework.  
As more precise information about the project becomes available, the contingency reserve may be used, reduced, or eliminated. Contingency should be clearly identified in schedule documentation. 
[..] 
Estimates may also be produced for the amount of management reserve of time for the project. Management  reserves are a specified amount of the project duration withheld for management control purposes and are reserved for unforeseen work that is within scope of the project. Management reserves are intended to address the “unknown-unknowns” that can affect a project. Management reserve is not included in the schedule baseline, but it is part of the overall project duration requirements. Depending on contract terms, use of management reserves may require a change to the schedule baseline.
Question 9
Updates to organizational process assets such as procurement files, deliverable acceptances, and lessons learned documentation are typical outputs of which process?
  1. Close Project or Phase
  2. Conduct Procurements
  3. Control Procurements
  4. Close Procurements
Correct answer: D
Explanation:
12.4.3.2 Organizational Process Assets Updates Elements of the organizational process assets that may be updated include, but are not limited to:Procurement file. A complete set of indexed contract documentation, including the closed contract, is prepared for inclusion with the final project fles. Deliverable acceptance. Documentation of formal acceptance of seller-provided deliverables may be required to be retained by the organization. The Close Procurement process ensures this documentation requirement is satisfed. Requirements for formal deliverable acceptance and how to address nonconforming deliverables are usually defined in the agreement. Lessons learned documentation. Lessons learned, what has been experienced, and process improvement recommendations, should be developed for the project fle to improve future procurements. Process: 12.4 Close ProcurementsDefinition: The process of completing each project procurement.Key Benefit: The key benefit of this process is that it documents agreements and related documentation for future reference.Inputs Project management plan Procurement documents   Tools & Techniques Procurement audits Procurement negotiations Records management system   Outputs Closed procurements Organizational process assets updates
12.4.3.2 Organizational Process Assets Updates 
Elements of the organizational process assets that may be updated include, but are not limited to:
  • Procurement file. A complete set of indexed contract documentation, including the closed contract, is prepared for inclusion with the final project fles. 
  • Deliverable acceptance. Documentation of formal acceptance of seller-provided deliverables may be required to be retained by the organization. The Close Procurement process ensures this documentation requirement is satisfed. Requirements for formal deliverable acceptance and how to address nonconforming deliverables are usually defined in the agreement. 
  • Lessons learned documentation. Lessons learned, what has been experienced, and process improvement recommendations, should be developed for the project fle to improve future procurements. 
Process: 12.4 Close Procurements
Definition: The process of completing each project procurement.
Key Benefit: The key benefit of this process is that it documents agreements and related documentation for future reference.
Inputs 
  1. Project management plan 
  2. Procurement documents 
  
Tools & Techniques 
  1. Procurement audits 
  2. Procurement negotiations 
  3. Records management system 
  
Outputs 
  1. Closed procurements 
  2. Organizational process assets updates
Question 10
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.
Correct answer: 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.
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.
HOW TO OPEN VCE FILES

Use VCE Exam Simulator to open VCE files
Avanaset

HOW TO OPEN VCEX AND EXAM FILES

Use ProfExam Simulator to open VCEX and EXAM files
ProfExam Screen

ProfExam
ProfExam at a 20% markdown

You have the opportunity to purchase ProfExam at a 20% reduced price

Get Now!