Courseiva
Develop a security and compliance planeasyMultiple ChoiceObjective-mapped

AZ-400 Develop a security and compliance plan Practice Question

You need to ensure that only signed-in users can view Azure DevOps project wikis. Which setting should you configure?

⚠ Common exam trap

Watch out — candidates often confuse repository-level visibility with project-level visibility, assuming that setting a repo to private will also secure the wiki, when in fact the wiki is a project-level artifact and its access is governed by the project's visibility setting.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Set project visibility to 'Private'

Setting the project visibility to 'Private' ensures that only authenticated users who are members of the Azure DevOps organization can access the project and its wikis. Anonymous or unauthenticated users are blocked entirely at the project level, which directly satisfies the requirement to restrict wiki viewing to signed-in users only.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Configure wiki permissions to deny anonymous users

    Why it's wrong here

    Wiki permissions in Azure DevOps are scoped per-wiki repository and do not affect the overall project visibility. Anonymous users can only exist in public projects, and denying them wiki access does not prevent them from viewing other project artifacts, so this fails to ensure all signed-in users only. The project-level visibility setting is the authoritative control for anonymous access.

  • Set project visibility to 'Private'

    Why this is correct

    Setting the project visibility to 'Private' in Azure DevOps is the definitive project-level setting that requires all users to authenticate before viewing any project data, including wikis, repos, boards, and pipelines. This ensures that anonymous users are completely barred from accessing Azure DevOps content, as private projects only allow authenticated members or explicitly added external users.

  • Set repository visibility to 'Private'

    Why it's wrong here

    Repository visibility in Azure DevOps controls access only to the source code in Git or TFVC repositories, not to the wiki or other project services. The wiki is a separate component, and its access is determined by project visibility and wiki permissions, so setting repositories to private does not prevent anonymous users from viewing the wiki in a public project.

  • Use Microsoft Entra ID Application Proxy

    Why it's wrong here

    Microsoft Entra ID Application Proxy is designed for publishing on-premises web applications to external users through the Entra ID authentication gateway, not for managing access to cloud-native Azure DevOps services. Azure DevOps already integrates with Entra ID for identity; anonymous access is controlled by the project visibility setting, making Application Proxy irrelevant for this requirement.

About these practice questions

One of 823 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.