You have an Azure DevOps organizationthat contains a project named Project1. You need to create a published wiki in Project1. What should you do…

Azure DevOps supports two types of wikis: a project wiki and a published wiki. A project wiki is created with a dedicated, system-managed Git repository. In contrast, a published wiki is created by publishing Markdown files from an existing Git repository that you manage. Therefore, the fundamental prerequisite and the first step to creating a published wiki is to have a source Git repository within the Azure DevOps project. This repository will contain the Markdown files and folder structure that will be rendered as the wiki content.

A. Modifying storage settings is related to Azure Artifacts and build/release retention policies, not the creation of a wiki.

B. An Azure DevOps pipeline is used for CI/CD automation and is not a prerequisite for creating the initial wiki structure.

D. Team configuration settings manage agile tools like backlogs, sprints, and area paths, which are unrelated to wiki creation.

1. Microsoft Docs

Azure DevOps Services. "Provisioned vs. published wiki". This document explicitly states

"You can publish content you already maintain in a Git repository to an Azure DevOps wiki." This confirms that a repository is the source for a published wiki.

Reference Location: The table comparing "Project wiki" and "Publish code as wiki".

2. Microsoft Docs

Azure DevOps Services. "Publish a Git repo to a wiki". This guide details the process

and the first prerequisite listed is having a Git repository.

Reference Location: The "Prerequisites" section states

"You must be a member of the project... You must have a Git repository that you want to publish to a wiki." The first step in the procedure is to navigate to an existing repository.