Pass the Microsoft Microsoft Certified: AI Business Professional AB-730 Questions and answers with CertsForce

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

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.

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.

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 .

Microsoft 365 Copilot operates within enterprise governance and compliance controls. For conversation history, tenant administrators can configure retention and deletion policies. Therefore, users can delete conversation history only if allowed by administrative policy, making Statement 1 correct.

Deleting a Copilot conversation removes the chat interaction but does not delete underlying source files such as documents stored in SharePoint or OneDrive. These files are governed independently by Microsoft 365 storage and retention policies. Hence, Statement 2 is incorrect.

When a Copilot agent is uninstalled, it removes access to the agent interface but does not delete previously generated conversations. Conversations are stored as part of user activity history and remain available unless explicitly deleted (subject to policy). Therefore, Statement 3 is correct.

Thus, the correct responses are Yes, No, Yes .

When building a custom analytics agent in Microsoft 365 Copilot that must process structured data from Excel files, advanced analytical capabilities are required. According to Microsoft AI Business Professional guidance, tasks such as performing mathematical calculations, generating aggregations, creating charts, and conducting structured data analysis require programmatic execution capabilities rather than simple text generation.

A code interpreter enables the agent to run Python-based analytical operations in a secure execution environment. This allows the agent to manipulate datasets, compute totals and averages, perform grouping and filtering, and generate visualizations such as bar charts or line graphs based on the Excel data. The interpreter bridges the gap between natural language instructions and executable analytical logic.

An image generator is designed for creative visual content and is unrelated to structured data analytics. Suggested prompts and templates improve usability and consistency but do not provide computational or visualization capabilities.

Therefore, to enable mathematical operations, aggregation, data analysis, and visualization of Excel sales data, the correct component to add to the agent is a code interpreter.

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.