CompTIA Updated PK0-005 Exam Questions and Answers by stanislaw

If a team member is still able (or forced) to charge time to a project months after it ended, the most likely missed closure activity is releasing project resources. In CompTIA Project+ closing activities, resource release/offboarding is a key step: it ensures people are formally transitioned off the project, their assignments are ended in the resourcing/timekeeping system, and they become available to be allocated to new work. If the PM neglects this, the organization’s resource management system may keep the person tied to the closed project code, preventing accurate time charging and creating both reporting and utilization problems.

“Removing access” (A) is a security/offboarding step and might be relevant for systems or repositories, but it doesn’t directly control time code availability or project assignment in resource planning. “Collecting stakeholder feedback” (C) supports lessons learned and continuous improvement, not time charging. “Having the closeout report approved” (D) is important for formal closure, but the specific symptom—charging time incorrectly and being blocked from new projects—points most directly to failing to release resources in the organization’s administrative systems.

So the PM neglected to complete the operational closure step of releasing the project resources, ensuring staffing and timekeeping are correctly transitioned to new work.

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 answer is based on the best practice of using historical information and lessons learned from previous projects to improve the planning and execution of current projects12. By using existing artifacts, such as scope statements, project plans, risk registers, and change logs, the PM can leverage the knowledge and experience of the previous PM and avoid repeating the same mistakes or oversights. However, the PM should also accommodate the artifacts based on the current project success criteria, which may differ from the previous project in terms of scope, schedule, budget, quality, or stakeholder expectations34. The PM should not rely solely on the previous PM’s advice, the project sponsor’s report, or the project charter, as these sources may not provide enough detail or accuracy for the current project’s scope statement. References = CompTIA Project+ Certification Study Guide5, CompTIA Project+ Certification Exam Objectives6, How to Use Historical Information in Project Management1, How to Use Lessons Learned to Improve Project Management2, How to Define Project Success Criteria3, How to Use Existing Artifacts in Project Management4

RACI is a tool that best illustrates how team members with different roles should interact on the team. RACI is an acronym that stands for responsible, accountable, consulted, and informed. RACI is a type of responsibility assignment matrix (RAM) that defines and clarifies the roles and responsibilities of each team member for each task or activity in a project. RACI can help to improve communication, collaboration, and accountability among team members and avoid confusion, duplication, or conflicts3