Free and Premium Microsoft AB-210 Dumps Questions Answers

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.

The correct date field is Actual End because the goal is based on calls that are finished during the calendar year. For the Phone Call table, Microsoft defines Actual End as the actual end date and time of the phone call, which is the proper date to evaluate whether the completed call falls within the January–December goal period.

The correct rollup field is Actual (Integer) because the goal measures the number of outgoing calls, not revenue or another money-based amount. Microsoft’s goal metric guidance explains that goal metrics can use count/integer values, and specifically gives sales calls made by a salesperson as an example of an integer goal metric. The actual integer field represents the achieved count as of the latest rollup calculation.

The correct source record type status is Made because the requirement is for outgoing calls that were completed. Microsoft’s Phone Call status reason options include Open , Made , Canceled , and Received ; “Made” represents completed outgoing phone calls, while “Received” represents completed incoming calls. Therefore, the rollup must count Phone Call records with status Made , using Actual End as the date boundary and Actual (Integer) as the accumulated value.

References/topics: Dynamics 365 Sales goals; goal metrics; rollup fields; phone call activity status; Actual End date; completed outgoing call tracking.

The correct integrations are SharePoint document management and Teams conversation collaboration . SharePoint document management is required because the company wants opportunity files stored in a central location. Microsoft’s Dynamics 365 Sales SharePoint integration is specifically designed to store documents related to Sales records in SharePoint while allowing users to access, share, and manage those documents from the Sales app. Opportunity is one of the standard Sales records supported for SharePoint document integration.

Teams conversation collaboration is required because sellers must collaborate using chat conversations associated with sales records. Microsoft’s Teams chat integration for Dynamics 365 Sales lets sellers start a new Teams chat or connect an existing chat directly to a Sales record, so conversations remain associated with the relevant opportunity, lead, account, or other record.

OneNote integration is for note-taking, not centralized file storage. Conversation intelligence analyzes calls and seller conversations for coaching and insights; it is not the feature for record-linked chat collaboration. Server-side synchronization with Exchange Online supports email, appointments, contacts, and tasks synchronization, but it does not satisfy the SharePoint file storage or Teams chat association requirements.

References/topics: SharePoint document management; Microsoft Teams chat integration; Dynamics 365 Sales collaboration; Sales record document storage.

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.

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

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.

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

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

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.

Requirement

Configuration

Automatically prioritize leads based on conversion probability

Predictive lead scoring

Ensure the lead scoring improvement requirement is met

Automatically retrain model

The correct capability for automatically prioritizing leads based on conversion probability is Predictive lead scoring . Dynamics 365 Sales predictive lead scoring assigns scores to leads so sellers can prioritize the leads most likely to qualify or convert. Microsoft’s Sales documentation states that predictive lead scoring helps sales teams prioritize leads based on scores and improve lead qualification outcomes. This directly matches Contoso’s requirement to guide sellers toward high-potential leads and reduce inconsistent manual prioritization across regions.

To meet the requirement that lead scoring must continuously improve based on historical sales outcomes, configure the model to automatically retrain . Microsoft’s predictive lead scoring guidance explains that retraining uses the latest leads in the organization to improve model accuracy, and automatic retraining allows the application to retrain the model every 15 days. This is the correct option because Contoso wants the scoring model to improve continuously as more closed lead outcome data becomes available.

“Lead scoring model” is too generic; the AI capability required is specifically predictive lead scoring. “Relationship intelligence” supports relationship analytics and engagement insights, but it does not score leads by conversion probability. “Configure forecast” applies to pipeline forecasting, not lead scoring accuracy.

References/topics: Predictive lead scoring; lead prioritization; scoring model accuracy; automatic model retraining; AI-driven lead qualification.

The issue is that the sales manager already generated a Sales Research Agent blueprint but forgot to include the quarterly competitive intelligence brief. The brief is an external document and the case study states it is delivered as a PDF document , so the correct first content action is to upload the competitive intelligence brief as a PDF file , not CSV. Microsoft’s Sales Research Agent documentation states that users can select Add data to upload files including CSV, Excel, or PDF to augment research with additional data.

The second required action is to add a data source , because the competitive intelligence brief is not part of the default Dynamics 365 Sales data. Sales Research Agent connects to Dynamics 365 Sales data by default, but additional external files must be added as supporting data sources before they can influence the analysis. The documentation identifies the Data area as the place where the research data source is specified and where additional data sources can be added.

The final action is to regenerate the canvas/blueprint so the agent reprocesses the analysis using the newly added PDF. Refreshing alone is not the best answer because the problem is not stale data; it is missing context. Regeneration creates updated research output with the new source included.

References/topics: Sales Research Agent; research canvas; adding PDF data sources; blueprint regeneration; intelligent opportunity research.