AB-210 Dumps with Practice Exam Questions Answers

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.

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.

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.

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.