Free Practice Questions for the Microsoft Certified: Dynamics 365 Sales AI Consultant Associate AB-210 Exam (2026 Updated)

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.

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.

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.

Requirement

Configuration

Open the Pipeline view by default in Opportunities

Configure Opportunity main form

Open a specific form for the opportunity side panel

Set the default Opportunity form

Ability to expand or collapse the grid by sections

Enable aggregation on view controls

Display the average value at the bottom of the grid

Enable aggregation on view controls

To open the Pipeline view by default, configure the Opportunity main form by adding the Pipeline view control for Opportunities. Microsoft states that the read-only grid is the default view for opportunities, but administrators can set the Opportunities pipeline view as the default by customizing the Opportunity table form and adding the Pipeline view component. The configuration includes selecting the Opportunities table, choosing the opportunity view, and enabling grouping and aggregation.

To open a specific form in the opportunity side panel, use Set the default Opportunity form . Microsoft’s configuration guidance states that when sellers open an opportunity from the pipeline view, the side panel displays opportunity details, and administrators can change the default side-panel form to the main opportunity form or a custom form.

For expanding/collapsing by sections such as Owner or Account and displaying average values at the bottom of the grid, enable aggregation/grouping behavior on the Pipeline view control. Microsoft states that Enable grouping and Enable aggregation allow sellers to group and aggregate opportunities in the pipeline view. This supports sectioned grid behavior and aggregate values such as average, sum, or count. The quick create form is irrelevant because it controls record creation, not pipeline display behavior.

References/topics: Opportunity pipeline view; Opportunity main form; side panel default form; grouping and aggregation; pipeline grid configuration.

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 correct answer is C . To review the Sales Close Agent behavior for an opportunity, you open an opportunity researched by the agent and select See full research . Microsoft’s current Dynamics 365 Sales documentation describes this flow: sellers open the My top opportunities from AI agent view, open an opportunity, review the summary section, and then select See full research to open the Opportunity research page , which contains the complete research insights and recommendations.

This page is the right place to understand what the agent is surfacing and why it is helping progress deals. The Opportunity research page includes deal importance, deal risks and mitigations, deal overview, key signals, and other research-driven insights. Option A is incomplete and incorrectly starts from Forecast; the documented entry point is the Opportunities area and the AI-agent opportunity view. Option B is not the best answer because Sales Agent Runs is used for operational run records and permissions, not the seller-facing full research output. Option D is fabricated; there is no requirement to configure the opportunity pipeline view to force the full research page into every opportunity side panel.

References/topics: Sales Close Agent Research mode; Sales Opportunity Agent; Opportunity research page; See full research; AI-generated opportunity insights and recommendations.

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.

Requirement

Configuration

Enable AI features in the environment

Deploy Copilot in Dynamics 365 Sales

Allow administrators to create agents

Assign Copilot Studio author role

Allow sellers to use AI insights

Assign Dynamics 365 Sales security roles

Allow agents to analyze sales records

Configure Dataverse security permissions

The environment-level AI prerequisite is to deploy Copilot in Dynamics 365 Sales . Microsoft states that Copilot features must be turned on for Dynamics 365 Sales and that enabling Copilot activates the embedded chat and Copilot experiences in sales apps. Microsoft also identifies AI Agents and AI insight cards as environment capabilities required for Sales agents.

Administrators who design or create agents need Copilot Studio author capability. Microsoft’s Copilot Studio licensing guidance specifically lists the Copilot Studio authors role as a supported access configuration and explains that this role is assigned through the Power Platform admin center.

Sellers must receive appropriate Dynamics 365 Sales security roles because Sales agent access is role-driven. Microsoft states that users must be assigned Sales Manager or Salesperson roles to use Sales agent capabilities in Dynamics 365 Sales.

Finally, agents can only analyze sales records when Dataverse access is correctly configured. Dataverse security roles define table privileges such as Read, Create, Write, Delete, Append, and Append To, so sales data access must be governed through Dataverse security permissions .

References/topics: Copilot in Dynamics 365 Sales; Sales agents prerequisites; Copilot Studio author role; Dynamics 365 Sales security roles; Dataverse security permissions.

Requirement

Solution

Provide an interface to capture data during calls

Embedded canvas app

Display revenue analytics in the opportunity record

Power BI report

Send a Microsoft Teams alert when an opportunity value exceeds a specific amount

Power Automate flow

Allow sellers to view product sales trends by region

Power BI report

An embedded canvas app is the correct component for capturing custom data during calls because canvas apps are used to design tailored interfaces and can be embedded inside model-driven app forms. This gives sellers a purpose-built call capture experience directly on the Opportunity form instead of forcing them to use only standard fields or a rigid stage process. A Business process flow guides users through stages, but it is not the best fit for a custom call-data capture interface. Microsoft describes business process flows as guided process bars that lead users through defined stages and steps, not as custom UI components for call forms.

A Power BI report is required for both revenue analytics inside the opportunity record and product sales trends by region. Microsoft states that Power BI reports can be embedded in model-driven app main forms to bring rich reporting and analytics directly into record context, and Power BI Q & A allows users to ask natural language questions over report data.

A Power Automate flow is the correct solution for sending a Teams alert when opportunity value exceeds a threshold. A Dataverse-triggered cloud flow can run when an opportunity is created or updated, evaluate the value condition, and use the Microsoft Teams connector to post a message or card.

References/topics: Embedded canvas apps; Power BI embedded analytics; Power BI Q & A; Power Automate Dataverse triggers; Microsoft Teams connector; Dynamics 365 Sales extensibility.

The correct agent type is Sales Qualification Agent: Research and engage . The requirement is specifically about inbound lead processing: researching incoming leads, generating outreach, autonomously contacting leads, following up, and evaluating qualification during the engagement process. Microsoft defines Sales Qualification Agent as the AI agent used to automate lead qualification in Dynamics 365 Sales, especially for high-volume inbound leads from sources such as websites, events, and webinars. In Research and engage mode, the agent researches the lead, evaluates fit using target customer profile and BANT criteria, sends personalized outreach emails, engages based on responses, sends follow-up emails, detects positive intent, and then hands promising leads to sellers.

Research-only mode is not enough because it generates a draft outreach email for seller review but does not send outreach emails or detect positive intent from responses. Microsoft’s mode comparison explicitly shows that BANT checking, sending outreach, detecting positive intent, and follow-up emails are available in Research and engage mode, not Research-only mode. Sales Close Agent options are wrong because they apply to opportunity/deal execution, not initial lead qualification.

References/topics: Sales Qualification Agent; Research and engage mode; lead research; outreach automation; BANT qualification; AI-driven lead prioritization.