AB-730 Exam Questions & Answers

Evaluating spend and performance trends and determining ROI is a structured analytics task. In Microsoft 365 Copilot, the Analyst agent is designed for quantitative analysis workflows: it can interpret tables, analyze datasets, identify trends over time, calculate metrics (such as ROI), and present results clearly (often including charts or summarized insights). This makes it the best fit when your goal is to compare marketing channels and understand which ones are delivering the strongest return based on last year's data.

Chat (Option B) can help you brainstorm questions or explain results, but it is not purpose-built for deep numeric analysis. The Researcher agent (Option C) is optimized for gathering and synthesizing information from sources and producing research-style outputs, not performing ROI calculations on internal performance data. A notebook (Option D) is useful for organizing files and keeping shared reference material across related conversations, but it does not itself perform the analysis---you would still need an analysis-capable agent.

Microsoft 365 Copilot provides structured ways to persist and reuse knowledge sources to avoid repeatedly uploading the same files.

Creating a notebook that references the five files (Option B) allows those documents to remain attached within a persistent workspace. Copilot can then consistently ground responses in those files without re-uploading them for every conversation.

Creating an agent with a defined knowledge source (Option D) also provides a reusable solution. By configuring the five files as part of the agent's knowledge base, the agent can automatically reference them in future interactions.

Saving a prompt does not persist file attachments. Fine-tuning models is not part of standard Microsoft 365 Copilot user workflows. Uploading a ZIP file does not improve reference management and may reduce accessibility of individual documents.

Therefore, the correct solutions are to create a notebook that references the files and to create an agent with a knowledge source.

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.

After a Microsoft Teams meeting ends, the Microsoft 365 Copilot feature designed specifically to help you catch up on what happened---including key discussion points, decisions, and next steps---is Recap (often referred to as intelligent recap). Recap aggregates post-meeting artifacts such as the recording, transcript, and AI-generated insights, and surfaces actionable items so attendees can quickly understand outcomes without rewatching the full meeting. This aligns directly with the requirement to review ''key points and next steps'' after each meeting.

Meeting Whiteboard is a collaborative canvas used during meetings for brainstorming and sketches; it does not automatically produce a structured summary of decisions and actions. Meeting info provides logistical details (participants, agenda, attachments) rather than a synthesized outcomes summary. Thread summaries focus on chat or channel message threads, not the meeting's recorded and transcribed content.

Microsoft 365 Copilot agents dynamically reflect updates such as new suggested prompts. When an agent is updated, users who already have the agent installed do not need to reinstall or have the agent reshared. Instead, the updated configuration becomes available when the agent is used again.

Suggested prompts are surfaced when a user interacts with the agent. Therefore, once Ben Smith issues any prompt to Agent1, the agent session refreshes and displays the latest suggested prompts, including the newly added one.

Stopping and resharing the agent (Option A) or reinstalling it (Option B) is unnecessary overhead. Option D refers to a non-standard command and is not part of Microsoft Copilot functionality.