AB-210 Exam Dumps - Microsoft Certified: Dynamics 365 Sales AI Consultant Associate Questions and Answers

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.

The required fix is about visibility and security , not agent operating mode. In the scenario, production has EnableRoleBasedSystemViews set to true, which restricts system views based on role configuration. Because the business requirement says all sellers should be able to access disqualified leads , the role-based system view setting must be updated so sellers can access the view that exposes leads disqualified by the Sales Qualification Agent.

The second required action is to change Lead table permissions. The customized Salesperson role currently grants sellers read access only to leads they own. That is too restrictive because leads disqualified by the Sales Qualification Agent may not be owned by each seller. To let all sellers view those records, sellers need organization-level Read permission on the Lead table. Option A is wrong because upgrading the agent to research and engage mode affects how the agent researches and interacts with leads; it does not solve seller access to disqualified records. Option C is also wrong because the look-back period controls which historical leads the agent evaluates, not who can view disqualified leads.

References/topics: Sales Qualification Agent; role-based system views; Dataverse security roles; Lead table read access; AI-driven lead qualification.

Requirement

Configuration

Enable guided sales qualifications

Business process flow

Allow sellers to create multiple opportunities when qualifying a lead

Lead qualification experience

Display emails with images

Timeline

Notify supervisors when leads are qualified

Power Automate cloud flow

Guided sales qualification is handled by a Business process flow because BPFs define the sales stages and required steps sellers follow during lead-to-opportunity execution. Microsoft describes lead qualification as the movement of a lead through the sales process into an opportunity, and business process flows are the native model-driven mechanism for guided stage-based work.

Creating multiple opportunities during qualification is controlled by the Lead qualification experience . Microsoft’s lead qualification configuration allows administrators to customize how account, contact, and opportunity records are created when a lead is qualified, including seller-controlled conversion behavior.

Full related emails, including rich email content, belong in the Timeline because the timeline control displays activities related to a record, including emails, appointments, phone calls, notes, and tasks. Microsoft also states the enhanced email experience is available from the Timeline section of customer engagement apps.

Supervisor notification should be implemented with a Power Automate cloud flow . A Dataverse-triggered cloud flow can run when a lead row changes status or when a qualification process creates an opportunity, then notify the supervisor.

References/topics: Business process flows; lead qualification experience; Dynamics 365 Sales timeline; Power Automate Dataverse triggers; lead-to-opportunity qualification automation.

Requirement

Component

Mountaineer range

Product family

Athlete package

Product bundle

Metal range

Product property

The Mountaineer range should be configured as a Product family because it represents a product classification hierarchy. Dynamics 365 Sales uses product families to organize related products, child products, and bundles under a parent structure. Microsoft’s product catalog guidance states that product families can contain child product families, products, and bundles in a hierarchy, which fits the mountaineer cycle range with economy and premium fitting variations.

The Athlete package should be configured as a Product bundle because it combines multiple sellable items: a cycle, connected devices, and subscription-based analytics services. A bundle is used when multiple products are sold together as one commercial package. Dynamics 365 Sales allows products to be associated with a bundle, including quantities and required or optional components.

The Metal range should be configured as a Product property because sellers must choose a configurable attribute—chrome, aluminum, or titanium—when adding the mountaineer cycle to an opportunity. Product properties define product characteristics such as size, color, or component, and can be used at run time when adding products to opportunities, quotes, orders, or invoices.

References/topics: Product catalog setup; product families; product bundles; product properties; opportunity product configuration.

The correct trigger type is Automated . The requirement is event-driven: when a lead is qualified and an opportunity is created or updated, the system must automatically create a follow-up task for the opportunity owner. In Power Automate, this is implemented as an automated cloud flow that starts when a Dataverse event occurs, such as when a row is added, modified, or deleted. Microsoft’s Dataverse trigger documentation states that the When a row is added, modified or deleted trigger runs a flow whenever a selected Dataverse table row is created or changed.

A scheduled trigger is wrong because the requirement is not time-based. Running the process hourly or daily would delay task creation and could miss the intended immediate follow-up behavior. An instant trigger is also wrong because it requires a user to manually start the flow. Microsoft describes instant cloud flows as manually triggered flows, while automated flows run after an event triggers them. For this case, the flow should listen for the qualifying lead or opportunity event in Dataverse, then create the follow-up task and assign it to the opportunity owner.

References/topics: Power Automate automated cloud flows; Dataverse row triggers; lead qualification; opportunity follow-up task automation; Dynamics 365 Sales extensibility.

Requirement

Tool

Perform purchase required by CFO

Microsoft 365 admin center

Configure Sandbox billing

Power Platform admin center

Configure Production billing

Microsoft 365 admin center

Why: Production requires reliable AI capacity so sellers are not blocked when prepaid Copilot capacity is depleted. The correct production setup is pay-as-you-go / billing policy configuration through the Microsoft 365 admin center . Azure portal is not the best answer here because the scenario says no Azure subscriptions are available , and Microsoft 365 admin center can be used for the billing policy workflow. Microsoft Agent 365 is for agent management/governance, not billing configuration.

The correct conclusion is that lead outcomes reflect updated evaluation criteria applied during processing . The Sales Qualification Agent evaluates inbound leads against the configured target customer profile and qualification settings. Microsoft states that the target customer profile suitability is determined by the attributes defined in the agent configuration’s handoff criteria, and the agent categorizes leads as high, moderate, or low fit based on how well the lead matches those attributes.

Therefore, when the sales manager updates the qualification criteria, a shift in categorization is expected. It means the agent is applying the new criteria to processed leads, not that the old evaluations were incomplete or that external factors are necessarily driving the change. The continued processing and absence of evaluation gaps also indicate normal operational continuity. Microsoft’s Sales Qualification Agent setup guidance explains that the agent works on assigned leads based on configured selection criteria and that stopping the agent prevents new lead processing; here, processing continued, so the agent remained active while using the revised configuration. Option A is too speculative: tuning might be useful later, but the evidence given does not prove a tuning problem. The clean interpretation is D .

References/topics: Sales Qualification Agent; target customer profile; qualification criteria; lead categorization; AI-driven lead qualification monitoring.

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.

Requirement

Configuration

Quantities a product can be sold

Unit group

Group product pricing for different currencies

Price list

Sale price of a product

Price list item

The correct configuration uses Unit group , Price list , and Price list item because these are the core Dynamics 365 Sales product catalog pricing components. A Unit group defines the collection of units in which a product can be sold. For example, a product might be sold as each, box, case, or pallet. The unit group provides the available quantity structure, while a primary unit identifies the default or base unit inside that group. Therefore, the requirement to define the quantities in which a product can be sold maps to Unit group , not just Unit or Primary unit.

A Price list is used to group product pricing, and each price list is associated with a currency. For a global company selling in different markets, separate price lists can be maintained for currencies such as USD, EUR, or GBP. The Price list item defines the actual sale price of a specific product within a price list, including the product, unit, currency context, and pricing amount. A discount list only defines discount rules, and a product family organizes products, not pricing.

References/topics: Product catalog configuration; unit groups and units; price lists; price list items; global pricing and currency-based product pricing in Dynamics 365 Sales.

The correct two UI elements are the Select record type dropdown and one of the Customize field dropdowns on the work item card. In Dynamics 365 Sales, a “company” record is represented by the Account table. The screenshot currently shows the selected record type as Contacts , which would expose contact-related fields such as Full Name, Job Title, and Company Name. That is not the correct entity if the requirement is to display the industry of a company. Therefore, the record type must first be changed to Accounts .

After selecting Accounts , modify the card layout by selecting the Industry field in the Customize section. Microsoft’s sales accelerator workspace guidance states that work item appearance can be customized for each record type so sellers see the most relevant information in their work list. The work item appearance page lets administrators choose the record type and configure the fields displayed on the work item card.

Do not modify Lock customization as the answer target. That controls whether users can personalize the layout; it does not select the account entity or display the Industry field.

References/topics: Sales accelerator workspace; work item appearance; account record type; field customization; seller work list configuration.