MB-700 Quick Reference: Every Number You Need to Memorise

ERP & business apps29 October 2026·8 min read·PractiseExam

MB-700 Quick Reference: Every Number You Need to Memorise

If you are sitting the Microsoft Dynamics 365 Finance and Operations Apps Solution Architect (MB-700) exam, you already know it is not a “click-through” certification. This is a scenario-heavy, architecture-level test that demands you recall specific percentages, lifecycle stages, and design trade-offs under time pressure. The good news: the exam tests a finite set of numbers—pass marks, domain weights, and a few critical thresholds—that, once memorised, give you a massive advantage.

This quick-reference guide distils the official exam blueprint into the only numbers that matter, plus the five to eight must-know concepts per major domain. Use this as your final revision sheet, not your first study guide. Related reading: Choosing Between PL-600 and MB-700: The Deciding Factors. For a deeper dive, check out AZ-400 Quick Reference: Every Number You Need to Memorise.

Exam Facts and Critical Numbers

Before you dive into domains, lock these baseline facts into memory. Microsoft does not publish the exact number of questions, but the following are stable across recent exam versions:

Exam code: MB-700
Number of questions: 40–60 (typically 50)
Passing score: 700 out of 1000 – This is a scaled score, not a percentage. You do not need 70% of questions correct; you need a scaled 700. In practice, most candidates report needing roughly 60–65% raw correct answers to pass.
Duration: 180 minutes (3 hours) – includes time for review and any case study sections.
Question types: Multiple choice, drag-and-drop, hot area, and case studies (usually 2–3 case studies with 5–8 questions each).
Exam delivery: Pearson VUE, online proctored or in-centre.
Language: English, Japanese, Chinese (Simplified), Korean, German, French, Spanish, Portuguese (Brazil).
Validity: 1 year from date of passing – you must renew annually via the Microsoft Learn renewal assessment (free, open-book, 30 minutes).

The scaled score means easy questions are worth less, hard questions worth more. Do not waste time on a single hard question if you can bank two easy ones.

Domain Weights: Where to Spend Your Study Time

The MB-700 blueprint splits into four domains. The percentages are the official weights from Microsoft’s exam page. Memorise these precisely: If this interests you, DP-203 Quick Reference: Every Number You Need to Memorise goes into more detail.

Once you have these weights, use free study plans and readiness checks to turn them into a balanced week-by-week schedule and a quick review of weak topics.

Domain 1: Architect a solution (25–30%)
Domain 2: Implement a solution (25–30%)
Domain 3: Test and deploy a solution (15–20%)
Domain 4: Manage and maintain a solution (15–20%)

Key takeaway: Domains 1 and 2 together account for 50–60% of your score. If you are short on time, master those two. Domains 3 and 4 are smaller but still worth 30–40% combined—you cannot skip them, but you can prioritise. Our post on The Hardest Domain on MB-700, Broken Down covers this further.

Domain 1: Architect a Solution (25–30%)

This domain is about requirements gathering, fit-gap analysis, and choosing the right modules and integrations. The exam loves to test your ability to say “no” to customisation when standard functionality works.

Must-Know Concepts

Fit-gap analysis process: Identify business requirements, map to standard Dynamics 365 F&O features, then classify gaps as “fit,” “workaround,” or “customisation.” The default answer is always use standard functionality first.
Requirement traceability matrix: Every requirement must map to a functional design, a test case, and a deployment item. The exam will give you a requirement and ask which test case validates it.
Module selection logic: Know which module handles which business process (e.g., Inventory Management for stock, Procurement and Sourcing for purchase orders, Accounts Payable for vendor invoices). A common trap is confusing Production control with Inventory management for BOMs.
Integration strategy patterns: Choose between batch data (ETL), real-time (REST/OData), and file-based (SFTP). For high-volume, low-latency, use batch; for immediate validation, use real-time.
Data entities vs. tables: Always use data entities for integrations and imports, never direct table access. The exam will present a scenario where a developer wants to write to a table directly—that is a trap.
Licensing and environment sizing: You need to know that sandbox environments are for development and testing, production is for live use, and tier-1 (single-box) is for demo, tier-2 (standard acceptance) is for UAT, and tier-3+ are for performance testing.
Lifecycle Services (LCS) project structure: Know that LCS is the central hub for all environments, code deployment, and service requests. A solution architect must decide the LCS project type (implementation, partner, or internal).

Common Traps

Choosing a custom integration when an OData endpoint already exists.
Picking a tier-1 environment for performance testing—always tier-3+.
Forgetting that the Default Data project in LCS is for initial data migration, not ongoing sync.

Domain 2: Implement a Solution (25–30%)

This is where you apply the architecture. The exam focuses on data migration, security, and configuration of core modules. Expect many “what should you do first?” questions. See also PSPO I Quick Reference: Every Number You Need to Memorise for a complementary perspective.

Must-Know Concepts

Data migration lifecycle: Extract → Transform → Load → Validate. The exam will ask about data entities, data packages, and export/import via LCS. Always use Data Management workspace, never SQL scripts.
Number sequences: Know that number sequences are set up per company, per reference (e.g., invoice, purchase order). A common trap is assigning the same number sequence to two companies—this causes conflicts.
Security roles and duties: Dynamics 365 F&O uses roles → duties → privileges → permissions. You assign roles to users, not individual duties. The exam tests that you must create a custom role when the standard roles do not match, but you must copy an existing role first.
Financial dimensions: You must know the difference between account structures and advanced rule structures. Account structures define the segment order and valid combinations; advanced rules allow conditional segment combinations based on dimension values.
Workspaces and personalisation: Users can personalise their own workspaces, but a solution architect must decide whether to deploy saved views to all users via code or use personalisation for individuals.
Feature management: Every new feature is disabled by default. You must enable features via Feature management workspace. The exam will ask which feature to enable for a specific business requirement (e.g., “Global inventory accounting”).
Electronic reporting (ER) vs. SSRS: Use ER for regulatory and electronic documents (e.g., XML, Excel), use SSRS for standard operational reports (e.g., invoices, statements). A trap is using SSRS for a new regulatory requirement—that should be ER.

Common Traps

Forgetting that data packages must be imported in the correct order (e.g., customers before sales orders).
Assuming that changing a number sequence after transactions exist is safe—it is not; it causes gaps or duplicates.
Assigning a user directly to a duty instead of a role—this is not allowed.

Domain 3: Test and Deploy a Solution (15–20%)

This domain is about the testing strategy and moving code from development to production. The exam loves to test your knowledge of the release pipeline and regression testing.

Must-Know Concepts

Test types: Unit (developer), integration (data flow), regression (existing functionality), UAT (user acceptance), and performance (load). The solution architect is responsible for the test strategy, not for writing all tests.
Regression testing suite: You must know that Regression Suite Automation Tool (RSAT) is the standard tool for automating regression tests in F&O. The exam will ask which tool to use for automated UI testing—the answer is RSAT, not Selenium.
Code promotion flow: Development environment → Build environment → Sandbox (tier-2) → Production. You must use LCS to deploy packages; you cannot deploy directly from Visual Studio to production.
Service updates vs. quality updates: Service updates are feature updates (monthly), quality updates are hotfixes (weekly). You must plan for a minimum of 8 service updates per year for F&O (Microsoft releases monthly, but you can skip some).
Downtime and cutover: The cutover plan must include a data freeze, final data migration, and a rollback strategy. The exam will ask what to do if a cutover fails—the answer is to restore from the last backup and re-run the migration.
Environment failure handling: Know that you can refresh a sandbox from production (a full copy) or from another sandbox. You cannot refresh production from a sandbox.

Common Traps

Choosing “run a manual test” when RSAT is available—automation is always preferred.
Confusing service update (new features) with quality update (bug fixes).
Forgetting that code signing and package validation happen in LCS, not in the build machine.

Domain 4: Manage and Maintain a Solution (15–20%)

The final domain covers post-go-live operations, monitoring, and continuous improvement. This is where many architects lose marks because they assume it is “just support.”

Must-Know Concepts

Lifecycle Services (LCS) monitoring tools: Use Environment monitoring for health, Telemetry for performance, and Issue search for known problems. The exam will present a symptom (e.g., slow batch job) and ask which LCS tool to use first—the answer is Environment monitoring or Telemetry, not opening a support ticket.
Batch job management: You must know that batch jobs are grouped into batch groups, and each group is assigned to a server (or cluster). A common trap is running all batch jobs on the same server—this causes bottlenecks; you must create separate groups for critical jobs.
Data retention and archiving: The Data archival feature in F&O allows you to move historical transactions to a separate database. The exam will ask about reducing the main database size—the answer is archival, not deletion.
System administration tasks: Know the periodic tasks (e.g., “Update currency exchange rates,” “Close accounting period”) and their frequency. A trap is scheduling a monthly task as a daily batch job.
Performance diagnostics: Use Performance timer and Trace parser to identify slow queries. The exam will ask about a slow form—you should use the Trace parser to analyse the execution.
Support and servicing: You must know the support lifecycle for F&O—Microsoft provides mainstream support for 5 years after release, then extended support for 5 more. For a solution architect, you need to plan for upgrades within the lifecycle.
Security and compliance: Periodic security audits and user access reviews are mandatory. The exam will ask who is responsible for reviewing user access—the answer is the customer’s IT team, not Microsoft.

Common Traps

Using batch job history to find a failed job

Turn theory into exam-ready confidence with Microsoft Dynamics 365: Finance and Operations Apps Solution Architect (MB-700) mock test questions that push you beyond textbook knowledge.

MicrosoftMB-700cheat-sheetMS Business Apps

All posts Sit a full-length mock