Microsoft Certified: Multi-Agent AI Solutions Expert (AI-500) Practice Tests

Explanation

Visual Studio Code stores MCP server definitions in an mcp.json file, created in the user configuration (Global) or in the workspace when you add a server; the file shows Start or Restart links and the Running status. host.json, local.settings.json, and function.json are Azure Functions configuration files, not MCP client configuration.

Explanation

Consolidation uses LLMs to merge similar or duplicate topics and to resolve conflicting facts. Extraction pulls candidate information from conversations, retrieval searches the store, and short-term memory tracks only the current session.

Explanation

Fine-tuning needs both data plane and control plane permissions, and deploying the fine-tuned model is a control plane permission. Foundry Owner is the only built-in role with both; Foundry User alone covers data plane and Foundry Account Owner is the control plane half of the two-role alternative.

Explanation

Prompt Optimizer is integrated into the Agent playground and tunes prompts using evaluation results. Insights surfaces recurring trace findings, Tool Search loads tool definitions on demand, and Model Router session affinity prefers the same model across related requests.

Explanation

Reviewers accessing the Foundry human evaluation preview web app require the Foundry User role. The Foundry Project Manager role is required for creating evaluation templates, not just viewing them. Log Analytics Reader is for viewing traces in Application Insights, and Agent Consumer is for calling agent endpoints, not reviewing evaluation results.