Microsoft AB-210 Accelerating Sales Pipelines with AI in Dynamics 365 Exam Practice Test

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

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.

For Dynamics 365 Sales predictive lead scoring, the model cannot be created unless there is enough historical lead outcome data in the selected training window. Microsoft’s predictive lead scoring configuration requirement states that the organization must have at least 40 qualified leads and 40 disqualified leads in the selected training period. The official guidance specifically explains that if the model is trained with leads from the past three months, the organization needs “at least 40 qualified and 40 disqualified leads” created and closed during that period.

In the sandbox, AdventureWorks has 30 qualified leads and 20 disqualified leads. However, 10 of the qualified leads are older than three months, and the business requirement says predictive scoring must be enabled for leads created within the last three months. Therefore, only 20 qualified leads are usable for this model. The sandbox currently has 20 usable qualified leads and 20 disqualified leads. To meet the required threshold of 40 each, the company needs 20 more qualified leads and 20 more disqualified leads . Simply creating 40 new leads is not enough because predictive scoring requires outcome-classified leads, not merely open or newly created records.

References/topics: Configure predictive lead scoring; lead scoring model training data requirements; AI-driven lead prioritization in Dynamics 365 Sales.

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 configuration is to set related record creation to Seller. The case study states that sales leadership requires flexibility in how leads are converted: inside sales need automatic opportunity creation, but field sellers need the option to manually decide whether an opportunity should be created when a lead is qualified. In the new lead qualification experience, Dynamics 365 Sales lets administrators control whether account, contact, and opportunity records are created automatically during lead qualification or whether sellers are prompted to choose which related records to create. Microsoft’s lead qualification guidance confirms that when automatic creation is not enabled, sellers are prompted to select which records should be created during qualification.

Option B and option E are wrong for field sellers because automatic creation would remove the manual decision point required by the case study. Option C is relevant to guiding sellers through sales stages, but the existing Lead to Opportunity Business Process Flow does not control whether related records are automatically created when a lead is qualified. Option D is unrelated because Copilot summaries help sellers review record information; they do not configure lead conversion behavior. Therefore, the required configuration for field sellers is Seller-controlled related record creation.

References/topics: Lead qualification experience; lead-to-opportunity conversion; related account, contact, and opportunity creation; Dynamics 365 Sales lead management.

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.

The solution does not meet the goal. Creating an Azure subscription is associated with pay-as-you-go billing scenarios, not the required pre-paid credits model. Microsoft’s Dynamics 365 Sales agent billing guidance states that Sales Copilot and agent capabilities support two billing models: prepaid capacity and pay-as-you-go . Prepaid capacity uses Copilot Studio message pack subscriptions purchased in advance, while pay-as-you-go bills for actual message consumption during the month.

Because the requirement explicitly says AI billing must use pre-paid credits , the correct approach is to purchase Copilot Studio message packs or Copilot Credits and assign/manage that capacity for the relevant environment. Power Platform guidance explains that Copilot Studio credits/capacity are managed and monitored through the Power Platform admin center, and if prepaid capacity is exhausted, admins must reallocate capacity, purchase more credits, or enable pay-as-you-go. An Azure subscription may be required for pay-as-you-go cost management, but it does not satisfy a prepaid-credit requirement by itself. Therefore, the proposed solution is incorrect.

References/topics: Dynamics 365 Sales agent billing; prepaid capacity; Copilot Studio message packs; Copilot Credits; pay-as-you-go billing.

The Sales Close Agent in Research mode is the correct fit for assessing opportunity risk and prioritizing opportunities that are gaining traction. Microsoft’s AI agents guidance states that the opportunity-focused sales agent helps sellers close deals faster by autonomously researching opportunities, providing visibility into emerging risks, and highlighting promising opportunities. It is designed to identify high-value and at-risk opportunities so sellers can prioritize their effort and act on critical insights.

The Sales Close Agent in Engage mode is the correct fit for recommending opportunity products to clients automatically. Microsoft describes Sales Close Agent as an autonomous agent for high-velocity sales execution that engages customers, recommends products, handles objections, and drives transactions toward closure using configured product catalog and pricing information.

The Sales Qualification Agent is not appropriate for these scenarios because it is lead-focused, not opportunity-focused. It researches inbound leads, evaluates fit, generates outreach, and can hand promising leads to sellers depending on the configured mode. It does not manage opportunity risk, opportunity traction, or client product recommendations for active deals.

References/topics: Sales Close Agent; opportunity research; opportunity risk; opportunity prioritization; Sales Close Agent Engage mode; product recommendations.

The correct answer is Product families because the requirement is to organize similar products into searchable categories. In Dynamics 365 Sales, product families are used to classify and group related products under a product hierarchy. Microsoft’s product catalog guidance explains that products can be created as standalone products or inside a family depending on how the organization wants to organize and classify them, and the training module specifically describes creating product family hierarchies that include product bundles and individual products.

For the example in the question, “flat screen TV” would be the product family, while individual versions such as 42-inch, 55-inch, OLED, QLED, or 4K models would be products inside that family. This makes browsing and searching easier for sellers because related variants are grouped logically. Product unit groups define how products are sold, such as each, box, or case; they do not categorize products. Related products are used for cross-sell, upsell, substitute, or accessory recommendations, not primary catalog organization. Product bundles combine multiple products sold together as a package. Therefore, the correct catalog structure is Product families .

References/topics: Product catalog setup; product families; product classification; product hierarchy; Dynamics 365 Sales core product configuration.

The three default rule-style suggestions are the Record Owner of the initiating record , the Created By user of the initiating record , and the manager assigned on the seller’s system user record . Suggested contacts in Dynamics 365 Sales Teams chat are intended to help sellers quickly find coworkers who are relevant to the record they are working on. Microsoft states that administrators can enable suggested contacts when a seller starts a new connected chat, and that rules-based contact suggestions can be configured for supported Dynamics 365 record types.

The rule engine supports relational rules: Microsoft explains that a relational rule suggests a user who has a relationship with the linked record type or one of its related records, and administrators can select a user field directly on the record or through related entities. The record owner and created-by user are direct relational users on the initiating record. The seller’s manager is reached through the system user relationship. The business-unit owner is not the default suggestion path for seller collaboration, and “last modified by” or a user who updated a timeline activity are not the default rule answers in this configuration set.

References/topics: Teams chat in Dynamics 365 Sales; suggested contacts; rules-based contact suggestions; relational suggestion rules; sales collaboration.

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 sales lifecycle is Lead → Opportunity → Quote → Order → Invoice . In Dynamics 365 Sales, a lead captures an initial prospect before the person or organization is qualified. Microsoft’s sales process guidance explains that sellers generally work with leads during the qualifying stage, and the goal is to qualify and advance the lead to the next stage of the sales process. Once qualified, the deal becomes an opportunity , which is the record used for pipeline tracking, revenue estimation, sales stages, probability, and forecasting analysis. Microsoft’s prospect-to-quote guidance states that Dynamics 365 Sales supports capturing, managing, scoring, and converting leads into opportunities when qualification criteria are met.

Quotes are then created from opportunities to present pricing proposals to customers. Microsoft states that quotes created from opportunities are prefilled with opportunity details and products. Once the proposal is accepted, the quote can be converted into a sales order for fulfillment and then into an invoice for billing; Microsoft’s quote/order/invoice process sample explicitly demonstrates converting an opportunity to a quote, a quote to a sales order, and a sales order to an invoice. Therefore, option B is the only sequence that correctly supports the full sales lifecycle.

References/topics: Lead management; opportunity pipeline; quote creation; order fulfillment; invoice billing; Dataverse Sales tables.

The correct answer is C . To review the Sales Close Agent behavior for an opportunity, you open an opportunity researched by the agent and select See full research . Microsoft’s current Dynamics 365 Sales documentation describes this flow: sellers open the My top opportunities from AI agent view, open an opportunity, review the summary section, and then select See full research to open the Opportunity research page , which contains the complete research insights and recommendations.

This page is the right place to understand what the agent is surfacing and why it is helping progress deals. The Opportunity research page includes deal importance, deal risks and mitigations, deal overview, key signals, and other research-driven insights. Option A is incomplete and incorrectly starts from Forecast; the documented entry point is the Opportunities area and the AI-agent opportunity view. Option B is not the best answer because Sales Agent Runs is used for operational run records and permissions, not the seller-facing full research output. Option D is fabricated; there is no requirement to configure the opportunity pipeline view to force the full research page into every opportunity side panel.

References/topics: Sales Close Agent Research mode; Sales Opportunity Agent; Opportunity research page; See full research; AI-generated opportunity insights and recommendations.