Courseiva

CCNA Information Extraction Questions

55 questions · Information Extraction · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
MCQeasy

What is the primary purpose of the 'selection marks' detection in the layout model?

A.To OCR printed text
B.To detect checkboxes and radio buttons
C.To identify table borders
D.To find handwritten signatures
AnswerB

Selection marks detection identifies the state of boxes and radio buttons in documents, returning whether each is selected or unselected. This lets the layout model expose form-field choices as structured data rather than plain text, distinct from general OCR of characters.

Why this answer

Selection marks in Azure AI Document Intelligence's layout model detect and extract checkboxes and radio buttons (and their selected/unselected state) from documents. The model returns each mark with a confidence score and a state of 'selected' or 'unselected', which is essential for processing forms, surveys, and questionnaires. OCR, table borders, and signatures are handled by other capabilities.

Exam trap

AI-103 often tests the distinction between layout model sub-capabilities, tempting candidates to confuse selection marks with OCR text extraction or table detection — the key is that selection marks specifically return checkbox/radio state.

How to eliminate wrong answers

Option A is wrong because OCR of printed text is the general read/OCR capability, not the specific purpose of selection marks. Option C is wrong because table border detection is part of the layout model's table extraction, not selection marks. Option D is wrong because handwritten signature detection is a separate capability (and often custom-model territory), not what selection marks provide.

Practice this question →
2
MCQhard

You are automating document processing. You want to trigger a workflow only after a Document Intelligence operation finishes. What is the standard way to implement this?

A.Poll the 'operation-location' URL
B.Use a fixed-delay thread sleep
C.Use a WebSocket
D.Wait for a push notification
AnswerA

Document Intelligence returns an operation-location URL when a long-running analysis begins. Polling that URL is the standard completion mechanism, since the service exposes no push callback. Polling satisfies the stem's requirement to trigger the workflow only after the operation finishes.

Why this answer

The Document Intelligence analyze operation is asynchronous: it returns a 202 Accepted response with an 'Operation-Location' header containing a URL. The standard way to detect completion is to poll that URL until the status field returns 'succeeded' or 'failed'. This is the documented pattern for all long-running Document Intelligence operations.

Exam trap

The trap is assuming the service pushes a notification or that a simple sleep suffices — candidates may overlook that Document Intelligence uses the standard long-running operation polling pattern.

How to eliminate wrong answers

Option B (Use a fixed-delay thread sleep) is wrong because a fixed sleep does not guarantee the operation has finished and can either waste time or proceed prematurely. Option C (Use a WebSocket) is wrong because Document Intelligence does not expose a WebSocket interface for operation completion. Option D (Wait for a push notification) is wrong because the service does not push completion events to the client — the client must poll the operation-location URL.

Practice this question →
3
MCQmedium

You are developing a custom extraction model using Azure AI Document Intelligence Studio. Your training dataset consists of multi-page invoices with varying structures, and some fields appear only on the final page. How should you structure your tagging configuration?

A.Create a separate custom model for the final page and chain them using an orchestration model.
B.Split every multi-page invoice into individual single-page documents before uploading.
C.Define all late-appearing fields as optional metadata parameters in the training configuration JSON file.
D.Tag the fields on whatever page they appear across the sample documents in Document Intelligence Studio.
AnswerD

Tagging each field on the page where it actually occurs lets the custom neural model learn page-position context, which matters because some fields appear only on the final page of these variably structured invoices. Tagging every field on page one would misrepresent that layout and degrade extraction accuracy.

Why this answer

In Document Intelligence Studio, you tag fields on the pages where they actually appear across your sample documents — the labeling tool is page-aware and stores the page number alongside each field's bounding region. This lets the trained model learn that, for example, 'Total' appears on page 1 in some invoices and page 3 in others. You do not need to split documents or build orchestration models just because fields appear on different pages.

Exam trap

AI-103 often tests whether candidates over-engineer solutions — the trap is assuming multi-page documents with late-appearing fields require splitting or orchestration, when the Studio natively supports tagging across pages in one model.

How to eliminate wrong answers

Option A is wrong because chaining a separate final-page model via orchestration adds unnecessary complexity and cost; a single custom model can learn fields across all pages of a multi-page document. Option B is wrong because splitting multi-page invoices into single-page files destroys the document context the model uses to associate fields (e.g., matching a line item to its invoice header) and multiplies labeling effort. Option C is wrong because Document Intelligence custom models do not support declaring fields as 'optional metadata parameters' in a JSON config — fields are defined by tagging them in the Studio UI, and the model learns optionality from the training data itself.

Practice this question →
4
Multi-Selecthard

Which THREE fields are typically returned by the prebuilt-receipt model?

Select 3 answers
A.MerchantName
B.EmployeeID
C.TransactionDate
D.PatientName
E.Total
AnswersA, C, E

MerchantName is one of the three fields the prebuilt-receipt model extracts, satisfying the stem's requirement for typical receipt output. The model returns merchant identification alongside transaction totals and line items, drawing the vendor name directly from the receipt header. This field appears in the model's default schema without custom training or configuration.

Why this answer

The prebuilt-receipt model in Azure AI Document Intelligence is designed to extract common receipt fields, and MerchantName (A) is one of them because it identifies the vendor or business that issued the receipt. TransactionDate (C) is also returned since the model recognizes the date the purchase occurred, which is a standard receipt field. Total (E) is included as the model extracts the final amount paid, a core field on virtually every receipt.

EmployeeID (B) is not a standard receipt field and is not returned by this model, as it relates to internal staff identifiers rather than receipt data. PatientName (D) is specific to healthcare or medical documents and is not part of the prebuilt-receipt schema.

Exam trap

AI-103 often tests whether candidates can distinguish fields returned by prebuilt-receipt versus other prebuilt models like prebuilt-idDocument or prebuilt-healthInsuranceCard, so mixing up domain-specific fields is a common trap.

Practice this question →
5
MCQmedium

You need to extract data from a document that includes handwritten signatures and printed text. Which capability is required?

A.Object Detection
B.Handwritten OCR (Read)
C.Custom Template model
D.Form Recognizer 2.0 API
AnswerB

Handwritten OCR (Read) satisfies the stem's requirement to extract both handwritten signatures and printed text, since the Read model handles mixed handwriting and print within one document. Standard printed-text OCR alone cannot recognise the cursive strokes of signatures, so Read's handwriting support is the specific capability needed here.

Why this answer

Handwritten OCR (Read) is the Azure AI Vision capability that recognizes both printed and handwritten text in documents and images, making it the required feature when signatures and handwriting are present. The Read API returns extracted text with bounding boxes and confidence, supporting mixed print and handwriting. This directly satisfies the requirement to extract data from documents containing handwritten signatures and printed text.

Exam trap

AI-103 often tests the confusion between OCR/Read (text recognition including handwriting) and custom extraction models, causing candidates to pick a custom template model when the question is specifically about recognizing handwritten text.

How to eliminate wrong answers

Option A is wrong because Object Detection identifies and localizes objects (e.g., cars, people) in images; it does not perform text recognition or handwriting extraction. Option C is wrong because a Custom Template model extracts structured fields from fixed-layout forms using labeled examples, but it relies on the underlying OCR for text recognition and does not by itself provide handwriting recognition as a distinct capability. Option D is wrong because Form Recognizer 2.0 API is a legacy version with limited handwriting support and has been superseded by newer Document Intelligence models; it is not the correct capability to cite for handwritten OCR.

Practice this question →
6
MCQeasy

Which tool provides a graphical user interface for labeling documents for custom models?

A.Azure CLI
B.Azure Storage Explorer
C.Document Intelligence Studio
D.Visual Studio Code
AnswerC

Document Intelligence Studio provides a graphical interface for labelling documents, training custom extraction models, and testing them without code. This satisfies the stem's requirement for a GUI labelling tool, unlike SDKs or REST APIs that require programmatic work.

Why this answer

Document Intelligence Studio is the web-based graphical interface provided by Azure that lets you visually label documents, define fields, train custom models, and test them against sample files. It is specifically designed for the labeling and project-management workflow of custom extraction and custom classification models, so it is the correct answer for a GUI-based labeling tool.

Exam trap

The trap here is confusing general-purpose Azure tools (Azure CLI, Storage Explorer, VS Code) with the purpose-built Document Intelligence Studio — candidates who have not used the Studio may assume any Azure GUI can label documents, but only Document Intelligence Studio provides the field-labeling and training workflow.

How to eliminate wrong answers

Option A is wrong because Azure CLI is a command-line tool for managing Azure resources — it has no graphical labeling interface for documents. Option B is wrong because Azure Storage Explorer is a GUI for browsing and managing blobs, queues, and tables in storage accounts; it can upload training documents but cannot label fields or train Document Intelligence models. Option D is wrong because Visual Studio Code is a code editor — while extensions exist for Azure, it does not provide the document-labeling GUI that Document Intelligence Studio offers.

Practice this question →
7
MCQeasy

You are developing a solution that must extract structured fields such as vendor name, invoice total, and due date from standard supplier invoices. The invoices come from many vendors but follow common invoice layouts. You want the fastest path to production without building or training a model. Which Azure AI Document Intelligence capability should you use?

A.A custom neural model trained on your invoice samples
B.A custom template model trained on your invoice samples
C.The prebuilt read model with a custom post-processing parser
D.The prebuilt invoice model
AnswerD

The prebuilt invoice model is purpose-built to extract common invoice fields such as vendor name, invoice total, due date, and line items without any training. It works across many vendors and standard layouts, matching the requirement for a fast, no-training path to production for supplier invoices.

Why this answer

The prebuilt invoice model is designed to extract common invoice fields across vendors without training. It satisfies the requirement for a fast, no-training deployment for standard supplier invoices. Custom models and the read model add effort or lack semantic understanding, so they do not meet the stated goal.

Exam trap

The trap here is reaching for a custom model by default when a prebuilt model already covers the required invoice fields.

Practice this question →
8
MCQmedium

You need to extract information from a business card. Which prebuilt model should you select?

A.prebuilt-businessCard
B.prebuilt-taxDocument
C.prebuilt-idDocument
D.prebuilt-layout
AnswerA

The prebuilt-businessCard model is trained specifically to extract fields such as contact names, job titles, company names, email addresses, and phone numbers from business card images, returning structured JSON. General document or receipt models lack these card-specific field schemas.

Why this answer

Azure AI Document Intelligence provides a dedicated prebuilt-businessCard model that extracts fields such as contact names, company, job title, phone numbers, email addresses, and website from business card images. Selecting this model avoids the need to train a custom model for a very common document type. It is the purpose-built choice for the scenario.

Exam trap

AI-103 often tests prebuilt model selection by name — candidates confuse prebuilt-idDocument (passports/licenses) with prebuilt-businessCard (contact info), or pick prebuilt-layout assuming it extracts semantic fields when it only returns raw structure.

How to eliminate wrong answers

Option B is wrong because prebuilt-taxDocument (e.g., prebuilt-tax.us.1040) is designed for US tax forms and returns IRS-specific fields like filer name, SSN, and income lines — irrelevant to business cards. Option C is wrong because prebuilt-idDocument extracts identity fields (name, date of birth, document number, expiration) from passports, driver's licenses, and similar IDs, not contact details from cards. Option D is wrong because prebuilt-layout only returns the general structure — text, tables, selection marks, and reading order — without semantic field extraction, so it would not identify 'Company' or 'Job Title' as named fields.

Practice this question →
9
MCQhard

You are configuring an Azure AI Document Intelligence container for deployment in an on-premises disconnected environment. Which environment variable is mandatory for the container to start successfully and report billing usage?

A.EULA=accept, billing=<billing-endpoint-uri>, apikey=<api-key>
B.AZURE_COGNITIVE_SERVICES_TENANT_ID
C.AZURE_AI_CONNECTOR_CONNECTION_STRING
D.DOCUMENT_INTELLIGENCE_MODEL_CACHE_DIR
AnswerA

Setting EULA=accept satisfies the licence-acceptance gate, while billing and apikey connect the container to Azure for usage metering. In a disconnected on-premises deployment these three variables are mandatory: without the billing endpoint and key, the container cannot start or report consumption to Azure.

Why this answer

Document Intelligence containers require three environment variables to start and report billing: EULA=accept (to acknowledge the license), billing=<billing-endpoint-uri> (the Azure endpoint that receives usage telemetry), and apikey=<api-key> (the key for that billing endpoint). Without all three, the container will not start or will not report usage, which is mandatory even in disconnected environments because billing telemetry is sent periodically when connectivity is available.

Exam trap

AI-103 often tests container prerequisites — the trap is forgetting that billing telemetry is still required for disconnected containers, or confusing container variables with unrelated Azure service connection strings.

How to eliminate wrong answers

Option B is wrong because AZURE_COGNITIVE_SERVICES_TENANT_ID is not a recognized environment variable for Document Intelligence containers — tenant ID is not part of the container billing configuration. Option C is wrong because AZURE_AI_CONNECTOR_CONNECTION_STRING is not a Document Intelligence container variable; it resembles a connector string from a different service and has no role here. Option D is wrong because DOCUMENT_INTELLIGENCE_MODEL_CACHE_DIR is not a mandatory variable — it may be used to specify a cache path for models, but the container starts without it and it does not affect billing.

Practice this question →
10
MCQmedium

You are training a custom template model in Azure AI Document Intelligence and notice that one of your key fields is consistently failing to extract on documents where the label text is vertically oriented. How should you address this issue?

A.Switch the model type from custom template to prebuilt read model.
B.Set the queryParameters property to 'orientation=vertical' in the training API request body.
C.Rotate the source PDF documents to landscape orientation prior to uploading them for training.
D.Re-examine and ensure all instances of the field across training samples are accurately tagged with correct bounding regions in Document Intelligence Studio.
AnswerD

Extraction failures on vertically oriented labels usually stem from inconsistent or missing bounding-region annotations in the training set. Retagging every occurrence of the field across samples with accurate bounding boxes gives the model the labelled examples it needs to learn that orientation.

Why this answer

The issue is likely due to inaccurate labeling of the field in the training samples, especially for vertically oriented text. Ensuring all instances of the field are accurately tagged with correct bounding regions in Document Intelligence Studio will help the model learn to extract the field regardless of orientation.

Exam trap

AI-103 often tests troubleshooting for custom model extraction failures; candidates might incorrectly think they can adjust API parameters or rotate documents, rather than ensuring training labels are accurate and consistent.

How to eliminate wrong answers

Option A is wrong because switching to prebuilt read model would not extract custom fields; it only provides OCR text. Option B is wrong because there is no queryParameters property for orientation in the training API; orientation is handled automatically by the model. Option C is wrong because rotating documents to landscape may not align with the actual orientation of the field and could introduce other issues; the model should be trained on the original orientation.

Practice this question →
11
Multi-Selecthard

When analyzing documents using Azure AI Document Intelligence, which THREE properties can be found within the returned JSON result object for an extracted table cell? (Choose THREE)

Select 3 answers
A.columnIndex
B.audioTranscript
C.sentimentScore
D.content
E.rowIndex
AnswersA, D, E

columnIndex is a zero-based integer giving the cell's horizontal position within the recognised table. It satisfies the stem's requirement by supplying the column coordinate in the JSON result, enabling reconstruction of the table grid alongside rowIndex and content.

Why this answer

In the Azure AI Document Intelligence analyze-result JSON, each table cell is represented with its grid position and text: option A (columnIndex) is correct because the zero-based column position of the cell within the table is returned as the columnIndex property, and option E (rowIndex) is correct because the zero-based row position is returned as the rowIndex property. Option D (content) is also correct because the cell's recognized text is returned in the content field (with spans and boundingRegions tying it to the source). Options B (audioTranscript) and C (sentimentScore) do not belong: audioTranscript relates to speech-to-text transcription and sentimentScore to language sentiment analysis, neither of which is part of the Document Intelligence table-cell schema.

Exam trap

The trap is confusing properties from other Azure AI services (like sentimentScore from Language, or audioTranscript from Speech) with Document Intelligence table cell properties; candidates must remember that Document Intelligence focuses on spatial and textual data.

Practice this question →
12
MCQeasy

You are configuring an Azure AI Document Intelligence prebuilt model to extract key-value pairs from standard invoices. Which API operation should your application call to process the document asynchronously?

A.POST /documentintelligence/documentModels/prebuilt-invoice:train?api-version=2024-02-29-preview
B.POST /documentintelligence/models/prebuilt-invoice/analyze?api-version=2024-02-29-preview
C.POST /formrecognizer/v2.1/prebuilt/invoice/analyze
D.POST /documentintelligence/documentModels/prebuilt-invoice:analyze?api-version=2024-02-29-preview
AnswerD

The `:analyze` operation submits the invoice and returns a 202 with an `Operation-Location` header, letting the application poll for results rather than block. This satisfies the asynchronous processing constraint, unlike synchronous `:analyze` variants or extraction endpoints that return results inline.

Why this answer

The correct async analyze operation for a prebuilt model in the 2024-02-29-preview API version is POST /documentintelligence/documentModels/{modelId}:analyze, where {modelId} is prebuilt-invoice. This returns a 202 Accepted with an Operation-Location header that your app polls until the analysis completes. The :analyze suffix is the long-running-operation (LRO) pattern used by Document Intelligence.

Exam trap

AI-103 often tests API path memorization — the trap is confusing the legacy /formrecognizer/ path with the current /documentintelligence/ path, or mixing up :train and :analyze action suffixes.

How to eliminate wrong answers

Option A is wrong because :train is the operation used to train a custom model, not to analyze a document with a prebuilt model. Option B is wrong because the path /documentintelligence/models/prebuilt-invoice/analyze is not the correct route — the service uses /documentModels/ and the :analyze suffix, not a slash-separated analyze segment. Option C is wrong because /formrecognizer/v2.1/prebuilt/invoice/analyze is the legacy Form Recognizer v2.1 endpoint, which is deprecated and does not match the 2024-02-29-preview API version specified in the question.

Practice this question →
13
MCQeasy

Which file format is NOT natively supported for training custom models in Azure AI Document Intelligence?

A.PDF
B.JPEG
C.BMP
D.DOCX
AnswerD

DOCX is not a native training format for custom models; Document Intelligence accepts PDF, JPEG, PNG, TIFF, BMP and text-based inputs. The question asks which format is unsupported, and DOCX requires conversion first, making it the exception among the listed options.

Why this answer

Azure AI Document Intelligence custom model training accepts PDF, JPEG, PNG, BMP, TIFF, and HEIF image formats, but DOCX (Word) files are not natively supported as training inputs. To train on Word content, you must first convert DOCX to PDF or render pages as images before uploading to the labeled training set. This is why DOCX is the correct answer to 'which is NOT natively supported.'

Exam trap

AI-103 often tests the assumption that 'any common document format works' — candidates pick PDF or JPEG thinking one of them is unsupported, missing that DOCX is the odd one out because Document Intelligence is image/PDF-centric.

How to eliminate wrong answers

Option A is wrong because PDF is one of the primary supported formats for custom model training (both text-based and scanned PDFs). Option B is wrong because JPEG is explicitly supported as an image input for custom template/neural model training. Option C is wrong because BMP is also a supported image format alongside PNG, TIFF, and HEIF.

Practice this question →
14
Multi-Selecteasy

Which THREE prebuilt document models are natively available out-of-the-box in Azure AI Document Intelligence? Each correct selection represents a valid prebuilt model.

Select 3 answers
A.Prebuilt W-2 tax form model
B.Prebuilt Invoice model
C.Prebuilt Video Sentiment analyzer
D.Prebuilt 3D CAD Model Analyzer
E.Prebuilt Receipt model
AnswersA, B, E

The prebuilt W-2 model is one of Document Intelligence's native US tax document models, requiring no training or custom labelling. It is available out-of-the-box via the prebuilt endpoint, satisfying the question's requirement for natively available models.

Why this answer

Azure AI Document Intelligence ships several prebuilt models for common business documents, and the prebuilt W-2 tax form model (A) is one of them, designed to extract US wage and tax statement fields such as wages, tips, and federal tax withheld. The prebuilt Invoice model (B) is also natively available and extracts key invoice fields like vendor name, invoice date, due date, line items, and amounts due. The prebuilt Receipt model (E) is likewise an out-of-the-box model that extracts merchant name, transaction date, line items, and totals from sales receipts.

Options C and D are not real Document Intelligence prebuilt models: Video Sentiment analyzer is not a document analysis capability, and 3D CAD Model Analyzer does not exist in the service's prebuilt model catalog.

Exam trap

AI-103 often tests the knowledge of which prebuilt models exist; candidates may confuse Document Intelligence capabilities with other Azure AI services like Language or Vision.

Practice this question →
15
MCQmedium

You are integrating Document Intelligence with Azure Blob Storage. You need to provide the model with a set of documents for training. How should you prepare the data?

A.Convert all files to CSV
B.Upload files and corresponding .labels.json and .ocr.json files
C.Store files in an Azure SQL database
D.Upload raw files only
AnswerB

Custom Document Intelligence models require each training document accompanied by a .labels.json file defining fields, plus an .ocr.json file providing the OCR layout. Uploading all three together to Blob Storage lets the model learn field positions and content.

Why this answer

To train a Document Intelligence model with documents in Azure Blob Storage, you must upload the documents along with their corresponding .labels.json and .ocr.json files. The .labels.json file contains the labeled data (field names and values), and the .ocr.json file contains the OCR results for the document. These files are generated using the Document Intelligence Studio or SDK and are required for training a custom model.

Exam trap

The trap is assuming that raw documents alone are sufficient for training; candidates must remember that labeled data and OCR files are required for custom extraction models.

How to eliminate wrong answers

Option A is wrong because converting files to CSV is not a supported format for Document Intelligence training; it requires the original document formats (PDF, JPEG, etc.) with accompanying JSON files. Option C is wrong because storing files in Azure SQL database is not a supported data source for Document Intelligence training; it requires Azure Blob Storage. Option D is wrong because uploading raw files only is insufficient; the labeled data and OCR files are necessary for supervised training.

Practice this question →
16
MCQmedium

Your application uses the Azure AI Document Intelligence Prebuilt Receipt model to process customer receipts. A receipt contains a custom tip amount that is not explicitly categorized by the default prebuilt schema. How should you extract this custom value?

A.Call the Azure OpenAI service directly with the raw image to guess the tip amount.
B.Pass a custom JSON schema parameter in the Prebuilt Receipt API request body to extend its extraction fields.
C.Modify the prebuilt receipt model schema directly in the Azure Portal to add a new required field.
D.Use the Prebuilt Layout model alongside custom regex rules or train a Custom model to capture the custom tip field.
AnswerD

The Prebuilt Receipt model returns only its fixed schema, so an uncategorised tip field cannot be extracted directly. Combining the Prebuilt Layout model with regex rules, or training a Custom model on labelled receipts, captures that field, satisfying the stem's requirement for the custom tip amount.

Why this answer

Prebuilt models expose a fixed schema and cannot be extended via request parameters or portal edits. To capture a field outside that schema (like a custom tip), you either use the Layout model to get raw text/lines and apply your own extraction logic (e.g., regex), or train a Custom extraction model with labeled samples that include the tip field. Option D describes both valid paths.

Exam trap

AI-103 often tests the misconception that prebuilt models can be 'extended' with a schema parameter or portal edit — in reality, prebuilt schemas are immutable and custom fields require Layout+logic or a Custom model.

How to eliminate wrong answers

Option A is wrong because calling Azure OpenAI directly bypasses Document Intelligence's structured extraction, introduces nondeterminism, and is not the supported mechanism for extending a prebuilt model's schema. Option B is wrong because the Prebuilt Receipt API does not accept a custom JSON schema parameter — prebuilt schemas are immutable and defined by Microsoft. Option C is wrong because prebuilt models cannot be modified in the Azure Portal; you cannot add required fields to a Microsoft-managed model.

Practice this question →
17
MCQeasy

What is the primary function of the 'layout' model in Azure AI Document Intelligence?

A.To translate text into different languages
B.To classify document types
C.To extract key-value pairs from receipts
D.To extract text, tables, and document structure
AnswerD

The layout model performs document structure analysis, returning extracted text, tables, selection marks and their bounding regions without applying domain-specific field schemas. It provides the general-purpose OCR and structural foundation that custom or prebuilt models build upon.

Why this answer

The layout model in Azure AI Document Intelligence extracts text, tables, selection marks, and document structure (such as paragraphs, headings, and reading order) without requiring a trained custom model. It is the general-purpose model for understanding a document's structural layout, making it the correct answer.

Exam trap

AI-103 often tests model-purpose confusion — candidates pick the receipt or custom model for key-value extraction, forgetting that the layout model is specifically about text, tables, and structural elements, not field extraction.

How to eliminate wrong answers

Option A is wrong because translation is handled by Azure AI Translator, not by any Document Intelligence model — Document Intelligence extracts content but does not translate it. Option B is wrong because document type classification is performed by the custom classification model (or the prebuilt/invoice models for specific types), not by the layout model, which does not categorize documents. Option C is wrong because key-value pair extraction from receipts is the job of the prebuilt receipt model (or a custom extraction model), whereas the layout model returns structure and content, not field-specific key-value pairs.

Practice this question →
18
Multi-Selectmedium

Which TWO metrics are reported by Document Intelligence Studio to evaluate model performance?

Select 2 answers
A.Recall
B.Throughput
C.Latencey
D.Precision
E.Confidence score
AnswersA, D

Recall measures the proportion of genuine labelled fields the model successfully extracted, directly quantifying missed detections. Document Intelligence Studio reports it alongside precision, so it satisfies the stem's requirement for a performance metric rather than a training setting or confidence threshold.

Why this answer

Document Intelligence Studio reports Recall (A) and Precision (D) as the two core metrics for evaluating a custom model's extraction quality. Recall measures the proportion of actual ground-truth field values that the model correctly extracted, indicating how many true items were found. Precision measures the proportion of the model's extracted values that are actually correct, indicating how many of its predictions were accurate.

These two metrics together characterize the model's accuracy on labeled test data in the Studio's evaluation view. Throughput (B) and Latency (C) are performance/operational characteristics rather than model accuracy metrics, and Confidence score (E) is a per-prediction value returned by the model, not an aggregate evaluation metric reported by the Studio.

Exam trap

AI-103 often tests the confusion between evaluation metrics (precision, recall, F1) and runtime attributes (confidence score, latency, throughput) — candidates pick confidence score because it sounds like a quality measure.

Practice this question →
19
MCQhard

You are processing large PDF documents. You only need the text in the table of contents. What is the most cost-effective approach?

A.Use a custom template model
B.Split the PDF into individual pages before uploading
C.Use the 'pages' query parameter
D.Process the entire PDF
AnswerC

Using the 'pages' query parameter restricts processing to the table of contents pages, so you are billed only for those pages rather than the entire PDF. This directly satisfies the cost-effectiveness constraint, since Azure AI Document Intelligence charges per page analysed.

Why this answer

The 'pages' query parameter in Azure AI Document Intelligence allows you to specify which pages to process, such as a single page or a range. If you only need the table of contents, you can identify the page number(s) containing it and pass the 'pages' parameter to limit processing to those pages. This reduces the number of pages processed, thereby lowering cost, since Document Intelligence pricing is based on the number of pages analyzed.

Exam trap

AI-103 often tests the misconception that you must process the entire document or split it manually, when in fact the 'pages' parameter provides a cost-effective way to target specific pages.

How to eliminate wrong answers

Option A is wrong because a custom template model is used for extracting structured data from forms with a consistent layout, not for selectively processing pages; it would still process the entire document unless combined with the 'pages' parameter. Option B is wrong because splitting the PDF into individual pages before uploading is a manual, inefficient approach that still requires processing each page separately and may not be cost-effective if you only need one page. Option D is wrong because processing the entire PDF incurs cost for all pages, which is not cost-effective when only the table of contents is needed.

Practice this question →
20
MCQmedium

You are migrating a custom extraction solution from a Custom Template model to a Custom Neural model in Azure AI Document Intelligence. What is a key advantage of choosing a Custom Neural model over a Custom Template model?

A.Custom Neural models can automatically generalize across documents with varying visual layouts and structures.
B.Custom Neural models only support English language documents.
C.Custom Neural models require zero training documents.
D.Custom Neural models do not support table extraction.
AnswerA

Custom Neural models learn layout-independent features from labelled samples, so they generalise across documents whose visual structure varies. Custom Template models instead rely on fixed positional anchors, which fail when layouts shift. This generalisation directly satisfies the migration scenario's need to handle varying layouts and structures.

Why this answer

Custom Neural models in Azure AI Document Intelligence use deep learning to learn the semantic and structural patterns of documents, enabling them to generalize across varying visual layouts, fonts, and formats. This is the key advantage over Custom Template models, which rely on fixed positional anchors and fail when layouts shift. Neural models are therefore preferred for documents with high variability.

Exam trap

AI-103 often tests the trade-off between Template and Neural models — candidates incorrectly assume Neural models need no training data or only work in English, when in fact they require labeled samples and support many languages.

How to eliminate wrong answers

Option B is wrong because Custom Neural models support multiple languages, not English only. Option C is wrong because Custom Neural models require a minimum of five labeled training documents (typically five samples per field), so they do not require zero training documents. Option D is wrong because Custom Neural models do support table extraction, including complex tables with merged cells.

Practice this question →
21
MCQhard

You are using Document Intelligence Studio to build a custom extraction model. You need to verify the model quality before deploying. Which metric is most critical?

A.Recall only
B.F1 Score
C.Precision only
D.Model ID
AnswerB

F1 score combines precision and recall into a single harmonic mean, making it the critical metric for verifying custom extraction model quality before deployment. It penalises both missed fields and false extractions, directly satisfying the stem's requirement to assess overall model accuracy across all extracted key-value pairs.

Why this answer

F1 Score is the harmonic mean of precision and recall, so it captures both false positives and false negatives in a single number. For custom extraction models where missing a field and misreading a field are both costly, F1 gives the most balanced view of overall model quality before deployment.

Exam trap

AI-103 often tests the misconception that a single metric (precision or recall) is sufficient — the exam expects you to recognize F1 as the balanced metric when both error types matter.

How to eliminate wrong answers

Option A is wrong because recall alone ignores precision — a model that extracts every possible token as a field would have high recall but terrible precision, and recall-only evaluation would hide that. Option C is wrong because precision alone ignores recall — a model that extracts only one very confident field correctly would score high precision while missing most fields. Option D is wrong because Model ID is just an identifier assigned by the service; it carries no quality information whatsoever.

Practice this question →
22
MCQhard

You are implementing cross-domain document extraction where incoming PDFs contain complex nested tables with merged cells. You need to extract these tables accurately into structured JSON. Which capability of Azure AI Document Intelligence should you rely on?

A.The documents collection, which converts tables into Markdown format automatically.
B.The keyValuePairs collection, which automatically flattens table rows into key-value pairs.
C.The styles collection, which identifies table gridlines through computer vision edge detection.
D.The tables collection in the analyze result, which provides rowSpan, colSpan, and cell bounding regions.
AnswerD

The tables collection returns each cell with rowSpan, colSpan and bounding regions, which is exactly what merged and nested table structures require. Those span attributes let you reconstruct the grid accurately into structured JSON rather than flattening merged cells.

Why this answer

The tables collection in the Document Intelligence analyze result is the correct capability because it returns each detected table with its cells, and each cell includes rowIndex, columnIndex, rowSpan, colSpan, content, and boundingRegions/polygon coordinates. This is exactly what you need to reconstruct merged cells and nested table structure into JSON. The other collections do not preserve the grid geometry required for merged cells.

Exam trap

The trap here is confusing Markdown output (documents collection) with structured table extraction; candidates assume Markdown preserves merged cells, but it does not expose rowSpan/colSpan.

How to eliminate wrong answers

Option A is wrong because the documents collection provides Markdown output for layout/read models, but Markdown flattens merged cells and does not expose rowSpan/colSpan metadata needed for accurate reconstruction. Option B is wrong because keyValuePairs is a form-recognition construct that pairs labels with values; it does not model table grids and cannot represent merged cells. Option C is wrong because the styles collection describes font/style attributes (e.g., handwriting) detected in the document, not table gridlines or cell spans.

Practice this question →
23
MCQhard

You are auditing an Azure AI Document Intelligence solution for data privacy compliance. Documents contain sensitive Personally Identifiable Information (PII). When using prebuilt models or custom models, how is data handled by Microsoft regarding model training?

A.Training data uploaded for custom models is made publicly available in the Azure AI gallery after 30 days.
B.Customer data and custom model training data are encrypted at rest and in transit, and are never used to train Microsoft foundation models.
C.Data privacy controls require you to deploy a local container, as cloud APIs store training documents indefinitely.
D.All submitted documents are automatically used to retrain the global prebuilt models overnight.
AnswerB

Microsoft guarantees that customer data and custom model training data remain encrypted at rest and in transit, and are never repurposed to train Microsoft foundation models. This directly satisfies the stem's PII privacy constraint, confirming that prebuilt and custom model processing does not leak sensitive data into shared Microsoft training corpora.

Why this answer

Microsoft's Azure AI Document Intelligence service treats customer data with strict privacy controls: all uploaded documents and custom model training data are encrypted at rest (AES-256) and in transit (TLS 1.2+), and Microsoft contractually commits that customer data is never used to train or improve Microsoft's foundation models. This aligns with Microsoft's Responsible AI and data privacy commitments, ensuring that sensitive PII remains isolated to the customer's resource.

Exam trap

AI-103 often tests the misconception that cloud AI services automatically use customer data for model training, when in fact Microsoft's default is to never use customer data for foundation model training without explicit consent.

How to eliminate wrong answers

Option A is wrong because Microsoft does not publish customer training data to any public gallery; custom models remain private to the Azure subscription. Option C is wrong because while Docker containers are available for on-premises deployment, cloud APIs do not store training documents indefinitely — they are retained only as needed for model training and can be deleted by the customer. Option D is wrong because prebuilt models are trained by Microsoft on its own datasets, not on customer-submitted documents, and no automatic overnight retraining with customer data occurs.

Practice this question →
24
MCQmedium

You are building an Azure AI Document Intelligence solution to process US W-2 tax forms. The forms are scanned at varying resolutions and contain tables with employee wage details. You need to extract specific fields such as wages, tips, and other compensation, and social security wages. You want to minimize development effort and ensure high accuracy. Which approach should you use?

A.Train a custom neural model using labeled samples of your W-2 forms.
B.Use the prebuilt tax model for US W-2 forms in Azure AI Document Intelligence.
C.Use the prebuilt invoice model and map the extracted fields to W-2 fields.
D.Use the general document model to extract all text and then parse the fields using custom code.
AnswerB

Azure AI Document Intelligence provides a prebuilt tax model specifically for US W-2 forms, designed to extract key fields like wages, tips, and social security wages with high accuracy. It eliminates the need for custom training and reduces development effort, directly addressing the requirement to minimize effort while ensuring accuracy for this standard form.

Why this answer

The prebuilt tax model for US W-2 forms is specifically trained to extract fields like wages, tips, and social security wages from W-2 documents. It provides high accuracy out of the box, eliminating the need for custom model training and reducing development effort. This aligns with the requirement to minimize effort while ensuring accurate extraction from standard tax forms.

Exam trap

The trap here is assuming that a custom model is always needed for high accuracy, overlooking that prebuilt models exist for common form types like W-2.

Practice this question →
25
MCQmedium

When labeling documents for a custom extraction model, what happens if you label the same field inconsistently across documents?

A.Model accuracy will decrease
B.The training will fail immediately
C.No impact
D.The model will automatically correct the labels
AnswerA

Inconsistent labels give the model contradictory supervision for identical field patterns, so it cannot learn a stable decision boundary. This label noise directly degrades precision and recall, meaning model accuracy will decrease — the constraint the question asks you to identify.

Why this answer

Inconsistent labeling of the same field across training documents introduces conflicting ground truth, which degrades the model's ability to learn a stable pattern. The neural trainer will still complete, but precision and recall for that field drop because the model receives contradictory signals. Consistency is a core labeling best practice in Document Intelligence Studio.

Exam trap

AI-103 often tests whether candidates understand that bad labels degrade accuracy rather than causing hard failures — the tempting wrong answer is 'training will fail immediately,' which sounds strict but is not how the service behaves.

How to eliminate wrong answers

Option B is wrong because inconsistent labels do not cause an immediate training failure — the service accepts the labels and produces a model, just a less accurate one. Option C is wrong because label quality directly drives model quality; claiming 'no impact' ignores how supervised learning works. Option D is wrong because the model has no mechanism to detect and auto-correct inconsistent human labels — it treats every label as ground truth.

Practice this question →
26
Multi-Selectmedium

Which THREE features are provided by the prebuilt Layout model in Azure AI Document Intelligence? (Choose THREE)

Select 3 answers
A.Automatic sentiment analysis of paragraph text
B.Extraction of text lines and words with bounding polygons
C.Table structure extraction (rows, columns, cell spans)
D.Language translation of extracted text into English
E.Selection mark state detection (selected or unselected checkboxes)
AnswersB, C, E

The Layout model returns a pages object containing lines and words, each with bounding polygons expressed as coordinate arrays. This satisfies the scenario's need for positional text extraction, distinct from the Read model's plainer output and from field-specific prebuilt models.

Why this answer

Option B is correct because the prebuilt Layout model in Azure AI Document Intelligence returns OCR results as text lines and individual words, each accompanied by bounding polygons that give the precise coordinates of the text on the page. Option C is correct because the Layout model extracts table structures, including the rows, columns, and cell spans, so tabular data is returned in an organized, machine-readable form. Option E is correct because the Layout model detects selection marks such as checkboxes and radio buttons and reports their state as selected or unselected.

Option A does not belong because sentiment analysis is a natural language processing capability (for example, from Azure AI Language), not a feature of the Document Intelligence Layout model. Option D does not belong because translation is handled by Azure AI Translator, whereas the Layout model only extracts and structures document content without translating it.

Exam trap

AI-103 often tests the misconception that the Layout model includes NLP features like sentiment analysis or translation, when it is strictly a document structure extraction model.

Practice this question →
27
Multi-Selecthard

Which THREE attributes are critical for a successful custom model training set?

Select 3 answers
A.High-quality images
B.Consistent labeling across all documents
C.Representative samples of all document layouts
D.All documents from the same printer
E.At least 1,000 pages per model
AnswersA, B, C

High-quality images directly satisfy the training-set requirement for accurate pattern recognition, since noisy, blurred or mislabelled samples degrade learned feature representations and inflate validation error. For custom model training, image fidelity and consistent labelling determine whether the model generalises beyond the training distribution, making quality a critical attribute alongside relevance and sufficient volume.

Why this answer

Option A (High-quality images) is correct because custom model training relies on OCR and layout analysis, so clear, well-lit, high-resolution scans or photos with minimal skew, blur, and noise give the model reliable visual features to learn from. Option B (Consistent labeling across all documents) is correct because supervised training requires ground-truth labels to be applied with the same schema and conventions throughout the dataset; inconsistent labels introduce contradictory signals that degrade accuracy and confuse the model. Option C (Representative samples of all document layouts) is correct because the model must generalize to every form, template, and layout it will encounter in production, so the training set must include examples covering the full variety of structures, fonts, and field placements.

Option D is not required because documents need not come from a single printer; in fact, variety in printers, scanners, and capture conditions improves robustness. Option E is not required because there is no fixed minimum of 1,000 pages per model; the needed volume depends on document complexity and diversity, and quality and representativeness matter more than a rigid page count.

Exam trap

AI-103 often tests training data requirements — candidates assume a large fixed page count (like 1,000 pages) is mandatory, but the real requirements are quality, consistent labeling, and layout diversity; quantity thresholds vary by model type (template vs. neural).

Practice this question →
28
Multi-Selectmedium

When building a custom template model in Azure AI Document Intelligence Studio, which THREE types of data or attributes can you extract by labeling your training documents? (Choose THREE)

Select 3 answers
A.Facial biometric embeddings
B.Real-time audio transcription timestamps
C.Tables (including row and column structures)
D.Selection marks (checkboxes and radio buttons)
E.Fields (key-value pairs)
AnswersC, D, E

Custom template models support labelled extraction of tables, capturing row and column structure alongside key-value pairs and selection marks. Labelling table cells teaches the model to reconstruct the grid, satisfying the scenario's requirement to extract tabular data from training documents.

Why this answer

Option C is correct because custom template models in Azure AI Document Intelligence Studio support labeling and extracting tabular data, including the row and column structure of tables, which the service returns as structured cells with row/column indices. Option D is correct because selection marks such as checkboxes and radio buttons are a first-class labeled entity type, returned with a state of selected or unselected and a confidence score. Option E is correct because the core purpose of a custom template model is to label and extract fields, i.e., key-value pairs such as invoice number, date, or total, which are returned as named field/value pairs.

Option A does not belong because facial biometric embeddings are produced by Azure AI Face, not by Document Intelligence, which analyzes document text, layout, and structure rather than identifying people. Option B does not belong because real-time audio transcription timestamps come from Azure AI Speech (for example, the Speech-to-Text API), whereas Document Intelligence processes documents and images, not live audio streams.

Exam trap

AI-103 often tests whether candidates know the exact set of labelable entity types in Document Intelligence Studio, and they mistakenly include capabilities from other Azure AI services like Face or Speech.

Practice this question →
29
MCQeasy

You are developing an application to extract specific fields from invoices using Azure AI Document Intelligence. Which prebuilt model should you use for this task?

A.custom-template
B.prebuilt-layout
C.prebuilt-document
D.prebuilt-invoice
AnswerD

The prebuilt-invoice model returns structured fields — vendor name, invoice date, due date, amounts, and line items — without custom training, satisfying the requirement to extract specific fields from invoices. Its dedicated schema targets invoice documents directly, unlike the general prebuilt-read or prebuilt-document models, which return raw text and generic key-value pairs.

Why this answer

The prebuilt-invoice model is purpose-built for invoice documents and returns structured fields such as VendorName, InvoiceDate, InvoiceTotal, DueDate, CustomerName, and line items without any training. Because the task is extracting specific fields from invoices, this prebuilt model directly matches the document type and required output. Custom models or generic layout models would require extra work and would not return invoice-specific fields out of the box.

Exam trap

AI-103 often tests whether candidates confuse generic document analysis (prebuilt-document or prebuilt-layout) with domain-specific prebuilt models, causing them to pick a general model when a specialized one like prebuilt-invoice is required.

How to eliminate wrong answers

Option A is wrong because custom-template requires you to label and train your own model on sample documents, which is unnecessary when a prebuilt invoice model already exists. Option B is wrong because prebuilt-layout only extracts structural elements like tables, selection marks, and text lines, not semantic invoice fields such as InvoiceTotal or VendorName. Option C is wrong because prebuilt-document is a general-purpose model for key-value pairs and entities across arbitrary documents, not a specialized invoice field extractor.

Practice this question →
30
MCQmedium

You are integrating Azure AI Document Intelligence into a web application. You call the analyzeDocument API and receive a 202 Accepted response. What is the correct pattern for your application to retrieve the final extraction results?

A.Wait for exactly 60 seconds and then send a GET request to the original analyze endpoint.
B.Immediately parse the response body of the 202 Accepted response for the extracted JSON data.
C.Poll the URL provided in the Operation-Location response header until the status returns 'succeeded', then fetch the results.
D.Open a WebSocket connection to the streaming endpoint specified in the WebSocket-Location header.
AnswerC

The 202 response means extraction is asynchronous, so the Operation-Location header carries the polling URL. Repeatedly GET that URL until the status field reads 'succeeded', then retrieve the results from the same endpoint. This satisfies the stem's requirement for the correct retrieval pattern after an accepted submission.

Why this answer

The analyzeDocument API is asynchronous: a 202 Accepted response means the request was accepted and processing is ongoing. The response includes an Operation-Location header with a URL that the client must poll until the operation status becomes 'succeeded', after which the results can be fetched from that same URL. This polling pattern is the documented and correct way to retrieve extraction results.

Exam trap

AI-103 often tests whether candidates treat analyzeDocument as synchronous and try to parse the 202 body directly, instead of following the Operation-Location polling pattern.

How to eliminate wrong answers

Option A is wrong because there is no fixed 60-second wait; processing time varies and the correct approach is to poll the Operation-Location URL until completion. Option B is wrong because the 202 response body does not contain the extracted JSON; it only acknowledges acceptance and provides the operation URL. Option D is wrong because Document Intelligence does not use a WebSocket streaming endpoint or a WebSocket-Location header for analyzeDocument results.

Practice this question →
31
MCQhard

You are configuring an Azure AI Document Intelligence custom extraction pipeline that processes thousands of diverse medical forms daily. You notice that extraction confidence scores for certain hand-written fields are low. What is the most effective remediation step within the Document Intelligence workflow?

A.Disable the OCR engine parameter in the API call to bypass text recognition steps.
B.Decrease the model training iterations configuration setting to prevent overfitting on handwriting.
C.Add additional labeled training documents that specifically feature diverse handwriting samples for those low-confidence fields.
D.Switch from a Custom Neural model to a Custom Template model.
AnswerC

Low confidence on handwritten fields reflects insufficient training examples matching that handwriting variability. Adding labelled documents containing diverse handwriting for those specific fields gives the custom extraction model the patterns it needs, directly raising confidence scores.

Why this answer

The most effective remediation for low-confidence extraction of handwritten fields in a custom Document Intelligence model is to provide more labeled training data that represents the variability causing the low confidence. Handwriting is highly variable, so adding diverse handwriting samples for the specific fields helps the model learn the patterns and improve accuracy. This directly addresses the root cause—insufficient training examples for those field variations—within the Document Intelligence workflow.

Exam trap

AI-103 often tests the misconception that tweaking model parameters (like iterations) or switching model types is the first fix for accuracy issues, when the primary solution is almost always improving training data quality and diversity.

How to eliminate wrong answers

Option A is wrong because disabling OCR would prevent any text recognition, making extraction impossible; OCR is essential for converting handwritten and printed text into machine-readable characters. Option B is wrong because decreasing training iterations would likely reduce model accuracy and underfit, not prevent overfitting; overfitting is typically addressed with more data or regularization, not fewer iterations. Option D is wrong because Custom Template models rely on fixed layouts and are poor at handling handwriting variability; switching to a template model would likely worsen performance on diverse handwritten forms.

Practice this question →
32
MCQeasy

Which of the following is a key advantage of using a 'prebuilt' model over a 'custom' model?

A.Higher accuracy for niche documents
B.Lower cost per page
C.Ability to define custom fields
D.No training required
AnswerD

Prebuilt models ship with pretrained weights, so they can be consumed immediately without any dataset preparation, training runs or compute spend. Custom models require labelled data and training time. This directly satisfies the scenario's constraint of avoiding the training effort entirely.

Why this answer

A prebuilt model is trained by the provider on a broad corpus of common document types, so it can be used immediately without any labeled training data or training cycle. This 'no training required' characteristic is its defining advantage — you get fast time-to-value and predictable behavior out of the box. Custom models, by contrast, require you to label documents and train, which costs time and effort.

Exam trap

AI-103 often tests the trade-off between prebuilt and custom models — candidates pick 'higher accuracy' as the prebuilt advantage, but accuracy on niche documents is exactly where custom models win; the correct prebuilt advantage is zero training effort.

How to eliminate wrong answers

Option A is wrong because higher accuracy on niche documents is precisely the advantage of a custom model, which is trained on your domain-specific data; prebuilt models often underperform on unusual layouts. Option B is wrong because lower cost per page is not a guaranteed advantage of prebuilt models — pricing depends on the service tier and volume, and custom models can be more cost-effective at scale for high-accuracy needs. Option C is wrong because defining custom fields is a capability of custom models (and in some services, composed models), not prebuilt ones, which return a fixed schema.

Practice this question →
33
Multi-Selectmedium

Which TWO actions should you perform to troubleshoot a model that consistently misinterprets tables?

Select 2 answers
A.Use the Read API instead
B.Disable the layout model
C.Change the resource region
D.Verify labels for alignment and completeness
E.Retrain with more diverse training samples
AnswersD, E

Verifying labels for alignment and completeness directly addresses table misinterpretation, since misaligned or missing annotations corrupt the training signal that teaches the model which cells belong to which rows and columns. This satisfies the stem's constraint that the model consistently misinterprets tables, pointing to systematic labelling errors rather than inference-time issues.

Why this answer

Option D is correct because when a model consistently misinterprets tables, the first troubleshooting step is to audit the ground-truth labels — verifying that bounding boxes, row/column tags, and table region annotations are aligned with the actual content and that no cells or headers are missing ensures the model is learning from accurate supervision. Option E is correct because table misinterpretation often stems from insufficient variety in the training data; retraining with more diverse samples (different table layouts, border styles, fonts, merged cells, and scan qualities) improves the model's ability to generalize to unseen table structures. Option A is not appropriate because the Read API is a general OCR endpoint for printed and handwritten text and does not provide the table-structure extraction or custom-model tuning needed to fix a misinterpreting custom model.

Option B is wrong because disabling the layout model removes the component that detects structural elements like tables, which would worsen rather than troubleshoot the problem. Option C is incorrect because changing the resource region only affects data residency and endpoint location, not the model's table-parsing accuracy.

Exam trap

The trap here is assuming an infrastructure or API change (region, Read API, disabling layout) can fix an accuracy problem, when the actual root cause in Document Intelligence troubleshooting is almost always data quality or training diversity.

Practice this question →
34
MCQeasy

Which prebuilt Azure AI Document Intelligence model should you use to extract line items, merchant name, transaction date, and total tax from point-of-sale purchase receipts?

A.prebuilt-invoice
B.prebuilt-idDocument
C.prebuilt-businessCard
D.prebuilt-receipt
AnswerD

The prebuilt-receipt model is trained specifically on point-of-sale receipts, returning fields including merchant name, transaction date, line items and total tax. Other prebuilt models target invoices, identity documents or business cards, so they lack the receipt-specific field schema the scenario demands.

Why this answer

The prebuilt-receipt model is designed to extract key fields from sales receipts, including line items, merchant name, transaction date, and total tax. It is specifically trained on receipt layouts and is the correct choice for point-of-sale purchase receipts.

Exam trap

AI-103 often tests the distinction between prebuilt models by their target documents; candidates might confuse receipt extraction with invoice or business card models if they overlook the specific fields like line items and total tax.

How to eliminate wrong answers

Option A is wrong because prebuilt-invoice is for invoices, which have different fields like invoice ID and due date. Option B is wrong because prebuilt-idDocument extracts information from identity documents like passports or driver's licenses. Option C is wrong because prebuilt-businessCard extracts contact information from business cards, not receipt data.

Practice this question →
35
Multi-Selecteasy

Which TWO file formats are natively supported as inputs for analysis in Azure AI Document Intelligence? (Choose TWO)

Select 2 answers
A.text/html
B.application/pdf
C.application/zip
D.image/jpeg
E.application/vnd.ms-excel
AnswersB, D

Document Intelligence accepts application/pdf natively, processing both text-based and scanned PDFs through its Read and prebuilt models. This satisfies the stem's requirement for a natively supported input format, unlike formats needing prior conversion such as DOCX or HTML.

Why this answer

Azure AI Document Intelligence natively accepts application/pdf (option B) because PDF is one of its primary supported input formats, allowing both digital and scanned documents to be submitted directly to the Analyze Document operations. It also natively supports image/jpeg (option D), since JPEG is among the supported image formats (along with PNG, BMP, TIFF, and HEIF) that the service can process for OCR and document analysis. The other options are not natively supported inputs: text/html (A) is not an accepted content type, application/zip (C) is not a document format the service reads directly, and application/vnd.ms-excel (E) is an Excel spreadsheet format that Document Intelligence does not accept as a native input.

Exam trap

AI-103 often tests whether candidates confuse 'formats the OCR engine can read after conversion' with 'formats natively accepted by the analyze API' — HTML and ZIP feel plausible but are not on the supported content-type list.

Practice this question →
36
MCQeasy

You are developing an application that needs to automatically extract key-value pairs and tabular data from standardized invoices without any prior labeled training data. Which Azure AI Document Intelligence model should you use?

A.Azure AI Document Intelligence General Document model
B.Azure AI Document Intelligence Custom Extraction model
C.Azure AI Document Intelligence Prebuilt Invoice model
D.Azure AI Vision OCR feature
AnswerC

The prebuilt invoice model is trained by Microsoft on invoice documents, extracting key-value pairs and line-item tables without any custom labelled data. This satisfies the stem's zero-training constraint, unlike custom or composed models that require labelled samples.

Why this answer

The Prebuilt Invoice model is purpose-built for standardized invoice documents and extracts key-value pairs (vendor, invoice date, totals, line items) plus tabular data out of the box, with no labeled training data required. It is one of the Document Intelligence prebuilt models trained on millions of invoice documents, so it handles common invoice layouts immediately. The General Document model extracts text and generic key-value pairs but does not understand invoice-specific fields like InvoiceTotal or DueDate.

Exam trap

AI-103 often tests the distinction between 'no training data required' (prebuilt models) and 'requires labeled samples' (custom models) — candidates who overlook the phrase 'without any prior labeled training data' may wrongly select Custom Extraction.

How to eliminate wrong answers

Option A is wrong because the General Document model only extracts generic text, layout, and untyped key-value pairs — it has no invoice-specific schema, so you would not get fields like VendorName or InvoiceTotal reliably. Option B is wrong because a Custom Extraction model requires you to label at least five sample documents and train the model, which contradicts the 'no prior labeled training data' requirement. Option D is wrong because Azure AI Vision OCR only returns raw text and bounding boxes; it does not understand invoice structure, key-value relationships, or tables.

Practice this question →
37
MCQmedium

Your company requires strict data privacy. Where should you host your Document Intelligence resources to ensure data remains in a specific region?

A.Regional Azure resource
B.Any available region
C.Global service endpoint
D.Public multi-region endpoint
AnswerA

A regional Azure resource pins Document Intelligence processing and storage to a single chosen geography, satisfying the strict data-residency constraint. Unlike multi-region or global endpoints, which may replicate data across boundaries, regional deployment guarantees that documents and extracted results never leave the specified region, meeting the company's privacy requirement.

Why this answer

To guarantee that Document Intelligence data (documents, extracted results, and processing) stays within a specific geography, you must deploy a regional Azure resource in the desired region. Regional resources pin both compute and data residency to that region, satisfying strict data-privacy and sovereignty requirements. Global or multi-region endpoints may replicate or route data outside the chosen geography, violating the requirement.

Exam trap

AI-103 often tests the misconception that 'any Azure region' or a 'global endpoint' satisfies data residency, when only a region-specific resource guarantees data stays in the required geography.

How to eliminate wrong answers

Option B (Any available region) is wrong because it provides no data-residency guarantee — Azure may place or process data in any region, breaching the privacy requirement. Option C (Global service endpoint) is wrong because global endpoints can route requests and store data across multiple regions, which is incompatible with strict regional data residency. Option D (Public multi-region endpoint) is wrong because multi-region endpoints inherently distribute data across regions and expose a public endpoint, both of which violate the requirement to keep data in a specific region.

Practice this question →
38
MCQeasy

You are using Azure AI Document Intelligence to extract information from identity documents, such as passports and driver licenses. Which prebuilt model should you select?

A.prebuilt-tax.us.w2
B.prebuilt-idDocument
C.prebuilt-W2
D.prebuilt-businessCard
AnswerB

The prebuilt-idDocument model is trained specifically for passports, driver licences and identity cards, extracting fields such as name, date of birth and document number. General or custom models lack this document-type-specific field schema, so they return weaker results for identity documents.

Why this answer

The prebuilt-idDocument model is specifically designed to extract key information from identity documents such as passports, driver licenses, and U.S. state IDs. It returns structured fields like name, date of birth, document number, and expiration date. This is the only prebuilt model among the options that targets identity documents.

Exam trap

AI-103 often tests the ability to distinguish between prebuilt models for different document types; candidates may confuse the W-2 model with identity documents or select an invalid model name like prebuilt-W2.

How to eliminate wrong answers

Option A is wrong because prebuilt-tax.us.w2 is for extracting data from U.S. W-2 tax forms, not identity documents. Option C is wrong because prebuilt-W2 is not a valid Azure AI Document Intelligence model name; the correct model for W-2 forms is prebuilt-tax.us.w2.

Option D is wrong because prebuilt-businessCard is for extracting information from business cards, not passports or driver licenses.

Practice this question →
39
Multi-Selectmedium

Which TWO of the following are valid ways to authenticate to the Document Intelligence service?

Select 2 answers
A.FTP Credentials
B.SSH Key
C.SQL Server Authentication
D.API Key
E.Microsoft Entra ID (RBAC)
AnswersD, E

API keys authenticate requests to Document Intelligence by passing a shared secret in the Ocp-Apim-Subscription-Key header, satisfying the requirement for a valid service authentication method. Unlike Microsoft Entra ID tokens, keys grant full resource access without role scoping, but they remain a supported credential for the service.

Why this answer

Option D (API Key) is correct because Azure AI Document Intelligence (formerly Form Recognizer) issues subscription keys that clients pass in the Ocp-Apim-Subscription-Key header (or as a query parameter) to authenticate REST/SDK requests. Option E (Microsoft Entra ID with RBAC) is correct because the service supports Entra ID token-based authentication, where a bearer token is obtained for the https://cognitiveservices.azure.com/ scope and access is governed by Azure RBAC roles such as Cognitive Services User. The remaining options do not apply: FTP credentials (A) are for file transfer servers, not Azure AI services; an SSH key (B) is for secure shell login to hosts; and SQL Server Authentication (C) is a database login mechanism unrelated to Document Intelligence's HTTP-based authentication.

Exam trap

AI-103 often tests whether candidates confuse generic IT authentication mechanisms (FTP, SSH, SQL logins) with Azure AI service authentication, which is limited to API keys and Microsoft Entra ID.

Practice this question →
40
MCQeasy

You need to extract text lines, words, bounding polygons, and selection marks (such as radio buttons and checkboxes) from arbitrary documents without training. Which prebuilt model should you invoke?

A.Prebuilt Business Card model
B.Prebuilt ID Document model
C.Prebuilt Layout model
D.Custom Neural model
AnswerC

The prebuilt Layout model returns text lines, words, bounding polygons and selection marks (radio buttons, checkboxes) from arbitrary documents without training, satisfying the no-training constraint. Unlike the Read model, which returns only text and no selection marks, Layout adds geometric and mark detection, matching every required output.

Why this answer

The prebuilt Layout model in Azure AI Document Intelligence extracts text lines, words, bounding polygons, and selection marks (checkboxes, radio buttons) from documents without any training. It is designed for general document structure extraction and is the correct choice when you need layout-level elements and selection marks from arbitrary documents. It requires no custom training and works out of the box.

Exam trap

AI-103 often tests whether candidates know that the Layout model is the no-training, general-purpose extractor for text, tables, and selection marks — the trap is selecting a specialized prebuilt model (ID, Business Card) or a custom model when the requirement is arbitrary documents with selection marks.

How to eliminate wrong answers

Option A is wrong because the Prebuilt Business Card model is specialized for extracting contact fields (name, phone, email, company) from business cards — it does not return general text lines, words, bounding polygons, or selection marks. Option B is wrong because the Prebuilt ID Document model targets identity documents (passports, driver's licenses) and extracts specific identity fields, not arbitrary layout elements or selection marks. Option D is wrong because the Custom Neural model requires labeled training data and is built for domain-specific field extraction — it is not a no-training, general-purpose layout extractor.

Practice this question →
41
MCQmedium

You are using Document Intelligence to classify documents into different types (e.g., invoices, bank statements). Which model is most appropriate?

A.Prebuilt-invoice
B.Custom classification model
C.Read model
D.Custom extraction model
AnswerB

A custom classification model trains on your labelled samples to assign documents to your own categories, such as invoices versus bank statements. Prebuilt models extract fields from known types, so they cannot classify arbitrary custom document types.

Why this answer

A custom classification model is purpose-built to categorize documents into user-defined types (e.g., invoice vs. bank statement) before or alongside extraction. It is trained on labeled examples of each document class and returns a document type with confidence. Prebuilt-invoice extracts fields from invoices but does not classify arbitrary document types.

Exam trap

AI-103 often tests the distinction between classification (what type of document is this?) and extraction (what fields are in this document?) — candidates pick 'custom extraction' because it sounds more powerful but it does not classify.

How to eliminate wrong answers

Option A is wrong because Prebuilt-invoice only extracts invoice fields — it cannot distinguish invoices from bank statements or other classes. Option C is wrong because the Read model only performs OCR and returns text/lines; it has no classification capability. Option D is wrong because a custom extraction model pulls structured fields from a known document type; it does not classify documents into types.

Practice this question →
42
MCQeasy

Your company processes business cards from international clients. Which prebuilt Azure AI Document Intelligence model should you use to extract names, company names, emails, and phone numbers from these cards?

A.prebuilt-businessCard
B.prebuilt-invoice
C.prebuilt-layout
D.prebuilt-receipt
AnswerA

The prebuilt-businessCard model is purpose-built to extract contact fields — names, company names, emails and phone numbers — from business card images. It satisfies the stem's requirement for a prebuilt model targeting business cards, avoiding the need to train a custom extraction model.

Why this answer

The prebuilt-businessCard model is specifically trained to extract common fields from business cards, including names, company names, emails, and phone numbers. It is optimized for the typical layout and content of business cards, making it the correct choice for this scenario.

Exam trap

AI-103 often tests the distinction between prebuilt models by their specific field sets; candidates may confuse business card extraction with invoice or receipt models if they overlook the unique fields like emails and phone numbers.

How to eliminate wrong answers

Option B is wrong because prebuilt-invoice is designed for invoices, extracting fields like invoice ID, due date, and vendor details, not business card information. Option C is wrong because prebuilt-layout extracts text and structure but does not provide semantic fields like names or emails. Option D is wrong because prebuilt-receipt is tailored for sales receipts, capturing items, totals, and transaction details, not business card data.

Practice this question →
43
MCQhard

You are configuring an Azure AI Document Intelligence orchestration model to automatically classify and extract data from incoming customer correspondence, which includes invoices, work orders, and purchase orders. One of the component models is failing to classify documents correctly. How should you resolve this issue?

A.Modify the orchestration model routing threshold in the Azure portal settings.
B.Switch the orchestration model from a template-based classifier to a neural classifier using the REST API.
C.Retrain the failing component custom model with more distinct sample documents that represent the specific document class.
D.Update the API version to bypass classification and force direct extraction via the general document model.
AnswerC

Retraining the failing component custom model directly addresses misclassification by supplying more distinct samples of the specific document class, sharpening the model's learned feature boundaries. Since orchestration routes documents to component models, each classifier's accuracy depends on representative training data; additional distinct samples reduce ambiguity between invoices, work orders and purchase orders.

Why this answer

The most effective way to resolve misclassification by a component model in an orchestration model is to retrain that custom model with more distinct sample documents that clearly represent the specific document class. This improves the model's ability to differentiate between classes.

Exam trap

AI-103 often tests troubleshooting steps for custom models; candidates might incorrectly think they can adjust routing thresholds or switch model types via API, rather than addressing the training data quality.

How to eliminate wrong answers

Option A is wrong because the orchestration model routing threshold is not a configurable setting in the Azure portal; orchestration uses the component models' own confidence scores. Option B is wrong because switching from template-based to neural classifier is not a simple API switch and may not address the root cause of poor training data. Option D is wrong because updating the API version does not bypass classification; orchestration always classifies first, and forcing extraction via general document model would lose the benefits of specialized models.

Practice this question →
44
MCQeasy

Your team needs to extract data from a large volume of standardized tax forms using Azure AI Document Intelligence. The forms have a fixed layout where fields are always in the exact same location. Which model type provides the fastest training and highest accuracy for this specific use case?

A.Custom template model
B.Prebuilt receipt model
C.Custom neural model
D.General document model
AnswerA

A custom template model learns fixed field positions from as few as five labelled samples, giving rapid training and high accuracy when layout is consistent. It suits standardised tax forms where fields never move, unlike custom neural or prebuilt models.

Why this answer

A custom template model is designed for documents with a consistent, fixed layout, and it trains quickly because it relies on layout/template matching rather than deep semantic learning. For standardized tax forms where fields are always in the same location, the template model achieves high accuracy with minimal training data and fast training time. This is the classic use case Microsoft documents for the template model type.

Exam trap

AI-103 often tests the trade-off between template and neural models, and candidates incorrectly assume 'neural' is always more accurate, when for fixed-layout forms the template model is faster to train and equally or more accurate.

How to eliminate wrong answers

Option B is wrong because the prebuilt receipt model is trained for sales receipts, not tax forms, and cannot be retrained on your specific form layout. Option C is wrong because the custom neural model is optimized for variable layouts and unstructured documents; it requires more training data and longer training time, and its advantage (handling layout variation) is wasted on fixed-layout forms. Option D is wrong because the general document model extracts only basic entities like key-value pairs and selection marks without customization, and it does not provide the field-level accuracy of a trained template model for your specific form.

Practice this question →
45
Multi-Selecthard

You are troubleshooting a low confidence score on specific fields extracted by your Azure AI Document Intelligence custom template model. Which TWO actions can help improve the extraction confidence for those fields? (Choose TWO)

Select 2 answers
A.Increase the confidence threshold parameter in the analyzeDocument request body to 0.99.
B.Convert all training PDFs to grayscale and reduce their resolution to 72 DPI to speed up processing.
C.Ensure all training documents are of high visual quality and free from blur or heavy skew.
D.Add more diverse training documents that represent variations in the document layout where the low-confidence fields appear.
E.Switch the model type from custom template to a prebuilt business card model.
AnswersC, D

Low-quality scans with blur or skew degrade the OCR stage, so extracted text feeding the template model is corrupted, lowering field confidence. Clean, sharp training documents raise OCR accuracy, which directly lifts confidence on the affected fields.

Why this answer

Option C is correct because custom template models learn field positions and visual patterns from the labeled samples, so blurry, skewed, or low-quality training documents degrade the model's ability to reliably locate and read those fields, producing low confidence scores; supplying sharp, straight, high-quality scans directly improves feature extraction and OCR accuracy. Option D is correct because low confidence on specific fields usually indicates the model has not seen enough layout variation for those fields, so adding diverse training documents that capture the different layouts, fonts, and positions where those fields appear lets the model generalize and raise its confidence. Option A is wrong because the confidence threshold in the analyzeDocument request only filters which results are returned or flagged; it does not change the model's actual extraction confidence.

Option B is wrong because converting to grayscale and downsampling to 72 DPI reduces image fidelity and typically lowers OCR and extraction quality rather than improving confidence. Option E is wrong because a prebuilt business card model is a fixed, general-purpose model that cannot be trained on your specific fields or layouts, so it cannot improve confidence for your custom template fields.

Exam trap

AI-103 often tests common misconceptions about improving model performance; candidates might think adjusting API parameters or switching to prebuilt models helps, rather than focusing on training data quality and diversity.

Practice this question →
46
MCQhard

You are deploying an Azure AI Document Intelligence custom extraction model for a regulated workload. Documents are uploaded to Azure Blob Storage in a private container, and no public network access is allowed. Your application runs in an Azure virtual network. You must ensure the Document Intelligence resource can access the documents for training and analysis without exposing them publicly. Which configuration should you implement?

A.Copy the documents into the Document Intelligence resource's own storage and reference them by internal path
B.Generate a long-lived SAS token for the container and embed it in the training request
C.Configure the Document Intelligence resource with a private endpoint and grant it access to the storage account through a managed identity with the Storage Blob Data Reader role
D.Enable public network access on the storage account but restrict it by IP firewall to the Document Intelligence outbound IP range
AnswerC

A private endpoint brings the Document Intelligence resource into the virtual network, and a managed identity with Storage Blob Data Reader lets the service read blobs without public exposure or shared keys. This satisfies the no-public-access requirement while enabling both training and analysis against private containers.

Why this answer

For private, no-public-access scenarios, the supported pattern is a private endpoint for the Document Intelligence resource plus a managed identity granted Storage Blob Data Reader on the storage account. This keeps traffic on the virtual network and avoids shared keys or SAS tokens. IP firewalls and SAS tokens do not satisfy the no-public-access constraint.

Exam trap

The trap here is treating a SAS token as sufficient for private access, when it leaves the storage account publicly reachable and adds credential risk.

Practice this question →
47
MCQmedium

You need to extract data from a highly varied set of tax forms where the layout changes frequently. Which approach is most efficient?

A.Use a Template model
B.Use a Neural custom model
C.Use Read API
D.Use General Document model
AnswerB

Neural custom models learn from labelled examples and tolerate layout variation, so frequently changing tax form structures do not break extraction. Template-based or form-specific approaches fail when fields shift position, whereas the neural model generalises across the highly varied layouts described in the stem.

Why this answer

A Neural custom model in Azure AI Document Intelligence is trained on your own labeled data and can generalize to layout variations, making it ideal for frequently changing tax forms. It learns the structure and key-value pairs from examples rather than relying on fixed templates. This provides the most efficient extraction for highly varied documents.

Exam trap

AI-103 often tests the trade-off between template and neural models, with candidates incorrectly assuming template models are more efficient for varied layouts due to their simplicity.

How to eliminate wrong answers

Option A is wrong because a Template model requires a fixed, consistent layout and fails when the layout changes frequently. Option C is wrong because the Read API only extracts text and does not understand structure or key-value pairs, so it cannot efficiently extract specific fields from tax forms. Option D is wrong because the General Document model is pre-trained for common document types and may not accurately extract specialized tax form fields, especially with layout variations.

Practice this question →
48
MCQhard

A financial services company uses a custom neural model in Azure AI Document Intelligence to extract fields from loan applications. After retraining the model with 30 additional labeled documents, field accuracy for the 'loanAmount' field dropped sharply, although the field was previously accurate. The new documents were labeled by a different team. You need to identify the most likely cause of the regression before retraining again. What should you investigate first?

A.Whether the service endpoint region was changed between trainings
B.Whether the model's confidence threshold was raised in the calling application
C.Whether the labeled documents use inconsistent field labels or value formatting for 'loanAmount' compared with the original training set
D.Whether the training dataset exceeded the maximum page count allowed for custom neural models
AnswerC

Custom neural models learn from label-value associations in the training data. If a second labeling team used a different field name, different currency formatting, or inconsistent bounding regions, the model receives contradictory supervision for the same field. That inconsistency directly degrades per-field accuracy and is the most probable cause of a sudden drop after adding documents.

Why this answer

Custom neural model quality depends heavily on consistent, accurate labels. When multiple teams label the same dataset, differences in field naming, value formatting, or region placement introduce conflicting training signals that disproportionately harm the affected field. Auditing label consistency for 'loanAmount' across both datasets is the correct first step before retraining.

Exam trap

The trap here is blaming infrastructure or configuration changes for a per-field accuracy regression when inconsistent training labels are the more common cause.

Practice this question →
49
Multi-Selecteasy

Which TWO of the following are valid Document Intelligence project types in the Studio?

Select 2 answers
A.Speech-to-text
B.Custom extraction
C.Sentiment analysis
D.Custom classification
E.Face detection
AnswersB, D

Custom extraction is a supported Document Intelligence Studio project type, training models to pull labelled field values from documents using custom neural or template approaches. It satisfies the stem by being one of the recognised project types available for selection in the Studio.

Why this answer

In Azure AI Document Intelligence Studio, the two valid project types are Custom extraction (B) and Custom classification (D). Custom extraction lets you build a model that pulls specific fields (key-value pairs, tables, entities) from documents using labeled samples, which is the core 'custom form'/'custom extraction' capability of Document Intelligence. Custom classification lets you train a model to categorize incoming documents into user-defined classes, a distinct project type also supported in the Studio.

The other options do not belong: Speech-to-text (A) is an Azure AI Speech capability, Sentiment analysis (C) is an Azure AI Language feature, and Face detection (E) is part of Azure AI Vision—none of these are Document Intelligence project types.

Exam trap

AI-103 often tests whether candidates can distinguish Document Intelligence capabilities (extraction, classification) from other Azure AI services (Speech, Language, Vision) — candidates who see 'custom' and assume any AI feature qualifies may incorrectly pick sentiment analysis or face detection.

Practice this question →
50
MCQmedium

Your custom extraction model is failing to identify fields on a new version of a document. You have labeled 50 documents. What is the most likely solution?

A.Change the API version to v2.1
B.Switch to a template model
C.Add more training documents with the new layout
D.Increase the confidence threshold
AnswerC

The model fails because the new layout differs from the 50 labelled samples it trained on. Adding training documents that reflect the new layout supplies the varied examples the model needs to generalise, satisfying the requirement to recognise fields on the updated document version.

Why this answer

When a custom extraction model fails on a new document layout, the most likely fix is to add more training documents that represent the new layout so the model can learn the additional variations. Custom models (especially neural) improve with more diverse, labeled examples covering the layouts they must handle; 50 documents of the old layout are insufficient for the new version. Retraining with representative samples is the standard remedy.

Exam trap

AI-103 often tests the misconception that tuning thresholds or switching model types fixes accuracy problems — the trap is selecting 'increase confidence threshold' or 'switch to template model' when the real issue is insufficient training data for the new layout.

How to eliminate wrong answers

Option A is wrong because changing the API version to v2.1 does not address a model accuracy problem on a new layout — API versions affect features and response schema, not the model's ability to recognize fields it was not trained on. Option B is wrong because switching to a template model would likely perform worse on a new layout — template models are rigid and require exact layout matching, so they fail even more readily on layout variations. Option D is wrong because increasing the confidence threshold only filters out low-confidence predictions; it does not improve the model's ability to detect fields it currently misses, and it would actually reduce recall further.

Practice this question →
51
MCQhard

You are building an Azure AI Document Intelligence solution to process complex financial statements. Due to varying layouts across different financial institutions, you decide to use a custom neural model instead of a custom template model. What is a key architectural advantage of the custom neural model in this scenario?

A.It requires significantly fewer training documents than a template model to achieve high accuracy.
B.It can be trained entirely unsupervised without requiring any human-labeled training documents.
C.It supports cross-page tables and varying visual layouts without requiring strict coordinate alignment.
D.It can extract data from scanned documents without running Optical Character Recognition (OCR) first.
AnswerC

Custom neural models use deep learning to handle variable layouts, cross-page tables and differing visual structures, so financial statements from different institutions need no fixed coordinate templates. This satisfies the varying-layout constraint that a custom template model, reliant on rigid positional alignment, cannot accommodate.

Why this answer

The custom neural model in Azure AI Document Intelligence is designed to handle complex, variable layouts, including cross-page tables and differing visual structures, without requiring strict coordinate alignment. This makes it ideal for financial statements from different institutions where layouts vary significantly. It leverages deep learning to understand document structure and extract fields accurately even when the position of data changes.

Exam trap

AI-103 often tests the assumption that neural models require less training data or are unsupervised, but they actually require labeled data and are supervised; the key advantage is layout flexibility, not data efficiency.

How to eliminate wrong answers

Option A is wrong because custom neural models typically require more training data (at least 5 labeled documents, but often more) compared to template models, which can work with as few as 5. Option B is wrong because custom neural models require human-labeled training documents; they are not unsupervised. Option D is wrong because all Document Intelligence models rely on OCR to extract text from scanned documents before further processing; neural models do not bypass OCR.

Practice this question →
52
Multi-Selectmedium

You are designing an information extraction solution using Azure AI Document Intelligence. Which TWO features are supported by Custom Neural models? Each correct selection represents a complete solution element.

Select 2 answers
A.Extraction of key-value pairs and fields defined during training
B.Zero-shot extraction of completely unseen document types without any training data
C.Extraction of tables from documents with variable layouts
D.Real-time voice-to-text transcription of document contents
E.Automatic language translation of extracted text into 100+ languages
AnswersA, C

Custom Neural models are trained on labelled samples to extract the specific key-value pairs and fields you define, generalising across layout variation. This directly satisfies the stem's requirement for trained field extraction, which template models cannot achieve when document structure varies.

Why this answer

Option A is correct because Custom Neural models are trained on labeled samples to extract the specific key-value pairs and fields you define during training, returning structured JSON with confidence scores for those fields. Option C is correct because Custom Neural models support table extraction, including documents with variable layouts, by learning the structure from your labeled training data. Option B is incorrect because zero-shot extraction of unseen document types without training data is not a Custom Neural capability; that is handled by prebuilt models or the newer query-field/zero-shot features, not by training a Custom Neural model.

Option D is incorrect because voice-to-text transcription is a speech service capability, not a Document Intelligence extraction feature. Option E is incorrect because automatic translation into 100+ languages is provided by Azure AI Translator, not by Custom Neural models.

Exam trap

AI-103 often tests the misconception that Custom Neural models can perform zero-shot extraction without training, causing candidates to select that option instead of the actual supervised capabilities.

Practice this question →
53
MCQhard

Your application is receiving 429 errors from the Document Intelligence service. What does this indicate?

A.Authentication failed
B.Rate limit exceeded
C.Server-side error
D.The request is malformed
AnswerB

HTTP 429 signals that the Document Intelligence service is throttling requests because the call rate or resource consumption has exceeded the assigned quota. This directly satisfies the stem's constraint: the application is being rate-limited, so retry with exponential backoff or request a quota increase.

Why this answer

HTTP 429 'Too Many Requests' indicates the client has exceeded the rate limit or quota for the Document Intelligence service. Azure Cognitive Services enforce per-second and per-minute transaction limits based on the pricing tier (e.g., S0 has specific TPS limits). The correct response is to implement retry with exponential backoff and/or request a quota increase.

Exam trap

AI-103 often tests the confusion between 429 (rate limit) and 401 (auth) or 400 (bad request) — candidates must map HTTP status codes precisely to their meanings for Azure AI services.

How to eliminate wrong answers

Option A is wrong because authentication failures return HTTP 401 Unauthorized, not 429. Option C is wrong because server-side errors return HTTP 5xx codes (500, 502, 503), not 429. Option D is wrong because malformed requests return HTTP 400 Bad Request, indicating a client-side syntax or validation issue, not a rate limit.

Practice this question →
54
MCQhard

You need to secure the communication between your app and Document Intelligence using a private endpoint. What is the primary benefit?

A.Reduced cost
B.Faster inference speeds
C.Increased throughput limits
D.Traffic stays within the Azure private network
AnswerD

A private endpoint assigns a private IP from your virtual network to the Document Intelligence resource, so requests never traverse the public internet. Traffic remains on the Azure backbone within the private network, eliminating public exposure and satisfying the security requirement.

Why this answer

A private endpoint for Document Intelligence creates a private IP address in your virtual network via Azure Private Link, so all traffic between your app and the Document Intelligence resource traverses the Microsoft backbone and never the public internet. The primary benefit is network isolation — traffic stays within the Azure private network, reducing exposure to internet-based threats and satisfying compliance requirements for data-in-transit isolation.

Exam trap

AI-103 often tests whether candidates confuse the security benefit of private endpoints (network isolation, no public internet exposure) with performance or cost benefits that private endpoints do not provide.

How to eliminate wrong answers

Option A is wrong because private endpoints do not reduce cost — in fact, Private Link endpoints and the associated data processing can add cost. Option B is wrong because private endpoints do not inherently make inference faster; latency may even increase slightly due to private DNS resolution and routing. Option C is wrong because private endpoints do not raise throughput or quota limits — those are governed by the pricing tier and service quotas, not by network path.

Practice this question →
55
MCQmedium

You are extracting data from tables. The layout model is missing specific column headers. How can you improve the results?

A.Use a Custom Neural model
B.Increase image resolution
C.Use the Read API
D.Enable 'document-classify' feature
AnswerA

Custom Neural models learn field semantics from your labelled samples, so they can infer column headers from layout and context rather than relying on fixed positional templates. This directly addresses the missing-header constraint, where the prebuilt layout model cannot map columns without explicit header text.

Why this answer

When the layout model misses specific column headers, a Custom Neural model can be trained with labeled examples that include those headers, allowing the model to learn the specific structure and improve extraction. Custom Neural models are designed for extracting structured data from documents with varying layouts and can be tailored to recognize custom fields, including headers that the prebuilt layout model might overlook.

Exam trap

The trap is assuming that general OCR improvements (resolution) or other prebuilt features (Read API, document-classify) can solve a specific extraction gap; the key is recognizing that custom training is needed for custom headers.

How to eliminate wrong answers

Option B is wrong because increasing image resolution may improve OCR accuracy but does not address the model's inability to recognize specific column headers; it is not a targeted fix for missing headers. Option C is wrong because the Read API only extracts text and does not provide table structure or header recognition; it is a lower-level OCR service. Option D is wrong because the 'document-classify' feature is used for classifying document types, not for improving table header extraction.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Information Extraction questions.

Start 20-question session