Microsoft AB-730 AI Business Professional Exam Practice Test

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

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.

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

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 .

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.

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 .

Microsoft 365 Copilot in Teams relies heavily on meeting transcripts to provide post-meeting intelligence such as summaries, key points, decisions, and action items. The transcript serves as the structured textual data that Copilot analyzes to understand what was discussed during the meeting.

The feature commonly referred to as recap or intelligent recap is generated based on this transcript. Without transcription enabled, Copilot lacks the necessary detailed conversation data to accurately reconstruct the meeting content. As a result, generating a recap of what was discussed is only possible when a transcript is available.

Other options such as scheduling a follow-up meeting or identifying attached content do not depend on transcription, as they rely on calendar data or meeting metadata rather than conversational analysis. However, summarization and recap capabilities are directly tied to the transcript.

Therefore, the correct completion is generate a recap of what was discussed during the meeting , as this action specifically requires the meeting to be transcribed.

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 .

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.

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 .

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.

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 .

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.

Prompt scheduling in Microsoft 365 Copilot enables users to automate recurring AI-driven tasks such as generating reports, summaries, or updates. However, there are defined operational limits to ensure system performance, responsible AI usage, and governance compliance.

First, the most frequent interval at which a prompt can be scheduled is once per day . Scheduling more frequently, such as hourly, is not supported. This limitation prevents excessive automated execution that could strain system resources or generate unnecessary redundant outputs.

Second, a scheduled prompt has a maximum execution limit of 15 times . After reaching this threshold, the schedule must be recreated if further automation is required. This control ensures users periodically review and validate automated prompts for relevance, accuracy, and business alignment.

These constraints reflect Microsoft’s enterprise AI governance strategy: balancing productivity automation with performance optimization, cost control, compliance oversight, and responsible AI lifecycle management within Microsoft 365 Copilot environments.

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

Custom instructions in Microsoft 365 Copilot allow users to define persistent preferences that shape how Copilot responds across future interactions. According to Microsoft AI Business Professional guidance, these instructions are intended to personalize the Copilot experience by specifying communication preferences such as writing style, tone, level of detail, formatting, and other response characteristics. Once configured, these preferences are automatically applied to new Copilot conversations, providing a more consistent experience without requiring users to repeat the same instructions in every prompt.

Option B is correct because it accurately describes the primary purpose of custom instructions. Examples include asking Copilot to respond in a professional tone, use concise language, produce executive summaries, or format responses as bullet points.

Option A is partially related because users may include personal information within custom instructions, but the primary purpose is not to provide profile information—it is to establish response preferences. Option C is incorrect because security and data-sharing policies are enforced through Microsoft 365 administration and Microsoft Purview, not through custom instructions. Option D is incorrect because custom instructions do not grant Copilot additional permissions or autonomous action capabilities.

Therefore, the correct answer is B .

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.

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.

According to Microsoft AI Business Professional guidance for Microsoft 365 Copilot, grounding a response means ensuring the AI generates output based on specific, authoritative content rather than relying on generalized training data. When working with enterprise documents such as proposals, grounding is achieved by explicitly referencing the source material within the prompt.

Option C is correct because referencing the proposal content directs Copilot to use that specific document as the primary context for generating the response. Microsoft documentation emphasizes that effective prompts should include clear context and explicit references to relevant files, meetings, emails, or documents stored in Microsoft 365. This reduces hallucinations and ensures factual alignment with organizational data.

Option A is incorrect because relying on training data increases the risk of inaccurate or fabricated information. Options B and D improve prompt clarity but do not guarantee grounding in the proposal itself.

Therefore, explicitly referencing the proposal content is the most reliable and best practice method for ensuring grounded, accurate responses in Microsoft 365 Copilot.

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.

Temporary chat in Microsoft 365 Copilot is designed for privacy-focused, non-persistent interactions. When a user initiates a temporary chat session, the conversation is not saved to Copilot chat history and is not retained for future reference within the standard conversation history interface.

Once the session ends or a new chat begins, the prompts and responses from that temporary session are deleted immediately. They are not moved to OneDrive, stored in a notebook, or retained for a delayed deletion period.

This feature supports secure and confidential usage scenarios where users may want to explore ideas, draft sensitive content, or test prompts without creating a stored record in their activity history.

From a generative AI governance perspective, this reflects Microsoft’s design principle of providing configurable persistence levels, balancing productivity with enterprise security, compliance, and user privacy controls.

Microsoft 365 Copilot in Teams is designed to provide real-time meeting assistance, including summarizing discussions, identifying key decisions, and highlighting action items. When joining a meeting late, the most efficient and immediate method to catch up is to directly prompt Copilot within the Teams meeting experience.

Option A is the best answer because Copilot in Teams can summarize what has occurred so far during the live meeting. It leverages the meeting transcript, speaker attribution, and contextual signals to generate a concise, structured summary in real time. This minimizes delay and provides actionable insights instantly.

Reading the transcript (Option B) would require manual review and is not the fastest method. Intelligent recap (Option D) is typically available after the meeting concludes and processes recording data. Asking Copilot from the separate Microsoft 365 Copilot app (Option C) may not provide immediate, in-meeting contextual awareness.

Therefore, the fastest and most effective approach is to ask Copilot in Teams to summarize what you missed.

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.

Enterprise data protection (EDP) (often referred to as commercial data protection) is the capability that ensures Microsoft 365 Copilot handles organizational data under enterprise security and privacy guarantees. With EDP, Copilot processes prompts and responses within the customer’s Microsoft 365 boundary, respecting tenant isolation and identity-based access controls. This means Copilot only retrieves and uses data that the signed-in user is permitted to access, and the data remains governed by Microsoft 365 compliance features (such as retention, eDiscovery, audit, and Purview controls). Critically, EDP ensures that your organization’s prompts and the retrieved business content are not used to train the underlying AI foundation models. This is essential for protecting confidential business information and meeting regulatory and contractual requirements. The other options (Common Data Model, sensitivity labels, and Zero Trust) support data structure, classification, and security posture, but they do not specifically represent the Copilot guarantee that tenant data stays protected and is not used for model training.

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.

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