MB-910 common mistakes
MB-910 · Understand the traps and how to avoid them.
Treating Dynamics 365 Customer Engagement as a single product and describing one shared set of features, instead of distinguishing the individual apps (Sales, Customer Service, Field Service, Customer Insights, Project Operations) and what each is for.
The exam objectives are framed around 'customer engagement apps' as a family, and candidates who have only touched one app generalize its screens and capabilities to all of them, then pick answers that describe the wrong app.
What to do instead
Build a one-page matrix with the apps as rows and columns for primary user, core records, and headline capability (for example opportunity pipeline for Sales, cases and entitlements for Customer Service, work orders and scheduling for Field Service). Recall the matrix before answering any 'which app' question.
Confusing model-driven apps with canvas apps, or assuming Dynamics 365 apps are built on Power Apps canvas, and then attributing canvas-only behaviors (free-form drag-and-drop layout, screen-based navigation) to Dynamics 365 apps.
Both are built on Microsoft Power Platform and appear in the same maker portal, so candidates who have built a canvas app assume the same design model applies to Dynamics 365 apps.
What to do instead
Memorize the distinction: Dynamics 365 customer engagement apps are model-driven, driven by a data model (entities, forms, views, business rules) rather than pixel layout. When a question mentions sitemap, form designer, or views, associate it with model-driven; when it mentions screens and galleries, associate it with canvas.
Mixing up the security model layers, for example claiming that a security role alone grants record access, or that business units are the same as teams.
The layered model (business unit, security role with privilege levels, team, record ownership, hierarchy, field security profile) is genuinely intricate, and candidates collapse it into 'roles give access' because that is how simpler systems work.
What to do instead
Learn the stack in order: a user belongs to one business unit, roles grant privileges at a level (user, business unit, parent-child business unit, organization), and record access depends on ownership plus hierarchy plus sharing. Practice with a concrete scenario: a seller in Business Unit A needs to see a record owned by a seller in Business Unit B, and trace which layer must change.
Answering questions about Dataverse as if it were a traditional relational database with no platform behaviors, ignoring that it provides built-in auditing, business rules, calculated and rollup fields, and security at the platform level.
Candidates with SQL backgrounds focus on tables, columns, and relationships and overlook the no-code and platform features that the exam treats as core value.
What to do instead
For each Dataverse capability question, ask 'is there a built-in platform feature for this?' before choosing a custom-code answer. Drill the difference between a business rule, a calculated field, a rollup field, and a workflow, since exam items test which one fits a given requirement.
Describing the business value of Dynamics 365 in vague marketing terms ('improves efficiency', 'better insights') rather than tying a capability to a specific outcome such as shorter case resolution, higher forecast accuracy, or reduced travel time for field technicians.
Value questions feel like soft questions, so candidates memorize slogans instead of mapping each app's capability to the operational metric it moves.
What to do instead
For each app, prepare one capability-to-outcome pair with a measurable metric (for example, unified customer timeline in Customer Service reduces average handle time because agents avoid switching systems). Use the outcome, not the adjective, when selecting an answer.
Assuming Dynamics 365 Customer Engagement includes finance and supply chain functionality, or that Finance and Supply Chain Management are part of the same app family and share the same data model.
Microsoft groups many products under the Dynamics 365 brand, and candidates who have seen the full product list blur the ERP apps with the customer engagement apps.
What to do instead
Draw a hard line: customer engagement apps focus on sales, service, field service, customer insights, and project-based customer work, while finance and supply chain are separate ERP apps. When a question mentions general ledger, inventory valuation, or procurement, it is outside the customer engagement scope being tested.
Confusing Customer Insights (the customer data platform used to unify and enrich customer profiles) with the customer engagement apps, or with the older marketing app, and then attributing segmentation and journey features to Sales or Service.
The Customer Insights name has been applied to more than one offering over time, and the boundaries between marketing, insights, and service are easy to blur.
What to do instead
Anchor on purpose: Customer Insights unifies and enriches data to create a single customer view and supports segments and journeys; Sales manages pipeline; Customer Service manages cases. When a question is about profile unification or audience segmentation, choose the insights offering.
Treating Power Platform components (Power BI, Power Automate, Power Apps, Copilot Studio) as unrelated to Dynamics 365, and failing questions about how they extend customer engagement apps.
Candidates study Dynamics 365 in isolation and do not connect the embedded analytics, flows, and custom apps that the exam expects them to recognize as part of the value story.
What to do instead
Map each component to a Dynamics 365 use: Power BI for embedded dashboards and reporting, Power Automate for triggers and approvals on records, Power Apps for custom model-driven or canvas apps on Dataverse, Copilot Studio for conversational agents. Learn one concrete example per mapping.
Confusing sales process concepts such as leads, opportunities, quotes, orders, and invoices, and describing the pipeline stages or the lead-to-opportunity qualification step incorrectly.
The records look similar and the transition points are specific; candidates who have not walked the process end to end guess at where qualification happens or when a quote becomes an order.
What to do instead
Trace the flow explicitly: lead captured, qualified into account, contact, and opportunity, opportunity progressed through business process flow stages, quote created and activated, order generated from a won quote, invoice generated from the order. Rehearse this chain until the order of records is automatic.
Skipping hands-on exploration and relying only on reading, so questions about where a feature lives (for example where to configure a business process flow, an entitlement, or a queue) are answered from memory of marketing pages rather than from having used the interface.
The exam tests familiarity with app navigation and configuration surfaces, and reading alone does not build that spatial memory.
What to do instead
Use a free trial environment to walk through each app: create a lead and qualify it, create a case and route it through a queue, build a simple business process flow, and add a Power BI dashboard. Note the navigation path for each action in your own words.