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

Why would a Mule application use the ${http.port} property placeholder for its HTTP Listener port when it is deployed to CloudHub?
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

Answer: A

Explanation:

This helps CloudHub to dynamically allocates a port at deployment time. MuleSoft Doc

Ref:

https://docs.mulesoft.com/mule-runtime/4.3/deploy-to-cloudhub#prerequisites

https://docs.mulesoft.com/runtime-manager/developing-applications-for-cloudhub