PK0-005 CompTIA Project+ Certification (2026) Questions and Answers

Updating the issue log is the first step in documenting the problem and determining its impact on the project. This aligns with CompTIA Project+ guidelines, which emphasize the importance of tracking issues as they arise.

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

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 RACI (Responsible, Accountable, Consulted, Informed) matrix clarifies roles and responsibilities, indicating who needs to be communicated with at various levels. CompTIA Project+ highlights RACI as a critical tool for effective project communication and accountability.

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 project manager should have identified and assessed the building owner as a key stakeholder in the initiation phase, and understood their expectations and requirements for the application. This would have helped to avoid the conflict over the corporate colors and the delay in testing. Stakeholder identification and assessment is an important process in the initiation phase, as it helps to define the project scope, objectives, and success criteria, and to establish a communication plan12. References = CompTIA Project+ PK0-005 Certification Study Guide,

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.

The project manager should produce a project charter first to start communication about the boundaries of the project. A project charter is a document that formally authorizes a project and defines its high-level scope, objectives, assumptions, constraints, stakeholders, roles and responsibilities, and key deliverables. A project charter can help to communicate the project vision and expectations to all stakeholders and provide a basis for future project decisions23

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.

If team members are confused about which meetings to attend, this indicates a flaw in the communication plan. Revising the plan ensures clear expectations on who participates in which communication events. Scope or schedule changes don’t automatically require altering the communication plan.

A gantt chart is a visual representation of a project timeline that shows the tasks, durations, dependencies, and resources of a project in a horizontal bar chart format. A gantt chart can help a project manager to calculate the progress of the whole project scope by comparing the planned and actual start and finish dates of each task, as well as the percentage of completion and the critical path. A gantt chart is also a useful tool for communicating the project status and performance to the sponsor and other stakeholders. Therefore, the first document that the project manager should update to calculate the progress of the whole project scope is the gantt chart. 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; What Is a Gantt Chart? 7 Examples for Project Management3

Real property (construction/real estate/building projects) is generally best suited to waterfall (predictive) management because the work is highly sequential, governed by physical dependencies, and often requires detailed upfront planning and permitting. For example, you typically must complete design, approvals, site preparation, foundation, framing, and inspections in a defined order. Changes later in construction can be expensive and disruptive, so strong baselining, stage gates, and formal change control align well with waterfall practices.

By contrast, research and data analytics often involve discovery and evolving understanding, making iterative/adaptive approaches more effective. Software development can be done in waterfall, but modern practice frequently benefits from Agile/iterative methods due to changing requirements, user feedback loops, and the ease of incremental delivery.

Project+ emphasizes selecting methodologies based on project characteristics (clarity of requirements, volatility, regulatory constraints, and deliverable nature). Real property projects commonly have well-defined deliverables, fixed constraints, and heavy reliance on documentation and approvals—conditions where waterfall’s structured phases and control points provide predictability and governance.

So, among the options, real property is the best candidate for waterfall management.

Corporate values compliance is a consideration when determining a project’s ESG factors, because it reflects how a project aligns with the ethical standards and social responsibility of the organization. Corporate values compliance can help to enhance the reputation, trust, and loyalty of the organization among its stakeholders, as well as to avoid legal or regulatory issues that may arise from violating the values. Corporate values compliance can also influence the project scope, objectives, deliverables, and stakeholders, as well as the project management methodology, processes, and practices.

The other options are not directly related to ESG factors. Project management methodology is the approach or framework that guides how a project is planned, executed, monitored, and controlled. IT infrastructure security is the protection of the hardware, software, network, and data components of a project from unauthorized access, use, modification, or destruction. Proper accounting practices are the rules and standards that govern how financial transactions and statements are recorded, reported, and audited for a project. 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; What Is Environmental, Social, and Governance (ESG) Investing

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.

When a project manager observes that the project's outcomes do not align with expectations, despite the vendor fulfilling all contractual obligations as per the Statement of Work (SOW), the appropriate next step is to perform a gap analysis. This analysis helps identify discrepancies between the current state (what has been delivered) and the desired state (stakeholder expectations).

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.5: Given a scenario, perform risk management activities, performing a gap analysis is a critical activity to assess and address such discrepancies. The gap analysis will provide insights into areas where the project may not be meeting stakeholder expectations, allowing the project manager to develop strategies to bridge these gaps.

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 dashboard is the most appropriate artifact to share when a stakeholder asks for project performance data. Dashboards are designed to present key performance indicators (KPIs) and trends in a concise, visual form—such as schedule progress, scope completion, burn/burndown, budget status, risks/issues summaries, and other metrics relevant to project health. This aligns with Project+ expectations around performance monitoring and communicating status in an efficient way tailored to stakeholder needs.

An issue log is too granular and focuses only on current problems; it is part of performance, but it’s not the overall performance view stakeholders typically want. A WBS is a scope decomposition artifact used for planning and organizing work, not performance reporting. A milestone chart shows key dates and whether major points are achieved, but it does not provide comprehensive performance data (cost, trend, throughput, overall health).

Therefore, to provide performance data effectively—especially for stakeholders who want quick, up-to-date visibility—the PM should send (or grant access to) the project dashboard, ensuring it reflects the latest reporting period and includes the metrics the stakeholder cares about.

Multifactor authentication (MFA) is a security method that requires users to provide two or more pieces of evidence to verify their identity before accessing a system. MFA can use different types of factors, such as something the user knows (e.g., password, PIN, security question), something the user has (e.g., token, smart card, mobile device), or something the user is (e.g., fingerprint, face, voice). MFA provides a layered approach to logging in to systems that contain an organization’s most valuable intellectual property, as it makes it harder for unauthorized users to gain access by compromising one factor alone. MFA can also prevent phishing, brute force, and credential theft attacks12. References = CompTIA Project+ PK0-005 Certification Study Guide,

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.

Outsourcing the development of a system component due to a lack of internal resources is a risk response strategy known as ‘transfer.’ This approach shifts the risk to a third party who will now be responsible for managing that portion of the project. It is commonly used when an organization does not have the expertise or capacity to handle specific risks internally.

References = The answer is based on standard project management practices and the typical use of risk response strategies in the field. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources.

Resolution time is a standard component of a Service Level Agreement (SLA), defining the maximum time for addressing issues. SLAs are essential for managing client expectations and service performance, in line with CompTIA Project+ concepts of contract management.

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.

The next step in the process after defining tasks, durations, resources, and costs is to seek baseline approval. A baseline is an approved version of a project plan that serves as a reference point for measuring progress and performance throughout the project lifecycle. A baseline typically includes scope, schedule, cost, quality, and risk parameters. Seeking baseline approval involves presenting the project plan to key stakeholders and obtaining their formal agreement on the project objectives and deliverables. Baseline approval can help to establish clear expectations, avoid scope creep, and facilitate change control during project execution.

The NEXT step after defining tasks, durations, resources, and costs during the planning phase is to seek baseline approval. Baseline approval involves finalizing the project plan and gaining approval from stakeholders, establishing the plan as the baseline for the project's performance. References: CompTIA Project+ Study Guide Section 3.4.1

The scenario indicates a breakdown in communication between the project team and the project sponsor. The sponsor was unaware of the issues and could not provide guidance on the next steps, highlighting a deficiency in the project's communication processes.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, it is essential to:

Develop communication platforms/modalities

Manage project communication

Control project communication

One of the key aspects of controlling project communication is:

Revising the communication plan

The communication plan outlines how information is disseminated among stakeholders, including the frequency, methods, and responsible parties. If a sponsor is uninformed about project issues, it suggests that the communication plan is either inadequate or not being followed correctly.

The CompTIA Project+ PK0-005 Certification Study Guide further elaborates on this by stating that:

The communication plan should be reviewed and updated regularly to ensure effective information flow among stakeholders.

In this case, revising the communication plan would address the communication gaps, ensuring that the sponsor and other stakeholders receive timely and accurate information about project issues and developments.

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

Applying the contingency plan is the immediate response to mitigate a security risk. CompTIA Project+ emphasizes the importance of having pre-established contingency plans to handle potential risks promptly and effectively.

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

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

Archiving project documentation is an important process to ensure that the project information is stored, retrieved, and updated in a consistent and efficient manner1. It also helps to meet legal requirements, enable long-term analysis, and support new projects and team members1. If the documentation was not archived as per the PMO standards, it would be difficult for the current project manager to find the relevant documents and learn from the previous project. This would cause the current project manager to keep asking questions to the previous project manager, who may not have all the answers or may not be available. Therefore, the most likely cause of this situation is that the documentation was not archived as per the PMO standards. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 14: Closing the Project, page 403; How to Archive a Completed Project: A Guide for PMOs, Introduction and Benefits 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)

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.

Scrum is an agile methodology well-suited for projects that require frequent milestone deliveries and functionality demonstrations. It emphasizes iterative development, with regular presentations to stakeholders, which aligns with CompTIA Project+ principles for agile project management.

A gate review is a type of meeting that evaluates the completion and quality of a project stage and decides whether the project can proceed to the next stage. A gate review is a formal governance step that involves reviewing the goals, progress, risks, deliverables, and benefits of the project, and discussing if the project is still aligned with the business strategy and stakeholder expectations. A gate review can have different outcomes, such as go, kill, hold, recycle, or conditional go, depending on the assessment of the project status and viability123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 9: Project Change Management, p. 323; Everything Project Managers Need To Know About Gate Reviews | monday.com Blog; Gate reviews: What to do and why you need them - Rebel’s Guide to Project Management; Gates and How to Operate Them - GenSight

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.

This answer is based on the best practice of choosing a project management methodology that suits the project characteristics and environment12. Scrum is an agile framework that is designed to handle complex and uncertain projects with frequent changes and tight deadlines34. Scrum involves a small, cross-functional team that works in short iterations called sprints, delivering incremental and potentially shippable products at the end of each sprint5. Scrum also allows for continuous feedback and improvement through daily stand-up meetings, sprint reviews, and retrospectives6. Scrum is suitable for this project because it can accommodate the high uncertainty, the risk of requirement changes, and the tight deadlines, while also enabling the two developers to collaborate effectively and deliver value to the customer. References = CompTIA Project+ Certification Study Guide7, CompTIA Project+ Certification Exam Objectives8, Project Management Methodologies Comparison (11 PM Methods)6, Project Management Methodologies: 12 Best Frameworks [2023]7, What is Scrum?5, Scrum Methodology: The Ultimate Guide6

A backlog is commonly used in agile project management to list deliverables and tasks that have not yet been completed. It allows the project manager to prioritize and organize the workload, especially for complex projects. This aligns with agile principles as outlined in CompTIA Project+.

The project manager should have considered environmental, social, and governance (ESG) factors during initial planning to prevent the situation of receiving a penalty for disposing of some computers improperly. ESG factors are criteria that measure the sustainability and ethical impact of an organization’s activities. They include aspects such as environmental protection, social responsibility, human rights, diversity, and corporate governance. Considering ESG factors can help to reduce risks, improve reputation, and enhance performance of an organization12

The BEST way to coordinate management of multiple related projects is to establish a program. A program is a group of related projects that are managed together to achieve specific strategic business objectives. References: CompTIA Project+ Study Guide Section 2.2.1

The organization should establish a program to coordinate management of multiple related projects. A program is a group of related projects, subprograms, and program activities that are managed in a coordinated way to obtain benefits and control not available from managing them individually. A program can help to align multiple projects with strategic goals, optimize resources and risks, and deliver value to stakeholders.

The only option that can be reliably inferred in a typical project chart/diagram context (e.g., a network diagram or dependency view) is a dependency relationship—specifically that Task B must finish before Task C can start (a Finish-to-Start relationship). In CompTIA Project+ objectives, dependency management is a core scheduling concept: identifying predecessors/successors and understanding how sequencing drives the schedule. Inference about task ordering is exactly what dependency visuals are designed to communicate.

The other options require information that is not inherently inferable without additional data. “Completed on time” (A) would require schedule baseline vs. forecast/critical path analysis. “Task D must be reworked” (B) would require quality/validation results or defect/issue information. “Over budget and behind schedule” (D) would require performance metrics such as EVM or cost/schedule variance and cannot be concluded solely from a dependency relationship.

So, the best inference is the sequencing rule: B must be completed before C begins, which is a fundamental scheduling/dependency concept emphasized in Project+ planning and schedule control practices.

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 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

Project sign-off is the activity most likely to have avoided the discrepancy because formal sign-off (especially at closure) confirms that key project outcomes—including final reporting—are reviewed, agreed, and approved by the appropriate authority (sponsor/customer/PMO/finance stakeholders). In CompTIA Project+ closing activities, sign-off is part of ensuring the project is properly closed, deliverables are accepted, and records are accurate and complete for governance and auditability. A formal sign-off step typically includes reconciling final cost/schedule performance, confirming financials match the system of record, and documenting approvals.

“Closing contracts” relates to procurement and vendor obligations and might influence final costs, but it doesn’t directly guarantee reconciliation between financial reporting sources. “Validation of deliverables” focuses on product acceptance/quality, not financial reporting alignment. “Removing access” is an offboarding/security step and doesn’t address financial discrepancies.

So, the best preventive control among the options is project sign-off, because it provides a structured checkpoint to reconcile and confirm closure information (including final financials) with stakeholders and records—reducing the chance of inconsistent reporting that later triggers audit findings.

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?

The project manager and contractor should review the vendor rules of engagement, which are the guidelines and expectations for the communication and interaction between the project team and the contractor. The vendor rules of engagement can help to prevent or resolve communication conflicts by clarifying the roles and responsibilities, the frequency and mode of communication, the escalation process, the feedback mechanism, and the performance evaluation criteria of the contractor. The vendor rules of engagement are usually part of the contract or the procurement management plan.

The vendor rules of engagement are different from the scope of work, which is the document that describes the work to be performed, the deliverables to be provided, and the acceptance criteria to be met by the contractor. The vendor rules of engagement are also different from the request for proposal, which is the document that solicits proposals from potential contractors by specifying the project requirements, evaluation criteria, and contract terms. The vendor rules of engagement are also different from the project schedule, which is the tool that displays the planned start and finish dates, durations, dependencies, and resources of the project activities and tasks. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 12: Procurement Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 12: Procurement Management2; Vendor Rules of Engagement3

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.

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.

Obtaining project sign-off is crucial in the closure phase, as it signifies formal acceptance of the project deliverables by the stakeholders. According to CompTIA Project+, project sign-off is a key milestone in officially closing the project.

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.

The project manager should validate against the scope statement and ask for sign-off after a system was implemented and testing was successfully completed. The scope statement is a document that defines and documents the project scope, objectives, deliverables, requirements, assumptions, and constraints. The scope statement can help to establish a common understanding and agreement between the project manager and the stakeholders on what the project aims to achieve and deliver. Validating against the scope statement means checking whether the project deliverables meet the agreed-upon scope criteria and quality standards. Asking for sign-off means requesting formal acceptance and approval of the project deliverables from the stakeholders.

The statement of work (SOW) would be the next document that a project manager should update once the need to procure goods and/or services is identified. 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 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. ()

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 correct step is to establish communication channels that ensure proper flow of information from idea origination through review and approval. Kickoff meetings occur later, while RACI matrices and stakeholder identification are planning tools — not communication flow structures.

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.

Project success criteria are the standards by which the success of a project is judged. They include specific goals, deliverables, and performance measures such as cost, time, and quality targets. Defining these criteria during the initiation phase provides a clear understanding of what constitutes project success and guides decision-making throughout the project lifecycle.

Per 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, establishing clear success criteria is fundamental for project planning and evaluation.

A risk log or risk register is used to document potential risks to the project, including the loss of team members due to high stress. CompTIA Project+ recommends this log as a tool for identifying and managing risks throughout the project lifecycle.

The process is out of control and should be revised. The project manager can use the rule of seven to determine the status of the process based on the control chart. The rule of seven states that if seven or more consecutive measurements fall on one side of the mean that there’s an assignable cause that needs investigation. In this case, the last seven data points are all below the mean, which indicates that the process is out of control and in need of adjustment12

A rollback plan (sometimes called a “backout plan”) defines the steps to revert a system to the last known good/operational state if an implemented change fails or creates unacceptable impacts. That is exactly what option B states: returning to the operational state before the change was applied. This aligns with IT change control practices emphasized in Project+ governance and change control contexts, where changes must include consideration for restoring service quickly if outcomes are not as expected.

Option A (“apply an alternative plan”) is closer to a general contingency/fallback plan, which may involve a different solution path rather than undoing the change. Options C and D are not standard control responses: restarting the entire project is extreme and unrelated to change backout, and repeating tasks “until they work” ignores risk control and service stability.

In project environments—especially IT—rollback planning is part of responsible change implementation because it reduces downtime, protects users, and supports controlled deployment. If validation/testing after the change shows failure, the rollback plan provides a predefined, approved path to quickly restore the prior baseline while the team reassesses or submits a revised change request.

A project schedule is an artifact that shows the sequence, duration, and dependencies of the project activities, as well as the resources assigned to each activity. A project schedule helps the project team understand what needs to be done, who needs to complete the tasks, and when the tasks need to be completed. A project schedule can also help monitor and control the project progress and performance1.

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

Milestones are activities with zero duration that are added to a project schedule by a project manager. Milestones are significant events or achievements in a project that mark the completion of a phase, deliverable, or task. Milestones can help to track and measure the progress and performance of a project and communicate it to stakeholders.

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.

For teams distributed across different regions, effective collaboration tools are essential. A wiki knowledge base allows team members to access and contribute to shared information asynchronously, while real-time, multi-authoring editing software enables simultaneous collaboration on documents.

The CompTIA Project+ PK0-005 exam objectives, under Domain 3.1: Given a scenario, use the appropriate tools throughout the project life cycle, highlight the importance of collaboration tools:

"Collaboration tools: Real-time, multi-authoring editing software; Wiki knowledge base."

CompTIA Project+ PK0-005 Exam Objectives

These tools facilitate seamless collaboration, knowledge sharing, and document management among geographically dispersed team members.

Informal communication is a type of communication that is casual, spontaneous, and unstructured. It does not follow any predefined rules, protocols, or formats. Examples of informal communication include email, phone calls, conversations in the hallway, and impromptu meetings12. The sponsor is using informal communication to communicate with the team, as these methods are convenient, flexible, and personal. However, informal communication may also have some drawbacks, such as lack of documentation, inconsistency, and potential for misunderstanding3. Therefore, the sponsor should also use formal communication when necessary, such as for official reports, contracts, and presentations4.

According to Four agile ceremonies, demystified, one of the Scrum ceremonies is the daily stand-up, which is a short meeting to discuss progress and identify blockers. Blockers are any issues or impediments that prevent the team from completing their tasks or achieving their goals. Reviewing project blockers during the daily stand-up helps the team to resolve them quickly, collaborate effectively, and stay on track1. The other options are not likely to take place during a Scrum ceremony, as they are either part of the initial project planning or outside the scope of Scrum.

This answer is based on the understanding that outsourcing is a form of procurement, which is one of the knowledge areas in project management. Procurement involves acquiring goods and services from external sources to support the project objectives. According to the CompTIA Project+ Study Guide1, procurement activities occur mainly in the planning phase of the project, where the project manager identifies the project needs, defines the scope of work, evaluates the potential vendors, and prepares the procurement documents. The other options are not correct because:

Initiating is the phase where the project manager defines the project purpose, objectives, and deliverables, and obtains the project charter and stakeholder approval. Initiating does not involve procurement activities, although it may involve some preliminary research on the feasibility and availability of external resources.

Controlling is the phase where the project manager monitors and measures the project performance, compares it with the baseline, and implements corrective actions if needed. Controlling does involve some procurement activities, such as reviewing the vendor deliverables, managing the changes, and resolving the issues, but these are not the main tasks of procurement.

Executing is the phase where the project manager leads and directs the project team and other resources to complete the project work according to the plan. Executing does involve some procurement activities, such as selecting the vendor, signing the contract, and managing the relationship, but these are not the main tasks of procurement. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 8: Planning Projects, Part 4 (Procurement and Communication), pages 243-260; CompTIA Project+ Certification Exam Objectives, Domain 2: Project Planning, Objective 2.5: Given a scenario, plan procurement for a project.

When stakeholders express concerns about the volume of communication, it’s important to review and adjust the communication plan to ensure it meets the project’s needs and stakeholders’ preferences. A RACI matrix is useful for defining roles and responsibilities but does not address communication frequency or methods directly. Escalating the issue may not be necessary if it can be resolved by revising the plan. Informing the CCB (Change Control Board) to stop communication is not advisable as the CCB’s role is to oversee changes, not to manage day-to-day communications. References = The CompTIA Project+ Certification Study Guide provides detailed information on managing the project life cycle, establishing communication plans, and handling stakeholder concerns1.

The product owner is the person who is responsible for managing the product backlog, which includes adding, removing, or changing items based on stakeholder feedback and business value. The product owner is also the one who can collaborate with the development team and the scrum master to decide if a change can be accommodated in the current sprint or deferred to a future sprint. Therefore, the stakeholder should have asked the product owner to request the change instead of the team member, who is not authorized to make changes to the sprint backlog12.

Time zones are the most important factor to consider when setting up a troubleshooting session for team members who are located in different regions of the world. The project manager should ensure that the session is scheduled at a convenient and reasonable time for all participants, and avoid scheduling conflicts or communication delays. Time zones can also affect the availability and responsiveness of stakeholders, vendors, and customers1.

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

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. ()

The project manager should contact the project management office (PMO) for assistance after learning that a similarly time-consuming project was executed previously in the organization. A PMO is a department or group within an organization that provides centralized guidance, governance, standards, best practices, resources, and oversight for project management activities. A PMO can help the project manager by providing access to historical data, lessons learned, templates, tools, methodologies, and expertise from previous projects that can be useful for planning and executing the current project.

This is a negative risk (threat): the manufacturer may be unable to deliver due to financial trouble, which could delay the project or increase cost. The scenario already indicates the response: “the servers will be sourced from another vendor.” That is best described as risk avoidance—changing the plan to eliminate exposure to the threatened vendor failure by not depending on that manufacturer. CompTIA Project+ includes performing risk management activities such as selecting risk management strategies and executing contingency/fallback plans.

“Mitigate” would mean reducing probability/impact while still accepting some exposure (e.g., adding schedule buffer, placing partial orders early, or increasing inspections), but here the team is switching vendors, which removes the root threat from the current plan. “Share” and “exploit” are typically associated with positive risks/opportunities, not threats, and don’t fit a supplier distress scenario.

So the correct strategy is Avoid: replace the risky supplier dependency with an alternate sourcing approach to prevent the risk from materializing into a project issue (late delivery, non-delivery, or contract disruption).

A decision tree helps in evaluating various choices and their potential outcomes, making it suitable for comparing vendors based on costs and risks. This aligns with CompTIA Project+ methodologies for decision-making tools and analysis.

In a standard change control flow, communicating the change deployment is done last, after the change has been evaluated/approved, implemented, and validated. CompTIA Project+ explicitly frames change control as a process that includes: collecting/documenting changes, assessing impacts, determining decision makers (often the CCB), updating plans/baselines as needed, implementing the change, validating/testing implementation, and communicating deployment. The communication step is last because stakeholders need confirmation of what was deployed, when it was deployed, and any impacts—based on verified results rather than assumptions.

Option A (escalate to the CCB) happens early when approval is needed. Option B (update the project plan) occurs after approval/impact assessment so the plan reflects the authorized change. Option C (test the implemented change request) is part of validation and must occur before announcing deployment completion; otherwise, you risk communicating a change that doesn’t work as intended.

So, after the change is approved, the plan updated, the change implemented and tested, the final step is to communicate the change deployment to affected stakeholders and teams—closing the loop and maintaining governance and transparency.

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

After that alignment is established, the PM can translate objectives into industry-specific constraints and success measures—where regulations/standards (A) become critical, especially in regulated industries. “Relevance to the global environment” (B) and “impact to the corporate brand” (D) are important considerations, but they are typically evaluated after the PM anchors the objectives to the organization’s strategic identity and purpose.

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

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

Capital Expenditures (CapEx) refer to funds used by an organization to acquire or upgrade physical assets such as property, industrial buildings, or equipment. Purchasing vehicles falls under CapEx as it involves acquiring a long-term asset.

In the context of the CompTIA Project+ PK0-005 exam, understanding the distinction between CapEx and operational expenditures (OpEx) is important, as highlighted in Domain 4.2: Compare and contrast common project team organizational structures.

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.

Because the issues are already occurring and are expected to negatively impact schedule and cost, the most direct mitigation action is to use contingency reserves/buffers that were planned for uncertainty. CompTIA Project+ explicitly includes both determining contingency reserves/buffers during planning and contingency reserve/buffer utilization during execution/controls as part of schedule and project control activities.

Updating the issue log is important for tracking, ownership, escalation, and outcomes, but it is primarily a documentation/control step, not the immediate mitigation that protects the timeline and budget. Communicating with stakeholders is also essential (especially if reserves will affect commitments), but communication alone doesn’t reduce the impact—reserves do. Reviewing the risk register can help connect issues back to known risks and validate whether contingency plans exist, but the question asks what is best to do to mitigate the schedule/cost impact now; that is exactly what contingency reserves are designed for.

In practice, the PM would typically: document the issues, apply the reserve/buffer, update schedule/budget baselines as needed, and then communicate the revised forecast—however, the mitigation action among the options is using contingency reserves.

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

Forcing is a conflict resolution technique where the project manager makes a decision unilaterally, without seeking consensus. According to CompTIA Project+, forcing may be used when time is critical, and decisions need to be made promptly.

The PM is building a Work Breakdown Structure (WBS). A WBS is the structured decomposition of the project’s deliverables and scope into progressively smaller pieces until you reach the lowest practical level of detail (often called work packages), which can then be scheduled, estimated, assigned, and tracked. In the CompTIA Project+ objectives, the WBS is explicitly listed as a planning artifact used to break down the work during initiation/planning activities.

The other options don’t fit the “smallest activity components” description. A milestone chart highlights key checkpoints/dates, not the granular decomposition of work. A task board visualizes workflow status (e.g., to-do/in-progress/done) but doesn’t inherently define the decomposition structure. A detailed project plan is broader and would include schedule, resources, budget, and governance—often informed by the WBS rather than being the decomposition itself.

By creating the smallest components list, the PM is effectively decomposing scope into manageable units, which is precisely the purpose of a WBS in Project+ planning and control.

A wiki is the best tool to record retrospective results for a distributed/virtual team because it provides a shared, persistent, easily editable knowledge base where outcomes can be documented and revisited. Retrospectives produce actionable items such as what went well, what didn’t, root causes/themes (e.g., production issues), and improvement experiments with owners and due dates. A wiki supports this by enabling structured pages, version history, links to incident records, and ongoing updates—helping the team track whether morale and operational stability improve over time. CompTIA Project+ includes meeting management and documentation practices (agendas, notes, action items) and recognizes collaboration tools used to capture and share project knowledge.

A presentation is typically one-way and not ideal for ongoing collaborative updates. Chat is transient and hard to curate as a long-term record; key decisions and actions get buried. Polling is useful for quick sentiment checks (which can help measure morale), but it doesn’t serve as the primary system to document discussion, decisions, and actions from the retrospective.

Therefore, to record retrospective results clearly and durably for a virtual team, the PM should use a wiki.

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 core Kanban concept is managing flow by limiting work in progress (WIP). Kanban uses visual workflow boards and explicit WIP limits to prevent overloading the system, expose bottlenecks, and improve throughput and predictability. By limiting how many items can be “in progress” at once, teams finish work faster, reduce context switching, and stabilize cycle time—key goals of flow-based delivery. CompTIA Project+ includes Agile and adaptive concepts, and Kanban is commonly distinguished by its focus on continuous flow and WIP limits rather than timeboxed iterations.

Option A describes iteration-based alignment (more associated with Scrum’s sprint cadence). Option B (color-coding tasks) can be a visual technique but is not a defining Kanban principle. Option C (allocating resources to high-priority tasks) is a general management practice; Kanban does include prioritization, but its hallmark control is WIP limitation to optimize flow.

Therefore, the correct Kanban concept is limiting WIP to manage flow—a fundamental mechanism used to improve delivery efficiency and quality while keeping the system from becoming congested.

The system is lacking proper access controls if a third-party vendor was able to see secured project information in a recently implemented system that resulted in a fine for the organization. Access controls are security mechanisms that regulate who or what can view, use, or modify data or resources in a system or network. Access controls typically involve authentication and authorization processes that verify the identity and permissions of users or devices before granting them access. Access controls can help to protect data confidentiality, integrity, and availability and prevent unauthorized access, misuse, or theft12

Conducting lessons learned sessions is a critical part of the project closing phase. The primary purpose is to document what went right and wrong during the project, as well as to identify possible improvements for future projects. This process helps in capturing valuable insights and experiences, which can be used to enhance the effectiveness and efficiency of future projects.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.5: Explain the importance of activities performed during the closing phase, one of the key activities is:

Collecting feedback from stakeholders

This includes conducting lessons learned sessions to gather insights on project performance, challenges faced, and areas of improvement.

Furthermore, the CompTIA Project+ PK0-005 Certification Study Guide emphasizes the importance of lessons learned sessions in the project closure process. It states that these sessions are conducted to:

Review what went well and what did not

Document lessons learned

Provide recommendations for future projects

By systematically analyzing the project's successes and shortcomings, organizations can build a repository of knowledge that serves as a reference for future projects, thereby fostering continuous improvement.

This violates the need-to-know principle because employees in the sales department should only have access to information required to perform their job responsibilities. Granting broad access to project files—especially files containing employee personal information—is an access control failure: permissions are too open and not aligned to role-based necessity. CompTIA Project+ emphasizes compliance and information security considerations that affect projects, including the expectation that sensitive information is protected through appropriate controls and access restrictions.

“Intellectual property” (B) concerns ownership and protection of creations (designs, trademarks, code, patents), not role-based access to personal data. “Multifactor authentication” (C) is an authentication mechanism that strengthens login security, but the scenario is about authorization/permissions (who is allowed to access what) rather than proving identity. “Facility access” (D) relates to physical security of locations, not digital file permissions.

In practice, the PM would coordinate with security/IT to correct access groups, implement least-privilege and role-based access control, and ensure sensitive data (like employee PII) is stored and shared with stricter controls—consistent with Project+ governance expectations around handling sensitive information appropriately.

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.

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

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 project manager can use the burn up chart to analyze the current status of the project based on its scope (value delivered), budget (cost), and schedule (time). A burn up chart is a graphical tool that shows how much work has been completed (burned up) versus how much work remains (scope) over time. It also shows how much budget has been spent (burned up) versus how much budget remains (budget) over time. A burn up chart can help to monitor and control the project progress and performance and identify any variances or deviations from the plan. The chart given shows that both scope and budget lines are above their respective target lines at any given time point. This means that less work has been completed than planned (scope variance) and more money has been spent than planned (budget variance) at any given time point. Therefore, the project is behind schedule and over budget.

The project manager should use a change control log to document the effects of the hurricane delay on the project. A change control log is a tool that records and tracks any changes that occur during the project lifecycle. It usually includes information such as change ID, description, impact, status, approval, and resolution. A change control log can help to monitor and manage the changes that affect the project scope, schedule, cost, quality, or resources and ensure that they are aligned with the project objectives and stakeholder expectations.

A wiki knowledge base is a tool that allows the project team to store, organize, and share information that is captured throughout the life cycle of a project. A wiki knowledge base is stored in a centralized location that is easily accessible to all stakeholders via a web browser. A wiki knowledge base also provides search functionality that enables the users to find the information they need quickly and easily. A wiki knowledge base can help the project team to document the project requirements, scope, schedule, budget, quality, risks, issues, lessons learned, and best practices.

A wiki knowledge base is different from a secure folder, which is a tool that protects the files and folders from unauthorized access or modification. A secure folder may not be easily accessible to all stakeholders, and may not provide search functionality or collaboration features. A wiki knowledge base is also different from a real-time, multiauthoring editing software, which is a tool that allows the project team to create and edit documents simultaneously and synchronously. A real-time, multiauthoring editing software may not be suitable for storing large amounts of information, and may not provide the same level of organization and structure as a wiki knowledge base. A wiki knowledge base is also different from a digital whiteboard, which is a tool that allows the project team to brainstorm, visualize, and communicate ideas. A digital whiteboard is not designed for storing information, and may not provide the same level of search functionality or security as a wiki knowledge base. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 3: Project Communications Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 3: Project Communications Management2; The 15 best collaboration tools for productive teams3

When a project relies on legacy applications, a primary and often heightened risk is a major cybersecurity event. Legacy systems frequently have older architectures, limited vendor support, weaker security controls, outdated dependencies, and delayed patching capabilities—factors that increase vulnerability exposure. From a Project+ perspective, risk management requires identifying threats with the highest potential impact; a cybersecurity incident can create severe consequences across confidentiality, integrity, and availability, leading to service outages, regulatory exposure (especially if PII is involved), reputational damage, and unplanned cost/schedule impacts.

“Infrastructure end of life” (A) is also a legitimate legacy-related risk, but it is typically a more predictable lifecycle risk that can be planned around (replacement schedules, support contracts). A “company reorganization” (B) is a general organizational risk not specific to legacy applications. “Digital transformation” (C) is more of a strategic initiative context than a discrete risk event.

Because the question asks for the main concern when using legacy apps, the most critical, high-impact threat that legacy systems exacerbate is a major cybersecurity event—the kind of risk that can derail timelines and budgets and force emergency scope changes and remediation work.

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

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

A Sprint Review involves reviewing the completed backlog items and presenting the work to stakeholders. This aligns with CompTIA Project+ agile practices, where a Sprint Review focuses on completed tasks and feedback.

A Fixed-Price Contract is most suitable when the project scope, requirements, and deliverables are clearly and thoroughly defined. This contract type sets a predetermined price for the work, regardless of the actual costs incurred, transferring the risk of cost overruns to the vendor. It is advantageous when the project details are well-understood and unlikely to change.

Per the CompTIA Project+ PK0-005 exam objectives, under Domain 1.11: Explain important project procurement and vendor selection concepts, understanding when to use fixed-price contracts is essential, particularly when the project scope is well-defined.

Enterprise resource planning (ERP) software is a type of software that integrates various business functions and processes, such as accounting, finance, inventory, sales, purchasing, human resources, and more. ERP software helps businesses store, organize, and manage information related to business transactions, such as invoices, payments, orders, receipts, and reports. ERP software also provides real-time data analysis, reporting, and forecasting capabilities12.

Escalating to the Change Control Board (CCB) is necessary when a change request impacts the project’s timeline or budget. The CCB reviews and approves changes, ensuring that they align with project objectives. CompTIA Project+ highlights the role of the CCB in change management processes.

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

When onboarding new staff who will handle sensitive data, the PM must first verify their security clearance or authorization. Only authorized personnel should access sensitive systems or datasets. Training follows after confirming clearance. Data analysis itself should never begin until security requirements are validated.

The project charter is a foundational document that formally authorizes a project and provides the project manager with the authority to apply organizational resources to project activities. Reviewing the project charter is essential at the outset to understand the project's objectives, scope, stakeholders, and any constraints or assumptions. This understanding is crucial, especially for large, complex projects with regulatory and environmental considerations, as it sets the direction for detailed planning and stakeholder engagement.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.1: Explain the value of artifacts in the discovery/concept preparation phase for a project, the project charter is a key artifact that guides the initiation and planning phases.

A project closure meeting is a formal gathering held at the end of a project timeline. Its chief purpose is to evaluate the project’s performance, identify and discuss the achieved outcomes, successes, and challenges, and confirm that all predefined tasks and objectives have been completed successfully1. The project closure meeting also involves obtaining project sign-off from all necessary parties, such as the project sponsor, the client, the stakeholders, and the team members. Project sign-off is the official approval that the project has met the agreed-upon criteria and quality standards, and that the project is formally closed2.

The Pareto Principle, or the 80/20 rule, is often represented by a Pareto chart, which is used to prioritize issues by showing the most significant factors. CompTIA Project+ recommends Pareto analysis as a valuable tool for quality control and decision-making.

Because the regulatory change is anticipated (“coming in the next month”) and has not yet impacted the project, it should be treated as a risk (a potential future event) rather than an issue (a current problem). The correct next step is to add the risk to the risk register so it can be assessed for probability/impact, assigned an owner, and have response actions planned (avoid/mitigate/transfer/accept and contingency plans). This aligns with CompTIA Project+ risk management expectations: using the risk register to capture and manage upcoming threats that could affect scope, schedule, cost, or compliance obligations.

The other options don’t fit “next.” An issue log is for something that is already occurring and needs resolution now. A CCB is used when a specific change request is ready to be evaluated/approved, but at this point the PM needs to first understand the regulatory impact and options (which begins with risk capture and analysis). A work-around is a temporary fix for an active problem, which does not apply to an upcoming regulatory change. The PM should document the risk, analyze impact, and then—if needed—raise change requests once requirements and compliance impacts are clear.

This work is best described as current state vs. future state analysis. The team first examined the existing process (the current state), identified areas of improvement (gaps/pain points), and then defined the desired outcomes (the future/target state). In CompTIA Project+ discovery/concept preparation activities, teams are expected to understand the problem/opportunity clearly before planning the solution; comparing the current state to the desired future state is a standard way to define what must change and what “better” looks like, and it becomes a foundation for scope definition and transition planning.

It’s not “process improvement” as the primary label here because that term typically describes the initiative type or the resulting actions, while the question is asking what the analysis itself is called. It’s also not “business objectives” (those are broader strategic goals), and it’s not “project success criteria” (the measurable conditions used to judge success). Those may come later, derived from the current-vs-future gap, but the described activity is the gap comparison between how things work now and how they should work after the project.

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.

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.

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

This describes a transition plan (also called a release plan) because it focuses on moving a deliverable into production/go-live, defining the target audiences/users, and identifying operational training needs. The CompTIA Project+ objectives explicitly list “Develop a transition plan/release plan” and include example components such as operational training, go live, operational handoff, and identifying internal vs. external audience—all of which match the scenario.

A contingency plan is for responding to risks/issues if something goes wrong, not the standard production handover approach. A scope statement defines what work/deliverables are included and excluded, but it doesn’t detail production cutover, operational ownership, or training. A communication plan defines how information is shared (who, what, when, and through what channels), but it is not specifically the go-live and operational handoff blueprint.

So, because the team is planning deployment/move to production plus user identification and training, they are developing the transition plan.

The project manager should have prepared acceptable communication channels to avoid the situation of a stakeholder not replying to emails due to intermittent Internet service. Acceptable communication channels are methods or modes of communication that are agreed upon by all parties involved in a project. They may include aspects such as email, phone call, text message, video conference, instant message, or face-to-face meeting. Acceptable communication channels can help to ensure that messages are delivered and received effectively and efficiently and that communication preferences and limitations are respected.

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.

The project manager should have generated a contingency plan first to alleviate the impact of this issue prior to deployment where a major malfunction resulted in an inoperative product condition during a code implementation. A contingency plan is a plan that outlines alternative courses of action or strategies to deal with potential problems or risks that may occur during a project. A contingency plan can help to prevent or minimize the negative impacts of unforeseen events or issues on the project objectives and deliverables and ensure business continuity and stability.

Country legal regulations. Country legal regulations are impacting the rest of the team that did not receive the equipment for testing. Country legal regulations are rules and laws that govern how businesses operate in different countries. They may include aspects such as customs, tariffs, taxes, import and export restrictions, data protection, intellectual property rights, and environmental standards. Country legal regulations can affect the delivery and use of equipment for a global project team and may require compliance with different procedures and documentation3

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.

The project manager should ask the developer to create a change request, which is a formal document that describes the proposed change, its benefits, costs, risks, and impacts on the project scope, schedule, budget, and quality. A change request is the first step in the change control process, which involves evaluating, approving, or rejecting changes to the project baselines. The project manager should not do nothing, because ignoring the recommendation could result in poor performance and customer dissatisfaction. The project manager should not ask the developer to implement the recommendation without following the change control process, because that could cause scope creep, which is the uncontrolled expansion of the project scope without proper authorization or adjustment of the project resources and objectives. The project manager should not communicate the change status before the change request is submitted and approved, because that could create confusion and false expectations among the project stakeholders. 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; What is a Change Request and How to Manage It3

The most important responsibility of an asset owner when introducing a new information asset is information classification. This process involves determining the level of sensitivity and the appropriate handling of the asset. Classification helps in applying the right security controls and access permissions, ensuring that the asset is protected according to its value and sensitivity.

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

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.

The project manager should approve the deliverables and monitor the performance of the outsourced structured cabling activities. These are the responsibilities of the project manager when dealing with external vendors or contractors, as they ensure that the quality standards, scope, schedule, and budget are met according to the contract terms and the project plan. The project manager should also communicate regularly with the vendor and provide feedback and guidance as needed. The other options are not correct because:

Purchasing the materials is not the responsibility of the project manager, but the vendor who is performing the structured cabling activities. The project manager should only verify that the materials are suitable and available for the project.

Assigning the resources is not the responsibility of the project manager, but the vendor who is performing the structured cabling activities. The project manager should only ensure that the vendor has the adequate and qualified resources to complete the work.

Accepting delays in the work is not a good practice for the project manager, as it can negatively affect the project schedule, scope, and quality. The project manager should proactively identify and manage the risks and issues that may cause delays, and implement contingency plans or corrective actions if necessary.

Negotiating with the vendors is not a task that the project manager should do during the execution of the structured cabling activities, as it should have been done during the planning and procurement phases of the project. The project manager should only adhere to the contract terms and conditions that have been agreed upon with the vendor, and only renegotiate if there are significant changes or disputes that require it. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 8: Planning Projects, Part 4 (Procurement and Communication), pages 243-260; CompTIA Project+ Certification Exam Objectives, Domain 2: Project Planning, Objective 2.5: Given a scenario, plan procurement for a project; Domain 3: Project Execution, Objective 3.2: Given a scenario, execute and monitor project tasks using traditional methodologies.

A dashboard is a visual tool that displays key project metrics and indicators in a single view12. A dashboard can help a project sponsor to provide the latest project status information on a weekly executive call by showing the project progress, budget, schedule, risks, issues, and milestones in a clear and concise way34. A dashboard can also facilitate communication, collaboration, and decision making among project stakeholders56. A dashboard should be reviewed and updated regularly to reflect the current state of the project7. References = CompTIA Project+ Certification Study Guide8, CompTIA Project+ Certification Exam Objectives9, Write a Project Status Report in 8 Steps + Template [2023] • Asana6, Project Status Reports: 9 Easy Steps & Examples [+ Template]7, How To Write a Project Status Report (Definition and Steps)8, How to Write a Project Status Report [Template Included] - Toggl9, What Is a Project Status? Definition and Key Terms - Indeed10

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.

Option C shows a graph that most likely represents the observed relationship in this scenario. The graph shows a learning curve, which is a graphical representation of the relationship between a learner’s performance on a task and the number of attempts or time required to complete the task. The learning curve theory proposes that a learner’s efficiency in a task improves over time the more the learner performs the task. In this case, the IT intern was able to complete more set-ups in less time as they gained more experience and proficiency over the two-week rotation12

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)