AB-731 Sample Questions Answers

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.

Answer Area

Microsoft Copilot in Outlook can automatically send follow-up replies to emails. Answer: No

Microsoft Copilot in Outlook can identify and surface tasks mentioned in your emails. Answer: Yes

Microsoft Copilot in Outlook can summarize long email threads and highlight action items and deadlines. Answer: Yes

1) No — Copilot in Outlook can draft email responses and help you take actions, but sending messages is not positioned as an automatic “follow-up reply” behavior. Microsoft describes capabilities such as “Draft with Copilot” (generating email drafts from prompts) and Copilot chat actions that update the mailbox, which implies user-directed execution rather than autonomous follow-up sending.

2) Yes — Copilot supports contextual help over your inbox and can help you “catch up” and understand what’s due, which includes surfacing action-oriented items from recent communications. This aligns with using Copilot to pull together summaries of email messages and identify what requires attention.

3) Yes — Microsoft explicitly documents email-thread summarization in Outlook: Copilot scans a conversation and produces a summary of key points. Microsoft also describes Copilot’s summarization capability as extracting key points from threads, which is commonly used to surface what matters most (including actions to take) when the thread is long.

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.

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.

The correct answer is B. Testing the AI solution to identify and mitigate unfair or inconsistent outcomes directly supports Microsoft responsible AI principles, especially fairness, reliability and safety, accountability, and inclusiveness. Before deployment, organizations should evaluate whether the system behaves consistently across different user groups, avoids discriminatory outcomes, and produces safe and reliable outputs. Automatically approving or rejecting loan applications increases risk unless strong governance and human oversight are in place. Collecting personal data can increase privacy exposure if it is not necessary and controlled. Prioritizing model performance alone is also insufficient because a technically accurate model can still produce biased, unsafe, or non-transparent outcomes. Responsible AI requires evaluation, mitigation, oversight, and monitoring.

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

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.

The requirement is specific: users must build and use declarative agents that can access work data (tenant data / organizational context). Microsoft’s licensing guidance for Copilot extensibility ties use of declarative agents to having the appropriate Copilot entitlement that enables tenant grounding and organizational data access. In Microsoft’s cost and licensing considerations for declarative agents, Microsoft states that to use a declarative agent, users must have a Microsoft 365 Copilot add-on license (or an equivalent Copilot Chat add-on path tied to eligible licensing). Therefore, among the provided options, the best recommendation is A.

Option B (Copilot Studio user license) is primarily about authoring/building agents in Copilot Studio, but it is not, by itself, the licensing prerequisite that grants end users the right to use those agents with full Microsoft 365 Copilot capabilities and work-data grounding inside the Microsoft 365 Copilot environment. Publishing/building can be separate from the end-user entitlement to use the agent with organizational context.

Option C (Copilot Chat pay-as-you-go) can enable usage-based access to declarative agents in some configurations, but the question asks for the best license recommendation for users who need work-data access through declarative agents. The Microsoft 365 Copilot add-on is the straightforward, fully supported entitlement for that scenario.

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.

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

When AI adoption spans multiple business units, the primary risk is fragmented delivery: inconsistent standards, duplicated spend, uneven risk controls, and misalignment with enterprise strategy. Establishing an AI council (D) is the best approach because it creates a cross-functional governance mechanism that aligns AI initiatives to business priorities while enforcing Responsible AI practices consistently.

An AI council typically includes senior stakeholders from business leadership, IT, security, legal, compliance, privacy, data, and HR. Its role is to define AI principles and guardrails, approve high-impact use cases, set policy for data usage and access, establish evaluation and monitoring requirements, and coordinate change management and training. This also enables portfolio management—deciding which projects to prioritize, reuse, or stop—so AI investments map to measurable business outcomes.

The other options are weaker: A encourages siloed deployments and inconsistent risk management. B centralizes too narrowly in IT; Responsible AI requires broader accountability than a single function. C can help delivery capacity but does not replace internal governance; vendors still need direction, controls, and oversight from the organization.

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.

crafting clear instructions to guide generative AI solutions in generating context-appropriate content.

Prompt engineering is fundamentally about how you communicate intent to a generative AI model so it produces outputs that meet business expectations. The best completion is “crafting clear instructions to guide generative AI solutions in generating context-appropriate content” because it captures the practical, day-to-day discipline: shaping the input (prompt) with the right task framing, constraints, context, and output format.

In real deployments, prompt engineering includes specifying the role and objective (for example, “act as a customer support agent”), providing the necessary context (product details, policy excerpts, audience), adding explicit requirements (tone, length, must/must-not statements), and defining structured output (JSON fields, bullet sections, headings). It can also include adding examples (few-shot prompting), clarifying what to do when information is missing, and instructing the model to cite only provided sources or to ask follow-up questions. These techniques reduce ambiguity, improve consistency, and lower the risk of hallucinations or off-brand responses.

The other options are not accurate definitions. “Integrating AI-powered tools into business workflows” describes solution adoption/integration, not prompt engineering. “Identifying and fixing errors in AI-generated content” is review/editing or quality assurance. “Designing, developing, and training generative AI models” is model development/ML engineering. Prompt engineering operates without changing model weights ; it’s about steering model behavior through well-constructed instructions and context.

Azure Machine Learning delivers the most strategic value when an organization needs to build, train, evaluate, and operationalize predictive models that improve decisions at scale. Option A is a classic predictive analytics use case: forecasting demand using historical sales across product categories. This typically involves time-series forecasting, feature engineering (seasonality, promotions, macro signals), model training/validation, deployment, and continuous monitoring—exactly the lifecycle Azure Machine Learning is designed to support (ML pipelines, model management, deployment endpoints, and MLOps). Forecasting demand can materially improve inventory optimization, supply chain planning, and revenue outcomes, which is why it’s strategic.

B (digitizing paper processes) is more aligned to workflow automation and document processing (often Document Intelligence + Power Automate), not primarily Azure ML. C is sentiment analysis, which can be solved with prebuilt language services and doesn’t necessarily require custom ML training unless you need a highly specialized classifier. D (location-based personalization) is commonly rules-based or CRM/marketing automation; it may use AI, but it doesn’t inherently require building a custom ML model—unless you’re doing advanced propensity modeling.

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 correct answer is D. predicting customer retention. Azure Machine Learning is best suited for predictive analytics scenarios where historical data is used to train a model that predicts future outcomes. Customer retention prediction typically uses customer behavior, purchase history, engagement data, service interactions, churn signals, and account attributes to estimate whether a customer is likely to stay or leave. That is a classic machine learning use case. Generating marketing campaigns and summarizing customer service transcripts are generative AI or natural language processing tasks. Creating product descriptions from images is a multimodal or generative AI scenario. The wording “predicting” is the key indicator: when the business requirement is to forecast outcomes from patterns in data, Azure Machine Learning is the correct fit.

Answer Area

A generative AI solution is well-suited to predict next-quarter sales trends. Answer: No

A generative AI solution can summarize lengthy policy documents. Answer: Yes

A generative AI solution can create product descriptions from product specifications. Answer: Yes

No — Predicting next-quarter sales trends is primarily a forecasting/predictive analytics problem. Microsoft differentiates predictive AI (forecasting outcomes from historical patterns) from generative AI (creating content like text, images, or code). While you can use LLMs to assist analysts (explain trends, draft narratives), the core forecasting model is typically traditional ML/time-series methods rather than generative AI as the main engine.

Yes — Summarization is a classic, high-value generative AI capability. Given a long policy, an LLM can compress it into executive summaries, key obligations, risks, and action items, often with formatting constraints (bullets, sections, “do/don’t” lists). Microsoft highlights summarization and analysis as common generative AI use cases in business contexts.

Yes — Generative AI is well-suited to transform structured inputs (features/specs) into natural-language outputs (product descriptions). This is straightforward “content generation,” where you control tone, length, and required fields (benefits, differentiators, disclaimers). Microsoft also points to generating product descriptions and similar marketing/customer-facing text as a practical generative AI scenario.

Answer Area

A text-to-image generator can be used to translate content into other languages. Answer: No

A predictive analytics model can generate new marketing content for a company’s online ads. Answer: No

A generative AI chatbot can engage customers in personalized conversations and recommend products. Answer: Yes

No — A text-to-image generator’s primary function is to create images from text prompts , not translate text between languages. Translation is a natural language processing task typically handled by language models or dedicated translation services. A text-to-image model could illustrate translated content (e.g., generate an image based on a translated prompt), but it is not the tool used to perform the translation itself.

No — Predictive analytics models are designed to predict outcomes (forecasts, probabilities, classifications) from historical patterns, such as predicting click-through rate, churn, or next-quarter demand. They are not designed to create new ad copy or marketing creatives. Generating new marketing content is a generative AI capability (text generation), not predictive analytics.

Yes — A generative AI chatbot is well-suited to interactive, natural-language conversations . With access to product catalogs and business rules, it can ask clarifying questions, tailor responses to customer needs, and recommend products (for example, suggesting tents based on group size, season, and budget). This combines conversational generation with retrieval/recommendation logic behind the scenes, enabling personalized customer engagement at scale.

Answer Area

Using incomplete or poor-quality data during generative AI model training can increase costs. Answer: Yes

AI models rely on training data to learn patterns and identify relationships to produce outputs. Answer: Yes

Generative AI models trained on non-representative datasets can produce inaccurate or unbalanced results. Answer: Yes

Yes — Poor-quality or incomplete training data increases cost because it drives more iterations: additional data cleaning, relabeling, re-training, and re-evaluation to reach acceptable performance. It can also increase operational costs after deployment if the model produces low-quality outputs that require human rework, escalations, or incident handling. In practice, data quality debt becomes model cost debt.

Yes — Training data is the primary mechanism by which AI models learn statistical patterns and relationships. For generative models, the training corpus shapes language fluency, factual associations, style tendencies, and the kinds of content the model can produce. Without sufficient and appropriate training signals, outputs degrade.

Yes — If the training dataset is not representative of the real-world population or business context, the model can systematically underperform for certain groups, topics, or edge cases. This can manifest as biased language, missing perspectives, and uneven accuracy, producing “unbalanced” results. That is why Responsible AI practice emphasizes representative data, evaluation across slices, and continuous monitoring.

Answer Area

Protect personal information and apply strong safeguards to keep data secure. Answer: Privacy and security

Make AI solutions understandable by explaining how and why decisions are made. Answer: Transparency

Design AI solutions that are accessible to people of all abilities and experiences. Answer: Inclusiveness

Involve human oversight in the control of AI solutions. Answer: Accountability

Microsoft’s Responsible AI principles provide a practical framework for building and deploying trustworthy AI systems.

Privacy and security is the principle focused on protecting personal information and ensuring strong safeguards—such as least privilege access, encryption, DLP controls, secure storage, and auditing—so data remains protected throughout collection, processing, and usage.

Transparency is about making AI systems understandable. This includes communicating when AI is being used, explaining system capabilities and limitations, and providing clarity on how outputs are produced (for example, what data sources are used, what assumptions apply, and why certain recommendations are generated). Transparency reduces confusion and helps users calibrate trust appropriately.

Inclusiveness ensures AI solutions are designed to benefit people of diverse abilities, backgrounds, and experiences. Practically, this includes accessibility (assistive technologies, readable outputs), inclusive UX design, and testing across diverse user groups so the solution does not exclude or disadvantage certain populations.

Accountability emphasizes that humans and organizations remain responsible for AI outcomes. Involving human oversight is a direct expression of accountability: setting governance, defining who owns decisions, establishing escalation paths, and ensuring there are controls for review, intervention, and correction when AI outputs are unsafe or incorrect.

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.

Answer Area

Content filtering controls can prevent AI-generated responses from exposing confidential and sensitive information. Answer: Yes

AI-generated content can unintentionally reveal sensitive information if the generative AI model has access to unsecured data sources. Answer: Yes

To prevent data exposure, only the prompts used by users must be protected by using policies. Answer: No

Yes — Content filtering (and related safety controls) can help reduce the chance that responses contain policy-violating or sensitive outputs by detecting and blocking certain categories of content. While filtering is not a perfect guarantee, it is a recognized control to prevent or reduce exposure risk in outputs (for example, blocking regulated data patterns, disallowed content categories, or unsafe disclosures).

Yes — If a model (or the solution’s retrieval layer) can access poorly governed repositories—such as broadly shared folders, misconfigured SharePoint sites, or unsecured databases—then the system can surface sensitive information in responses even without malicious intent. This is why access control, data classification, and permission hygiene are critical prerequisites for deploying AI assistants grounded in organizational content.

No — Protecting only user prompts is insufficient. Data exposure can occur through multiple paths: retrieved documents, generated outputs, logs/telemetry, training/fine-tuning data, and connector/index configuration. Preventing exposure requires layered controls: data governance (labels, DLP, least privilege), secure connectors, output filtering, auditing, and user training—not prompt policy alone.

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.