Refer to the exhibits. Larger image Larger image Larger image The Mule application configures and uses two HTTP Listener global configuration elements. Mule application is run in Anypoint Studio. If…

Question

Exhibits

Options

• AThe mule application fails to start
• BThe mule application start successfully
• CThe mule application fails to start because of the port binding conflict as HTTP request also use
• DThe mule application start successfully

• A
  13% (3)
• B
  4% (1)
• C
  4% (1)
• D
  79% (19)

Explanation

In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues. Hence correct answer is The mule application start successfully Web client requests can be received at URI on port 2222 and on port 3333. Lets check why other options are incorrect 1) The mule application fails to start. There is URL path conflict because both HTTP Listeners are configured with same path ---- This is incorrect as port value is different in both listeners 2) The mule application start successfully. Web client requests can only be received at URI on port 2222 but not on port 3333 --- This is incorrect as there is no reason for not receiving requests on port 3) The mule application fails to start because of the port binding conflict as HTTP request also use same port i.e. 3333 --- Port binding conflict will not happen in this case. It would have if both listener configurations would have been on same port . But that is not the case here. Mule Ref Doc : HTTP Listener Reference - Mule 4 | MuleSoft Documentation

No community discussion yet for this question.