As a candidate for this exam, you design, develop, test, secure, and troubleshoot Microsoft Power Platform solutions. You implement components of a solution that include:
- Application enhancements
- Custom user experiences
- System integrations
- Data conversions
- Custom process automation
You must have:
- A strong applied knowledge of Microsoft Power Platform services, including in-depth understanding of its capabilities, boundaries, and constraints.
- A basic understanding of authentication, security, and application lifecycle management (ALM) practices for the Microsoft Power Platform.
As a candidate, you should have development experience that includes Microsoft Power Platform services, JavaScript, JSON, TypeScript, C#, HTML, RESTful Web APIs, and Microsoft Azure.
Microsoft Power Platform Developer Exam Summary:
| Exam Name | Microsoft Certified - Power Platform Developer Associate |
| Exam Code | PL-400 |
| Exam Price | $165 (USD) |
| Exam Price | 120 mins |
| Number of Questions | 40-60 |
| Passing Score | 700 / 1000 |
| Books / Training | PL-400T00-A: Microsoft Power Platform Developer |
| Sample Questions | Microsoft Power Platform Developer Sample Questions |
| Practice Exam | Microsoft PL-400 Certification Practice Exam |
Microsoft PL-400 Exam Syllabus Topics:
| Topic | Details |
| Create a technical design (10-15%) | |
| Design technical architecture | - Design the technical architecture for a solution - 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 Power Automate cloud flows - Determine when to use serverless computing, plug-ins, or Power Automate - Determine when to use standard tables, virtual tables, or connectors - Describe security capabilities of the Microsoft Power Platform including data loss prevention (DLP) policies, security roles, teams, business units and row sharing |
| Design solution components | - Design a Microsoft Dataverse data model - Design Power Apps reusable components including canvas components, code components, and client scripting - Design custom connectors - Design Dataverse code components including plug-ins and Custom APIs - Design automations including Power Automate cloud flows and real-time workflows - Design Azure inbound and outbound integrations |
| Configure Microsoft Dataverse (15-20%) | |
| Configure Microsoft Power Platform to support development | - Troubleshoot operational security issues found in testing - Configure Dataverse security roles and column-level security profiles - Configure business units and teams - Manage Microsoft Power Platform environments for development |
| Configure tables | - Configure table options - Configure columns - Configure relationships - Configure business rules |
| Implement application lifecycle management (ALM) | - Create solutions and manage solution components - Import and export solutions - Manage solution dependencies - Create and use environment variables - Describe the difference between unmanaged and managed solutions - Manage solution layers |
| Create and configure Power Apps (10-15%) | |
| Create model-driven apps | - Create and Configure a model-driven app - Configure forms - Configure views - Configure commands and buttons using Power Fx - Configure commands and buttons using JavaScript |
| Create canvas apps | - Create and configure a canvas app or a custom page - Implement complex Power Fx formulas - Build reusable component libraries - Test an app by using Power Apps Test Studio - Utilize Power Automate cloud flows to implement business logic from a canvas app |
| Manage and troubleshoot apps | - Troubleshoot canvas and model-driven app issues by using Monitor and other browser-based debugging tools - Identify and resolve connector and API errors - Optimize canvas app performance including pre-loading data and query delegation - Optimize model-driven app performance including forms and views |
| Extend the user experience (10-15%) | |
| Apply business logic using client scripting | - Create JavaScript code that targets the Client API object model - Describe event handler registration options - Create client scripting that targets the Dataverse Web API - Describe the client API object model - Determine when to use business rules or client scripting |
| Create a Power Apps Component Framework (PCF) code component | - Describe the code component lifecycle - Initialize a new code component - Configure a code component manifest - Implement component interfaces - Package, deploy, and consume a component - Configure and use Device, Utility, and Web API features in component logic |
| Extend the platform (35-40%) | |
| Create a Dataverse plug-in | - Describe the plug-in execution pipeline - Describe the plug-in execution context - Develop a plug-in that implements business logic - Implement Pre Images and Post Images to support plug-in logic - Perform operations in plug-ins by using the Organization service - Optimize plug-in performance - Configure a Dataverse Custom API message - Register custom assemblies by using the Plug-in Registration Tool - Develop a plug-in that implements a Custom API |
| Create custom connectors | - Create an Open API definition for a REST API - Configure API security - Use policy templates to modify connector behavior at runtime - Import definitions from existing APIs including Open API definitions, Azure services, and GitHub - Create a custom connector for an Azure service - Create an Azure Function to be used in a custom connector - Extend an Open API definition for a custom connector |
| Use platform APIs | - Perform operations with the Dataverse Web API - Perform operations with the Organization service - Implement API limit retry policies - Optimize for performance, concurrency, transactions, and batching - Perform authentication by using OAuth |
| Process workloads by using Azure Functions | - Process long-running operations by using Azure Functions - Configure scheduled and event-driven triggers in Azure Functions - Authenticate to Microsoft Power Platform by using managed identities |
| Configure Power Automate cloud flows | - Create and manage cloud flows - Configure flow steps to use Dataverse connector actions and triggers - Implement complex expressions in flow steps - Manage sensitive input and output parameters - Implement Azure Key Vault and Microsoft Entra ID service principals - Describe flow control actions including error handling - Add a cloud flow step to a business process flow - Configure trigger filter and retry policies |
| Develop Integrations (5-10%) | |
| Publish and consume Dataverse events | - Publish a Dataverse event by using the IServiceEndpointNotificationService - Publish a Dataverse event by using the Plug-in Registration Tool - Register service endpoints including webhooks, Azure Service Bus, and Azure Event Hub - Describe options for listening to Dataverse events |
| Implement data synchronization with Dataverse | - Describe synchronizing data by using change tracking - Read table change records by using platform APIs - Create and use alternate keys - Use the UpsertRequest message to synchronize data |
Posts
0 comments:
Post a Comment