Microsoft AB-210 Accelerating Sales Pipelines with AI in Dynamics 365 Exam Practice Test

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

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.

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

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.

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.

The correct configuration is Sales Qualification Agent in Research and engage mode . The question contains one conflicting sentence about human-managed outreach, but the explicit agent requirements require autonomous outreach, response handling, BANT evaluation, positive-intent detection, disqualification of poor-fit leads, supervisor notification, and seller handoff. Those capabilities map only to Research and engage mode.

Microsoft’s Sales Qualification Agent documentation states that both modes can research leads and check target customer profile fit, but only Research and engage mode checks BANT criteria, sends outreach emails, detects positive intent, sends follow-up emails, and engages with leads based on their responses. Microsoft’s handoff criteria documentation also states that BANT criteria are only used by Research and engage mode, and that leads satisfying BANT and purchase-interest criteria are handed over to sellers, while leads that do not satisfy the configured criteria are disqualified and added for supervisor review.

Option B or D would be correct only if the controlling requirement were strictly “human sellers must manage all outreach.” But the listed automation requirements go beyond Research-only mode, so the exam answer is C .

References/topics: Sales Qualification Agent; Research and engage mode; target customer profile; BANT; purchase intent; lead handoff; supervisor review.

Requirement

Configuration

Quantities a product can be sold

Unit group

Group product pricing for different currencies

Price list

Sale price of a product

Price list item

The correct configuration uses Unit group , Price list , and Price list item because these are the core Dynamics 365 Sales product catalog pricing components. A Unit group defines the collection of units in which a product can be sold. For example, a product might be sold as each, box, case, or pallet. The unit group provides the available quantity structure, while a primary unit identifies the default or base unit inside that group. Therefore, the requirement to define the quantities in which a product can be sold maps to Unit group , not just Unit or Primary unit.

A Price list is used to group product pricing, and each price list is associated with a currency. For a global company selling in different markets, separate price lists can be maintained for currencies such as USD, EUR, or GBP. The Price list item defines the actual sale price of a specific product within a price list, including the product, unit, currency context, and pricing amount. A discount list only defines discount rules, and a product family organizes products, not pricing.

References/topics: Product catalog configuration; unit groups and units; price lists; price list items; global pricing and currency-based product pricing in Dynamics 365 Sales.

The correct answer is Goal metric . In Dynamics 365 Sales, the goal metric defines how goal performance is calculated. Microsoft explains that each goal uses a goal metric to determine how the goal is tracked, and goal metrics can track actual, in-progress, and custom values through rollup fields. For won opportunity revenue, the metric can use the Opportunity table as the source and roll up the actual value for opportunities that are closed as won.

The quarterly requirement is handled by the goal’s time period. The goal metric specifies the calculation logic, including the source table, source attribute, date attribute, and source status such as Won. Microsoft’s goal metric documentation states that the date attribute is validated against the goal time period, so records participate in the rollup only when their date falls between the goal start and end dates. A rollup query is not the best answer because it only applies additional filtering criteria to an existing goal metric; it does not create the core calculation.

References/topics: Dynamics 365 Sales goals; goal metrics; rollup fields; won opportunity calculations; quarterly goal tracking.

The solution does not meet the goal. The requirement is explicit: AI billing must use pre-paid credits . Microsoft’s Dynamics 365 Sales billing guidance separates Copilot and agent billing into two models: prepaid capacity and pay-as-you-go . Prepaid capacity uses Copilot Studio message pack subscriptions that are purchased in advance, while pay-as-you-go bills for the actual number of messages consumed during the month.

Configuring capacity overages to a billing plan is not the prepaid-credit model. Overages are tied to consumption beyond allocated capacity and are handled through billing-plan/pay-as-you-go behavior. That conflicts with the requirement to use pre-purchased credits. For prepaid billing, the correct approach is to purchase Copilot Studio message packs or capacity packs and assign that prepaid capacity to the Dynamics 365/Power Platform environment. Microsoft’s Power Platform capacity guidance states that prepaid capacity can be assigned to environments, and when prepaid capacity is exhausted, administrators must reallocate capacity, purchase more credits, or enable pay-as-you-go billing.

Therefore, configuring overages may support monthly usage billing, but it does not satisfy the stated requirement that billing must use prepaid credits.

References/topics: Dynamics 365 Sales consumption-based billing; prepaid capacity; Copilot Studio message packs; Copilot credit capacity; pay-as-you-go overage handling.

The correct behavior is that the Sales Close Agent retries up to three times within the next hour , using an exponential backoff strategy. If those immediate attempts fail, the system continues retrying the engagement over the next three days . If the engagement still fails after that retry window, the record is marked as a failure . Microsoft’s Sales Close Agent documentation explicitly describes this retry pattern for engagement errors and also identifies the possible run statuses as Active, Failure, and Completed.

Option A is wrong because the agent does not retry only once after 24 hours, and failed records are not marked Completed. Option B is wrong because the agent has a defined automatic retry cycle before failure status is finalized. Option C is also wrong because the retry behavior is bounded; it does not retry indefinitely every few minutes. The failure handling is controlled, time-limited, and designed to avoid uncontrolled AI-credit consumption while still giving transient failures a chance to recover. This matters for sales managers because failed engagements must be monitored and remediated through the Sales Agent Runs view rather than assuming every selected record was successfully progressed.

References/topics: Sales Close Agent; engagement processing; retry behavior; Sales Agent Runs monitoring; opportunity/deal progression.

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.

The correct configuration is Business process flow . A structured lead qualification process requires sellers to move through defined stages and steps before a lead is converted into an opportunity. Microsoft describes business process flows as a way to guide users through stages of sales, marketing, or service processes toward completion. Business process flows can also include branching logic and defined steps, which makes them the correct mechanism for standardizing how sellers qualify leads before conversion.

The other options do not enforce a structured qualification path. Sales accelerator helps prioritize seller activities and guide daily work, but it is not the core process-control mechanism for lead qualification. Lead activity timeline displays activities, emails, notes, and interactions; it does not define qualification stages. Lead assignment rules route leads to sellers or teams, but they do not structure the seller’s qualification steps. Predictive lead scoring helps prioritize leads by likelihood to qualify, but it does not require sellers to complete a defined qualification process. Therefore, to make sellers follow a controlled lead qualification sequence before converting leads to opportunities, configure a Business process flow .

References/topics: Business process flows; lead qualification; structured sales process; lead-to-opportunity conversion; Dynamics 365 Sales process guidance.