|
| 1 | +### YamlMime:ModuleUnit |
| 2 | +uid: learn.wwl.develop-ai-agents-azure-vs-code.knowledge-check |
| 3 | +title: Knowledge check |
| 4 | +metadata: |
| 5 | + title: Knowledge Check |
| 6 | + description: Check your knowledge of AI agent development with Microsoft Foundry. |
| 7 | + ms.date: 02/12/2026 |
| 8 | + author: ivorb |
| 9 | + ms.author: berryivor |
| 10 | + ms.topic: unit |
| 11 | + ai-usage: ai-generated |
| 12 | +durationInMinutes: 3 |
| 13 | +quiz: |
| 14 | + title: Check your knowledge |
| 15 | + questions: |
| 16 | + - content: What is the primary benefit of using Microsoft Foundry Agent Service compared to building agents with standard APIs? |
| 17 | + choices: |
| 18 | + - content: It provides access to more powerful AI models |
| 19 | + isCorrect: false |
| 20 | + explanation: Incorrect. Microsoft Foundry Agent Service uses the same models available through standard APIs. |
| 21 | + - content: It requires no Azure subscription |
| 22 | + isCorrect: false |
| 23 | + explanation: Incorrect. You need an Azure subscription to use Microsoft Foundry Agent Service. |
| 24 | + - content: It handles tool calling, state management, and infrastructure automatically |
| 25 | + isCorrect: true |
| 26 | + explanation: Correct. Microsoft Foundry Agent Service manages the complexity of tool calling, conversation state, and infrastructure, reducing development effort. |
| 27 | + - content: It only works with the Azure portal |
| 28 | + isCorrect: false |
| 29 | + explanation: Incorrect. Microsoft Foundry Agent Service works with both the Azure portal and Visual Studio Code extension. |
| 30 | + - content: How does Microsoft Foundry Agent Service handle conversation state? |
| 31 | + choices: |
| 32 | + - content: By requiring developers to manually manage conversation history |
| 33 | + isCorrect: false |
| 34 | + explanation: Incorrect. The service handles conversation state automatically. |
| 35 | + - content: Through external database connections |
| 36 | + isCorrect: false |
| 37 | + explanation: Incorrect. The service manages state internally without requiring external databases. |
| 38 | + - content: Through the Responses API which automatically manages conversation context |
| 39 | + isCorrect: true |
| 40 | + explanation: Correct. The Responses API handles conversation context automatically, removing the need for manual state management. |
| 41 | + - content: Using local file storage on the client device |
| 42 | + isCorrect: false |
| 43 | + explanation: Incorrect. Conversation state is managed by the service, not stored locally on client devices. |
| 44 | + - content: Which of the following is NOT a recommended security practice for AI agents? |
| 45 | + choices: |
| 46 | + - content: Using role-based access controls |
| 47 | + isCorrect: false |
| 48 | + explanation: Incorrect. This is a recommended security practice. |
| 49 | + - content: Implementing prompt filtering and validation |
| 50 | + isCorrect: false |
| 51 | + explanation: Incorrect. This is a recommended security practice to prevent injection attacks. |
| 52 | + - content: Maintaining comprehensive logging and traceability |
| 53 | + isCorrect: false |
| 54 | + explanation: Incorrect. This is a recommended security practice for auditability. |
| 55 | + - content: Allowing agents unrestricted access to all enterprise data |
| 56 | + isCorrect: true |
| 57 | + explanation: Correct. This is NOT recommended. Agents should follow least privilege principles with restricted access based on their specific needs. |
| 58 | + - content: What happens when an agent determines it needs a tool to respond to a user request? |
| 59 | + choices: |
| 60 | + - content: The agent asks the user for permission to use the tool |
| 61 | + isCorrect: false |
| 62 | + explanation: Incorrect. Agents don't request permission; they automatically use configured tools. |
| 63 | + - content: The agent stops processing and waits for developer input |
| 64 | + isCorrect: false |
| 65 | + explanation: Incorrect. Agents handle tool invocation automatically without developer intervention. |
| 66 | + - content: The agent automatically invokes the tool, processes results, and incorporates them into its response |
| 67 | + isCorrect: true |
| 68 | + explanation: Correct. Microsoft Foundry Agent Service handles the complete tool-calling lifecycle automatically. |
| 69 | + - content: The agent sends the request to a separate processing queue |
| 70 | + isCorrect: false |
| 71 | + explanation: Incorrect. Tool execution happens synchronously as part of the response generation process. |
0 commit comments