CompTIA PK0-005 CompTIA Project+ Certification (2026) Exam Practice Test

This answer is based on the best practice of conflict resolution in project management, which is to use a collaborative or problem-solving approach that seeks a win-win outcome for all parties involved12. By facilitating a meeting, the project manager can help the team members communicate effectively, understand each other’s perspectives, and find a mutually acceptable solution that meets the project requirements. This way, the project manager can also maintain team morale and cohesion, and avoid imposing a decision that may cause resentment or dissatisfaction among the team members3. References = CompTIA Project+ Certification Study Guide4, CompTIA Project+ Certification Exam Objectives5, How Do You Handle Conflict in Project Management?1, 7 Strategies for Conflict Resolution in Project Management2, The Conflict Resolution Skills Every Project Manager Needs3

The communication plan defines the meeting cadence, frequency, participants, formats, and methods of communication. If participation is low, the project manager refers to this plan for validation and adjustment. This is part of governance and compliance to ensure the right stakeholders are engaged appropriately.

Videoconference is the best tool to use when conducting project meetings across time zones, as it allows real-time communication, visual cues, screen sharing, and collaboration among the participants. Videoconference can also help build rapport and trust among the team members, and reduce the risk of misunderstandings or miscommunication. Videoconference tools such as Zoom, Skype, or Google Meet can also accommodate different time zones by showing the local time of each participant and allowing them to schedule meetings in advance12.

The total amount that should be budgeted for the task is calculated by adding the expected value of the risk to the original estimate. The expected value of the risk is the product of the probability and the impact of the risk. In this case, the expected value of the risk is 0.2 x (5 days and $1,000) = 1 day and $200. Therefore, the total amount that should be budgeted for the task is 9 days and $3,000 + 1 day and $200 = 10 days and $3,2001.

Continuous Integration and Continuous Delivery (CI/CD) aim to accelerate software delivery while maintaining high quality through frequent automated testing and deployment. This practice is endorsed by CompTIA Project+ as part of modern project methodologies for improving efficiency and quality.

The technical lead should follow the escalation path. The issue described is a performance/response problem that is impacting delivery while the PM is unavailable. CompTIA Project+ emphasizes having and using an escalation path as part of issue management and governance, ensuring problems are raised to the correct authority quickly (e.g., acting PM, functional manager, HR/people manager, or sponsor depending on severity and policy). Escalation is appropriate because the team needs timely intervention to restore progress and accountability.

Updating the issue register (B) is a useful documentation step, but it does not by itself resolve the problem; escalation drives action. Informing all stakeholders (A) is usually excessive and can create noise or reputational harm; stakeholder communication should be controlled and targeted, typically after escalation determines impacts and a recovery approach. Initiating a change request (D) is inappropriate because the core problem is not a requested change to scope or requirements; it is a delivery/behavior issue requiring management intervention.

A good escalation approach is: document facts (missed deliverables, non-responsiveness), attempt direct contact, then escalate per policy to the designated backup PM or functional manager for corrective action (reassign work, coaching, or formal performance steps).

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.

Avoiding is a conflict resolution technique that involves postponing or withdrawing from a conflict situation. The project manager is using this technique by taking a break and continuing the meeting on another day, hoping that the conflict will resolve itself or become less important over time. This technique may be appropriate when the conflict is trivial, the potential damage is greater than the benefits, or more information is needed before making a decision. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Executing and Closing Projects, page 287; [CompTIA Project+ Certification Exam Objectives], Domain 3: Project Execution, Objective 3.2: Given a scenario, apply appropriate conflict resolution techniques.

A common disadvantage of cloud models is higher dependency on the vendor—often described as vendor lock-in. When solutions rely on a provider’s proprietary services, APIs, data formats, or managed offerings, switching providers (or moving back on-premises) can become costly and complex. This dependency can reduce portability and negotiating leverage over time, and it can increase switching costs if pricing, service levels, or strategic needs change.

Options A and B are generally the opposite of typical cloud benefits: cloud platforms usually provide elastic scaling and abundant capacity relative to on-prem constraints (assuming budget allows). Latency (C) can be a disadvantage in some architectures, but it isn’t as consistently defining as vendor dependence—latency can be mitigated through region selection, edge services, and network design, and many workloads experience acceptable performance. Vendor dependency/lock-in, however, is a well-known structural risk of adopting cloud-native services.

From a project management lens, this matters in planning and governance: procurement strategy, architectural choices, and exit/migration planning help manage the risk of over-dependence on a single provider.

Issue log and change log are documents that should be used to record the event where the project team has just experienced an unexpected event and implemented a work-around. An issue log is a document that tracks and records any issues or problems that arise during a project and how they are resolved. An issue log can help to monitor and control the project performance and quality and prevent any negative impacts on the project objectives and deliverables. A change log is a document that tracks and records any changes or modifications that are made to the project scope, schedule, cost, quality, or resources during a project. A change log can help to document the change request, approval, implementation, and impact of each change and ensure traceability and transparency.

Identifying the root cause analysis. Identifying the root cause analysis is a quality assurance tool that can help to find and eliminate the underlying causes of quality problems or defects. Root cause analysis is a systematic process of asking why a problem occurred and tracing it back to its source. Root cause analysis can help to prevent recurrence of the same or similar problems, improve quality performance, and reduce costs and risks12

In project management, understanding the difference between the current state and the desired future state is essential for identifying gaps and planning improvements. The current state refers to the organization's existing conditions, processes, or performance levels. The desired future state represents the target conditions or performance levels the organization aims to achieve through the project. This comparison is fundamental in conducting a gap analysis, which helps in planning the necessary steps to transition from the current to the desired state.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.3: Given a scenario, apply the change control process throughout the project life cycle, understanding the current and desired states is crucial for effective change management and project planning.

This activity is best described as approving deliverables (often in a procurement/payment context). The PM is verifying that what the vendor invoiced—and the supporting documentation—matches what the Statement of Work (SOW) requires. That is a form of verification/acceptance: confirming the vendor has provided the contracted deliverables or services to the agreed standard before payment is approved. In Project+ procurement management, PMs are expected to manage vendor performance against contractual artifacts (SOW, acceptance criteria) and ensure work is validated before closing out payments and contracts.

“Enforcing vendor rules of engagement” is broader and might include communication protocols, escalation paths, or behavioral expectations, but the scenario is specifically about matching invoices and documentation to SOW requirements—an acceptance/verification step. “Reporting overall process” is unrelated, and “scheduling team touch points” refers to meeting cadence and coordination, not invoice/SOW reconciliation.

In practice, this check reduces financial risk (paying for unperformed work), strengthens auditability, and supports clean contract administration. It also helps detect scope misunderstandings early—before they become disputes—by tying vendor charges directly back to agreed deliverables in the SOW.

The team is leveraging lessons learned to create a preventive plan for avoiding issues in the upcoming project enhancement. This falls under risk management and compliance, ensuring previous failures do not repeat.

A milestone chart is the best chart to use to show major accomplishments for key events, because it displays the important deliverables or outcomes of a project along a timeline12. A milestone chart can provide a high-level overview of the project progress and achievements, without showing the details of each task or activity34. A milestone chart can also help communicate the project status and expectations to the stakeholders, and identify any potential risks or delays that may affect the project completion56. References = CompTIA Project+ Certification Study Guide7, CompTIA Project+ Certification Exam Objectives8, What is a Milestone Chart?1, How to Create a Milestone Chart in Excel in 3 Steps2, Milestone Chart: The Easiest Way to Track Project Milestones3, How to Use Milestones in Project Management4

Agile methodologies emphasize flexibility and iterative progress, so strict deadlines can be a concern. They may limit the team’s ability to adapt and respond to change, as emphasized by CompTIA Project+ in agile project management principles.

Agile is a methodology that emphasizes iterative and incremental development, customer collaboration, and responsiveness to change. Agile is suitable for developing a minimum viable product (MVP), which is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development. Agile allows the project sponsor to deliver an MVP quickly and test it with real users, and then adapt the product based on the feedback and changing requirements. Agile also reduces the risk of wasting time and resources on a product that does not meet the customer’s needs or expectations123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 2: Project Methodologies, p. 55; What is a Minimum Viable Product (MVP)? | Agile Alliance; Minimum Viable Product (MVP): What is it & Why it Matters - Atlassian

The PM should create a project organizational chart to clarify who is who, reporting lines, and role visibility across the team. When team members are unclear about each other’s roles, the fastest way to reduce confusion is to make the project structure explicit: who leads which workstream, who approves decisions, who supports, and how to escalate. This aligns with Project+ people/resource management expectations: establish clear responsibilities and team structure to reduce duplication, gaps, and conflict caused by ambiguity.

A project plan is broader (scope/schedule/budget/governance), but it won’t necessarily provide a simple, visual map of roles. A road map is high-level sequencing of outcomes over time; it’s not meant to define roles. A milestone chart highlights key dates and deliverables, not responsibilities.

In practice, the PM often pairs the project org chart with a RAM/RACI for detailed accountability, but since the question asks which chart to create to fix role confusion, the best answer is the project organizational chart.

the brand of a project should deliver the message about its value and goals, and a proper brand helps the project get the necessary support and increases loyalty. The project that promotes new initiatives to expand its benefit to other communities is the one that best represents the project impact to a company’s brand value, as it shows the company’s vision, cause, and reputation.

A Request for Proposal (RFP) is a document issued by an organization to solicit proposals from potential vendors for a specific solution or service. It outlines the organization's requirements and criteria for evaluation, allowing vendors to propose how they would meet those needs. An RFP is appropriate when the company seeks detailed proposals for a solution to its specific needs.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 3.4: Explain important project procurement and vendor selection concepts, understanding the use of RFPs is essential for effective procurement management.

The RACI (Responsible, Accountable, Consulted, Informed) matrix is used to document which resources are responsible for which tasks. The RACI matrix is a tool that helps to clarify roles and responsibilities on a project. It assigns a level of responsibility to each resource involved in the project. References: CompTIA Project+ Study Guide Section 3.4.

The project manager should use a RACI matrix to document which resources are responsible for which tasks. A RACI matrix is a type of responsibility assignment matrix (RAM) that plots the roles and responsibilities of resources on a project team. RACI stands for Responsible, Accountable, Consulted, and Informed. A RACI matrix can help to clarify who does what on a project, avoid confusion and duplication of work, and improve communication and collaboration among team members.

The project charter is a high-level authorization document that outlines the purpose, objectives, and identifies key stakeholders. It does not contain detailed schedules, risk management plans, or resource allocation — those come later in the planning process.

Stress testing is a type of performance testing that evaluates how a system behaves under extreme load conditions, such as high volume of data, concurrent users, or transactions12. Stress testing can help to identify the system’s breaking point, bottlenecks, and resource limitations, and to ensure that the system can recover from failures and maintain its functionality34. In this case, the team performed stress testing to validate that system performance will not be impacted by migrating all data to a single system following the merger of two companies. This implies that the team simulated a high amount of data transfer and processing, and measured the system’s response time, throughput, availability, and reliability under such load. Stress testing is better than the other options because:

Regression testing is a type of functional testing that verifies that a system’s existing features and functionality are not affected by a change or an update56. Regression testing does not focus on system performance or load conditions, but rather on system correctness and quality.

Smoke testing is a type of functional testing that checks the basic functionality and stability of a system before performing more detailed and comprehensive testing78. Smoke testing does not measure system performance or load conditions, but rather ensures that the system is ready for further testing.

Automation testing is a technique of using software tools or scripts to execute test cases and compare the actual results with the expected results910. Automation testing is not a specific type of testing, but rather a way of performing testing. Automation testing can be applied to various types of testing, including stress testing, regression testing, and smoke testing.

References = CompTIA Project+ Certification Study Guide, CompTIA Project+ Certification Exam Objectives, What is Stress Testing?1, Stress Testing: A Complete Guide2, What is Regression Testing?3, Regression Testing: A Complete Guide4, What is Smoke Testing?5, Smoke Testing: A Complete Guide6, What is Automation Testing?7, Automation Testing: A Complete Guide8

The PM should consult the communication plan because it defines who receives updates, what information they need, when/how often they should receive it, and which channel/form should be used (email, meeting, dashboard, report, chat, etc.). Project+ emphasizes tailoring communications to stakeholder needs and using a planned approach to avoid confusion, missed expectations, or inconsistent messaging—especially around deliverables, acceptance, and progress.

A dashboard is a tool that may be used to publish updates, but it doesn’t decide communication rules by itself. A status report is one possible artifact (often produced on a cadence defined in the communication plan), but it’s not the governing document for selecting channels and audiences. Meeting minutes document what happened in a meeting; they’re useful for traceability, but they’re not the primary guide for how deliverable updates should be distributed going forward.

So, when the question is specifically “how to send updates,” the communication plan is the source of truth: it ensures consistent delivery, reduces noise, and aligns with stakeholder preferences and governance requirements.

The Project Gantt chart is a scheduling tool used to track task progress and timelines. When tasks are completed ahead of schedule, updating the Gantt chart ensures accurate tracking. This aligns with CompTIA Project+ recommendations on project scheduling and monitoring.

A weak matrix organizational structure is one where the project manager has low authority and the functional manager has high authority. The project manager is considered to be a coordinator or an escalator, and the team members are primarily loyal to their functional units. This can cause issues with team motivation, communication, and performance1

An ERP (Enterprise Resource Planning) system integrates financial management, HR, and operations. In this case, ERP can handle time tracking and cost reporting together. EDRMS manages documents, CRM handles customer relationships, and CMS manages content—not project costs.

Application deployment typically involves making a software application available for use, often involving downtime or unavailability of the application. The description of the project manager notifying users about the application being unavailable for a certain period aligns with standard practices during deployment phases. The other options, such as rollback plans, validation checks, and maintenance window schedules, although important, do not directly indicate the action of making an application available for use, as described in the scenario.

A videoconference is the best channel for delivering weekly presentations to geographically dispersed stakeholders because it supports real-time, synchronous communication while enabling visual content sharing (slides, dashboards, demos) and interactive Q&A. CompTIA Project+ emphasizes selecting communication methods appropriate to the audience and purpose; presentations generally benefit from richer media than text-only channels, especially when alignment and decision-making are needed.

“In-person meetings” (A) are impractical “across the country” on a weekly cadence due to travel cost, time, and logistics. “Email” (B) can distribute slide decks, but it’s asynchronous and often results in misunderstandings, delayed feedback, and lower engagement—weak for a presentation format requiring discussion. “Telephone” (C) is synchronous but lacks visuals, making it harder to present complex status, plans, or demonstrations effectively.

Using videoconferencing also supports meeting best practices: agenda and timeboxing, screen sharing for consistent messaging, and easy recording (where appropriate) to help absent stakeholders catch up—aligning with Project+ meeting and communication management expectations.

When managing vendor contracts, the PM must validate vendor status reports to confirm progress and monitor vendor performance against agreed service levels. Approving deliverables occurs less frequently, and creating charters/baselining schedules are initiation tasks, not recurring vendor management tasks.

In agile methodology, an epic is a large user story or body of work that can be broken down into smaller backlog items deliverable within iteration cycles. This enables large projects to be incrementally deployed while maintaining predictable iteration lengths.

In response to new legislation requiring the release of contractors or their conversion to full-time employees, the project manager should prioritize compliance with the law. This may involve using only full-time employees, even if it results in project delays. The focus should be on legal compliance and the ethical treatment of workers, rather than solely on project timelines.

References = The answer is based on standard project management practices and the typical response to changes in legislation affecting project staffing. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources.

Customer relationship management (CRM) software would be the best to use to store information related to business transactions. CRM software is a type of software that helps businesses manage their interactions and relationships with current and potential customers. CRM software can store and organize information such as customer contact details, purchase history, preferences, feedback, complaints, etc. CRM software can help businesses improve customer service, satisfaction, loyalty, retention, and revenue1

After completing development and internal testing phases, the next step is to conduct User Acceptance Testing (UAT). UAT is performed by the end-users to ensure the system meets their requirements and is ready for deployment.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.3: Explain the importance of quality management and testing in project management, UAT is a critical phase to validate that the product meets the business needs and requirements.

A downtime window schedule specifies a timeframe during which systems can be taken offline or changed without affecting business operations. CompTIA Project+ includes this as part of deployment planning to ensure minimal disruption to stakeholders.

The project manager should distribute an agenda before a call to ensure all meeting items are addressed and the correct participants attend. An agenda is a document that outlines the purpose, topics, and objectives of a meeting. It also includes information such as date, time, duration, location, attendees, and roles. Distributing an agenda can help to prepare the participants for the meeting, set clear expectations, and facilitate a productive and focused discussion12

A data warehouse is a centralized repository that stores data from multiple sources in a structured and organized manner. It is designed to facilitate reporting and analysis by consolidating large volumes of data.

In the CompTIA Project+ PK0-005 exam objectives, under Domain 4.2: Compare and contrast common project team organizational structures, understanding the implementation of data storage solutions like data warehouses is essential .

Implementing a data warehouse allows the project manager to efficiently manage and analyze data from various sources, supporting informed decision-making processes.

Unit testing is a testing technique that verifies the functionality and quality of individual units or components of software, such as modules, classes, functions, etc. Unit testing can help prevent issues with preexisting capabilities by detecting and fixing errors at an early stage of development, before they affect the integration and system testing. Unit testing can also ensure that new capabilities do not break or interfere with the existing ones, by checking the compatibility and dependencies of the units. Unit testing can be performed by developers using tools and frameworks that automate the process and generate reports. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 10: Project Quality Management; CompTIA Project+ Certification Exam Objectives, Domain 3: Project Execution, Objective 3.2: Execute quality management activities.

Confronting, also known as problem-solving or collaborating, is a method of conflict resolution that involves addressing the root cause of the conflict and finding a mutually beneficial solution that satisfies both parties. Confronting is the most effective method when the stakes are high and the relationship is important, as it can lead to increased trust, respect, and cooperation. Confronting requires open communication, active listening, empathy, and creativity from both parties. Confronting is the best method to use in this scenario, as it can help the stakeholders overcome their personal animosity, focus on their common goals, and work together to complete their tasks on time12. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Project Stakeholder Management, p. 246; What is Conflict Resolution, and How Does It Work?

Meeting with the team to emphasize the importance of following change management procedures is the best approach to prevent future unauthorized changes. CompTIA Project+ highlights the importance of adhering to formal change control processes to ensure project alignment and accountability.

Evaluating the impact to baselines (such as schedule and budget) helps determine the delay’s effect on the project. This aligns with CompTIA Project+ guidance on project control, which emphasizes analyzing impacts before taking corrective actions.

In Agile methodologies, the Product Owner is responsible for defining and prioritizing the product requirements to ensure they align with customer needs. Defining success criteria involves establishing clear, measurable goals that determine whether the project's technical features meet customer expectations.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Explain the basic characteristics of a project and various methodologies and frameworks used in IT projects, understanding roles and responsibilities, including that of the Product Owner, is essential.

Home address and date of birth must be protected as personally identifiable information (PII). PII is any information that can be used to identify, contact, or locate an individual person, either alone or in combination with other sources. PII can include information such as name, email address, phone number, social security number, passport number, driver’s license number, bank account number, credit card number, biometric data, medical records, etc. PII must be protected from unauthorized access, use, disclosure, modification, or destruction to prevent identity theft, fraud, or other malicious activities that may harm the individual’s privacy or security.

According to PRINCE2, a project management methodology, the process of initiating a project includes creating the project plan, which is a high-level plan that covers the whole project scope, schedule, budget, quality, and risks. The project plan is based on the project brief, the business case, and the product descriptions. The project plan is used to obtain the authorization from the project board to initiate and execute the project. The project plan is also refined and updated throughout the project life cycle as more information becomes available.

The other processes are not directly involved in creating the project plan. Starting up a project is a pre-project process that ensures the project is viable and worthwhile, and produces the project brief and the initiation stage plan. Managing product delivery is a process that coordinates the delivery of products from the team managers to the project manager, and ensures that the work conforms to the quality criteria and the project plan. Directing a project is a process that enables the project board to oversee and control the project, and make key decisions and approvals. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 5: Project Scope Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 5: Project Scope Management2; PRINCE2 Processes - 7 Processes Of PRINCE2 Explained3; Initiating a Project Process – This process is the procedure which defines the product quality, Project Product, project timeline, costs, the commitment of resources, risk analysis, and assembles the Project Initiation Documentation (PID)4

A maintenance window is a predefined period of time during which planned changes or updates can be performed on a system or network with minimal impact on the users or business operations1. A project manager should consider the maintenance window next when deploying a new networking device into an existing production environment, as it will help to reduce the risk of downtime, disruption, or errors. A maintenance window should be scheduled in advance, communicated to the stakeholders, and aligned with the change management plan2.

The statement of work (SOW) would clarify what the project implementation partner was contractually expected to complete after disagreeing with the project manager about completed requirements. A SOW is a document that defines the scope, deliverables, schedule, and terms and conditions of a project or contract. A SOW typically includes information such as purpose, scope of work, location of work, period of performance, deliverables schedule, applicable standards, acceptance criteria, special requirements, and payment schedule. A SOW can help to establish a common understanding and agreement between the client and the service provider on what needs to be done and how it will be done.

A warranty period is the time during which a manufacturer or seller agrees to repair or replace a product that is defective or does not meet the specified standards. A warranty period can be expressed in terms of duration (e.g., one year) or usage (e.g., 10,000 miles). A warranty period is a form of consumer protection that obliges the manufacturer or seller to bear the costs of repairing or changing any part of the product that is not functioning properly1.

This is where an existing application that is highly utilized by clients is moving to a new release, as it involves deploying and operating it in a live environment. References = CompTIA Project+ Study Guide1, Chapter 4: Project Environments

Scope creep is most likely happening when a key stakeholder recommends to a senior developer that a new feature be added that is not part of the current requirement documentation. Scope creep is a term that refers to the uncontrolled expansion or change of a project’s scope beyond its original boundaries or objectives. Scope creep can happen due to various reasons, such as changing customer demands, unclear or incomplete requirements, poor communication, lack of change control, or stakeholder interference. Scope creep can have negative impacts on a project, such as delays, cost overruns, quality issues, or reduced customer satisfaction12

Once a work-around is in place, the next best step is root cause analysis (RCA) to identify and remove the underlying cause so the defect does not recur and so the permanent fix can be designed correctly. CompTIA Project+ explicitly includes issue management activities such as handling work-arounds and performing root cause analysis, indicating that RCA is a standard follow-on control after stabilizing the situation.

Submitting a change to the CCB (A) may be necessary later if the permanent fix requires a formal change request, but RCA should come first so the team knows what change is actually needed and can accurately assess impact/risk. Escalating to a steering committee (C) is reserved for high-severity governance decisions (e.g., major budget/scope shifts), and may not be required if the team can resolve within existing authority. Updating the risk register (D) can be appropriate (e.g., record the risk of recurrence), but this is secondary to diagnosing and eliminating the defect’s cause.

So, after implementing a temporary work-around, the correct next action is to perform root cause analysis.

A contingency plan is a risk mitigation strategy that involves preparing alternative courses of action in case the original plan fails or encounters unexpected problems. A contingency plan can help reduce the impact of negative risks and ensure the project continuity and success. In this case, the project manager should develop a contingency plan to mitigate the risk of hurricanes affecting the implementation of the new radar system. For example, the contingency plan could include backup resources, alternative locations, emergency procedures, and communication channels in case of a hurricane. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Risk Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 7: Risk Management

One of the primary purposes of a stand-up meeting is to identify blocking tasks that hinder progress. This allows the team to address issues promptly and maintain momentum.

In the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, stand-up meetings are highlighted as a tool for daily communication to surface impediments and coordinate efforts.

A ticketing system is a tool that allows the project manager to assign, track, and manage tasks for the testing phase. A ticketing system can help the resources to remain at their desks and only react when needed, because they can receive notifications, updates, and feedback on their tickets through email or other channels. A ticketing system can also help the project manager to monitor the progress, quality, and issues of the testing phase, and to generate reports and metrics. A ticketing system is different from a videoconference, which is a tool that allows the project team to communicate and collaborate in real time through audio and video. A videoconference is not suitable for allowing the resources to remain at their desks and only react when needed, because it requires their active participation and attention. A ticketing system is also different from a simple messaging system, which is a tool that allows the project team to exchange text messages and files. A simple messaging system is not effective for assigning, tracking, and managing tasks for the testing phase, because it lacks the features and functions of a ticketing system, such as prioritization, categorization, status, and history. A ticketing system is also different from a corporate social media, which is a tool that allows the project team to share information and ideas through online platforms. A corporate social media is not appropriate for allowing the resources to remain at their desks and only react when needed, because it may not be secure, reliable, or professional for the testing phase. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Project Execution1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 10: Project Execution2; The 15 best collaboration tools for productive teams3

A postmortem (often synonymous with a structured “lessons learned”/retrospective at the end of a project) is specifically intended to identify what worked, what didn’t, and what to improve next time. It creates actionable improvements for future projects—process changes, tooling updates, training needs, better estimation approaches, risk triggers, and governance refinements. CompTIA Project+ closing-phase expectations include evaluating the project and collecting feedback, which is the exact purpose of a postmortem-style activity.

A contract review is valuable for procurement performance and compliance, but it’s narrower than overall delivery improvement. Archived documents are essential for auditability and reference, but archiving is primarily record retention; it doesn’t inherently analyze improvement opportunities unless paired with a review session. Project rewards support morale and recognition (also called out as part of closure activities), but they don’t generate systematic improvement insights.

A strong postmortem typically produces: a short list of top improvement themes, owners, due dates, and where to embed changes (templates, playbooks, onboarding, QA practices). That turns closure learning into measurable organizational improvement—exactly what the question is asking for.

A multitiered architecture project is a type of project that involves designing and implementing a system that consists of multiple layers or tiers, such as presentation, application, and data. A multitiered architecture project can provide a high level of redundancy, scalability, and performance, as each tier can have multiple servers or components that can handle requests and failures independently. A Tier 5 redundancy level is the highest level of redundancy that requires a fully redundant, mirrored system plus one additional backup unit for every component12.

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.

Rolling out a new POS system is an organizational change for frontline staff, so the best assistance focuses on enablement and adoption. The two strongest activities are Training sessions (D) and Documentation (A). In CompTIA Project+ execution-phase objectives, organizational change management includes “Impacts and responses” such as Training, Communication, Documentation, and establishing new knowledge bases—all aimed at ensuring users can adopt the new process and tool successfully.

Training sessions build hands-on competence (logging in, processing sales/returns, handling exceptions, end-of-day steps) and reduce errors during the cutover. Documentation provides durable job aids (quick-reference guides, FAQs, troubleshooting steps) that staff can consult during real customer interactions—critical in retail where time pressure is high and turnover may be higher.

“Gap analysis” is useful for the project team to understand differences between old and new processes, but it doesn’t directly help staff operate the new system day-to-day. “Team collaboration” and “progress monitoring” are supportive management activities. “Touch points” (check-ins) can help, but if only two are allowed, the most direct adoption enablers are training + documentation.

A business case exists to justify why the project should be done—what problem/opportunity it addresses and what benefits/value it provides relative to cost. In CompTIA Project+ objectives, the business case is part of discovery/concept and initiation, linked to business objectives and ROI, and is used to support approval decisions. The first, foundational element of that justification is clearly stating the problem being solved (or the opportunity being captured). ()

Option D best captures that intent: specify what problem is being solved by the project. Once the problem is defined, the business case typically expands to include expected benefits, costs, assumptions, constraints, and high-level risks—but those are supporting elements, not the primary objective.

Option A is more aligned to risk management artifacts (risk register, issue log). Option B (timeline and budget) is more aligned to the project plan and estimating/scheduling. Option C (specific tasks) aligns to a WBS or backlog planning. The sponsor is asking for the “why” and justification for investment before committing effort—so the business case objective is to articulate the problem and the value of solving it. ()

Scrum is an Agile framework that is well-suited for projects with rapidly changing requirements. It operates in iterative cycles called sprints, allowing for regular reassessment and adaptation of project goals. This flexibility makes Scrum ideal for environments where the company's strategy and product requirements evolve frequently, as it facilitates continuous improvement and responsiveness to change.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.2: Compare and contrast Agile vs. Waterfall concepts, Scrum is highlighted as a methodology that supports adaptability and iterative development.

Assess the impact of the request and create a change request. The project manager should assess the impact of the request and create a change request in response to the stakeholder asking to add mobile device functionality to a project that is on track to be completed under budget and ahead of schedule. A change request is a document that formally proposes and records a modification or addition to some aspect of a project, such as scope, schedule, cost, quality, or resources. A change request can help to communicate and justify the need and rationale for the change and its implications on the project objectives and deliverables. A change request also helps to initiate the change control process, which involves reviewing, approving, implementing, and monitoring the change12

The Scrum team should break the stories into workable items that can be completed within one sprint, which is a time-boxed period of 7 to 30 days, during which the team delivers a potentially releasable product increment. Breaking the stories into smaller and more manageable items can help the team to estimate them more accurately, plan them more effectively, and deliver them more reliably. Breaking the stories also aligns with the agile principle of delivering working software frequently and satisfying the customer through early and continuous delivery of valuable software.

The other options are not the best steps for the Scrum team to take next. Assigning more resources to complete similar stories in the future may not solve the problem of underestimation, and may introduce additional complexity and communication overhead. Extending the sprint duration when required with the approval of the product owner may compromise the consistency and predictability of the Scrum process, and may delay the feedback and validation from the stakeholders. Releasing the current progress into production and carrying over the rest of the code for the next sprint may result in an incomplete or unstable product increment, and may violate the definition of done, which is a shared understanding of the quality criteria that the product increment must meet. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 5: Project Scope Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 5: Project Scope Management2; The 3 Scrum Roles and Responsibilities Explained3; Implementation of Scrum - 7 Steps for an Effective Process4

KPIs (Key Performance Indicators) are measurable values tied to project goals. If KPIs are being met, the PM can confirm that the project outcomes align with objectives. Audit reports verify compliance, while lessons learned capture knowledge at project closure.

 Review the resource pool and review the project objectives are activities that the project manager should undertake after accepting a new project. Reviewing the resource pool involves identifying and evaluating the availability, skills, and competencies of the human and material resources that are needed for the project. Reviewing the project objectives involves understanding and clarifying the expected outcomes and benefits of the project and how they align with the organizational strategy and stakeholder expectations. These activities can help to plan and execute the project effectively and efficiently.

Infrastructure as a service (IaaS) is a cloud model that provides on-demand access to cloud-hosted physical and virtual servers, storage, and networking resources. IaaS customers can provision, configure, and use these resources as they would use on-premises hardware, but without the hassle of purchasing, installing, managing, and maintaining them. The cloud service provider owns, manages, and maintains the hardware and computing resources in its own data centers, and charges the customers based on their usage. IaaS is suitable for customers who need flexibility, scalability, and control over their IT infrastructure, and who want to avoid the high costs and complexity of owning and operating their own hardware. The other options are not correct because:

Software as a service (SaaS) is a cloud model that provides on-demand access to ready-to-use, cloud-hosted application software. SaaS customers do not need to install, update, or maintain the software, as the cloud service provider handles all the technical aspects. SaaS is suitable for customers who need to access common applications, such as email, office productivity, or customer relationship management, without worrying about the underlying infrastructure or platform.

Data as a service (DaaS) is a cloud model that provides on-demand access to cloud-hosted data sources, such as databases, data warehouses, or data lakes. DaaS customers can query, analyze, and visualize the data, as well as integrate it with other applications or services, using APIs or web interfaces. DaaS is suitable for customers who need to leverage data from various sources, such as social media, IoT devices, or third-party providers, without having to store, manage, or process the data themselves.

Platform as a service (PaaS) is a cloud model that provides on-demand access to a complete, ready-to-use, cloud-hosted platform for developing, running, maintaining, and managing applications. PaaS customers can use the platform’s tools, frameworks, libraries, and services to create and deploy applications, without having to worry about the underlying infrastructure or software. PaaS is suitable for customers who need to develop, test, and deploy applications quickly and efficiently, and who want to take advantage of the cloud’s scalability, reliability, and security features. References = IaaS vs. PaaS vs. SaaS; AWS Fundamentals: Understanding Compute, Storage, Database, Networking & Security; What are the different types of cloud computing?; What is Cloud Storage and How to Use It

The current stage of the project team is norming, which is the third stage of the five stages of team development. In this stage, the team members have resolved their conflicts and differences, and have established a sense of cohesion and collaboration. They are more productive, supportive, and cooperative, and they follow the agreed norms and rules of the team. They also communicate effectively and seek feedback and assistance from each other. The norming stage is preceded by the forming stage, where the team members get to know each other and the project goals, and the storming stage, where the team members experience disagreements and challenges. The norming stage is followed by the performing stage, where the team members work efficiently and autonomously towards the project outcomes, and the adjourning stage, where the team members complete the project and celebrate their achievements. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 11: Team Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 11: Team Management2; The 5 Stages of Team Development (Including Examples)3

A burndown chart tracks how much work remains over time in an iteration (or release). The most direct inputs are the remaining work and the work completed (often expressed as tasks, story points, or hours). Therefore, to obtain burndown data efficiently, the PM should analyze remaining and completed tasks. This aligns with CompTIA Project+ Agile metrics concepts, where burn charts are used to visualize progress and forecast completion based on work remaining versus time.

The other options are not primary burndown inputs. “Number of people available” affects capacity and can influence how fast work burns down, but it is not what the chart directly measures. “Cost variance” is an earned value / financial control concept (more predictive/traditional) and not what burndown charts are built from. “Number of issues registered” is useful for quality and risk/issue tracking but does not represent the work remaining in the sprint backlog unless issues are explicitly counted as backlog items—and even then, the chart is still fundamentally about remaining work, not raw issue counts.

So, for efficient burndown extraction, the PM should use the team’s work tracking (sprint backlog/task board) to calculate remaining vs. completed tasks/work, which is exactly what the burndown visualizes.

A finish-to-start dependency is a type of relationship dependency in project management, where the start of one task depends on the finish of another task12. In this case, the project manager is using a finish-to-start dependency, because testing cannot start until requirements development is finished. This implies that testing is a successor task, and requirements development is a predecessor task. A finish-to-start dependency is the most common type of dependency in project management, and it ensures that tasks are performed in a logical sequence34. References = CompTIA Project+ Certification Study Guide5, CompTIA Project+ Certification Exam Objectives6, Understanding Dependencies in Project Management [2023] • Asana1, Dependencies in Project Management | Smartsheet2, Understanding Task Dependencies in Project Management3, What are Dependencies in Project Management? - KnowledgeHut4

When an organization lacks the internal resources or expertise to develop a specific feature, subcontracting is an effective procurement method. This involves hiring an external entity to perform the work, thereby filling the skill gap.

The CompTIA Project+ PK0-005 exam objectives, under Domain 1.11: Explain important project procurement and vendor selection concepts, list subcontracting as a procurement method:

"Resource procurement methods: Build, Buy, Lease, Subscription/pay-as-you-go."

CompTIA Project+ PK0-005 Exam Objectives

Subcontracting falls under the 'Buy' category, where services are procured externally to meet project requirements.

Platform as a Service (PaaS) is designed to accelerate software delivery by providing a managed platform that typically includes the operating system layer, runtime, middleware, databases, and developer tooling—so teams can focus on building the service rather than provisioning and maintaining infrastructure and OS components. This directly supports the goal of speeding development and delivery while integrating closely with OS-level services provided by the platform (e.g., runtime services, identity, logging, scaling, patching). CompTIA Project+ includes understanding cloud models as part of IT concepts that affect project delivery choices.

By comparison, SaaS is a finished application you consume (not a development platform). IaaS provides raw compute/storage/networking; you still manage the OS and much of the stack, which is slower for development acceleration. DaaS generally refers to delivering desktops or data services depending on context, but it is not the standard model for speeding application development via an integrated platform stack.

Therefore, PaaS best matches the scenario: it reduces setup/maintenance work, standardizes environments, and helps teams deliver software faster and more reliably.

The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to accomplish project objectives. If tasks can be broken into smaller deliverables, the WBS should be updated first to reflect these changes.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.2: Given a scenario, determine the appropriate scope management activities, maintaining an accurate WBS is crucial for effective scope management.

This is compromising because the PM negotiates a middle-ground solution: the end users reduce/simplify what they originally wanted, and the project can implement a version of the change without increasing the constrained budget. Compromising is characterized by each side giving up something to reach an agreement that is acceptable and achievable within constraints (scope/cost/time). This matches Project+ objectives that include applying appropriate communication and people-management techniques (including handling disagreements and stakeholder expectations) to keep delivery feasible.

It is not collaborating, which aims for a true win-win by addressing root needs and often requires more time or resources (for example, securing more budget, changing constraints, or redesigning to meet all requirements). It is not smoothing (downplaying differences and emphasizing agreement) because the PM is actively changing the request content to fit constraints. It is not avoiding, because the PM is directly engaging and resolving the conflict rather than postponing or sidestepping it.

So the PM used compromising to maintain stakeholder buy-in while protecting the budget constraint and still achieving an implementable change outcome.

The project manager has taken a risk mitigation approach by buying the item from another vendor who can supply it immediately. Risk mitigation is a strategy that involves reducing the probability and/or impact of a negative risk to an acceptable level. By purchasing the item from another vendor, the project manager has reduced the impact of the delay on the project schedule, even though it may have increased the project cost. Risk mitigation is different from risk transfer, which involves shifting the responsibility or burden of a risk to a third party, usually through a contract or insurance. Risk acceptance is a strategy that involves acknowledging the risk and being prepared to deal with its consequences. Risk sharing is a strategy that involves allocating some or all of the ownership of a risk to another party who is willing to take on that risk, usually for some form of incentive or reward. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Risk Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 7: Risk Management2

A project is defined by its temporary nature, having both a specific start and end date. This aligns with CompTIA Project+ and general project management definitions, which emphasize a project’s unique and finite duration.

A RACI matrix clarifies roles and responsibilities for tasks, reducing confusion and disagreements among team members. Missing or incomplete information in the RACI matrix could lead to disputes, as it is a key tool for accountability in project management per CompTIA Project+.

A project manager who makes a company-wide announcement about the successful completion of a project and thanks team members is doing the following:

Celebrating the team’s hard work: This is the correct answer, as the project manager is acknowledging the efforts and contributions of the team members and showing appreciation and recognition for their performance12.

Bringing attention to the project sponsor: This is not the correct answer, as the project manager is not highlighting the role or involvement of the project sponsor, who is the person who provides the resources and authority for the project.

Sharing lessons learned: This is not the correct answer, as the project manager is not discussing the successes, challenges, or best practices of the project, which are part of the lessons learned process.

Collecting feedback: This is not the correct answer, as the project manager is not soliciting any input or opinions from the team members or other stakeholders, which are part of the feedback process.

A time and materials (T&M) contract is the best fit when you need temporary, specialized resources for a limited period (here, only during the testing phase) and the exact effort/hours are not fully predictable. With T&M, the buyer pays for the actual labor time (often at an agreed hourly/daily rate) and any approved materials/expenses. This aligns to CompTIA Project+ procurement objectives around selecting appropriate contract considerations and types, where time and material is a standard option used when work is phase-specific or scope is not fully defined to a fixed deliverable.

By contrast, fixed-price is most appropriate when the scope and deliverables are clearly defined upfront (less suitable for staff augmentation). Cost-plus reimburses allowable costs plus a fee and is typically used for broader, less-defined deliverables—often creating higher buyer cost risk than T&M for a small, contained staffing need. A warranty is not a primary contract type for acquiring temporary engineers; it’s usually a contract provision related to quality/defects after delivery.

A change log is a document that records and tracks the changes that are made to the project scope, schedule, budget, or quality. It helps the project manager to monitor and control the project performance and ensure that the changes are aligned with the project objectives and stakeholders’ expectations. A change log can also include information such as the change description, impact, status, approval, and date. A change log is the best source for the PM to use to confirm the assertion that the functionality request was rejected during the planning phase, as it would show the details and reasons for the rejection12.

When analyzing the backlog to decide what to include in the next sprint, the most important aspect to consider is the impact to the project. This involves assessing which items will provide the most value and contribute significantly towards achieving the project goals. It’s crucial to prioritize work that has the highest impact on the project’s success.

References = The answer is based on standard agile project management practices, particularly in the context of sprint planning where prioritization is key. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources

An Ishikawa diagram is a tool that the project team should use to find the cause of the defects associated with project deliverables. An Ishikawa diagram, also known as a fishbone diagram or a cause-and-effect diagram, is a graphical tool that shows the possible causes of a problem or effect using a fishbone-like structure. An Ishikawa diagram can help to identify and analyze the root causes of defects or issues and find solutions to prevent or eliminate them.

Lessons learned, removing resources, and removing access are activities that a project manager would perform during the closing phase of a project. Lessons learned is a process of collecting and documenting the knowledge and experience gained from a project for future reference and improvement. Removing resources is a process of releasing or reallocating any human or material resources that were used for the project. Removing access is a process of revoking any permissions or privileges that were granted to the project team members or stakeholders for accessing any systems or data related to the project. These activities can help to finalize and close a project successfully and ensure that all deliverables are transferred, all documentation is approved and archived, all contracts are closed, and all stakeholders are satisfied.

This meeting should identify (and re-confirm) the project scope because repeated “additional changes” are classic drivers of scope change/scope creep, and scope is the primary input for setting a realistic delivery date. In CompTIA Project+ objectives, scope is explicitly treated as a planning-phase activity—e.g., creating a detailed scope statement and defining units of work—which then enables reliable scheduling and estimating.

When stakeholders keep adding changes, the project manager must use the change control process (collect the change requests, assess impacts, determine decision makers/CCB involvement, update the project plan, implement and validate changes, and communicate deployment). Agreeing on an “expected delivery date” requires stakeholders to align on what work is actually included (scope boundaries) so impacts to the schedule can be calculated and accepted.

While budget, objectives, and communication are important, they don’t directly resolve the problem created by ongoing additions: without a clarified, agreed scope baseline (what’s in vs. out), any delivery date becomes unstable and will continue to slip as new work is introduced.

A Responsibility Assignment Matrix (RAM) is the best tool for assigning and clarifying roles and responsibilities. A RAM maps project work (deliverables, work packages, or tasks) to people/roles and defines who is responsible/ accountable, and who provides input or needs to be informed (often implemented as a RACI chart). CompTIA Project+ lists RAM/RACI-style responsibility mapping under planning and resource management practices because it prevents ambiguity, reduces duplication, and supports accountability. ()

The distractors are not designed for role assignment. ERP is an enterprise resource planning system used to manage business processes; it can store resource data but isn’t the PM artifact for defining responsibilities. JAR is not a standard project management responsibility tool in this context. CCB (Change Control Board) governs change requests; it does not assign day-to-day delivery responsibilities.

Using a RAM early (initiation/planning) helps the PM establish clear ownership, streamline handoffs, and support effective communication planning. It also reduces the risk of “I thought someone else was doing that,” which is a common execution failure mode when responsibilities are not explicitly documented. ()

Control objectives are the desired outcomes or goals of implementing security controls to mitigate risks and protect information assets. Control objectives should be the primary basis for establishing metrics that measure the effectiveness of an information security program, as they align with the business objectives, requirements, and expectations of the organization and its stakeholders. Metrics based on control objectives can help to evaluate the performance, efficiency, and maturity of the security program, and to identify gaps, issues, and areas for improvement. The other options are not correct because:

Residual risk is the remaining risk after applying security controls. Residual risk is not a basis for establishing metrics, but rather a result of measuring the effectiveness of security controls. Residual risk should be monitored and reported, but it does not define the desired outcomes or goals of the security program.

Regulatory requirements are the external standards, laws, and regulations that the organization must comply with to avoid legal or financial penalties. Regulatory requirements are not a basis for establishing metrics, but rather a constraint or a driver for the security program. Metrics based on regulatory requirements can help to demonstrate compliance, but they may not reflect the actual effectiveness or efficiency of the security program.

Risk tolerance is the level of risk that the organization is willing to accept or bear. Risk tolerance is not a basis for establishing metrics, but rather a factor or an input for the security program. Metrics based on risk tolerance can help to prioritize and allocate resources, but they may not measure the actual outcomes or goals of the security program. References = Key Performance Indicators for Security Governance, Part 1; 14 Cybersecurity Metrics + KPIs You Must Track in 2023; KPIs in Information Security: The 10 Most Important Security Metrics; Why metrics are crucial to proving cybersecurity programs’ value; Implementing and Maintaining Security Program Metrics

A Gantt chart is a visual tool used in project management to represent the timing of tasks required to complete a project. It is particularly useful for showing the start and finish dates of elements of a project, dependencies between tasks, and the current schedule status. This makes it an ideal choice for a project manager to discern overlapping tasks and allocate resources efficiently.

References = CompTIA Project+ Certification Study Guide (PK0-005)

Identifying and assessing stakeholders is an action item that will benefit from the analysis of the objectives, the high-level requirements, the success criteria, and the budget resources in the initiation phase. By reviewing these elements, the PM can determine who are the key individuals or groups that have an interest or influence in the project, what are their expectations and needs, and how to engage them effectively throughout the project life cycle12.

A formal contract is a legal document that defines the terms and conditions of the agreement between the project parties, such as the scope, schedule, budget, quality, deliverables, roles and responsibilities, payment methods, and dispute resolution mechanisms. A formal contract is essential for external projects, especially when there is an exchange of money involved, to protect the interests and rights of both parties and to ensure mutual understanding and compliance. A formal contract is different from a business requirement, which is a statement of the needs and expectations of the customer or stakeholder for the project outcome. A formal contract is also different from a client statement of work, which is a document that describes the work to be performed, the deliverables to be provided, and the acceptance criteria to be met by the project vendor or contractor. A formal contract is also different from a project charter, which is a document that authorizes the project and provides the high-level information about the project objectives, scope, stakeholders, and project manager. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Project Integration Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 4: Project Integration Management2; 11 Essential Documents To Use as a Project Manager3

Awareness of the local environment refers to the understanding of the external factors that may affect the project, such as legal, regulatory, social, cultural, economic, and environmental aspects1. In this case, the legal department applied this awareness to identify the potential risk of violating new legislation and rejected the project accordingly. This shows that the legal department was concerned about the compliance and reputation of the organization and the project in the local context. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 1: Project Management Concepts, page 17; Incorporating environmentalism into project management, Abstract and Definition of Terms sections.

During the project closure phase in the waterfall methodology, it is crucial to validate the deliverables to ensure that all project requirements have been met and the project outputs are complete and satisfactory. Additionally, reconciling the project budget is performed to ensure all financial records are accurate and reflect the actual project costs, which is essential for the formal closing of the project.

References = CompTIA Project+ Certification Study Guide (PK0-005)

Work with the project scheduler to update the project timeline. The project manager should work with the project scheduler to update the project timeline after finding an unforeseen dependency on one of the critical project activities that will most likely cause a delay. The project scheduler is a person or a tool that helps plan, schedule, monitor, and control the project activities and resources. The project scheduler can help the project manager to assess the impact of the dependency on the project schedule and identify any possible ways to mitigate or resolve it. The project scheduler can also help to update the project timeline with the revised dates and durations of the project activities and communicate them to the relevant stakeholders.

A business case provides justification for undertaking a project, programme or portfolio. It evaluates the benefit, cost and risk of alternative options and provides a rationale for the preferred solution. A business case is essential for demonstrating the value of the project and securing the approval and funding from the governance. A business case is different from a scope statement, which defines the project boundaries and deliverables; a sponsor request, which initiates the project idea and seeks support; and a project charter, which authorizes the project and assigns the project manager. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 3: Initiating Projects; What is business case? | APM

An RFP (request for proposal) is a document that solicits proposals from potential vendors for a specific project or service. An RFP typically describes the project scope, requirements, evaluation criteria, and instructions for submitting proposals. An RFP is the best document for the company to use to obtain and compare information on cabling services and costs from various vendors, as it allows the company to evaluate the vendors’ qualifications, experience, approach, and pricing12.

Pll stands for personally identifiable information, which is any data that can be used to identify a specific individual. Examples of Pll include name, address, phone number, email address, social security number, passport number, driver’s license number, etc. IP address and email address are both Pll because they can be used to trace the identity and location of a person. Medical record and test result values, name and year of birth, and x-ray and blood type are not Pll by themselves, but they can become Pll if they are combined with other data that can link them to a specific individual. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Project Security, page 331. CompTIA Project+ Certification Exam Objectives, Domain 4: Project Security, Objective 4.1: Given a scenario, apply security best practices to a project, Sub-objective: Identify and classify Pll.

According to 6 Techniques for Running Project Management Meetings, one of the best practices for effective project meetings is to assign meeting roles to stay focused. By delegating the roles and responsibilities of facilitator, timekeeper, scribe, and presenter, the project manager can ensure that the meeting agenda is followed, the action items are recorded, and the outcomes are communicated. This can also increase the engagement and accountability of the project team members, and reduce the frustration of the project manager.

A capital expense is the cost of acquiring or making improvements to fixed assets that have a useful life of more than one year1. A building purchase is an example of a capital expense, as it is a long-term investment that increases the value of the company’s assets2. Building lease, maintenance, and insurance are not capital expenses, as they are recurring or short-term costs that do not increase the value of the company’s assets3.

Testing whether a website supports multiple concurrent users signed in at the same time is a question about system behavior under load/concurrency. Among the listed methods, stress testing is the best match because it evaluates how the system performs when pushed toward or beyond normal operating conditions—often involving high volumes of transactions or many simultaneous users/sessions. CompTIA Project+ explicitly includes stress testing as one of the testing cycles/methods candidates should understand in the context of quality and performance management.

The other choices don’t align: unit testing validates individual components/functions in isolation, not full end-to-end multi-user session handling; smoke testing is a quick confidence check that basic functionality works after a build/change; and regression testing verifies that existing features still work after changes—useful, but not primarily focused on concurrent-user capacity.

So, to answer the PM’s specific question (concurrent sign-ins), the team should run a stress test (often implemented using load-generation tools) to validate session handling, authentication, and resource utilization when many users are logged in simultaneously, and to identify bottlenecks or failure points.

Smoke testing is the best fit because it is a quick, high-level validation that a new build’s most critical functions work and the build is stable enough to proceed to deeper testing. The scenario specifically says “ready for the next testing phase,” which is exactly the gate smoke testing supports: confirm the build is not “broken” and that core paths execute without major failures. CompTIA Project+ includes smoke testing as one of the testing cycles/methods candidates should recognize in project quality activities. ()

The other options are not the best match. Unit testing is low-level testing of individual components (often done by developers) and doesn’t validate that the integrated build’s critical workflows function end-to-end. Regression testing is broader and verifies existing features weren’t broken by changes; it typically takes more time and is usually run after the build passes smoke checks. Performance testing evaluates responsiveness, throughput, and resource usage—important, but not the initial readiness check for a new build entering the next test stage.

So, to quickly confirm essential functionality and determine readiness to proceed, the PM should ensure a smoke test is performed.

A cost-plus contract is a type of contract where the buyer agrees to reimburse the seller for the actual costs of the work plus a fee, which can be fixed, percentage, incentive, or award based. This type of contract has the highest risk for the buyer because the buyer has no control over the cost or quantity of the work and the seller has little incentive to control the costs or complete the work efficiently. The seller may inflate the costs or prolong the work to increase the fee. The buyer may end up paying much more than the estimated budget or the market value of the work. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 9: Project Procurement Management; CompTIA Project+ Certification Exam Objectives, Domain 3: Project Execution, Objective 3.3: Execute procurement activities.

When implementing an IT infrastructure change that takes risks into consideration, the project manager should develop a rollback plan. A rollback plan is a contingency plan that outlines the steps that need to be taken in case the change does not work as expected. It includes a plan to roll back the changes and restore the system to its previous state. References: CompTIA Project+ Study Guide Section 3.3.

The project manager should develop a rollback plan when implementing an IT infrastructure change that takes risks into consideration. A rollback plan is a contingency plan that describes how to revert back to the previous state of the system in case of a failure or disruption during the change implementation. A rollback plan can help to minimize the impact of the change on the system performance and availability and ensure business continuity and data integrity.

The rules of engagement are the guidelines and expectations that define the relationship between the contractor and the company. They may include topics such as communication, confidentiality, access, security, performance, and compliance. The project manager should reinforce the rules of engagement with the contractor to ensure that they understand and respect the boundaries and protocols of the company. This will help to avoid any potential conflicts, misunderstandings, or breaches of contract. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Project Stakeholder Management, p. 239; Contractor Rules of Engagement - Cox Enterprises, p. 1; Legal Considerations for Engaging Contractors | LegalVision

Encryption is the process of transforming data into an unreadable format that can only be accessed by authorized parties who have the decryption key. Encryption is the best approach for the project manager to keep the PII confidential, as it protects the data from unauthorized access during storage and transmission12.

ROI (return on investment) is a business-case concept used to evaluate whether the benefits/value of a project justify the investment. In CompTIA Project+ (PK0-005) objectives, ROI is explicitly referenced under “Business case or business objective – Return on investment (ROI)” as an artifact used during the discovery/concept and initiation work to support approval decisions.

Option C best matches that need because it focuses on the value the project will bring after the investment (benefits/returns). This value description is what the sponsor compares against the project’s expected costs to judge attractiveness and prioritize investments.

Option A (current vs desired outcome) can help define the problem and target state, but it isn’t ROI itself. Option B describes procurement documentation such as a statement of work/contract-style responsibilities, which is not the sponsor’s ROI input. Option D focuses on operational costs (OpEx) in normal operations; while OpEx may be part of the financial picture, ROI is specifically about investment return, not just “normal operations” cost analysis.

The results are best described as a positive correlation: as extra hours worked increase, the number of defects also increases. A positive correlation means the variables move in the same direction (higher X is associated with higher Y). This is consistent with the common quality-management interpretation that sustained overtime can correlate with higher error rates due to fatigue, reduced review quality, and rushed work—an important insight for a PM balancing schedule pressure with quality outcomes.

Within Project+ quality and performance monitoring concepts, interpreting basic analytical outputs (such as charts/diagrams that show relationships) supports better decisions about staffing approaches, sustainable pacing, and corrective actions (e.g., limiting overtime, increasing peer review, adding automated tests, or re-planning). The distractors represent other possible patterns: “no correlation” would show scattered results without a trend; “negative correlation” would show defects decreasing as hours rise (unlikely for overtime/fatigue scenarios); and “non-linear” would require evidence of a curved pattern rather than a straight trend. Based on the stated results interpretation for this scenario, the correct description is positive correlation.

In Tuckman’s team development model (forming, storming, norming, performing, adjourning), the storming phase is characterized by conflict, tension, and disagreement as members challenge ideas, roles, and ways of working. Option A describes this best: conflict that affects relationships. CompTIA Project+ includes people management concepts such as team dynamics and the need for PMs to apply leadership, conflict resolution, and motivation techniques as the team develops. ()

Option C describes forming (meeting and learning about the project). Option B describes performing (high-functioning, well-organized execution). Option D aligns with adjourning (closing/disbanding after work completion).

In storming, the PM’s role is to help the team move toward norming by clarifying goals and roles, setting working agreements, reinforcing communication norms, and addressing conflicts early and constructively. For a tax application (high accuracy/compliance needs), stabilizing team collaboration is crucial to reduce defects and rework. Therefore, the life-cycle description that matches storming is conflict affecting relationships. ()

An issue log is used to document and track problems that arise during a project, including unforeseen events like the departure of a project manager. It helps in recording the issue, assigning responsibility, and tracking the resolution process. This tool is essential for maintaining project continuity and ensuring that issues are addressed promptly.

Per the CompTIA Project+ PK0-005 exam objectives, under Domain 2.5: Given a scenario, perform issue management activities, maintaining an issue log is a key activity for tracking and managing project issues effectively.

The closing phase is when the project manager and the team finalize the project, deliver the outcomes to the customer, obtain formal acceptance, conduct lessons learned, and hand over the project to the operations team. Identifying the baseline go-live date, the operational training, and the handoff procedures are part of the closing activities that ensure a smooth transition and closure of the project. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 14: Closing Projects, p. 333-334.

When a risk trigger is detected, the risk hasn’t yet turned into an issue, but the conditions indicate it may happen. At this stage, the project team should execute the contingency plan that was pre-developed during risk planning. Assigning a risk owner happens earlier in the planning stage, and work-arounds are used only for unplanned risks. Escalation is only needed if the contingency cannot address the risk.

A finish-to-start relationship is a type of logical dependency between two tasks, in which the first task must be completed before the second task can start. In this scenario, the document containing information about how the new system will interact with other systems within the organization is a prerequisite for the configuration of the system in development. Therefore, the document writing task must finish before the configuration task can start, which is a finish-to-start relationship. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Schedule Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 6: Schedule Management2

A task board is a visual tool that displays team progress for stand-up meetings. A task board usually consists of columns that represent different stages or statuses of tasks, such as to do, in progress, done, or blocked. Each task is represented by a card or sticky note that can be moved across the columns as the task progresses. A task board can help to facilitate communication, collaboration, and transparency among team members and stakeholders. It can also help to track and manage work flow, prioritize tasks, identify bottlenecks, and resolve issues3

The project sponsor typically defines the success criteria and overall goals of the project. This alignment ensures the project meets organizational objectives, as outlined in CompTIA Project+ guidance on roles and responsibilities.

DevOps architecture integrates development and operations to enhance the software development lifecycle. It emphasizes continuous integration and delivery, automation, and collaboration, ensuring that factors like reliability, scalability, security, and cost-effectiveness are integral to project goals and objectives. By adopting DevOps practices, organizations can achieve faster deployment times, improved system stability, and efficient resource utilization.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Explain the basic characteristics of a project and various methodologies and frameworks used in IT projects, DevOps is recognized as a methodology that supports these critical factors.

An Ishikawa diagram, also known as a fishbone diagram, is a tool used to identify and analyze the root causes of a particular problem. CompTIA Project+ references this tool as essential for quality management and problem-solving.

The project manager can use the survey results as an input for performance feedback for the project team members. Performance feedback is a process of providing constructive and timely information on the performance of individuals or teams in relation to project goals and expectations. Performance feedback can help to motivate, improve, and recognize project team members345

The survey results can be used as an input for performance feedback. Performance feedback involves analyzing and evaluating the performance of the project team and project management against the project plan, including identifying areas for improvement. The survey results can help identify these areas for improvement and provide feedback to the project team on their performance. References: CompTIA Project+ Study Guide Section 4.1.1

Timeboxing means setting a fixed, predefined amount of time for an activity or discussion, then stopping (or consciously extending via a decision) when that time expires. In the context of a kickoff meeting, timeboxing helps ensure the meeting stays controlled, covers required topics, and respects attendees’ time. CompTIA Project+ explicitly includes timeboxing as part of meeting management techniques (along with agendas, roles, action items, and minutes).

Option D matches this definition precisely: “allowing a conversation to continue for a predefined period of time.” Option A (“until a decision is made”) is the opposite of timeboxing; it can lead to overrun and agenda failure. Option B suggests open-ended extension, again opposite of timeboxing’s discipline. Option C describes a flexible timeline to cover everything, which usually increases meeting risk (scope creep within the meeting) rather than ensuring outcomes.

Practically, timeboxing in a kickoff might look like: 10 minutes for goals/success criteria, 10 for roles/RACI, 10 for scope boundaries, 5 for risks/assumptions, and 5 for next steps—creating focus, accountability, and a predictable meeting flow.

Language barriers can significantly impact communication within a project team, especially when team members lack a common understanding of technical terminology and jargon. This can lead to misunderstandings, errors, and inefficiencies. Effective communication is critical for project success, and addressing language barriers is essential for ensuring that all team members are aligned and informed.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, recognizing and mitigating communication challenges, including language barriers, is vital for effective project management.

The best action is to assign training so the developer can close the skills gap and return to expected performance. Project+ emphasizes team and resource management—including managing team performance and addressing resource gaps—and also highlights organizational change management activities such as training to ensure adoption of new ways of working.

Option C is the most constructive and sustainable response: it improves capability, reduces rework/defects, and helps the project maintain velocity without creating new staffing or morale issues. Requesting an additional developer (A) may be appropriate if capacity is truly insufficient, but it increases cost and onboarding time and doesn’t solve the original skill deficiency. Giving only non-critical tasks (B) can temporarily reduce risk, but it can also delay critical work and still leaves the underlying competency problem unaddressed. Removing the developer (D) is a last resort typically reserved for persistent performance issues after coaching/training or for role mismatch that cannot be corrected within project constraints.

A practical PM approach is to pair training with short-term support (mentoring, pairing, code reviews) and then monitor performance metrics and deliverables—consistent with Project+ execution-phase management and performance monitoring expectations.

A program is a group of related projects managed in a coordinated way to achieve benefits and control that would not be available if the projects were managed separately. Option C—a consolidation of related projects with a common goal—matches the standard program definition used across project management frameworks and aligns with CompTIA Project+ terminology that distinguishes projects (temporary endeavors producing unique outputs) from programs (coordinated management of multiple related projects).

Option A is incorrect because unrelated projects do not form a program; that is closer to a portfolio (a collection of projects/programs managed to meet strategic objectives, not necessarily related). Option B describes operational tracking, not a program definition. Option D sounds like scope decomposition or workload definition, which is not what a program is.

Programs typically have overarching governance, shared resources, interdependent timelines, and integrated risk/benefit management. The focus is on achieving strategic outcomes/benefits across the combined effort, such as rolling out a suite of capabilities or transforming an end-to-end business process via multiple projects.

The project manager is using multiauthoring software to maintain the version control for the documentation of requirements. Multiauthoring software is a type of software that allows multiple users to create, edit, and collaborate on documents simultaneously. It also provides features such as tracking changes, commenting, reviewing, and merging versions. Multiauthoring software can help to improve the quality, accuracy, and consistency of documents and facilitate communication and feedback among stakeholders. Examples of multiauthoring software include Google Docs, Microsoft Word Online, and Confluence34

Time and materials contracts are flexible and beneficial when the project scope has many unknowns. They allow costs to be adjusted based on actual time and resources used, which is consistent with CompTIA Project+ recommendations for projects with uncertain requirements.

An issue log is a tool that records and tracks any issues that arise during the project. It helps the project manager to identify, prioritize, assign, monitor, and resolve the issues in a timely manner. An issue log can also include information such as the issue description, impact, status, owner, and resolution date1. An issue log is different from a defect log, which records and tracks the defects or errors in the project deliverables. A risk register is a tool that records and tracks the potential risks that may affect the project objectives. A change log is a tool that records and tracks the changes that are made to the project scope, schedule, budget, or quality2.

Archival involves preserving project records and communications so that they are accessible for future reference. This helps ensure important information is not lost over time, consistent with best practices in project documentation as per CompTIA 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.

A focus group is a technique that involves bringing together a group of stakeholders and facilitating a discussion to elicit their opinions, needs, and expectations about the project. This technique can help to gather requirements from stakeholders in an interactive and collaborative way1, p. 67

The diagram shows that the customer added requests for previously unrequested features during execution and the change control process was not followed. That combination most strongly points to scope creep as the root cause of the missed deadline: additional scope entered the workstream without proper evaluation, approval, replanning, and schedule/budget adjustment. CompTIA Project+ emphasizes controlling scope through defined requirements, scope baselines/artifacts, and a formal change control process; when that process is bypassed, uncontrolled scope growth commonly drives schedule slippage and cost overruns.

Gold plating (building “unnecessary features”) is also present, but in the diagram it appears as a downstream effect of weak requirements discipline and poor change control—teams often overbuild when requirements are incomplete or shifting. The initiating problem highlighted is that the customer did not provide all requirements early, which increases later change requests; when those changes are not properly controlled, the project experiences scope creep and deadline impact.

Team conflicts and unvalidated deliverables are not supported by the causal chain shown. The best root-cause label among the options is scope creep.

A kickoff meeting is the best fit because it is used at the start of a project (or phase) to align stakeholders and the team on core fundamentals such as scope, objectives, roles, high-level schedule/timeline, budget constraints, risks, and ways of working. If the PM is unclear about budget and timeline before work begins, a kickoff (often preceded by initiation artifacts like the charter) is where those expectations are clarified, confirmed, and communicated broadly.

A “demo” is used to show working product increments. A “stand-up” is a short Agile daily coordination meeting focused on immediate work, blockers, and next steps—not initial budget/timeline clarity. A “status call” is a recurring execution-phase update meeting; it assumes the project already has an agreed baseline.

Therefore, to establish shared understanding and confirm budget and timeline expectations prior to start, the PM should hold a kickoff meeting (or kickoff-style alignment session) to confirm baselines and ensure everyone begins execution with the same commitments and constraints.

A traceability matrix is a document that maps the requirements of a project to the deliverables, test cases, and changes that are produced to meet those requirements. It helps the project manager to track the origin, status, and impact of each requirement throughout the project life cycle. A traceability matrix can also identify who requested or approved each requirement. Therefore, the project manager can use the traceability matrix to identify who requested the specific item that caused the regression test to fail12.

Timeboxing is a time management technique that involves allocating a fixed, maximum unit of time for an activity and completing the activity within that time frame. In the context of meetings, timeboxing helps ensure that discussions stay within the allotted time, preventing overruns.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, timeboxing is listed as a meeting management technique to control the duration of meetings and keep them focused .

By implementing timeboxing, the project manager can structure the status calls to adhere strictly to the scheduled one-hour duration, improving efficiency and respecting participants' time.

 The project manager is creating a quality assurance plan when identifying multiple techniques that will help the project team ensure confidence and alignment with the project scope and goals during a brainstorming meeting. A quality assurance plan is a plan that defines and documents the standards, criteria, methods, activities, and tools for ensuring and verifying that the quality requirements and expectations of a project are met. A quality assurance plan can help to improve the quality of the project processes and deliverables and prevent or reduce defects or errors.

A RACI chart would be the most useful option for the project manager to illustrate roles for major project activities for an upcoming project kickoff. A RACI chart is a visual representation of a RACI matrix that shows who is responsible, accountable, consulted, and informed for each task or activity in a project using a table format. A RACI chart can help to communicate and document the roles and expectations of each team member and stakeholder for the project and ensure alignment and agreement.