In a custom connector, where can you write code to transform data?

In the Open API definition file

In the 'Code' section of the connector's test or development environment

A custom connector sends data to an API that requires the data to be base64-encoded. The data is provided as a string in the connector. The developer wants to encode the data before sending it. What is the best way to achieve this?

Modify the OpenAPI definition to specify that the parameter is base64-encoded.

Ask users to encode the data before entering it.

Use a policy template to encode the string to base64.

Create an Azure Function to encode the string and call it from the connector.

What is the purpose of extending an Open API definition for a custom connector?

To increase the API's rate limit

To compile the connector into a native application

To add new operations or parameters that are not in the original API definition

To change the authentication type of the connector

A company is building a custom connector for an internal REST API that uses OAuth 2.0 with the authorization code flow. The API requires a client ID and client secret, and the connector will be used in Power Apps and Power Automate. The security team mandates that the client secret must not be stored in plain text within the connector definition. What should you do?

Use API key authentication and embed the secret in the OpenAPI definition's security scheme.

Use OAuth 2.0 authentication and enter the client ID and secret in the connector's authentication settings, which are encrypted at rest.

Store the client secret in an Azure Key Vault and reference it in the connector's authentication parameters.

Implement a custom authentication policy template to inject the client secret from an environment variable at runtime.

A custom connector uses OAuth 2.0 with Azure AD. The API requires a specific 'scope' parameter in the token request. The connector is currently failing with an 'invalid scope' error. What should you configure?

Add the scope as a query parameter in the OpenAPI definition for each operation.

Add the scope to the 'Scope' field in the connector's authentication settings.

Use a policy template to inject the scope into the Authorization header.

Modify the API to accept a different scope.

Microsoft Certified:Power Platform Developer Associate

Domain 5Objective 2

Create Custom Connectors PL-400 Practice Questions (Page 1)

Part of the Extend the platform domain, which accounts for 30–35% of the PL-400 exam. Microsoft does not publish an official question count, but from its 100-minute exam (~40–65 total, ~12–23 in this domain), expect 2–5 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

8concepts

30–35%of the exam

Questions 1–5

1foundation · medium
In a custom connector, where can you write code to transform data?
Select an answer first
2application · medium
A custom connector sends data to an API that requires the data to be base64-encoded. The data is provided as a string in the connector. The developer wants to encode the data before sending it. What is the best way to achieve this?
Select an answer first
3foundation · medium
What is the purpose of extending an Open API definition for a custom connector?
Select an answer first
4application · medium
A company is building a custom connector for an internal REST API that uses OAuth 2.0 with the authorization code flow. The API requires a client ID and client secret, and the connector will be used in Power Apps and Power Automate. The security team mandates that the client secret must not be stored in plain text within the connector definition. What should you do?
Select an answer first
5application · medium
A custom connector uses OAuth 2.0 with Azure AD. The API requires a specific 'scope' parameter in the token request. The connector is currently failing with an 'invalid scope' error. What should you configure?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PL-400

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “PL-400” is a trademark of its owner, used for identification only.