A custom connector has a Create ticket action with a project parameter. Makers should choose the project from a dropdown filled at design time by calling the connector's own List projects operation, which returns an array of objects with id and name properties. Which OpenAPI extension should the developer add to the project parameter?
Select an answer to reveal the explanation.
Short Explanation
When the list of choices lives in the API, you let the designer go fetch it. x-ms-dynamic-values calls List projects, shows each name, and stores each id. A hard-coded enum works until the first new project shows up.
Full Explanation
The x-ms-dynamic-values extension tells the designer to call another operation of the same connector and use its results to populate a parameter's dropdown. Its operationId names the List projects operation, value-collection identifies the array when the response wraps it in a property, value-path selects the id property sent to the API, and value-title selects the name property shown to makers. Because the list is fetched at design time from the live API, new projects appear without changing the connector. An enum hard-codes values into the definition, so every new or renamed project requires a connector update, and it cannot show friendly names separately from ids. The x-ms-dynamic-schema extension describes a parameter's or response's shape that changes with input values; it defines structure, not the list of choices. The x-ms-visibility extension only controls prominence such as important, advanced or internal; it never turns a field into a dropdown. Exam caveat: x-ms-dynamic-list is the newer extension that supports more complex parameter references, and both can be present together for compatibility. Operational check: update the connector, add the Create ticket action in a test flow, open the project field and confirm the dropdown lists current project names and saves the matching id.