A program manager must move scattered onboarding guides from chat threads into a durable team knowledge base that non-developers can read and update, with version history and links between setup, tooling, and support pages. Which use of creating and updating wikis best meets the collaboration need?

The correct approach succeeds because a repository wiki provides a durable, centrally discoverable knowledge base outside transient chat, markdown keeps formatting maintainable, inter-page links connect setup, tooling, and support into a navigable structure, and in-place editing with built-in revision history lets both technical and non-technical contributors read, update, and audit content over time. Storing the same linked markdown under version control with pull-request review is a respected docs-as-code practice, but it fails the collaboration need on accessibility because non-developers are forced through a code workflow to propose even simple updates. Maintaining openly editable wiki pages with history for each topic captures durability and inclusivity, yet keeping each topic isolated without cross-links fails the requirement for a connected information architecture that helps newcomers navigate dependencies. Sharing linked wiki content by circulating exported copies is common for distribution, but it fails on sustainability and traceability because the system of record fragments into detached files with no reliable version history or single place to update. For the exam, distinguish repository storage mechanics from collaboration affordances and do not select a technically robust method that omits one stated audience or structural need. As a practical check, confirm any proposed solution lets a non-developer find the setup page, follow a link to tooling and support, make an edit, and review prior versions without leaving the wiki.