AB-730 Dumps with Practice Exam Questions Answers

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

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.

Use the Analyst agent for Prompt 1 because it is optimized for structured data work: consolidating worksheets, performing calculations, sentiment breakdowns by category (product line), and producing visualizations. These tasks align with analysis-style workflows where quantitative processing and charting are required.

Use the Researcher agent for Prompt 2 because it is designed to synthesize information from multiple sources, including SharePoint content plus web grounding , and to produce a well-structured brief with citations . Researcher is best when you need evidence-backed insights, reputable sourcing, and an organized narrative with risks and gaps.

Use Chat for Prompt 3 because the goal is drafting a refined executive email based on an attached document with tone control and communication standards. Chat excels at business writing, rewriting, tone adjustment, and producing polished communications without needing the deeper research workflow or heavy data analytics specialization.

Microsoft Purview is the correct choice because it is Microsoft’s unified compliance and data governance solution that helps organizations apply and enforce policies across Microsoft 365 content— including Copilot-related interactions where those interactions are captured in services such as Microsoft 365 audit, eDiscovery, and Purview compliance experiences. Purview supports capabilities such as data loss prevention (DLP) , retention , eDiscovery , audit , and sensitivity labeling so organizations can manage and govern data and AI-assisted content in line with regulatory and internal requirements. In contrast, Microsoft Entra ID focuses on identity and access management, Intune focuses on device and application management, and Defender for Cloud focuses on cloud security posture management. Governance policies for Copilot-generated conversations and associated compliance controls align most directly with Purview , which is designed to manage information protection and compliance across the Microsoft 365 environment.