You create a plug-in to validate data. Users report that validation is not working as expected. You need to debug the plug-in. Which tool should you use?

The correct answer is A. Plug-in profiler. Because the plug-in executes on a remote server, you cannot attach a debugger to the plug-in process. The plug-in profiler captures a profile of an executing plug- in and allows you to re-play the execution of the plug-in using Visual Studio on your local computer. Install…

Submitted by haru.x· Apr 18, 2026

Question

You create a plug-in to validate data. Users report that validation is not working as expected. You need to debug the plug-in. Which tool should you use?

Options

APlug-in profiler
BPower Platform Tools for Visual Studio
CPlug-in dashboard
DPlug-in Registration Tool

How the community answered

(48 responses)

A
79% (38)
B
13% (6)
C
2% (1)
D
6% (3)

Explanation

Because the plug-in executes on a remote server, you cannot attach a debugger to the plug-in process. The plug-in profiler captures a profile of an executing plug- in and allows you to re-play the execution of the plug-in using Visual Studio on your local computer. Install plug-in profiler There are two tools available from which to run the Plug-in Profiler: the Plug-in Registration Tool and Power Platform Tools for Visual Studio. Follow these steps to begin profiling a plug-in's execution. 1. In the Plug-in Registration tool, select the (Step) BasicPlugin.FollowupPlugin: Create of account step you registered earlier, and click Start Profiling. 2. When presented with the Profiler Settings dialog, accept the default settings and click OK to close the dialog. https://docs.microsoft.com/en-us/power-apps/developer/data-platform/tutorial-debug-plug-in

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice