A customer service team leader at a homeware retailer wants Claude to draw on the company's 40-page returns policy every time the team drafts replies to customers. A colleague suggests asking Claude to remember the whole policy through Memory rather than setting up a Project with the policy in its knowledge. Which statement best explains why the Project is the better choice?
- AMemory is available only to some accounts, so a Project is the one option that every member of the team can use.
- BProject knowledge holds the full document for Claude to consult, whereas Memory carries brief context and is not for reference documents. Correct
- CMemory would store the policy word for word, but Claude would then answer far more slowly in every chat that drew on it.
- DA Project updates the policy file automatically whenever the retailer changes its returns rules, so the stored copy never goes out of date.
Why A is wrong: Availability can feel like a practical reason to choose, which is why this tempts. But the stem gives no information about accounts, and the real issue is what each feature is for, not who can switch it on.
Why B is correct: Project knowledge is designed to hold reference material that Claude consults in every chat in that Project. Memory keeps useful context about the user and past work between chats, but it is not a store for a long document whose exact wording matters.
Why C is wrong: This tempts because it accepts that Memory would work and blames only speed. In fact Memory is not built to hold a long document verbatim, so the premise is wrong and speed is not the deciding issue.
Why D is wrong: It is tempting to assume a Project keeps itself current. An uploaded knowledge file is a copy; when the policy changes, someone must replace the file with the new version, so this is not why the Project is better.