An API team provides an OpenAPI 2.0 definition file for its REST service, already describing the operations, parameters, responses and security scheme. A developer must create a custom connector from it with minimal manual entry. How should the developer start?
Select an answer to reveal the explanation.
Short Explanation
If someone hands you the blueprint, don't redraw it by hand. Importing the OpenAPI file builds the actions, parameters and security for you, and then you just tidy up. The Code tab is for C# transformations, not for pasting definitions.
Full Explanation
Custom connectors are defined with OpenAPI behind the scenes, and the custom connector wizard can import an existing OpenAPI definition, from a file or from a URL. Importing creates the connector's general settings, operations, parameters, responses and, where the definition includes it, the security scheme, so the developer then reviews each tab, adds summaries or visibility where needed, and tests. Create from blank defines everything manually; the Code tab holds optional C# that transforms requests and responses and does not parse a definition. The Postman importer expects a Postman collection format, and an OpenAPI document is not a collection, so the import fails or produces nothing useful. Web resources are model-driven app assets such as scripts and images; the connector's General tab takes scheme, host and base URL and cannot reference a web resource as a definition. Exam caveat: custom connectors use OpenAPI 2.0, so an OpenAPI 3.0 document must be converted before import, and the definition must pass validation before the connector is saved. Operational check: import the file, fix any validation messages on the Definition tab, create a connection and test one operation from the Test tab.