Microsoft AB-730 AI Business Professional Exam Practice Test

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.

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 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 building a custom agent in Microsoft 365 Copilot for marketing use cases, the required capabilities must align with the intended outputs. Marketing collateral includes written copy as well as visual assets such as logos and artwork. According to Microsoft AI Business Professional documentation, generative AI solutions that produce visual creative assets require integrated image generation capabilities powered by multimodal AI models.

Option C is correct because an image generator enables the agent to create visual marketing materials such as logos, artwork, and design elements. While templates and suggested prompts can improve usability and consistency, they do not provide the underlying capability to generate images. A code interpreter is designed for data analysis, calculations, or technical scripting tasks and is not relevant to creative marketing asset production.

Therefore, to fulfill the requirement of producing both textual and visual marketing collateral, the most essential addition to the custom agent is an image generator.

 You can continue the conversation in Copilot in Word.

Answer: Yes

 You can continue the conversation in Copilot for Teams.

Answer: Yes

 You can continue the conversation in Copilot in Outlook.

Answer: Yes

Microsoft 365 Copilot provides cross-application continuity across supported Microsoft 365 apps. When using the Researcher agent, users can continue or extend their work within applications such as Word, Teams, and Outlook.

In Word, users can incorporate research results directly into drafted documents, enabling seamless transition from research to content creation. In Teams, Copilot supports contextual collaboration by allowing insights from research to inform meetings or chats. In Outlook, findings can be referenced to compose informed and data-driven communications.

This interoperability is enabled by Microsoft Graph integration, which allows Copilot to securely access and contextualize enterprise data across applications while respecting organizational permissions.

These capabilities demonstrate effective management of prompts and conversations by maintaining workflow continuity, enhancing productivity, and supporting enterprise-grade collaboration powered by generative AI.

Microsoft 365 Copilot can use Microsoft Graph-grounded data (based on the user’s permissions) to help users work with Microsoft 365 content. This includes surfacing and summarizing information from Teams chats , so statement 1 is true. Copilot can also summarize and generate content related to Teams meetings (for example, meeting recap details, key discussion points, and follow-up actions when meeting artifacts such as transcript/notes are available), and it can answer questions and draft related content—so statement 3 is true.

Statement 2 is false because, while Copilot can draft emails and help prepare messages, it does not independently schedule and send emails automatically “based on conditions” as a native Copilot function. Conditional sending is typically handled through workflow automation tools (for example, Power Automate) and still requires appropriate configuration, permissions, and governance. In enterprise environments, this separation helps reduce risk by ensuring that automated outbound communication remains controlled, auditable, and compliant.

Comprehensive and Detailed 150 to 200 words of Explanation Microsoft AI Business professional documents:

Microsoft 365 Copilot conversation retention is governed by Microsoft Purview Data Lifecycle Management and an organization ' s retention policies. Under the default Microsoft 365 configuration , no automatic retention period is configured specifically for Copilot conversations. This means Copilot interactions remain subject to the organization ' s existing Microsoft 365 retention configuration and are retained indefinitely until a retention or deletion policy is applied or a user deletes the conversation (where permitted by organizational policy). Microsoft introduced dedicated retention policies for Copilot so administrators can configure periods such as 30 days or other business-specific durations, but these are administrator-configured policies , not default behavior.

Therefore, options A (30 days) and D (90 days) represent examples of configurable retention periods rather than the default. Option C (one year) is not the default Microsoft setting. With Microsoft 365 services using their default configuration and no explicit retention policy configured, Copilot conversations can be retained indefinitely , subject to organizational compliance requirements and any future administrator-defined retention policies.

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

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.

Therefore, the best choice to evaluate spending and performance trends and calculate ROI is the Analyst 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.

Microsoft 365 Copilot operates within two primary knowledge boundaries: its foundational large language model training data and the organizational data available within the Microsoft 365 tenant. However, Copilot strictly enforces Microsoft’s security and compliance model, meaning it only retrieves and uses data that the signed-in user is authorized to access.

When using the Work scope, Copilot combines the general knowledge it was trained on with organizational data such as documents, emails, chats, calendars, and files stored in Microsoft 365. Importantly, Copilot respects role-based access control and existing permissions. It does not surface information from content the user does not have access to.

Option A is incomplete because Work scope includes organizational data. Option B is incorrect because Copilot does not access all tenant data indiscriminately; it is permission-scoped. Option D is incomplete because Copilot also leverages its general training knowledge.

Therefore, the correct explanation is that Copilot provides responses based only on data the user can access, combined with its general training knowledge.

When you add a file to a Microsoft 365 Copilot notebook from a Microsoft SharePoint site , you are referencing a document that is stored and managed within Microsoft 365. SharePoint maintains a single authoritative file that can be updated over time (with version history behind the scenes). Copilot notebooks that reference SharePoint content are designed to stay grounded in the current version of that cloud-hosted document, subject to your permissions.

Because Process.docx is stored in SharePoint, the notebook reference points to the SharePoint document itself rather than a static local snapshot. When another user updates the document in SharePoint, the “latest” content becomes the current version available at that location. When you chat in the notebook, Copilot will use the file as it exists now in SharePoint, which means it will reference the most recent version.

Option A would be typical only if you attached a local file upload (a static copy) rather than a SharePoint-hosted file. Option C is incorrect because Copilot uses the current file at the referenced location, not multiple historical versions simultaneously.

Therefore, the chat will reference the most recent version of Process.docx .

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 .

Comprehensive and Detailed 150 to 200 words of Explanation Microsoft AI Business professional documents:

When you share a Microsoft 365 Copilot prompt that references files stored in OneDrive, the prompt sharing action does not automatically change file permissions. Copilot follows the Microsoft 365 permission model, meaning users can only access, summarize, analyze, or ground responses in files that they already have permission to open.

Option C is correct because the shared prompt can be used successfully with the referenced files only if the recipient already has access to those OneDrive files. Sharing the prompt shares the prompt structure and instructions, not the underlying file access rights. This prevents accidental exposure of private or confidential business documents.

Option B is incorrect because Copilot does not automatically grant access to files when a prompt is shared. Option A is too strong because the files are not necessarily removed from the prompt; they remain referenced but usable only if permissions allow. Option D may happen in some Microsoft 365 file-sharing contexts, but the best general rule is that access must already exist or be granted separately.

Therefore, the user can run the prompt successfully only if they have access to the referenced OneDrive files.

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.

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

a specific date range of activity

The Microsoft 365 My Account portal provides users with control over their Copilot activity history in alignment with enterprise privacy and compliance standards. When selecting Delete history , users can remove Copilot activity based on a defined time range rather than deleting only a single conversation or all activity universally.

This functionality reflects Microsoft’s commitment to transparency, user control, and responsible AI governance. Allowing deletion by date range enables organizations and individuals to manage data retention policies efficiently while maintaining compliance with regulatory frameworks such as GDPR and internal data governance policies.

The other options are incorrect because deleting a specific conversation or all conversations with a specific agent is not the primary method offered in the My Account activity deletion setting. Instead, deletion is structured around activity time periods.

This capability reinforces generative AI best practices: secure data management, lifecycle control of AI interactions, and user-directed privacy management within enterprise environments.

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.

Microsoft 365 Copilot agents operate within the security, compliance, and identity boundaries of a Microsoft 365 tenant. Custom agents created in the Microsoft 365 Copilot app are governed by organizational policies, role-based access control, and Microsoft Entra ID authentication.

According to Microsoft AI Business Professional guidance, Copilot agents are designed for enterprise use and are shared within the organization unless administrators configure broader sharing capabilities. External sharing with personal Microsoft accounts or arbitrary email addresses is not supported by default due to security, data protection, and compliance requirements.

Because the agent in this scenario interacts with organizational data such as client emails, project milestones, and internal reports, access must remain restricted to authenticated users within the same tenant. This ensures that sensitive business information remains protected and that data access respects existing permissions.

Therefore, the agent can be shared only with people in your organization, making option D the correct answer.

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

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 .

Microsoft 365 Copilot respects Microsoft 365 permissions (“permission trimming”). This means it can only access and summarize content you are authorized to view. Therefore, Copilot cannot answer questions about Teams meetings you are not invited to (and otherwise don’t have access to), making statement 1 No .

Copilot can summarize and answer questions about Teams artifacts you do have access to—such as chat messages, channel posts, and meeting content (for example, transcripts, notes, recordings, and meeting recap details when available). That makes statement 2 Yes .

Copilot can also help you prepare for your schedule by summarizing upcoming meetings you’re invited to , using calendar and meeting context (subject, time, participants, related emails/files, and available agenda/notes). This supports planning and prioritization for the week ahead, so statement 3 is Yes .