nerdexam
Microsoft

PL-400 · Question #179

You deploy a Power Platform plug-in to a production environment. The plug-in code contains detailed tracing information. You are a member of the Environment Maker security role for the environment…

The correct answer is B. Send a GET request to retrieve the plugintracelogs records. It is easier to query this data using the Web API in your browser using the following query with the plugintracelog EntityType, using the typename property to filter results in the messageblock property based on the name of the plug-in class: GET <your org…

Submitted by fernanda_arg· Apr 18, 2026

Question

You deploy a Power Platform plug-in to a production environment. The plug-in code contains detailed tracing information. You are a member of the Environment Maker security role for the environment. Users report unexpected results when they interact with confidential data by using the plug-in. You confirm that the plug-in works without errors in a development environment. You need to investigate the root cause of the plug-in errors. What should you do?

Options

  • ASend a PUT request to enable plug-in tracing for the production environment.
  • BSend a GET request to retrieve the plugintracelogs records.
  • CInstall Plug-in profiler in the production environment by using the Plug-in Registration tool.
  • DReproduce and capture the errors, then debug from Visual Studio.

How the community answered

(30 responses)
  • A
    13% (4)
  • B
    77% (23)
  • C
    7% (2)
  • D
    3% (1)

Explanation

It is easier to query this data using the Web API in your browser using the following query with the plugintracelog EntityType, using the typename property to filter results in the messageblock property based on the name of the plug-in class: GET <your org uri>/api/data/v9.0/plugintracelogs?$select=messageblock&$filter=typename eq 'BasicPlugin.FollowUpPlugin'

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-400 Practice