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.

The correct integrations are SharePoint document management and Teams conversation collaboration. SharePoint document management is required because the company wants opportunity files stored in a central location. Microsoft's Dynamics 365 Sales SharePoint integration is specifically designed to store documents related to Sales records in SharePoint while allowing users to access, share, and manage those documents from the Sales app.
Opportunity is one of the standard Sales records supported for SharePoint document integration.
Teams conversation collaboration is required because sellers must collaborate using chat conversations associated with sales records. Microsoft's Teams chat integration for Dynamics
365 Sales lets sellers start a new Teams chat or connect an existing chat directly to a Sales record, so conversations remain associated with the relevant opportunity, lead, account, or other record.
OneNote integration is for note-taking, not centralized file storage. Conversation intelligence analyzes calls and seller conversations for coaching and insights; it is not the feature for record- linked chat collaboration. Server-side synchronization with Exchange Online supports email, appointments, contacts, and tasks synchronization, but it does not satisfy the SharePoint file storage or Teams chat association requirements.

Explanation:
Requirement
Configuration
Define shared properties for several drone models
Product family
Combine drones and accessories into a package
Bundle
Represent a single drone model
Product
The correct configuration is based on the product catalog hierarchy in Dynamics 365 Sales. A Product family is used when several related products need to share common characteristics or inherited properties. For example, a drone product family can define shared attributes such as flight time, camera type, battery compatibility, or warranty tier, and individual drone models can inherit or specialize those attributes. This is exactly what the requirement means by defining shared properties for several drone models.
A Bundle is used when multiple sellable products are combined into one package. If the company wants to sell a drone together with spare batteries, propellers, carrying cases, or accessories, that package should be configured as a bundle. The seller can then add the bundle to an opportunity, quote, order, or invoice instead of manually selecting each component.
A Product represents a single sellable item, such as one specific drone model. Price list is not correct for any of these requirements because price lists define pricing structures and currencies; they do not define catalog hierarchy, shared product properties, or bundled offerings.
References/topics: Dynamics 365 Sales product catalog; product families; product bundles; products; product hierarchy and catalog configuration.

The correct answer is Rounding Amount . In Dynamics 365 Sales price list item configuration, rounding is used when calculated prices must follow a specific price-ending convention, such as ending in .98 or .99 .
Microsoft's pricing guidance explains that price list items can use rounding behavior so calculated product prices can be rounded and made to end in a specified amount, such as 99 cents. The value that defines the exact ending amount is the Rounding Amount . Therefore, to make all calculated prices end in $.98 , the administrator would configure the rounding amount as 0.98 .
Rounding Policy is not precise enough by itself. It controls the direction of rounding, such as rounding up, down, or to the nearest value, but it does not define the exact cents-ending requirement. Pricing Method determines how the price is calculated, such as a currency amount, percentage of list price, markup, or margin. Percentage is used when a percentage-based pricing method is selected, but it does not force prices to end in $.98 . The requirement is explicitly about the final rounded price ending, so Rounding Amount is the correct function.
References/topics: Price lists; price list items; rounding amount; rounding policy; Dynamics 365 Sales product pricing.

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.