Free Microsoft AB-730 Practice Exam with Questions & Answers

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.

In the Microsoft 365 Copilot app, the Conversations list can display status indicators next to individual conversation titles. In the exhibit, the Standings conversation has a distinct indicator (a green badge) shown to the right of the conversation name. This badge is used to signal that the conversation includes a verified response.

A verified response indicator is intended to help users quickly recognize outputs that were produced with stronger grounding and traceability—for example, responses that include supporting citations or references that can be reviewed for accuracy. This aligns with Microsoft’s guidance on improving trust in AI output by making source-backed or verification-supported responses easier to identify and validate.

The other options do not match the indicator shown. Conversations that are shared or added to notebooks typically use different share/notebook iconography, and scheduled prompts are represented with scheduling-related indicators rather than a verification badge. “Anonymous data” is not something Copilot marks at the conversation level in this manner.

Therefore, the best inference is that the Standings conversation contains a verified response.

All three statements are false because generative AI responses are not guaranteed to be identical even when the prompt is the same. First, when grounded in the web , results can vary due to changing web content, different retrieved sources, or differences in how information is summarized at run time. Second, when grounded in your organization’s data , responses can change based on updates to files, emails, meetings, permissions, or which specific items Copilot retrieves as the most relevant context at that moment. Third, even when relying only on the model’s general knowledge, large language models are probabilistic: they may choose different wording, structure, examples, or emphasis across runs, especially when temperature/decoding settings and internal routing differ. In business scenarios, this means Copilot outputs should be treated as drafts that may require validation, and repeatability should be improved by adding precise constraints (cite specific sources, use fixed formats, specify exact sections, and request verbatim quotes where appropriate).

Agents created in the Microsoft 365 Copilot app are primarily designed for use within the Copilot Chat experience and related Copilot surfaces, not directly embedded inside individual applications like Word. Therefore, such agents are not automatically available in Microsoft Word, making Statement 1 incorrect.

However, these agents are designed for collaboration and reuse within an organization. Microsoft guidance confirms that agents can be shared with other users in the same tenant , allowing teams to leverage common tools, prompts, and knowledge sources. Hence, Statement 2 is correct.

For advanced automation scenarios involving complex workflows and third-party connectors, Microsoft provides Copilot Studio rather than the standard Copilot app. The Copilot app focuses on lightweight agent creation using natural language, files, and simple configurations. It does not support complex orchestration with external connectors. Therefore, Statement 3 is incorrect.

Thus, the correct answers are No, Yes, No .

Prompt injection is a generative AI security risk where an attacker inserts instructions (often hidden in text, documents, webpages, or user inputs) to override or manipulate the assistant’s intended behavior. This can lead to unintended actions such as ignoring policy controls, producing unsafe outputs, or attempting to reveal sensitive information. Because generative AI systems follow natural-language instructions, they can be socially engineered to prioritize malicious content unless safeguards are in place. This is why prompt injection can cause data exposure (for example, attempting to extract confidential content from grounded sources) and can also embed harmful instructions that redirect the model’s behavior. In enterprise settings like Microsoft 365 Copilot, mitigations include grounding boundaries, permission trimming, content filtering, and instruction hierarchy (system policies over user instructions). From a business governance perspective, users should treat untrusted inputs (emails, documents, web text) as potentially hostile and apply least-privilege access and validation when using AI outputs in decision-making.

Microsoft provides centralized activity management controls through the My Account portal, which allows users to manage privacy settings, activity history, and data associated with Microsoft 365 services, including Copilot. When the requirement is to delete all conversations with minimal effort, the most efficient method is to use the account-level activity management tools rather than deleting conversations individually.

The My Account portal enables bulk management of Copilot activity data, allowing users to clear conversation history in a consolidated manner. This approach aligns with Microsoft’s privacy-by-design framework, giving users control over their AI-generated interaction history without requiring administrative intervention.

Using the Copilot web or desktop app would typically require manually deleting conversations one at a time, increasing effort. The Windows 11 Settings app is unrelated to Microsoft 365 Copilot data management.

Therefore, to delete all Copilot conversations efficiently and with the least amount of effort, the correct approach is to use the My Account portal in Microsoft 365.

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.

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

In Microsoft 365 Copilot, notebooks are designed to organize related work into a single, reusable workspace. A notebook can group multiple Copilot conversations and associate them with shared reference materials (for example, the same set of files, links, or notes). This directly addresses both requirements in the question: (1) making conversations easier to find by collecting them in one place, and (2) enabling those conversations to use the same reference sources for grounding and continuity.

An agent is best when you want a specialized Copilot experience with predefined instructions, capabilities, and (optionally) a configured knowledge source. However, an agent does not primarily function as a “container” to gather and organize multiple existing conversations.

A page is used to capture and edit output (such as a generated report) for collaboration, not to organize multiple conversations with shared references. An app is a broader product surface and does not solve the conversation organization requirement.

Therefore, the best solution is to use a notebook .

The correct answer is instructions because an agent’s persona—such as being warm, friendly, formal, or analytical—is defined through its behavioral and communication guidance. In Microsoft 365 Copilot, the Instructions field controls how the agent responds, including tone, style, personality, response structure, and interaction patterns.

The description typically explains what the agent does, not how it communicates. Capabilities define what tasks the agent can perform, such as summarizing documents or analyzing data. Suggested prompts provide example user queries but do not control the agent’s personality or communication style.

To establish a warm and friendly persona, the instructions should explicitly state guidance such as: “Respond in a supportive, conversational tone. Use clear and positive language. Be encouraging and approachable.” This ensures consistent tone across all interactions.

Defining persona through instructions reflects prompt engineering best practices in generative AI, enabling predictable behavior, improved user experience, and alignment with organizational communication standards within Microsoft 365 Copilot environments.

After a Microsoft Teams meeting ends, the Microsoft 365 Copilot feature designed specifically to help you catch up on what happened—including key discussion points, decisions, and next steps—is Recap (often referred to as intelligent recap). Recap aggregates post-meeting artifacts such as the recording, transcript, and AI-generated insights, and surfaces actionable items so attendees can quickly understand outcomes without rewatching the full meeting. This aligns directly with the requirement to review “key points and next steps” after each meeting.

Meeting Whiteboard is a collaborative canvas used during meetings for brainstorming and sketches; it does not automatically produce a structured summary of decisions and actions. Meeting info provides logistical details (participants, agenda, attachments) rather than a synthesized outcomes summary. Thread summaries focus on chat or channel message threads, not the meeting’s recorded and transcribed content.

Therefore, to consistently catch up on key points and next steps after meetings, the correct Copilot feature to use is Recap .