Microsoft AB-210 Exam Dumps

The correct answer is Opportunity summary. The requirement is not to score the opportunity, show the next activity, or display health indicators; it is to reduce the seller's manual review effort before contacting the customer. Microsoft's Copilot capability for Dynamics 365 Sales provides AI-generated summaries for opportunity records so sellers can quickly understand key deal context, related activities, emails, and important history without reading the full timeline manually. Microsoft specifically states that Copilot record summarization generates concise summaries of key information from sales records such as opportunities, leads, and accounts.

Because the company uses a custom opportunity form, the opportunity summary widget must be added to that form. Microsoft's implementation guidance explicitly flags custom opportunity forms and asks whether the opportunity summary widget has been added, and the Copilot summary documentation notes that the opportunity summary widget is available by default on the standard form but must be added to custom forms. Up next guides sellers to the next activity, Health score and Predictive opportunity scoring evaluate opportunity risk or likelihood, and Timeline highlights is narrower than the full AI-generated opportunity overview.

References/topics: Copilot opportunity summary; custom opportunity forms; AI-generated sales record summaries; seller productivity in Dynamics 365 Sales.

The correct answer is D. Opportunities that use the expired price list can continue through their lifecycle. In Dynamics 365 Sales, a price list can include a Start Date and End Date to define the effective period for that price list, such as a promotional pricing period. Microsoft's pricing guidance explains that price lists and price list items define pricing for products, and that price calculation applies across opportunity, quote, order, and invoice records.

The expiration date controls the effective availability of the price list going forward; it does not automatically invalidate existing opportunity records that already reference that price list. This distinction matters operationally: if an opportunity was already created with a valid price list, the sales process can continue without forcing users to replace pricing midstream. That preserves pricing consistency across the opportunity lifecycle and prevents disruption to quotes, orders, and downstream sales documents.

Option A is too strong because Dynamics 365 does not require replacement of prices simply because the referenced price list later expires. Option B incorrectly limits use based on the creation date of the opportunity. Option C is not the best answer because the key supported behavior is continuation of existing opportunities, not adding expired price lists to new opportunities with a warning.

References/topics: Price lists; price list start and end dates; opportunity pricing; product catalog pricing; opportunity lifecycle management.

No, the solution does not meet the goal. The requirement clearly states that sales managers need insights about deals, but the system must not perform automatic outreach to buyers. Sales Close Agent Engage mode is designed for autonomous customer engagement. It can interact with buyers, send outreach or follow-up communications, and help progress sales conversations automatically. That violates the restriction in the question.

For this scenario, the appropriate configuration is Sales Close Agent in Research mode, not Engage mode. Research mode supports opportunity management by analyzing deal context, surfacing risks, identifying signals, and providing recommended next actions to sellers. It gives managers and sellers AI-generated deal insights while keeping buyer communication under human control. That is exactly what the company requires.

Engage mode would only be acceptable if the company wanted the agent to actively contact buyers or automate customer-facing communication. Since the requirement explicitly prohibits automatic outreach, Engage mode fails the stated goal.

References/topics: Sales Close Agent; Research mode versus Engage mode; opportunity insights; deal risk analysis; AI-assisted opportunity management without autonomous outreach.

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 components are mobile security roles and appropriate user licenses. Installing the mobile app alone does not grant access to Dynamics 365 Sales records. Microsoft's mobile setup guidance states that Dataverse security privileges control access to Dynamics 365 mobile apps, and the required mobile privilege is preconfigured for Sales roles but may need to be added to custom roles. It also states that the app must be shared with the security role assigned to the user, and users without the privilege can see an empty app list or an access error.

The license requirement is equally important. The Dynamics 365 Sales mobile experience exposes Sales Hub or Sales Professional according to the user's license, so sellers must have the correct Dynamics 365 Sales license assigned before they can access the appropriate Sales app and records. Mobile offline profiles are used for offline synchronization scenarios; they are not the base requirement for record access after app installation. Inbound and outbound profiles are unrelated to Sales mobile access and are not used to authorize sellers in the mobile application.

References/topics: Dynamics 365 Sales mobile app; Dataverse security roles; mobile access privilege; Sales Hub mobile access; Dynamics 365 Sales licensing.