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.

A common reason models degrade after being successful in production is data drift (also called concept drift). Over time, the distribution of input data changes —for example, customer behavior shifts, product catalog changes, seasonality changes, new categories appear, sensors get recalibrated, or business processes evolve. When the model sees data that differs from what it was trained on, its predictions can become less accurate. This is exactly what option A describes and is the most likely “six months later” cause.

Option B is not a primary explanation for reduced predictive accuracy. More compute can improve throughput/latency, but it does not inherently improve correctness of predictions. If anything, compute constraints typically cause timeouts or slower responses, not a systematic accuracy drop.

Option C (trained incorrectly) would usually manifest earlier—poor performance from the start—unless the “incorrectness” is that the model was trained on a snapshot that later became stale (which again maps back to drift). The correct operational response is to monitor for drift, validate performance regularly, and retrain/refresh the model using newer representative data and updated features/labels.

Enterprise AI adoption succeeds when it is cross-functional from the start . Option A is best practice because AI impacts legal risk, privacy, security, compliance, workforce processes, and business strategy—not just technology. Including leadership ensures alignment to priorities and funding; including business units ensures use cases and success metrics are real; including legal/compliance ensures responsible AI and regulatory obligations are addressed early. This prevents rework and reduces the chance of deploying solutions that are misaligned with policy or unacceptable risk.

Options B and C delay governance and business alignment, which often leads to “build first, govern later” failure modes—solutions that work technically but cannot be approved or scaled due to privacy/security gaps or unclear accountability. Option D over-optimizes for vendor selection without ensuring the organization has defined responsible AI requirements, target use cases, and operating model. Procurement is important, but it is not the primary driver of a successful adoption team. The most sustainable approach is a representative adoption team that integrates business, technical, and governance stakeholders from day one.

This scenario is a clear violation of the fairness principle. Fairness in Microsoft’s Responsible AI framework is about ensuring AI systems do not create unjustified bias or discriminatory outcomes—especially when decisions affect people’s access to opportunities such as credit, employment, housing, or education. A rule or learned behavior that rejects all applicants over a certain age creates a systematic, categorical disadvantage for a protected demographic group and indicates a discriminatory decision boundary rather than an individualized assessment of creditworthiness.

Even if the model designers believed age correlates with risk, using a hard cutoff that rejects every applicant older than 60 is not an equitable approach. It suggests the model is either using age directly as a dominant feature or reflects biased training data/labels that encoded discriminatory outcomes. Fairness requires you to evaluate model outcomes across groups (for example, age brackets), measure disparate impact, and apply mitigations such as feature review (removing or constraining sensitive attributes), rebalancing training data, adjusting thresholds, or using fairness-aware training/evaluation methods. It also requires governance and review of high-stakes automated decisions.

The other principles are not the best match: transparency concerns explainability and user understanding, accountability concerns human oversight and ownership, and reliability and safety concerns consistent and safe operation. The core issue here is discriminatory treatment across an age group— fairness .

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.

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.

Answer Area

Retrieval Augmented Generation RAG requires model fine-tuning. Answer: No

Retrieval Augmented Generation RAG is helpful when you need a generative AI solution that can access current, verifiable information. Answer: Yes

Retrieval Augmented Generation RAG enables you to get more relevant responses based on your organization’s documents without retraining the base model. Answer: Yes

RAG is an architecture pattern that improves generative AI responses by retrieving relevant information from external knowledge sources (for example, a document index, database, or knowledge base) and injecting that information into the model’s prompt/context at runtime.

No — RAG does not inherently require fine-tuning. Fine-tuning changes the model weights. RAG, instead, keeps the base model as-is and augments it with retrieved context. Fine-tuning can be complementary (for style, domain tone, or specialized tasks), but it is not required for RAG to work.

Yes — RAG is especially valuable when you need current and verifiable information because the retrieval layer can pull the latest approved content (updated policies, product specs, incident runbooks) and provide it to the model. This reduces hallucinations and makes answers traceable to known sources.

Yes — A major benefit of RAG is improved relevance to organizational documents without retraining. Instead of rebuilding the model whenever documents change, you update the underlying content store/index; the model then generates responses grounded in the retrieved passages, producing answers that align with your organization’s latest information and terminology.