News / Exam Questions

This question has been asked by one of our members and a similar question could most likely be on the exam. All answers have been verified by MuleSoft certified FoMS experts.

Question

Why would a Mule application use the ${http.port} property placeholder for its HTTP Listener
port when it is deployed to CloudHub?

Answer

A) Allows CloudHub to automatically change the HTTP port to allow external clients to connect to the HTTP Listener

B) Allows CloudHub to automatically register the application with API Manager

C) Allows MuleSoft Support to troubleshoot the application by connecting directly to the HTTP Listener

D) Allows clients to VPN directly to the application at the Mule application's configured HTTP port

The correct answer to this question is A.

Explanation

According to MuleSoft, instead of using static values for your Mule application configurations, such as connections, you can create a .yaml or a .properties file to contain your properties and then reference the properties from your application.

Configuring a properties file improves the organization and maintainability of your applications.

If you use Anypoint Connector for HTTP (HTTP Connector), define the host address in the CloudHub configuration as 0.0.0.0. CloudHub routes requests from your application domain URL to the endpoint. If you deploy multiple workers, CloudHub load-balances incoming traffic automatically across the workers for you. As your application scales, work loads automatically distribute between your workers.

If your application requires an externally accessible HTTP or HTTPS port to receive messages, trigger events, or expose a web service or user interface, declare the HTTP Listener port using the reserved property ${http.port} or ${https.port}. On CloudHub, port ${http.port} or ${https.port} is assigned automatically by the platform services. Traffic on port 80 to your application domain’s URL is routed to ${http.port} and traffic on port 443 is route to ${https.port}.

To support routing to multiple CloudHub services over this port, you need to configure each with unique paths on the URL that is exposed. For example:

http://0.0.0.0:${http.port}/service/path/one
http://0.0.0.0:${http.port}/service/path/two