Microsoft AB-210 Dumps

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.

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

The Sales Close Agent in Research mode is the correct fit for assessing opportunity risk and prioritizing opportunities that are gaining traction. Microsoft’s AI agents guidance states that the opportunity-focused sales agent helps sellers close deals faster by autonomously researching opportunities, providing visibility into emerging risks, and highlighting promising opportunities. It is designed to identify high-value and at-risk opportunities so sellers can prioritize their effort and act on critical insights.

The Sales Close Agent in Engage mode is the correct fit for recommending opportunity products to clients automatically. Microsoft describes Sales Close Agent as an autonomous agent for high-velocity sales execution that engages customers, recommends products, handles objections, and drives transactions toward closure using configured product catalog and pricing information.

The Sales Qualification Agent is not appropriate for these scenarios because it is lead-focused, not opportunity-focused. It researches inbound leads, evaluates fit, generates outreach, and can hand promising leads to sellers depending on the configured mode. It does not manage opportunity risk, opportunity traction, or client product recommendations for active deals.

References/topics: Sales Close Agent; opportunity research; opportunity risk; opportunity prioritization; Sales Close Agent Engage mode; product recommendations.

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.

The correct two UI elements are the Select record type dropdown and one of the Customize field dropdowns on the work item card. In Dynamics 365 Sales, a “company” record is represented by the Account table. The screenshot currently shows the selected record type as Contacts , which would expose contact-related fields such as Full Name, Job Title, and Company Name. That is not the correct entity if the requirement is to display the industry of a company. Therefore, the record type must first be changed to Accounts .

After selecting Accounts , modify the card layout by selecting the Industry field in the Customize section. Microsoft’s sales accelerator workspace guidance states that work item appearance can be customized for each record type so sellers see the most relevant information in their work list. The work item appearance page lets administrators choose the record type and configure the fields displayed on the work item card.

Do not modify Lock customization as the answer target. That controls whether users can personalize the layout; it does not select the account entity or display the Industry field.

References/topics: Sales accelerator workspace; work item appearance; account record type; field customization; seller work list configuration.

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

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

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.

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

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.

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

Component

Mountaineer range

Product family

Athlete package

Product bundle

Metal range

Product property

The Mountaineer range should be configured as a Product family because it represents a product classification hierarchy. Dynamics 365 Sales uses product families to organize related products, child products, and bundles under a parent structure. Microsoft’s product catalog guidance states that product families can contain child product families, products, and bundles in a hierarchy, which fits the mountaineer cycle range with economy and premium fitting variations.

The Athlete package should be configured as a Product bundle because it combines multiple sellable items: a cycle, connected devices, and subscription-based analytics services. A bundle is used when multiple products are sold together as one commercial package. Dynamics 365 Sales allows products to be associated with a bundle, including quantities and required or optional components.

The Metal range should be configured as a Product property because sellers must choose a configurable attribute—chrome, aluminum, or titanium—when adding the mountaineer cycle to an opportunity. Product properties define product characteristics such as size, color, or component, and can be used at run time when adding products to opportunities, quotes, orders, or invoices.

References/topics: Product catalog setup; product families; product bundles; product properties; opportunity product configuration.