September 6, 2026 · 8 min read
TL;DR: Knowledge transfer questions test whether the receiving person can do the work unaided, not whether the knowledge was recorded. Documentation appears as an option in 24 of the 45 multiple-choice questions in this bank's knowledge transfer slice and is keyed correct in 4. When the knowledge is judgement, the keyed answer puts two people on the same task. When it is a record that must outlive everyone, documentation wins.
A specialist gives notice. You have four weeks and a team that has never touched their work. One option has them write everything up before they go. It sounds responsible. On this exam it is usually the distractor.
Explicit knowledge is written down. It copies cleanly, it stores, it searches, and it arrives stripped of the situation that produced it. Tacit knowledge is the judgement in someone's head. It transfers badly, and its advantage is exactly what makes it hard to move: it comes with its context attached.
One bank question tests that as vocabulary and nothing else. It asks for an advantage of tacit knowledge, and the key is that it has context built in. The three wrong options all describe explicit knowledge: readily shared, readily codified, open to interpretation. That last one is a real weakness of written material, offered as though it were tacit knowledge's problem.
| Explicit | Tacit | |
|---|---|---|
| Where it lives | Documents, repositories, models, code | People's judgement and habits |
| Transfers by | Being read | Being watched, then practised |
| Fails by | Going stale, losing context | Walking out of the building |
| Keyed fix in the bank | A named owner, a verification date, a retired-document marker | Shadowing, secondment, paired work, a shared workshop |
Most scenarios do not use either word. They describe a situation and let you work out which kind of knowledge is at stake, which is the real skill being tested.
Because a document transfers information and the question asks for capability. Of the 45 multiple-choice questions in this slice, a documentation option appears in 24 and is keyed correct in 4. In the other 20 it is the trap, and 14 of the keys put one person alongside another instead.
One scenario has a forestry group commissioning log-grading scanners at four sawmills in turn. The first mill is done, its crew has moved on, and a different crew starts the second next week. The plausible option circulates the first crew's written lessons. The keyed answer seconds one installer from the first mill into the second mill's crew, for a reason the explanation states plainly: written lessons capture only what the writer thought to record.
Another has a gas network replacing a control system its field operators have run for twenty years. Every transfer arrangement moves knowledge outward to operations and none of it inward to the team designing the replacement. Asking the operators to write down what they do is wrong for a precise reason: it yields only what they know they know, the part least at risk. The key puts the design team on shift with them.
Common trap: picking the option that produces an artefact. The distractors that lose here create a document, a log entry or a manual in place of a transfer. Learn the two exceptions as exceptions. Documentation wins when the record itself went missing (a test report vanished with the technician who ran it; the fix is a shared repository) and when written material exists but nobody trusts it (the fix is a named verifier and a last-confirmed date, not more writing). Transfer the judgement, unless what failed was the record.
Identify what knowledge leaves and who needs it, capture the explicit part while the holder can still check it, transfer the tacit part by paired work, verify the receiver can do the job unaided, then release the person. The verification step is the one candidates drop, and it is the one the sequence exists for.
An ordering question in the bank walks those five steps, and the logic behind each position is worth more than the list. Identification comes first because a handover attempting everything moves nothing well. Capture precedes shadowing so the receiver has something to work from and the holder something to correct. Verification sits before release because it is the last moment a gap can be found while somebody can still fill it. A handover signed off on the day the specialist leaves is a hope, not a transfer.
Departures are the biggest cluster in the slice. Of the 47 questions, 21 involve someone leaving, rotating, handing over or being onboarded, which explains why so many keys turn on time rather than technique. A creamery's only control-settings expert is scheduled to finish the build work and train the shift leads in the same weeks. The keyed answer moves the build work to other people. Nothing clever, just the recognition that a teaching plan with no hours in it is not a plan.
In the Governance performance domain, Section 2.1. Manage Project Knowledge is one of the nine processes it owns, and unlike many PMBOK 6 process names it survived the restructure intact. The exam files the work under People instead.
The standard treats knowledge as a governance concern; the July 2026 Exam Content Outline tests it as People Task 7, "help ensure knowledge transfer." In the previous outline it was a Process task. That move is the clearest signal of what the exam now thinks the topic is.
The split matters when you revise, because a related topic lives elsewhere. Of the 54 bank records mentioning lessons learned, 27 sit in Business Environment under continuous improvement and 17 in Process under project closure. Exactly 1 sits in the knowledge transfer slice. Learn lessons learned as part of handover and you will meet it on the exam in the wrong frame. It is a closure and improvement topic. Knowledge transfer is about one person and one job.
A newer group of scenarios has grown up around AI assistants, seven of the 47, and they follow the same rule. A summarizer records decisions accurately but drops the reasoning, so later teams reopen settled questions; the key records the reasoning with the decision. An assistant answers new joiners from a store still holding overturned decisions; the key marks those retired. A team ships dispatch rules the assistant wrote that nobody can explain, three weeks before handover; the key has them work through the rules until they can.
In each of those the tool works and the transferable understanding is missing, which is the tacit and explicit distinction in newer clothes. What separates a candidate who gets them right is knowing why the plausible option fails, which is why every wrong answer in this bank is explained, not just marked wrong.
What is the difference between tacit and explicit knowledge? Explicit knowledge is written down, copyable and searchable, but it arrives without its context. Tacit knowledge is judgement held in a person's head. Its advantage, and one bank question keys this exactly, is that it has context built in.
Why is "document it" so often the wrong answer? A document transfers information, not capability. In the 45 multiple-choice questions in this slice, a documentation option appears in 24 and is keyed correct in 4. The rest of the time the key puts a person next to another person.
Is Manage Project Knowledge still a PMBOK 8 process? Yes. Unlike several PMBOK 6 process names it survived, and it is owned by the Governance performance domain in Section 2.1. The exam tasks it against People, which is why the scenarios read as people problems.
Where does the exam test lessons learned? Mostly outside this topic. Of 54 bank records mentioning it, 27 are Business Environment continuous improvement and 17 are Process closure. Only 1 is in the knowledge transfer slice.
The 47 knowledge transfer questions in PMP Practice sit inside a bank of 2,141 re-certified against PMBOK 8 and the July 2026 Exam Content Outline, and every wrong answer carries the reasoning that makes it wrong, explained rather than just marked. Start the free 20-question sample with no card and no signup.
Related: Project closure: the sequence that trips candidates · Servant leadership on the 2026 exam · People domain study guide · Business environment study guide
Sources: PMI — PMP Examination Content Outline, 2026 (PDF) · PMI — PMBOK Guide standards
What is the difference between tacit and explicit knowledge?
Explicit knowledge is written down and can be copied, stored and searched, but it arrives without the context that produced it. Tacit knowledge is judgement held in someone's head, harder to share because it carries its context with it. One bank question keys exactly that: the advantage of tacit knowledge is that it has context built in.
Why is 'document it' so often the wrong answer on knowledge transfer questions?
Because a document transfers information, not capability. Across the 45 multiple-choice knowledge transfer questions in this bank's People slice, a documentation option appears in 24 and is keyed correct in 4. The keyed answer usually puts a person next to another person: shadowing, secondment, paired work, a joint workshop.
Is Manage Project Knowledge still a PMBOK 8 process?
Yes. It survives in PMBOK 8 as one of the nine processes owned by the Governance performance domain (Section 2.1). The exam tasks it against the People domain of the July 2026 Exam Content Outline, which is why the scenarios read as people problems rather than filing problems.
Where does the exam test lessons learned, if not under knowledge transfer?
Mostly elsewhere. Of the 54 records in this bank that mention lessons learned, 27 sit in Business Environment under continuous improvement and 17 in Process under project closure. Only 1 sits in the knowledge transfer slice. Lessons learned is an organizational-improvement topic on this exam, not a handover topic.