Exam MB-400 Microsoft Power Apps + Dynamics 365 Developer

The content of this exam will be updated on May 22, 2020. Please download the skills measured document below to see what will be changing.

Candidates for this exam are Developers who work with Microsoft Power Apps model-driven apps in Dynamics 365 to design, develop, secure, and extend a Dynamics 365 implementation. Candidates implement components of a solution that include application enhancements, custom user experience, system integrations, data conversions, custom process automation, and custom visualizations.

Candidates must have strong applied knowledge of Power Apps model-driven apps in Dynamics 365, including in-depth understanding of customization, configuration, integration, and extensibility, as well as boundaries and constraints. Candidates should have a basic understanding of DevOps practices for Power Apps model-driven apps in Dynamics 365. Candidates must expose, store, and report on data.

Candidates should have development experience that includes JavaScript, TypeScript, C#, HTML, .NET, Microsoft Azure, Office 365, RESTful Web Services, ASP.NET, and Power BI.

Skills measured
The content of this exam will be updated on May 22, 2020. Please download the skills measured document below to see what will be changing.
Create a technical design (10-15%)
Configure Common Data Service (CDS) (15-20%)
Create and configure Power Apps (10-15%)
Configure business process automation (10-15%)
Extend the user experience (15-20%)
Extend the platform (15-20%)
Develop integrations (10-15%)

Audience Profile Candidates for this exam are developers who work with Microsoft Power Apps model-driven apps in Dynamics 365 to design, develop, secure, and extend a Dynamics 365 implementation. Candidates implement components of a solution that include application enhancements, custom user experience, system integrations, data conversions, custom process automation, and custom visualizations. Candidates must have strong applied knowledge of Power Apps model-driven apps in Dynamics 365, including in-depth understanding of customization, configuration, integration, and extensibility, as well as boundaries and constraints. Candidates should have a basic understanding of DevOps practices for Power Apps model-driven apps in Dynamics 365. Candidates must expose, store, and report on data. Candidates should have development experience that includes JavaScript, TypeScript, C#, HTML, .NET, Microsoft Azure, Office 365, RESTful Web Services, ASP.NET, and Power BI. Skills Measured

NOTE: The bullets that appear below each of the skills measured are intended to illustrate how we are assessing that skill. This list is not definitive or exhaustive.

NOTE: In most cases, exams do NOT cover preview features, and some features will only be added to an exam when they are GA (General Availability).

Create a Technical Design (10-15%)
Validate requirements and design technical architecture
 design and validate technical architecture
 design authentication and authorization strategy
 determine whether requirements can be met with out-of-the-box functionality
 determine when to use Logic Apps versus Microsoft Flow
 determine when to use serverless computing vs. plug-ins
 determine when to build a virtual entity data source provider vs. when to use connectors Create a data model
 design a data model Configure Common Data Service (CDS) (

15-20%) Configure security to support development
 troubleshoot operational security issues
 create or update security roles and field-level security profiles Implement entities and fields
 configure entities
 configure fields
 configure relationships Create and maintain solutions
 configure solutions
 import and export solutions
 manage solution dependencies Create and Configure Power Apps

(10-15%) Create model-driven apps
 configure a model-driven app
 configure forms
 configure views
 configure visualizations Create Canvas Apps
 configure a Canvas App
 develop complex expressions Configure business process automation

(10-15%) Configure Microsoft Flow
 configure a Flow
 configure actions to use CDS connectors
 develop complex expressions Implement processes
 create and configure business process flows
 create and configure business rules

Extend the user experience

(15-20%) Apply business logic using client scripting
 configure supporting components
 create JavaScript or Typescript code
 register an event handler
 use the Web API from client scripting

Create a Power Apps Component Framework (PCF) component
 initialize a new PCF component
 configure a PCF component manifest
 implement the component interfaces
 package, deploy, and consume the component
 use Web API device capabilities and other component framework services

Create a command button function
 create the command function
 design command button triggers, rules, and actions
 edit the command bar using the Ribbon Workbench
 modify the form JavaScript library dependencies

Extend the platform (15-20%)


Create a plug-in
 debug and troubleshoot a plug-in
 develop a plug-in
 use the Organization Service
 optimize plug-ins for performance
 register custom assemblies by using the Plug-in Registration Tool
 create custom actions

Configure custom connectors for Power Apps and Flow
 create a definition for the API
 configure API security
 use policy templates

Use platform APIs
 interact with data and processes using the Web API
 optimize for performance, concurrency, transactions, and batching
 perform discovery using the Web API
 perform entity metadata operations with the Web API
 use OAuth with the platform APIs

Develop Integrations (10-15%)
Publish and consume events
 publish an event by using the API
 publish an event by using the Plug-in Registration Tool
 register a webhook
 create an Azure event listener application

Implement data synchronization
 configure and use entity change tracking
 configure the data export service to integrate with Azure SQL Database
 create and use alternate keys

The exam guide below shows the changes that will be implemented on May 22, 2020. Audience Profile Candidates for this exam are developers who work with Microsoft Power Apps model-driven apps in Dynamics 365 to design, develop, secure, and extend a Dynamics 365 implementation. Candidates implement components of a solution that include application enhancements, custom user experience, system integrations, data conversions, custom process automation, and custom visualizations. Candidates must have strong applied knowledge of Power Apps model-driven apps in Dynamics 365, including in-depth understanding of customization, configuration, integration, and extensibility, as well as boundaries and constraints. Candidates should have a basic understanding of DevOps practices for Power Apps model-driven apps in Dynamics 365. Candidates must expose, store, and report on data. Candidates should have development experience that includes JavaScript, TypeScript, C#, HTML, .NET, Microsoft Azure, Office 365, RESTful Web Services, ASP.NET, and Power BI.

Skills Measured NOTE:
The bullets that appear below each of the skills measured are intended to illustrate how we are assessing that skill. This list is not definitive or exhaustive.
NOTE: In most cases, exams do
NOT cover preview features, and some features will only be added to an exam when they are GA (General Availability). Create a Technical Design

(10-15%) Validate requirements and design technical architecture
 design and validate technical architecture
 design authentication and authorization strategy
 determine whether requirements can be met with out-of-the-box functionality
 determine when to use Logic Apps versus Microsoft FlowPower Automate flows
 determine when to use serverless computing vs. plug-ins
 determine when to build a virtual entity data source provider vs. when to use connectors Create a data model
 design a data model Configure Common Data Service (CDS)

(15-20%) Configure security to support development
 troubleshoot operational security issues
 create or update security roles and field-level security profiles Implement entities and fields
 configure entities
 configure fields
 configure relationships Create and maintain solutions
 configure solutions
 import and export solutions
 manage solution dependencies Create and Configure Power Apps

(10-15%) Create model-driven apps
 configure a model-driven app
 configure forms
 configure views
 configure visualizations Create Canvas Apps
 configure a Canvas App
 develop complex expressions Configure business process automation

(10-15%) Configure Microsoft FlowPower Automate
 configure a Flow
 configure actions to use CDS Common Data Service connectors
 develop complex expressions Implement processes
 create and configure business process flows
 create and configure business rules

Extend the user experience (15-20%)
Apply business logic using client scripting

 configure supporting components
 create JavaScript or Typescript code
 register an event handler
 use the Web API from client scripting

Create a Power Apps Component Framework (PCF) component
 initialize a new PCF component
 configure a PCF component manifest
 implement the component interfaces
 package, deploy, and consume the component
 use Web API device capabilities and other component framework services

Create a command button function
 create the command function
 design command button triggers, rules, and actions
 edit the command bar using the Ribbon Workbench
 modify the form JavaScript library dependencies

Extend the platform (15-20%)
Create a plug-in
 debug and troubleshoot a plug-in
 develop a plug-in
 use the Organization Service global Discovery Service endpoint
 optimize plug-ins for performance
 register custom assemblies by using the Plug-in Registration Tool
 create custom actions

Configure custom connectors for Power Apps and Flow
 create a definition for the API
 configure API security
 use policy templates

Use platform APIs
 interact with data and processes using the Web API
 optimize for performance, concurrency, transactions, and batching
 perform discovery using the Web API
 perform entity metadata operations with the Web API
 use OAuth with the platform APIs

Develop Integrations (10-15%)
Publish and consume events
 publish an event by using the API
 publish an event by using the Plug-in Registration Tool
 register a webhook
 create an Azure event listener application

Implement data synchronization
 configure and use entity change tracking
 configure the data export service to integrate with Azure SQL Database
 create and use alternate keys

QUESTION 1
You need to replace the bicycle inspection forms.
Which two solutions should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

A. a canvas app that guides the technician through the inspection
B. a logic app that guides the technician through the inspection
C. a flow that maps inspection data to Dynamics 365 for Field Service
D. a model-driven app based on customer service entities

Correct Answer: C,D


QUESTION 2
Note: This question is part of a series of questions that present the same scenario. Each question in
the series contains a unique solution that might meet the stated goals. Some question sets might have
more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.

A Common Data Service (CDS) environment has two custom entities named Building code and Work item.
Building code has a code date custom field and Work item has an elapsed time custom field. Construction
workers use a consolidated custom form with data from both entities to fill.in their daily work items.
A JavaScript library is used with these custom entities and fields to apply complex logic.
You need to ensure that the JavaScript library continues to function as originally designed if other developers
expand the environment.
Solution: In form properties of the consolidated form, add the JavaScript library in the events tab and add the
two custom fields to the dependent fields section of the non-event dependencies tab.
Does the solution meet the goal?

A. Yes
B. No

Correct Answer: B

QUESTION 3
Note: This question is part of a series of questions that present the same scenario. Each question in
the series contains a unique solution that might meet the stated goals. Some question sets might have
more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.

A Common Data Service (CDS) environment has two custom entities named Building code and Work item.
Building code has a code date custom field and Work item has an elapsed time custom field. Construction
workers use a consolidated custom form with data from both entities to fill.in their daily work items.
A JavaScript library is used with these custom entities and fields to apply complex logic.
You need to ensure that the JavaScript library continues to function as originally designed if other developers
expand the environment.
Solution: In the JavaScript library, add Building code with Code date and Work item with Elapsed time in the dependencies tab.
Does the solution meet the goal?

A. Yes
B. No

Correct Answer: A

Actualkey Microsoft Certified Power Apps MB-400 exam pdf, Certkingdom MB-400 PDF

MCTS Training, MCITP Trainnig

Best Microsoft Certified Power Apps MB-400 Certification, Microsoft Certified Power Apps MB-400 Training at certkingdom.com

Exam MB-400 Microsoft Power Apps + Dynamics 365 Developer
Scroll to top