PL 400 Custom Connectors 3 — Questions and Answers
Question 1: When using OAuth 2.0 in a custom connector, where should the client secret be stored to keep it secure?
- In the connector's OpenAPI definition as a default value
- In the connector's security definition within the portal, not in the definition file (Correct answer)
- In an environment variable referenced by the flow
- In a canvas app's OnStart property
Correct answer: In the connector's security definition within the portal, not in the definition file
Client secrets are entered in the connector portal's security section and are stored encrypted server-side, never exposed in the definition file.
Question 2: A custom connector trigger needs to notify Power Automate when a new event occurs in an external system. Which trigger type uses a callback URL registered with the external API?
- Polling trigger
- Webhook trigger (Correct answer)
- Scheduled trigger
- Hybrid trigger
Correct answer: Webhook trigger
Webhook triggers register a callback URL with the external service, which then calls that URL to push events to Power Automate.
Question 3: You need to test a custom connector action against a live endpoint before deploying to production. Which built-in capability within the custom connector editor allows this?
- Connector checker
- Test console (Correct answer)
- Flow checker
- API gateway probe
Correct answer: Test console
The Test console tab in the custom connector editor lets you invoke actions against the real API and inspect requests and responses.
Question 4: Which x-ms extension property causes the connector designer to display a human-readable summary instead of the raw operation ID?
- x-ms-api-annotation
- x-ms-summary (Correct answer)
- x-ms-visibility
- x-ms-dynamic-values
Correct answer: x-ms-summary
The x-ms-summary extension provides a friendly display name shown in the Power Platform designer for operations and parameters.
Question 5: An ISV wants to distribute a certified custom connector so it appears in the default connector gallery for all Power Platform tenants. What process must they follow?
- Submit the connector to Microsoft for certification via the open-source GitHub connector repo (Correct answer)
- Purchase a Power Apps per-app plan and publish to AppSource
- Register the connector in Azure API Management
- Export the connector as a managed solution and list it on the marketplace
Correct answer: Submit the connector to Microsoft for certification via the open-source GitHub connector repo
Microsoft-certified connectors are submitted through the public GitHub connectors repository and reviewed by Microsoft before being added to the gallery.
Question 6: Which connection reference feature allows ALM pipelines to swap the underlying custom connector connection between environments without editing flows?
- Environment variables
- Connection references (Correct answer)
- Managed identities
- Service principal tokens
Correct answer: Connection references
Connection references decouple a flow from a specific connection, allowing different connections to be mapped per environment during deployment.
Question 7: A custom connector action must send a binary file to a REST endpoint. Which content type and parameter schema type should be used?
- application/json with type string
- multipart/form-data with type string format binary (Correct answer)
- text/plain with type integer
- application/xml with type array
Correct answer: multipart/form-data with type string format binary
Binary file uploads require multipart/form-data content type and a parameter schema of type string with format binary.
When using OAuth 2.0 in a custom connector, where should the client secret be stored to keep it secure?