Pass the Microsoft Microsoft Certified: Dynamics 365 Sales AI Consultant Associate AB-210 Questions and answers with CertsForce

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.

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.

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

The correct behavior is that the Sales Close Agent retries up to three times within the next hour , using an exponential backoff strategy. If those immediate attempts fail, the system continues retrying the engagement over the next three days . If the engagement still fails after that retry window, the record is marked as a failure . Microsoft’s Sales Close Agent documentation explicitly describes this retry pattern for engagement errors and also identifies the possible run statuses as Active, Failure, and Completed.

Option A is wrong because the agent does not retry only once after 24 hours, and failed records are not marked Completed. Option B is wrong because the agent has a defined automatic retry cycle before failure status is finalized. Option C is also wrong because the retry behavior is bounded; it does not retry indefinitely every few minutes. The failure handling is controlled, time-limited, and designed to avoid uncontrolled AI-credit consumption while still giving transient failures a chance to recover. This matters for sales managers because failed engagements must be monitored and remediated through the Sales Agent Runs view rather than assuming every selected record was successfully progressed.

References/topics: Sales Close Agent; engagement processing; retry behavior; Sales Agent Runs monitoring; opportunity/deal progression.

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.

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.

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