Pass the Microsoft Certified: Dynamics 365 Sales AI Consultant Associate AB-210 Questions and answers with ExamsMirror

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.

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.

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.

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.

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 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.

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 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.