AB-730 Practice Questions

 When Microsoft 365 Copilot searches for content on the web, it uses the Bing search service.

Answer: Yes

 When Microsoft 365 Copilot searches for content on the web, it uploads the entire conversation history into the search request.

Answer: No

 When Microsoft 365 Copilot searches for content on the web, the query is anonymized and stripped of any user-identifiable information.

Answer: Yes

Microsoft 365 Copilot can use web grounding when a response requires current or public information. For web search, Copilot uses the Bing search service to retrieve relevant web results, so Statement 1 is Yes . This allows Copilot to supplement its response with up-to-date internet content when web grounding is enabled or selected.

Statement 2 is No because Copilot does not send the entire conversation history to Bing as a web search request. Instead, Copilot generates a search query based on the user’s prompt and relevant context. Sending the complete conversation would create unnecessary privacy and data exposure risk, which would conflict with Microsoft’s enterprise data protection model.

Statement 3 is Yes because Microsoft 365 Copilot is designed to protect user and tenant information during web grounding. Search queries are handled in a privacy-preserving way, with user-identifiable and tenant-identifiable information removed before the query is sent to Bing.

Statements:

You can add a Microsoft Teams chat as a knowledge source to a Microsoft 365 Copilot agent.

Answer: Yes

You can add a Microsoft 365 Copilot conversation as a knowledge source to a Copilot agent.

Answer: No

You can use an image file, such as a JPG file, as a knowledge source for a Microsoft 365 Copilot agent.

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

In Microsoft 365 Copilot, when content from a document is summarized or referenced, Copilot respects Microsoft 365 security, compliance, and data protection policies such as sensitivity labels . Sensitivity labels can restrict how content is accessed, shared, or processed, and Copilot behavior reflects these constraints.

The exhibit shows that Copilot is able to summarize the document but provides only limited or generalized insights, indicating restricted handling of the content. This is consistent with documents that have sensitivity labels applied (for example, Confidential or Highly Confidential), where Copilot may limit exposure of detailed content or apply safeguards when generating responses.

Other options do not align with the scenario. If the file were not supported, Copilot would not process it at all. If it were inaccessible outside the organization, that would affect sharing rather than summarization behavior. Being in a notebook does not impose restrictions on how content is summarized.

Therefore, the correct inference is that Document1.docx has a sensitivity label applied .

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