The HTTP Listener path attribute supports URI templates, including wildcards. The asterisk () wildcard is used to match a single segment in the URL path. In this case, the path /status will correctly match both /order/status and /customer/status because the will match either order or customer as a single path segment. This allows a single HTTP Listener to handle requests for both endpoints, routing them to the same flow for processing.

A. [order,customer]/status is not a valid URI template syntax for the HTTP Listener path. It resembles a regular expression, which is not the matching mechanism used here.

B. ?[order,customer]/status is invalid syntax. The ? character is used to denote the beginning of query parameters, not for path segment matching.

D. status is incorrect because the wildcard matches a whole path segment. This pattern would match URLs like /somethingstatus but not /order/status.

1. MuleSoft Documentation, "HTTP Listener Connector". In the "Path" attribute description, it states: "The path can contain URI template parameters, which allow you to bind parts of the URI to variables in the flow." Wildcards are a form of this.

2. MuleSoft Documentation, "Create an HTTP Listener Source". Under the "General" tab configuration for the path, it explains the use of path parameters and wildcards. For example, /users/{userId}. The single segment wildcard functions similarly to a named parameter like {userId} but without capturing the value to a variable.