Microsoft AB-210 Exam Questions

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.

The correct configuration is Sales Qualification Agent in Research and engage mode. The question contains one conflicting sentence about human-managed outreach, but the explicit agent requirements require autonomous outreach, response handling, BANT evaluation, positive-intent detection, disqualification of poor-fit leads, supervisor notification, and seller handoff. Those capabilities map only to Research and engage mode.

Microsoft's Sales Qualification Agent documentation states that both modes can research leads and check target customer profile fit, but only Research and engage mode checks BANT criteria, sends outreach emails, detects positive intent, sends follow-up emails, and engages with leads based on their responses. Microsoft's handoff criteria documentation also states that BANT criteria are only used by Research and engage mode, and that leads satisfying BANT and purchase-interest criteria are handed over to sellers, while leads that do not satisfy the configured criteria are disqualified and added for supervisor review.

Option B or D would be correct only if the controlling requirement were strictly ''human sellers must manage all outreach.'' But the listed automation requirements go beyond Research-only mode, so the exam answer is C.

References/topics: Sales Qualification Agent; Research and engage mode; target customer profile; BANT; purchase intent; lead handoff; supervisor review.

Yes, the solution meets the goal. The requirement has two parts: sales managers need deal insights, and the system must not automatically perform outreach to buyers. Sales Close Agent in Research mode is the correct fit because it researches opportunities, calculates importance and risk, generates summaries, and provides actionable recommendations for sellers to review manually. Microsoft states that the opportunity research experience shows a summary and a See full research page with complete opportunity insights and recommendations.

Research mode is intentionally different from Engage mode. Engage mode is the autonomous customer-interaction mode; Microsoft describes Sales Close Agent Engage as managing customer interactions and driving sales for high-velocity deals. By contrast, Research mode focuses on research, opportunity insights, risks, and seller guidance. Microsoft's configuration guidance for Sales Close Agent Research describes selecting opportunities to research, configuring refresh frequency, and providing company context so the agent can curate research insights. Therefore, using Research mode while requiring sellers to manually review the insights satisfies both requirements: the organization receives AI-generated deal intelligence, but buyer outreach remains under human seller control.

References/topics: Sales Close Agent Research mode; opportunity research insights; manual seller review; Engage mode versus Research mode; AI-supported opportunity management.

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 feature is Cloud flow. Dynamics 365 Sales mobile app push notifications are created through Power Automate by using the Send push notification V2 action. Microsoft's Sales mobile documentation states that the Dynamics 365 Sales mobile app supports push notifications created with the Send push notification V2 action, where the mobile app is set to Sales, the target app is selected, recipients are defined, and the notification can open a specific table record when selected.

Power Automate documentation also describes the creation process as a notification from a flow: go to Power Automate, create an automated flow, choose a trigger such as Microsoft Dataverse, then add the Send push notification V2 action. That matches the requirement to configure several seller notifications for the Sales mobile app. Classic flow is not the correct answer because modern mobile notification automation should be implemented with Power Automate cloud flows, not legacy/classic workflow patterns. Plug-in is also wrong because plug-ins are server-side Dataverse extensions for custom business logic; they are not the standard no-code configuration mechanism for mobile push notifications.

References/topics: Dynamics 365 Sales mobile app; custom push notifications; Power Automate cloud flows; Send push notification V2; Dataverse-triggered seller automation.