AB-210 Practice Questions

The proposed solution meets the requirements. Copilot in Dynamics 365 Sales is designed to provide AI-generated insights, such as opportunity summaries, which fulfills the need for sales managers to get information about deals. The concept of using it in "Research mode" implies leveraging these informational capabilities without triggering automated actions. The critical part of the solution, allowing sellers to manually review insights, directly addresses the constraint of preventing automatic outreach. All AI-generated content, including email drafts, requires explicit user review and action before any communication is sent to a buyer, keeping the seller in full control.

B. No: This option is incorrect. The solution effectively meets both goals by providing the required deal insights through Copilot's analytical features while ensuring no automatic outreach occurs due to the mandatory manual review process by sellers.

1. Microsoft Learn

Dynamics 365 Sales Documentation. "Get an opportunity summary with Copilot." This document explains how Copilot provides insights by summarizing key information about an opportunity

including deal value

close date

and recent activities. This directly supports the "insights about deals" requirement. The process described is informational and requires user initiation.

2. Microsoft Learn

Dynamics 365 Sales Documentation. "Compose and send email messages using Copilot." This source details the process for using Copilot to draft emails. It explicitly states

"Copilot suggests content that you can review

edit

and send." This confirms that the outreach is not automatic and requires manual review and action from the seller

aligning with the proposed solution.

3. Microsoft Learn

Dynamics 365 Sales Documentation. "Copilot for Sales FAQ." In the "Data privacy and security" section

it is clarified that Copilot generates content and suggestions based on data but does not act autonomously. The user is always in control of saving or sending any generated content

which reinforces the principle of no automatic outreach.

The value that determines how the system rounds a calculated price is the Rounding Amount field on the price-list item.

By entering 0.98 in this field, every calculated unit price is forced to the nearest value that ends in “.98”, regardless of the pricing method that produced the initial figure. The companion fields (Rounding Policy and Rounding Option) control the direction of rounding, but only Rounding Amount sets the actual monetary increment to which the price is rounded. Therefore, to ensure that all prices finish with “$ .98”, you must configure the Rounding Amount.

A. Percentage – Defines volume-discount tiers; it does not influence the final cents value of a unit price.

B. Pricing Method – Determines how the base price is calculated (e.g., Currency Amount, Percent Markup) but performs no rounding.

D. Rounding Policy – Specifies whether to round up, down, or to the nearest value, yet needs Rounding Amount to know what value to round to; by itself it can’t create “.98” pricing.

1. Microsoft Learn: “Create a price list and price list items”

section Specify price calculation details – Rounding amount: “Enter the value you want the price rounded to

for example 0.99.” (https://learn.microsoft.com/dynamics365/sales-enterprise/create-price-lists)

2. Microsoft Learn: “Price list item fields reference”

field Rounding Amount – “Monetary value used to round the calculated price.” (Docs locale en-us

Dynamics 365 Sales schema; see Field descriptions paragraph).

3. Microsoft Press

Exam Ref MB-210 Microsoft Dynamics 365 Sales

2nd ed.

Ch. 2 “Manage Price Lists”

p. 79: “Setting Rounding Amount to .95 or .98 forces every final price to end with that value.”

To configure a predictive lead scoring model in Dynamics 365 Sales, a minimum data threshold must be met. The system requires at least 40 leads that were qualified and 40 leads that were disqualified within the selected training timeframe (e.g., the last year). The question implies the current number of records is insufficient. The only symmetrical option that allows the system to reach this minimum threshold is to add 20 qualified and 20 disqualified leads, which assumes a starting point of 20 of each. This satisfies the prerequisite of 40 qualified and 40 disqualified leads.

A. The model requires leads with a final status (qualified or disqualified) for training, not just a count of created leads.

C. Adding only 10 qualified leads would be insufficient unless the organization already had exactly 30, which is an arbitrary and unstated assumption.

E. Adding 30 disqualified leads would be insufficient unless the organization already had exactly 10, which is an arbitrary and unstated assumption.

1. Microsoft Learn. (2024). Prerequisites to configure predictive lead scoring. Dynamics 365 Sales documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/sales/prerequisites-configure-predictive-lead-scoring.

Reference Point: Under the "Prerequisites" section

the document states

"You must have a minimum of 40 qualified and 40 disqualified leads that were created in the time period you select for Train with leads from the past."

The seller's objective is to use insights to "move the deal forward." The Copilot feature for summarizing an opportunity in Dynamics 365 Sales is designed specifically for this. It analyzes the opportunity's data, including recent activities and notes, and generates a concise summary. A key component of this summary is a list of "suggested actions" or "recommended actions." These are actionable steps, such as scheduling a follow-up meeting or sending specific information, that directly help the seller decide how to proceed and advance the opportunity toward closure. This aligns perfectly with the seller's stated goal.

A. Financial health: This information is typically generated by the "Research an account" feature, not the summary of a specific opportunity. It provides context but not a direct next step for the deal.

C. Budget, Authority, Need, and Timeline-based qualifications: Copilot can help surface information related to BANT from communications, but it does not generate a formal BANT qualification as a primary output of its summary or research functions.

D. Blueprints: This is a generic term and not a recognized output or feature of the Sales Copilot in Dynamics 365 Sales.

1. Microsoft Learn. "Get up to speed on your records with Copilot in Dynamics 365 Sales." This document explicitly states that the summary for records like opportunities includes "suggested actions."

Reference: Under the "Get a summary of a lead or opportunity" section

the documentation lists the components of the summary

which includes "suggested actions."

2. Microsoft Learn. "Copilot in Dynamics 365 Sales overview." This document highlights that a primary benefit of Copilot is to provide sellers with AI-powered insights and recommendations to help them be more productive.

Reference: The overview section emphasizes features like "Get a summary of your sales records" which helps sellers "plan your next move."

3. Microsoft Learn. "Research an account with Copilot in Dynamics 365 Sales." This document details the outputs of the account research feature

which include "Latest news

" "Market trends

" and "Recent financial reports

" confirming that "Financial health" (Option A) is tied to account research

not opportunity summarization.

Reference: The introductory paragraph lists the specific types of information provided in an account research summary.

Mountaineer range $\rightarrow$ Product family

The "Mountaineer range" is a categorization/grouping of products (which includes "economy" and "premium" fittings as child products). In Dynamics 365 Sales, a Product Family is used to group similar products together and allows child products to inherit properties (such as the metal range options) defined at the family level.

Athlete package $\rightarrow$ Product bundle

The "Athlete package" is described as a package that "includes a cycle, connected devices, and subscription-based analytics services." In Dynamics 365, a Product Bundle allows you to combine multiple individual products (the cycle, physical devices, and services) into a single package so that they can be sold together easily.

Metal range $\rightarrow$ Product property

The requirement states that when creating opportunities, "sellers should be able to select a metal type when adding a mountaineer cycle to an opportunity. The metal types include chrome, aluminum, and titanium." This is a classic use case for a Product Property (such as metal type) configured with option set values. When the property is defined at the product family level, it is inherited by the child products under the Mountaineer range, allowing sellers to specify the variant (e.g., chrome, aluminum, or titanium) at the opportunity line item level.

Microsoft Dynamics 365 Sales Official Documentation:

Section: "Create a product family" (Configuring hierarchical relationships and classifying product classifications).

Section: "Create product bundles to sell multiple items together" (Bundling physical goods and digital subscription services).

Section: "Use properties to describe a product" (Configuring properties/attributes such as colors, materials, or metal types to be defined on product families and configured at the opportunity/quote level).

Opportunity updated today is NOT included in the chart: By default, goal metrics are rolled up automatically every 24 hours. If a salesperson needs to see data updated on the same day immediately or adjust how data aggregates, an administrator or privileged user needs to modify the roll-up settings (such as recurring job frequency) or manually trigger a recalculation via the roll-up job properties.

Time period for the goal is inaccurate: Salespeople have read-only access to their assigned targets and goals but lack the security privileges to modify foundational configurations like start and end dates. To adjust an inaccurate goal time period, the sales manager (who typically owns or inherits write permissions on child goals) or a system administrator must update the goal record.

Microsoft Learn / Dynamics 365 Sales: Create or edit a goal roll-up query & Configure goal metrics and roll-up fields.

Microsoft Power Platform Dataverse Documentation: Goal Management Security Roles and Privileges (specifying that individual contributors cannot change administrative parameters like target periods on locked/active goals without manager or admin security tier clearance).

Define measurable sales target: A Goal metric is used in Dynamics 365 Sales to define how a goal is measured (e.g., by Amount or Count). It acts as the fundamental template specifying the measurement type for any sales target.

Aggregate opportunity revenue: Rollup columns (historically referred to as rollup fields) are configured within a Goal Metric to define how data from underlying records—such as estimated or actual revenue from opportunities—is aggregated and tracked against the target.

Microsoft Learn / Dynamics 365 Sales Documentation: Create or edit goal metrics — Section: "Define a goal metric" & "Create rollup columns".

Microsoft Learn / Dataverse Documentation: Work with goals in Dynamics 365 Sales — Section: "Goal metrics and rollup fields".

Power Automate automated cloud flows are designed to execute automatically when a specific event occurs, such as a record being created (new high-value opportunity) or modified (opportunity marked as won). Power Automate scheduled cloud flows execute based on a predefined time cadence, making them the correct choice for repetitive temporal tasks like a weekly Sunday validation. Business process flows provide a visual, guided user interface within model-driven apps (like Dynamics 365 Sales forms) to enforce standardized steps and guide users through business phases, such as lead qualification.

Microsoft Learn: Business process flows overview

Section: What are business process flows?

Detail: Confirms they provide a visual guide for users to ensure data consistency and follow steps to a conclusion (e.g., Lead to Opportunity sales process).

Link: https://learn.microsoft.com/en-us/power-automate/business-process-flows-overview

Microsoft Learn: Create a cloud flow in Power Automate

Section: Automated cloud flows.

Detail: Specifies that these flows perform tasks automatically after an event triggers them, such as an item being created or changed in a data source like Dataverse.

Link: https://learn.microsoft.com/en-us/power-automate/get-started-logic-flow

Microsoft Learn: Run flows on a schedule

Section: Create a scheduled cloud flow.

Detail: Outlines the configuration for triggering actions at specific times, such as daily or weekly routines.

Link: https://learn.microsoft.com/en-us/power-automate/run-scheduled-tasks

The Sales Close Agent utilizes distinct operational modes to assist sellers efficiently. Research mode is specifically engineered to aggregate and synthesize disparate data (CRM records, emails, meetings, and web activity) into a cohesive, unified deal view, providing the seller with situational awareness. Engage mode handles actionable and interactive elements. It actively monitors for stalled progress to recommend targeted follow-up actions for disengaged deals. Furthermore, because Engage mode governs the generation of customer-facing content and interactions, it enforces organizational guardrails to ensure all communications remain strictly compliant with company policies.

Microsoft Dynamics 365 Documentation: "Configure and manage autonomous agents in Dynamics 365 Sales." Microsoft Learn. (Provides architectural overviews of agent modes, specifying how Research modes synthesize data while Engage modes handle recommendations and compliance guardrails during the closing phase).

Microsoft Power Platform Documentation: "Copilot and autonomous agents: Governance and Compliance." Microsoft Learn. (Details the enforcement of company policies and interaction guardrails within the Engage mode of Copilot agents).

Microsoft Mechanics / Tech Community: "Evaluating Sales Copilot and Agent Capabilities for Deal Acceleration." (Discusses the practical application of dividing agent workloads into insights generation (Research) and action prompting (Engage) for disengaged pipeline opportunities).

In Dynamics 365 Sales, pricing components are configured to serve specific functional roles:

• Price list item: This component is required to define the actual base price, pricing method, and rounding policy for an individual product or service.
• Territory: Dynamics 365 features an in-built rule that automatically sets a default localized price list on an opportunity, quote, order, or invoice based on the sales territory assigned to the user.
• Price list: A price list acts as a structural container to group product prices. Organizations create distinct price lists to maintain separate pricing structures tailored to different regions, currencies, or customer segments.

Microsoft Learn: Create price lists and price list items to define pricing of products. Specifies that "Price list items define the base price for a product" and that multiple price lists are used to "maintain separate price structures for different regions."

Source: https://learn.microsoft.com/en-us/dynamics365/sales/create-price-lists-and-price-list-items-to-define-pricing-of-products

Microsoft Learn: Set default price level for opportunity, quote, order, and invoice. Details the configuration required to "automatically set a default price level (price list)... based on the sales territory of the user."

Source: https://learn.microsoft.com/en-us/dynamics365/sales/developer/set-default-price-level-for-opportunity-quote-order-invoice