AB-210 Microsoft Accelerating Sales Pipelines with AI in Dynamics 365 Free Practice Exam Questions (2026 Updated)

Requirement

Configuration

Advance the lead to the Development stage

Set the decision maker field as required.

Ensure that the default process is applied

Authorize the process for field sellers.

The lead qualification process should be controlled through the Lead to Opportunity Business Process Flow, because the case study states that field sellers use this existing process to manage leads. To prevent a lead from advancing to the Development stage until a decision maker is confirmed, configure the Decision Maker step as required in the business process flow. Microsoft’s business process flow guidance states that each stage contains steps mapped to columns, and a step can be made required so users must enter data before moving to the next stage. This stage-gating behavior directly satisfies the requirement that leads cannot progress until the decision maker is confirmed.

To ensure the correct process is applied for field sellers, authorize the business process flow for the field seller security role. Microsoft explains that business process flows can be associated with security roles so only users with those roles can view or use them, and that the first active process available for a user’s security role is applied by default according to process order.

Do not choose Power Automate to advance the lead; the requirement is to block advancement until a required qualification criterion is completed, not to automate progression. “Switch to a different process” is user action, not a configuration standard.

References/topics: Business process flows; stage-gating; Lead to Opportunity Sales Process; security role authorization; seller workflow standardization.

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

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.

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

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.

The correct outcome is that the agent disqualifies the lead, notifies the supervisor, and the lead continues to be assigned to the agent . In Research-only mode, the Sales Qualification Agent evaluates whether the lead fits the target customer profile. Microsoft states that when target customer profile suitability is high or medium , the lead is handed over to a seller according to the configured assignment rule. When target customer profile suitability is low , the agent disqualifies the lead, notifies the supervisor, and the lead remains assigned to the agent.

Option A is wrong because Research-only mode does not always transfer every lead to a seller; low-fit leads can be disqualified. Option C describes Research and engage behavior, where the agent sends outreach, manages responses, and hands over leads when positive intent is detected. Research-only mode generates outreach drafts but does not send outreach emails or engage with leads. Option D is also wrong because BANT criteria are only used by Research and engage mode, not Research-only mode. Therefore, a low target customer profile suitability result in Research-only mode results in agent disqualification and supervisor notification.

References/topics: Sales Qualification Agent; Research-only mode; target customer profile suitability; lead disqualification; supervisor notification; lead handoff rules.

No, the solution does not meet the goal. The requirement clearly states that sales managers need insights about deals , but the system must not perform automatic outreach to buyers . Sales Close Agent Engage mode is designed for autonomous customer engagement. It can interact with buyers, send outreach or follow-up communications, and help progress sales conversations automatically. That violates the restriction in the question.

For this scenario, the appropriate configuration is Sales Close Agent in Research mode , not Engage mode. Research mode supports opportunity management by analyzing deal context, surfacing risks, identifying signals, and providing recommended next actions to sellers. It gives managers and sellers AI-generated deal insights while keeping buyer communication under human control. That is exactly what the company requires.

Engage mode would only be acceptable if the company wanted the agent to actively contact buyers or automate customer-facing communication. Since the requirement explicitly prohibits automatic outreach, Engage mode fails the stated goal.

References/topics: Sales Close Agent; Research mode versus Engage mode; opportunity insights; deal risk analysis; AI-assisted opportunity management without autonomous outreach.

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.

The administrator must have both the correct license and an environment that supports Dynamics 365 apps . Microsoft states that when creating a production or sandbox Power Platform environment with a Dataverse database, administrators can add Dynamics 365 apps such as Dynamics 365 Sales, but they must select Enable Dynamics 365 apps during database provisioning. Microsoft also states that a valid Dynamics 365 license is required to enable Dynamics 365 apps.

Therefore, the administrator must be assigned a Dynamics 365 Sales Enterprise license , and the environment must have Dataverse added with Dynamics 365 apps enabled . After the Sales license is available, Dynamics 365 Sales apps such as Sales Hub can be installed from the Power Platform admin center under the environment’s Dynamics 365 apps resources.

Option A is wrong because server-side synchronization is used for Exchange email, appointments, contacts, and tasks integration; it is not required to deploy Sales Hub. Option D is not required because a sandbox environment can support Dynamics 365 apps when Dataverse and Dynamics 365 apps are enabled. Option E is unnecessary unless the administrator is excluded from the security group; the scenario already states the administrator has the System Administrator role.

References/topics: Power Platform environment provisioning; Dataverse database; Enable Dynamics 365 apps; Dynamics 365 Sales licensing; Sales Hub deployment.

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.

The correct scenarios are B and C . Sales Research Agent is designed for research and analysis, not autonomous record updates or email engagement. Microsoft describes the agent as an AI-powered research canvas that lets users solve complex business questions through natural language, generate research blueprints, review sales-data insights, and ask follow-up questions to refine the analysis. It can use Dynamics 365 Sales data, uploaded offline files such as CSV, Excel, or PDF, and connected data sources to support pipeline exploration and sales operations analysis.

Option B is correct because Microsoft states that Sales Research Agent may use Bing Search only when the Bing search consent setting is enabled. When Bing search is disabled, the agent operates only on internal data sources that the user already has permission to access. Option C is also correct because the agent generates a research blueprint with visualizations and a text overview, and users can continue iterating by asking follow-up questions or changing visualizations on the canvas. Option A is wrong because Sales Research Agent is analytical; it does not update opportunities with risk or importance values. Option D is wrong because automatic email engagement is the domain of sales/qualification engagement agents, not Sales Research Agent.

References/topics: Sales Research Agent; research canvas; AI-generated blueprints; Bing search consent; internal sales data analysis; intelligent opportunity research.