Microsoft Accelerating Sales Pipelines with AI in Dynamics 365 AB-210 Exam Dumps: Updated Questions & Answers (August 2026)

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.

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.

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.

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

Advance the lead to the Development stage

Set the decision maker field as required.

Ensure that the default process is applied

Authorize the process for field sellers.

The lead qualification process should be controlled through the Lead to Opportunity Business Process Flow, because the case study states that field sellers use this existing process to manage leads. To prevent a lead from advancing to the Development stage until a decision maker is confirmed, configure the Decision Maker step as required in the business process flow. Microsoft’s business process flow guidance states that each stage contains steps mapped to columns, and a step can be made required so users must enter data before moving to the next stage. This stage-gating behavior directly satisfies the requirement that leads cannot progress until the decision maker is confirmed.

To ensure the correct process is applied for field sellers, authorize the business process flow for the field seller security role. Microsoft explains that business process flows can be associated with security roles so only users with those roles can view or use them, and that the first active process available for a user’s security role is applied by default according to process order.

Do not choose Power Automate to advance the lead; the requirement is to block advancement until a required qualification criterion is completed, not to automate progression. “Switch to a different process” is user action, not a configuration standard.

References/topics: Business process flows; stage-gating; Lead to Opportunity Sales Process; security role authorization; seller workflow standardization.

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.

The correct insight to share is Recommended actions . Sales Close Agent in Research mode is opportunity-focused: it helps sellers understand the state of a deal, identify risks, and decide what to do next. Microsoft explains that the opportunity agent provides critical insights and recommendations so sellers can ramp up on opportunities, engage the right stakeholders, and mitigate risks effectively. The Responsible AI FAQ also describes the agent as identifying deal risks early and providing recommended mitigation strategies based on historical data and communication analysis.

The question specifically says the seller must decide how to proceed and wants to move the deal forward. That points directly to recommended actions, not static context. Financial health may be part of a broader opportunity view, but it is not the best answer for next-step guidance. Budget, Authority, Need, and Timeline is BANT qualification and belongs to lead qualification scenarios, especially Sales Qualification Agent, not opportunity research. Blueprints are generated by the Sales Research Agent on a research canvas for analytics-style exploration, not by the Sales Close Agent opportunity summary. Therefore, the correct insight category is Recommended actions .

References/topics: Sales Close Agent Research mode; opportunity recommendations; deal risk mitigation; Sales Opportunity Agent insights; opportunity progression.

The correct answer is Goal metric . In Dynamics 365 Sales, the goal metric defines how goal performance is calculated. Microsoft explains that each goal uses a goal metric to determine how the goal is tracked, and goal metrics can track actual, in-progress, and custom values through rollup fields. For won opportunity revenue, the metric can use the Opportunity table as the source and roll up the actual value for opportunities that are closed as won.

The quarterly requirement is handled by the goal’s time period. The goal metric specifies the calculation logic, including the source table, source attribute, date attribute, and source status such as Won. Microsoft’s goal metric documentation states that the date attribute is validated against the goal time period, so records participate in the rollup only when their date falls between the goal start and end dates. A rollup query is not the best answer because it only applies additional filtering criteria to an existing goal metric; it does not create the core calculation.

References/topics: Dynamics 365 Sales goals; goal metrics; rollup fields; won opportunity calculations; quarterly goal tracking.