promote the ethical and accountable use of AI.

Microsoft’s Responsible AI principles exist to guide organizations toward trustworthy, ethical, and accountable development and use of AI systems. Among the provided options, “promote the ethical and accountable use of AI” is the most accurate and comprehensive statement because it reflects the purpose of the principles themselves: ensuring AI is built and deployed in a way that respects people, reduces harm, and assigns clear responsibility for outcomes.

The other choices are either too absolute or too narrow. “Ensure that AI models deliver consistent and equitable results” is aspirational but not guaranteed—responsible AI practices reduce bias and improve reliability, but they cannot ensure perfect consistency or equity across all contexts. “Help organizations increase trust in fully autonomous AI systems” is not the intent; responsible AI emphasizes oversight and accountability, not pushing toward full autonomy. “Standardize model development practices across AI teams” can be a side benefit of governance, but it’s not the primary reason to adopt responsible AI principles.

In practice, adopting these principles leads to concrete actions: defining governance and accountability, performing fairness and safety evaluations, protecting privacy and security, being transparent with users, and monitoring systems after deployment. These actions build stakeholder trust and enable sustainable adoption, but the foundational reason is that the principles provide a framework for ethical and accountable AI use.

To align an AI customer support agent with Microsoft’s Responsible AI principles, two high-impact actions are fairness/inclusiveness validation and transparency to users. B is correct because testing for inclusive and culturally sensitive responses directly supports fairness and helps reduce harm. In practice, you evaluate responses across diverse user personas, languages/dialects, accessibility scenarios, and sensitive contexts. You look for biased assumptions, stereotyping, exclusionary language, and disparate quality of service. This also implies ongoing monitoring because model behavior can drift as prompts, knowledge sources, and user inputs evolve.

E is correct because a clear disclaimer supports transparency: customers should know they are interacting with an AI system, understand the type of assistance it can provide, and know what to do if the response is incorrect or they need a human. A disclosure is also a practical risk-control that reduces overreliance and sets expectations about limitations.

The other options are not best for Responsible AI alignment: A (retain all conversations) can conflict with privacy/data minimization; retention must be justified and governed, not automatic. C (operate independently) undermines accountability and human oversight. D (multiple purposes) increases scope and risk rather than improving responsible use.

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.

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

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.

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.

Generative AI is designed to create new outputs, such as text, images, code, summaries, emails, product descriptions, and conversational responses, based on patterns learned from training data and the user’s prompt. Predictive AI is different because it focuses on forecasting outcomes, classifying data, or estimating probabilities from historical patterns, such as predicting customer churn, sales demand, or equipment failure. Generative AI does not necessarily use a smaller dataset, and it does not automatically produce more accurate results than predictive AI. Accuracy depends on data quality, grounding, model design, and validation. The defining distinction is content creation: generative AI produces new material, while predictive AI predicts likely outcomes.

The correct answer is D. Retrieval Augmented Generation (RAG). A pretrained LLM does not automatically know frequently updated proprietary content unless that content is supplied to it during use or the model is retrained. RAG solves this by retrieving relevant, current information from internal documents, knowledge bases, or indexed repositories at runtime and adding that information to the model’s prompt context. This keeps responses grounded in the latest approved business content without changing the model weights. Fine-tuning adapts the model but is more expensive and does not automatically keep up with frequently changing knowledge. Content filtering is a safety control, not a freshness mechanism. Prompt engineering improves instructions, but by itself it does not retrieve current proprietary content.

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.

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.