A company requires an agent in Copilot Studio to answer questions using content stored in a third-party knowledge base system and reuse that content for knowledge grounding.
The agent must ground answers using indexed enterprise knowledge from a non-Microsoft system.
You need to choose the correct integration approach.
What should you use?

• A. Call the third-party API from a topic for each question.
• B. Add a Copilot Studio tool and call it from a topic.
• C. Add a Copilot connector knowledge source for authorized content.
• D. Add a Copilot Studio tool as a real-time knowledge source.

Explanation: Only visible for PrepPDF members. You can sign-up / login (it's free).

A company wants an agent to retrieve real-time answers from a large, frequently updated document repository stored outside Dataverse, with strong relevance ranking. Which knowledge source should you configure?

• A. A single uploaded file
• B. Dataverse table search only
• C. Public website URLs only
• D. Azure AI Search

Explanation: Only visible for PrepPDF members. You can sign-up / login (it's free).

Hotspot Question
You run multiple evaluation tests for an agent in Copilot Studio before expanding user access.
You observe the following about the evaluation results:
- Each evaluation case is reported as meeting or missing the expected
response.
- Some evaluation cases fail repeatedly across several runs.
- Each run displays the expected response and the response generated by the agent.
You need to interpret what the evaluation results reveal.
What should you conclude based on each interpretation? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Explanation:
Box 1: Pass or fail status.
Based on the evaluation results, you can conclude the Pass or fail status.
Direct mapping: Measuring whether a case "meets" or "misses" an expectation is the definition of a binary pass/fail test.
Insufficient data for production: You cannot fully determine Production readiness because readiness requires broader metrics like latency, security, and user acceptance testing.
No diagnostic data: You cannot determine the Failure configuration because a simple "miss" label does not explain why the system failed or how it is misconfigured.
Box 2: Consistent outcomes
Based on the evaluation results, you can conclude that these are Consistent outcomes.
Definition of Consistency: Because the specific evaluation cases fail repeatedly across several runs, the behavior is predictable and stable, not random.
Box 3: Expected and generated responses:
The correct conclusion from these evaluation results is Expected and generated responses.
Expected and generated responses: The evaluation results explicitly show a side-by-side comparison between what the agent was supposed to say (expected response) and what it actually said (generated response). This allows you to conclude exactly how well the agent's outputs align with your test cases.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-agent-evaluation-results

An agent's flow-based tool intermittently fails when passed nested JSON objects as input parameters. What is the most likely cause?

• A. The flow trigger doesn't support the data type/schema being passed
• B. The environment variable is misnamed
• C. The knowledge source is offline
• D. The agent has too many topics

Explanation: Only visible for PrepPDF members. You can sign-up / login (it's free).

Drag and Drop Question
A solution containing an agent in Copilot Studio is deployed to multiple environments that require different configuration values.
Configuration values must vary by environment without modifying the solution contents.
Configuration values must meet the following requirements:
- Allow values to be set during import.
- Exclude values from the agent definition.
- Run a dedicated agent instance for each individual environment.
You need to associate each requirement with the configuration approach.
What should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Explanation:
Box 1: Define environment variables in the solution.
The correct ALM-related configuration to use for this requirement is Environment Variables.
You must use Environment Variables (specifically with the Current Value left blank in the development solution) to allow different configuration values across multiple environments without modifying the solution contents. When you export the solution as managed and import it into a target environment, the system will explicitly prompt the administrator to set the values during import.
Box 2: Define environment variables in the solution
Define environment variables in the solution is the correct Application Lifecycle Management (ALM) configuration to use for this requirement.
Separates Data from Code: Environment variables act as parameters that store configuration keys and values separately from your agent's definition.
Preserves Solution Integrity: You can transport the same solution across development, testing, and production environments without modifying any of its internal contents.
Excludes Hardcoded Values: They explicitly remove the need to embed sensitive or environment- specific data directly inside the agent, satisfying your exact requirement.
Box 3: Define environment variables in the solution
You should use Environment Variables combined with Connection References within Power Platform / Copilot Studio.
Define parameters centrally: Create environment variables inside your solution to act as placeholders for your configuration values (like URLs, IDs, or API keys).
Keep the solution generic: Your Copilot agent references these variables rather than hardcoded values.
Set values per deployment: When you import the managed solution into a new environment (Test, Production, etc.), the deployment pipeline prompts you to provide the specific values for that environment.
Isolate agent traffic: Because the variables point to environment-specific backend services, data sources, or IDs, a single solution definition naturally spins up and drives a dedicated, isolated agent instance in each environment.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/alm