Online Access Free AI-300 Practice Test

You have an Azure Machine Learning workspace named Workspace 1 Workspace! has a registered Mlflow model named model 1 with PyFunc flavor You plan to deploy model1 to an online endpoint named endpointl without egress connectivity by using Azure Machine learning Python SDK vl You have the following code:

You need to add a parameter to the ManagedOnllneDeployment object to ensure the model deploys successfully Solution: Add the with_package parameter.
Does the solution meet the goal?

• A.No
• B.Yes

you create an Azure Machine learning workspace named workspace1. The workspace contains a Python SOK v2 notebook mat uses Mallow to correct model coaxing men's anal arracks from your local computer.
Vou must reuse the notebook to run on Azure Machine I earning compute instance m workspace.
You need to comminute to log training and artifacts from your data science code.
What should you do?

• A.Log in to workspace1.
• B.Instantiate the MLClient class.
• C.Instantiate the job class.
• D.Configure the tracking URL.

-
A team is developing a Retrieval-Augmented Generation (RAG) system.
The team requires improvements to the system ' s retrieval quality to ensure accurate, grounded responses.
You need to assess RAG performance before you can suggest an improvement strategy.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

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.

You have an Azure Machine Learning workspace named workspaces.
You must add a datastore that connects an Azure Blob storage container to workspaces. You must be able to configure a privilege level.
You need to configure authentication.
Which authentication method should you use?

• A.Service principal
• B.Account key
• C.SAS token
• D.Managed identity

A team is building a generative AI agent by using Retrieval-Augmented Generation (RAG) in Microsoft Foundry.
The team frequently updates prompt content. The team must be able to track changes across contributors while avoiding full application redeployments.
You need to enable rapid prompt iteration with traceability. Applications consuming the agent must be able to use updated prompts without requiring redeployment.
What should you configure for each requirement? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

Correct Answer:

Explanation:
For tracking changes across contributors, Git integration is the answer: by connecting the Microsoft Foundry project to a Git repository, every prompt file change is tracked as a commit with author attribution, timestamp, and diff view, and pull requests enforce review before changes reach production. The Git history provides the complete audit trail and rollback capability needed for traceability. For allowing applications to consume updated prompts without requiring redeployment, Microsoft Foundry ' s prompt management feature allows prompts to be stored and versioned as named artifacts in the project. Applications reference prompts by name and load the latest approved version at inference time, rather than having prompt text hard-coded in the application deployment artifact. This decoupling means updating a prompt is a content operation - not a code deployment - so applications automatically pick up the new prompt without any redeployment.
Microsoft Learn Reference Topic: Prompt management in Microsoft Azure AI Foundry - Git integration and dynamic prompt versioning