Important Microsoft AB-731 Exam Questions

Answer: A

Explanation:

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

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

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

Answer: A, B

Explanation:

When a non-reasoning generative AI model produces inconsistent outputs, the most reliable improvement is to make the prompt more specific, constrained, and demonstrative of what ''good'' looks like.

A is correct because adding high-quality examples is a form of few-shot prompting. Examples act like ''training wheels'' at inference time: they show the model the desired structure, tone, level of detail, formatting rules, and boundaries. This reduces ambiguity and variance, especially for tasks like marketing copy, summaries, policy text, or customer replies. The more your examples resemble real target outputs (including edge cases), the more consistent the model's completions become.

B is correct because adding context, relevant source material, and explicit expectations narrows the model's degrees of freedom. Including the intended audience, purpose, constraints (length, voice, banned claims), and trusted reference content (approved facts, product specs, policy excerpts) helps the model stay aligned and reduces hallucinations and off-brand language. This is also where you specify acceptance criteria such as ''must include 3 bullet points,'' ''use UK English,'' or ''cite only provided text.''

C is not best: technical jargon can confuse or bias output if it's not aligned to the task; clarity beats jargon. D is not best: a single concise requirement is usually under-specified and often increases variability.

Answer: D

Explanation:

An AI governance council (often called an ''AI Council'') exists primarily to set direction and provide cross-functional oversight so AI adoption stays aligned to the organization's values, risk posture, and Responsible AI commitments. That maps most directly to D. Microsoft's guidance on creating an AI Council describes leadership responsibilities such as defining and communicating the organization's AI vision, values, and policies, reviewing and approving AI use cases/projects, and coordinating with enablement and technical readiness teams to understand risks, issues, and opportunities. It also emphasizes representation across distinct functions (for example: senior leadership, legal, compliance, risk, ethics, data, technology, business, HR) to ensure governance decisions reflect a broad, accountable perspective.

The other options describe activities that may be supporting outcomes of governance, but they are not the council's primary purpose. A is narrow (IT policy enforcement/user monitoring) and is typically handled by security/compliance operations rather than the top-level governance body. B is user enablement/training (commonly owned by adoption/change management teams). C focuses on technical delivery and performance management (often owned by engineering/MLOps/service owners). The governance council's central value is strategic guidance + oversight + cross-functional alignment to ensure Responsible AI adoption is consistent, accountable, and sustainable across the business.

Answer: A

Explanation:

The requirement is an interactive generative AI experience that can converse with customers and ask clarifying questions (for example: ''What climate are you hiking in?'', ''How many people will share the tent?'', ''What's your budget?'', ''Do you prioritize weight or comfort?''). The best solution component for that conversational, question-and-answer interaction is a chatbot (A), powered by a generative AI model.

A chatbot provides the dialog framework: maintaining conversational context across turns, prompting the user for missing requirements, and responding in natural language. This makes it suitable for customer support, guided shopping assistance, troubleshooting, and pre-sales Q&A---especially when customers don't know exactly what they need and benefit from a guided conversation.

The other options don't match the core requirement. Predictive AI (B) forecasts outcomes (like demand or churn) and isn't inherently conversational. Computer vision (C) analyzes images (like recognizing products from photos) and doesn't address asking questions in dialogue. A recommendation engine (D) can be useful in ecommerce, but it typically suggests items based on behavior or attributes; it doesn't by itself provide a conversational flow that asks users questions and adapts responses in natural language. In practice, you can combine a chatbot with a recommendation engine behind the scenes---but the ''include in the solution'' component that directly satisfies interactive questioning is the chatbot.

Answer: A

Explanation:

Microsoft 365 Copilot is designed to work within the Microsoft 365 ecosystem and use organizational context that is already governed by Microsoft Entra ID, Microsoft 365 permissions, and compliance controls. By default, Copilot can use Microsoft Graph signals and content that exist in Microsoft 365 workloads the user already has access to---most commonly emails, files, meetings, and chats. That corresponds to A.

The key concept is permission-trimming: Copilot doesn't magically gain access to everything; it can only surface or use data that the signed-in user is permitted to access in Microsoft 365. This is what makes Copilot valuable for productivity scenarios---summarizing email threads, drafting replies, generating meeting recaps, creating documents from your files, or pulling context from Teams chats---because those artifacts are already part of daily work and already subject to tenant policies.

The other options are not ''by default'' Microsoft Graph content for Copilot: B (file shares) typically requires additional integration or migration into Microsoft 365 repositories or indexing via connectors; it's not inherently available. C is unrelated to Microsoft 365 tenant work data. D (public web) is not ''information in Microsoft Graph''; web grounding is a separate capability and not the default Graph workload data source referenced here.