Free Microsoft AB-730 Practice Exam with Questions & Answers | Set: 2

In Microsoft 365 Copilot, agents such as Researcher are accessed through the Agents experience within the Copilot app. If the user interface does not immediately display a specific agent, the correct action is to browse or search the available agents catalog. The exhibit shows the left navigation pane with an Explore agents option.

According to Microsoft AI Business Professional guidance, built-in and custom agents can be discovered and enabled through the Explore agents section. If the user already has the appropriate Copilot license and is signed in with their work account, there is no need to switch accounts or request another license.

Signing in through a browser does not change feature availability, and using a personal account would remove access to organizational features. Therefore, to access the Researcher agent, you should select Explore agents and search for Researcher.

==================================================

Microsoft 365 Copilot does not train the underlying large language model on your organization’s tenant data. Instead, it uses your organization’s data at run time to ground responses (for example, by retrieving relevant emails or documents you have permission to access). This separation protects confidentiality and supports enterprise compliance.

If a mailbox (or specific folders) is shared with you and your account has the required permissions, Copilot can summarize emails from that shared content because Copilot respects Microsoft 365 access controls (“permission trimming”).

Copilot also relies on Microsoft 365’s established security and compliance framework—identity, permissions, and policy enforcement—so it only surfaces content you’re authorized to see. This ensures Copilot’s outputs remain aligned with organizational governance, information protection, and least-privilege access principles.

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.

suggested prompts

In Microsoft 365 Copilot, suggested prompts are designed to help users get started quickly and interact with an agent effectively. Microsoft guidance for Copilot agents emphasizes that many users struggle most at the beginning—knowing what to ask, how to phrase requests, and how to take advantage of an agent’s purpose. Suggested prompts address this by providing ready-to-use examples that demonstrate the best ways to engage the agent for its intended scenarios.

Suggested prompts also act as lightweight “guardrails” for good prompting. They show users the expected input patterns, the types of tasks the agent can perform, and the kinds of outputs they can request. This accelerates adoption and improves the quality of results by steering users toward well-structured requests and appropriate context.

By contrast, capabilities describe what an agent can do (tools/features), instructions define how the agent should behave, and agent settings control configuration. None of those are primarily meant to help users begin conversations through example starters.

Therefore, the correct completion is suggested prompts.

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.

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.

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

Microsoft 365 Copilot notebooks use the version of a file that was uploaded or attached at the time it was added to the notebook. When a document such as Process.docx is added from a local folder, Copilot references that uploaded snapshot of the file. If the file is later modified locally, the notebook does not automatically sync or refresh with the updated local version unless the updated file is re-uploaded.

Microsoft guidance on grounding and file references explains that Copilot works with the specific content stored in Microsoft 365 or the attached artifact within the notebook session. Since the updated version remains in the local folder and was not reattached, Copilot continues to use the originally added version.

Therefore, during subsequent chats in the notebook, Copilot references only the original uploaded version of Process.docx.

==================================================

Comprehensive and Detailed 150 to 200 words of Explanation Microsoft AI Business professional documents:

Microsoft’s approach to transparency for AI-generated media relies on provenance signals rather than cosmetic indicators. File names and descriptions can be edited easily and are not reliable evidence of how an image was created. Watermarks may appear in some contexts, but they are not consistently applied across all AI image-generation workflows and can sometimes be removed or lost through copying, screenshotting, or file conversion.

Microsoft supports the use of content credentials to help users verify whether digital content was created or modified with AI. Content credentials are part of a provenance standard (often associated with C2PA) that can embed tamper-evident metadata into media files. When present, these credentials can show information about the tool or process used to generate or edit the image, providing a verifiable chain of origin.

Therefore, the most dependable way to verify whether the images were AI-generated is to check for content credentials (option C), since they are designed specifically to provide authenticity and provenance information for AI-created or AI-edited content.

Comprehensive and Detailed 150 to 200 words of Explanation Microsoft AI Business professional documents:

This scenario is an example of overreliance. Microsoft’s AI guidance highlights that Copilot is an assistive tool that can accelerate analysis and drafting, but users remain responsible for validating outputs—especially for high-impact business decisions. Overreliance occurs when someone treats AI output as authoritative and acts on it without applying judgment, cross-checking sources, or validating against current conditions.

Here, the merchandiser uses Copilot to generate stocking recommendations from historical sales data, then places a large order without reviewing the suggestions or incorporating current market trends. Even if the historical data is accurate, demand can shift due to seasonality changes, competitor actions, pricing, supply constraints, macroeconomic factors, or new product launches. Copilot’s recommendations should be treated as a starting point for decision-making, not the final decision.

Option A (verification) is the opposite behavior—checking accuracy before acting. Option C (fabrication) would involve Copilot inventing facts; the prompt doesn’t indicate fictional data, only unvalidated reliance. Option D (prompt injection) involves malicious instructions embedded in content to manipulate the model, which is not described here.

Therefore, the best answer is overreliance.

Comprehensive and Detailed 150 to 200 words of Explanation Microsoft AI Business professional documents:

Copilot in Microsoft Teams is designed to help users work faster by summarizing meeting content and assisting with message composition in chats and channels. Microsoft guidance highlights that Copilot can synthesize what was discussed in a meeting by generating a structured recap that includes key points, decisions, and action items. This directly matches option C. Copilot can also help you respond more quickly in Teams conversations by drafting replies grounded in the context of the existing chat or channel thread, which matches option D.

Options A and B are not Copilot capabilities. Muting and unmuting participants is a meeting control function handled by Teams meeting roles and settings, and it is not automatically driven by Copilot based on participant location. Creating custom backgrounds is a Teams visual feature (and can involve Designer or image tools), but it is not a Copilot-in-Teams productivity function for summarization or drafting based on conversation context.

Therefore, the two tasks you can achieve using Copilot in Teams are generating meeting summaries with decisions and action items, and drafting responses to channel messages based on conversation context.

When creating an agent in the Microsoft 365 Copilot app using a template, administrators or authorized users can configure specific behaviors and knowledge sources for the agent. Therefore, it is correct that you can choose which knowledge sources the agent can use. This ensures proper grounding in approved Microsoft 365 data such as SharePoint sites, OneDrive folders, or other organizational repositories. Controlling knowledge sources supports responsible AI principles, including data security, relevance, and compliance.

Agents created within Microsoft 365 are designed primarily for internal organizational use. As a result, sharing the agent with users inside the organization is supported, enabling collaboration and productivity improvements across teams.

However, sharing the agent with external users is not supported by default. External sharing would introduce security and compliance risks, so Microsoft enforces tenant-level boundaries to protect enterprise data.

These capabilities reflect best practices in managing AI prompts and agents securely within enterprise environments.