AB-210 Certification Exam Guide + Practice Questions Updated 2026

Explanation:
Requirement Configuration
Define measurable sales target Goal metric
Aggregate opportunity revenue Rollup column
The correct configuration for defining measurable sales targets is Goal metric. In Dynamics 365 Sales, goals are measured by using goal metrics, which define what is being measured and how performance is calculated. Microsoft’s goal documentation explains that goals help measure progress toward targets such as revenue, while goal metrics and their rollup fields define the values used to calculate performance against those targets.
To aggregate opportunity revenue, use the Rollup column. A goal metric uses rollup fields/columns to calculate actual, in-progress, or custom values. Microsoft specifically describes a money-based goal metric that uses the Opportunity table and the opportunity actual revenue field to track money amounts from opportunities closed as won. This matches the requirement to aggregate opportunity revenue for monthly seller targets. Rollup query is not the best answer because it only adds filtering criteria to an existing goal metric, such as limiting records by owner, territory, or other conditions; it does not define the revenue aggregation itself. Goal hierarchy organizes parent-child goals, and forecasting supports pipeline projections, but neither defines the measurable target calculation or aggregates opportunity revenue for goal achievement.
References/topics: Dynamics 365 Sales goals; goal metrics; rollup columns/fields; opportunity revenue aggregation; seller revenue target tracking.

Explanation:
Requirement
Configuration or action
Make a product available for selling
Publish product
Organize related products so they inherit shared attributes
Product family
Create a combined offering of several products
Bundle
The correct action to make a product available for selling is Publish product. In Dynamics 365 Sales, products, families, and bundles are typically created or revised before being published. Microsoft states that publishing makes products available for selling, and sellers can choose only published products and bundles when creating sales records such as opportunities and quotes.
To organize related products so they inherit shared attributes, use a Product family. Product families provide the hierarchy used to classify and manage similar products. Microsoft’s product catalog documentation explains that a product family can contain child product families, products, and bundles in a hierarchy, and the parent family is used to structure related catalog items.
To sell coffee machines, filters, and grinders together, configure a Bundle. A bundle is the correct component when several products are sold together as one combined offering. Microsoft’s product catalog guidance distinguishes bundles from product families: families organize related catalog items, while bundles package multiple sellable products together. Currency is not used here because it supports pricing localization and monetary values, not catalog structure, publication, or combined product offerings.
References/topics: Product catalog lifecycle; publish product; product families; product bundles; Dynamics 365 Sales product catalog configuration.

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

Explanation:
The solution does not meet the goal because a billing policy for the Dynamics 365 Sales environment is associated with the pay-as-you-go consumption model, not the prepaid-credit model required in the question. Microsoft separates Dynamics 365 Sales 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 charges for the actual number of messages consumed by agents during the month.
For prepaid AI credits, the correct configuration is to purchase the Copilot message pack subscription and then assign that prepaid capacity to the required Power Platform/Dynamics 365 Sales environment. Microsoft’s setup steps for prepaid capacity specifically state that admins must purchase Copilot message packs through the Microsoft 365 admin center or Partner Center and assign prepaid capacity to the Power Platform environment through the Power Platform admin center.
So the proposed solution is wrong for the stated requirement. It may support monthly tracked consumption under pay-as-you-go, but it does not satisfy the explicit requirement to use pre-paid credits.
References/topics: Dynamics 365 Sales consumption-based billing; prepaid capacity; Copilot Studio message packs; Power Platform environment capacity assignment; pay-as-you-go billing policy.

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