AB-210 Microsoft Accelerating Sales Pipelines with AI in Dynamics 365 Free Practice Exam Questions (2026 Updated)

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

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.

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.

Requirement

Configuration

Enable guided sales qualifications

Business process flow

Allow sellers to create multiple opportunities when qualifying a lead

Lead qualification experience

Display emails with images

Timeline

Notify supervisors when leads are qualified

Power Automate cloud flow

Guided sales qualification is handled by a Business process flow because BPFs define the sales stages and required steps sellers follow during lead-to-opportunity execution. Microsoft describes lead qualification as the movement of a lead through the sales process into an opportunity, and business process flows are the native model-driven mechanism for guided stage-based work.

Creating multiple opportunities during qualification is controlled by the Lead qualification experience . Microsoft’s lead qualification configuration allows administrators to customize how account, contact, and opportunity records are created when a lead is qualified, including seller-controlled conversion behavior.

Full related emails, including rich email content, belong in the Timeline because the timeline control displays activities related to a record, including emails, appointments, phone calls, notes, and tasks. Microsoft also states the enhanced email experience is available from the Timeline section of customer engagement apps.

Supervisor notification should be implemented with a Power Automate cloud flow . A Dataverse-triggered cloud flow can run when a lead row changes status or when a qualification process creates an opportunity, then notify the supervisor.

References/topics: Business process flows; lead qualification experience; Dynamics 365 Sales timeline; Power Automate Dataverse triggers; lead-to-opportunity qualification automation.

The correct Research mode capabilities are analyzing historical interaction data to generate opportunity insights and reviewing deal signals with risks and recommended mitigations . Microsoft’s Sales Opportunity Agent documentation describes the opportunity-focused agent as helping sellers focus on important opportunities by identifying high-value and at-risk deals, providing critical insights and recommendations, and helping sellers mitigate risks. Microsoft also states that the agent gathers information from multiple sources and provides a streamlined research experience, stakeholder and competitor intelligence, and actionable risk mitigation strategies.

Option C is correct because the agent uses opportunity context, CRM history, emails, meetings, and other available signals to generate deal insights. Option D is also correct because Microsoft’s Responsible AI FAQ specifically identifies early risk detection and recommended mitigation strategies based on historical data and communication analysis. Options A and B describe customer engagement behavior: running sales sequences or initiating follow-up communication. That belongs to engagement automation, not Research mode. Option E is too workflow-task oriented; Research mode surfaces insights and recommendations, but it is not primarily a task-generation or outreach automation engine.

References/topics: Sales Close Agent Research mode; Sales Opportunity Agent; opportunity insights; deal signals; risk mitigation; intelligent opportunity research.

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 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 correct answer is Opportunity summary . The requirement is not to score the opportunity, show the next activity, or display health indicators; it is to reduce the seller’s manual review effort before contacting the customer. Microsoft’s Copilot capability for Dynamics 365 Sales provides AI-generated summaries for opportunity records so sellers can quickly understand key deal context, related activities, emails, and important history without reading the full timeline manually. Microsoft specifically states that Copilot record summarization generates concise summaries of key information from sales records such as opportunities, leads, and accounts.

Because the company uses a custom opportunity form , the opportunity summary widget must be added to that form. Microsoft’s implementation guidance explicitly flags custom opportunity forms and asks whether the opportunity summary widget has been added, and the Copilot summary documentation notes that the opportunity summary widget is available by default on the standard form but must be added to custom forms. Up next guides sellers to the next activity, Health score and Predictive opportunity scoring evaluate opportunity risk or likelihood, and Timeline highlights is narrower than the full AI-generated opportunity overview.

References/topics: Copilot opportunity summary; custom opportunity forms; AI-generated sales record summaries; seller productivity in Dynamics 365 Sales.

Requirement

Configuration

Define shared properties for several drone models

Product family

Combine drones and accessories into a package

Bundle

Represent a single drone model

Product

The correct configuration is based on the product catalog hierarchy in Dynamics 365 Sales. A Product family is used when several related products need to share common characteristics or inherited properties. For example, a drone product family can define shared attributes such as flight time, camera type, battery compatibility, or warranty tier, and individual drone models can inherit or specialize those attributes. This is exactly what the requirement means by defining shared properties for several drone models.

A Bundle is used when multiple sellable products are combined into one package. If the company wants to sell a drone together with spare batteries, propellers, carrying cases, or accessories, that package should be configured as a bundle. The seller can then add the bundle to an opportunity, quote, order, or invoice instead of manually selecting each component.

A Product represents a single sellable item, such as one specific drone model. Price list is not correct for any of these requirements because price lists define pricing structures and currencies; they do not define catalog hierarchy, shared product properties, or bundled offerings.

References/topics: Dynamics 365 Sales product catalog; product families; product bundles; products; product hierarchy and catalog configuration.

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.