AB-210 Sample Questions Answers

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

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 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.

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 feature is Cloud flow . Dynamics 365 Sales mobile app push notifications are created through Power Automate by using the Send push notification V2 action. Microsoft’s Sales mobile documentation states that the Dynamics 365 Sales mobile app supports push notifications created with the Send push notification V2 action, where the mobile app is set to Sales , the target app is selected, recipients are defined, and the notification can open a specific table record when selected.

Power Automate documentation also describes the creation process as a notification from a flow : go to Power Automate, create an automated flow, choose a trigger such as Microsoft Dataverse, then add the Send push notification V2 action. That matches the requirement to configure several seller notifications for the Sales mobile app. Classic flow is not the correct answer because modern mobile notification automation should be implemented with Power Automate cloud flows, not legacy/classic workflow patterns. Plug-in is also wrong because plug-ins are server-side Dataverse extensions for custom business logic; they are not the standard no-code configuration mechanism for mobile push notifications.

References/topics: Dynamics 365 Sales mobile app; custom push notifications; Power Automate cloud flows; Send push notification V2; Dataverse-triggered seller automation.

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.

Yes, the solution meets the goal. The requirement is very specific: sales managers need deal insights , but the organization must avoid automatic outreach to buyers . Sales Close Agent in Research mode is the correct configuration because it focuses on researching opportunities, analyzing deal context, identifying risks and signals, and providing recommendations to sellers without autonomously engaging customers.

Research mode is intended to help sellers understand an opportunity more quickly by surfacing insights such as deal health, signals, risks, and suggested next actions. It supports opportunity management by giving the team intelligence that can help progress deals, while leaving communication decisions in the hands of the seller. That directly aligns with the stated requirement for insights about deals.

The critical distinction is that Engage mode is the mode that performs automated outreach and customer interaction. Since the company explicitly does not want automatic outreach to buyers, Engage mode would violate the requirement. By configuring the Sales Close Agent in Research mode , the company gets AI-assisted opportunity analysis without autonomous communications.

References/topics: Sales Close Agent; Research mode; opportunity insights; deal analysis; recommended next actions; distinction between Research mode and Engage mode.

Parameter

Option

Entity

Opportunity

Date field

Actual Close Date

Revenue field

Actual Revenue

The correct table is Opportunity because the goal measurement is based on deal amounts when opportunities are closed. In Dynamics 365 Sales goal metrics, rollup fields define which table and source attribute are used to calculate actual or in-progress goal values. Microsoft’s goal metric documentation gives the direct example of using the Opportunity table with the opportunity actual value/source attribute to track actual money amounts from opportunities closed as Won .

The correct date field is Actual Close Date because the goal period must be determined by when the deal was actually closed, not when the opportunity was created. Microsoft’s goal metric configuration guidance states that the Date Field determines the goal period that records roll up into, and gives Actual Close Date as the relevant example.

The correct revenue field is Actual Revenue because the requirement is based on the total deal amount upon closing the opportunity. Budget Amount and Total Amount do not represent the final closed deal value for goal actuals. Goal rollup fields calculate actual performance values for completed measurable results, which fits closed opportunity revenue.

References/topics: Dynamics 365 Sales goals; goal metrics; rollup fields; opportunity actual revenue; actual close date; sales performance tracking.

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.