A company uses five different shipping companies to deliver products to customers. Each shipping company has a separate service that quotes delivery fees for destination addresses. You need to…

Question

Exhibit

Options

• AAuthentication model
• BAddress parameter
• COpenAPI definition
• DFee parameter
• EFee reference

• A
  82% (23)
• D
  7% (2)
• E
  11% (3)

Explanation

Building a custom connector requires three foundational elements: an OpenAPI definition (C) to formally describe the APIs you're connecting to (endpoints, operations, request/response shapes); an Authentication model (A) to specify how the connector secures its calls to each shipping company's API (API key, OAuth, etc.); and an Address parameter (B) because the destination address is the input you send to the API to receive a quote in return.

Why D (Fee parameter) is wrong: The fee is the response/output returned by the shipping company's API - it's what you receive, not something you define as a parameter you send. You don't pass the fee to the API; the API gives it back to you.

Why E (Fee reference) is wrong: "Fee reference" is not a recognized element in custom connector design (OpenAPI/Power Platform). It has no standard meaning in this context and is a distractor meant to confuse with terminology that sounds plausible.

Memory tip: Think of the three correct answers as covering the three questions every connector must answer - "Who are you?" (Authentication), "What do you want?" (Address parameter as input), and "How does the whole thing work?" (OpenAPI definition as the blueprint). If something is a result you receive back, it belongs to the response, not the connector's definition.

No community discussion yet for this question.