Requirement

Configuration

Blueprints

Name the blueprint workspace and pin the workspace.

Questions

Create a business function with seeded prompts.

For Blueprints, the correct configuration is to name the blueprint workspace and pin the workspace. The requirement is not asking to regenerate analysis; it asks for a reliable way to return to frequently used research output. In Sales Research Agent, a generated blueprint exists inside a workspace, and Microsoft states that the workspace displays the workspace name, can be renamed, and can be switched from the workspace menu. That makes naming and pinning the workspace the correct operational pattern for reusable research access.

For Questions, the correct configuration is to create a business function with seeded prompts. Sales Research Agent business functions are designed to tailor research to a specific use case, and administrators can add starter prompts. Microsoft explains that starter prompts appear on the Sales Research Agent home page for quick access and that the full prompt is sent to the agent when selected. This directly satisfies the requirement to retain a reusable library of approved questions.

Do not select regenerate the blueprint because regeneration refreshes or recreates analysis, but it does not create a persistent shortcut to frequently used research. Do not select custom table or manual prompt questions in Sales Copilot because the native Sales Research Agent feature already supports reusable business-function prompts.

References/topics: Sales Research Agent; research blueprints; workspace management; business functions; seeded/starter prompts; intelligent opportunity research.

The issue is that the sales manager already generated a Sales Research Agent blueprint but forgot to include the quarterly competitive intelligence brief. The brief is an external document and the case study states it is delivered as a PDF document , so the correct first content action is to upload the competitive intelligence brief as a PDF file , not CSV. Microsoft’s Sales Research Agent documentation states that users can select Add data to upload files including CSV, Excel, or PDF to augment research with additional data.

The second required action is to add a data source , because the competitive intelligence brief is not part of the default Dynamics 365 Sales data. Sales Research Agent connects to Dynamics 365 Sales data by default, but additional external files must be added as supporting data sources before they can influence the analysis. The documentation identifies the Data area as the place where the research data source is specified and where additional data sources can be added.

The final action is to regenerate the canvas/blueprint so the agent reprocesses the analysis using the newly added PDF. Refreshing alone is not the best answer because the problem is not stale data; it is missing context. Regeneration creates updated research output with the new source included.

References/topics: Sales Research Agent; research canvas; adding PDF data sources; blueprint regeneration; intelligent opportunity research.

Requirement

Component

Mountaineer range

Product family

Athlete package

Product bundle

Metal range

Product property

The Mountaineer range should be configured as a Product family because it represents a product classification hierarchy. Dynamics 365 Sales uses product families to organize related products, child products, and bundles under a parent structure. Microsoft’s product catalog guidance states that product families can contain child product families, products, and bundles in a hierarchy, which fits the mountaineer cycle range with economy and premium fitting variations.

The Athlete package should be configured as a Product bundle because it combines multiple sellable items: a cycle, connected devices, and subscription-based analytics services. A bundle is used when multiple products are sold together as one commercial package. Dynamics 365 Sales allows products to be associated with a bundle, including quantities and required or optional components.

The Metal range should be configured as a Product property because sellers must choose a configurable attribute—chrome, aluminum, or titanium—when adding the mountaineer cycle to an opportunity. Product properties define product characteristics such as size, color, or component, and can be used at run time when adding products to opportunities, quotes, orders, or invoices.

References/topics: Product catalog setup; product families; product bundles; product properties; opportunity product configuration.

For Dynamics 365 Sales predictive lead scoring, the model cannot be created unless there is enough historical lead outcome data in the selected training window. Microsoft’s predictive lead scoring configuration requirement states that the organization must have at least 40 qualified leads and 40 disqualified leads in the selected training period. The official guidance specifically explains that if the model is trained with leads from the past three months, the organization needs “at least 40 qualified and 40 disqualified leads” created and closed during that period.

In the sandbox, AdventureWorks has 30 qualified leads and 20 disqualified leads. However, 10 of the qualified leads are older than three months, and the business requirement says predictive scoring must be enabled for leads created within the last three months. Therefore, only 20 qualified leads are usable for this model. The sandbox currently has 20 usable qualified leads and 20 disqualified leads. To meet the required threshold of 40 each, the company needs 20 more qualified leads and 20 more disqualified leads . Simply creating 40 new leads is not enough because predictive scoring requires outcome-classified leads, not merely open or newly created records.

References/topics: Configure predictive lead scoring; lead scoring model training data requirements; AI-driven lead prioritization in Dynamics 365 Sales.

Requirement

Tool

Perform purchase required by CFO

Microsoft 365 admin center

Configure Sandbox billing

Power Platform admin center

Configure Production billing

Microsoft 365 admin center

Why: Production requires reliable AI capacity so sellers are not blocked when prepaid Copilot capacity is depleted. The correct production setup is pay-as-you-go / billing policy configuration through the Microsoft 365 admin center . Azure portal is not the best answer here because the scenario says no Azure subscriptions are available , and Microsoft 365 admin center can be used for the billing policy workflow. Microsoft Agent 365 is for agent management/governance, not billing configuration.

The required fix is about visibility and security , not agent operating mode. In the scenario, production has EnableRoleBasedSystemViews set to true, which restricts system views based on role configuration. Because the business requirement says all sellers should be able to access disqualified leads , the role-based system view setting must be updated so sellers can access the view that exposes leads disqualified by the Sales Qualification Agent.

The second required action is to change Lead table permissions. The customized Salesperson role currently grants sellers read access only to leads they own. That is too restrictive because leads disqualified by the Sales Qualification Agent may not be owned by each seller. To let all sellers view those records, sellers need organization-level Read permission on the Lead table. Option A is wrong because upgrading the agent to research and engage mode affects how the agent researches and interacts with leads; it does not solve seller access to disqualified records. Option C is also wrong because the look-back period controls which historical leads the agent evaluates, not who can view disqualified leads.

References/topics: Sales Qualification Agent; role-based system views; Dataverse security roles; Lead table read access; AI-driven lead qualification.

Requirement

Agent mode

Recommend action for disengaged deals

Research

Generate insights from records and research into a unified deal view

Research

Ensure customer interactions are compliant

Engage

The first two requirements belong to Research mode because they are insight-generation functions for opportunity management. Microsoft describes the opportunity-focused Sales agent as identifying risks such as disengaged stakeholders, slowing momentum, and competitive pressure, then recommending targeted actions to keep the deal moving forward. It also provides a comprehensive deal view by surfacing buyer needs, stakeholder roles, competitor mentions, and deal health in one unified place. This directly matches both “recommend targeted action for disengaged deals” and “generate insights from CRM records, emails, meetings, and web research into a unified deal view.”

The compliance requirement maps to Engage mode because compliance matters when the agent communicates externally with customers. Sales Close Agent Engage mode automates customer engagement through outreach and follow-up emails, and Microsoft states that admins configure an email delivery compliance profile so the agent’s communications follow organizational policies and regulatory requirements. Research mode produces insights for sellers; it does not perform customer outreach. Therefore, use Research for opportunity intelligence and Engage for compliant customer interaction.

References/topics: Sales Close Agent; Sales Opportunity Agent Research mode; Sales Close Agent Engage mode; opportunity risk insights; compliance profile for agent email communications.

Statement

Correct selection

To enable the business process flow to pass validation, you should ensure that

the column used to evaluate the condition is added to the preceding stage.

After the flow has been updated to pass validation, when a user starts creating a new pet record, the user will see

one stage.

The condition in the business process flow evaluates the Type column to determine whether the pet is a Cat . However, the preceding stage, Basic Details , only contains the Name step. In a business process flow, a branching rule must be based on steps in the stage immediately before the condition. Microsoft’s business process flow design guidance states that branching rules must be based on the steps in the preceding stage, so the Type column must be added as a step in the Basic Details stage before the condition can validate correctly.

After validation is corrected, a user who starts creating a new pet record will initially see one stage : Basic Details . The Litter type stage is conditional and appears only when the Type value satisfies the rule, meaning the pet type equals Cat. Microsoft explains that branch selection is automatic and happens in real time based on the rules defined in the process definition. Until the user enters a Type value that satisfies the condition, the cat-specific branch is not part of the visible process path.

References/topics: Business process flows; conditional branching; preceding-stage steps; process validation; model-driven app process bar.

The correct actions are to enable server-side synchronization and approve the users’ mailboxes . This is a very specific Dynamics 365 Sales mobile prerequisite. Microsoft’s Sales mobile setup guidance states that to set a regarding record for a meeting, server-side synchronization must be enabled in the environment and the email address must be approved. The mobile meeting documentation repeats the same requirement: users can set the regarding record only when server-side synchronization is enabled and the email address is approved.

This makes options A and B the only correct pair. Server-side synchronization connects Dynamics 365 with Exchange/Outlook data for appointments, contacts, tasks, and email synchronization. Microsoft’s server-side synchronization documentation describes it as the synchronization mechanism between customer engagement apps and Exchange, including support for appointments and mobile scenarios. A mobile offline profile controls offline data availability, not whether Outlook meetings can be tracked to customer records. Relevance search improves search behavior and performance, but it does not enable the Regarding field for meetings.

References/topics: Dynamics 365 Sales mobile app; meeting tracking; Regarding record; server-side synchronization; mailbox approval; Outlook appointments.

Requirement

Automation type

Notify a manager when a high-value opportunity is created

Power Automate automated cloud flow

Validate the products with an external ERP system every Sunday

Power Automate scheduled cloud flow

Display a guided lead qualification interface on the lead form

Business process flow

Update an external ERP system when an opportunity is won

Power Automate automated cloud flow

A Power Automate automated cloud flow is the correct automation type when work must run automatically after a business event occurs. Microsoft describes cloud flows as flows that can perform actions automatically after an event triggers them, such as sending a notification after a triggering event occurs. Therefore, notifying a manager when a high-value opportunity is created and updating an external ERP system when an opportunity is won are both event-driven scenarios, so they should use automated cloud flows with Dataverse triggers.

A Power Automate scheduled cloud flow is correct for validating products with an external ERP system every Sunday. Microsoft states that a scheduled cloud flow runs at a specific time or recurring schedule, such as daily or weekly, and uses a recurrence trigger. That directly matches the weekly Sunday validation requirement.

A Business process flow is correct for displaying a guided lead qualification interface on the lead form. Business process flows provide a streamlined user experience that guides users through defined processes, and Dynamics 365 Sales documentation explains that stages and steps display in a control at the top of a form. Instant cloud flow is not used because none of the requirements ask for a manually triggered user action.

References/topics: Power Automate automated cloud flows; scheduled cloud flows; Dataverse triggers; Business process flows; Dynamics 365 Sales automation and extensibility.