Microsoft AB-730 AI Business Professional Exam Practice Test

The Researcher agent in Microsoft 365 Copilot is designed to gather and synthesize information from web and organizational sources. To support transparency and trust, Copilot provides citations alongside generated content when external or referenced material is used.

Citations allow users to review the original sources that informed the generated report. This aligns with Microsoft’s Responsible AI commitment to transparency and verifiability. By selecting or reviewing citations, users can confirm that the information originates from credible and relevant references rather than unsupported model-generated text.

Instructions define how the agent behaves but do not validate source authenticity. Memory refers to conversational context retention and does not confirm source validity. Capabilities describe what the agent can do, not whether its output is grounded in legitimate sources.

Therefore, to verify that a report generated by the Researcher agent uses valid sources, you should review the citations.

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.

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.

Microsoft 365 Copilot is designed to be helpful by using work context —for example, the files you have access to, recent activity, meetings, emails, and SharePoint/OneDrive content—to suggest relevant prompts and help you start tasks faster. It also uses this context to augment your prompt before it is sent to the LLM. This is the grounding approach (often described as retrieval-augmented generation): Copilot retrieves relevant organizational content you’re permitted to access and adds it as supporting context so responses are accurate and business-relevant. However, Microsoft 365 Copilot does not use your organization’s contextual data to train the underlying foundation model . That separation is critical for enterprise privacy and compliance: your prompts, responses, and tenant data are used to generate the answer for your session and permissions, but are not used to improve or retrain the base LLM. This approach supports responsible AI, protects confidential business information, and ensures outputs respect access controls.

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.

Microsoft 365 Copilot follows Microsoft’s Responsible AI principles and enforces strict content safety policies. When a prompt violates safety guidelines—such as containing harmful, abusive, illegal, or restricted content—the system may refuse to generate a response. The refusal message shown is consistent with safety filtering behavior.

Generative AI systems include moderation layers that evaluate prompts before generating output. If the prompt is classified as unsafe or non-compliant with policy, Copilot blocks the request and encourages the user to try a different topic.

A vague prompt typically results in a generic or clarifying response rather than a refusal. There is no fixed limit of five requests per prompt. Exceeding the context window usually results in truncation or processing errors, not a safety-based refusal message.

Therefore, the most likely cause of the response is that the prompt contains language that violates safety guidelines.

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

When you use Microsoft 365 Copilot Chat without a Microsoft 365 Copilot license, Copilot Chat operates in a “general” mode rather than a Microsoft Graph-grounded work mode. In this configuration, Copilot does not have the entitlement to access and reason over your organization’s protected Microsoft 365 content (such as SharePoint sites, OneDrive files, Outlook mail, Teams messages, or other tenant resources). It also does not connect directly to your organization’s internal databases unless separate, explicitly configured integrations exist.

Instead, Copilot relies on three primary sources to generate a response: (1) the prompt context you provide in the current request (what you ask, plus any text you paste), (2) the conversation history within the current chat thread to maintain continuity, and (3) internet search data (when web grounding is available) to supplement general knowledge with up-to-date public information.

Therefore, the correct selections are C (prompt context), E (internet search data), and F (conversation history) , while organizational Microsoft 365 data and Teams chat data are not used without the Copilot license.

In the Microsoft 365 Copilot app, the Conversations list can display status indicators next to individual conversation titles. In the exhibit, the Standings conversation has a distinct indicator (a green badge) shown to the right of the conversation name. This badge is used to signal that the conversation includes a verified response.

A verified response indicator is intended to help users quickly recognize outputs that were produced with stronger grounding and traceability—for example, responses that include supporting citations or references that can be reviewed for accuracy. This aligns with Microsoft’s guidance on improving trust in AI output by making source-backed or verification-supported responses easier to identify and validate.

The other options do not match the indicator shown. Conversations that are shared or added to notebooks typically use different share/notebook iconography, and scheduled prompts are represented with scheduling-related indicators rather than a verification badge. “Anonymous data” is not something Copilot marks at the conversation level in this manner.

Therefore, the best inference is that the Standings conversation contains a verified response.

Microsoft 365 Copilot Pages supports collaboration similarly to other Microsoft 365 documents. Collaboration requires notifying or granting access to colleagues.

Using @mentions within the page (Option A) directly notifies the colleague and facilitates collaborative engagement. Sharing the page link (Option D) allows others to access and edit the content according to permissions. These two methods provide complete collaboration workflows.

Adding the page to a notebook does not grant collaborative access. Opening the page in Word changes the editing surface but does not inherently enable collaboration unless shared.

Therefore, the correct answers are A and D.

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

The instructions will apply to new chat conversations.

Answer: Yes

The instructions will apply to new conversations with the Researcher agent and the Analyst agent.

Answer: Yes

The instructions will apply to previous responses in existing conversation.

Answer: No

Custom instructions in Microsoft 365 Copilot are a persistent preference mechanism that influences how Copilot responds going forward. Once configured, they are applied when you start new interactions, helping Copilot maintain consistent tone, formatting, and behavioral preferences across future chats. Therefore, they apply to new chat conversations (Statement 1 = Yes).

Custom instructions also carry into new conversations you initiate with Copilot experiences and agents (such as Researcher and Analyst), because the instructions act as a user-level guidance layer that shapes responses regardless of which Copilot “mode” you start—provided those agents are being used in the same Copilot environment and are subject to your settings (Statement 2 = Yes).

However, custom instructions do not retroactively change content that was already generated. Existing conversation history and any prior responses remain unchanged; the instructions affect subsequent turns or new threads, not previously produced outputs (Statement 3 = No).

Microsoft 365 Copilot includes a memory capability that allows it to retain user-provided preferences or details across interactions when explicitly instructed to remember them. These stored details are referred to as memories and are separate from standard conversation history.

If you previously asked Copilot to remember specific trip-related details, those details are stored as structured memory items. Simply deleting the conversation does not necessarily remove stored memory entries. Likewise, deleting activity history through the My Account portal removes conversation records but does not directly manage structured Copilot memories. Custom instructions define persistent behavioral preferences and are unrelated to trip-specific stored data.

To ensure Copilot no longer retains those trip details, you must delete the stored memories directly within Copilot. Microsoft documentation explains that users can view and manage saved memories and remove them individually to control what Copilot retains.

Therefore, the correct action to ensure Copilot forgets the trip details is to delete the memories.

Microsoft 365 Copilot notebooks use the version of a file that was uploaded or attached at the time it was added to the notebook. When a document such as Process.docx is added from a local folder, Copilot references that uploaded snapshot of the file. If the file is later modified locally, the notebook does not automatically sync or refresh with the updated local version unless the updated file is re-uploaded.

Microsoft guidance on grounding and file references explains that Copilot works with the specific content stored in Microsoft 365 or the attached artifact within the notebook session. Since the updated version remains in the local folder and was not reattached, Copilot continues to use the originally added version.

Therefore, during subsequent chats in the notebook, Copilot references only the original uploaded version of Process.docx.

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

Effective prompting in Microsoft 365 Copilot requires two critical components: clear instructions and grounding in authoritative content. Microsoft guidance emphasizes that prompts should explicitly state the desired output format, tone, length, and purpose. In this case, specifying “a bulleted list of three to five concise, simply worded key points” represents concise instructions, making option B essential.

Additionally, grounding the response in a specific knowledge source—such as attaching or referencing the proposal document—ensures factual accuracy and reduces hallucination. Option D ensures Copilot uses the actual proposal content rather than relying on generalized model knowledge.

Profiles and stakeholder contact details are unrelated to summarization requirements. Therefore, the correct selections are B and D.

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

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.

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 Chat is included at no additional cost for users with qualifying Microsoft 365 subscriptions such as Business Basic, Business Standard, Business Premium, E3, and E5. Therefore, users without a Microsoft 365 Copilot add-on license can still access Copilot Chat.

Copilot Chat allows users to upload documents from their local device within a session for summarization, analysis, and drafting assistance. However, advanced enterprise-integrated features—such as creating agents that access organizational SharePoint folders—require a Microsoft 365 Copilot license.

Agent creation and enterprise data grounding leverage Microsoft Graph integration and are considered premium Copilot capabilities tied to licensed Copilot services.

This distinction reflects Microsoft’s licensing model: baseline AI chat access is included with qualifying subscriptions, while deep Microsoft 365 app integration and enterprise data agents require the additional Copilot license.

Microsoft distinguishes Microsoft 365 Copilot (the full, licensed experience integrated across Microsoft 365 apps and Microsoft Graph) from Microsoft 365 Copilot Chat (the chat-first experience available more broadly). Some advanced capabilities—especially those tied to specialized agents and persistent work organization—are typically associated with the full Copilot license.

The Researcher agent is an advanced capability and is not consistently available in Copilot Chat across tenants because it is treated as a premium agent experience. Copilot Notebooks are also a structured organization feature used to group conversations and share reference materials; this is typically positioned as part of the full Microsoft 365 Copilot experience.

Copilot Pages , however, is the collaborative, editable canvas used to refine, organize, and share Copilot-generated content. Pages is designed to work alongside Copilot Chat so users can move from a chat response into an editable artifact for collaboration and reuse. This makes Pages the feature most commonly available in both the full Microsoft 365 Copilot and Microsoft 365 Copilot Chat experiences.

Therefore, the best answer is Copilot Pages .

Copilot in Microsoft Teams is designed to help users work faster by summarizing meeting content and assisting with message composition in chats and channels. Microsoft guidance highlights that Copilot can synthesize what was discussed in a meeting by generating a structured recap that includes key points, decisions, and action items. This directly matches option C . Copilot can also help you respond more quickly in Teams conversations by drafting replies grounded in the context of the existing chat or channel thread, which matches option D .

Options A and B are not Copilot capabilities. Muting and unmuting participants is a meeting control function handled by Teams meeting roles and settings, and it is not automatically driven by Copilot based on participant location. Creating custom backgrounds is a Teams visual feature (and can involve Designer or image tools), but it is not a Copilot-in-Teams productivity function for summarization or drafting based on conversation context.

Therefore, the two tasks you can achieve using Copilot in Teams are generating meeting summaries with decisions and action items, and drafting responses to channel messages based on conversation context.

This scenario is an example of overreliance . Microsoft’s AI guidance highlights that Copilot is an assistive tool that can accelerate analysis and drafting, but users remain responsible for validating outputs—especially for high-impact business decisions. Overreliance occurs when someone treats AI output as authoritative and acts on it without applying judgment, cross-checking sources, or validating against current conditions.

Here, the merchandiser uses Copilot to generate stocking recommendations from historical sales data, then places a large order without reviewing the suggestions or incorporating current market trends. Even if the historical data is accurate, demand can shift due to seasonality changes, competitor actions, pricing, supply constraints, macroeconomic factors, or new product launches. Copilot’s recommendations should be treated as a starting point for decision-making, not the final decision.

Option A (verification) is the opposite behavior—checking accuracy before acting. Option C (fabrication) would involve Copilot inventing facts; the prompt doesn’t indicate fictional data, only unvalidated reliance. Option D (prompt injection) involves malicious instructions embedded in content to manipulate the model, which is not described here.

Therefore, the best answer is overreliance .

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 .

All three statements are false because generative AI responses are not guaranteed to be identical even when the prompt is the same. First, when grounded in the web , results can vary due to changing web content, different retrieved sources, or differences in how information is summarized at run time. Second, when grounded in your organization’s data , responses can change based on updates to files, emails, meetings, permissions, or which specific items Copilot retrieves as the most relevant context at that moment. Third, even when relying only on the model’s general knowledge, large language models are probabilistic: they may choose different wording, structure, examples, or emphasis across runs, especially when temperature/decoding settings and internal routing differ. In business scenarios, this means Copilot outputs should be treated as drafts that may require validation, and repeatability should be improved by adding precise constraints (cite specific sources, use fixed formats, specify exact sections, and request verbatim quotes where appropriate).

Prompt-grounding means ensuring Copilot’s response is based on authoritative, relevant source material rather than inferred or generalized information. Microsoft guidance for Copilot emphasizes that the most effective way to ground responses is to explicitly point Copilot to the content you want it to use—such as specific SharePoint documents, OneDrive files, emails, meeting notes, or other Microsoft 365 resources the user has permission to access.

Option D is therefore the best answer because referencing specific files anchors Copilot’s reasoning to the exact material that should be used for facts, terminology, and details. This reduces hallucinations (fabrication) and improves accuracy and traceability, especially when Copilot can provide citations back to the referenced sources.

Option B (desired output format) improves structure and readability but does not, by itself, ground content. Option A can sometimes improve clarity, but shorter prompts do not guarantee grounding. Option C may help comprehension in some cases, but it is not a grounding strategy and can be counterproductive if the source material is technical.

Therefore, the best approach to improve prompt-grounding is to reference specific files .