PK0-005 Practice Questions

When a deliverable is rejected, the change control process begins by documenting the new requirements. The project manager identifies stakeholders using the RACI matrix to ensure the right people are involved in the impact assessment. Impact assessment (cost, time, risk) must occur before seeking formal approval (sign off) from the Change Control Board (CCB). Once approved, project documents like the Change Log and Schedule are updated to reflect the new baseline. Finally, the technical work is performed (Update and test), verified by the customer (Demonstration), and communicated to the wider organization.

PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition: Section 4.6 "Perform Integrated Change Control," pages 113-120 (Process flow, Change Log updates, and Impact Assessment).

PMI, PMBOK® Guide – Seventh Edition: Section 2.5 "Project Work Performance Domain," pages 77-78 (Change control and document updates).

Project Management Institute: The Standard for Project Management, Section 3.8 "Navigate Complexity," regarding impact assessment and stakeholder engagement via RACI.

IEEE Std 12207-2017: ISO/IEC/IEEE International Standard - Systems and software engineering - Software life cycle processes (Section 6.3.5, Configuration Management and Change Control).

A Content Management System (CMS) is a software application or set of related programs used to create and manage digital content. Its core function is to provide a collaborative environment where multiple users can create, edit, review, and publish content, typically for a website, without needing advanced technical knowledge of web programming. The system manages the underlying data, versioning, and presentation, allowing contributors to focus on the content itself. This aligns with managing shared data for creation, editing, and publication by multiple contributors.

A. A system to manage electronic signatures and document workflow is more accurately described as a document management system (DMS) or a workflow automation tool, not a CMS.

B. This description is too generic; many enterprise systems, such as middleware or Enterprise Resource Planning (ERP) systems, manage database integration and messaging services.

D. This describes a records management or archival system. Its primary purpose is long-term storage and retrieval for compliance or historical reference, not active content creation and publishing.

1. CompTIA. (2022). CompTIA Project+ PK0-005 Exam Objectives. Section 1.5

"Explain common project management tools." While not defining CMS directly

it lists "Collaboration tools" which encompass the functionality of a CMS for shared content creation and management.

2. University of Washington. (n.d.). IT Connect: Content Management Systems (CMS). Retrieved from UW.edu. The documentation states

"A content management system (CMS) is software that helps users create

manage

and modify content on a website without the need for specialized technical knowledge... A CMS provides a collaborative environment..." This directly supports the concept of multiple contributors creating

editing

and publishing.

3. Valacich

J. S.

& George

J. F. (2020). Modern Systems Analysis and Design (9th ed.). Pearson. Chapter 10

"Designing the User Interface

" discusses how a CMS is used to manage the content

structure

and design of a website

enabling multiple users to contribute and publish content through a structured workflow.

The project charter is the foundational document that formally authorizes the project's existence. It provides a high-level overview of the project's objectives, key deliverables, and, crucially, the success criteria. When stakeholders dispute whether the expected results have been achieved during project closure, the charter serves as the authoritative agreement established at the project's outset. It is the primary document to consult to compare the final outcomes against the originally defined and approved measures of success.

A. Work breakdown structure: This document decomposes the project scope into deliverables and work packages; it details what work is to be done, not the business objectives or success criteria.

C. Quality plan: This document defines the quality standards and metrics for the project's deliverables, which is only one aspect of the overall project success.

D. Solution design: This document outlines the technical specifications and architecture of the final product; it describes how the solution is built, not the high-level goals it was meant to achieve.

1. CompTIA. (2022). The Official CompTIA Project+ Student Guide (Exam PK0-005). Section 2-2

"Develop a Project Charter

" describes the charter as containing key project deliverables

high-level requirements

and project approval requirements (success criteria)

which are used to determine if the project is successful.

2. University of Wisconsin-Madison

Office of the CIO. (n.d.). Project Management Toolkit: Project Charter. In the section "What is a Project Charter?"

the document states the charter includes "Success criteria: How will we know the project is successful?" This confirms its role as the reference for judging project success.

3. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.2.1

"Project Charter

" explains that the charter documents high-level project information

including measurable project objectives and related success criteria

which link the project to the strategic objectives of the organization.

The risk management strategy being used is Transfer. This strategy involves shifting the negative impact of a threat, along with ownership of the response, to a third party. By purchasing an extended warranty, the project manager transfers the financial risk associated with server failure to the vendor or warranty provider. Should a server fail, the third party is responsible for the cost of repair or replacement, thus protecting the project's budget from the financial impact of this specific risk.

B. Avoid: This strategy involves changing the project plan to eliminate the threat entirely. In this case, it would mean not purchasing the servers at all.

C. Accept: This strategy involves acknowledging a risk and not taking any action unless it occurs. The manager took a proactive step by buying a warranty.

D. Mitigate: This strategy aims to reduce the probability or impact of a risk. An example would be buying servers with redundant power supplies to reduce the chance of failure.

1. CompTIA Project+ PK0-005 Exam Objectives. (2022). Version 3.0. Section 2.4

"Given a scenario

apply the appropriate risk management activities

" lists the key risk response strategies as Avoid

Transfer

Mitigate

and Accept. This document establishes the foundational knowledge domain for the exam.

2. University of Washington

Department of Civil & Environmental Engineering. (n.d.). CEE 441: Project Risk Management. Course Lecture Notes. In discussions on risk response planning

the "Transfer" strategy is defined as shifting the consequence of a risk to a third party. The notes explicitly cite "insurance policies or warranties" as primary examples of risk transference.

3. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling (12th ed.). John Wiley & Sons. Chapter 18

"Risk Management

" section 18.9

describes risk handling

where transference is detailed as "deflecting or transferring the risk to a third party

" with insurance and warranties being common methods. This is a standard academic textbook for project management.

The analysis of stakeholder impact, whether positive or negative, is a critical input for the communication management plan. This plan outlines the strategies for engaging with different stakeholder groups. Understanding who will be positively or negatively affected allows the project manager to tailor communication messages, frequency, and methods appropriately. For instance, negatively impacted stakeholders may require more detailed and frequent communication to manage their concerns and mitigate potential resistance, while positively impacted stakeholders can be engaged as project champions. This strategic planning is formalized in the communication plan.

A. List both positively and negatively impacted stakeholders.

This action is part of creating the stakeholder register, which precedes and informs the communication plan. It is a data-gathering step, not the strategic action taken with the findings.

C. List the negatively impacted stakeholders only.

Ignoring positively impacted stakeholders is a critical error. They are key allies and potential advocates for the project whose support needs to be cultivated through effective communication.

D. List the positively impacted stakeholders only.

Ignoring negatively impacted stakeholders is a major risk. Their opposition, if not managed properly through a tailored communication strategy, can derail the project.

1. CompTIA Project+ Study Guide for Exam PK0-005

(2022). CompTIA.

Chapter 4

"Planning the Project

" Section: "Develop the Communications Management Plan

" explains that the plan is based on the information needs of the stakeholders. It states

"The stakeholder register is an input to this process because you need to know who the stakeholders are and what their communication requirements are." This directly links the stakeholder analysis (which includes their impact) to the creation of the communication plan.

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Section 2.2.3

"Stakeholders

" discusses that understanding stakeholders' sentiments (positive

negative

neutral) is key to developing effective engagement strategies. The communication approach is a primary component of the overall stakeholder engagement strategy.

3. Heldman

K. (2021). CompTIA Project+ Study Guide: Exam PK0-005 (2nd ed.). Sybex.

Chapter 6

"Planning Communications

" details the inputs to the Communications Management Plan. It explicitly lists the stakeholder register as a key input

noting that the register contains "stakeholder classification" which is used to determine the appropriate communication strategy for each group.

A focus group is a qualitative data-gathering technique where a small, representative group of people is brought together to provide feedback, opinions, and perceptions about a product, service, or concept. The scenario describes multiple small teams (six people each) being coordinated to record their opinions on a new product. This feedback is then used to define the final version for production. This aligns perfectly with the purpose and structure of a focus group, which is a key tool for eliciting stakeholder requirements and validating product concepts before a full-scale launch.

A. Demonstration: A demonstration is a one-way presentation to show how a product functions. While it can precede feedback, the core activity described is the feedback session itself.

B. Workshop: A workshop is a broader, collaborative session where participants actively work together to create a specific deliverable, such as a plan, design, or solution, not just provide opinions.

C. Brainstorming: Brainstorming is a technique focused on generating a large volume of new ideas in a free-form manner, rather than providing structured feedback on an existing product.

1. CompTIA. (2022). CompTIA Project+ (PK0-005) Exam Objectives. Section 2.2

"Given a scenario

use the appropriate tool or technique to elicit project requirements

" lists "Focus groups" as a specific technique for this purpose.

2. University of Wisconsin-Madison. (n.d.). Program Development and Evaluation: Data Collection Methods. In the section on Focus Groups

it states

"A focus group is a small group interview with a trained moderator... to learn about the participants’ opinions

beliefs

and attitudes about a topic." This directly supports the scenario's activity of recording opinions to define a product.

3. Carnegie Mellon University. (n.d.). Eberly Center: Focus Groups. The center's teaching resources define a focus group as a method to "gather in-depth

qualitative data from a small group of people... to explore their perspectives on a particular topic." This aligns with using the teams' opinions to define the final product.

4. University of California

Berkeley. (n.d.). Project Management Office: Business Analysis - Elicitation. The documentation differentiates techniques

describing workshops (e.g.

JAD sessions) as events to "produce a work product" through collaboration

which is distinct from the opinion-gathering nature of the focus group described in the question.

The production environment is the live, operational setting where an application is deployed for its intended use by end-users, in this case, the clients. The key phrase "highly utilized by clients" is the defining characteristic of a production environment. While a new release is being prepared, the current, stable, and client-facing version of the application resides in production. The other environments (Development, Testing, QA) are pre-production stages used internally to build and validate the new release before it is deployed to the live production environment for client use.

A. Development: This environment is exclusively for developers to write, build, and unit-test code. It is unstable and not accessible to clients.

C. Testing: This is a controlled environment where testers formally verify application functionality and find defects before a release. It is not for live client operations.

D. QA: The Quality Assurance environment is used for pre-release validation to ensure the application meets all quality standards. It is not the live system for end-users.

1. University Courseware: University of Washington

Paul G. Allen School of Computer Science & Engineering. (n.d.). CSE 403: Software Engineering

Lecture 18 - Testing. "Production: The live system that users interact with. This is where the money is made or lost." This definition clearly distinguishes the production environment as the client-facing system.

2. Academic Publication: Pressman

R. S.

& Maxim

B. R. (2020). Software Engineering: A Practitioner's Approach (9th ed.). McGraw-Hill. In Chapter 21

"Software Testing Strategies

" the text distinguishes between development testing and validation in controlled environments versus the operational "production" environment where the software is used by its intended audience.

3. University Courseware: Carnegie Mellon University

School of Computer Science. (n.d.). 15-313: Foundations of Software Engineering

Lecture 21: DevOps. The course materials describe the deployment pipeline where code moves from development to testing/staging environments before finally being deployed to the production environment

which is defined as the live environment serving users.

The project sponsor, a key stakeholder, was unaware of the details surrounding project issues, indicating a failure in the communication process. The communication plan is the document that defines what information will be shared, with whom, when, and through which channels. The scenario demonstrates that the current plan is ineffective at keeping the sponsor adequately informed, preventing them from contributing effectively to problem-solving. Therefore, the communication plan must be revised to ensure timely and appropriate information flows to all key stakeholders, especially regarding critical project issues. This revision will prevent surprises in high-level meetings and enable better decision-making.

A. Project dashboard: A dashboard is a visual reporting tool. The problem is the failure to communicate information, not necessarily the tool used to display it.

B. Gap analysis: This is a planning technique used to compare the current state to a desired future state, not for managing ongoing project communications.

C. Risk register: This document logs potential risks. While the issues may have originated as risks, the core failure described is in communication, not in risk documentation.

1. CompTIA Project+ PK0-005 Exam Objectives. (2022). Section 2.3

"Given a scenario

use a communication plan." This objective highlights the plan's role in managing stakeholder communication requirements

including the frequency

method

and content of communications

which failed in the given scenario.

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.5

"Project Performance Domain: Delivery

" and Section 4.2.5

"Communication." The PMBOK® Guide emphasizes that effective communication

as outlined in the communication plan

is essential for stakeholder engagement and ensuring stakeholders have the information needed to make decisions. The sponsor's inability to provide next steps is a direct result of a communication breakdown.

3. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling (12th ed.). Wiley. Chapter 8

"Project Communications

" details that the communications plan is the primary tool for ensuring that stakeholders

like a project sponsor

receive the right information at the right time to fulfill their roles.

The project manager is engaging in a crucial project closing activity: recognizing and celebrating the team's accomplishments. A company-wide announcement of a successful project completion, coupled with a public thank you to the team members, serves to formally acknowledge their efforts and contributions. This action boosts team morale, provides a sense of closure, and reinforces positive performance, which is essential for motivating individuals for future projects. This practice is a key component of effective team management and project closure.

A. Bringing attention to the project sponsor: While the sponsor is vital, the action described specifically focuses on thanking the team members, not highlighting the sponsor's role.

B. Sharing lessons learned: A success announcement is not the appropriate forum for sharing detailed lessons learned, which is a formal process involving documentation and review meetings.

C. Collecting feedback: An announcement is a one-way communication method; it is used for disseminating information, not for gathering feedback from the company.

1. CompTIA. (2022). CompTIA Project+ PK0-005 Exam Objectives. Section 4.3

"Explain the importance of closing a project or phase." The objective explicitly lists "Celebrate success" as a key activity in the project closeout process.

2. West

R. E.

& Rich

P. J. (Eds.). (2022). Project Management for Instructional Designers. EdTech Books. Chapter 10

"Closing a Project

" Section: "Celebrate Success." This chapter states

"It is important to celebrate the successes of the project team... A celebration can be as simple as a company-wide email." This directly supports the scenario described. (Available at: https://edtechbooks.org/pm4id/closingaproject)

3. Massachusetts Institute of Technology (MIT) OpenCourseWare. (2012). 15.S21 Nuts and Bolts of Business Plans. Session 10: Project Management. The course materials emphasize the final phase of a project

which includes "Recognition and Celebration" to acknowledge the team's effort and formally mark the project's conclusion.

An agenda is the foundational document for an effective meeting. Distributing it in advance clearly outlines the topics to be discussed, which ensures all necessary items are planned for and addressed. It also provides context for invitees, enabling them to understand the meeting's purpose and determine if their participation is required. This process helps guarantee that the correct stakeholders are present and prepared, making the agenda the most beneficial tool for achieving both stated goals.

A. Assign action items to attendees.

Action items are tasks resulting from a meeting's discussion and decisions; they are typically assigned during or after the meeting, not before.

C. Email the minutes from the previous meeting.

Previous minutes provide a historical record but do not define the scope or topics for the new meeting, which is the agenda's function.

D. Schedule a convenient time.

A convenient time increases the likelihood of attendance but does not ensure the correct people attend or that all specific topics are covered.

---

3. References

1. CompTIA Project+ PK0-005 Exam Objectives. (2022). CompTIA.

Section 1.5: "Explain the importance of communication management." This objective covers essential communication activities, including the proper planning and execution of meetings, for which an agenda is a critical artifact for setting expectations and topics.

2. Baskerville, R. L., & Stage, P. A. (1995). Meeting Management (Technical Note CMU/SEI-95-TN-002). Software Engineering Institute, Carnegie Mellon University.

Page 4, "The Agenda": "The agenda is the single most important tool for managing a meeting... It tells the participants what the meeting is about, what they are expected to contribute, and what will be the result." This directly supports that an agenda ensures topics are addressed and the right people attend.

3. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Section 4.2.5, "Artifacts": The PMBOK® Guide lists "Agendas" as a common project artifact. It implicitly defines its purpose as outlining the items for discussion and the objectives for meetings, which is fundamental to project communication and stakeholder engagement.