Microsoft AB-210 - Accelerating Sales Pipelines with AI in Dynamics 365

Requirement

Configuration

Define pricing for products

Price list item

Automatically use a localized price list

Territory

Group product prices for each region

Price list

The correct component for defining product-specific prices is the Price list item . In Dynamics 365 Sales, price list items connect a product, unit, pricing method, and amount to a specific price list. Microsoft’s product pricing guidance states that price lists and price list items are used to define product pricing, and price list items are where the per-product pricing details are configured.

To automatically use a localized price list, configure Territory . Dynamics 365 Sales can automatically select a default price list for opportunities, quotes, orders, and invoices based on the sales territory of the user. Microsoft states that a price list can be associated with a territory by using the Territory Default Pricelist connection role, allowing users in that territory to have the correct price list selected by default.

To group product prices for each region, use a Price list . A price list is the container that groups the prices charged for products or services. Microsoft guidance explains that organizations can create multiple price lists to maintain separate pricing structures for different regions, sales channels, or territories. Currency supports monetary localization, but it does not group regional product prices by itself. Product bundle is unrelated because it combines products for sale as a package, not regional pricing.

References/topics: Product catalog pricing; price lists; price list items; territory-based default price lists; regional pricing configuration.

Requirement

Agent mode

Recommend action for disengaged deals

Research

Generate insights from records and research into a unified deal view

Research

Ensure customer interactions are compliant

Engage

The first two requirements belong to Research mode because they are insight-generation functions for opportunity management. Microsoft describes the opportunity-focused Sales agent as identifying risks such as disengaged stakeholders, slowing momentum, and competitive pressure, then recommending targeted actions to keep the deal moving forward. It also provides a comprehensive deal view by surfacing buyer needs, stakeholder roles, competitor mentions, and deal health in one unified place. This directly matches both “recommend targeted action for disengaged deals” and “generate insights from CRM records, emails, meetings, and web research into a unified deal view.”

The compliance requirement maps to Engage mode because compliance matters when the agent communicates externally with customers. Sales Close Agent Engage mode automates customer engagement through outreach and follow-up emails, and Microsoft states that admins configure an email delivery compliance profile so the agent’s communications follow organizational policies and regulatory requirements. Research mode produces insights for sellers; it does not perform customer outreach. Therefore, use Research for opportunity intelligence and Engage for compliant customer interaction.

References/topics: Sales Close Agent; Sales Opportunity Agent Research mode; Sales Close Agent Engage mode; opportunity risk insights; compliance profile for agent email communications.

The correct Research mode capabilities are analyzing historical interaction data to generate opportunity insights and reviewing deal signals with risks and recommended mitigations . Microsoft’s Sales Opportunity Agent documentation describes the opportunity-focused agent as helping sellers focus on important opportunities by identifying high-value and at-risk deals, providing critical insights and recommendations, and helping sellers mitigate risks. Microsoft also states that the agent gathers information from multiple sources and provides a streamlined research experience, stakeholder and competitor intelligence, and actionable risk mitigation strategies.

Option C is correct because the agent uses opportunity context, CRM history, emails, meetings, and other available signals to generate deal insights. Option D is also correct because Microsoft’s Responsible AI FAQ specifically identifies early risk detection and recommended mitigation strategies based on historical data and communication analysis. Options A and B describe customer engagement behavior: running sales sequences or initiating follow-up communication. That belongs to engagement automation, not Research mode. Option E is too workflow-task oriented; Research mode surfaces insights and recommendations, but it is not primarily a task-generation or outreach automation engine.

References/topics: Sales Close Agent Research mode; Sales Opportunity Agent; opportunity insights; deal signals; risk mitigation; intelligent opportunity research.

Statement

Correct selection

To enable the business process flow to pass validation, you should ensure that

the column used to evaluate the condition is added to the preceding stage.

After the flow has been updated to pass validation, when a user starts creating a new pet record, the user will see

one stage.

The condition in the business process flow evaluates the Type column to determine whether the pet is a Cat . However, the preceding stage, Basic Details , only contains the Name step. In a business process flow, a branching rule must be based on steps in the stage immediately before the condition. Microsoft’s business process flow design guidance states that branching rules must be based on the steps in the preceding stage, so the Type column must be added as a step in the Basic Details stage before the condition can validate correctly.

After validation is corrected, a user who starts creating a new pet record will initially see one stage : Basic Details . The Litter type stage is conditional and appears only when the Type value satisfies the rule, meaning the pet type equals Cat. Microsoft explains that branch selection is automatic and happens in real time based on the rules defined in the process definition. Until the user enters a Type value that satisfies the condition, the cat-specific branch is not part of the visible process path.

References/topics: Business process flows; conditional branching; preceding-stage steps; process validation; model-driven app process bar.