Online Access Free AB-210 Practice Test

Hotspot Question
You are configuring Microsoft Teams calling for a company. The company uses Dynamics 365 Sales and Microsoft Teams. The Microsoft Teams dialer is enabled with all the prerequisites.
Sellers report the following issues:
- The Microsoft Teams dialer is enabled and the security role is
assigned in the dialer configuration, but sellers in the security role
are not able to access the dialer in Sales Hub.
- Sellers report that their existing third-party telephony system
stopped working in Sales.
- Sellers are able to use the Microsoft Teams dialer in Sales Hub, but
sellers that are using a custom model-driven app are not able to access the dialer.
You need to resolve the issues.
How should you configure the Microsoft Teams dialer setup? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Correct Answer:

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

You use price lists in Dynamics 365 Sales. Some price lists have expired.
Users need to be able to continue to manage their opportunities.
Which option is possible?

• A.Opportunities that use the expired price list will display a warning that prices must be replaced.
• B.Users can add the expired price list to opportunities created prior to the expiration date.
• C.Users can add the expired price list to an opportunity but will see a warning.
• D.Opportunities that use the expired price list can continue through their lifecycle.

Hotspot Question
You are customizing a workspace in the sales accelerator.
The workspace must display the industry of a company.
You need to configure the work item appearance for a company.
Which two settings should you modify? To answer, select the appropriate UI element in the answer area.
NOTE: Each correct selection is worth one point.

Correct Answer:

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.

You manage Dynamics 365 Sales.
The sales managers want to confirm that the Sales Close Agent generates insights that help progress deals. When monitoring the Sales Close Agent, you observe that some engagements are failing.
You need to determine how the Sales Close Agent handles engagement failures.
How should you expect the agent to behave when an error occurs?

• A.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.
• B.Retries indefinitely every few minutes until successful.
• C.Stops retrying for that record unless an administrator uses Apply changes in the agent settings to reprocess already-handled records.
• D.Retries once after 24 hours. If it fails again, the record is immediately marked Completed to prevent duplicate processing.

Hotspot Question
A company generates leads from a webform. Salespeople manage leads by country/region. All salespeople are part of the same Dynamics 365 Sales team.
The sales manager requires the following functionality:
- Automate lead assignments.
- Ensure each seller can never have more than 20 open leads.
You create a country/region attribute for the process. You must simplify the process. You plan to use segments when possible.
You need to create a lead assignment rule for each country/region.
Which configurations should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Correct Answer:

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