AB-730 AI Business Professional Question and Answers

Microsoft’s approach to transparency for AI-generated media relies on provenance signals rather than cosmetic indicators. File names and descriptions can be edited easily and are not reliable evidence of how an image was created. Watermarks may appear in some contexts, but they are not consistently applied across all AI image-generation workflows and can sometimes be removed or lost through copying, screenshotting, or file conversion.

Microsoft supports the use of content credentials to help users verify whether digital content was created or modified with AI. Content credentials are part of a provenance standard (often associated with C2PA) that can embed tamper-evident metadata into media files. When present, these credentials can show information about the tool or process used to generate or edit the image, providing a verifiable chain of origin.

Therefore, the most dependable way to verify whether the images were AI-generated is to check for content credentials (option C), since they are designed specifically to provide authenticity and provenance information for AI-created or AI-edited content.

This scenario is an example of fabrication, which is commonly referred to in generative AI contexts as a hallucination. Fabrication occurs when an AI system generates information that appears credible but is factually incorrect, invented, or unsupported by verifiable sources.

According to Microsoft AI Business Professional guidance, large language models predict text based on patterns learned during training. They do not “know” facts in the human sense. As a result, when asked to generate reports using web-based information, the model may produce plausible-sounding but fictional details if sufficient grounding or reliable sources are not provided.

Deepfake refers specifically to synthetic media such as manipulated images, audio, or video. Overreliance describes a human behavior risk where users trust AI outputs without verification. Prompt injection is a malicious technique designed to manipulate model behavior. Bias refers to systematic unfairness in outputs.

In this case, the presence of fictional information in the generated report directly aligns with fabrication, making option B the correct answer.

When creating an agent in the Microsoft 365 Copilot app using a template, administrators or authorized users can configure specific behaviors and knowledge sources for the agent. Therefore, it is correct that you can choose which knowledge sources the agent can use. This ensures proper grounding in approved Microsoft 365 data such as SharePoint sites, OneDrive folders, or other organizational repositories. Controlling knowledge sources supports responsible AI principles, including data security, relevance, and compliance.

Agents created within Microsoft 365 are designed primarily for internal organizational use. As a result, sharing the agent with users inside the organization is supported, enabling collaboration and productivity improvements across teams.

However, sharing the agent with external users is not supported by default. External sharing would introduce security and compliance risks, so Microsoft enforces tenant-level boundaries to protect enterprise data.

These capabilities reflect best practices in managing AI prompts and agents securely within enterprise environments.

To generate an effective monthly summary with Copilot in Excel, Microsoft prompting guidance emphasizes two core elements: clear intent and expected output structure . First, you should state the goal explicitly—such as “summarize total sales by month based on OrderDate and Amount, and highlight month-over-month changes.” This directs Copilot to the correct aggregation and analysis behavior (Option D).

Second, specifying the desired format improves usability and reduces ambiguity. For example, requesting “a table with Month, Total Sales, Number of Orders, and Average Order Value” or “a bulleted executive summary plus a small summary table” ensures Copilot returns results in a format you can immediately use (Option A).

A specific cell range (Option B) is usually unnecessary when the data is already in a recognized Excel table, because Copilot can work from the table context. The workbook file name (Option C) does not help analysis. Providing a formula (Option E) is not required because Copilot can compute monthly totals; formulas are optional if you want a specific calculation method, but they are not the best prompt ingredients for an effective summary.

Therefore, the best answers are A and D .

Microsoft provides centralized activity management controls through the My Account portal, which allows users to manage privacy settings, activity history, and data associated with Microsoft 365 services, including Copilot. When the requirement is to delete all conversations with minimal effort, the most efficient method is to use the account-level activity management tools rather than deleting conversations individually.

The My Account portal enables bulk management of Copilot activity data, allowing users to clear conversation history in a consolidated manner. This approach aligns with Microsoft’s privacy-by-design framework, giving users control over their AI-generated interaction history without requiring administrative intervention.

Using the Copilot web or desktop app would typically require manually deleting conversations one at a time, increasing effort. The Windows 11 Settings app is unrelated to Microsoft 365 Copilot data management.

Therefore, to delete all Copilot conversations efficiently and with the least amount of effort, the correct approach is to use the My Account portal in Microsoft 365.

Microsoft Purview is the correct choice because it is Microsoft’s unified compliance and data governance solution that helps organizations apply and enforce policies across Microsoft 365 content— including Copilot-related interactions where those interactions are captured in services such as Microsoft 365 audit, eDiscovery, and Purview compliance experiences. Purview supports capabilities such as data loss prevention (DLP) , retention , eDiscovery , audit , and sensitivity labeling so organizations can manage and govern data and AI-assisted content in line with regulatory and internal requirements. In contrast, Microsoft Entra ID focuses on identity and access management, Intune focuses on device and application management, and Defender for Cloud focuses on cloud security posture management. Governance policies for Copilot-generated conversations and associated compliance controls align most directly with Purview , which is designed to manage information protection and compliance across the Microsoft 365 environment.

When building a custom analytics agent in Microsoft 365 Copilot that must process structured data from Excel files, advanced analytical capabilities are required. According to Microsoft AI Business Professional guidance, tasks such as performing mathematical calculations, generating aggregations, creating charts, and conducting structured data analysis require programmatic execution capabilities rather than simple text generation.

A code interpreter enables the agent to run Python-based analytical operations in a secure execution environment. This allows the agent to manipulate datasets, compute totals and averages, perform grouping and filtering, and generate visualizations such as bar charts or line graphs based on the Excel data. The interpreter bridges the gap between natural language instructions and executable analytical logic.

An image generator is designed for creative visual content and is unrelated to structured data analytics. Suggested prompts and templates improve usability and consistency but do not provide computational or visualization capabilities.

Therefore, to enable mathematical operations, aggregation, data analysis, and visualization of Excel sales data, the correct component to add to the agent is a code interpreter.

Microsoft guidance for effective prompting emphasizes clarity and context as the two most important factors. Providing context (Option A) ensures that Copilot understands the background, data sources, and constraints relevant to the task. This improves grounding and reduces ambiguity, leading to more accurate and useful responses.

Providing a clear goal (Option D) is equally critical. A well-defined objective—such as summarizing, analyzing, or drafting—helps Copilot determine the correct approach, structure, and level of detail for the response. Without a clear goal, outputs may be generic or misaligned with user expectations.

Using a broad range of instructions can introduce confusion rather than clarity. Acronyms may reduce clarity unless explicitly defined. Keeping prompts generic is discouraged because specificity improves quality and relevance of responses.

Therefore, the correct answers are A (adding context) and D (providing a clear goal) .

Microsoft 365 Copilot agents are designed to integrate with Microsoft 365 data sources and provide flexible, natural-language-driven configuration. Agents can be connected to organizational data such as SharePoint, OneDrive, and Exchange. Since shared mailboxes are part of Exchange Online and accessible through Microsoft Graph (subject to permissions), agents can be configured to search shared mailboxes, making Statement 1 correct.

Microsoft also enables natural language creation of agents , allowing users to describe what the agent should do, its purpose, and behavior using conversational instructions rather than requiring code. This simplifies agent creation and aligns with Copilot’s low-code/no-code approach, so Statement 2 is correct.

However, agents cannot use other agents as knowledge sources. Knowledge sources are limited to structured content such as files, sites, and data repositories. Agents operate independently rather than being nested or chained as data sources, making Statement 3 incorrect.

Thus, the correct answers are Yes, Yes, No .

Custom instructions allow users to define persistent preferences for tone, style, and response behavior across conversations. Microsoft documentation explains that Custom instructions help tailor Copilot responses to professional roles, communication styles, and domain expectations.

For a medical researcher requiring consistently professional, field-appropriate responses, configuring Custom instructions in Settings ensures that Copilot maintains the desired tone and terminology in future interactions.

Attaching examples influences only a single conversation. Saving prompts to the Prompt Gallery aids reuse but does not enforce tone globally. Copilot Memory stores factual preferences but is not intended for style configuration.

Therefore, the best and most comprehensive approach is to configure Custom instructions in Settings.

Agents created in the Microsoft 365 Copilot app are primarily designed for use within the Copilot Chat experience and related Copilot surfaces, not directly embedded inside individual applications like Word. Therefore, such agents are not automatically available in Microsoft Word, making Statement 1 incorrect.

However, these agents are designed for collaboration and reuse within an organization. Microsoft guidance confirms that agents can be shared with other users in the same tenant , allowing teams to leverage common tools, prompts, and knowledge sources. Hence, Statement 2 is correct.

For advanced automation scenarios involving complex workflows and third-party connectors, Microsoft provides Copilot Studio rather than the standard Copilot app. The Copilot app focuses on lightweight agent creation using natural language, files, and simple configurations. It does not support complex orchestration with external connectors. Therefore, Statement 3 is incorrect.

Thus, the correct answers are No, Yes, No .

The Describe tab is where you leverage generative AI to help build an agent by describing what you want the agent to do in natural language. Instead of manually configuring everything first, you provide the agent’s purpose, target users, tone, and the tasks it should perform (for example: “Create an onboarding agent that answers HR policy questions in a friendly tone and references SharePoint policies”). Copilot then uses that description to propose an initial agent setup—such as suggested behaviors, starter prompts, and structure—accelerating agent creation and improving consistency. By contrast, the Configure tab is typically used to fine-tune and finalize settings (such as knowledge sources, actions, and other parameters) after the agent concept is established. A Copilot notebook or Copilot page can help organize content and outputs, but they are not the primary place where generative AI “builds” the agent definition. Using the Describe tab reflects best practice: start with clear intent and constraints, then refine configuration for governance, accuracy, and usability.

In Microsoft 365 experiences, the standard way to invoke or reference people and specific resources in-context is by using the @mention pattern. Microsoft 365 Copilot extends this familiar interaction model to agents: when you want to switch to, invoke, or direct a question to a specific agent from within an existing Copilot conversation, you use @ followed by the agent’s name. This makes the agent selection explicit and reduces ambiguity about which assistant or capability you want to use for the next turn.

The other syntaxes listed are commonly associated with different systems: square brackets are not used for agent invocation, hashtags are typically used for topics/tags, and slash commands are used in some chat applications for command execution—but they are not the standard method for calling a Copilot agent in Microsoft 365 Copilot Chat.

Therefore, to chat with an agent named Agent1 during an open Copilot conversation, you should enter @Agent1 .

Microsoft 365 Copilot operates within the security, compliance, and identity boundaries of a Microsoft 365 tenant. Shared prompts, prompt links, and Copilot artifacts are governed by organizational access controls and tenant isolation. If a prompt is created and shared from outside your organization, cross-tenant access may not be supported depending on the sharing configuration and administrative policies.

When a user attempts to open a prompt that resides in another organization’s tenant without proper cross-tenant sharing permissions, Copilot cannot locate or validate the resource within the user’s own environment. As a result, the system displays a “Prompt not found” message.

Option B would typically result in an access or permissions error rather than the prompt being unavailable entirely. Sensitivity labels and scheduled prompts do not inherently cause a “not found” error. Therefore, the most likely cause is that the prompt exists outside your organization’s tenant boundary and is not accessible to you.

==================================================

Microsoft 365 Copilot does not train the underlying large language model on your organization’s tenant data. Instead, it uses your organization’s data at run time to ground responses (for example, by retrieving relevant emails or documents you have permission to access). This separation protects confidentiality and supports enterprise compliance.

If a mailbox (or specific folders) is shared with you and your account has the required permissions, Copilot can summarize emails from that shared content because Copilot respects Microsoft 365 access controls (“permission trimming”).

Copilot also relies on Microsoft 365’s established security and compliance framework—identity, permissions, and policy enforcement—so it only surfaces content you’re authorized to see. This ensures Copilot’s outputs remain aligned with organizational governance, information protection, and least-privilege access principles.

When Microsoft 365 Copilot cannot access a referenced file, it may return a message indicating that the file is empty, corrupted, or cannot be processed. In many cases, this message appears when the user does not have sufficient permissions to open the file in SharePoint, OneDrive, or another Microsoft 365 location.

Copilot operates within the Microsoft Graph security boundary and strictly respects user permissions. If a saved prompt references File.docx but the user no longer has access to it—due to permission changes, file relocation, or removal—Copilot cannot retrieve the content for grounding. As a result, it cannot analyze or summarize the file and returns a processing-related error.

Not scheduling the prompt is unrelated to file processing. Running from a web or desktop app does not affect file readability. Using a different agent does not typically cause a file-format processing error.

Therefore, the most likely cause is that you do not have access to the file.

Prompt injection is a generative AI security risk where an attacker inserts instructions (often hidden in text, documents, webpages, or user inputs) to override or manipulate the assistant’s intended behavior. This can lead to unintended actions such as ignoring policy controls, producing unsafe outputs, or attempting to reveal sensitive information. Because generative AI systems follow natural-language instructions, they can be socially engineered to prioritize malicious content unless safeguards are in place. This is why prompt injection can cause data exposure (for example, attempting to extract confidential content from grounded sources) and can also embed harmful instructions that redirect the model’s behavior. In enterprise settings like Microsoft 365 Copilot, mitigations include grounding boundaries, permission trimming, content filtering, and instruction hierarchy (system policies over user instructions). From a business governance perspective, users should treat untrusted inputs (emails, documents, web text) as potentially hostile and apply least-privilege access and validation when using AI outputs in decision-making.

To ensure cited information is accurate, Microsoft’s AI guidance emphasizes human verification of AI-generated outputs, especially when the content will be used in formal business documents. Even when Copilot grounds responses in SharePoint files, it can still misinterpret text, summarize imprecisely, or attribute a statement to the wrong section of a source. The most reliable way to confirm accuracy is to check each citation against the original SharePoint document and validate that the claim is supported exactly as written.

Option A is the best answer because manual verification is the definitive control for accuracy and accountability. Option B may help by asking Copilot to re-check or restate where information came from, but it is still an AI-generated confirmation and does not replace direct source validation. Options C and D can improve consistency and reuse of standards or references, but they do not guarantee citation correctness; they still depend on model interpretation.

Therefore, the best approach is to manually verify the citations in the generated proposal content.

The correct completion is “cannot modify the settings of” because built-in agents such as the Researcher agent in Microsoft 365 Copilot are system-defined experiences. These agents are designed and managed by Microsoft to ensure consistent functionality, security, compliance, and alignment with responsible AI standards.

While users can interact with Researcher, provide prompts, and refine outputs during conversations, they cannot directly modify the core system settings or configuration of the built-in agent from Microsoft 365. Administrative configuration and deeper customization are available when creating custom Copilot agents through approved development tools, but default Microsoft-provided agents have controlled configurations.

Options such as modifying agent instructions, adding prompts, or deleting suggested prompts imply direct structural customization of the built-in agent interface, which is not supported in the standard Microsoft 365 Copilot experience.

This reflects a key generative AI governance principle in enterprise environments: system-level controls remain centrally managed to maintain data protection, compliance, and responsible AI implementation across the organization.