MuleSoft MCD - Level 1 Practice Test 1
Refer to the exhibit.
What is the correct syntax to add an employee ID as a URI parameter in an HTTP Listener path?
Paths
The path of an HTTP listener can be static, which requires exact matches, or feature placeholders. Placeholders can be wildcards (*), which match against anything they are compared to, or parameters ({param}), which not only match against anything but also capture those values on a URI parameters map.
Take the following example paths for three listeners using a configuration that establishesapi/v1as the base path:
account/mulesoft/main-contact: only match the exact path requesthttp://awesome-company.com/api/v1/account/mulesoft/main-contact
account/{accountId}/main-contact: matches all path requests structured similarly, such ashttp://awesome-company.com/api/v1/account/salesforce/main-contact, and savesalesforceas the value ofaccountId.
account/{accountId}/*: matches all path requests different frommain-contact, such ashttp://awesome-company.com/api/v1/account/mulesoft/users, and savemulesoftas the value ofaccountId.
Mule Ref Doc :https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#paths