MB 600: Microsoft Dynamics 365 + Power Platform Solution Architect – Revision Guide

I am currently preparing to take the Microsoft Dynamics 365 + Power Platform Solution Architect certification. Or “MB 600” for short!

As I prepare I plan to write revision notes that I will publish. In this post you will find a collection of links to those posts.

I do try and group my revision guides into posts that directly relate back to the skills measured statements. And I have tried to take that approach with this exam …. but I did find a lot of cross-over between topics. Additionally some of the topics in my revision haven’t always fitted neatly into one particular heading. So I will do my best to create logical groupings for the information I’ve included. BUT if I document some topics in the “wrong area”, please don’t shoot me!!

Additionally, I don’t (yet) know how technical the questions in the MB 600 exam will be. (These are my revision notes … I haven’t taken the exam yet!) I am going to assume anyone preparing for the exam already has a pretty good understanding of the Power Platform from a technical point of view. Therefore most of my  notes will focus on the role of the Solution Architect, how we should capture requirements, how we should approach designing solutions etc etc. Rather than technically how these things are achieved.

Depending on your level of experience you may therefore want to also review various technical aspects of the Power Platform, examples being how security works, how we define entities, how we integrate with external systems and much more. If you read the skills measured statement carefully I believe there is a significant amount of implied knowledge. For example, a phrase like “Identify technical requirements” implies we may need an appreciation of the technologies which might be leveraged to deliver these requirements.


The Solution Architect’s Role

Project Life Cycle

Perform solution envisioning and requirement analysis
Initiate solution planning Evaluate business requirements

Identify solution components

Identify and estimate migration effort

Identify organization information and metrics Identify and document an organization’s business processes

Assess organization’s risk factors

Identify existing solutions and systems Evaluate organization enterprise architecture

Identify data sources to be included in the solution

Define usage and quality of legacy data

Identify desired high-level organizational business processes

Capture requirements
Refine high level requirement

Identify functional requirements

Identify technical requirements

Confirm requirements meet organization’s goals

Perform fit/gap analysis Determine feasibility of requirements

Evaluate Dynamics 365 apps and AppSource options to solve requirements

Address functional gaps through alternate solutions

Determine scope

Revision Guides

Initiate solution planning

Identify organization information and metrics

Identify existing solutions and systems

Capture requirements

Perform fit/gap analysis

Architect a solution
Lead design process
Design solution topology

Design customizations for Dynamics 365 apps or AppSource apps

Validate and/or design user experience prototypes

Identify opportunities for component reuse

Communicate system design visually

Design Application Lifecycle Management

Design data migration strategy

Partition features into apps

Design visualization strategy

Design for upgradeability

Create functional design documents

Design data and security model
Design entities and fields

Design reference and configuration data

Design complex scenarios

Design business unit team structure

Design security roles

Design field security

Design integrations
Design collaboration integration

Design Dynamics 365 integration

Design internal system integration

Design third-party integration

Design authentication strategy

Design business continuity strategy

Design integrations with Microsoft Azure

Revision Guides

Lead design process  – Part One

Lead design process  – Part Two

Lead design process  – Part Three

Design data and security model  – Part One

Design data and security model  – Part Two

Design integrations

Implement the solution
Validate the solution design
Evaluate detail designs and implementation

Validate security

Support Go-Live
Facilitate risk reduction of performance items

Troubleshoot data migration

Review and advise in deployment planning

Review and advise with Go-Live Assessment

Revision Guides

Validate the solution design

Support Go-Live

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s