The requirement describes a predictive analytics / machine learning scenario: using historical data to learn patterns and then predict future outcomes . The Microsoft service that directly supports the end-to-end machine learning lifecycle—data preparation, model training, evaluation, deployment, and MLOps—is Azure Machine Learning , which is why C is the best choice. Azure Machine Learning is explicitly designed to help data scientists and engineers train and deploy models and manage the ML project lifecycle, making it the right fit for building a predictive model from your dataset.

The other options focus on different problem classes: Azure Document Intelligence is for extracting structured data from documents (OCR, key-value pairs, tables), not for general predictive modeling. Azure Content Understanding is for deriving structured insights from multimodal content (documents, images, audio, video) into a user-defined schema; it’s not the primary service for training predictive models from a tabular historical dataset. Microsoft Foundry is a broader platform for building AI apps/agents and orchestrating models/tools, but the specific need here is classical ML training and prediction—handled most directly by Azure Machine Learning.

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.

generative

The sentence describes an AI system that creates new, original content (for example, text, images, audio, code) by learning patterns from large datasets. That is the defining characteristic of generative AI , so “generative” is the correct completion.

To clarify the contrasts: predictive AI primarily uses historical data to forecast outcomes or estimate probabilities (for example, predicting next-quarter sales, predicting equipment failure, or classifying whether a transaction is fraudulent). It focuses on what is likely to happen or which category something belongs to , rather than producing novel content. Prescriptive AI goes a step further by recommending actions or decisions (for example, “increase inventory by X,” “route tickets to team Y,” “schedule maintenance next week”) often using optimization and business constraints.

Generative AI, by comparison, is focused on content synthesis . It identifies statistical patterns and relationships in training data and then generates new sequences that resemble the learned distribution while being responsive to prompts. In business use cases, that translates to drafting emails and documents, summarizing reports, generating meeting notes, creating product descriptions, producing marketing copy, and building chat-based assistants. While all three categories can “recognize patterns,” only generative AI is explicitly characterized by the ability to produce new and original content , which is what the question is testing.

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.

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.

The problem is harmful output language (inappropriate or exclusionary/ableist content). The requirement says you must prevent those responses while minimizing costs . The most cost-effective and direct control is to add a content-moderation filter (B) to screen and block (or rewrite/escalate) responses that violate your safety or inclusion standards. Moderation can be applied at the output stage (and often also at input) without retraining the model, which keeps costs and delivery time low. It also provides an immediate safety layer even if the underlying model occasionally produces biased or exclusionary phrasing.

Option A is not reliable: a newer model version might reduce issues but does not guarantee elimination of ableist language, and you still need policy enforcement. Option C (retraining on only inclusive content) can help, but it is typically expensive (data curation, re-training, re-evaluation, regression testing, re-deployment) and not the “minimize costs” path—also it can reduce coverage/utility if overly restrictive. Option D is clearly wrong because it would amplify the harmful behavior.

In practice, the lowest-cost, high-impact approach is to implement moderation thresholds and handling actions (block, warn, regenerate with constraints, human review) and then, if needed, follow up later with deeper mitigations like prompt constraints, targeted fine-tuning, red-teaming, and continuous evaluation.

Answer Area

A generative AI model guarantees factually accurate responses if the model is trained on a large dataset. Answer: No

Content filtering and responsible AI safeguards help a generative AI model generate safe and inoffensive content. Answer: Yes

A generative AI model always produces fair and unbiased results when the training data has been properly prepared and reviewed for fairness. Answer: No

No — A larger training dataset can improve coverage and fluency, but it does not guarantee factual accuracy. Generative models can still hallucinate, mix concepts, or produce plausible-but-incorrect statements because they generate likely text rather than verifying truth. This is why solution designs commonly add grounding/retrieval, validation, and human review for high-stakes outputs.

Yes — Content filtering and Responsible AI controls are specifically used to reduce harmful, unsafe, or policy-violating outputs . In practice, safeguards include input/output filters, safety classifiers, and governance controls that help enforce safety policies and minimize offensive content. These controls don’t make outputs “perfect,” but they materially reduce risk and are a standard part of production AI deployments.

No — Even with careful data preparation and fairness reviews, models can still produce biased outcomes due to residual bias in data, label/measurement issues, deployment context, and shifting real-world distributions. “Always fair and unbiased” is an absolute claim that is not achievable in real systems; fairness is managed through continuous evaluation, monitoring, and mitigations—not assumed as guaranteed.