CompTIA PK0-005 Online Practice Questions and Exam Preparation

CompTIA PK0-005 Online Questions & Answers

• Question 331:

  A PM is reviewing objectives for a project in a new industry. Which of the following items should the PM review first?

  A. Applicable regulations and standards
  B. Relevance to the global environment
  C. Company vision, mission, and values
  D. Impact to the corporate brand
  C. Company vision, mission, and values

  ---

  Explanation

  When reviewing objectives--especially in a new industry--the PM should start with company vision, mission, and values because they provide the highest-level alignment for why the organization is pursuing the work and how success should support strategic direction. In Project+ terms, objectives should tie back to business goals and the organization's strategic intent; starting with vision/mission helps ensure the project's objectives are meaningful, prioritized correctly, and framed in language leadership supports.

  After that alignment is established, the PM can translate objectives into industry-specific constraints and success measures--where regulations/standards (A) become critical, especially in regulated industries.

  "Relevance to the global environment" (B) and "impact to the corporate brand" (D) are important considerations, but they are typically evaluated after the PM anchors the objectives to the organization's strategic identity and purpose.

  So the best first review item is company vision, mission, and values, which sets the "north star" for objectives; then the PM can validate feasibility and compliance via regulations, market/environment considerations, and brand implications.

• Question 332:

  During the execution of a project, a project manager wanted to discover how the number of worked hours was affecting the quality of given tasks. For a two-month period, the following data was documented:

  Average worked hours

  Which of the following describes the result?

  A. A negative correlation exists between the number of mistakes and the working hours.
  B. No correlation exists between the number of mistakes and the working hours.
  C. A low correlation exists between the working hours and the number of mistakes.
  D. A positive correlation exists between the number of mistakes and the working hours.
  D. A positive correlation exists between the number of mistakes and the working hours.

  ---

  Explanation

  A positive correlation means that as the number of worked hours increases, so does the number of mistakes. According to CompTIA Project+, understanding such correlations is crucial for effective resource and quality management.

• Question 333:

  An IT infrastructure change request needs to be implemented in the production environment. Which of the following elements are the most important prerequisites? (Select two).

  A. Rollback plans
  B. Project management plan
  C. Deployment plan
  D. Asset management plan
  E. Communication plan
  F. Resource management plan
  A. Rollback plans
  C. Deployment plan

  ---

  Explanation

  A rollback plan is a contingency plan that describes how to revert the system to its previous state in case the change fails or causes problems. A rollback plan is important to minimize the impact of a failed change and ensure the system's

  availability and functionality.

  A deployment plan is a document that outlines the steps and procedures for implementing the change in the production environment. A deployment plan is important to ensure the change is executed smoothly, efficiently, and securely, and

  that the system meets the expected performance and quality standards.

• Question 334:

  A software development team implemented an approved change but does not obtain the expected results.

  The team notifies the change control board (CCB) about the failed change. Which of the following control processes is being followed?

  A. Scope creep
  B. Recovery plan
  C. Incident report
  D. Risk response
  C. Incident report

  ---

  Explanation

  Notifying the CCB that an approved change "failed" is consistent with logging and escalating an issue / incident arising from change implementation. In CompTIA Project+ objectives, the change control process includes not only approval and implementation, but also validating the change implementation and communicating change deployment. If validation shows the change did not achieve the expected outcome, that result must be documented and escalated through the same governance path (often the CCB) so the project can decide whether to roll back, revise, or raise a new change request.

  CompTIA also separates risk management (responses to potential future events) from issue management (handling problems that have already occurred), including issue tracking, escalation path, ownership, and a resolution plan, and it highlights "connections between issues and changes." A failed implemented change is an issue now, so an incident report (documenting what happened, impact, and next steps) best matches the control process being followed.

  "Scope creep" is unauthorized scope growth, "risk response" is for anticipated risks, and "recovery plan" could be a next action, but the process described is the reporting/documentation and escalation of the incident.

• Question 335:

  A company is creating a new technology. The company is concerned that the project details could be compromised if a cloud service is used, and another company could launch the technology before the current projected delivery. Which of the following can the company do to minimize this risk?

  A. Use an on-premises project management scheduling tool.
  B. Limit access to members of the project team.
  C. Mandate overtime to get the project completed sooner.
  D. Ensure all team members have signed a non-disclosure agreement.
  B. Limit access to members of the project team.

  ---

  Explanation

  Limiting access to members of the project team is a way to minimize the risk of compromising the project details if a cloud service is used. This means that only authorized and trusted individuals can access, view, modify, or share the project

  information stored in the cloud. Limiting access can prevent unauthorized access, data leakage, cyberattacks, or espionage from external parties who might want to steal or sabotage the new technology. Limiting access can also reduce the

  risk of human error, negligence, or misconduct from internal parties who might accidentally or intentionally expose or misuse the project information.

  References:

  CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Project Communications, p. 143; Cloud Security Risks and How to Mitigate Them | Cloud Academy; Cloud Security: How to Secure Your Data in the Cloud | Kaspersky;

  Cloud Security: Best Practices for Securing Cloud Computing | Cloud Security Alliance

• Question 336:

  During the kickoff meeting, a stakeholder raises a concern that an assigned responsibility is outside of the stakeholder's domain.

  Which of the following would MOST likely be the reason?

  A. The communication plan is outdated.
  B. The project manager did not assess the stakeholders.
  C. The project manager did not update the risk register.
  D. The statement of work does not reflect the impacted stakeholders.
  D. The statement of work does not reflect the impacted stakeholders.

• Question 337:

  Which of the to and allowing interactive feedback from a project team?

  A. Text message
  B. Chat
  C. Email
  D. Videoconference
  D. Videoconference

  ---

  Explanation

• Question 338:

  During the testing phase of a project, the legal department rejected a deliverable due to compliance issues. The project manager reviewed the risk register and triggered the mitigation plan for this item. Which of the following documents should the project manager update next?

  A. Schedule
  B. Status report
  C. Issue log
  D. Task board
  C. Issue log

  ---

  Explanation

  An issue log is a document that records and tracks any issues that arise during a project and how they are resolved. It is different from a risk register, which records and tracks potential risks that may or may not occur during a project. When a

  risk becomes an issue, it means that it has occurred and has a negative impact on the project. Therefore, the project manager should update the issue log next to document the compliance issue, its cause, its impact, its priority, its owner, and

  its resolution status. Updating the issue log will help the project manager communicate the issue to the stakeholders, monitor the progress of the mitigation plan, and prevent similar issues from happening again.

  References:

  CompTIA Project+ PK0-005 Certification Study Guide, Chapter 11: Executing Projects Part 2, page 331; Project Risk Mitigation Guide + Starter Kit | Smartsheet, Risk Register section; How to Make a Risk Management Plan (Template

  Included) - ProjectManager, Risk Register section; Issue Log - Project Management Knowledge, Introduction section; Issue Log Template: Free Download | ProjectManager, Introduction and How to Use an Issue Log sections.

• Question 339:

  A project manager is working on an existing, large, complex project that involves regulatory and environmental considerations. The development of a detailed project plan will be critical.

  Which of the following should the project manager do first?

  A. Review the project charter.
  B. Start the process of engaging the stakeholders.
  C. Arrange a kickoff meeting.
  D. Evaluate potential risks.
  A. Review the project charter.

  ---

  Explanation

• Question 340:

  The project team determines that software installation can only begin after the desktops have been installed and can be powered on. Which of the following dependencies does this represent?

  A. External
  B. Internal
  C. Mandatory
  D. Discretionary
  C. Mandatory

  ---

  Explanation

  The dependency between software installation and desktop installation is a mandatory dependency. A mandatory dependency is a type of dependency that is inherent in the nature or logic of the work and cannot be avoided or changed. It is

  also known as a hard dependency or a hard logic dependency. A mandatory dependency means that one task must be completed before another task can start or finish. For example, software installation can only start after desktop

  installation is finished.

  The dependency between desktop installation and software installation represents a mandatory dependency. A mandatory dependency is a type of task dependency that is inherent in the nature of the work being performed. In this case,

  software installation cannot begin until desktops are installed and powered on, and therefore, the dependency is mandatory.

  References: CompTIA Project+ Study Guide, Chapter 3: Project Integration Management, Objective 3.1: Identify the project management processes and the interactions between them.