CompTIA Updated PK0-005 Exam Questions and Answers by kieran

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,

To show sequencing between all tasks (i.e., predecessor/successor relationships and dependency flow), the PM should provide a project network diagram. A summary Gantt chart is great for high-level timelines and major bars, but it can hide the detailed dependency logic that explains why tasks occur in a particular order and how delays propagate. In the CompTIA Project+ objectives, “Project network diagram” is explicitly listed among the key tracking charts/diagrams used to inform project decisions (alongside Gantt and milestone charts).

The other choices don’t match the need. A fishbone (Ishikawa) diagram is a root-cause analysis tool for quality issues, not for schedule dependencies. A burndown chart is used mainly in Agile to show remaining work over time, not task-to-task sequencing. A milestone chart highlights key dates, but it doesn’t show the detailed dependency chain between tasks.

So, to satisfy the team’s request for full sequencing visibility, the PM should share a project network diagram.

Objectives and success criteria are core elements of the project charter, which formally authorizes the project and establishes the high-level direction for what success looks like. During initiation, the PM works with stakeholders to define the project’s purpose, objectives, high-level scope, key stakeholders, assumptions/constraints, and success criteria. That aligns to CompTIA Project+ initiation artifacts and the practice of establishing alignment before detailed planning begins.

A requirements traceability matrix is used later to map detailed requirements through design/build/test to ensure nothing is missed; it’s not the primary artifact for initial objectives and success criteria. A communications plan defines audiences, channels, frequency, and message types; it’s informed by objectives but isn’t where objectives are defined. A risk register captures uncertainties and responses; it’s created/expanded as risks are identified but is not the main artifact for defining objectives and success measures.

So, when the PM is meeting stakeholders to define objectives and success criteria, they are primarily working on the project charter (or charter-level initiation documentation) that anchors the project’s “why” and how success will be evaluated.

Preliminary procurement involves identifying and evaluating potential vendors based on their qualifications and capabilities. This step is essential for project procurement and aligns with CompTIA Project+ best practices for vendor selection.