Free Microsoft AB-210 Practice Test Questions MCQs

Explanation:

The solution does not meet the goal because creating a billing policy is not a valid configuration for tracking or billing AI usage with pre-paid credits in Dynamics 365 Sales.

Billing policies are a concept used in some Microsoft services (e.g., Azure Cost Management) to define rules for cost allocation and governance. However, they are not applicable to Dynamics 365 Sales or Power Platform for tracking AI credit consumption.

To track and bill AI usage with pre-paid credits in Dynamics 365 Sales, the correct actions include:
Purchasing AI credits (capacity add-ons) through the Microsoft 365 admin center.
Assigning AI capacity to the Dynamics 365 environment in the Power Platform admin center.
Monitoring AI credit consumption through the Power Platform admin center or Copilot Studio analytics.

Creating a billing policy does not:
Allocate AI capacity to the environment.
Track AI agent usage.
Enable pre-paid credit billing for AI services.

References:

Microsoft Learn – Dynamics 365 AI credits overview – Explains that AI capabilities are billed through pre-paid credits purchased via the Microsoft 365 admin center.

Explanation:

The solution  does not meet the goal because configuring capacity overages does not enable pre-paid AI credit billing or monthly tracking of AI usage.

Capacity overages refer to scenarios where an organization exceeds its allocated storage or database capacity in Power Platform, and additional charges are incurred. This is a billing mechanism for storage and infrastructure, not for AI credits or AI agent usage.

To track and bill AI usage with pre-paid credits in Dynamics 365 Sales, the correct approach is:

* Purchase AI credits (also known as AI capacity add-ons) through the Microsoft 365 admin center.
* Assign AI capacity to the Dynamics 365 environment in the Power Platform admin center.
* Monitor AI credit consumption through the Power Platform admin center or Copilot Studio analytics.

Configuring capacity overages does not:

* Track AI agent usage.
* Enable pre-paid credit billing for AI services.
* Allocate AI capacity to the environment.

📚 References:

* Microsoft Learn – Dynamics 365 AI credits overview – Explains that AI capabilities are billed through pre-paid credits purchased via the Microsoft 365 admin center.

Explanation:

Users are unable to update meetings by setting the Regarding record in the mobile app. This issue is related to the synchronization of Outlook meetings with Dynamics 365 Sales. Meetings created in Outlook must be synchronized to Dynamics 365 to allow users to set the Regarding record and track them to customer records.

A. Enable server-side synchronization in your environment – Server-side synchronization is required to synchronize appointments, meetings, and emails between Outlook/Exchange and Dynamics 365. Without this enabled, meetings created in Outlook will not sync to Dynamics 365, and users cannot update the Regarding record in the mobile app.

B. Approve the mailboxes for the users – After enabling server-side synchronization, each user's mailbox must be approved in the Dynamics 365 mailbox configuration. This approval allows the system to synchronize email and appointment data for that user. If mailboxes are not approved, synchronization will not occur, and meetings will not be available in the mobile app for tracking.

❌ Why Other Options Are Incorrect:

C. Configure a mobile offline profile – A mobile offline profile defines which data is available offline on the mobile device. While this is useful for offline access, it does not affect the synchronization of meetings from Outlook. The issue is with synchronization, not offline availability.

D. Enable relevance search in Dataverse – Relevance search is a search feature that improves search results across records. It does not impact meeting synchronization or the ability to set the Regarding record. This is unrelated to the issue.

📚 References:

* Microsoft Learn – Server-side synchronization – Explains how to enable synchronization for appointments and emails.

Explanation:

Sellers in the security role are not able to access the dialer → Add the security role to the dialer’s allowed roles list – Even though the security role is assigned to the users, the dialer configuration has an  allowed roles list that explicitly defines which roles can access the dialer. Simply assigning the role to users is not sufficient; the role must also be added to the dialer's allowed roles list to grant dialer access. This ensures that only specified roles can use the dialer.

Existing third-party telephony system stopped working in Sales → Deactivate the phone system in Channel Integration Framework – When the Microsoft Teams dialer is enabled, it can conflict with existing third-party telephony systems integrated through the Channel Integration Framework (CIF). To resolve this, you must deactivate the phone system in the Channel Integration Framework. This disables the third-party integration, allowing the Teams dialer to function without conflicts.

Dialer is not accessible in a custom model-driven app → Set the custom app as an available app in the dialer configuration – The Microsoft Teams dialer is not automatically available in all apps. For the dialer to appear in a custom model-driven app, you must set the custom app as an available app in the dialer configuration. This allows the dialer to be surfaced in the custom app's interface.

❌ Why Other Configurations Are Incorrect:

Update the dialer scope to all security roles – This is not the correct action for this issue. Scope determines which security roles can access the dialer, but the immediate fix for missing access is adding the specific role to the allowed list, not changing the scope globally.

Assign the security role to the root business unit – This is not related to dialer access. Business unit assignment determines data access, not the availability of the dialer feature.

Disable the Microsoft Teams dialer for sellers using the third-party system – This would disable the Teams dialer, which is the opposite of what you want. The issue is that the third-party system stopped working, so you should deactivate the third-party system, not disable Teams.

Remove the public switch telephone network connection from the Microsoft Teams admin center – This is an extreme action that would break all Teams calling, not just the integration with Sales. It is not the correct resolution.

Republish the dialer configuration after saving changes – This is a step to apply changes, but it does not address the specific issue of the custom app. Publishing is required after changes but is not the primary configuration for making the dialer available in a custom app.

Enable the Microsoft Teams dialer for all security roles in the dialer settings – This would grant dialer access to all roles, which is not secure or specific to the issue. The correct action is to add the specific security role to the allowed list.

📚 References:

* Microsoft Learn – Configure Teams dialer allowed roles – Explains how to add security roles to the allowed list for dialer access.

Explanation:

Sellers spend significant time manually reviewing information about opportunities before contacting customers. To reduce this time, you should add the  Opportunity summary to the form. The Opportunity summary is an AI-powered component that provides a concise, contextual overview of the opportunity, including key details such as recent activities, upcoming tasks, and relevant insights.

A. Opportunity summary – This feature synthesizes information from the opportunity record, timeline, and related activities into a single, easy-to-read summary. It helps sellers quickly understand the current status of an opportunity without having to scroll through multiple sections or review each activity individually. This directly reduces the time required for opportunity review.

❌ Why Other Options Are Incorrect:

B. Up next – The "Up next" feature suggests the next best action for the seller (e.g., follow-up task, email, meeting). While helpful, it focuses on recommending an action rather than summarizing the opportunity's history and context, which is what the requirement asks for.

C. Health score – Health score is a measure of the overall health of an opportunity based on AI analysis. While it provides a quick indicator of deal health, it does not provide the comprehensive context or summary of the opportunity's history and activities.

D. Predictive opportunity scoring – Predictive opportunity scoring provides a score indicating the likelihood of winning an opportunity. It is useful for prioritization but does not summarize the opportunity's history or recent activities.

E. Timeline highlights – Timeline highlights show a few key activities from the timeline, but they are not as comprehensive or contextual as the Opportunity summary. The summary provides a more complete overview, including recent emails, meetings, tasks, and notes in a narrative format.

📚 References:

Microsoft Learn – Opportunity summary – Explains how the Opportunity summary provides a contextual overview to help sellers quickly understand opportunities.

Explanation:

To place outbound calls directly from Dynamics 365 Sales records using Microsoft Teams, you must enable the  Microsoft Teams dialer. This feature integrates Teams calling capabilities directly into the Dynamics 365 Sales interface, allowing sellers to initiate calls from records (e.g., leads, opportunities, contacts) with a single click.

B. Enable the Microsoft Teams dialer – The Teams dialer must be enabled in the Dynamics 365 Sales settings. Once enabled, sellers see a call button on records, and clicking it initiates an outbound call through Teams. The call is automatically logged in the timeline, and if configured, call recordings and transcripts can be captured.

❌ Why Other Options Are Incorrect:

A. Configure phone numbers for outbound calling – Phone numbers are required for the dialer to function, but the primary action is enabling the dialer itself. Configuring phone numbers is a prerequisite or supporting task, not the main configuration. The question asks what you should configure to enable calling, which is the Teams dialer.

C. Install the Dynamics 365 Sales mobile app – The mobile app is a separate application for accessing Dynamics 365 on mobile devices. It does not enable the Teams dialer in the main Sales app. The Teams dialer can be used in both web and mobile environments, but installation of the mobile app is not required to enable the dialer.

D. Enable Microsoft Teams meeting integration – Teams meeting integration allows sellers to schedule and join Teams meetings from Dynamics 365 records. This is different from the dialer, which is used for direct outbound calls. Meeting integration does not enable outbound calling.

📚 References:

* Microsoft Learn – Microsoft Teams dialer in Dynamics 365 Sales – Explains how to enable and use the Teams dialer for outbound calls.

Explanation:

Determine if the engagement for the opportunity record is pending, completed, or failed → Sales Agent Runs table view – The  Sales Agent Runs table view provides a detailed, record-level view of each engagement attempt made by the Sales Close Agent. It shows the status of each engagement for a specific opportunity, including whether it is  pending,  completed, or  failed. This view allows administrators and managers to drill into individual records to troubleshoot why a specific opportunity stopped receiving automated outreach.

Provide a weekly performance view that includes Last refreshed and the time period filter → Insights and metrics for the Sales Close Agent – The  Insights and metrics dashboard provides an aggregated, high-level performance view of the Sales Close Agent. It includes key metrics such as total engagements, success rates, and failure rates. This dashboard also features a  Last refreshed timestamp (indicating when the data was last updated) and a time period filter (allowing users to view performance by week, month, or custom range). This is the correct place for a weekly performance view.

❌ Why Other Options Are Incorrect:

Engage settings of the Sales Close Agent – Engage settings are used to configure the agent's behavior (e.g., email templates, sequences, compliance rules). They do not provide performance metrics or engagement status for individual records.

Opportunity pipeline view – The pipeline view displays opportunities by stage and revenue but does not show engagement status (pending, completed, failed) or provide agent performance metrics. It is used for deal progression, not agent monitoring.

📚 References:

* Microsoft Learn – Monitor Sales Close Agent – Explains how to use the Sales Agent Runs table view to check engagement status.

Explanation:

Open the Pipeline view by default in Opportunities → Set the default Opportunity form – The Pipeline view is a specific view within the Opportunity form. To ensure that sellers see the Pipeline view by default when they navigate to Opportunities, you must set the default Opportunity form to the one that includes the Pipeline view as the default view. This configuration determines which form and view are displayed first.

Open a specific form for the opportunity side panel → Configure Opportunity main form – The side panel in the opportunity pipeline view displays details of the selected opportunity. To control which form appears in this side panel, you must configure the Opportunity main form. You can define the specific form that should be used for the side panel display, ensuring sellers see the right fields and layout.

Provide the ability to expand or collapse the grid by sections → Configure Opportunity main form – The ability to expand or collapse grid sections (e.g., by Owner, Account, or Stage) is a property of the Opportunity main form. When you configure the main form, you can enable grouping and section expansion/collapse in the pipeline view. This setting is part of the form's grid configuration.

Display the average value at the bottom of the grid → Enable aggregation on view controls – To display summary values (such as the average estimated revenue) at the bottom of the grid, you must enable aggregation on view controls. This setting allows you to configure column aggregations (e.g., Sum, Average, Min, Max) for the Pipeline view, which then appear in the grid footer.

❌ Why Other Configuration Is Incorrect:

Configure Opportunity quick create form – The quick create form is used for quickly creating new opportunities from other areas of the application. It is not used for configuring the Pipeline view, the side panel, grid sections, or aggregations. This is not applicable to any of the requirements.

📚 References:

* Microsoft Learn – Configure pipeline view – Explains how to set default views and configure grid settings.

Explanation:

The sales manager updated the qualification criteria to better align with the target customer profile. The monitoring data shows:

* A shift in how leads are categorized compared to earlier results.
* Continued processing of incoming leads.
* No gaps in evaluation activity.

This data indicates that the agent is functioning as expected after the update.

D. Lead outcomes reflect updated evaluation criteria applied during processing – The shift in categorization is a direct result of the updated qualification criteria. The agent is now evaluating leads based on the new rules, which naturally changes how leads are classified (e.g., more leads may be disqualified or qualified based on the revised profile). Since processing continues without gaps, the agent is actively applying the new criteria to all incoming leads. This is expected and correct behavior.

❌ Why Other Options Are Incorrect:

A. Changes in outcome distribution indicate that additional tuning may be required – A shift in outcomes does not automatically mean additional tuning is required. The shift is expected because the criteria were intentionally updated. Additional tuning would only be needed if the outcomes were inconsistent or not aligned with business goals, but the data does not indicate that.

B. Differences between current and prior results indicate that earlier evaluations were incomplete – Differences between current and prior results do not mean earlier evaluations were incomplete. The differences are due to the criteria change, not because the previous evaluations were flawed or incomplete.

C. Variation in categorization suggests that external factors are influencing lead evaluation – The variation is not due to external factors; it is a direct result of the updated criteria. The agent is applying the new rules consistently, and external factors are not indicated by the data.

📚 References:

* Microsoft Learn – Monitor Sales Qualification Agent – Explains how to interpret shifts in lead categorization after updating criteria.

Explanation:

When the Sales Close Agent encounters an engagement failure (e.g., an email fails to send, a task cannot be created, or an API call times out), it does not continuously retry indefinitely. Instead, the agent  stops retrying for that specific record to prevent duplicate or excessive processing.

B. Stops retrying for that record unless an administrator uses Apply changes in the agent settings to reprocess already-handled records – This is the correct behavior. Once an engagement fails, the agent marks the record and ceases further attempts. An administrator can then use the Apply changes option in the agent settings to reprocess previously handled (failed) records. This gives administrators control over retrying failed engagements without causing system performance issues or duplicate actions.

❌ Why Other Options Are Incorrect:

A. Retries once after 24 hours. If it fails again, the record is immediately marked Completed to prevent duplicate processing – The agent does not retry after 24 hours, nor does it mark failed records as "Completed." Completed status indicates successful processing, which would be misleading for failed engagements.

C. Retries indefinitely every few minutes until successful – Indefinite retries every few minutes would cause significant system load and performance degradation. The agent does not behave this way; it stops after failure to avoid resource exhaustion.

D. Retries up to three times within the next hour. If those attempts fail, the system retries over the next three days. If the agent continues to fail, it is marked as a failure – This describes a more complex retry policy that does not match the actual behavior of the Sales Close Agent. The agent does not have a multi-day retry window; it stops after the initial failure.

📚 References:

* Microsoft Learn – Troubleshoot Sales Close Agent – Explains that failed engagements stop retrying and require administrator action to reprocess.