Microsoft AI Business Professional Exam (AB-730) - Microsoft

Statements: You can add a Microsoft Teams chat as a knowledge source to a Microsoft 365 Copilot agent. Answe r: Yes You can add a Microsoft 365 Copilot conversation as a knowledge source to a Copilot agent. Answe r: No You can use an image file, such as a JPG file, as a knowledge source for a Microsoft 365 Copilot agent. Answe r: NO Microsoft 365 Copilot Agent Builder supports grounding agents in approved knowledge sources so responses are accurate and permission-trimmed. Teams chats can be used as a knowledge source: Microsoft Learn confirms you can ground an agent in Teams data, including chat messages (and optionally scope to specific chats), enabling the agent to reference collaboration context when answering questions. A Copilot conversation itself is not a supported “knowledge source” option; knowledge sources are configured from items like SharePoint content, Teams, email, websites, uploaded files, and connectors—not prior chat transcripts. Finally, JPG images are not supported as knowledge-source file types. Microsoft’s supported file types for agent knowledge include documents like .doc/.docx, .pdf, .ppt/.pptx, .txt, and Excel formats (.xls/.xlsx), but not image formats. Therefore, you cannot use a JPG as a knowledge source for a Copilot agent.

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.<br />
<br />
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.<br />
<br />
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<br />
for ensuring grounded, accurate responses in Microsoft 365 Copilot.

<img src="https://examsqa.com/storage/question-images/microsoft-ai-business-professional-exam-ab-730-2_page_3_Im4.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
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.<br />
While users can interact with Researcher, provide prompts, and refine outputs during conversations,<br />
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 This reflects a key generative AI governance principle in enterprise environments: system-level Microsoft 365 Copilot experience. controls remain centrally managed to maintain data protection, compliance, and responsible AI implementation across the organization.

Microsoft 365 Copilot follows Microsoft’s enterprise data governance and privacy principles, which allow users to manage their own conversation history where appropriate. According to Microsoft AI Business Professional guidance, users can review and delete individual Copilot conversation histories directly from their personal account settings without requiring administrative intervention.<br />
<br />
Option D is correct because the My Account portal in Microsoft 365 Copilot allows individual users to manage their activity history, including deleting specific conversations. This enables targeted removal of sensitive interactions while retaining other conversation data.<br />
<br />
Option A is incorrect because the Copilot app itself does not provide full account-level activity management capabilities. Options B and C are administrative tools used for tenant-wide governance, compliance, retention policies, and eDiscovery. These portals typically require administrative privileges and are not intended for individual user self-service deletion of specific conversations. Therefore, to delete a single confidential Copilot conversation without affecting other chats and without requiring administrator approval, the correct tool is the My Account portal in Microsoft 365 Copilot.

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.