RESTful interfaces expose endpoints corresponding to resources and methods; in MuleSoft, listeners can be created manually or generated from API definitions.

• A. They must be defined in RAML only
• B. Listeners can only be created manually
• C. Listeners for each resource/method can be created manually or generated from API definition
• D. Listeners are not used in RESTful interfaces

Answer: (C)

REST endpoints map to resources and HTTP methods, and in MuleSoft those endpoints are wired through HTTP Listeners in a flow. You can set these up by creating each listener manually, specifying the path and the allowed methods, which gives you precise control. You can also generate the listener scaffolding from an API definition so that each resource and method gets a corresponding inbound listener automatically, aligning the implementation with the API spec and speeding development. This dual capability—manual creation or generation from the API definition—best describes how listeners relate to REST interfaces. RAML is a common way to define the API, but the approach isn’t limited to RAML alone, and listeners are essential for handling RESTful traffic.