support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  1. Home
  2. Exams
  3. Microsoft
  4. AI-103

Microsoft AI-103 Exam Prep
Developing AI Apps and Agents on Azure (Page 13 )

Updated On: 16-Sep-2026
Page 5 of 28
PDF with 161 Questions

You have a Microsoft Foundry project named Project1 that contains an agent. The agent uses an OpenAPI 3.0 specification to call an external weather service.
The weather service requires a key to be passed in an HTTP header. The key value is stored as a connection in Project1.
You need to ensure that the key value from the connection is included automatically whenever the OpenAPI tool is invoked.
What should you configure in the OpenAPI specification?

  1. a header parameter defined for each operation
  2. an Azure Key Vault connection
  3. an API key security scheme
  4. a Bearer token security scheme

Answer(s): C

Explanation:

To ensure Microsoft Foundry automatically injects the API key from your project connection whenever the OpenAPI tool is invoked, your OpenAPI 3.0 specification must explicitly include a securitySchemes component mapping to the exact header name, and a global or operation-level security requirement referencing that scheme.The orchestrator matches the name field in the specification against the key stored inside your project's custom connection.
1. Required OpenAPI 3.0 Configuration You must add both the components.securitySchemes block and the security block to your specification file:
openapi: 3.0.0 info: title: External Weather Service version: 1.0.0 paths: /weather: get: operationId: getWeather responses: '200': description: Successful weather retrieval
# 1. Define the security scheme in the components section components: *-> securitySchemes: weatherApiKey: # Arbitrary logical identifier for this scheme *-> type: apiKey in: header name: X-Weather-API-Key # MUST match the "key" name configured in your Foundry Connection
# 2. Apply the security requirement globally (or inside individual operations) security: - weatherApiKey: [] # Instructs Foundry to enforce this scheme on the API requests in: header: Explicitly instructs the Foundry proxy layer to attach the credential value to the HTTP request headers (rather than as a query parameter).name: This string value is the exact HTTP header key (e.g., X-Weather-API-Key or Authorization). Crucially, this value must identically match the "Key" property given to the secret in your Microsoft Foundry Custom Connection.
security: Actively triggers the authentication workflow for the tool's endpoints. Without this block, Microsoft Foundry treats the API call as anonymous and strips out connection values.


Reference:

https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/openapi



You have a Microsoft Foundry project that serves a high-volume chat app.
Most requests are simple FAQs, but some require advanced reasoning.
You need to reduce costs and latency for common queries, without degrading the quality of the responses to complex questions.
What should you do?

  1. Route all the requests to a smaller model.
  2. Use a model cascade that routes the requests to different models.
  3. Increase the value of the max_tokens parameter for all the requests.
  4. Route all the requests to the most capable model.

Answer(s): B

Explanation:

One should absolutely use a model cascade to route requests to different models based on complexity. This architectural pattern is highly effective for high-volume chat applications because it directly addresses the trade-off between operational cost, API latency, and response quality.
Using a model cascade router ensures that your high-volume Microsoft Foundry application scales efficiently by reserving expensive computational power exclusively for queries that actually require advanced cognitive processing.
Note: 1. Analyze Request Complexity Implement a lightweight intent classifier or routing layer at the entry point of your Microsoft Foundry project. This router quickly inspects incoming user prompts using basic heuristic keyword matching, semantic embeddings, or a highly optimized, fast model (like Phi-3 or GPT-4o-mini) to categorize the query as either a "Simple FAQ" or a "Complex Reasoning" request.
2. Route to the Optimal TierTier 1 (Fast & Cheap): Route standard, predictable FAQ requests to a smaller, cost-effective model or a local cache/vector database lookup. This keeps latency in milliseconds and drastically lowers token costs.
Tier 2 (Advanced Reasoning): Route multi-step logic, coding, or highly contextual queries to a frontier model (like GPT-4o).
3. Implement Fallback LogicDesign the cascade to be dynamic. If the smaller Tier 1 model generates a response with low confidence, or if the user asks a follow-up question that invalidates the simple FAQ status, seamlessly upgrade the conversation loop to the Tier 2 model.


Reference:

https://medium.com/@sujathamudadla1213/what-is-the-primary-purpose-of-a-model-cascade-in-machine-learning-0b145a7bc6e2



HOTSPOT (Drag and Drop is not supported)
You have a Microsoft Foundry project that contains an internal Q&A agent.
Users report the following issues when they ask the agent questions:
-An increase in the following response: “No relevant information found”
-Periodic HTTP 429 rate limit exceeded errors during peak hours
You need to identify whether each issue is caused by model unavailability, resource limits, or inference failures.
What should you do? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Model Availability rate and Provisioned Utilization. Metrics to enable
To diagnose these issues, the Model Availability rate and Provisioned Utilization metrics are needed.
Problem 1 ("No relevant information found"): This points to an inference failure (RAG hallucination or retrieval gap), which is often caused by the model hallucinating when it is missing contextual grounding.
Problem 2 (HTTP 429 rate limit exceeded): This indicates resource limits. Monitoring provisioned utilization helps identify if your allocated capacity is simply maxing out during peak hours.
Box 2: RequestResponse Diagnostic log to collect
To isolate whether your issues are caused by model unavailability, resource limits, or inference failures, you need to collect and analyze the RequestResponse diagnostic log category (also referred to as RequestResponseLogs).
While your enabled metrics provide high-level context (e.g., Model Availability highlights backend service drops and Provisioned Utilization highlights capacity strain), they do not reveal per-request details. The RequestResponse log records the exact HTTP status codes, error codes, and backend latency for every transaction.


Reference:

https://learn.microsoft.com/en-us/azure/foundry/foundry-models/how-to/monitor-models



You have a Microsoft Foundry project that contains a high-traffic agent.
After a recent update, operational costs increase significantly.
Monitoring confirms that the volume of user traffic to the agent remains unchanged.
You suspect that changes to the request or response characteristics are causing the increase. You need to identify whether the additional costs are driven by the model input size, the model output size, or expanded tool usage.
Which observability capability should you use?

  1. latency
  2. evaluation metrics
  3. run success rate
  4. token usage

Answer(s): D

Explanation:

To identify whether model input, model output, or expanded tool usage is driving the cost spike, you should focus on token usage.
Granular tracking of token usage breaks down the costs directly: Input vs. Output Tokens: Tracing token usage isolates whether the user prompt (input) has grown or if the model is generating longer, more expensive responses (output).
Tool Calling: Expanded tool usage consumes extra tokens each time the agent schema processes an execution loop, which will clearly reflect as inflated token counts.


Reference:

https://www.mindstudio.ai/blog/subtraction-principle-agent-harness-optimization



HOTSPOT (Drag and Drop is not supported)
You have a Microsoft Foundry project that contains an agent.
The agent uses tools to retrieve internal content and call external APIs. The agent is configured to let the model decide when to call the tools.
You need to publish the agent for a compliance workflow. The solution must meet the following requirements:
-Each workflow run must include a retrieval step before generating a response.
-Tool calls must authenticate by using the published agent’s own identity.
-Tool access must use an identity isolated from other project resources.
-Tool access must use support audit tracing.
What should you do? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: required Tool choice
To comply with your strict workflow and compliance requirements, you set tool_choice parameter required.
Setting tool_choice to required mathematically forces the model to invoke at least one tool (your internal retrieval mechanism) during the turn before it can finalize its answer.
Incorrect [Not auto] Setting tool_choice to auto hands over absolute decision-making power to the underlying foundational model. If the model determines it already "knows" the answer from its training data, it can skip the retrieval step entirely.
Box 2: Using a distinct agent identity bound to the client application Configure the tool to authenticate by
Restriction: Use Published Agent's Own Identity Map the agent to a Microsoft Entra Agent Identity. This gives the published agent its own distinct service principal identity within Entra ID, ensuring it does not inherit or use user tokens or secondary administrative keys.
Restriction: Identity Isolated from Project Resources Rather than sharing the default Microsoft Foundry project managed identity (project-mi), assign a unique User-Assigned Managed Identity exclusively to this agent instance. Limit its role-based access control (RBAC) scopes solely to the specific retrieval indexes and the target external API endpoints.


Reference:

https://learn.microsoft.com/en-us/azure/foundry/agents/concepts/tool-catalog



  PDF
Viewing page 13 of 28
Viewing questions 61 - 65 out of 161 questions


Post your Comments and Discuss Microsoft AI-103 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!