PK0-005 CompTIA Exam Lab Questions

The project manager should review existing artifacts to get an understanding of the purpose of the project. Existing artifacts are documents or records that provide information about the project background, context, scope, objectives, requirements, stakeholders, and deliverables. They may include documents such as project proposal, project charter, business case, feasibility study, statement of work (SOW), or contract. Reviewing existing artifacts can help to clarify the project vision and expectations and provide a basis for planning and executing the project.

The execution phase is when the project manager and the team execute the project plan, deliver the project outputs, and monitor and control the project performance. This includes tracking and managing the project budget, scope, schedule, quality, and risks. Making adjustments to the budget based on the actual project expenditures is part of the monitoring and controlling process in the execution phase. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Executing and Closing Projects, p. 263.

Company vision and mission statement should be considered in the evaluation of the project portfolio based on the company’s strategic plan. Company vision is a statement that describes the long-term aspirations and desired future state of the organization. Company mission statement is a statement that defines the core purpose and values of the organization and how it serves its customers and stakeholders. These statements provide direction and guidance for the strategic planning and decision making of the organization. They also help to align the project portfolio with the organizational goals and objectives and ensure that the projects and programs in the portfolio deliver value and benefits to the organization12

During the stabilization phase of recently deployed software, the project manager will most likely use a defect log to track and manage reported bugs. A defect log is a document that contains information about the defects or issues identified during testing or after the deployment of software. It includes the severity of the defect, the steps to reproduce the problem, and the actions taken to resolve the defect. References: CompTIA Project+ Study Guide Section 4.1.

The project manager will most likely use a defect log during the stabilization phase for recently deployed software to record a bug that is compromising data integrity. A defect log is a tool that tracks and documents any errors or flaws found in a software product or system during testing or operation. It usually includes information such as defect ID, description, severity, priority, status, resolution, and responsible person. A defect log can help to monitor and manage the quality of the software product or system and ensure that all defects are identified and resolved before delivery or release.