Microsoft AB-731 Exam Questions

To reduce Azure OpenAI costs with minimal quality loss, you target the biggest cost drivers: token usage and model price per token (or throughput unit). C (Optimize the prompts) is a best practice because shorter, clearer prompts reduce unnecessary input tokens and often reduce output length by tightening instructions and formatting. Prompt optimization can preserve or even improve quality by removing ambiguity, adding constraints, and using compact context (for example, only the most relevant grounding passages). Lower token consumption directly lowers cost while maintaining response usefulness.

D (Switch to an alternate model) is also effective because different models have different price/performance tradeoffs. Moving from a premium model to a more cost-efficient model (or a smaller variant) can significantly reduce spend. You can minimize quality impact by validating outputs on representative scenarios and using a tiered approach (cheap model by default, expensive model only for complex cases).

The other options are less aligned to the goal. A (Fine-tune) typically increases cost (training and ongoing evaluation) and is not the first-line cost reducer. B (Content moderation) is primarily a safety control; it can add overhead and doesn't directly reduce token costs. E (Decrease hosting hours) applies to capacity-based hosting scenarios, but the question states a prebuilt Azure OpenAI model for content generation---cost reduction is best achieved by prompt/token optimization and selecting the right model.

The requirement is explicit: users must have access to the Researcher agent in Microsoft 365 Copilot and use it to search across organizational content stored in SharePoint. Microsoft's licensing guidance for Researcher indicates that Researcher is available to Microsoft 365 business and enterprise users who have a Microsoft 365 Copilot add-on license (and also to certain consumer ''Microsoft 365 Premium'' subscriptions).

That maps directly to option C. The Researcher agent is part of the Microsoft 365 Copilot experience for work tenants; it is not enabled merely by having a baseline Microsoft 365 subscription entitlement (B). Baseline subscriptions can provide access to Microsoft 365 apps and content repositories (like SharePoint/OneDrive), but the Researcher agent itself is a Copilot capability that requires the Copilot add-on to unlock.

Option A (pay-as-you-go) and D (usage-based consumption license in Azure) describe consumption models that apply to Azure services or agent metering in some scenarios, but they are not the standard licensing requirement to enable the built-in Researcher agent for Microsoft 365 Copilot users. When the goal is to enable Researcher inside Microsoft 365 Copilot for staff, the practical and correct recommendation is to assign the Microsoft 365 Copilot per-user add-on license to the users who need it, ensuring their SharePoint access is already properly permissioned and governed.

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.

Azure AI Search provides an indexing and retrieval layer that makes large, distributed document collections searchable in a consistent way. The key benefit in an information discovery scenario is that it can index content from many sources and then retrieve relevant documents/passages using rich query capabilities, including natural language-style queries and semantic ranking. That directly aligns with B.

This retrieval capability is foundational for RAG architectures: the system uses Azure AI Search to find the best matching content, then supplies those results to a generative model so the answer is grounded in organizational knowledge. That improves relevance and reduces hallucinations because the model is guided by retrieved evidence.

Option A is the opposite of what you want---Search is used precisely to reference existing data. C is more aligned to workflow automation platforms (Logic Apps/Power Automate) and document processing services. D describes fine-tuning, which is a different approach; Azure AI Search improves discovery and grounding through retrieval, not by changing model weights.

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.