CompTIA Updated PK0-005 Exam Questions and Answers by avani

The sponsor wants the document where the initial scope is defined, and the best place to confirm that baseline is the project charter. The charter authorizes the project and typically includes the high-level purpose, objectives, high-level scope, key stakeholders, and success criteria. CompTIA Project+ emphasizes reviewing and using existing project artifacts to maintain alignment; when a stakeholder’s view of scope differs, the PM should first reference the authoritative initiation artifact that establishes the original agreement.

Creating a new project management plan (A) is premature and could worsen confusion if the baseline is not reconfirmed. Meeting minutes (B) can provide context, but they are not the formal scope authorization document the sponsor is asking for. “Perform project scope management” (C) is important as an ongoing process, but the question is asking what to do next to clarify differences and provide the initial scope document—reviewing the charter is the fastest and most correct step.

After reviewing the charter, the PM can facilitate alignment with the new stakeholder, and if scope truly needs to change, route it through formal change control and update scope artifacts accordingly.

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

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

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.