Microsoft AB-210 Exam With Confidence Using Practice Dumps

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.

The correct answer is Rounding Amount . In Dynamics 365 Sales price list item configuration, rounding is used when calculated prices must follow a specific price-ending convention, such as ending in .98 or .99 . Microsoft’s pricing guidance explains that price list items can use rounding behavior so calculated product prices can be rounded and made to end in a specified amount, such as 99 cents. The value that defines the exact ending amount is the Rounding Amount . Therefore, to make all calculated prices end in $.98 , the administrator would configure the rounding amount as 0.98 .

Rounding Policy is not precise enough by itself. It controls the direction of rounding, such as rounding up, down, or to the nearest value, but it does not define the exact cents-ending requirement. Pricing Method determines how the price is calculated, such as a currency amount, percentage of list price, markup, or margin. Percentage is used when a percentage-based pricing method is selected, but it does not force prices to end in $.98 . The requirement is explicitly about the final rounded price ending, so Rounding Amount is the correct function.

References/topics: Price lists; price list items; rounding amount; rounding policy; Dynamics 365 Sales product pricing.

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.