|
| 1 | +### YamlMime:ModuleUnit |
| 2 | + |
| 3 | +uid: learn.dpu.deploy-windows.knowledge-check |
| 4 | + |
| 5 | +title: Knowledge check |
| 6 | + |
| 7 | +metadata: |
| 8 | + title: Knowledge check |
| 9 | + description: This content is part of the "Deploy updates for Windows client and Microsoft 365 apps" module. |
| 10 | + ms.date: 04/15/2026 |
| 11 | + author: Stephanie-Rosenzweig |
| 12 | + ms.author: v-stephanier |
| 13 | + ms.topic: unit |
| 14 | + ms.service: windows |
| 15 | + |
| 16 | +durationInMinutes: 5 |
| 17 | + |
| 18 | +quiz: |
| 19 | + title: Check your knowledge |
| 20 | + questions: |
| 21 | + |
| 22 | + - content: "What deployment approach is used during the Deploy phase of Windows 11 deployment?" |
| 23 | + choices: |
| 24 | + - content: "A ring-based or phased deployment approach" |
| 25 | + isCorrect: true |
| 26 | + explanation: "Correct. The Deploy phase uses a ring-based or phased approach to manage risk and validate success as deployment expands." |
| 27 | + - content: "A single, organization-wide deployment" |
| 28 | + isCorrect: false |
| 29 | + explanation: "Incorrect. The Deploy phase does not recommend deploying to the entire organization at once." |
| 30 | + - content: "Manual deployment on a per-device basis" |
| 31 | + isCorrect: false |
| 32 | + explanation: "Incorrect. Deployment is managed through structured deployment rings, not manual per-device deployment." |
| 33 | + - content: "A deployment approach focused only on new devices" |
| 34 | + isCorrect: false |
| 35 | + explanation: "Incorrect. The Deploy phase can address the full Windows environment, not only newly provisioned devices." |
| 36 | + |
| 37 | + |
| 38 | + - content: "Which six areas are addressed during the Deploy phase?" |
| 39 | + choices: |
| 40 | + - content: "Security, networking, identity, storage, backup, and compliance" |
| 41 | + isCorrect: false |
| 42 | + explanation: "Incorrect. These areas are important but are not the six areas defined in this module." |
| 43 | + - content: "Operations, applications, infrastructure, configurations, devices, and users" |
| 44 | + isCorrect: true |
| 45 | + explanation: "Correct. The module is structured around these six areas, which collectively support a successful Windows 11 deployment." |
| 46 | + - content: "Planning, testing, preparation, imaging, support, and training" |
| 47 | + isCorrect: false |
| 48 | + explanation: "Incorrect. Planning and preparation occur in earlier phases, not as part of the six Deploy areas." |
| 49 | + - content: "Hardware, firmware, licensing, procurement, inventory, and disposal" |
| 50 | + isCorrect: false |
| 51 | + explanation: "Incorrect. These activities may support deployment, but they are not the six areas outlined in this module." |
| 52 | + |
| 53 | + |
| 54 | + - content: "Why does the module recommend using pilot and broad deployment phases?" |
| 55 | + choices: |
| 56 | + - content: "To delay deployment until all devices are replaced" |
| 57 | + isCorrect: false |
| 58 | + explanation: "Incorrect. Deployment proceeds based on readiness and validation, not device replacement schedules." |
| 59 | + - content: "To limit deployment to a small group permanently" |
| 60 | + isCorrect: false |
| 61 | + explanation: "Incorrect. Pilot phases are temporary and designed to inform broader rollout." |
| 62 | + - content: "To validate readiness and monitor results before expanding deployment" |
| 63 | + isCorrect: true |
| 64 | + explanation: "Correct. Pilot and broad deployment phases help validate success criteria and reduce risk before wider rollout." |
| 65 | + - content: "To avoid the need for monitoring during deployment" |
| 66 | + isCorrect: false |
| 67 | + explanation: "Incorrect. Monitoring is a core component of both pilot and broad deployment phases." |
| 68 | + |
| 69 | + |
| 70 | + - content: "Why is it important to maintain deliverables throughout the Deploy phase?" |
| 71 | + choices: |
| 72 | + - content: "To support collaboration, tracking, and reporting across the deployment lifecycle" |
| 73 | + isCorrect: true |
| 74 | + explanation: "Correct. Deliverables should be easy to share and update, so they can support collaboration and reporting throughout deployment." |
| 75 | + - content: "To replace monitoring and management tools" |
| 76 | + isCorrect: false |
| 77 | + explanation: "Incorrect. Deliverables support deployment efforts but do not replace technical monitoring tools." |
| 78 | + - content: "To document the project only after deployment is complete" |
| 79 | + isCorrect: false |
| 80 | + explanation: "Incorrect. Documentation should be maintained continuously during deployment, not only at the end." |
| 81 | + - content: "To eliminate the need for stakeholder communication" |
| 82 | + isCorrect: false |
| 83 | + explanation: "Incorrect. Deliverables help support stakeholder communication but do not remove the need for it." |
0 commit comments