AB-210 Accelerating Sales Pipelines with AI in Dynamics 365 Question and Answers

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.

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.

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.

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.

Requirement

Component

Record engagement is pending, completed, or failed

Sales Agent Runs table view

Weekly performance view of the Sales Close Agent in Research mode

Insights and metrics for the Sales Close Agent

For a specific opportunity that stopped receiving automated outreach, use the Sales Agent Runs table view . Microsoft states that to resolve the engagement status of a specific record, administrators can go to the sales agent run record view and filter the Regarding column by the record of interest. The Status field shows whether the engagement is Active , Failure , or Completed ; Active means pending, Failure means the engagement failed, and Completed means it finished successfully.

For the manager’s weekly performance requirement, use Insights and metrics for the Sales Close Agent . That is the performance reporting surface for the agent, not the per-record run table. The requirement specifically mentions a weekly performance view plus Last refreshed and a time period filter , which maps to the agent’s insights dashboard/metrics area. The Sales Agent Runs view is operational monitoring for individual records, while the insights and metrics view is for aggregate performance analysis such as engagement outcomes, response rates, and trend monitoring. Do not select Engage settings because settings configure how the agent behaves; they do not provide performance metrics. Opportunity pipeline view helps sellers manage opportunities, but it is not the agent performance monitoring dashboard.

References/topics: Sales Close Agent monitoring; Sales Agent Runs table; engagement status; Sales Close Agent insights and metrics; Research mode performance reporting.

The correct answer is Product families because the requirement is to organize similar products into searchable categories. In Dynamics 365 Sales, product families are used to classify and group related products under a product hierarchy. Microsoft’s product catalog guidance explains that products can be created as standalone products or inside a family depending on how the organization wants to organize and classify them, and the training module specifically describes creating product family hierarchies that include product bundles and individual products.

For the example in the question, “flat screen TV” would be the product family, while individual versions such as 42-inch, 55-inch, OLED, QLED, or 4K models would be products inside that family. This makes browsing and searching easier for sellers because related variants are grouped logically. Product unit groups define how products are sold, such as each, box, or case; they do not categorize products. Related products are used for cross-sell, upsell, substitute, or accessory recommendations, not primary catalog organization. Product bundles combine multiple products sold together as a package. Therefore, the correct catalog structure is Product families .

References/topics: Product catalog setup; product families; product classification; product hierarchy; Dynamics 365 Sales core product configuration.

The minimum dataset for a predictive lead scoring model is 40 qualified leads and 40 disqualified leads . Microsoft’s Dynamics 365 Sales documentation states that an organization must have created and closed at least 40 qualified and 40 disqualified leads within the selected training period to train the model. The broader lead and opportunity scoring documentation confirms the same threshold and distinguishes lead scoring from opportunity scoring: lead scoring requires qualified and disqualified leads, while opportunity scoring requires won and lost opportunities.

This distinction is critical. Predictive lead scoring predicts the likelihood that a lead will qualify or convert based on historical lead outcomes, so the model needs examples of both successful and unsuccessful lead qualification results. Won and lost opportunities are not the correct training records for lead scoring; they apply to predictive opportunity scoring. The question also states that the company has historical sales records for three years, but the model requirement is based on the minimum qualifying lead dataset, not merely the total age of available data. Therefore, the required minimum is 40 qualified leads and 40 disqualified leads .

References/topics: Predictive lead scoring; lead scoring model prerequisites; qualified leads; disqualified leads; AI-driven lead prioritization.

The correct scenarios are B and C . Sales Research Agent is designed for research and analysis, not autonomous record updates or email engagement. Microsoft describes the agent as an AI-powered research canvas that lets users solve complex business questions through natural language, generate research blueprints, review sales-data insights, and ask follow-up questions to refine the analysis. It can use Dynamics 365 Sales data, uploaded offline files such as CSV, Excel, or PDF, and connected data sources to support pipeline exploration and sales operations analysis.

Option B is correct because Microsoft states that Sales Research Agent may use Bing Search only when the Bing search consent setting is enabled. When Bing search is disabled, the agent operates only on internal data sources that the user already has permission to access. Option C is also correct because the agent generates a research blueprint with visualizations and a text overview, and users can continue iterating by asking follow-up questions or changing visualizations on the canvas. Option A is wrong because Sales Research Agent is analytical; it does not update opportunities with risk or importance values. Option D is wrong because automatic email engagement is the domain of sales/qualification engagement agents, not Sales Research Agent.

References/topics: Sales Research Agent; research canvas; AI-generated blueprints; Bing search consent; internal sales data analysis; intelligent opportunity research.

The correct action is Update a single block in the canvas . In Sales Research Agent, the research canvas generates a blueprint that contains research findings, visualizations, and blocks of insight. Microsoft states that users can interact with visualizations through the AI cursor, ask follow-up questions, and then choose whether to update the existing block or generate a new blueprint. If Update block is selected, the existing block is updated with the new information; if Generate new blueprint is selected, the agent creates a new blueprint and adds a journey line.

This distinction matters. The requirement is to update one component , not rebuild the full blueprint. Regenerate the blueprint or Refresh the blueprint would affect the broader blueprint output: Microsoft documents refresh/regenerate as actions for using latest data or producing new visualizations and insights, not for targeted single-block editing. The Dynamics 365 AI Optimization hub is unrelated to editing individual research canvas blocks.

References/topics: Sales Research Agent; research canvas; blueprint blocks; AI cursor; update block; intelligent opportunity research.

The three default rule-style suggestions are the Record Owner of the initiating record , the Created By user of the initiating record , and the manager assigned on the seller’s system user record . Suggested contacts in Dynamics 365 Sales Teams chat are intended to help sellers quickly find coworkers who are relevant to the record they are working on. Microsoft states that administrators can enable suggested contacts when a seller starts a new connected chat, and that rules-based contact suggestions can be configured for supported Dynamics 365 record types.

The rule engine supports relational rules: Microsoft explains that a relational rule suggests a user who has a relationship with the linked record type or one of its related records, and administrators can select a user field directly on the record or through related entities. The record owner and created-by user are direct relational users on the initiating record. The seller’s manager is reached through the system user relationship. The business-unit owner is not the default suggestion path for seller collaboration, and “last modified by” or a user who updated a timeline activity are not the default rule answers in this configuration set.

References/topics: Teams chat in Dynamics 365 Sales; suggested contacts; rules-based contact suggestions; relational suggestion rules; sales collaboration.

Requirement

Configuration

Open the Pipeline view by default in Opportunities

Configure Opportunity main form

Open a specific form for the opportunity side panel

Set the default Opportunity form

Ability to expand or collapse the grid by sections

Enable aggregation on view controls

Display the average value at the bottom of the grid

Enable aggregation on view controls

To open the Pipeline view by default, configure the Opportunity main form by adding the Pipeline view control for Opportunities. Microsoft states that the read-only grid is the default view for opportunities, but administrators can set the Opportunities pipeline view as the default by customizing the Opportunity table form and adding the Pipeline view component. The configuration includes selecting the Opportunities table, choosing the opportunity view, and enabling grouping and aggregation.

To open a specific form in the opportunity side panel, use Set the default Opportunity form . Microsoft’s configuration guidance states that when sellers open an opportunity from the pipeline view, the side panel displays opportunity details, and administrators can change the default side-panel form to the main opportunity form or a custom form.

For expanding/collapsing by sections such as Owner or Account and displaying average values at the bottom of the grid, enable aggregation/grouping behavior on the Pipeline view control. Microsoft states that Enable grouping and Enable aggregation allow sellers to group and aggregate opportunities in the pipeline view. This supports sectioned grid behavior and aggregate values such as average, sum, or count. The quick create form is irrelevant because it controls record creation, not pipeline display behavior.

References/topics: Opportunity pipeline view; Opportunity main form; side panel default form; grouping and aggregation; pipeline grid configuration.