nerdexam
Microsoft

PL-400 · Question #370

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 A. Yes. Exporting a custom connector from the maker portal as part of a solution is the standard method for deployment, preserving its single-tenant configuration.

Submitted by valeria.br· 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 once 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 develops a new custom connector for a Microsoft Entra ID-protected Azure Function that was created as a single tenant app. The custom connector must be moved to a production environment. The connector must be visible and accessible only to users in the tenant. You need to deploy the custom connector. Solution: Use the maker portal to export the custom connector. Then use the maker portal to import the connector into the production environment. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(57 responses)
  • A
    72% (41)
  • B
    28% (16)

Why each option

Exporting a custom connector from the maker portal as part of a solution is the standard method for deployment, preserving its single-tenant configuration.

AYesCorrect

Using the maker portal to export the custom connector, typically as part of a solution, is the standard and correct method for deploying custom connectors from a development environment to a production environment. When exported in a solution, the custom connector's configuration, including its single-tenant Microsoft Entra ID protection, is preserved, allowing it to be visible and accessible only to users within that tenant in the target environment.

BNo

Exporting via the maker portal is a valid method for deploying custom connectors within a tenant.

Concept tested: Custom connector deployment via solutions

Source: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/export-import-custom-connector

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice