AB-730 Sample Questions Answers

In Microsoft 365 Copilot, notebooks are designed to organize related work into a single, reusable workspace. A notebook can group multiple Copilot conversations and associate them with shared reference materials (for example, the same set of files, links, or notes). This directly addresses both requirements in the question: (1) making conversations easier to find by collecting them in one place, and (2) enabling those conversations to use the same reference sources for grounding and continuity.

An agent is best when you want a specialized Copilot experience with predefined instructions, capabilities, and (optionally) a configured knowledge source. However, an agent does not primarily function as a “container” to gather and organize multiple existing conversations.

A page is used to capture and edit output (such as a generated report) for collaboration, not to organize multiple conversations with shared references. An app is a broader product surface and does not solve the conversation organization requirement.

Therefore, the best solution is to use a notebook .

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 .

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 integrates with Microsoft Search to help users discover relevant content across their organization’s Microsoft 365 data estate, including SharePoint, OneDrive, Teams, and Exchange. When the objective is to determine whether similar training plans already exist, the appropriate action is to perform a search across organizational content.

Using Search allows Copilot to query indexed enterprise documents and return files, plans, or related materials that the user has permission to access. This supports content reuse, avoids duplication of work, and aligns with Microsoft’s guidance on leveraging organizational knowledge efficiently.

Designer is focused on visual content creation, Apps provides access to Microsoft 365 applications, and Pages is used for creating and organizing content within Copilot. None of these options are intended for discovering existing documents across the tenant.

Therefore, to identify similar existing training plans within your organization, the correct tool to use in Copilot is Search.

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

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.

The correct answer is instructions because an agent’s persona—such as being warm, friendly, formal, or analytical—is defined through its behavioral and communication guidance. In Microsoft 365 Copilot, the Instructions field controls how the agent responds, including tone, style, personality, response structure, and interaction patterns.

The description typically explains what the agent does, not how it communicates. Capabilities define what tasks the agent can perform, such as summarizing documents or analyzing data. Suggested prompts provide example user queries but do not control the agent’s personality or communication style.

To establish a warm and friendly persona, the instructions should explicitly state guidance such as: “Respond in a supportive, conversational tone. Use clear and positive language. Be encouraging and approachable.” This ensures consistent tone across all interactions.

Defining persona through instructions reflects prompt engineering best practices in generative AI, enabling predictable behavior, improved user experience, and alignment with organizational communication standards within Microsoft 365 Copilot environments.

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.

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

suggested prompts

In Microsoft 365 Copilot, suggested prompts are designed to help users get started quickly and interact with an agent effectively. Microsoft guidance for Copilot agents emphasizes that many users struggle most at the beginning—knowing what to ask, how to phrase requests, and how to take advantage of an agent’s purpose. Suggested prompts address this by providing ready-to-use examples that demonstrate the best ways to engage the agent for its intended scenarios.

Suggested prompts also act as lightweight “guardrails” for good prompting. They show users the expected input patterns, the types of tasks the agent can perform, and the kinds of outputs they can request. This accelerates adoption and improves the quality of results by steering users toward well-structured requests and appropriate context.

By contrast, capabilities describe what an agent can do (tools/features), instructions define how the agent should behave, and agent settings control configuration. None of those are primarily meant to help users begin conversations through example starters.

Therefore, the correct completion is suggested prompts .

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

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.

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 .

Copilot in Outlook is designed to reduce time spent reading and writing email by using AI to summarize message threads and generate drafts grounded in the current email context. Microsoft guidance for Copilot in Outlook highlights core capabilities such as drafting replies that reflect the conversation tone and content, and summarizing email threads or inbox content so users can quickly understand what requires action.

Option B is correct because Copilot can generate a draft reply based on the context of the email conversation, helping you respond faster while keeping the response aligned to what was discussed. Option C is correct because Copilot can summarize emails—such as unread messages or a thread—by extracting key points, requests, decisions, and suggested next steps, which supports rapid triage.

Option A is not a Copilot task; inserting or customizing an HTML signature is a standard Outlook configuration feature. Option D is also a traditional Outlook management function and is not an AI drafting/summarization capability.

Therefore, the two tasks you can achieve with Copilot in Outlook are drafting responses and summarizing unread emails .

Microsoft 365 Copilot can be accessed via its dedicated web experience for enterprise users. The correct web entry point for Microsoft 365 Copilot is https://m365.cloud.microsoft , which provides authenticated access to Copilot features within the Microsoft 365 environment.

This URL routes users into the Microsoft 365 ecosystem where Copilot integrates with organizational data such as SharePoint, OneDrive, Teams, and Outlook. It ensures that users are authenticated through Microsoft Entra ID and that access controls are enforced according to tenant policies.

Option B refers to Copilot Studio, which is used to build and manage custom copilots and agents rather than access the Microsoft 365 Copilot chat experience. Option C (My Apps) is a general application launcher portal. Option D is an incorrect account management URL and does not provide Copilot access.

Therefore, to access Microsoft 365 Copilot from a web browser, the correct URL is https://m365.cloud.microsoft .

In Microsoft 365 Copilot, agents such as Researcher are accessed through the Agents experience within the Copilot app. If the user interface does not immediately display a specific agent, the correct action is to browse or search the available agents catalog. The exhibit shows the left navigation pane with an Explore agents option.

According to Microsoft AI Business Professional guidance, built-in and custom agents can be discovered and enabled through the Explore agents section. If the user already has the appropriate Copilot license and is signed in with their work account, there is no need to switch accounts or request another license.

Signing in through a browser does not change feature availability, and using a personal account would remove access to organizational features. Therefore, to access the Researcher agent, you should select Explore agents and search for Researcher.

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

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.

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

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 fully respects Microsoft Purview Information Protection, including sensitivity labels applied to documents. When content is used as a source to generate new content (for example, creating a PowerPoint presentation from a Word document), Copilot ensures that data protection policies are preserved and inherited.

If the source Word document is labeled Highly Confidential, the generated presentation will automatically inherit the same sensitivity label. This ensures that the classification, encryption, and access restrictions applied to the original content are consistently enforced in derived content. This behavior aligns with Microsoft’s compliance and data governance model, which prevents accidental data exposure when content is reused or transformed.

Option A is incorrect because Copilot does not require manual reclassification when a label is already present on the source. Option B is incorrect because labels are not dropped during content generation. Option D is incorrect because Copilot can still generate content from labeled documents, provided the user has access.

Therefore, the presentation will be generated with the Highly Confidential label applied.

The first statement is correct because Microsoft 365 provides transparency and user control through the My Account portal, where users can review their Copilot activity history. This aligns with Microsoft’s responsible AI and data governance principles, ensuring visibility into AI interactions.

The second statement is incorrect. Deleting Copilot activity history removes stored interaction records (such as prompts and responses), but it does not automatically delete associated notebooks, documents, or pages stored in services like OneDrive or SharePoint. Those files remain governed by standard Microsoft 365 retention and lifecycle policies.

The third statement is correct because users can delete their entire Copilot activity history, including both prompts and generated responses. This reinforces enterprise-grade privacy controls and regulatory compliance requirements.

These controls demonstrate core generative AI fundamentals: transparency, user data ownership, security boundaries, and responsible lifecycle management of AI-generated interactions within Microsoft 365 environments.

In Microsoft 365 Copilot, the Copilot Prompt Gallery is used to store and reuse prompts that have been created and tested. To save a prompt into the gallery, Copilot must first have the prompt as an executed interaction so it can be captured as a reusable prompt (often alongside the context and intended outcome). Microsoft guidance for prompt management emphasizes validating prompts by running them and reviewing the output, then saving the prompt for reuse once it produces the desired results.

Option D is therefore the correct first step: run the prompt . After execution, you can save it to the Prompt Gallery so it becomes easily discoverable and reusable for future project reports or for sharing within your organization (subject to policy).

Creating a notebook is useful for organizing reference materials across related conversations, but it is not required to publish a prompt to the gallery. Adding an agent is for creating specialized assistants with knowledge and capabilities, not for saving a single prompt. Creating a page is used to refine and collaborate on generated content, not to make a prompt available in the gallery.

Therefore, the first action is to run the prompt .