AB-210 Questions and Answers

Requirement

Configuration

Blueprints

Name the blueprint workspace and pin the workspace.

Questions

Create a business function with seeded prompts.

For Blueprints, the correct configuration is to name the blueprint workspace and pin the workspace. The requirement is not asking to regenerate analysis; it asks for a reliable way to return to frequently used research output. In Sales Research Agent, a generated blueprint exists inside a workspace, and Microsoft states that the workspace displays the workspace name, can be renamed, and can be switched from the workspace menu. That makes naming and pinning the workspace the correct operational pattern for reusable research access.

For Questions, the correct configuration is to create a business function with seeded prompts. Sales Research Agent business functions are designed to tailor research to a specific use case, and administrators can add starter prompts. Microsoft explains that starter prompts appear on the Sales Research Agent home page for quick access and that the full prompt is sent to the agent when selected. This directly satisfies the requirement to retain a reusable library of approved questions.

Do not select regenerate the blueprint because regeneration refreshes or recreates analysis, but it does not create a persistent shortcut to frequently used research. Do not select custom table or manual prompt questions in Sales Copilot because the native Sales Research Agent feature already supports reusable business-function prompts.

References/topics: Sales Research Agent; research blueprints; workspace management; business functions; seeded/starter prompts; intelligent opportunity research.

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.

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.

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.

Requirement

Configuration

Define shared properties for several drone models

Product family

Combine drones and accessories into a package

Bundle

Represent a single drone model

Product

The correct configuration is based on the product catalog hierarchy in Dynamics 365 Sales. A Product family is used when several related products need to share common characteristics or inherited properties. For example, a drone product family can define shared attributes such as flight time, camera type, battery compatibility, or warranty tier, and individual drone models can inherit or specialize those attributes. This is exactly what the requirement means by defining shared properties for several drone models.

A Bundle is used when multiple sellable products are combined into one package. If the company wants to sell a drone together with spare batteries, propellers, carrying cases, or accessories, that package should be configured as a bundle. The seller can then add the bundle to an opportunity, quote, order, or invoice instead of manually selecting each component.

A Product represents a single sellable item, such as one specific drone model. Price list is not correct for any of these requirements because price lists define pricing structures and currencies; they do not define catalog hierarchy, shared product properties, or bundled offerings.

References/topics: Dynamics 365 Sales product catalog; product families; product bundles; products; product hierarchy and catalog configuration.

The correct action is to select a valid price list on the opportunity and verify that the product has a matching price list item for the selected unit. Dynamics 365 Sales calculates Price Per Unit from the price list item when an existing catalog product is added to an opportunity, quote, order, or invoice. Microsoft states that if an existing product is associated with a price list, the price per unit is calculated from the related price list item; otherwise, it is set to 0 .

The failure pattern described in the question is classic missing or mismatched price-list setup. Price calculation will not occur when no price list is selected, when the selected price list does not contain the product, or when the required price list item is missing. Microsoft also notes that price lists tie the product, unit, and pricing details together. Option A is incomplete because matching currency alone does not create the product/unit price list item. Option B is wrong because User Provided revenue bypasses system calculation. Option D handles discounts only; it does not fix a zero base unit price.

References/topics: Opportunity products; price lists; price list items; Price Per Unit calculation; system-calculated opportunity revenue.

The correct answer is D. Opportunities that use the expired price list can continue through their lifecycle. In Dynamics 365 Sales, a price list can include a Start Date and End Date to define the effective period for that price list, such as a promotional pricing period. Microsoft’s pricing guidance explains that price lists and price list items define pricing for products, and that price calculation applies across opportunity, quote, order, and invoice records.

The expiration date controls the effective availability of the price list going forward; it does not automatically invalidate existing opportunity records that already reference that price list. This distinction matters operationally: if an opportunity was already created with a valid price list, the sales process can continue without forcing users to replace pricing midstream. That preserves pricing consistency across the opportunity lifecycle and prevents disruption to quotes, orders, and downstream sales documents.

Option A is too strong because Dynamics 365 does not require replacement of prices simply because the referenced price list later expires. Option B incorrectly limits use based on the creation date of the opportunity. Option C is not the best answer because the key supported behavior is continuation of existing opportunities, not adding expired price lists to new opportunities with a warning.

References/topics: Price lists; price list start and end dates; opportunity pricing; product catalog pricing; opportunity lifecycle management.

The solution does not meet the goal. The requirement is explicit: AI billing must use pre-paid credits . Microsoft’s Dynamics 365 Sales billing guidance separates Copilot and agent billing into two models: prepaid capacity and pay-as-you-go . Prepaid capacity uses Copilot Studio message pack subscriptions that are purchased in advance, while pay-as-you-go bills for the actual number of messages consumed during the month.

Configuring capacity overages to a billing plan is not the prepaid-credit model. Overages are tied to consumption beyond allocated capacity and are handled through billing-plan/pay-as-you-go behavior. That conflicts with the requirement to use pre-purchased credits. For prepaid billing, the correct approach is to purchase Copilot Studio message packs or capacity packs and assign that prepaid capacity to the Dynamics 365/Power Platform environment. Microsoft’s Power Platform capacity guidance states that prepaid capacity can be assigned to environments, and when prepaid capacity is exhausted, administrators must reallocate capacity, purchase more credits, or enable pay-as-you-go billing.

Therefore, configuring overages may support monthly usage billing, but it does not satisfy the stated requirement that billing must use prepaid credits.

References/topics: Dynamics 365 Sales consumption-based billing; prepaid capacity; Copilot Studio message packs; Copilot credit capacity; pay-as-you-go overage handling.

Requirement

Automation type

Notify a manager when a high-value opportunity is created

Power Automate automated cloud flow

Validate the products with an external ERP system every Sunday

Power Automate scheduled cloud flow

Display a guided lead qualification interface on the lead form

Business process flow

Update an external ERP system when an opportunity is won

Power Automate automated cloud flow

A Power Automate automated cloud flow is the correct automation type when work must run automatically after a business event occurs. Microsoft describes cloud flows as flows that can perform actions automatically after an event triggers them, such as sending a notification after a triggering event occurs. Therefore, notifying a manager when a high-value opportunity is created and updating an external ERP system when an opportunity is won are both event-driven scenarios, so they should use automated cloud flows with Dataverse triggers.

A Power Automate scheduled cloud flow is correct for validating products with an external ERP system every Sunday. Microsoft states that a scheduled cloud flow runs at a specific time or recurring schedule, such as daily or weekly, and uses a recurrence trigger. That directly matches the weekly Sunday validation requirement.

A Business process flow is correct for displaying a guided lead qualification interface on the lead form. Business process flows provide a streamlined user experience that guides users through defined processes, and Dynamics 365 Sales documentation explains that stages and steps display in a control at the top of a form. Instant cloud flow is not used because none of the requirements ask for a manually triggered user action.

References/topics: Power Automate automated cloud flows; scheduled cloud flows; Dataverse triggers; Business process flows; Dynamics 365 Sales automation and extensibility.