Free Practice Questions for Microsoft AB-731 Exam

Grounding is an AI solution pattern used to improve response quality by ensuring the model’s output is based on trusted, relevant information provided at inference time , rather than relying only on what the model “remembers” from training. Therefore, C is correct : grounding anchors responses in specific data sources .

In practical deployments, grounding commonly uses retrieval (often called Retrieval Augmented Generation, or RAG) where the system first finds relevant content from approved sources—such as internal policy documents, product documentation, knowledge bases, or databases—and then includes that content in the prompt context sent to the model. Microsoft’s guidance describes grounding data as information supplied at inference time to help responses become more accurate and relevant because the model is guided by authoritative, up-to-date content that may not have been part of original training.

The other options do not define grounding. A relates to inclusion practices and diversity considerations, which are important for responsible AI but are not what grounding means. B describes transparency/explainability concepts. D relates to model evaluation/communication of limitations. Grounding is specifically about tying outputs to known sources , which reduces hallucinations and improves business trust in the generated responses.

For scanned invoices, the requirement is structured field extraction (invoice number/ID, vendor, totals) from document images or PDFs at scale. The best fit is Azure Document Intelligence because it is purpose-built for document processing and provides prebuilt invoice models that combine OCR with layout/structure understanding to extract common invoice fields into a structured output. Microsoft’s invoice model is explicitly designed to analyze invoices (including scanned images) and return key fields and line items in structured form, which directly maps to this scenario.

Azure Vision (B) can perform OCR and basic image analysis, but OCR alone typically returns text without robust invoice-specific field interpretation (e.g., reliably identifying “Invoice ID” vs. “Order ID,” totals vs. subtotals, vendor vs. ship-to). Document Intelligence is optimized for advanced document structure extraction and is therefore the “best” single recommendation.

Azure AI Search (C) focuses on indexing and retrieval/knowledge mining across a corpus; it’s not the primary service for extracting invoice fields for downstream processing. Azure Machine Learning (D) could be used to build a custom model, but that adds cost and time compared with a prebuilt invoice extractor designed for this document type.

Provisioned (PTUs)

For continuous, large-scale workloads, the key needs are predictable throughput, consistent latency, and cost/performance stability . Azure OpenAI Provisioned Throughput Units (PTUs) are designed for this scenario because you reserve model capacity to meet sustained demand. This reduces the risk of variability that can occur with purely on-demand usage during peak periods and provides a more predictable operating model when the workload is always “on” and high volume.

Standard (On-Demand) is best when usage is variable or you’re starting small (PoCs, pilots, spiky workloads), because it is flexible pay-as-you-go but can be less predictable at sustained scale. Batch API is optimized for asynchronous, non-interactive processing where you can tolerate delayed results (for example, large offline summarization jobs), not for always-on, real-time interactions at scale.

Therefore, for continuous high-volume production workloads, Provisioned (PTUs) is the best pricing model choice.