Hard AI-103 practice questions
Challenge — multi-step scenarios, trade-offs, and subtle distinctions. 13 hard questions available — no sign-up, always free.
You are building a RAG ingestion pipeline for a library of engineering white papers that contain descriptive charts and diagrams embedded within the text. Your grounding requirement is that when an agent answers a question about a chart, the retrieved chunk must include a natural-language description of what the chart depicts (trends, axes, labeled regions) rather than just the surrounding paragraph text, so the model can reason about the visual without receiving the raw image at query time. You are using Azure AI Content Understanding to produce the grounded representation. Which configuration produces the required output for downstream reasoning?
A financial services team uses Azure AI Content Understanding to extract line items from vendor invoices. They need the extracted vendor names and account codes validated against an authoritative master list of approved vendors so that the analyzer can flag entries that do not match a known record. Which capability should they configure to achieve this validation during extraction?
You are building a semiautonomous Azure AI Foundry agent for an e-commerce operations team. The agent uses a custom function tool named submit_refund that calls an internal payments API to issue customer refunds. During load testing you notice that transient network timeouts occasionally cause the agent's runtime to retry the tool call, resulting in some customers being refunded twice. You must prevent duplicate refunds without disabling automatic retries. What is the most effective approach?
You are building an Azure AI Foundry agent that must call your company's internal Orders REST API, which is protected by OAuth 2.0 client-credentials flow against Microsoft Entra ID. You register the API as an OpenAPI-specified tool for the agent. When configuring the tool, you must ensure the agent can authenticate to the API without embedding long-lived secrets in the tool definition and while respecting the API's token audience requirements. Which authentication configuration should you use for the OpenAPI tool?
A financial services team is deploying an Azure AI Foundry agent that can execute stock trades through a registered tool. Regulatory policy requires that any trade exceeding $10,000 be reviewed by a licensed broker before execution, while smaller trades and read-only balance inquiries may proceed automatically to maintain responsiveness. Which oversight configuration best satisfies these requirements?
You are building an Azure AI Foundry agent for a travel-booking assistant. The agent has three registered tools: get_user_preferences (reads a profile store), search_flights (queries an airline API using the retrieved preferences), and check_weather (queries a public weather API for the destination). During a single turn the agent must produce a recommendation that uses flight results filtered by user preferences, while weather information is independent. You want to minimize end-to-end latency without producing incorrect results. How should you design the tool-calling behavior for this turn?
A financial services company is designing an Azure AI Foundry solution that must serve customers in the European Union. Legal compliance requires that all customer data used for inference and all model processing remain within EU borders. The team also needs guaranteed capacity for a GPT-4o model deployment during predictable business-hour peaks, with no cross-region data transfer under any circumstances. Which combination of choices best satisfies these requirements?
A financial services team builds a loan pre-qualification assistant in Azure AI Foundry. Certain decisions—such as rejecting applicants below a legally mandated minimum credit score—must be enforced with 100% consistency and be fully auditable, while free-form explanation and customer Q&A should be handled conversationally. The team wants to combine an LLM with a deterministic rules engine. Which orchestration approach best satisfies both the compliance and conversational requirements?
A financial services team is building a customer support agent in Azure AI Foundry. The agent must answer questions using a knowledge base of 40,000 policy documents that are updated weekly, and it must consistently adopt the company's formal brand tone and a specific structured response format. The team wants to minimize ongoing maintenance overhead while keeping answers accurate against the latest documents. Which approach should they adopt?
You are building a customer support solution in Azure AI Foundry that requires several specialized agents (billing, technical, and escalation) to collaborate. The orchestration logic is complex: agents must dynamically decide which peer to invoke next based on runtime conversation state, and the flow cannot be predetermined as a fixed sequence. You want to author this coordination logic in code using an open-source multi-agent framework that Microsoft has consolidated its agentic development around, with native integration into Foundry. Which approach should you choose?
You are orchestrating a multi-agent solution in Azure AI Foundry for an insurance claims workflow. A 'Triage' agent classifies incoming claims and must pass the extracted claim number, policy ID, and damage category to a downstream 'Assessment' agent that runs in a separate thread. The Assessment agent frequently fails because it receives a natural-language summary rather than the exact structured field values, causing lookup errors. What is the most reliable way to transfer this data between the agents?
You are building a RAG ingestion pipeline in Azure AI Search for a corpus of long technical manuals (200+ pages each). Retrieval must return small, focused passages for precise grounding, but the agent needs enough surrounding context to reason accurately. During ingestion you must split each document into fine-grained chunks for embedding while still being able to hydrate the full parent section into the agent prompt at query time. Which indexing approach in the skillset should you configure?
You are building an Azure AI Search RAG ingestion pipeline for a library of long technical manuals. A skillset splits each manual into text chunks and generates vector embeddings per chunk. You need the index to store one document per chunk for fine-grained retrieval, while also preserving the parent manual's metadata (title, product line, revision date) so it can be returned as grounding context. Which indexer configuration achieves this?