|
| 1 | +### YamlMime:ModuleUnit |
| 2 | +uid: learn.wwl.configure-ai-ready-infrastructure-microsoft-foundry.knowledge-check |
| 3 | +title: "Module assessment" |
| 4 | +metadata: |
| 5 | + title: "Knowledge check" |
| 6 | + description: "Test your understanding of Microsoft Foundry infrastructure configuration by applying concepts to realistic scenarios. These questions assess your ability to make architectural decisions about hub design, connection strategies, and RBAC assignments rather than memorizing portal navigation steps. Consider the organizational context, compliance requirements, and cost implications when selecting your answers." |
| 7 | + ms.date: 02/02/2026 |
| 8 | + author: wwlpublish |
| 9 | + ms.author: bradj |
| 10 | + ms.topic: unit |
| 11 | + ms.custom: references_regions |
| 12 | + module_assessment: false |
| 13 | +durationInMinutes: 7 |
| 14 | +content: "Choose the best response for each of the following questions." |
| 15 | +quiz: |
| 16 | + questions: |
| 17 | + - content: "Your organization runs 12 AI projects across three departments: Sales (4 projects), Marketing (5 projects), and Support (3 projects). The CFO requires monthly cost reports showing AI spending per department for chargeback purposes. Projects within each department share common Azure AI Search indexes but need isolated Azure OpenAI deployments due to different prompt engineering approaches. What connection strategy optimizes costs while enabling accurate department-level cost tracking?" |
| 18 | + choices: |
| 19 | + - content: "Create department-specific hubs (Sales Hub, Marketing Hub, Support Hub), establish hub-level Azure AI Search connections for shared indexes, and use project-level Azure OpenAI connections tagged with department cost centers" |
| 20 | + isCorrect: true |
| 21 | + explanation: "Department-specific hubs with mixed connection levels provide the optimal balance. Option A correctly establishes hub boundaries aligned with cost allocation requirements (departments) while using hub-level connections for shared services (search) and project-level connections for isolated services (OpenAI). Each department's hub aggregates costs for shared infrastructure, while project-level tags enable fine-grained tracking of dedicated resources. Microsoft Cost Management automatically groups spending by hub (department-level) and by project tags (application-level)." |
| 22 | + - content: "Create environment-based hubs (Production Hub, Development Hub), establish all connections at hub level including both Azure AI Search and Azure OpenAI, then use Azure tags on projects to track department spending" |
| 23 | + isCorrect: false |
| 24 | + explanation: "Option B fails because environment-based hubs don't align with the CFO's requirement for department-level reporting—all production projects across departments would aggregate into one cost bucket." |
| 25 | + - content: "Create one enterprise hub with all connections at hub level, rely on Microsoft Cost Management's resource-level spending reports to manually allocate costs per department each month" |
| 26 | + isCorrect: false |
| 27 | + explanation: "Option C requires manual cost allocation effort every month and risks errors when teams deploy resources outside the standard pattern." |
| 28 | + - content: "A junior team member attempts to connect to a hub's shared Azure AI Search service from a new project and receives error 'AuthorizationFailed: The client does not have authorization to perform action 'Microsoft.Search/searchServices/read''. The hub's managed identity has Search Index Data Reader role on the search service, and the team member holds Cognitive Services Contributor role on the hub. What is the most likely cause and appropriate solution?" |
| 29 | + choices: |
| 30 | + - content: "The team member needs the Search Service Contributor role assigned directly on the Azure AI Search service; add this role assignment to resolve access issues" |
| 31 | + isCorrect: false |
| 32 | + explanation: "The first option is incorrect because individual users don't need direct RBAC roles on the search service—they access it through the hub's inherited connection using the hub's managed identity." |
| 33 | + - content: "The project was created before the hub-level search connection was established, so it didn't inherit the connection; recreate the project to reinitialize connection inheritance" |
| 34 | + isCorrect: true |
| 35 | + explanation: "Connection inheritance only occurs at project creation time—projects don't automatically discover connections added to the hub after they already exist. Option B correctly identifies that the project needs to be recreated to inherit the new hub-level connection. When you create a project in a hub, Microsoft Foundry copies the hub's connection metadata into the project's configuration. Connections added later don't automatically propagate to existing projects." |
| 36 | + - content: "The hub's managed identity role assignment hasn't propagated yet; wait 10-15 minutes for Azure RBAC replication, then retry the search operation" |
| 37 | + isCorrect: false |
| 38 | + explanation: "The third option misdiagnoses the problem: the error message indicates missing authorization at the search service level, not RBAC propagation delays which would show different error patterns." |
0 commit comments