nerdexam
Microsoft

PL-400 Real Exam Questions

Microsoft Power Platform Developer. Everything you need to prepare, practice, and pass.

242

Questions

5

Exam Domains

Included

Explanations

Ready to practice?

242+ questions with detailed explanations

Start Now

From $49.99 USD · refund policy applies

Browse all 242 PL-400 questions

Certification Overview

The exam tests your ability to architect and extend the Dataverse platform (Microsoft's cloud data engine), secure enterprise solutions using Azure AD and advanced security controls, develop Power Apps across model-driven and canvas patterns, automate business processes, and integrate Power Platform with external systems. You must understand both the low-code/no-code Power Apps layer and the deeper development aspects (APIs, plugins, authentication).

What This Certification Proves

The PL-400 validates expertise in designing and developing solutions on the Microsoft Power Platform, with emphasis on Power Apps, Dataverse, and enterprise integrations. This certification proves you can architect scalable solutions, secure data effectively, and extend the platform to meet complex business requirements—skills essential for organizations modernizing their business applications.

Who Should Take This Exam

Developers with 1-3+ years of experience in Power Platform or transitioning from other Microsoft technologies (C#, .NET, or Azure). Candidates should have hands-on experience building Power Apps or Power Platform solutions, plus foundational knowledge of cloud platforms and API-driven architectures.

Topic Breakdown

5 domains covering 11 questions

DomainQuestionsWeight
Develop Integrations655%
Implement Power Apps Improvements218%
Configure Business Process Automation19%
Configure Microsoft Dataverse19%
Extend The User Experience19%

Study Plans

Choose a study plan that matches your schedule and experience level

30 Days

Intensive Sprint

Week 1-2

  • Master fundamentals: Develop Integrations
  • Read Microsoft official documentation
  • Complete 9 questions daily

Week 3

  • Deep dive: Implement Power Apps Improvements
  • Review weak areas from results
  • Take 2 full-length exams

Week 4

  • Review all flagged questions
  • Timed exams to build stamina
  • Final revision of key concepts

60 Days

Balanced Approach

Week 1-2

  • Survey all exam domains
  • Set up study environment
  • Begin with foundational topics

Week 3-4

  • Focus: Develop Integrations
  • Focus: Implement Power Apps Improvements
  • 5 questions daily

Week 5-6

  • Focus: Configure Business Process Automation
  • Hands-on labs if applicable
  • Review explanations for wrong answers

Week 7-8

  • Complete all 242 questions
  • Identify and eliminate weak areas
  • Take 3 full-length timed tests

90 Days

Comprehensive Study

Month 1

  • Learn all exam domains at a comfortable pace
  • Build strong foundational knowledge
  • 3 questions daily

Month 2

  • Deep dive into each domain
  • Hands-on practice and labs
  • Take weekly timed exams

Month 3

  • Work through all 242 questions
  • Identify and eliminate weak areas
  • Take 3 full-length timed exams

PL-400-Specific Tips

  • Master Dataverse Web API and Discovery Service—these are heavily tested and critical for integration scenarios; practice real API calls and filtering syntax
  • Deep-dive into Azure AD authentication patterns and Conditional Access policies; understand how app registration and OAuth flows work in Power Platform context
  • Build model-driven apps from scratch and understand the metadata layer; focus on form logic, business rules, and plugin architecture for extensibility
  • Study business process flows thoroughly—including stage transitions, data steps, and security filtering within process flows
  • Practice hands-on with Power Apps CLI and ALM scenarios; understand solution management, versioning, and deployment across environments
  • Focus on Dataverse security model: field-level security, row-level security (sharing + filtering), and privilege inheritance—this is nuanced and frequently tested
  • Work with real integrations: Dataverse to external systems via Web API, webhooks, and plugins; understand when to use each integration pattern

Relevant Career Roles

Power Platform DeveloperPower Apps Developer / EngineerDataverse Solutions ArchitectPower Platform Integration EngineerBusiness Applications DeveloperMicrosoft Cloud Solutions Developer

Sample Questions

Try 5 free questions from the PL-400 question bank

Q1

Case Study 8 - City Power & Light Background City Power & Light is an energy and utilities company that has offices in Europe. The company subsidizes home improvements for domestic customers, to improve energy efficiency and to meet environmental commitments. The company also distributes and generates electricity for domestic and commercial customers. The company has 2,000 employees in multiple offices and in work- from-home locations. City Power & Light uses a team of schedulers, assessors, field engineers, and customer support agents for home improvements in a program named Get Energy Fit. Current Environment Get Energy Fit Program City Power & Light uses the following to manage the Get Energy Fit program: - The company uses a Microsoft Excel spreadsheet named Planning Hub on Microsoft SharePoint Online to store information about customer appointments, customer details, and customer eligibility in the program. - The company records sensitive customer information that includes the document identification numbers and the customer's financial information. - The company uses an assessor to verify customer eligibility in the program and to perform a suitability assessment. The assessor completes the suitability assessment by using a paper and clipboard at the customer property and enters the data to the Planning Hub after the assessment is completed. The assessor also uploads photographs to an on-premises document library. The assessor completes the eligibility assessment by using an application written in React. - Schedulers use Microsoft Outlook to schedule engineers and assessors for home improvement appointments. About 200 appointments are scheduled daily. - Employees for the company submit funding claims on behalf of the customer by uploading evidence and compliance checks information to an application named the Claim Submission Portal. Technical Environment - Schedulers use Windows 11 desktop and laptop computers with the latest version of Microsoft Edge. - Assessors use iOS and Android tablet devices. - The Claim Submission Portal uses REST-based APIs for all operations and a dedicated testing environment. Authentication to the API is provided by using the following example header key and value pair: o Authentication: 2C8D41431415E429C7FC7A74D8315 - The company uses Microsoft Azure for hosting multiple applications. Requirements Overview City Power & Light plans to implement Microsoft Power Platform to improve the customer experience and increase delivery for the Get Energy Fit program. Business Requirements - Only team leaders and senior managers should have access to read personally identifiable information (PII). - All development changes must be tested in a separate environment. - The company requires out-of-the-box solutions, when possible. - Sensitive credentials, such as user passwords and API secrets, must be stored securely. - The Claim Submission Portal must allow citizen developers to create automated solutions. - Customer and appointment information must be accessible to all applications. Planning Hub Application The company is planning to replace the Planning Hub spreadsheet with a new application. The new application has the following requirements: - The application must support a component design that provides rapid changes requested by the schedulers. - The data model for the application must capture the following information: o Information about customers such as name, address, and other PII. o The data and time for an assessor's or engineer's appointment. Schedulers must be able to view all appointments without filters. o Records the details of the home improvements installed for the customer. o Contains all the information and evidence for submission to the Claim Submission Portal. - After an assessor uploads the funding application and all evidence after a home improvement has been complete, the company requires that the status of the application is set to Submit and should run the following: o Retrieve the details about the customer and the improvement installed. o Send an approval to a senior manager to review and approve in Microsoft Teams. o Upload the information to the API endpoint. o If the upload fails to complete, it should retry after a delay of 30 seconds up to three times. If an error occurs after three times, the application should send an email notification to the application support team. o Must record the status on the funding application. Suitability Assessment Tool The company plans to implement a new application named the Suitability Assessment Tool for the assessors. The new application has the following requirements: - Must integrate with Microsoft Power Platform. - Assessors must be able to complete the eligibility assessment by using the Suitability Assessment Tool. The assessors must be able to upload photographs to the on-premises file share. - Must be developed by using modular components that can be used by other applications. - Must be optimized for use on tablet devices. - All changes to the application must be completed in the Suitability Assessment Tool solution. Reporting The company has the following requirements for a reporting solution: - The data source for the reporting solution must support incremental refreshes. - The solution must report accurate data if an error occurs. Issues - A recent audit identified that all users can access the PII in the Planning Hub spreadsheet. - After a developer deploys a change to the production environment, a user reports information is loaded incorrectly to the test system when processing a funding application. - After deploying a change to the new eligibility assessment tool in the development environment, you observe that the changes do not appear in the development environment. - After removing a column from the Planning Hub application and deploying the changes to the production environment, you observe that the column is still present. - You deploy the customizations for the data model. Users report that the email address of the user who created the appointment is missing and that searches on the description information do not return any results. You need to resolve the funding application issue. Which component should you use?

Q2

Case Study 1 - Bellows Sports Background Bellows Sports is the region's newest, largest, and most complete sports complex. The company features baseball and soccer fields and two full-size hockey rinks. The complex provides coaching, recreational leagues, a pro shop, and state-of-the art customer and player amenities. The company is organized into the following divisions: Baseball Hockey Soccer Bellow Sports runs tournaments several times per year. Each tournament runs six weeks. Current environment Requirements Bellow Sports tracks players and events in Microsoft Excel workbooks and uses email to communicate with players, partners, and prospective customers. The company uses a proprietary cloud-based accounting system. The company relies on referrals from athletes for new business. Bellows uses a third-party marketing company to gather feedback and referrals from athletes. The third-party marketing company uploads a Microsoft Excel file containing lists of potential customers and players to the FTP site that Bellows Sports maintains. Tournaments Customer information is stored in the Accounts entity. Each tournament record must list the associated sales representative as the tournament owner. When team members create tournament records they must enter the start date for a tournament. The end date of the tournament must be automatically calculated. Registration form You must create a form to allow players to register for tournaments. The registration form must meet the following requirements: Each division has tournaments that take place in specific locations. Users must be able to select the division for a tournament location. Information about upcoming tournaments must be pre-located into the registration form when the registration form loads. The form must include a custom button that sends an email confirmation to the player after the player registers. The button must not be visible until after the form is saved. Security The company identifies the following job roles: You must grant users the minimum permissions required to perform their job tasks. Data automation Customer name must be added to Dynamics 365 Finance automatically after it is entered. You must produce a report that details the number of registrations for a day and send the report as a PDF to the management team. You must implement mechanisms to handle all code-related errors. When a customer record is updated, the system must look up the account number for the customer in the accounting system. Referrals must be imported into the system as soon as they are available. Issues Apps The captions for the New and Save buttons do not render properly on the form. Interns can create apps but cannot interact with their own data. Portal The query for all registered users must return the data categorized by division. Queries must return only the Name and Sport fields. Queries return all fields. The query is as follows: Solution checker issues You run solution checker and observe Plug-in or workflow activity errors in the following code sets: Code The following code runs when the registration form loads. You must implement a mechanism to handle errors that occur in the code: You need to add the script for the registration form event handling. Which code segment should you use?

Q3

Case Study 7 - Northwind Traders Background Northwind Traders uses Microsoft Dynamics 365 Sales to manage its sales process. To better understand its customers, Northwind Traders invests in a team of researchers who gather data from multiple sources. The company stores the data it collects in a Microsoft Azure SQL Database. The company plans to use the data to enrich account records and make the sales team more effective. Current environment Environment - The company has three Microsoft Power Platform environments with Dynamics 365 Sales installed. The environments are named development, test, and production. - Each environment has an application user that can be used for integrations. - The company must use solutions to perform all customization and configuration deployment. Data - Researchers are responsible for creating account records. - Researchers have permissions on the Account table to create records, read all records, and update records they own. - A synchronous plug-in runs when an account record is created and could reassign the record to a different user. - Users must access data as themselves to enforce security and audit changes. - A column named new_dataid is added to the Account table. The column uniquely identifies which data it should receive. - Researchers have researched only the top 20 percent of account records. Web API - The company creates an Azure Function to run a RESTful .NET Web API. - Data can be retrieved by placing a GET request to the URL https://dataservice- [ENVIRONMENTNAME].azurewebsites.net/enrich/[DATAID]. - [ENVIRONMENTNAME] is the name of the Microsoft Power Platform environment that requests the data. - [DATAID] is the new_dataid column in the Account table. • The Web API response will return a 200 response plus data if the DataId is found. Otherwise, a 404 response is returned. • Developers plan to create a custom connector from the Web API to make it accessible from Microsoft Power Platform. Requirements Custom connector - The Web API definition used to create the custom connector must be generated based on a low-code technology. - The URL used by the custom connector must incorporate the current environment name without hardcoding values. - Errors generated by the custom connector must not cause downstream processes to fail. - Text descriptions and field placeholder text that describe the use of the custom connector must appear for non-developers. Process - All account records must be updated with data from the Web API once automatically. - Only account records that contain a DataId should be updated by the Web API. - Researchers must create Power Automate flows to specify data analysis priority. - The researchers require a process that repurposes a set of identical steps of parameterized Microsoft Dataverse queries from a Power Automate flow for use in other flows that have different parameters. The researchers want to avoid recreating the steps manually each time they create a flow to save time and avoid errors. Issues - A tester attempts to connect to the production instance of the Web API with a DataId that should return data. The tester receives an error stating that the remote name could not be resolved. - A missing component causes an error to occur when importing the solution that contains the Power Automate flow to update account records in a test environment. You need to ensure data returned from the Web API corresponds to the correct environment. What should you use?

Q4

You are implementing business logic for a model-driven app form by using multiple JavaScript web resources. The business logic, number of JavaScript files, and the columns that the business logic requires are expected to change frequently. Some form fields will not be visible. Occasionally, non- developers will also make changes to the form. You need to prevent columns referenced by the JavaScript from accidentally being removed from the form based. What should you do?

Q5

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 once 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. You are developing a model-driven app for a company. When you create a new Account record, you must automatically display a form to collect data that is needed to create a Contact record. The form must switch to the appropriate form layout based on the contact type. You open the Contact form by using JavaScript. You pass the contact type information to the form by using the Xrm.Navigation.openForm function. An OnLoad event handler in the Contact form processes the data and shows only the appropriate sections of the form for the given contact type. You need to configure the receiving form to accept the data parameter. Solution: In the form editor, add a web resource that sets formContext.data.attributes. Does the solution meet the goal?

Browse all 242 PL-400 questionsUnlock all 242 questions

PL-400 FAQ

Ready to pass PL-400?

Join thousands of professionals who passed their certification exam with NerdExam.

Get PL-400 Exam Questions