Free Microsoft AB-210 Practice Exam with Questions & Answers

The Sales Close Agent in Research mode is the correct fit for assessing opportunity risk and prioritizing opportunities that are gaining traction. Microsoft’s AI agents guidance states that the opportunity-focused sales agent helps sellers close deals faster by autonomously researching opportunities, providing visibility into emerging risks, and highlighting promising opportunities. It is designed to identify high-value and at-risk opportunities so sellers can prioritize their effort and act on critical insights.

The Sales Close Agent in Engage mode is the correct fit for recommending opportunity products to clients automatically. Microsoft describes Sales Close Agent as an autonomous agent for high-velocity sales execution that engages customers, recommends products, handles objections, and drives transactions toward closure using configured product catalog and pricing information.

The Sales Qualification Agent is not appropriate for these scenarios because it is lead-focused, not opportunity-focused. It researches inbound leads, evaluates fit, generates outreach, and can hand promising leads to sellers depending on the configured mode. It does not manage opportunity risk, opportunity traction, or client product recommendations for active deals.

References/topics: Sales Close Agent; opportunity research; opportunity risk; opportunity prioritization; Sales Close Agent Engage mode; product recommendations.

The correct Research mode capabilities are analyzing historical interaction data to generate opportunity insights and reviewing deal signals with risks and recommended mitigations . Microsoft’s Sales Opportunity Agent documentation describes the opportunity-focused agent as helping sellers focus on important opportunities by identifying high-value and at-risk deals, providing critical insights and recommendations, and helping sellers mitigate risks. Microsoft also states that the agent gathers information from multiple sources and provides a streamlined research experience, stakeholder and competitor intelligence, and actionable risk mitigation strategies.

Option C is correct because the agent uses opportunity context, CRM history, emails, meetings, and other available signals to generate deal insights. Option D is also correct because Microsoft’s Responsible AI FAQ specifically identifies early risk detection and recommended mitigation strategies based on historical data and communication analysis. Options A and B describe customer engagement behavior: running sales sequences or initiating follow-up communication. That belongs to engagement automation, not Research mode. Option E is too workflow-task oriented; Research mode surfaces insights and recommendations, but it is not primarily a task-generation or outreach automation engine.

References/topics: Sales Close Agent Research mode; Sales Opportunity Agent; opportunity insights; deal signals; risk mitigation; intelligent opportunity research.

The correct actions are to enable server-side synchronization and approve the users’ mailboxes . This is a very specific Dynamics 365 Sales mobile prerequisite. Microsoft’s Sales mobile setup guidance states that to set a regarding record for a meeting, server-side synchronization must be enabled in the environment and the email address must be approved. The mobile meeting documentation repeats the same requirement: users can set the regarding record only when server-side synchronization is enabled and the email address is approved.

This makes options A and B the only correct pair. Server-side synchronization connects Dynamics 365 with Exchange/Outlook data for appointments, contacts, tasks, and email synchronization. Microsoft’s server-side synchronization documentation describes it as the synchronization mechanism between customer engagement apps and Exchange, including support for appointments and mobile scenarios. A mobile offline profile controls offline data availability, not whether Outlook meetings can be tracked to customer records. Relevance search improves search behavior and performance, but it does not enable the Regarding field for meetings.

References/topics: Dynamics 365 Sales mobile app; meeting tracking; Regarding record; server-side synchronization; mailbox approval; Outlook appointments.

The solution does not meet the goal. Creating an Azure subscription is associated with pay-as-you-go billing scenarios, not the required pre-paid credits model. Microsoft’s Dynamics 365 Sales agent billing guidance states that Sales Copilot and agent capabilities support two billing models: prepaid capacity and pay-as-you-go . Prepaid capacity uses Copilot Studio message pack subscriptions purchased in advance, while pay-as-you-go bills for actual message consumption during the month.

Because the requirement explicitly says AI billing must use pre-paid credits , the correct approach is to purchase Copilot Studio message packs or Copilot Credits and assign/manage that capacity for the relevant environment. Power Platform guidance explains that Copilot Studio credits/capacity are managed and monitored through the Power Platform admin center, and if prepaid capacity is exhausted, admins must reallocate capacity, purchase more credits, or enable pay-as-you-go. An Azure subscription may be required for pay-as-you-go cost management, but it does not satisfy a prepaid-credit requirement by itself. Therefore, the proposed solution is incorrect.

References/topics: Dynamics 365 Sales agent billing; prepaid capacity; Copilot Studio message packs; Copilot Credits; pay-as-you-go billing.

Issue

Configuration

Sellers are not able to access the dialer in Sales Hub

Assign the security role to the root business unit.

Existing third-party telephony system stopped working

Disable the Microsoft Teams dialer for sellers using the third-party system.

Dialer is not accessible in a custom model-driven app

Set the custom app as an available app in the dialer configuration.

For the first issue, the security role must be associated with the root business unit . Microsoft states that when Teams dialer is enabled for specific security roles, the selected roles must be associated with the root business unit; otherwise, users do not see the Teams dialer in Sales Hub. Merely assigning the role in the dialer configuration is not enough if the role is not rooted correctly.

For the second issue, Teams dialer conflicts with third-party telephony integrations that use Dynamics 365 Channel Integration Framework. Microsoft explicitly notes that when Microsoft Teams dialer is enabled, other telephony systems connected through Channel Integration Framework stop working for users for whom Teams dialer is enabled. Therefore, sellers who must continue using the third-party telephony system should not have Teams dialer enabled.

For the custom model-driven app issue, the dialer must be made available for that app in the dialer configuration. In the Teams dialer advanced options, administrators select the apps where the dialer should be available; Sales Hub is selected by default, so custom apps must be added explicitly.

References/topics: Microsoft Teams dialer; Dynamics 365 Sales calling; security roles; root business unit; Channel Integration Framework; custom model-driven app availability.

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.

Requirement

Configuration

Define measurable sales target

Goal metric

Aggregate opportunity revenue

Rollup column

The correct configuration for defining measurable sales targets is Goal metric . In Dynamics 365 Sales, goals are measured by using goal metrics, which define what is being measured and how performance is calculated. Microsoft’s goal documentation explains that goals help measure progress toward targets such as revenue, while goal metrics and their rollup fields define the values used to calculate performance against those targets.

To aggregate opportunity revenue, use the Rollup column . A goal metric uses rollup fields/columns to calculate actual, in-progress, or custom values. Microsoft specifically describes a money-based goal metric that uses the Opportunity table and the opportunity actual revenue field to track money amounts from opportunities closed as won. This matches the requirement to aggregate opportunity revenue for monthly seller targets. Rollup query is not the best answer because it only adds filtering criteria to an existing goal metric, such as limiting records by owner, territory, or other conditions; it does not define the revenue aggregation itself. Goal hierarchy organizes parent-child goals, and forecasting supports pipeline projections, but neither defines the measurable target calculation or aggregates opportunity revenue for goal achievement.

References/topics: Dynamics 365 Sales goals; goal metrics; rollup columns/fields; opportunity revenue aggregation; seller revenue target tracking.

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.

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.