Practice Free AB-210 Exam Online Questions

Explanation:

Requirement Configuration

Enable AI features in the environment Deploy Copilot in Dynamics 365 Sales

Allow administrators to create agents Assign Copilot Studio author role

Allow sellers to use AI insights Assign Dynamics 365 Sales security roles

Allow agents to analyze sales records Configure Dataverse security permissions

The environment-level AI prerequisite is to deploy Copilot in Dynamics 365 Sales. Microsoft states that Copilot features must be turned on for Dynamics 365 Sales and that enabling Copilot activates the embedded chat and Copilot experiences in sales apps. Microsoft also identifies AI Agents and AI insight cards as environment capabilities required for Sales agents.

Administrators who design or create agents need Copilot Studio author capability. Microsoft’s Copilot Studio licensing guidance specifically lists the Copilot Studio authors role as a supported access configuration and explains that this role is assigned through the Power Platform admin center.

Sellers must receive appropriate Dynamics 365 Sales security roles because Sales agent access is role-driven. Microsoft states that users must be assigned Sales Manager or Salesperson roles to use Sales agent capabilities in Dynamics 365 Sales.

Finally, agents can only analyze sales records when Dataverse access is correctly configured. Dataverse security roles define table privileges such as Read, Create, Write, Delete, Append, and Append To, so sales data access must be governed through Dataverse security permissions.

References/topics: Copilot in Dynamics 365 Sales; Sales agents prerequisites; Copilot Studio author role; Dynamics 365 Sales security roles; Dataverse security permissions.

Explanation:

Requirement Component

Record engagement is pending, completed, or failed Sales Agent Runs table view

Weekly performance view of the Sales Close Agent in

Research mode

Insights and metrics for the Sales Close

Agent

For a specific opportunity that stopped receiving automated outreach, use the Sales Agent Runs table view. Microsoft states that to resolve the engagement status of a specific record, administrators can go to the sales agent run record view and filter the Regarding column by the record of interest. The Status field shows whether the engagement is Active, Failure, or Completed; Active means pending, Failure means the engagement failed, and Completed means it finished successfully.

For the manager’s weekly performance requirement, use Insights and metrics for the Sales Close Agent. That is the performance reporting surface for the agent, not the per-record run table. The requirement specifically mentions a weekly performance view plus Last refreshed and a time period filter, which maps to the agent’s insights dashboard/metrics area. The Sales Agent Runs view is operational monitoring for individual records, while the insights and metrics view is for aggregate performance analysis such as engagement outcomes, response rates, and trend monitoring. Do not select Engage settings because settings configure how the agent behaves; they do not provide performance metrics. Opportunity pipeline view helps sellers manage opportunities, but it is not the agent performance monitoring dashboard.

References/topics: Sales Close Agent monitoring; Sales Agent Runs table; engagement status; Sales Close Agent insights and metrics; Research mode performance reporting.

Explanation:

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.

Explanation:

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.

Explanation:

Requirement Configuration

Filter leads for assignment

Create a segment to filter the lead source. Add country/region as

an additional condition.

Assign the country/region to the

correct group

Assign the country/region to sellers with matching attributes.

Distribute leads to salespeople Use load balancing.

The clean configuration is to create one reusable segment for webform leads, then add the varying country/region condition inside each country-specific assignment rule. Dynamics 365 Sales assignment rules are built by selecting the eligible segment first, then adding rule conditions to further filter records. Microsoft also recommends splitting conditions between segments and assignment rules to keep rules simpler and more efficient.

For routing to the correct sellers, use sellers with matching attributes. The scenario says salespeople manage leads by country/region and that a country/region attribute has been created. Assignment rules support assigning records to sellers who satisfy matching seller attributes or existing seller record fields, which avoids hardcoding individual sellers and is much easier to maintain as sellers change regions.

For distribution, use load balancing because the requirement is capacity-based: no seller should exceed 20 open leads. Dynamics 365 Sales load balancing distributes records based on seller workload/capacity, and seller capacity is calculated by subtracting active assigned records from the maximum configured capacity. Round robin is weaker here because it primarily considers assignment order, not workload.

References/topics: Sales accelerator work assignment; segments; lead assignment rules; seller attributes; seller capacity; load balancing.

Explanation:

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.

Explanation:

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.

Explanation:

Requirement

Configuration or action

Make a product available for selling

Publish product

Organize related products so they inherit shared attributes

Product family

Create a combined offering of several products

Bundle

The correct action to make a product available for selling is Publish product. In Dynamics 365 Sales, products, families, and bundles are typically created or revised before being published. Microsoft states that publishing makes products available for selling, and sellers can choose only published products and bundles when creating sales records such as opportunities and quotes.

To organize related products so they inherit shared attributes, use a Product family. Product families provide the hierarchy used to classify and manage similar products. Microsoft’s product catalog documentation explains that a product family can contain child product families, products, and bundles in a hierarchy, and the parent family is used to structure related catalog items.

To sell coffee machines, filters, and grinders together, configure a Bundle. A bundle is the correct component when several products are sold together as one combined offering. Microsoft’s product catalog guidance distinguishes bundles from product families: families organize related catalog items, while bundles package multiple sellable products together. Currency is not used here because it supports pricing localization and monetary values, not catalog structure, publication, or combined product offerings.

References/topics: Product catalog lifecycle; publish product; product families; product bundles; Dynamics 365 Sales product catalog configuration.