nerdexam
Microsoft

PL-400 · Question #426

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 i

The correct answer is A. Send the BypassCustomPluginExecution as an optional parameter with the create request. C. Disable the plug-in step prior to starting the data load.. 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 af

Submitted by fatima_kr· Apr 18, 2026

Question

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.

Options

  • ASend the BypassCustomPluginExecution as an optional parameter with the create request.
  • BSend the SuppressCallbackRegistrationExpanderJob as an optional parameter with the request.
  • CDisable the plug-in step prior to starting the data load.
  • DSet the BypassPluginExecution property on the CrmServiceClient.

How the community answered

(19 responses)
  • A
    74% (14)
  • B
    16% (3)
  • D
    11% (2)

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

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-400 Practice