nerdexam
Microsoft

PL-400 · Question #412

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…

The correct answer is B. No. Registering an asynchronous plug-in alone does not inherently provide an automatic retry mechanism for HTTP requests based on a 500 status code if the external REST API is unavailable.

Submitted by salim_om· 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 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?

Options

  • AYes
  • BNo

How the community answered

(31 responses)
  • A
    19% (6)
  • B
    81% (25)

Why each option

Registering an asynchronous plug-in alone does not inherently provide an automatic retry mechanism for HTTP requests based on a 500 status code if the external REST API is unavailable.

AYes

The proposed solution (registering an asynchronous plug-in) does not meet the explicit requirement for automatic retries on a 500 status code response.

BNoCorrect

A standard asynchronous plug-in executes a single time and does not automatically implement retry logic for specific HTTP status codes like 500 when an external REST API is unavailable. To achieve this, custom retry logic would need to be coded within the plug-in, or a different integration pattern with built-in retry policies (e.g., Azure Logic Apps) would be more suitable.

Concept tested: Dataverse plug-in HTTP call retries

Source: https://learn.microsoft.com/en-us/power-apps/developer/dataverse/best-practices/business-logic/perform-long-running-operations

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-400 Practice