Free Practice Questions for Microsoft AB-731 Exam

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 Area

A manufacturer can use Azure Vision in Foundry Tools to identify product defects on an assembly line. Answer: Yes

A logistics company can use Azure Vision in Foundry Tools to recognize package shipping labels. Answer: Yes

The HR department at your company can only use Azure Vision in Foundry Tools to extract written content from Microsoft Word files. Answer: No

Azure Vision in Foundry Tools provides computer vision capabilities to analyze images, including identifying visual features and reading text with OCR. Because it is designed to “analyze images” and support vision scenarios, it can be applied to manufacturing quality inspection use cases where the goal is to detect anomalies/defects from images captured on a production line. This aligns with statement 1 being Yes.

Statement 2 is also Yes because recognizing shipping labels is fundamentally text extraction from images (often plus some layout/field parsing). Azure Vision supports optical character recognition (OCR) to read printed text from images, and Microsoft documentation explicitly notes OCR can extract text from images such as product labels and similar real-world text surfaces—making shipping labels a direct fit.

Statement 3 is No because it is incorrectly restrictive. Azure Vision is not limited to extracting written content from Word documents, nor is OCR restricted to Word files. Vision capabilities apply broadly to images (and, depending on the capability, various document/image inputs) for tasks like image analysis and text recognition. HR could use it for many scenarios such as extracting text from scanned images, photos, or other visual inputs—not “only” Word files.

Answer Area

To use Microsoft 365 Copilot Chat, you must have a Microsoft 365 Copilot license. Answer: No

Microsoft 365 Copilot Chat provides context-aware assistance in Microsoft 365 apps. Answer: Yes

Microsoft 365 Copilot Chat can only access information in open files and read emails. Answer: No

No — Microsoft documents and pricing guidance indicate that Copilot Chat is available for eligible Microsoft Entra ID users with a qualifying Microsoft 365 subscription, and that capabilities can vary depending on whether users also have the Microsoft 365 Copilot add-on. In other words, Copilot Chat isn’t universally “Copilot-license required” in all cases; the add-on impacts which premium work features are enabled, but the baseline chat experience can be available without assigning the add-on to every user.

Yes — Microsoft describes Copilot Chat as a side-by-side experience in select Microsoft 365 apps (for example Word, Excel, PowerPoint, OneNote, Outlook) that is aware of the user’s open content, enabling context-aware help such as summarizing, drafting, and Q & A based on what the user is working on.

No — The word only makes this statement inaccurate. Copilot Chat can be grounded in more than just open files and emails (for example, it can also be grounded in the web, and— depending on licensing and configuration—can use agents/connectors for broader scoped tasks). So limiting it strictly to “open files and read emails” is too restrictive compared to how Microsoft positions the feature set.

Responsible AI is fundamentally about earning and maintaining trust while scaling AI across the enterprise. Option C is the best answer because responsible AI practices (fairness, reliability and safety, privacy and security, transparency, accountability, and inclusiveness) reduce reputational, legal, and operational risk and make adoption sustainable over time. When stakeholders trust that AI is governed, tested, and monitored, the organization can expand AI usage confidently across business units.

The other options are incorrect because they make absolute or counterproductive claims. A is false: responsible AI does not “guarantee” accuracy; it reduces risk and improves assurance, but no model can be guaranteed correct in all contexts. B is the opposite of reality: responsible AI increases the importance of data protection and governance; it does not reduce the need for them. D is also incorrect: responsible AI requires clear ownership and oversight, especially from leadership, because accountability is a core principle. In short, responsible AI matters because it builds stakeholder confidence and provides guardrails that support long-term, scalable, and compliant AI adoption—exactly what executives care about when investing in an AI portfolio.

By default, Microsoft 365 Copilot is grounded in your organization’s Microsoft 365 data through Microsoft Graph, and it respects the user’s existing permissions. For “find and summarize information across internal documents,” the most direct default document repositories in Microsoft 365 are SharePoint (team sites and shared libraries) and OneDrive (a user’s work files). That is why C (Microsoft SharePoint) and D (Microsoft OneDrive) are the correct selections. Microsoft explicitly describes Copilot as accessing organizational content via Microsoft Graph, including user documents and related work content.

The other options are not “by default” sources. A (on-premises file share) is not automatically part of Microsoft Graph unless you integrate/migrate content or use connectors to make it discoverable in Microsoft 365 experiences. B (custom CRM) similarly requires an integration approach (for example, Microsoft 365 Copilot connectors / Graph connectors) to index and expose that data for Copilot to use. E (Microsoft Sway) is not a primary default content source for Copilot’s document grounding and is not typically referenced as a core internal document repository compared to SharePoint/OneDrive.

So, for immediate, out-of-the-box internal document discovery and summarization within Microsoft 365, SharePoint + OneDrive are the default answer.

Answer Area

Azure Vision in Foundry Tools can extract and analyze key phrases from PDF files. Answer: No

Azure Vision in Foundry Tools can generate images based on natural language descriptions. Answer: No

Azure Document Intelligence in Foundry Tools can be used to automate the processing of invoices and credit notes. Answer: Yes

No — Azure Vision in Foundry Tools focuses on computer vision tasks such as image analysis and OCR (reading text from images and documents). While it can extract text from scanned PDFs via OCR, key phrase extraction is a natural language processing capability provided by Azure Language in Foundry Tools, not Azure Vision. Key phrase extraction analyzes text to identify main concepts, which is a different service family than vision.

No — Azure Vision can analyze existing images (for example, generate captions/descriptions of an image), but generating new images from a text prompt is a generative model capability (for example, DALL·E through Azure OpenAI/Azure AI Foundry model endpoints), not an Azure Vision feature. Vision describes what it “sees”; it doesn’t synthesize new images from natural language.

Yes — Azure Document Intelligence in Foundry Tools is designed for intelligent document processing, including automating extraction of structured fields from financial documents. Microsoft provides prebuilt models for invoices and supports custom extraction for similar document types, which makes it suitable for automating workflows involving invoices and credit-note style documents (field extraction, validation, routing).

Azure Machine Learning delivers the most strategic value when an organization needs to build, train, evaluate, and operationalize predictive models that improve decisions at scale. Option A is a classic predictive analytics use case: forecasting demand using historical sales across product categories. This typically involves time-series forecasting, feature engineering (seasonality, promotions, macro signals), model training/validation, deployment, and continuous monitoring—exactly the lifecycle Azure Machine Learning is designed to support (ML pipelines, model management, deployment endpoints, and MLOps). Forecasting demand can materially improve inventory optimization, supply chain planning, and revenue outcomes, which is why it’s strategic.

B (digitizing paper processes) is more aligned to workflow automation and document processing (often Document Intelligence + Power Automate), not primarily Azure ML. C is sentiment analysis, which can be solved with prebuilt language services and doesn’t necessarily require custom ML training unless you need a highly specialized classifier. D (location-based personalization) is commonly rules-based or CRM/marketing automation; it may use AI, but it doesn’t inherently require building a custom ML model—unless you’re doing advanced propensity modeling.

Answer Area

The marketing department at your company wants AI to summarize emails and create presentations. Answer: Use Microsoft 365 Copilot

The HR department at your company wants a conversational agent for policy questions and leave requests. Answer: Build with Microsoft Copilot Studio

The manufacturing department at your company wants AI to predict maintenance schedules. Answer: Build with Azure Machine Learning

The finance department at your company wants AI-powered access to enterprise resource planning ERP data by using familiar productivity tools. Answer: Extend with Microsoft 365 Copilot connectors

These scenarios map to four distinct solution patterns: out-of-the-box productivity assistance, low-code conversational agents, predictive ML, and enterprise data integration.

Marketing’s need to summarize emails and create presentations is a core “productivity copilot” use case. Microsoft 365 Copilot is embedded in Outlook, Word, PowerPoint, and Teams, so it directly supports summarization, drafting, and presentation generation without building a custom solution—making Use Microsoft 365 Copilot the best fit.

HR’s requirement is a conversational agent tailored to internal policies and workflows such as leave requests. That typically needs custom dialog, grounded knowledge sources, and possibly actions/workflows. Microsoft Copilot Studio is designed to build and manage such agents with organizational knowledge and business process integration, so Build with Microsoft Copilot Studio fits best.

Manufacturing’s predictive maintenance scheduling is classic predictive analytics: learning patterns from historical telemetry/maintenance data to forecast failures or optimal service windows. This is best addressed with Azure Machine Learning, which supports training, evaluating, and deploying custom predictive models.

Finance wants AI-powered access to ERP data “using familiar productivity tools,” which implies bringing external line-of-business data into the Microsoft 365 Copilot experience. That is precisely where Microsoft 365 Copilot connectors help—indexing and exposing enterprise data sources so Copilot can reference them in a governed way—so Extend with Microsoft 365 Copilot connectors is the best approach.

Answer Area

Allowing AI models to make autonomous decisions supports the Microsoft responsible AI principle of accountability. Answer: No

Regularly testing AI models for fairness and inclusiveness helps ensure they align with Microsoft’s Responsible AI principles. Answer: Yes

Protecting user data and limiting access to personal information supports the Microsoft responsible AI principles of privacy and security. Answer: Yes

Microsoft’s Responsible AI principles emphasize that people and organizations must remain accountable for AI systems and their outcomes. Accountability is strengthened by governance, human oversight, clear ownership, auditability, and processes to review and address issues—not by letting models make unchecked autonomous decisions. Therefore, statement 1 is No: increasing autonomy can actually increase risk unless paired with human-in-the-loop controls and clear escalation paths, because accountability requires clear responsibility for decisions and impacts.

Statement 2 is Yes because fairness and inclusiveness are explicitly supported through ongoing evaluation. Regular testing helps detect disparate impact, performance gaps across user groups, and unintended bias introduced by data drift or changes in usage patterns. It’s not a one-time activity; it’s continuous assurance that the system behaves appropriately as conditions change.

Statement 3 is Yes because privacy and security are directly supported by protecting personal/sensitive data, enforcing least privilege access, and implementing controls such as data loss prevention, encryption, access logging, and strong identity governance. Limiting access to personal information reduces exposure and supports compliance obligations while aligning with privacy-by-design and secure-by-design expectations for AI-enabled solutions.