Diagnose Foundry Agent Issues: Model Availability, Limits, and Inference
HOTSPOT
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.
Community Insight
This question tests your ability to match specific error symptoms (HTTP 429 vs. logical failure) to the appropriate Foundry telemetry metrics and logs for root cause analysis.
Learn to map Microsoft Foundry agent errors like HTTP 429 and 'No relevant information found' to the correct diagnostic logs. This page explains how to distinguish between model unavailability, resource limits, and inference failures using specific monitoring tools.
Learners often confuse Request/Response logs with Trace logs or fail to recognize that HTTP 429 is a direct indicator of resource throttling rather than a model availability issue.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct mapping relies on understanding what each telemetry source captures in Microsoft Foundry. For 'Periodic HTTP 429 rate limit exceeded errors', the correct selection is Resource Limits (specifically Provisioned Utilization), as HTTP 429 is the standard status code for rate limiting/throttling when capacity is exhausted. For 'An increase in... “No relevant information found”', this is a logical outcome where the model processed the request but returned an empty or null result due to retrieval gaps; this is best investigated via Request/Response Logs to see the exact input/output and grounding results. Model Availability would typically manifest as 503 errors or timeouts, not 429s or empty retrievals.Why Other Candidate Answers Are Wrong
Selecting 'Model Availability' for HTTP 429 is incorrect because 429 indicates the service is available but overloaded, whereas availability issues imply the service is down. Selecting 'Trace' for the 'No relevant information found' issue is less precise than Request/Response logs for identifying why a specific Q&A response was empty, as traces are better for latency and span-level debugging rather than content logic.Community Comment Notes
As Amelia233 noted, matching HTTP 429 to 'Provisioned Utilization' is key for resource limits. Another user suggested 'trace' for diagnostics, but trace is more granular; for high-level symptom mapping like 'No info found', request/response data is the primary diagnostic tool for content accuracy.Exam Strategy
Always associate HTTP 429 with 'Rate Limits' or 'Throttling' in Azure/AI contexts. Differentiate between 'Availability' (is the API up?) and 'Capacity' (is the API too slow/busy?). Use Request/Response logs for content/logic errors and Metrics for infrastructure/limit errors.
Frequently Asked Questions
What does HTTP 429 mean in Microsoft Foundry?
HTTP 429 means 'Too Many Requests', indicating you have hit a rate limit or resource cap (Provisioned Utilization), not that the model is unavailable.
How do I debug 'No relevant information found' in Foundry?
Check the Request/Response logs to see if the retrieval step failed to find documents or if the model simply chose not to generate an answer.
Related Analysis
Practice All AI-103 Questions
Access 88 questions with complete answers and detailed explanations.
View Full AI-103 Practice Test →