Correct Answer:

Explanation:
Correct sequence:
* Collect retrieval logs.
* Run RAG evaluators.
* Adjust chunking strategy.
* Re-index documents.
The process should begin by collecting retrieval logs . Retrieval diagnostics provide the evidence needed to understand which queries were issued, which document chunks were returned, and whether relevant content is being surfaced. Without retrieval telemetry, optimization becomes speculative rather than measurable.
Next, run RAG evaluators . Microsoft Foundry provides retrieval-oriented evaluators that assess how relevant retrieved context is to a query. The Retrieval evaluator measures contextual relevance without requiring ground truth, while the Document Retrieval evaluator can calculate metrics such as Fidelity and NDCG when labeled retrieval ground truth exists. These measurements help establish the retrieval-quality baseline before modifications are made.
After identifying retrieval deficiencies, adjust the chunking strategy . Microsoft specifically recommends reviewing chunk size and chunking methodology when retrieval returns irrelevant or incomplete passages.
Chunks that are too small can lose context, while oversized chunks can introduce irrelevant material and reduce retrieval precision.
Finally, re-index the documents so the revised chunking configuration is reflected in the searchable corpus.
Changing temperature or regenerating the prompt template primarily affects generation behavior rather than correcting the underlying retrieval pipeline.
Study Guide Reference: Implement generative AI quality assurance and observability - RAG evaluation, retrieval telemetry, retrieval-quality metrics, chunk optimization, indexing, and grounded-response assessment.

Correct Answer:

Explanation:

Correct Answer: B  🗳️

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

Correct Answer:

Explanation:
Azure Machine Learning ' s experiment tracking is built around two complementary concepts. First, experiments are named containers that group related runs. By calling mlflow.set_experiment with an experiment name at the start of your training code, all subsequent runs are grouped under that experiment name in the AML workspace, creating the centralized record required. Second, metrics are scalar values such as accuracy, loss, or AUC that represent model performance. Calling mlflow.log_metric with a metric name and value during training persists these values to the run ' s record in the experiment history. These values appear on the Azure ML Studio run detail page and can be compared across runs using the experiment comparison view. Without set_experiment, runs fall into a default experiment. Without log_metric, the run history has no performance data to display or compare.
Microsoft Learn Reference Topic: Track machine learning experiments with MLflow in Azure Machine Learning

Correct Answer:

Explanation:
For a tool that must process text inputs up to 200k tokens long, generate concise summaries in seconds, and support interactive testing, the configuration must address three requirements. The large token context window points to GPT-4o, which supports up to 128k tokens and is among the largest-context Azure OpenAI models available in Foundry, making it suitable for long documents such as meeting transcripts. Low latency with the need to generate responses in seconds rules out batch deployment types; Data Zone Standard provides the best latency for single-tenant enterprise use cases with zone-level routing. Interactive testing before integration points directly to Microsoft Foundry ' s built-in Chat Playground or Prompt Playground, where you can paste transcripts, adjust system prompts, and evaluate outputs interactively before writing any application integration code.
Microsoft Learn Reference Topic: Deploy and test models in Microsoft Foundry - Model selection for long- context summarization