AB-731 Microsoft AI Transformation Leader Free Practice Exam Questions (2026 Updated)

Provisioned (PTUs)

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

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

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

The requirement is specific: users must build and use declarative agents that can access work data (tenant data / organizational context). Microsoft’s licensing guidance for Copilot extensibility ties use of declarative agents to having the appropriate Copilot entitlement that enables tenant grounding and organizational data access. In Microsoft’s cost and licensing considerations for declarative agents, Microsoft states that to use a declarative agent, users must have a Microsoft 365 Copilot add-on license (or an equivalent Copilot Chat add-on path tied to eligible licensing). Therefore, among the provided options, the best recommendation is A.

Option B (Copilot Studio user license) is primarily about authoring/building agents in Copilot Studio, but it is not, by itself, the licensing prerequisite that grants end users the right to use those agents with full Microsoft 365 Copilot capabilities and work-data grounding inside the Microsoft 365 Copilot environment. Publishing/building can be separate from the end-user entitlement to use the agent with organizational context.

Option C (Copilot Chat pay-as-you-go) can enable usage-based access to declarative agents in some configurations, but the question asks for the best license recommendation for users who need work-data access through declarative agents. The Microsoft 365 Copilot add-on is the straightforward, fully supported entitlement for that scenario.

Microsoft Copilot Studio is built for creating and managing custom agents that handle employee self-service and business process automation. The two capabilities that align directly to this purpose are D and E.

D is correct because Copilot Studio lets you build agents that connect to enterprise data and systems and then perform actions on behalf of users. This is the foundation for automation and self-service: the agent can answer questions using connected knowledge sources and can also trigger workflows (for example, submitting a request, creating a ticket, checking status, or updating records) through connectors and actions. These integrations allow the agent to move beyond “chat” into real operational outcomes, which is exactly what business process automation requires.

E is correct because Copilot Studio provides the controls needed to customize how an agent behaves and responds. This includes defining conversational topics/flows, setting instructions and guardrails, shaping tone and response style, configuring fallback behavior, and controlling how generative answers are produced (for example, using approved knowledge sources). Customization ensures the agent behaves consistently with company policies and provides reliable employee experiences.

The other choices represent different Microsoft products: A is aligned to security operations tooling (Security Copilot), B relates to information protection/governance (Purview), and C is a Microsoft 365 Copilot capability inside Word/PowerPoint rather than a Copilot Studio feature.

Azure Machine Learning

Forecasting product demand from historical sales data is a predictive analytics / machine learning use case. It typically requires selecting an appropriate forecasting approach (for example, regression, tree-based methods, or time-series models), preparing and splitting historical data, training and validating the model, tuning hyperparameters, and then deploying the model for ongoing inference. The Microsoft service designed to support that end-to-end ML lifecycle is Azure Machine Learning, which is why it correctly completes the sentence.

Azure Machine Learning provides the tooling and infrastructure to: manage datasets, run training jobs on scalable compute, track experiments, compare model performance, register models, and operationalize them through managed endpoints and pipelines. This makes it well-suited for iterative forecasting work, where you may retrain on new data regularly, monitor drift, and update models as product lines, promotions, or seasonality patterns change.

The other options do not directly fit “train a model” for forecasting. Azure AI Search is an indexing/retrieval service used to search and ground generative AI responses, not for training predictive models. Azure OpenAI provides access to large language and multimodal models for generative tasks (drafting, summarizing, Q & A) and is not the primary platform for building classical forecasting models. Microsoft Foundry is a broader platform experience for building and governing AI apps and agents, but the specific service for training a forecasting model on historical sales data is Azure Machine Learning.

Answer Area

Protect personal information and apply strong safeguards to keep data secure. Answer: Privacy and security

Make AI solutions understandable by explaining how and why decisions are made. Answer: Transparency

Design AI solutions that are accessible to people of all abilities and experiences. Answer: Inclusiveness

Involve human oversight in the control of AI solutions. Answer: Accountability

Microsoft’s Responsible AI principles provide a practical framework for building and deploying trustworthy AI systems.

Privacy and security is the principle focused on protecting personal information and ensuring strong safeguards—such as least privilege access, encryption, DLP controls, secure storage, and auditing—so data remains protected throughout collection, processing, and usage.

Transparency is about making AI systems understandable. This includes communicating when AI is being used, explaining system capabilities and limitations, and providing clarity on how outputs are produced (for example, what data sources are used, what assumptions apply, and why certain recommendations are generated). Transparency reduces confusion and helps users calibrate trust appropriately.

Inclusiveness ensures AI solutions are designed to benefit people of diverse abilities, backgrounds, and experiences. Practically, this includes accessibility (assistive technologies, readable outputs), inclusive UX design, and testing across diverse user groups so the solution does not exclude or disadvantage certain populations.

Accountability emphasizes that humans and organizations remain responsible for AI outcomes. Involving human oversight is a direct expression of accountability: setting governance, defining who owns decisions, establishing escalation paths, and ensuring there are controls for review, intervention, and correction when AI outputs are unsafe or incorrect.

Answer Area

Extracting structured data from forms and invoices: Answer: Azure Document Intelligence in Foundry Tools

Summarizing written content from business reports: Answer: Azure Language in Foundry Tools

Generating descriptive text for uploaded images: Answer: Azure Vision in Foundry Tools

These three tasks align to three different Azure AI capability families: document processing, language understanding/generation, and computer vision.

Forms and invoices are semi-structured documents where the business need is to extract specific fields (IDs, names, totals, dates) reliably into structured output. Azure Document Intelligence is designed for intelligent document processing and includes prebuilt models (such as invoices) as well as custom extraction options, making it the correct choice for structured data extraction from documents.

Summarizing written business reports is an NLP task focused on compressing long text into key points, themes, and action items. Azure Language provides language processing capabilities (including summarization features within language service capabilities), so it is the best fit for summarization scenarios.

Generating descriptive text for images (image captioning/description) is a computer vision task. Azure Vision can analyze uploaded images and return descriptions/captions and other visual insights, which directly matches the requirement to produce descriptive text from images.

Answer Area

Prompt engineering changes how a generative AI model was trained. Answer: No

Prompt engineering focuses on designing clear, concise, and context-rich instructions. Answer: Yes

Effective prompt engineering involves maximizing the number of tokens used in each request. Answer: No

No — Prompt engineering does not modify model weights or retrain the model. It is an inference-time technique: you steer outputs by improving the instructions and context you send to the model. Changing how a model was trained would involve pretraining, fine-tuning, or other training methods—separate from prompt engineering.

Yes — The primary goal of prompt engineering is to reduce ambiguity and variability by providing clear instructions, the right context, and explicit output constraints. This often includes specifying role and task, providing necessary facts or grounding text, defining format (bullets, JSON, headings), and adding examples (few-shot) when helpful. Well-constructed prompts improve consistency, relevance, and usefulness of outputs.

No — Good prompt engineering does not mean “use as many tokens as possible.” In fact, using unnecessary tokens can increase cost and may degrade quality by adding noise. Effective prompts are typically as short as possible but as long as necessary: enough context to achieve accuracy and alignment, but not bloated. Token discipline matters because most pricing is token-based and long contexts can dilute attention over what’s most important.