Study guide
16.2 Evaluating Use Cases for Business Logic
Microsoft Certified: Intelligent Applications Builder Associate AB-410
Track your progress as you read
Finished sections get a check mark.
1 Introduction
1.1 About the AB-410 Exam 1.2 How to Use This Study Guide
2 Chapter 2: Designing Power Platform Solutions with AI-Enabled Tools
2.1 Analyzing Requirements and Identifying Components 2.2 Evaluating Built-in Agents for Business Solutions 2.3 Recommending Extensibility Options
3 Chapter 3: Environments and ALM Strategy
3.1 Recommending Environment Types 3.2 Solution and Application Lifecycle Management Strategy
4 Chapter 4: Dataverse Tables and Columns
4.1 Creating and Editing Tables in the Data Workspace 4.2 Configuring Table Properties 4.3 Creating and Modifying Columns
5 Chapter 5: Relationships, AI Data Features, and Data Security
5.1 Configuring Table Relationships 5.2 Configuring Prompt Columns and Row Summaries 5.3 Configuring Public Views and Main Forms 5.4 Configuring Dataverse Security
6 Chapter 6: Model-Driven App Forms and Views
6.1 Creating and Configuring Forms for Model-Driven Apps 6.2 Creating and Configuring Views for Model-Driven Apps 6.3 Creating Generative Pages with Natural Language
7 Chapter 7: Composing, Securing, and Visualizing Model-Driven Apps
7.1 Composing a Model-Driven App 7.2 Configuring Access to Model-Driven Apps, Forms, and Views 7.3 Model-Driven App Charts and Dashboards
8 Chapter 8: Creating and Designing Canvas Apps
8.1 Creating a Canvas App Using Data 8.2 Designing for Accessibility, Performance, Responsiveness, and Usability 8.3 Automating Business Processes from Canvas Apps
9 Chapter 9: Canvas App Components, Variables, and Error Handling
9.1 Reusable Components, Named Formulas, and User-Defined Functions 9.2 Managing Variables and Collections 9.3 Implementing Error Handling in Canvas Apps
10 Chapter 10: Testing Canvas Apps and Creating Agents from Apps
10.1 Testing Canvas Apps with Monitor 10.2 Creating a Copilot Studio Agent from a Canvas App
11 Chapter 11: Cloud Flow Triggers, Connectors, and Approvals
11.1 Recommending Cloud Flow Triggers 11.2 Evaluating and Recommending Connectors 11.3 Managing Approvals with Cloud Flows
12 Chapter 12: Cloud Flow Actions, Control, and Troubleshooting
12.1 Configuring Cloud Flow Actions 12.2 Implementing Flow Control with Conditions and Loops 12.3 Testing and Troubleshooting Cloud Flows
13 Chapter 13: Building Prompts in AI Hub
13.1 Building Prompts from Templates or from Blank 13.2 Adding Inputs to a Prompt 13.3 Adding Knowledge to a Prompt
14 Chapter 14: Prompt Settings, Models, and Consuming AI
14.1 Customizing Prompt Settings and Models 14.2 Consuming Prompts in Apps and Cloud Flows 14.3 Consuming AI Models in Apps and Cloud Flows
15 Chapter 15: Business Rules and Business Process Flows
15.1 Configuring Business Rules 15.2 Configuring Business Process Flows
16 Chapter 16: Calculated Columns and Business Logic Strategy
16.1 Calculated, Rollup, and Formula Columns 16.2 Evaluating Use Cases for Business Logic
16.2 Evaluating Use Cases for Business Logic
Key Takeaways Explain This Topic AI
The core exam heuristic: choose the least complex tool that fully meets the requirement — configuration before automation, automation before code
Business rules deliver instant form logic (show/hide, enable/disable, set required, set values, show errors); scoped to the table they also run server-side on every save
A business process flow can span up to 5 tables with up to 30 stages and 30 steps per stage, guiding users through a consistent process in model-driven apps
Cloud flows are the default for approvals, cross-system integration through 1,000+ connectors, and asynchronous automation; classic Dataverse workflows are legacy awareness only
Plug-ins run synchronously inside the database transaction and are reserved for complex logic that must roll back with the save and that declarative tools cannot express
Last updated: July 2026
Domain 3 of AB-410 — Build business application logic and automation at 40–45% of the exam — is dominated by scenario questions of the form: a requirement, four tools, pick the right one . The winning strategy is a fixed decision order: configuration before automation, automation before code . Always choose the least complex tool that fully meets every stated requirement — and read the scenario for the one constraint that disqualifies the simpler options.
The Business Logic Toolbox
Tool Runs Strengths Watch for
Business rule Form (client); server when scoped to the table Instant UX logic: show/hide, enable/disable, set required, set or clear values, show error messages, recommendations Current-row columns only; no loops, no related-table data, no API calls
Business process flow Model-driven app form Guided stages and steps across up to 5 tables , up to 30 stages , up to 30 steps per stage , with branching Guidance and visualization, not a data-validation engine by itself
Calculated / rollup / formula column Dataverse Derived data with zero automation to build or monitor Values only — none can trigger an action
Cloud flow Asynchronous (or on demand) Approvals, 1,000+ connectors, cross-system integration, scheduled and automated triggers Runs after the commit, not inside the save transaction; licensing and API request limits apply
Classic Dataverse workflow Background or real time Still runs in mature environments; real-time workflows execute inside the transaction Legacy — Microsoft's guidance is to build new automation with cloud flows
Plug-in / custom API Synchronous, inside the database transaction Complex validation, high-volume transactional math, participates in rollback Requires .NET code, plus ALM and maintenance cost; the last resort
Business rules in detail
A business rule combines conditions with actions . Scope decides where it executes: scoped to a specific form or all forms , it runs in the browser for instant feedback; scoped to the table , it also executes server-side on every save, regardless of which app or API wrote the data. Available actions: set column value, clear column value, set business required, set visibility, enable or disable (lock/unlock), show error message for validation, and recommendations. Hard limits: conditions read only the current row's columns, and multi-select choices, file, and language columns are not supported.
Business process flows in detail
A business process flow (BPF) renders a chevron bar across the top of a model-driven form that walks users through stages (for example, Qualify, Develop, Propose, Close), each containing steps (columns to complete or actions to take). A single BPF can span up to 5 tables , with up to 30 stages and 30 steps per stage , and supports conditional branching. BPFs guide the process rather than enforce data correctness — pair one with business rules for stage-aware requirements, such as requiring Estimated Revenue only in the Propose stage.
Classic workflows and plug-ins
Background (asynchronous) and real-time (synchronous) workflows still exist in long-lived environments; AB-410 expects awareness that they are legacy and that new work defaults to cloud flows. Plug-ins are .NET classes registered on event-pipeline steps (pre-validation, pre-operation, post-operation) that run inside the transaction — choose them only when declarative options genuinely cannot do the job: multi-row transactional math, logic that must roll back with the save, or performance-critical validation on bulk operations.
Worked Scenarios
Scenario 1 — Instant form validation. Requirement: when an account's Relationship Type becomes Customer, Credit Limit must become visible and required immediately. Answer: a business rule scoped to the form (or the table). Zero automation, instant feedback, no run history to monitor. A scheduled flow here is the classic over-engineering trap.
Scenario 2 — Approval outside Dataverse. Requirement: discounts over 20% need manager approval in Microsoft Teams, and the quote cannot proceed until approved. Answer: a cloud flow with an approvals action. Approvals, Teams, and Outlook live outside Dataverse — no business rule or column type can reach them.
Scenario 3 — Transactional integrity. Requirement: when an invoice line is saved, the remaining budget on the cost center must decrement inside the same transaction, and any failure must roll the entire save back. Answer: a plug-in . A cloud flow is asynchronous — it fires after the commit, so a failed flow leaves committed, inconsistent data. Rollups are hourly. Only in-transaction logic guarantees the invariant.
Scenario 4 — Guided process. Requirement: new support agents must follow a consistent Triage, Investigate, Resolve sequence, with required steps per stage and management visibility into where every case sits. Answer: a business process flow on the Case table, optionally with business rules making stage-specific columns required.
Scenario 5 — Legacy awareness. Requirement: an existing real-time workflow stamps a reference number on case creation. Answer: leave working legacy logic alone, but meet new equivalent requirements with a cloud flow for background work or a plug-in when truly transactional. Recognize the mapping: real-time workflow means synchronous legacy; background workflow means asynchronous legacy.
Trap Patterns the Exam Repeats
A flow for what a rule does free: hiding or showing columns, setting required state, simple value defaults on a form — business rules do this instantly with no monitoring overhead. Any answer proposing a scheduled flow for form UX is wrong.
Code for what config does: proposing a plug-in to multiply two columns when a calculated or formula column does it natively, with no code, no deployment pipeline, and no maintenance burden.
A rollup for real-time needs: a rollup can be up to an hour stale, so the phrase must be current the moment the child row saves kills the rollup answer.
A calculated column for aggregates: calculated columns see the current row and its parents — never a sum over children.
A business rule for integration: rules cannot call APIs, send mail, or touch other systems — that is flow or code territory.
When two answers both seem plausible, find the requirement word that breaks the tie: immediately on the form points to a business rule; approval , another system , or scheduled points to a cloud flow; inside the transaction or must roll back points to a plug-in; guiding users through stages points to a business process flow.