Most Recent Microsoft AB-210 Exam Dumps

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.

The correct feature is Cloud flow. Dynamics 365 Sales mobile app push notifications are created through Power Automate by using the Send push notification V2 action. Microsoft's Sales mobile documentation states that the Dynamics 365 Sales mobile app supports push notifications created with the Send push notification V2 action, where the mobile app is set to Sales, the target app is selected, recipients are defined, and the notification can open a specific table record when selected.

Power Automate documentation also describes the creation process as a notification from a flow: go to Power Automate, create an automated flow, choose a trigger such as Microsoft Dataverse, then add the Send push notification V2 action. That matches the requirement to configure several seller notifications for the Sales mobile app. Classic flow is not the correct answer because modern mobile notification automation should be implemented with Power Automate cloud flows, not legacy/classic workflow patterns. Plug-in is also wrong because plug-ins are server-side Dataverse extensions for custom business logic; they are not the standard no-code configuration mechanism for mobile push notifications.

References/topics: Dynamics 365 Sales mobile app; custom push notifications; Power Automate cloud flows; Send push notification V2; Dataverse-triggered seller automation.

The correct outcome is that the agent disqualifies the lead, notifies the supervisor, and the lead continues to be assigned to the agent. In Research-only mode, the Sales Qualification Agent evaluates whether the lead fits the target customer profile. Microsoft states that when target customer profile suitability is high or medium, the lead is handed over to a seller according to the configured assignment rule. When target customer profile suitability is low, the agent disqualifies the lead, notifies the supervisor, and the lead remains assigned to the agent.

Option A is wrong because Research-only mode does not always transfer every lead to a seller; low-fit leads can be disqualified. Option C describes Research and engage behavior, where the agent sends outreach, manages responses, and hands over leads when positive intent is detected. Research-only mode generates outreach drafts but does not send outreach emails or engage with leads. Option D is also wrong because BANT criteria are only used by Research and engage mode, not Research-only mode. Therefore, a low target customer profile suitability result in Research-only mode results in agent disqualification and supervisor notification.

References/topics: Sales Qualification Agent; Research-only mode; target customer profile suitability; lead disqualification; supervisor notification; lead handoff rules.

The correct answer is D. Opportunities that use the expired price list can continue through their lifecycle. In Dynamics 365 Sales, a price list can include a Start Date and End Date to define the effective period for that price list, such as a promotional pricing period. Microsoft's pricing guidance explains that price lists and price list items define pricing for products, and that price calculation applies across opportunity, quote, order, and invoice records.

The expiration date controls the effective availability of the price list going forward; it does not automatically invalidate existing opportunity records that already reference that price list. This distinction matters operationally: if an opportunity was already created with a valid price list, the sales process can continue without forcing users to replace pricing midstream. That preserves pricing consistency across the opportunity lifecycle and prevents disruption to quotes, orders, and downstream sales documents.

Option A is too strong because Dynamics 365 does not require replacement of prices simply because the referenced price list later expires. Option B incorrectly limits use based on the creation date of the opportunity. Option C is not the best answer because the key supported behavior is continuation of existing opportunities, not adding expired price lists to new opportunities with a warning.

References/topics: Price lists; price list start and end dates; opportunity pricing; product catalog pricing; opportunity lifecycle management.

The correct configuration is Sales Qualification Agent in Research and engage mode. The question contains one conflicting sentence about human-managed outreach, but the explicit agent requirements require autonomous outreach, response handling, BANT evaluation, positive-intent detection, disqualification of poor-fit leads, supervisor notification, and seller handoff. Those capabilities map only to Research and engage mode.

Microsoft's Sales Qualification Agent documentation states that both modes can research leads and check target customer profile fit, but only Research and engage mode checks BANT criteria, sends outreach emails, detects positive intent, sends follow-up emails, and engages with leads based on their responses. Microsoft's handoff criteria documentation also states that BANT criteria are only used by Research and engage mode, and that leads satisfying BANT and purchase-interest criteria are handed over to sellers, while leads that do not satisfy the configured criteria are disqualified and added for supervisor review.

Option B or D would be correct only if the controlling requirement were strictly ''human sellers must manage all outreach.'' But the listed automation requirements go beyond Research-only mode, so the exam answer is C.

References/topics: Sales Qualification Agent; Research and engage mode; target customer profile; BANT; purchase intent; lead handoff; supervisor review.