Examice

Exam MCD - Level 1 All QuestionsBrowse all questions from this exam

Question 128

A Mule application’s HTTP Listener is configured with the HTTP protocol. The HTTP Listener's port attribute is configured with a property placeholder named http.port. The Mule application sets the http.port property placeholder’s value to 9090.

Tho Mule application’s deployed to CloudHub without setting any properties in the Runtime Manager Properties tab, and a log message reports the status of the HTTP Listener after the Mule application deployment completes.

After the Mule application is deployed, what information is reported in the worker logs related to the port on which the Mule application’s HTTP Listener listens?

The HTTP Listener is listening on port 8081.

The HTTP Listener is listening on port 9090.

The HTTP Listener failed to bind to the port and is not listening for connections.

The HTTP Listener is listening on port 80.

Correct Answer: A

When deploying a Mule application on CloudHub, the HTTP Listener must listen on host 0.0.0.0 and either port 8081 for HTTP traffic or port 8082 for HTTPS traffic. Despite the HTTP Listener's port attribute being configured with a property placeholder value of 9090, CloudHub overrides this to ensure the application is accessible through its standard ports for HTTP and HTTPS. Therefore, the HTTP Listener will be reported as listening on port 8081 in the worker logs.

Discussion

ExamDevOption: A

The correct answer is A: Each application deployed on CloudHub has a CNAME record that refers to the load balancer, for example myapp.region.cloudhub.io. Mule apps deployed in CloudHub must listen on host 0.0.0.0 and to either the HTTP port (8081) or to the HTTPS port (8082).

[Removed]Option: A

Answer is A https://docs.mulesoft.com/cloudhub-1/cloudhub-networking-guide

aiden_03Option: A

I believe answer is A https://blogs.perficient.com/2017/02/28/enabling-https-for-mule-application/#:~:text=By%20default%2C%20http.,forwards%20port%2080%20to%20http.