Exam PL-400 topic 2 question 57 discussion

Actual exam question from Microsoft's PL-400

Question #: 57
Topic #: 2

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 Postman to export the custom connector. Then use Postman to import the connector into the production environment.

Does the solution meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: B 🗳️

by Serious123 at Feb. 7, 2024, 8:38 a.m.

Comments

Submit Cancel

loftuscheek

5 months, 3 weeks ago

Selected Answer: B

Correct Approach: Managed Solution Packaging: Add the custom connector to a managed solution, export the managed solution, and then import it into the production environment. This method meets all the goals of secure, tenant-restricted deployment and aligns with Microsoft’s ALM best practices. False Approaches: Maker Portal Export/Import: Using the maker portal directly to export and import the connector fails to leverage solution management benefits. Postman Export/Import: This manual process bypasses ALM practices and risks misconfiguration. Publishing to AppSource: This approach exposes the connector to a broader audience, contradicting the requirement for tenant-only visibility.

upvoted 1 times

...

VKS5

9 months, 3 weeks ago

A. Yes.

upvoted 2 times

...

rrustick

1 year, 5 months ago

B. No Explanation: Using Postman to export and import the custom connector does not meet the goal of deploying the connector to a production environment and ensuring it is visible and accessible only to users in the tenant. Postman is an API client tool used for testing and debugging APIs, but it does not provide the necessary functionality to manage custom connectors within the Microsoft Power Platform or Azure environment.

upvoted 1 times

...

Serious123

1 year, 6 months ago

You could import the custom connector as a postman collection right?

upvoted 3 times

VKS5

9 months, 3 weeks ago

yes, OpenAPI is supported.

upvoted 1 times

...