A consultant wants deal-risk scoring on the forecast page to factor in a custom 'contract complexity index' that the client calculates from clauses not captured anywhere in Dynamics 365 Sales. Which extension approach delivers this?
Select an answer to reveal the explanation.
Short Explanation
The starting problem is that a piece of information the client cares about simply does not exist inside the system yet — nobody has ever asked Dynamics to calculate anything like it. Turning on call-recording analysis will not help, because that tool listens to conversations, and this index comes from contract clauses, not from what gets said on a call. Handing the job to a lead-scoring tool will not help either, because that tool's whole purpose is judging how promising a new lead is, long before a deal reaches the forecasting stage where this index matters. Typing a number into a comments box by hand might feel like progress, but it is invisible to the automated risk narrative that reads structured fields, not free text. The real fix is to teach a model to calculate the index from the client's contract data, publish that model, and then connect its output to a field the risk scoring actually looks at — that is how a brand-new signal becomes part of an existing AI-driven process.
Full Explanation
The correct answer is D. The client's contract complexity index is a bespoke calculation based on data that does not exist anywhere in Dynamics 365 Sales, so the extension has to both generate that score and make it consumable by the platform's deal-risk configuration; building an AI Builder model trained on the client's contract data, publishing it, and surfacing its output through a custom field that the deal-risk configuration references accomplishes both steps. Option A is incorrect because Conversation Intelligence analyzes call recordings and transcripts for talk patterns and keyword mentions, which has no relationship to contract clause complexity captured outside of calls. Option B is incorrect because the Sales Qualification Agent evaluates leads before they become opportunities; it is not designed to compute or attach a risk factor to opportunities already in the forecasting pipeline. Option C is incorrect because typing the index into a comments field manually is not an extension of the AI-driven deal-risk scoring at all, and it will not be picked up by the automated forecast narrative the way a properly wired field would be.