Free AB-210 Practice Test Questions and Answers (2026)

The Copilot summary feature in Dynamics 365 Sales generates a concise overview of records, including recent activities and historical changes. To provide this context, Copilot relies on the audit history of the Account, Lead, and Opportunity tables. If auditing is not enabled for these tables, Copilot cannot access the data logs of field changes and other historical events, resulting in a summary that lacks key business context and history. Enabling auditing for these specific tables allows Copilot to synthesize a complete and informative summary for sellers.

A. Enable AI insight cards in the Power Platform environment.

Insight cards are a separate Sales Insights feature that provides proactive, actionable suggestions. They do not serve as the data source for the generative Copilot record summary.

B. Configure predictive scoring.

Predictive scoring models generate a numerical score to rank leads or opportunities. While this score can be a data point, it does not provide the detailed historical narrative that auditing does.

D. Configure the opportunity pipeline view settings.

The pipeline view is a specific user interface for managing multiple opportunities. Its settings control visualization and do not impact the underlying data available to Copilot for individual record summaries.

1. Microsoft Learn | Dynamics 365 Sales Documentation. "Enable and configure Copilot in Dynamics 365 Sales." Under the section "Prerequisites

" the documentation explicitly states: "To get summaries for leads

opportunities

and accounts

the audit history for these tables must be turned on. If you see a message that audit history isn't turned on when you open a record

you or your administrator must turn it on."

2. Microsoft Learn | Dynamics 365 Sales Documentation. "Understand the Copilot summary page." This document details the functionality of the summary feature and implicitly relies on the availability of historical data

which is captured through auditing. The section "What's new with my sales records" is directly powered by audit logs.

In Dynamics 365 Sales, when a price list is associated with an opportunity, the pricing context for that deal is established. If the price list subsequently expires (its end date passes), it does not affect opportunities that are already using it. These existing opportunities can proceed through their entire sales lifecycle, including conversion to a quote, order, and invoice, using the prices from the now-expired list. The expiration's primary function is to prevent the price list from being selected for any new opportunities or other transaction records created after the expiration date.

A. The system does not display a warning on existing opportunities to replace prices. The price list remains valid for the context of that specific, in-progress opportunity.

B. An expired price list cannot be selected and added to any opportunity, new or old. The expiration date makes it unavailable in the price list lookup view.

C. Users are blocked from adding an expired price list to an opportunity. The system does not permit the action with a warning; it prevents the selection entirely.

1. Microsoft Learn | Dynamics 365 Sales Documentation: Create or edit a price list (Sales Hub). This document describes the StartDate and EndDate fields for a price list. It states

"Select the dates that the price list is valid for." This implies that outside of this date range

the price list is not valid for selection on new records

but it does not state that it invalidates existing transactions that are already using it. The system's behavior is to honor the price list that was valid at the time of its association with the opportunity.

2. Microsoft Learn | Dynamics 365 Sales Documentation: Add products to an opportunity. This guide explains the process of adding products

which requires selecting a price list first. The lookup for available price lists filters out those that are not active or are outside their valid date range

preventing the selection of an expired list for any opportunity. This confirms that options B and C are incorrect as the system prevents this action.

The opportunity summary feature uses generative AI to create a concise overview of an opportunity's status, recent activities, and key details. It synthesizes information from the opportunity record, notes, and timeline activities into a brief paragraph. This allows sellers to quickly grasp the context and history of an opportunity without needing to manually read through multiple entries. Adding this summary to the form directly addresses the goal of reducing the time required for reviewing opportunities before contacting a customer.

B. Up next: This widget displays the next recommended action from a sequence, guiding sellers on what to do next rather than providing a comprehensive summary for review.

C. Health score: This is a single metric that indicates the quality of the customer relationship; it does not provide a detailed summary of the opportunity itself.

D. Predictive opportunity scoring: This feature provides a score indicating the likelihood of an opportunity closing as won, which is used for prioritization, not for summarizing its context.

E. Timeline highlights: This feature flags important activities in the timeline but still requires the seller to read through those individual activities, unlike a consolidated summary.

1. Microsoft Learn. (2024). Get a summary of an opportunity. Dynamics 365 Sales Documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/sales/get-summary-opportunity.

Reference Details: The section "How the opportunity summary helps you" states

"The opportunity summary feature helps you get a quick overview of an opportunity without having to read through all the notes and activities."

2. Microsoft Learn. (2024). What is the sales accelerator?. Dynamics 365 Sales Documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/sales/what-is-sales-accelerator.

Reference Details: The "Up next widget" section describes it as a tool that "helps sellers to view and perform actions on the current activity

the upcoming activity

and the subsequent activities in a sequence."

3. Microsoft Learn. (2024). Predictive opportunity scoring. Dynamics 365 Sales Documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/sales/predictive-opportunity-scoring.

Reference Details: The introduction states

"Predictive opportunity scoring uses a machine learning model to calculate a score for open opportunities... The score helps sellers prioritize opportunities."

4. Microsoft Learn. (2024). Relationship analytics and health. Dynamics 365 Sales Documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/sales/relationship-analytics.

Reference Details: The "Overall relationship health" section explains that the health score is an indicator based on "activities

recency

engagement

and sentiment of the interactions between sellers and customers."

Access to Dynamics 365 Sales, including via the mobile application, is fundamentally governed by two components. First, each user must have an appropriate Dynamics 365 Sales license assigned to their account to be entitled to use the service. Without a license, no access is possible. Second, access to specific data (records) and application features is controlled by security roles. For mobile access, the security role assigned to the user must not only grant privileges to the necessary data entities (like Leads or Opportunities) but also include the specific "Dynamics 365 for Mobile" privilege, which explicitly authorizes the use of the mobile client. If some sellers cannot access records, it indicates a failure in one or both of these foundational access control mechanisms.

A. Configure the mobile offline profile.

This is incorrect because mobile offline profiles enable users to access data without an internet connection. It is a feature configured after a user already has basic online access to the app and its records.

B. Configure inbound and outbound profiles.

This is incorrect as inbound and outbound profiles are typically related to configuring email server settings or other communication channels, not for controlling user access to the core application or its data.

1. Microsoft Learn. (2024). Security roles and privileges. In Dynamics 365 Sales Documentation. "To control access to data

you must set up a security structure that protects sensitive data while allowing for collaboration. [...] For users to be able to access the mobile app

they need a security role with the Dynamics 365 for Mobile privilege."

Reference: https://learn.microsoft.com/en-us/dynamics365/sales/security-roles-privileges (Under the "Required privileges" section).

2. Microsoft Learn. (2024). Assign licenses to users. In Microsoft 365 admin center documentation. "As an admin

you assign licenses to users for the Microsoft products your organization has

such as Microsoft 365

or in this case

Dynamics 365. When you assign a license to a user

they can start using the apps and services that are included with that license."

Reference: https://learn.microsoft.com/en-us/microsoft-365/admin/manage/assign-licenses-to-users (This is a general M365 principle that is the foundation for D365 access).

3. Microsoft Learn. (2024). Set up mobile offline synchronization. In Power Apps model-driven apps documentation. "To set up mobile offline

an admin needs to enable tables for offline

create an offline profile

and add users to the profile." This process assumes users already have licensed and role-based access to the application online.

Reference: https://learn.microsoft.com/en-us/power-apps/mobile/setup-mobile-offline (This reference clarifies the purpose of offline profiles

supporting why option A is incorrect).

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).

Enable AI features in the environment: To activate generative AI features and autonomous capabilities within the sales workflows, you must deploy and enable Copilot in Dynamics 365 Sales at the environment level.

Allow administrators to create agents: Custom AI agents in Microsoft Dynamics 365 are designed, orchestrated, and managed using Microsoft Copilot Studio. To build and manage these conversational or autonomous agents, administrators must be assigned the Copilot Studio author security role.

Allow sellers to use AI insights: To interact with Copilot features and AI-generated insights directly inside the Sales Hub, users must have appropriate Dynamics 365 Sales security roles (such as Salesperson) that include privileges to access Copilot intelligence components.

Allow agents to analyze sales records: Since Dynamics 365 Sales stores its core relational data (leads, opportunities, accounts) inside Microsoft Dataverse, AI agents require appropriate data access rights. Ensuring they can read and evaluate this information requires configuring specific Dataverse security permissions or configuring the dedicated service identity's security roles.

Microsoft Learn: Enable and configure Copilot in Dynamics 365 Sales — Detail on setting up the environment-level Copilot deployment.

Microsoft Learn: Assign roles and security permissions to users in Copilot Studio — Outlines the necessity of the Copilot Studio author role for creating and configuring custom AI agents.

Microsoft Learn: Security roles and privileges in Dataverse — Highlights data access controls required for systems and automated services interacting with platform records.

Perform purchase required by CFO: The CFO requested that Copilot message packs be pre-purchased using the Copilot Studio subscription license. Purchase of licenses, add-ons, and subscriptions within a Microsoft tenant is strictly managed through the Microsoft 365 admin center (under Billing > Purchase services).

Configure Sandbox billing: The technical requirement specifies that AI capacity should be capped in the sandbox environment. Allocating, capping, and managing specific AI Builder or Copilot capacity credits per environment is configured directly within the Power Platform admin center (under Resources > Capacity).

Configure Production billing: Because the scenario explicitly states that "No Azure subscriptions are available in the tenant," pay-as-you-go billing via the Azure portal is not an option. To ensure that AI capacity remains reliably available to production sellers without interruption, additional prepaid capacity/add-on licenses must be allocated and managed via the Microsoft 365 admin center.

Microsoft Learn - Buy or manage add-ons: Details how billing administrators use the Microsoft 365 admin center to purchase add-ons and capacity licenses.

Microsoft Learn - Power Platform Capacity Add-ons: Explains how environment-level capacity allocation, throttling, and capping are configured using the Power Platform admin center.

A Business process flow provides a visual, guided step-by-step track (like the standard Lead to Opportunity Sales Process) to ensure sellers follow consistent methodologies during qualification. The Lead qualification experience settings in the Sales Hub allow administrators to customize what happens upon qualification, such as prompting users to select which records (Account, Contact, Opportunity) are generated, facilitating multiple opportunity creation if configured. The Timeline control natively aggregates and renders activities directly on a record's form, supporting the display of rich-text emails and inline images. Finally, a Power Automate cloud flow acts as the automation engine, capable of triggering an email or Teams notification to supervisors the moment a lead's status transitions to "Qualified."

Business Process Flows:

Microsoft Learn, Dynamics 365 Documentation. Overview of business process flows. Details how BPFs guide users through work processes, specifically highlighting the Lead to Opportunity process.

URL: [learn.microsoft.com/en-us/power-automate/business-process-flows-overview](https://learn.microsoft.com/en-us/power-automate/business-process-flows-overview)

Lead Qualification Experience:

Microsoft Learn, Dynamics 365 Sales Documentation. Customize the lead qualification experience. Outlines how to configure system settings to prompt users to choose which records to create upon lead qualification.

URL: [learn.microsoft.com/en-us/dynamics365/sales/customize-lead-qualification-experience](https://learn.microsoft.com/en-us/dynamics365/sales/customize-lead-qualification-experience)

Timeline Control:

Microsoft Learn, Power Apps Documentation. Set up the timeline control. Explains how the timeline component displays notes, posts, and rich-content emails (including images) on model-driven app forms.

URL: [learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/set-up-timeline-control](https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/set-up-timeline-control)

Power Automate Cloud Flows:

Microsoft Learn, Power Automate Documentation. Trigger flows when a row is added, modified, or deleted. Describes using Dataverse triggers to initiate automated notification workflows upon record state changes.

URL: [learn.microsoft.com/en-us/power-automate/dataverse/create-update-delete-trigger](https://learn.microsoft.com/en-us/power-automate/dataverse/create-update-delete-trigger)

To automate a quote approval process, you must first create a Power Automate cloud flow to serve as the foundation of your automation. Next, you need an event-driven mechanism to initiate the flow; since Dynamics 365 Sales records are stored in Microsoft Dataverse, you should add a Dataverse trigger (e.g., when a quote record is updated or created). Following the trigger, you must address the core business requirement by adding an action to define an approval step, which routes the quote to the appropriate stakeholders. Finally, to ensure the logic works and to deploy the automation for end users, you must test and activate the flow.

Microsoft Learn: Power Automate Documentation. "Create and test an approval workflow with Power Automate." Section: Create an approval flow. This document outlines the foundational steps of initiating a cloud flow and adding an "Approvals" action.

Microsoft Learn: Power Automate Documentation. "Trigger a cloud flow based on Microsoft Dataverse." Section: Add a trigger. This section details how event-driven automation in Dynamics 365 and Dataverse relies on Dataverse triggers rather than scheduled triggers.

Microsoft Learn: Power Automate Documentation. "Get started with testing flows." Section: Test your flow. Details the final mandatory steps of testing logic and activating/turning on the flow for production use.

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