Pass the Microsoft Certified: Dynamics 365 Sales AI Consultant Associate AB-210 Questions and answers with ExamsMirror

The administrator must have both the correct license and an environment that supports Dynamics 365 apps . Microsoft states that when creating a production or sandbox Power Platform environment with a Dataverse database, administrators can add Dynamics 365 apps such as Dynamics 365 Sales, but they must select Enable Dynamics 365 apps during database provisioning. Microsoft also states that a valid Dynamics 365 license is required to enable Dynamics 365 apps.

Therefore, the administrator must be assigned a Dynamics 365 Sales Enterprise license , and the environment must have Dataverse added with Dynamics 365 apps enabled . After the Sales license is available, Dynamics 365 Sales apps such as Sales Hub can be installed from the Power Platform admin center under the environment’s Dynamics 365 apps resources.

Option A is wrong because server-side synchronization is used for Exchange email, appointments, contacts, and tasks integration; it is not required to deploy Sales Hub. Option D is not required because a sandbox environment can support Dynamics 365 apps when Dataverse and Dynamics 365 apps are enabled. Option E is unnecessary unless the administrator is excluded from the security group; the scenario already states the administrator has the System Administrator role.

References/topics: Power Platform environment provisioning; Dataverse database; Enable Dynamics 365 apps; Dynamics 365 Sales licensing; Sales Hub deployment.

Requirement

Component

Record engagement is pending, completed, or failed

Sales Agent Runs table view

Weekly performance view of the Sales Close Agent in Research mode

Insights and metrics for the Sales Close Agent

For a specific opportunity that stopped receiving automated outreach, use the Sales Agent Runs table view . Microsoft states that to resolve the engagement status of a specific record, administrators can go to the sales agent run record view and filter the Regarding column by the record of interest. The Status field shows whether the engagement is Active , Failure , or Completed ; Active means pending, Failure means the engagement failed, and Completed means it finished successfully.

For the manager’s weekly performance requirement, use Insights and metrics for the Sales Close Agent . That is the performance reporting surface for the agent, not the per-record run table. The requirement specifically mentions a weekly performance view plus Last refreshed and a time period filter , which maps to the agent’s insights dashboard/metrics area. The Sales Agent Runs view is operational monitoring for individual records, while the insights and metrics view is for aggregate performance analysis such as engagement outcomes, response rates, and trend monitoring. Do not select Engage settings because settings configure how the agent behaves; they do not provide performance metrics. Opportunity pipeline view helps sellers manage opportunities, but it is not the agent performance monitoring dashboard.

References/topics: Sales Close Agent monitoring; Sales Agent Runs table; engagement status; Sales Close Agent insights and metrics; Research mode performance reporting.

The solution does not meet the goal. The requirement is explicit: AI billing must use pre-paid credits . Microsoft’s Dynamics 365 Sales billing guidance separates 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 bills for the actual number of messages consumed during the month.

Configuring capacity overages to a billing plan is not the prepaid-credit model. Overages are tied to consumption beyond allocated capacity and are handled through billing-plan/pay-as-you-go behavior. That conflicts with the requirement to use pre-purchased credits. For prepaid billing, the correct approach is to purchase Copilot Studio message packs or capacity packs and assign that prepaid capacity to the Dynamics 365/Power Platform environment. Microsoft’s Power Platform capacity guidance states that prepaid capacity can be assigned to environments, and when prepaid capacity is exhausted, administrators must reallocate capacity, purchase more credits, or enable pay-as-you-go billing.

Therefore, configuring overages may support monthly usage billing, but it does not satisfy the stated requirement that billing must use prepaid credits.

References/topics: Dynamics 365 Sales consumption-based billing; prepaid capacity; Copilot Studio message packs; Copilot credit capacity; pay-as-you-go overage handling.

The correct sales lifecycle is Lead → Opportunity → Quote → Order → Invoice . In Dynamics 365 Sales, a lead captures an initial prospect before the person or organization is qualified. Microsoft’s sales process guidance explains that sellers generally work with leads during the qualifying stage, and the goal is to qualify and advance the lead to the next stage of the sales process. Once qualified, the deal becomes an opportunity , which is the record used for pipeline tracking, revenue estimation, sales stages, probability, and forecasting analysis. Microsoft’s prospect-to-quote guidance states that Dynamics 365 Sales supports capturing, managing, scoring, and converting leads into opportunities when qualification criteria are met.

Quotes are then created from opportunities to present pricing proposals to customers. Microsoft states that quotes created from opportunities are prefilled with opportunity details and products. Once the proposal is accepted, the quote can be converted into a sales order for fulfillment and then into an invoice for billing; Microsoft’s quote/order/invoice process sample explicitly demonstrates converting an opportunity to a quote, a quote to a sales order, and a sales order to an invoice. Therefore, option B is the only sequence that correctly supports the full sales lifecycle.

References/topics: Lead management; opportunity pipeline; quote creation; order fulfillment; invoice billing; Dataverse Sales tables.