PK0-005 Exam Dumps - CompTIA Project+ Certification (2026)

The project manager should put in place a time and materials contract before work begins for a third party that needs to perform a short-term task for which the duration cannot be accurately estimated and the cost cannot be calculated in advance. A time and materials contract is a type of contract where the buyer pays the seller based on the actual time spent and materials used during the project. A time and materials contract is suitable for projects that have uncertain or variable scope, duration, or cost. A time and materials contract can provide flexibility and adaptability for both parties and allow them to adjust to changing requirements or circumstances.

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

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

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

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

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.

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?

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.

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.

Before starting a new project that involves personal data, the project manager should first understand the relevant privacy regulations that apply to the data subjects, the data controllers, and the data processors. These regulations may vary depending on the location, industry, and nature of the data. For example, GDPR applies to any project that processes the personal data of individuals in the European Union, regardless of where the project is based or executed. Understanding the applicable privacy regulations will help the project manager to identify the legal obligations, risks, and compliance requirements for the project data. References = CompTIA Project+ Study Guide, Chapter 3: Project Planning, Section 3.4: Data Privacy and Security, p. 121-122; A Project Management Approach to Data Protection Compliance; 10 Data Protection Considerations Before Starting a New Project; Project Teams Must Manage Risk and New Requirements to Ensure Data Privacy