Hotspot Question
You are creating a business process flow named "Onboard new pet" to support onboarding of new clients for a pet care business.
A partially completed business process flow is shown in the following exhibit.
Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the exhibit.
NOTE: Each correct selection is worth one point.

Explanation:
The condition in the business process flow evaluates the Type column to determine whether the pet is a Cat. However, the preceding stage, Basic Details, only contains the Name step. In a business process flow, a branching rule must be based on steps in the stage immediately before the condition. Microsoft's business process flow design guidance states that branching rules must be based on the steps in the preceding stage, so the Type column must be added as a step in the Basic Details stage before the condition can validate correctly.
After validation is corrected, a user who starts creating a new pet record will initially see one stage:
Basic Details. The Litter type stage is conditional and appears only when the Type value satisfies the rule, meaning the pet type equals Cat. Microsoft explains that branch selection is automatic and happens in real time based on the rules defined in the process definition. Until the user enters a Type value that satisfies the condition, the cat-specific branch is not part of the visible process path.

A company is using Dynamics 365 Sales.
The company is NOT using predictive lead scoring. The company has historical sales records for the last three years.
You need to configure a predictive lead scoring model.
What is the minimum number of records required?

• A. 40 qualified leads and 40 won opportunities
• B. 40 qualified leads and 40 disqualified leads
• C. 40 qualified leads and 40 lost opportunities

Explanation: Only visible for Actual4Exams members. You can sign-up / login (it's free).

A seller receives dozens of customer emails daily. The organization wants AI to summarize long conversations and highlight important commitments before meetings. Which Copilot capability provides the greatest benefit?

• A. Email summarization
• B. Duplicate lead detection
• C. Opportunity close prediction
• D. Territory assignment

Explanation: Only visible for Actual4Exams members. You can sign-up / login (it's free).

Case Study 1 - AdventureWorks
Background
AdventureWorks Cycles is a global manufacturer of high-performance bicycles headquartered in Seattle. The company sells products through distributors, specialty retailers, and a growing direct- to-consumer online channel. AdventureWorks Cycles recently expanded its product catalog to include the athlete package. This package includes a cycle, connected devices and subscription- based analytics services.
To support this expansion, the company wants to modernize its sales operations by implementing Microsoft Dynamics 365 Sales. The leadership team wants sellers to focus on building relationships with distributors and enterprise buyers rather than manually qualifying leads or assembling product packages.
The sales operations team is responsible for configuring the Dynamics 365 Sales environment.
Their goal is to implement Al-driven processes that streamline the lead-to-cash workflow while ensuring that sellers can easily identify the most promising opportunities.
Current Environment
AdventureWorks Cycles previously used a legacy CRM system that tracked leads and opportunities but lacked predictive intelligence or automated lead qualification. Sellers manually evaluate incoming leads, which creates delays and inconsistent prioritization.
The global sales team manages approximately 15,000 leads per month generated from marketing campaigns, trade shows, and partner referrals.
Product data is stored in multiple systems. Product managers maintain products and pricing in spreadsheets. Information regarding custom relationships, competitor analysis, and region- specific marketing content is stored in a SharePoint site called the sales portfolio.
The organization has identified several challenges they want to resolve with a new solution:
Sellers often spend significant time researching leads that ultimately do not convert.
Regional managers require in-depth reporting using information from the sales pipeline and seller activities, the point-of-sale solution, website analytics, and the accounting system.
Multiple product offerings are difficult to manage because components are defined in different systems.
Team leads require real-time information on active opportunities, as well as visibility of seller's appointments and phone calls, without needing to navigate into multiple views.
All sellers are assigned Dynamics 365 Sales Enterprise licenses, Also, the CFO has requested that Copilot message packs are pre-purchased by using the Copilot Studio subscription license.
A Dynamics 365 sales sandbox environment has been in use for six months. There are 60 leads records with 30 records that are qualified and 20 that are disqualified. Ten of the qualified leads are over three months old.
Business Requirements:
AdventureWorks Cycles has defined the following business requirements for the production environment of Dynamics 365 Sales:
Sellers in all regions should be able to review the new mountaineer cycles. The cycles include economy and premium fittings. When creating opportunities, sellers should be able to select a metal type when adding a mountaineer cycle to an opportunity. The metal types include chrome, aluminum, and titanium.
Pricing managers must be able to create deals for the same products in their own currencies and at their own prices, without reference to the cost of the product.
Sellers must be able to quickly view their own opportunities by phase.
Predictive scoring should be enabled for leads created within the last three months in the sandbox environment. This should provide seller training on the scoring's interpretation and usage.
A segment of leads named Hot is needed that will contain all leads where the source is phone, employee referral or partner. Leads from this segment should be distributed to sellers by using a round robin method.
Agents should not be able to take action on any data that is created in the production environment before they are started.
All sellers should be able to access disqualified leads.
Technical Information and Requirements:
The new Dynamics 365 Sales environment must meet the following technical requirements:
Agents must use a dedicated service identity to execute write actions with a controlled security role in Dataverse.
The sales operations team lead must be assigned the Power Platform administrator role.
The lead pricing manager must be assigned to the Microsoft 365 billing admin role.
The vice president of sales must be assigned the Al admin role.
A sandbox and a production environment must be created. Both of the environments must be enabled for Al capacity, but usage should be capped on the sandbox environment.
A trial environment must be created, with the Sales Qualification Agent configured to business requirements.
Sellers must be assigned the security roles on the production environment only.
All sellers must be assigned a customized version of the salesperson role. This role should grant read access only to the leads that the sellers own.
The EnableRoleBasedSystemViews property must be set to true for the production environment.
No Azure subscriptions are available in the tenant.
Issues:
During early testing, the sales operations team identify the following issues:
The Sales Qualification Agent has disqualified several leads in the trial environment. The vice president of sales has requested to understand the reason for the disqualified leads.
Sellers are unable to create agents in the production environment.
Agent consumption has been unreliable. The company requires that Al capacity is always available to sellers.
You need to allow sellers to view leads disqualified by the Sales Qualification Agent in production.
Which two actions should you perform? Each correct answer presents part of the solution.
Choose two.

• A. Assign organization level read on lead table to sellers.
• B. Upgrade the agent to research and engage mode.
• C. Update the agent look back period.
• D. Update the EnableRoleBasedSystemViews setting.

Explanation: Only visible for Actual4Exams members. You can sign-up / login (it's free).

Case Study 2 - Contoso Ltd
Background
Contoso Ltd. is a global technology distributor headquartered in Redmond, Washington. The company sells networking equipment, cloud infrastructure, and managed services to enterprise customers across North America and Europe.
Contoso Ltd. currently manages its sales operations by using Microsoft Dynamics 365 Sales and plans to enable Sales Insights in the future.
The leadership team wants to modernize the sales organization by introducing capabilities that help sellers prioritize leads, analyze opportunities, and accelerate deal closure.
The company has approximately 150 field sellers, 40 insider sellers, 20 sales managers, and a central IT team responsible for configuring the sales platform. Contoso Ltd.'s executive leadership has defined the following goals for the new sales platform implementation:
Improve seller productivity by reducing manual research and data entry.
Use Al insights to prioritize leads and opportunities.
Provide automated recommendations to sales representatives throughout the deal lifecycle.
Improve collaboration between sellers and sales managers.
Current Environment:
Sales platform
Contoso Ltd. uses Microsoft Dynamics 365 Sales integrated with Microsoft 365 services.
The following components are currently deployed:

Data and lead management
Leads are important for driving new business at Contoso Ltd. They are generated from multiple sources including:
- Marketing automation campaigns
- Website registrations
- Partner referrals
- Trade show contact imports
Marketing teams import lead lists weekly into Dynamics 365 Sales by using spreadsheet imports.
Sellers currently evaluate leads manually.
Sales managers report that this process results in inconsistent prioritization across regions.
Opportunity management
Opportunities are tracked in Dynamics 365 Sales through a defined qualification-to-opportunity lifecycle to ensure accurate reporting.
Sales leadership has requested the Contoso Ltd. IT team to evaluate the following capabilities:
- AI-generated summaries of opportunity records.
- AI-driven research for customer organizations.
- Automated recommendations for closing deals.
Business Requirement:
Contoso Ltd.'s executives have defined the following business requirements:
Lead management
Inside sellers must use a seller engagement workspace that prioritizes leads automatically based on predicted likelihood to convert.
All sellers are guided through a consistent set of qualification steps aligned to Contoso Ltd.'s sales strategy.
Leads cannot be advanced to the development stage until a decision maker has been confirmed.
Sales leadership requires flexibility in how leads are converted. Inside sales need automatic opportunity creation. Field sellers need the option to manually decide whether an opportunity should be created when a lead is qualified.
Lead scoring must be implemented to help sellers identify high potential leads automatically.
Lead scoring must continuously improve based on historical sales outcomes.
Opportunity development
The opportunity flow must be improved by using Al-driven research and automated insights.
Field sellers must be able to access contextual research about customers and competitors while working on opportunities.
Opportunity records must display Al-generated summaries to reduce the time required to review historical activities.
Field sellers must use the Opportunity pipeline view to visualize, prioritize, and manage opportunities.
All opportunity revenue must be calculated using opportunity line items based on selected Contoso Ltd.'s products and standard pricing.
Sales managers must receive an external quarterly competitive intelligence brief to help with their research. This should be delivered as a PDF document.
Sales performance
Sales managers require improved pipeline and revenue forecasting capabilities. The managers need to report on their business performance and use insights, visuals, and recommended next actions.
The new solution must provide the following:
- Allow sales managers to configure forecasts for opportunity pipelines.
- Notify the seller's manager when a draft quote is created and requires approval.
- Allow leadership to track performance against revenue goals.
- Ask questions about Dynamics 365 Sales data to support executive analysis and decision making.
- Support data definitions used at Contoso Ltd. when reporting.
Technical Requirement:
Contoso Ltd.'s IT department defines the following priorities for the sales platform.
AI capabilities
The platform must support the following Al features:
- Lead scoring to guide sellers to priority items.
- Opportunity research insights to prepare deal analysis.
- Copilot-generated summaries of sales records to help with decision making.
- AI-powered research and analytics to aid leadership reporting.
- When performing sales research, sales managers must be able to save their favorite prompts.
Automation
Automation must be implemented to guide sellers through recommended next steps during the sales cycle.
Any approvals must use the Power Automate Approvals connector.
Field sellers use the existing Lead to Opportunity Business Process Flow to manage their leads.
A Power Automate desktop flow is used to process orders into a partner ordering application that completes fulfillment.
Collaboration
All sellers must be able to collaborate by using Teams and store related sales documents in SharePoint.
AI-driven insights
The company is deploying the Sales accelerator to guide seller activities.
The Sales Research Agent
Sales managers will use the Sales Research Agent to gather intelligence about customer organizations.
The sales managers have the following requirements:
- Must be able to reuse visualizations after they are created; they don't want to recreate them.
- Must have a consistent method to quickly return to a blueprint that they frequently use.
- Must be able to retain a library of questions to receive consistent responses based on definitions approved by the company.
- Should have Bing search enabled on the environment for generative Al feature settings.
Platform extensions
The IT department plan to extend the platform by doing the following:
- Create Power Automate flows to automate seller tasks.
- Embed Power Apps components inside model-driven forms.
- Embed Power BI reports for sales analytics.
Testing
The IT department is testing predictive lead scoring with a small group of sellers.
The IT department edits the existing lead scoring model by adding new fields.
Issues:
Users have reported the following issues:
- Field sellers spend a significant amount of time researching customers before engaging with prospects.
- Sales managers cannot easily identify the most promising opportunities across regions.
- Lead prioritization varies significantly between sales teams.
- Testers report they cannot access the field changes in the lead score.
- A sales manager generated a blueprint but forgot the competitive intelligence brief.
Hotspot Question
You need to configure AI capabilities that prioritize leads and improve scoring accuracy in Dynamics 365 Sales.
How should each requirement be configured? To answer, select the appropriate options in the answer area.

Explanation:
The correct capability for automatically prioritizing leads based on conversion probability is Predictive lead scoring. Dynamics 365 Sales predictive lead scoring assigns scores to leads so sellers can prioritize the leads most likely to qualify or convert. Microsoft's Sales documentation states that predictive lead scoring helps sales teams prioritize leads based on scores and improve lead qualification outcomes. This directly matches Contoso's requirement to guide sellers toward high- potential leads and reduce inconsistent manual prioritization across regions.
To meet the requirement that lead scoring must continuously improve based on historical sales outcomes, configure the model to automatically retrain. Microsoft's predictive lead scoring guidance explains that retraining uses the latest leads in the organization to improve model accuracy, and automatic retraining allows the application to retrain the model every 15 days. This is the correct option because Contoso wants the scoring model to improve continuously as more closed lead outcome data becomes available.
"Lead scoring model" is too generic; the AI capability required is specifically predictive lead scoring. "Relationship intelligence" supports relationship analytics and engagement insights, but it does not score leads by conversion probability. "Configure forecast" applies to pipeline forecasting, not lead scoring accuracy.