The three default rule-style suggestions are the Record Owner of the initiating record , the Created By user of the initiating record , and the manager assigned on the seller's system user record . Suggested contacts in Dynamics 365 Sales Teams chat are intended to help sellers quickly find coworkers who are relevant to the record they are working on. Microsoft states that administrators can enable suggested contacts when a seller starts a new connected chat, and that rules-based contact suggestions can be configured for supported Dynamics 365 record types.
The rule engine supports relational rules: Microsoft explains that a relational rule suggests a user who has a relationship with the linked record type or one of its related records, and administrators can select a user field directly on the record or through related entities. The record owner and created-by user are direct relational users on the initiating record. The seller's manager is reached through the system user relationship. The business-unit owner is not the default suggestion path for seller collaboration, and "last modified by" or a user who updated a timeline activity are not the default rule answers in this configuration set.
References/topics: Teams chat in Dynamics 365 Sales; suggested contacts; rules-based contact suggestions; relational suggestion rules; sales collaboration.

The correct configuration is Business process flow. A structured lead qualification process requires sellers to move through defined stages and steps before a lead is converted into an opportunity. Microsoft describes business process flows as a way to guide users through stages of sales, marketing, or service processes toward completion. Business process flows can also include branching logic and defined steps, which makes them the correct mechanism for standardizing how sellers qualify leads before conversion.

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.

The correct conclusion is that lead outcomes reflect updated evaluation criteria applied during processing
. The Sales Qualification Agent evaluates inbound leads against the configured target customer profile and qualification settings. Microsoft states that the target customer profile suitability is determined by the attributes defined in the agent configuration's handoff criteria, and the agent categorizes leads as high, moderate, or low fit based on how well the lead matches those attributes.
Therefore, when the sales manager updates the qualification criteria, a shift in categorization is expected. It means the agent is applying the new criteria to processed leads, not that the old evaluations were incomplete or that external factors are necessarily driving the change. The continued processing and absence of evaluation gaps also indicate normal operational continuity. Microsoft's Sales Qualification Agent setup guidance explains that the agent works on assigned leads based on configured selection criteria and that stopping the agent prevents new lead processing; here, processing continued, so the agent remained active while using the revised configuration. Option A is too speculative: tuning might be useful later, but the evidence given does not prove a tuning problem. The clean interpretation is D .
References/topics: Sales Qualification Agent; target customer profile; qualification criteria; lead categorization; AI-driven lead qualification monitoring.

The correct trigger type is Automated. The requirement is event-driven: when a lead is qualified and an opportunity is created or updated, the system must automatically create a follow-up task for the opportunity owner. In Power Automate, this is implemented as an automated cloud flow that starts when a Dataverse event occurs, such as when a row is added, modified, or deleted.
Microsoft's Dataverse trigger documentation states that the When a row is added, modified or deleted trigger runs a flow whenever a selected Dataverse table row is created or changed.
A scheduled trigger is wrong because the requirement is not time-based. Running the process hourly or daily would delay task creation and could miss the intended immediate follow-up behavior. An instant trigger is also wrong because it requires a user to manually start the flow.
Microsoft describes instant cloud flows as manually triggered flows, while automated flows run after an event triggers them. For this case, the flow should listen for the qualifying lead or opportunity event in Dataverse, then create the follow-up task and assign it to the opportunity owner.