Free Microsoft AI Transformation Leader AB-731 Exam Questions

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.

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.

Preventing generative AI from accessing confidential or classified information is primarily a data access and classification control problem. The most effective broad solution is data governance (B)---the framework of policies and controls that ensures sensitive content is identified, classified, protected, and access is restricted using least privilege. Data governance includes information classification/sensitivity labels, access control reviews, secure sharing practices, data loss prevention (DLP), and auditing---controls that directly limit what data is available to the AI through permission trimming and policy enforcement.

An information barrier (A) policy is more specific: it's intended to prevent communication and collaboration between defined user groups (often for regulatory/ethical walls). It does not comprehensively address document classification or restrict AI access to sensitive files across the tenant. A data retention policy (C) governs how long content is kept and when it's deleted; it's not a primary access-prevention mechanism. Communication monitoring (D) is a detection/oversight control; it can help identify risky activity, but it does not itself prevent access to confidential content by the AI.

Therefore, to prevent AI from surfacing confidential/classified data during summarization and analysis, you should recommend data governance as the primary control layer.

For a proof of concept, the key requirements are low commitment, quick start, and the ability to scale up or down as you learn what real usage looks like. Azure OpenAI Standard On-Demand pricing is designed for exactly that: you pay per token consumed (input and output) on a pay-as-you-go basis, which makes it ideal when demand is uncertain or variable---typical in early pilots and PoCs.

By contrast, Provisioned (PTUs) is best when you have well-defined, predictable throughput and latency requirements---usually a more mature, production workload. PTUs involve reserving model processing capacity to achieve consistent performance and more predictable costs, which is usually premature for a PoC where actual traffic patterns are not yet known.

Batch API is optimized for asynchronous high-volume jobs with a target turnaround (for example, up to 24 hours) and discounted pricing. That's great for offline processing, but it does not match an interactive ''agent'' PoC that typically needs near-real-time responses and iterative testing.

Microsoft 365 Copilot is a separate SaaS licensing model and is not the Azure OpenAI pricing model for building your own agent solution.

To establish governance principles for AI use, your company needs two key actions:

1. Establish an AI governance framework: This involves creating comprehensive policies, standards, and guidelines that define how AI should be used responsibly within the organization. This framework should align with company values and ensure ethical use of AI technologies.

2. Conduct regular audits and assessments: Governance is not a one-time effort. Regular audits and assessments ensure that AI systems remain compliant with regulatory requirements and company values over time. This includes monitoring for bias, performance, security, and compliance issues.

These two actions work together to create a systematic approach to responsible AI governance that addresses both the initial framework and ongoing compliance verification.

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.

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.

For a proof of concept (PoC) project using Azure OpenAI that needs to start small with flexibility to scale, Provisioned throughput is the recommended pricing model.

Why Provisioned Throughput:

• Cost-effective for PoCs: You can start with a small provisioned capacity allocation and scale up as demand grows without disrupting service
• Predictable costs: You pay for reserved capacity, making budgeting more predictable during the PoC phase
• Scalability: As the PoC validates success and usage increases, you can provision additional throughput without changing your application code
• Flexibility: Unlike pay-as-you-go models, provisioned throughput allows you to reserve capacity in advance and adjust allocations as needed

This approach is ideal for PoCs because it balances cost control with the ability to scale up smoothly when the solution proves successful.

Microsoft Foundry is positioned as a unified, enterprise-grade platform that helps organizations build, deploy, scale, and govern AI apps and agents---especially generative AI solutions that need to work with business context and internal data. That directly aligns with A: Foundry provides a scalable platform for developing and deploying generative AI solutions. Microsoft describes Foundry as an interoperable platform that makes it easier to build, deploy, and scale AI apps and agents, while also providing centralized security and governance features for organizations.

B is incorrect because Foundry does not remove model choice/configuration; in fact, it supports selecting among models and using tools/frameworks to build solutions. You still choose appropriate model(s), configure endpoints, and design grounding and safety controls.

C and D are not the best characterization of Foundry's primary benefit. While Foundry offers ''friendly interfaces,'' Microsoft primarily positions it for developers, model builders, and enterprise AI operations---not as a low-code platform for business users (that role is more commonly filled by Copilot Studio/Power Platform).

Generative AI's defining characteristic is that it creates new content (text, images, code, summaries, drafts) in response to instructions---most commonly natural language prompts. Option C captures that general-purpose description in a stakeholder-friendly way: users provide prompts and the system generates responses or content. This framing is broad enough to cover common business value scenarios such as summarizing documents, drafting communications, creating marketing copy, generating reports, building assistants, and producing structured outputs from unstructured requests.