Automating Contoso's draft quote approval in sequence
Short answer
Create a Power Automate cloud flow, add a Dataverse trigger on the Quote table for draft quotes, add a Start and wait for an approval step using the Approvals connector routed to the manager, then test the flow and turn it on.
Question
Case Study
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study
To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions. When you are ready to answer a question, select the “Question” button to return to the question.
Background
Contoso Ltd. is a global technology distributor headquartered in Redmond, Washington and has 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 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 AI insights to prioritize leads and opportunities.
Provide automated recommendations to sales representatives throughout the deal lifecycle.
Current environment
Sales platform
Contoso Ltd. uses Microsoft Dynamics 365 Sales integrated with Microsoft 365 services. The following components are currently deployed:

Business requirements
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
Opportunities are tracked in Dynamics 365 Sales through a defined qualification-to-opportunity lifecycle to ensure accurate reporting.
The opportunity flow must be improved by using AI-driven research and automated insights.
Field sellers must be able to access contextual research about customers and competitors while working on 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:
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.
Technical requirements
Contoso Ltd.'s IT department defines the following priorities for the sales platform.
AI capabilities
The platform must support the following AI features:
Lead scoring to guide sellers to priority items.
Opportunity research insights to prepare deal analysis.
AI-powered research and analytics to aid leadership reporting.
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.
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 AI 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 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.
Testers report they cannot access the field changes in the lead score.
A sales manager generated a blueprint but forgot the competitive intelligence brief.
You need to automate the quote approval process.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Key Takeaways
It tests whether you can separate true approval routing (Power Automate Approvals connector) from seller guidance or record-status automation, and order the flow build correctly.
This AB-210 case study asks how to automate draft quote approval at Contoso, and the answer is a Power Automate cloud flow: Dataverse trigger, then an Approvals connector step, then test and activate the flow.
Common mistake: Using the Sales accelerator's recommended next actions, a desktop flow, or simply changing the quote status instead of adding an Approvals connector step, which fails Contoso's technical requirement that all approvals use that connector.
Expert Analysis
The boundary this question tests
The key distinction is between approvals as a Power Automate construct and everything else that could plausibly "automate" a quote in Dynamics 365 Sales. Contoso's technical requirement is explicit: any approvals must use the Power Automate Approvals connector. That places this scenario firmly on the Power Platform side of the boundary, not inside the Sales accelerator, the Lead to Opportunity Business Process Flow, or a Dynamics 365 record-status change.
What sits on the wrong side
The Sales accelerator and its recommended next actions can nudge a seller, but they do not route an approval to a manager for a decision. Likewise, the desktop flow Contoso uses for partner ordering is meant for UI-level automation of an external fulfillment application — it is not the approval mechanism. A learner who picks a desktop flow, an accelerator step, or merely changing the quote status has crossed the boundary in the wrong direction.
The correct sequence
Build a Power Automate cloud flow: (1) create the cloud flow; (2) add a Dataverse trigger on the Quote table that fires when a draft quote is created or modified; (3) add a Start and wait for an approval step from the Approvals connector, routed to the seller's manager with an Approve/Reject outcome; (4) test the flow and turn it on so the approval fires in production.
Where the learner comment lands
An anonymous learner proposed exactly this order — create the cloud flow, add a Dataverse trigger, define the approval step, then test and activate — which matches the requirement that approvals run through the Approvals connector.
Exam Strategy
When a case study mentions approvals, immediately anchor on the Power Automate Approvals connector and reject any distractor built on desktop flows, business process flows, or record-status changes. For sequence drag-drops, order the flow logically: trigger first, then the decision action, then validation and activation last. Always re-read the technical requirements section before ordering, because it usually names the exact connector the answer must use.
Frequently Asked Questions
Why not use a desktop flow or the Sales accelerator for Contoso's quote approval?
Which trigger starts the quote approval flow?
What does the approval step do after the manager responds?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Franck56000 👍 1I would propose 1. Create a Power Automate cloud flow 2. Add a dataverse trigger 3. Define an approval step 4. Test and activate the flow.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AB-210 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AB-210 Practice Test →