|
| 1 | +### YamlMime:ModuleUnit |
| 2 | +uid: learn.wwl.manage-ado-mcp-server.knowledge-check |
| 3 | +title: Module assessment |
| 4 | +metadata: |
| 5 | + title: Module Assessment |
| 6 | + description: "Knowledge check" |
| 7 | + ms.date: 02/27/2026 |
| 8 | + author: wwlpublish |
| 9 | + ms.author: petender |
| 10 | + ms.topic: unit |
| 11 | + module_assessment: true |
| 12 | +durationInMinutes: 8 |
| 13 | +quiz: |
| 14 | + title: "Check your knowledge" |
| 15 | + questions: |
| 16 | + - content: "After installing and configuring the Azure DevOps MCP Server in Visual Studio Code, what is the best first step to validate setup safely?" |
| 17 | + choices: |
| 18 | + - content: "Run a read-only query that confirms organization and project context before approving broader actions." |
| 19 | + isCorrect: true |
| 20 | + explanation: "Correct. A scoped read-only validation confirms identity, connectivity, and context with minimal risk." |
| 21 | + - content: "Immediately execute a batch update on work items to verify write permissions." |
| 22 | + isCorrect: false |
| 23 | + explanation: "Incorrect. Starting with high-impact write operations increases risk before trust and context are validated." |
| 24 | + - content: "Approve all prompts for the session to reduce setup friction." |
| 25 | + isCorrect: false |
| 26 | + explanation: "Incorrect. Broad approvals should come only after confidence is established through deliberate validation." |
| 27 | + - content: "Which prompt approach most improves reliability when creating and linking work items through MCP?" |
| 28 | + choices: |
| 29 | + - content: "Use explicit project, work item type, and relationship intent so the payload scope is unambiguous." |
| 30 | + isCorrect: true |
| 31 | + explanation: "Correct. Clear targets and relationship intent reduce ambiguity and produce safer, more actionable results." |
| 32 | + - content: "Use short generic prompts and rely on MCP to infer the rest from prior chat context." |
| 33 | + isCorrect: false |
| 34 | + explanation: "Incorrect. Overly generic prompts often lead to scope drift and extra correction cycles." |
| 35 | + - content: "Avoid linking work items until after the sprint ends to reduce prompt complexity." |
| 36 | + isCorrect: false |
| 37 | + explanation: "Incorrect. Delayed linking weakens traceability during active planning and delivery." |
| 38 | + - content: "When managing pull requests with MCP, what reflects strong governance-aligned practice?" |
| 39 | + choices: |
| 40 | + - content: "Use MCP to assemble context and draft focused comments, while keeping final approval with required human reviewers and branch policies." |
| 41 | + isCorrect: true |
| 42 | + explanation: "Correct. MCP accelerates review preparation, but policy and accountable human approval still govern merge decisions." |
| 43 | + - content: "Auto-approve pull requests when MCP summaries indicate low risk." |
| 44 | + isCorrect: false |
| 45 | + explanation: "Incorrect. Summaries assist review, but they do not replace required policy checks and human judgment." |
| 46 | + - content: "Skip linked work-item validation if the PR title appears complete." |
| 47 | + isCorrect: false |
| 48 | + explanation: "Incorrect. Traceability checks are essential for quality and auditability." |
| 49 | + - content: "During release-day pipeline monitoring, which action best supports fast and reliable incident response?" |
| 50 | + choices: |
| 51 | + - content: "Anchor follow-up queries to the build ID, track stage status, and escalate to targeted log inspection when failures appear." |
| 52 | + isCorrect: true |
| 53 | + explanation: "Correct. Build ID anchoring and focused escalation create a clean path from detection to diagnosis." |
| 54 | + - content: "Monitor by pipeline display name only and rerun immediately on any failure." |
| 55 | + isCorrect: false |
| 56 | + explanation: "Incorrect. Name-only tracking can cause ambiguity, and immediate reruns without diagnosis can hide root causes." |
| 57 | + - content: "Wait until all pipelines complete before checking failures to avoid interruptions." |
| 58 | + isCorrect: false |
| 59 | + explanation: "Incorrect. Delayed triage increases delivery risk and slows coordinated response." |
0 commit comments