Free and Premium Microsoft AB-210 Dumps Questions Answers

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.

The required fix is about visibility and security , not agent operating mode. In the scenario, production has EnableRoleBasedSystemViews set to true, which restricts system views based on role configuration. Because the business requirement says all sellers should be able to access disqualified leads , the role-based system view setting must be updated so sellers can access the view that exposes leads disqualified by the Sales Qualification Agent.

The second required action is to change Lead table permissions. The customized Salesperson role currently grants sellers read access only to leads they own. That is too restrictive because leads disqualified by the Sales Qualification Agent may not be owned by each seller. To let all sellers view those records, sellers need organization-level Read permission on the Lead table. Option A is wrong because upgrading the agent to research and engage mode affects how the agent researches and interacts with leads; it does not solve seller access to disqualified records. Option C is also wrong because the look-back period controls which historical leads the agent evaluates, not who can view disqualified leads.

References/topics: Sales Qualification Agent; role-based system views; Dataverse security roles; Lead table read access; AI-driven lead qualification.

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.

For Dynamics 365 Sales predictive lead scoring, the model cannot be created unless there is enough historical lead outcome data in the selected training window. Microsoft’s predictive lead scoring configuration requirement states that the organization must have at least 40 qualified leads and 40 disqualified leads in the selected training period. The official guidance specifically explains that if the model is trained with leads from the past three months, the organization needs “at least 40 qualified and 40 disqualified leads” created and closed during that period.

In the sandbox, AdventureWorks has 30 qualified leads and 20 disqualified leads. However, 10 of the qualified leads are older than three months, and the business requirement says predictive scoring must be enabled for leads created within the last three months. Therefore, only 20 qualified leads are usable for this model. The sandbox currently has 20 usable qualified leads and 20 disqualified leads. To meet the required threshold of 40 each, the company needs 20 more qualified leads and 20 more disqualified leads . Simply creating 40 new leads is not enough because predictive scoring requires outcome-classified leads, not merely open or newly created records.

References/topics: Configure predictive lead scoring; lead scoring model training data requirements; AI-driven lead prioritization in Dynamics 365 Sales.

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

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.

Issue

Configuration

Sellers are not able to access the dialer in Sales Hub

Assign the security role to the root business unit.

Existing third-party telephony system stopped working

Disable the Microsoft Teams dialer for sellers using the third-party system.

Dialer is not accessible in a custom model-driven app

Set the custom app as an available app in the dialer configuration.

For the first issue, the security role must be associated with the root business unit . Microsoft states that when Teams dialer is enabled for specific security roles, the selected roles must be associated with the root business unit; otherwise, users do not see the Teams dialer in Sales Hub. Merely assigning the role in the dialer configuration is not enough if the role is not rooted correctly.

For the second issue, Teams dialer conflicts with third-party telephony integrations that use Dynamics 365 Channel Integration Framework. Microsoft explicitly notes that when Microsoft Teams dialer is enabled, other telephony systems connected through Channel Integration Framework stop working for users for whom Teams dialer is enabled. Therefore, sellers who must continue using the third-party telephony system should not have Teams dialer enabled.

For the custom model-driven app issue, the dialer must be made available for that app in the dialer configuration. In the Teams dialer advanced options, administrators select the apps where the dialer should be available; Sales Hub is selected by default, so custom apps must be added explicitly.

References/topics: Microsoft Teams dialer; Dynamics 365 Sales calling; security roles; root business unit; Channel Integration Framework; custom model-driven app availability.

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.

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.

Requirement

Agent mode

Recommend action for disengaged deals

Research

Generate insights from records and research into a unified deal view

Research

Ensure customer interactions are compliant

Engage

The first two requirements belong to Research mode because they are insight-generation functions for opportunity management. Microsoft describes the opportunity-focused Sales agent as identifying risks such as disengaged stakeholders, slowing momentum, and competitive pressure, then recommending targeted actions to keep the deal moving forward. It also provides a comprehensive deal view by surfacing buyer needs, stakeholder roles, competitor mentions, and deal health in one unified place. This directly matches both “recommend targeted action for disengaged deals” and “generate insights from CRM records, emails, meetings, and web research into a unified deal view.”

The compliance requirement maps to Engage mode because compliance matters when the agent communicates externally with customers. Sales Close Agent Engage mode automates customer engagement through outreach and follow-up emails, and Microsoft states that admins configure an email delivery compliance profile so the agent’s communications follow organizational policies and regulatory requirements. Research mode produces insights for sellers; it does not perform customer outreach. Therefore, use Research for opportunity intelligence and Engage for compliant customer interaction.

References/topics: Sales Close Agent; Sales Opportunity Agent Research mode; Sales Close Agent Engage mode; opportunity risk insights; compliance profile for agent email communications.

Requirement

Configuration

Define pricing for products

Price list item

Automatically use a localized price list

Territory

Group product prices for each region

Price list

The correct component for defining product-specific prices is the Price list item . In Dynamics 365 Sales, price list items connect a product, unit, pricing method, and amount to a specific price list. Microsoft’s product pricing guidance states that price lists and price list items are used to define product pricing, and price list items are where the per-product pricing details are configured.

To automatically use a localized price list, configure Territory . Dynamics 365 Sales can automatically select a default price list for opportunities, quotes, orders, and invoices based on the sales territory of the user. Microsoft states that a price list can be associated with a territory by using the Territory Default Pricelist connection role, allowing users in that territory to have the correct price list selected by default.

To group product prices for each region, use a Price list . A price list is the container that groups the prices charged for products or services. Microsoft guidance explains that organizations can create multiple price lists to maintain separate pricing structures for different regions, sales channels, or territories. Currency supports monetary localization, but it does not group regional product prices by itself. Product bundle is unrelated because it combines products for sale as a package, not regional pricing.

References/topics: Product catalog pricing; price lists; price list items; territory-based default price lists; regional pricing configuration.

The correct date field is Actual End because the goal is based on calls that are finished during the calendar year. For the Phone Call table, Microsoft defines Actual End as the actual end date and time of the phone call, which is the proper date to evaluate whether the completed call falls within the January–December goal period.

The correct rollup field is Actual (Integer) because the goal measures the number of outgoing calls, not revenue or another money-based amount. Microsoft’s goal metric guidance explains that goal metrics can use count/integer values, and specifically gives sales calls made by a salesperson as an example of an integer goal metric. The actual integer field represents the achieved count as of the latest rollup calculation.

The correct source record type status is Made because the requirement is for outgoing calls that were completed. Microsoft’s Phone Call status reason options include Open , Made , Canceled , and Received ; “Made” represents completed outgoing phone calls, while “Received” represents completed incoming calls. Therefore, the rollup must count Phone Call records with status Made , using Actual End as the date boundary and Actual (Integer) as the accumulated value.

References/topics: Dynamics 365 Sales goals; goal metrics; rollup fields; phone call activity status; Actual End date; completed outgoing call tracking.

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.