nerdexam
Microsoft

PL-400 · Question #84

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals…

The correct answer is B. No. Increasing the plugin execution timeout typically only delays a timeout for an inefficient synchronous PostOperation plugin and does not resolve the underlying performance issue.

Submitted by satoshi_tk· Apr 18, 2026

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets 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 in the review screen. A company implementsDynamics 365 Customer Service. The company deploys synchronous plug-ins for the PreOperation and PostOperation stages on create and for the PostOperation stage on update for processing different case type. Users experience errors when updating cases. The plug-in trace log files show that the PostOperation plug-in update of case times out after two minutes. You perform basic testing and discover that this plug-in is triggered on every update of a case. You examine the code and discover that the plug-in retrieves all columns for the updated case record performing its work. You need to reduce the number of errors. You need to achieve this goal with the test amount of changes. Solution: In the Plug-in Registration tool, set filtering attributes on the plug-in to only Case Type filed. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(14 responses)
  • A
    29% (4)
  • B
    71% (10)

Why each option

Increasing the plugin execution timeout typically only delays a timeout for an inefficient synchronous PostOperation plugin and does not resolve the underlying performance issue.

AYes

The proposed solution is ineffective in resolving a plugin timeout, therefore 'Yes' is not the correct assessment.

BNoCorrect

Merely increasing the plugin timeout setting does not address the root cause of an inefficient or long-running synchronous PostOperation plugin, which will likely still timeout or degrade performance.

Concept tested: Dynamics 365 plugin timeout resolution

Source: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/org-service/understand-synchronous-and-asynchronous-plugins

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice