Microsoft AB-730 Dumps Questions Answers

In Microsoft 365 experiences, the standard way to invoke or reference people and specific resources in-context is by using the @mention pattern. Microsoft 365 Copilot extends this familiar interaction model to agents: when you want to switch to, invoke, or direct a question to a specific agent from within an existing Copilot conversation, you use @ followed by the agent’s name. This makes the agent selection explicit and reduces ambiguity about which assistant or capability you want to use for the next turn.

The other syntaxes listed are commonly associated with different systems: square brackets are not used for agent invocation, hashtags are typically used for topics/tags, and slash commands are used in some chat applications for command execution—but they are not the standard method for calling a Copilot agent in Microsoft 365 Copilot Chat.

Therefore, to chat with an agent named Agent1 during an open Copilot conversation, you should enter @Agent1 .

Microsoft guidance for effective prompting emphasizes clarity and context as the two most important factors. Providing context (Option A) ensures that Copilot understands the background, data sources, and constraints relevant to the task. This improves grounding and reduces ambiguity, leading to more accurate and useful responses.

Providing a clear goal (Option D) is equally critical. A well-defined objective—such as summarizing, analyzing, or drafting—helps Copilot determine the correct approach, structure, and level of detail for the response. Without a clear goal, outputs may be generic or misaligned with user expectations.

Using a broad range of instructions can introduce confusion rather than clarity. Acronyms may reduce clarity unless explicitly defined. Keeping prompts generic is discouraged because specificity improves quality and relevance of responses.

Therefore, the correct answers are A (adding context) and D (providing a clear goal) .

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 .