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

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 correct configuration is to set related record creation to Seller. The case study states that sales leadership requires flexibility in how leads are converted: inside sales need automatic opportunity creation, but field sellers need the option to manually decide whether an opportunity should be created when a lead is qualified. In the new lead qualification experience, Dynamics 365 Sales lets administrators control whether account, contact, and opportunity records are created automatically during lead qualification or whether sellers are prompted to choose which related records to create. Microsoft’s lead qualification guidance confirms that when automatic creation is not enabled, sellers are prompted to select which records should be created during qualification.

Option B and option E are wrong for field sellers because automatic creation would remove the manual decision point required by the case study. Option C is relevant to guiding sellers through sales stages, but the existing Lead to Opportunity Business Process Flow does not control whether related records are automatically created when a lead is qualified. Option D is unrelated because Copilot summaries help sellers review record information; they do not configure lead conversion behavior. Therefore, the required configuration for field sellers is Seller-controlled related record creation.

References/topics: Lead qualification experience; lead-to-opportunity conversion; related account, contact, and opportunity creation; Dynamics 365 Sales lead management.

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.

Create a Power Automate cloud flow.

Add a Dataverse trigger.

Define an approval step.

Test and activate the flow.

The correct automation pattern is an automated Power Automate cloud flow triggered by a Dataverse event. The case study states that the process must notify the seller’s manager when a draft quote is created and requires approval, and that approvals must use the Power Automate Approvals connector. Therefore, the flow should first be created as a cloud flow, then started by a Dataverse trigger such as when a row is added, modified, or deleted on the Quote table, filtered for the draft quote condition. Microsoft’s Dataverse trigger guidance confirms that this trigger runs when a selected Dataverse table row is created, modified, or deleted.

After the trigger is defined, the flow must include an approval step using Power Automate approvals. Microsoft’s approval workflow guidance states that Power Automate can manage approvals across services including Dynamics 365 and Dataverse-based processes. The final action is to test and activate the flow so the quote approval automation is available to users. Do not use a scheduled trigger because the requirement is event-driven, not time-based. Do not connect to the existing desktop flow because that desktop flow processes partner orders for fulfillment, not draft quote approvals. A Teams step is optional collaboration, not the required approval mechanism.

References/topics: Power Automate cloud flows; Dataverse triggers; Approvals connector; Dynamics 365 Sales quote approval automation; sales platform extension.

Requirement

Configuration

Advance the lead to the Development stage

Set the decision maker field as required.

Ensure that the default process is applied

Authorize the process for field sellers.

The lead qualification process should be controlled through the Lead to Opportunity Business Process Flow, because the case study states that field sellers use this existing process to manage leads. To prevent a lead from advancing to the Development stage until a decision maker is confirmed, configure the Decision Maker step as required in the business process flow. Microsoft’s business process flow guidance states that each stage contains steps mapped to columns, and a step can be made required so users must enter data before moving to the next stage. This stage-gating behavior directly satisfies the requirement that leads cannot progress until the decision maker is confirmed.

To ensure the correct process is applied for field sellers, authorize the business process flow for the field seller security role. Microsoft explains that business process flows can be associated with security roles so only users with those roles can view or use them, and that the first active process available for a user’s security role is applied by default according to process order.

Do not choose Power Automate to advance the lead; the requirement is to block advancement until a required qualification criterion is completed, not to automate progression. “Switch to a different process” is user action, not a configuration standard.

References/topics: Business process flows; stage-gating; Lead to Opportunity Sales Process; security role authorization; seller workflow standardization.

Requirement

Configuration

Automatically prioritize leads based on conversion probability

Predictive lead scoring

Ensure the lead scoring improvement requirement is met

Automatically retrain model

The correct capability for automatically prioritizing leads based on conversion probability is Predictive lead scoring . Dynamics 365 Sales predictive lead scoring assigns scores to leads so sellers can prioritize the leads most likely to qualify or convert. Microsoft’s Sales documentation states that predictive lead scoring helps sales teams prioritize leads based on scores and improve lead qualification outcomes. This directly matches Contoso’s requirement to guide sellers toward high-potential leads and reduce inconsistent manual prioritization across regions.

To meet the requirement that lead scoring must continuously improve based on historical sales outcomes, configure the model to automatically retrain . Microsoft’s predictive lead scoring guidance explains that retraining uses the latest leads in the organization to improve model accuracy, and automatic retraining allows the application to retrain the model every 15 days. This is the correct option because Contoso wants the scoring model to improve continuously as more closed lead outcome data becomes available.

“Lead scoring model” is too generic; the AI capability required is specifically predictive lead scoring. “Relationship intelligence” supports relationship analytics and engagement insights, but it does not score leads by conversion probability. “Configure forecast” applies to pipeline forecasting, not lead scoring accuracy.

References/topics: Predictive lead scoring; lead prioritization; scoring model accuracy; automatic model retraining; AI-driven lead qualification.

Issue

Action

Opportunity updated today is NOT included in the chart

Update roll-up settings

Time period for the goal is inaccurate

Have the manager update the goal

For the opportunity updated today not appearing in the goals chart, the issue is the goal rollup timing , not the opportunity record itself. Dynamics 365 Sales goal actuals are calculated through rollup processing. Microsoft states that automatic goal rollup duration and frequency are controlled from the Goals tab in system settings, and that manual rollup can also be performed when needed. Therefore, the correct action is to update the roll-up settings so goal charts reflect recent opportunity changes more appropriately. Microsoft also notes that selecting Recalculate updates goal actuals based on the latest data, confirming that goal charts depend on rollup recalculation rather than instant real-time updates.

For the inaccurate goal time period, the correct action is to have the manager update the goal . In Dynamics 365 Sales goal management, the goal manager is responsible for setting or modifying goal targets, adjusting the goal time period, and assigning the goal owner. The salesperson is typically the goal owner who is measured against the target, but the manager controls the goal definition and period.

References/topics: Dynamics 365 Sales goals; goal rollup settings; goal recalculation; goal manager responsibilities; opportunity target tracking.

The administrator must have both the correct license and an environment that supports Dynamics 365 apps . Microsoft states that when creating a production or sandbox Power Platform environment with a Dataverse database, administrators can add Dynamics 365 apps such as Dynamics 365 Sales, but they must select Enable Dynamics 365 apps during database provisioning. Microsoft also states that a valid Dynamics 365 license is required to enable Dynamics 365 apps.

Therefore, the administrator must be assigned a Dynamics 365 Sales Enterprise license , and the environment must have Dataverse added with Dynamics 365 apps enabled . After the Sales license is available, Dynamics 365 Sales apps such as Sales Hub can be installed from the Power Platform admin center under the environment’s Dynamics 365 apps resources.

Option A is wrong because server-side synchronization is used for Exchange email, appointments, contacts, and tasks integration; it is not required to deploy Sales Hub. Option D is not required because a sandbox environment can support Dynamics 365 apps when Dataverse and Dynamics 365 apps are enabled. Option E is unnecessary unless the administrator is excluded from the security group; the scenario already states the administrator has the System Administrator role.

References/topics: Power Platform environment provisioning; Dataverse database; Enable Dynamics 365 apps; Dynamics 365 Sales licensing; Sales Hub deployment.

The correct components are mobile security roles and appropriate user licenses . Installing the mobile app alone does not grant access to Dynamics 365 Sales records. Microsoft’s mobile setup guidance states that Dataverse security privileges control access to Dynamics 365 mobile apps, and the required mobile privilege is preconfigured for Sales roles but may need to be added to custom roles. It also states that the app must be shared with the security role assigned to the user, and users without the privilege can see an empty app list or an access error.

The license requirement is equally important. The Dynamics 365 Sales mobile experience exposes Sales Hub or Sales Professional according to the user’s license, so sellers must have the correct Dynamics 365 Sales license assigned before they can access the appropriate Sales app and records. Mobile offline profiles are used for offline synchronization scenarios; they are not the base requirement for record access after app installation. Inbound and outbound profiles are unrelated to Sales mobile access and are not used to authorize sellers in the mobile application.

References/topics: Dynamics 365 Sales mobile app; Dataverse security roles; mobile access privilege; Sales Hub mobile access; Dynamics 365 Sales licensing.