Microsoft PL-400 Exam
Microsoft Power Platform Developer (Page 2 )

Updated On: 1-Feb-2026
View Related Case Study

DRAG DROP (Drag and Drop is not supported)
You need to select connectors for the app.

Which types of connectors should you use? To answer, drag the appropriate connectors to the correct requirements. Each connector may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Create a custom connector
A custom connector is a wrapper around a REST API (Logic Apps also supports SOAP APIs) that allows Logic Apps, Power Automate, or Power Apps to communicate with that REST or SOAP API.

Box 2: Use an AppSource connector
You can only retrieve the Customer, UnifiedActivity, and Segments entities through the Power Apps connector. Other entities are shown because the underlying connector supports them through triggers in Power Automate.

Scenario: Customer information is stored in the Accounts entity. Box 3: Use a native application function
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.


Reference:

https://docs.microsoft.com/en-us/connectors/custom-connectors/
https://docs.microsoft.com/en-us/dynamics365/customer-insights/audience-insights/export-power-apps



You are creating a .NET application to load a large volume of data into a Dataverse table with one default column value. A synchronous plug-in already sets the same default column value for new rows in the table.

To speed up the process, you must disable the plug-in during the data load. The data load must run during business hours. The load must not affect rows users may be creating.

You need to perform the operations.

What are two possible ways to achieve this goal? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

  1. Send the BypassCustomPluginExecution as an optional parameter with the create request.
  2. Send the SuppressCallbackRegistrationExpanderJob as an optional parameter with the request.
  3. Disable the plug-in step prior to starting the data load.
  4. Set the BypassPluginExecution property on the CrmServiceClient.

Answer(s): A,C

Explanation:

Send the BypassCustomPluginExecution as an optional parameter with the create request:
This parameter is specifically designed to bypass plug-ins during a data load, ensuring better performance while not impacting other rows created by users. This approach is granular and only affects the specific operation being executed.

Disable the plug-in step prior to starting the data load:
Temporarily disabling the plug-in step ensures that the plug-in does not execute during the bulk data operation. After the data load is complete, the plug-in can be re-enabled. This approach impacts all operations on the table while the plug-in is disabled, so it must be carefully coordinated.



A company creates a custom connector for its cloud-based ERP system.
The company requires an authentication method that can be consumed by the custom connector.

You need to configure the authentication method.

Which authentication method should you use?

  1. basic authentication
  2. Windows Active Directory authentication
  3. certificate-based authentication
  4. password less authentication

Answer(s): A

Explanation:

Basic authentication is widely supported by custom connectors in Power Platform. It requires a username and password to authenticate and is straightforward to configure for cloud-based ERP systems. It is commonly used when connecting to external systems that do not natively support advanced authentication methods like OAuth.



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 on the review screen.

You are designing an integration that sends created records from a custom Dataverse table to an exposed REST API.

When the REST API is unavailable, you must be able to retry if the response status code is 500.
You need to select a solution that meets the requirement.

Solution: Register a service endpoint for an Azure Service Bus queue. Use an Azure Function to process messages from the queue and forward them to the REST API. Redirect failed messages to the dead-letter queue.

Does the solution meet the goal?

  1. Yes
  2. No

Answer(s): A

Explanation:

Azure Service Bus queues are well-suited for handling message-based integrations, ensuring reliable delivery even when external systems (like a REST API) are unavailable. Using an Azure Function to process messages and forward them to the REST API adds flexibility and resilience, as it allows for retries and error handling, including the scenario where the API returns a 500 status code.
Redirecting failed messages to the dead-letter queue ensures that unprocessed messages are not lost, allowing further investigation or retries. This solution provides the necessary retry mechanism and error handling.



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 on the review screen.

You are designing an integration that sends created records from a custom Dataverse table to an exposed REST API.

When the REST API is unavailable, you must be able to retry if the response status code is 500.
You need to select a solution that meets the requirement.

Solution: Register an asynchronous plug-in that makes an HTTP request to the REST API. Raise an InvalidPluginExecutionException that is configured to retry when the request fails.

Does the solution meet the goal?

  1. Yes
  2. No

Answer(s): B



Viewing page 2 of 80
Viewing questions 6 - 10 out of 429 questions



Post your Comments and Discuss Microsoft PL-400 exam prep with other Community members:

Join the PL-400 Discussion