AI-300 Certification Practice Question #19

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
You work in Microsoft Foundry with a prompt flow.
You must manually evaluate prompts and compare results across prompt variants.
You need to capture the inputs, outputs, token usage, and latencies for each flow run for the evaluation.
Solution: In Microsoft Foundry, turn on Tracing for the prompt flow of the project and execute test runs to produce trace data.
Does the solution meet the goal?

Accepted Answer

The goal enumerates **inputs, outputs, token usage, and latency per run** — the precise telemetry that Foundry **Tracing** records (token_consumption + flow_latency, plus prompt/response content). Turning on tracing and executing test runs therefore captures the required evaluation data, so the solution meets the goal (**Yes**), matching the Suggested Answer and MS Learn. The community Most Voted (No) argues tracing isn't the formal variant-comparison experience, but the question only requires capturing the run data, not side-by-side comparison. Because a high-weight signal (Most Voted) dissents, confidence is held at 74% and both views are documented; this also stays consistent with the sibling Q11 (where the Evaluation experience is judged *not* to capture this telemetry).

More AI-300 practice questions