|
| 1 | +### YamlMime:ModuleUnit |
| 2 | +uid: learn.wwl.design-implement-sql-solutions-ai-assisted-tools.knowledge-check |
| 3 | +title: Module assessment |
| 4 | +metadata: |
| 5 | + ai_generated_module_assessment: true |
| 6 | + title: Module assessment |
| 7 | + description: Knowledge check for designing and implementing SQL solutions using AI-assisted tools |
| 8 | + ms.date: 02/02/2026 |
| 9 | + author: JulianePadrao |
| 10 | + ms.author: jupadrao |
| 11 | + ms.topic: unit |
| 12 | + module_assessment: false |
| 13 | +azureSandbox: false |
| 14 | +labModal: false |
| 15 | +durationInMinutes: 5 |
| 16 | +quiz: |
| 17 | + questions: |
| 18 | + - content: "A database developer wants to use AI assistance while writing T-SQL in SQL Server Management Studio. Which tool should they install?" |
| 19 | + choices: |
| 20 | + - content: "Fabric Copilot extension" |
| 21 | + isCorrect: false |
| 22 | + explanation: "Incorrect. Fabric Copilot is available within Microsoft Fabric workspaces, not SSMS. For SSMS, you need GitHub Copilot." |
| 23 | + - content: "GitHub Copilot through the AI Assistance workload" |
| 24 | + isCorrect: true |
| 25 | + explanation: "Correct. GitHub Copilot is installed in SSMS 22+ through the Visual Studio Installer by selecting the AI Assistance workload." |
| 26 | + - content: "Azure OpenAI extension" |
| 27 | + isCorrect: false |
| 28 | + explanation: "Incorrect. While Azure OpenAI powers some AI features, SSMS uses GitHub Copilot, which is installed through the AI Assistance workload." |
| 29 | + - content: "SQL IntelliSense extension" |
| 30 | + isCorrect: false |
| 31 | + explanation: "Incorrect. IntelliSense provides code completion but isn't an AI assistant. GitHub Copilot provides AI-powered assistance in SSMS." |
| 32 | + |
| 33 | + - content: "What security practice should you follow when using AI-assisted tools with database credentials?" |
| 34 | + choices: |
| 35 | + - content: "Store credentials in instruction files so Copilot can access them" |
| 36 | + isCorrect: false |
| 37 | + explanation: "Incorrect. Never store credentials in instruction files or any files that AI tools can access. Use environment variables instead." |
| 38 | + - content: "Include connection strings in prompts for accurate suggestions" |
| 39 | + isCorrect: false |
| 40 | + explanation: "Incorrect. Never paste credentials or connection strings with passwords into AI prompts. This exposes sensitive information." |
| 41 | + - content: "Use environment variables and never paste credentials into prompts" |
| 42 | + isCorrect: true |
| 43 | + explanation: "Correct. Store credentials in environment variables and never include actual passwords or secrets in prompts or files visible to AI assistants." |
| 44 | + - content: "Grant AI tools full database access for better context" |
| 45 | + isCorrect: false |
| 46 | + explanation: "Incorrect. Follow the principle of least privilege. AI tools typically only need read-only schema access, not full database permissions." |
| 47 | + |
| 48 | + - content: "What does Model Context Protocol (MCP) enable AI assistants to do?" |
| 49 | + choices: |
| 50 | + - content: "Generate code faster by using more powerful models" |
| 51 | + isCorrect: false |
| 52 | + explanation: "Incorrect. MCP doesn't change the AI model's speed or power. It provides context by connecting to external data sources." |
| 53 | + - content: "Connect directly to data sources for real-time schema and metadata access" |
| 54 | + isCorrect: true |
| 55 | + explanation: "Correct. MCP allows AI assistants to query your actual database schema, metadata, and sample data to provide more accurate, contextual suggestions." |
| 56 | + - content: "Encrypt communications between the IDE and AI service" |
| 57 | + isCorrect: false |
| 58 | + explanation: "Incorrect. While security is important, MCP's primary purpose is enabling AI assistants to access external data sources, not encryption." |
| 59 | + - content: "Store AI conversations for later reference" |
| 60 | + isCorrect: false |
| 61 | + explanation: "Incorrect. MCP is about connecting to data sources for context, not storing conversation history." |
| 62 | + |
| 63 | + - content: "Where should you place a copilot-instructions.md file to apply custom instructions to a repository?" |
| 64 | + choices: |
| 65 | + - content: "In the repository root folder" |
| 66 | + isCorrect: false |
| 67 | + explanation: "Incorrect. The instruction file should be in the GitHub configuration folder at the repository root, not directly in the root folder." |
| 68 | + - content: "In the VS Code configuration folder" |
| 69 | + isCorrect: false |
| 70 | + explanation: "Incorrect. The VS Code folder is for workspace settings and MCP configuration. Copilot instructions go in the GitHub configuration folder." |
| 71 | + - content: "In the GitHub configuration folder at the repository root" |
| 72 | + isCorrect: true |
| 73 | + explanation: "Correct. The copilot-instructions.md file should be placed in the GitHub configuration folder at your repository root to apply instructions to all repository users." |
| 74 | + - content: "In the user's home directory" |
| 75 | + isCorrect: false |
| 76 | + explanation: "Incorrect. User-level settings are separate from repository instructions. Repository-wide instructions go in the GitHub configuration folder." |
| 77 | + |
| 78 | + - content: "A team wants to connect their AI assistant to a Fabric Lakehouse. What should they configure?" |
| 79 | + choices: |
| 80 | + - content: "Install the MSSQL extension and connect directly" |
| 81 | + isCorrect: false |
| 82 | + explanation: "Incorrect. While the MSSQL extension works for SQL databases, Fabric Lakehouse requires publishing a data agent as an MCP server or using the Fabric MCP Server extension." |
| 83 | + - content: "Publish a Fabric data agent as an MCP server and connect using the MCP endpoint URL" |
| 84 | + isCorrect: true |
| 85 | + explanation: "Correct. Fabric data agents can be published as MCP servers. Copy the MCP server URL from the agent's settings and configure it in your mcp.json file." |
| 86 | + - content: "Use Azure Blob Storage connection strings" |
| 87 | + isCorrect: false |
| 88 | + explanation: "Incorrect. Fabric Lakehouse uses MCP servers, not direct blob storage connections, for AI assistant integration." |
| 89 | + - content: "Configure GitHub Actions to sync with Fabric" |
| 90 | + isCorrect: false |
| 91 | + explanation: "Incorrect. GitHub Actions are for CI/CD workflows, not for connecting AI assistants to Fabric Lakehouse. Use MCP servers instead." |
0 commit comments