AB-210 Exam Dumps : Accelerating Sales Pipelines with AI in Dynamics 365

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.

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