AB-731 AI Transformation Leader Questions and Answers

The correct selections are Yes, No, Yes. Microsoft 365 Copilot helps users create, rewrite, summarize, and analyze content in Microsoft 365 apps such as Outlook, Word, Excel, PowerPoint, and Teams. Therefore, it can help compose professional emails and summarize conversations. It can also summarize recent updates across business content such as documents, spreadsheets, and presentations when the user has access to that content. The second statement is false because Copilot is not generally described as autonomously updating business spreadsheets without user control. It can assist with analysis, formulas, summaries, and suggested changes, but autonomous modification of sales data would require governed user action, permissions, and potentially workflow controls. Copilot is an assistant, not an unrestricted autonomous spreadsheet operator.

Even when training data is already consistent and uniform, the first step in building a custom Azure Machine Learning model is still to prepare the training data. “Consistent” data reduces the amount of cleaning you may need, but preparation is broader than cleaning: you still must confirm the schema, validate data types, handle missing values (if any), ensure label quality (for supervised learning), select/engineer features, and split data into training/validation/test sets. Those actions determine whether training will be stable and whether evaluation metrics will be meaningful.

If you skip preparation and go directly to training (C), the model might learn from the wrong columns, inconsistent labels, or poorly partitioned data, producing misleading results. Evaluation (B) comes after training because you need a trained model to score and measure. Hyperparameter tuning (D) is an optimization activity that presupposes you already have a working training pipeline and a baseline model to improve. Deployment (E) is last, after you have validated performance and selected the model candidate.

Azure Machine Learning commonly operationalizes these steps through pipelines, where data preparation is a foundational stage that precedes training and evaluation (and can also be iterated as you refine features and quality).

The strongest privacy risk mitigation for analyzing customer feedback is to minimize personal data exposure while preserving the analytical value of the text. A is best because anonymizing (or de-identifying) the dataset removes direct identifiers (names, emails, phone numbers, addresses, account IDs) and reduces the likelihood of privacy breaches, unauthorized re-identification, or inadvertent leakage in model outputs. This aligns with privacy-by-design and the general principle of data minimization: only retain the information necessary for the business purpose.

B is usually impractical and undermines business value and auditability; organizations often need retention windows for validation, traceability, and improvement. C is not the best privacy mitigation: keeping data attributable to individuals increases privacy exposure; while deletion-on-request is important for compliance, it’s not the primary mechanism to reduce privacy risk during analysis. D is explicitly poor practice; privacy reviews should occur throughout the lifecycle (requirements, design, data acquisition, testing, deployment, monitoring), not only at the end. Therefore, anonymizing/removing PII at the source is the best first-line approach.

Answer Area

Microsoft 365 Copilot connectors enable you to index data from multiple sources to make the data available in Copilot. Answer: Yes

You can build a custom Microsoft 365 Copilot connector when the available connectors do NOT meet your data integration requirements. Answer: Yes

To use Microsoft 365 Copilot connectors, you need a Microsoft Copilot Studio license. Answer: No

Yes — Microsoft 365 Copilot connectors (including synced connectors) are designed to bring external data into Microsoft Graph so it can be semantically indexed and surfaced in Microsoft 365 Copilot experiences. Microsoft explicitly states that synced connectors ingest/crawl content into Microsoft Graph where it’s indexed and then available for Copilot prompts and citations.

Yes — When Microsoft-provided connectors don’t meet integration needs, organizations can create custom connectors (often referred to as Microsoft Graph connectors / custom connector development) to connect other data sources. This is a common extensibility path to index line-of-business repositories and make that content discoverable via Copilot and Microsoft Search.

No — Using Microsoft 365 Copilot connectors does not require a Copilot Studio license. Connectors are generally configured and managed in Microsoft 365 admin/search experiences, and Microsoft’s licensing guidance indicates that users can view connector data in Microsoft 365 Copilot and Microsoft Search with valid Microsoft 365/Office 365 licensing—Copilot Studio licensing is about building agents in Copilot Studio, not a prerequisite to use connectors.

Answer Area

You can use Azure Language in Foundry Tools to analyze the sentiment of customer reviews. Answer: Yes

You can use Azure Language in Foundry Tools to translate internal reports into multiple languages. Answer: No

You can use Azure Language in Foundry Tools to extract text from scanned documents. Answer: No

Azure Language is designed for natural language processing (NLP) over text that is already machine-readable. That includes capabilities like sentiment analysis, key phrase extraction, entity recognition, summarization, and classification. Therefore, statement 1 is Yes: sentiment analysis of customer reviews is a standard NLP workload where the service scores text as positive/negative/neutral (and often provides confidence scores), helping organizations quantify customer satisfaction and detect recurring issues.

Statement 2 is No because translation is typically handled by a dedicated translation capability (commonly delivered as a separate translator service) rather than the core “Language” NLP features. While translation is an AI language workload, it’s not what the Azure Language service is primarily used for in this context; the expected Microsoft service choice for multi-language translation is the translator capability, not Azure Language.

Statement 3 is No because extracting text from scanned documents is OCR (optical character recognition), which is a computer vision/document processing function. OCR is delivered through Azure Vision and/or Azure Document Intelligence, which can read printed/handwritten text from images and PDFs and return structured output. Azure Language can analyze extracted text after OCR, but it does not perform the image-to-text extraction step itself.

uses reasoning capabilities to generate deep insights based on organizational data and the web.

The sentence is best completed by the option describing Researcher as a research-oriented reasoning agent that combines information from the web and your work data to produce deeper insights. Microsoft describes Researcher as an agent built into Microsoft 365 Copilot to tackle complex, multistep research and to help users gather, analyze, and summarize information from “the web, your work documents, or both,” producing a structured output that supports decision-making. That is exactly what the completion “uses reasoning capabilities to generate deep insights based on organizational data and the web” captures.

The other dropdown options are better matches for different tools/agents: “creates visual dashboards from structured data in Excel and Power BI” is more aligned to BI/reporting workflows; “generates a pivot table and performs time series forecasting” is spreadsheet/analytics functionality; and “performs complex, multi-step, data analysis and code execution tasks over arbitrary datasets” is the hallmark positioning of the Analyst agent (“virtual data scientist”) rather than Researcher. Researcher’s differentiator is deep research across both organizational context and the open web, while Analyst’s differentiator is data analysis and computation.

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.

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.

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.

The correct answer is A. Microsoft Security Copilot. The requirement is clearly a security operations scenario: analysts must investigate incidents across endpoint, identity, cloud, and security operations data. Microsoft Security Copilot is designed for security teams and supports natural-language investigation, alert summarization, incident context, affected-resource identification, and recommended response actions. Microsoft 365 Copilot is focused on productivity tasks such as drafting, summarizing, and analyzing content in Microsoft 365 apps. Azure Document Intelligence extracts structured information from documents such as forms and invoices. Microsoft Copilot Studio is used to build and customize agents for business workflows. Because the scenario centers on security incident investigation and response guidance, Microsoft Security Copilot is the correct solution.

Microsoft Graph

Microsoft 365 Copilot connectors (built on Microsoft Graph connectors) are used to bring external, line-of-business content into the Microsoft 365 ecosystem by ingesting it into Microsoft Graph. Once connected, the content can be indexed and made discoverable through Microsoft Search and available for Copilot experiences, enabling users to use natural language prompts to find and summarize relevant LOB information—subject to permissions and governance controls.

The other choices don’t match how Copilot connectors are positioned. Azure AI Search is an Azure indexing/retrieval service used in custom RAG solutions, but Microsoft 365 Copilot connectors are specifically designed to surface external content through Microsoft 365 experiences via Graph. Microsoft Purview focuses on data governance, compliance, and risk management rather than being the primary ingestion target for Copilot connector content. SharePoint can store content, but the connector model is about indexing external systems into Microsoft Graph so the content becomes searchable and usable across Microsoft 365, not merely placing it into SharePoint as the destination.

So the correct completion is Microsoft Graph because that is the foundational data and indexing fabric Copilot uses to reason over organizational content with appropriate permission trimming.

The correct answer is data security. The principle of least privilege means users, apps, and services receive only the minimum access required to perform their work. Microsoft 365 Copilot respects existing Microsoft 365 permissions and does not grant users new access to content they are not already authorized to view. That behavior is a security control because it helps prevent unauthorized access to company information. Data classification is about labeling or categorizing information by sensitivity. Data compliance focuses on meeting policy, legal, or regulatory requirements. Data loss prevention helps prevent sensitive information from being shared inappropriately. Least privilege is primarily an access-control practice, so the best category is data security.

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.

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).

Answer Area

Retrieval Augmented Generation (RAG) architectures require that a large language model (LLM) be retrained on proprietary data. Answer: No

Retrieval-Augmented Generation (RAG) grounds a language model to produce more factual and context-relevant responses. Answer: Yes

Retrieval Augmented Generation (RAG) retrieves information from external knowledge sources at runtime instead of relying solely on the knowledge of a generative AI model. Answer: Yes

1) No — RAG does not require retraining or fine-tuning the base LLM on proprietary data. The defining idea of RAG is to keep the model as-is and instead supply it with relevant context retrieved from trusted sources at inference time. Fine-tuning can be optional for style or specialized behavior, but it is not a requirement for RAG.

2) Yes — RAG is a grounding approach. By retrieving authoritative passages (policies, manuals, product specs, internal knowledge bases) and injecting them into the prompt context, the model’s answer is constrained by evidence that is relevant to the user’s question. This improves factuality and domain relevance and helps reduce hallucinations.

3) Yes — RAG explicitly depends on runtime retrieval from external knowledge sources, such as indexed documents, databases, or enterprise repositories. The retrieval layer finds the best matching content for the query, and the generation layer uses that retrieved content to craft the response. This is why RAG is valuable when information changes frequently: you update the source documents/index rather than retraining the LLM.

Overall, RAG is best understood as an architecture pattern that combines search/retrieval + generation, improving accuracy and freshness without the cost and risk of retraining the underlying model each time the knowledge base changes.

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.

Answer Area

Microsoft 365 Copilot enables users to search across emails, files, chats, meetings, and connected apps, by using natural language queries. Answer: Yes

Microsoft 365 Copilot provides data protection, and helps ensure that user prompts and chat data are secure. Answer: Yes

Microsoft 365 Copilot is included in all Microsoft 365 subscriptions. Answer: No

Yes — Microsoft 365 Copilot is grounded in Microsoft 365 content through Microsoft Graph and is designed to help users find and summarize information across their work context (emails, files, chats, meetings). With extensions/connectors, Copilot can also incorporate information from connected apps, allowing users to query using natural language and get summarized, actionable outputs.

Yes — A key enterprise benefit of Microsoft 365 Copilot is that it operates within the Microsoft 365 security, identity, and compliance boundary. It respects existing permissions (users only get content they are authorized to access) and supports organizational controls intended to protect prompts and generated content. This is part of the business value compared to consumer tools: IT can apply policies, auditing, and compliance controls to reduce data risk.

No — Microsoft 365 Copilot is not automatically included in every Microsoft 365 subscription. In most business scenarios it is licensed as an add-on (or separate Copilot entitlement) for eligible Microsoft 365 plans, meaning it requires explicit licensing rather than being universally bundled with all subscriptions.

The correct answer is D. Microsoft Copilot Studio. The requirement is to create an AI assistant for a public customer support portal that can answer customer questions and initiate follow-up actions with minimal development effort. Microsoft Copilot Studio is designed for building custom agents using a low-code approach. It can connect to knowledge sources, provide generative answers, define conversation behavior, and trigger actions through connectors or workflows. Microsoft 365 Copilot Chat is intended for workplace productivity and organizational users, not public customer support portals. Microsoft Security Copilot is for security operations and incident investigation. Microsoft 365 Copilot connectors only make external data available to Copilot experiences; they do not by themselves create a public-facing customer support assistant.

improves the accuracy and reliability of the predictions and outputs of AI.

High-quality grounding data improves a generative AI solution by anchoring responses to trusted, relevant, and up-to-date information, which increases the likelihood that outputs are accurate, consistent, and aligned with the organization’s expectations. This is why the best completion is “improves the accuracy and reliability of the predictions and outputs of AI.” When the model is given authoritative context (for example, approved policy text, product specifications, knowledge base articles, or controlled enterprise content), it has less need to “guess” based on general patterns in its training data. That reduces hallucinations and improves response relevance to the user’s question and the business domain.

It does not “ensure that all responses are factually accurate” because grounding reduces errors but cannot eliminate them completely—retrieval can return incomplete or irrelevant passages, user prompts can be ambiguous, and the model can still misinterpret context. It also does not inherently “increase performance of an AI model” in the sense of speed/throughput or model capability; grounding is an architecture and data strategy that improves output quality, not compute efficiency. Finally, grounding is not about “increasing storage required to host an AI model.” While you may store documents in an index or repository, the core benefit is improved response quality through better context, not larger model hosting requirements.

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.

Grounding is an AI solution pattern used to improve response quality by ensuring the model’s output is based on trusted, relevant information provided at inference time, rather than relying only on what the model “remembers” from training. Therefore, C is correct: grounding anchors responses in specific data sources .

In practical deployments, grounding commonly uses retrieval (often called Retrieval Augmented Generation, or RAG) where the system first finds relevant content from approved sources—such as internal policy documents, product documentation, knowledge bases, or databases—and then includes that content in the prompt context sent to the model. Microsoft’s guidance describes grounding data as information supplied at inference time to help responses become more accurate and relevant because the model is guided by authoritative, up-to-date content that may not have been part of original training.

The other options do not define grounding. A relates to inclusion practices and diversity considerations, which are important for responsible AI but are not what grounding means. B describes transparency/explainability concepts. D relates to model evaluation/communication of limitations. Grounding is specifically about tying outputs to known sources, which reduces hallucinations and improves business trust in the generated responses.

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.

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.

Option A is a single use case (translation), not the defining description. Option B describes predictive analytics/forecasting, which is a different AI category focused on outcomes and probabilities rather than content creation. Option D describes recommendation systems, typically driven by ranking/behavioral signals; while AI can enhance recommendations, that is not the core definition of generative AI. Therefore, the most accurate and relevant description for stakeholders is C.

The correct answer is A. transparency. Transparency means users and stakeholders should understand when AI is being used, what the AI system can do, what its limitations are, and how important outputs or decisions were produced. In this scenario, applicants can request an explanation for why a loan application was denied. That explanation capability makes the AI-assisted decision more understandable and reviewable, which directly supports transparency. Fairness is related to avoiding unjust bias or discriminatory outcomes. Privacy and security focus on protecting personal and organizational data. Inclusiveness focuses on ensuring AI systems work for people with different abilities, backgrounds, and experiences. Because the scenario is specifically about explaining a decision, the best answer is transparency.

The correct selections are Yes, No, Yes. Prompt engineering is the practice of designing clear and effective inputs that guide a generative AI model toward relevant, accurate, and useful output. Guidelines, constraints, role instructions, tone requirements, and output-format rules are all common prompt-engineering techniques, so statement A is true. Statement B is false because examples are normally considered examples or few-shot demonstrations, not the instruction itself. The instruction tells the model what task to perform, while examples demonstrate the preferred pattern or output style. Statement C is true because context supplies the background information, source material, business scenario, audience, or constraints the model should use when generating the answer. Strong prompts usually combine instruction, context, constraints, and examples.