nerdexam
Microsoft

PL-400 · Question #368

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 h

The correct answer is B. No. Adding a custom connector to a managed solution facilitates deployment, but it doesn't inherently control its visibility or access exclusively to users within a specific tenant.

Submitted by minji_kr· 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: Add the custom connector to a managed solution, export the managed solution, and then import the managed solution into the production environment. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(41 responses)
  • A
    20% (8)
  • B
    80% (33)

Why each option

Adding a custom connector to a managed solution facilitates deployment, but it doesn't inherently control its visibility or access exclusively to users within a specific tenant.

AYes

Adding to a managed solution is a deployment mechanism, not an access control mechanism for tenant visibility.

BNoCorrect

Adding a custom connector to a managed solution facilitates its deployment and lifecycle management across environments, but it does not inherently guarantee or enforce that the connector will only be visible and accessible to users within a specific tenant. The single-tenant restriction is primarily determined by the Azure Function's Microsoft Entra ID application registration and the custom connector's authentication configuration.

Concept tested: Custom connector deployment and tenant access

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

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice