Microsoft AI-300 Value Pack (Frequently Bought Together)

Correct Answer:

Explanation:
The command deploys the resources into an existing resource group named rg-foundry-dev: Yes The system-assigned managed identity defined in the template will automatically be inherited by all Microsoft Foundry projects: No To deploy this template to a different subscription, you must modify the Bicep file to include a subscriptionId parameter: No The first statement is Yes . The command uses az deployment group create --resource-group rg-foundry-dev, which performs an Azure Resource Manager deployment at resource-group scope . Microsoft documents that the target resource group must already exist; if it does not, it must be created before running the resource- group deployment.
The second statement is No . The Bicep declaration assigns a system-assigned managed identity to the Foundry resource itself . A Microsoft Foundry project is a child resource and can have its own managed identity . Microsoft explicitly shows project creation with " identity " : { " type " : " SystemAssigned " } and separately discusses assigning permissions to a project ' s managed identity. Therefore, the parent ' s system- assigned identity is not automatically inherited as the identity of every project.
The third statement is No . Because targetScope = ' resourceGroup ' , the same Bicep template can be deployed to a resource group in another subscription without adding a subscriptionId parameter. Azure CLI supports the global --subscription argument, or the active subscription can be changed with az account set.

Correct Answer:

Explanation:

Correct Answer:

Explanation:
Detect when the system is slow at returning output: Latency
Identify when the system cannot sustain expected request volume: Throughput Measure the duration of handling a request: Response time Latency measures delay experienced while waiting for model output and is therefore the appropriate metric for identifying degradation in perceived responsiveness. Microsoft describes latency as the time required to obtain a response from the model and exposes metrics such as Time to Response/Time to First Token and Time Between Tokens for generative AI workloads. An increase indicates that users are waiting longer for output to begin or continue.
Throughput represents the amount of workload the system can process over a unit of time. Microsoft describes system-level throughput in terms such as requests per minute and tokens per minute. Consequently, throughput is the correct metric when determining whether a deployment can sustain the required request volume as demand increases.
Response time represents the overall duration required to handle an individual request. It is appropriate for measuring end-to-end request processing and validating request-duration SLOs. Microsoft specifically includes latency, throughput, and response times among the performance metrics candidates are expected to monitor for generative AI applications.
Concurrency measures simultaneous active requests and can influence capacity and latency, but none of these requirements directly asks for simultaneous-request count.
Study Guide Reference: Implement generative AI quality assurance and observability - continuous monitoring, latency, throughput, response times, production troubleshooting, and SLO monitoring.

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

Correct Answer: B  🗳️

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