一番質高い AI-300 試験問題集

正解：B  🗳️

正解：A  🗳️

解説: (Tech4Exam メンバーにのみ表示されます)

正解：

Explanation:
Load the model when the service starts: init()
Use the model to score new data: run()
Azure Machine Learning scoring scripts for online endpoints use two required entry-point functions: init() and run() . Microsoft explicitly states that the scoring script specified for an online deployment must contain both functions.
The init() function is invoked when the inference container is initialized or started, typically immediately after a deployment is created or updated. It is intended for one-time initialization tasks such as locating the registered model through AZUREML_MODEL_DIR, deserializing the model, and storing it in memory.
Loading the model once during initialization avoids repeatedly loading it for every inference request, which reduces latency and processing overhead.
The run() function is called each time the endpoint receives an inference request. It accepts the incoming request data, transforms or parses the input as required, invokes the loaded model ' s prediction logic, and returns the scoring result. Microsoft describes run() as the function that performs the actual scoring or prediction for each endpoint invocation.
main(), score(), and predict() may exist inside application code or model libraries, but they are not the required Azure Machine Learning scoring-script entry points.

正解：

Explanation:
Domain specialization: Supervised fine-tuning
Poor response accuracy of a RAG-based solution: Apply prompt engineering For domain specialization , Supervised Fine-Tuning (SFT) is the correct first strategy. Microsoft describes SFT as the foundational fine-tuning technique for training a model from labeled input-output pairs , and specifically identifies domain specialization as one of its principal use cases. Microsoft also recommends starting with SFT for most customization projects because it supports task specialization, instruction following, style, and domain-specific behavior. Fabrikam already possesses evaluation data containing input- output pairs, which aligns directly with the SFT data model.
For poor RAG response accuracy , the first action is prompt engineering . The case explicitly requires advanced fine-tuning only when prompt engineering is insufficient. In a RAG system, prompt engineering determines how the model interprets retrieved context, constrains answers to grounding information, handles missing evidence, and formats responses. Microsoft notes that inadequate RAG prompting can produce false or incomplete answers even when retrieval returns appropriate content.
DPO is primarily appropriate for alignment using preferred versus non-preferred responses, while RFT targets complex reward-based reasoning optimization. Neither is the initial technique for domain specialization in this requirement.
Study Guide Reference: Optimize generative AI systems and model performance - prompt engineering, RAG optimization, supervised fine-tuning, preference optimization, and model customization strategy.

正解：

Explanation:
Correct sequence:
* Install the Foundry SDK project client locally.
* Configure safety evaluators.
* Submit an evaluation to the Microsoft Foundry project in the cloud.
The first step is to install and configure the Microsoft Foundry SDK project client . Microsoft documents the Foundry project client as the programmatic entry point for authenticating to a Foundry project and accessing its evaluation capabilities. The client typically uses DefaultAzureCredential, avoiding embedded credentials while enabling access to project resources.
Next, configure the safety evaluators that correspond to the risks that must be measured. Microsoft Foundry provides built-in safety evaluators for categories including Violence, Sexual content, Self-harm, and Hate
/Unfairness . These evaluators analyze generated responses and return structured safety assessments rather than relying on subjective manual review.
Finally, submit the evaluation to the Microsoft Foundry project in the cloud . Current Foundry evaluation workflows define the evaluator configuration, create an evaluation, and start an evaluation run in the project.
Results are persisted in Foundry for comparison, auditing, and CI/CD quality gates.
Uploading evaluation data is unnecessary because the scenario explicitly states that the dataset is already registered . Microsoft documentation specifically instructs users to skip dataset upload when a registered dataset already exists. Free-form text upload is also inappropriate because structured evaluation datasets use supported schemas such as JSONL or CSV.
Study Guide Reference: Implement generative AI quality assurance and observability - Foundry evaluations, safety evaluators, evaluation datasets, cloud evaluation runs, and harmful-content measurement.