PL 400 Custom Connectors 2

Question 1

When defining a custom connector in Power Platform, which file format is used to describe the API operations and parameters?

Accepted Answer

OpenAPI (Swagger) 2.0 or 3.0

Answer

Custom connectors use OpenAPI (Swagger) 2.0 or 3.0 specifications to describe API operations, parameters, and responses.

Question 2

A custom connector needs to call an API that returns paginated results. Which feature should you configure to automatically retrieve all pages?

Accepted Answer

Pagination policy

Answer

The pagination policy on a custom connector action automatically fetches subsequent pages by following next-page links or incrementing offsets.

Question 3

You want to hide an internal API parameter from canvas app makers using your custom connector. What should you set on that parameter?

Accepted Answer

Visibility = internal

Answer

Setting a parameter's visibility to 'internal' hides it from the connector UI while still allowing it to be sent in requests.

Question 4

Which authentication type should you choose for a custom connector that must support individual user logins via Azure AD without sharing a single service account?

Accepted Answer

OAuth 2.0

Answer

OAuth 2.0 delegates authentication to Azure AD so each user authenticates with their own identity rather than a shared credential.

Question 5

A custom connector action returns a dynamic list of properties that vary per record. Which feature lets Power Automate show these properties dynamically in the designer?

Accepted Answer

Dynamic schema using x-ms-dynamic-schema

Answer

The x-ms-dynamic-schema extension calls a separate API endpoint to retrieve the actual response schema at design time.

(PL 400) Microsoft Certified Power Platform Developer Associate Practice Test

(PL 400) Microsoft Certified Power Platform Developer Associate Practice Test

PL 400 Custom Connectors 2