Which reserved property enables an HTTPS Listener to be accessed by external web clients after deployment to CloudHub?

Which reserved property enables an HTTPS Listener to be accessed by external web clients after deployment to CloudHub?

• A. ${secure.port}
• B. ${https.port}
• C. ${http.port}
• D. ${domain.port}

Answer: (B)

When you deploy to CloudHub, the platform exposes a public port for HTTPS traffic and makes it available to your app through a reserved property. The HTTPS listener should bind to that port so external web clients can reach it after deployment. Using the reserved property for HTTPS port ensures the listener uses the exact port CloudHub exposes for secure traffic, enabling external access. The HTTP port would be for non-secure traffic, which isn’t what external HTTPS clients use. The other reserved properties aren’t the standard ones CloudHub provides for HTTPS access, so they wouldn’t guarantee connectivity.

When you deploy to CloudHub, the platform exposes a public port for HTTPS traffic and makes it available to your app through a reserved property. The HTTPS listener should bind to that port so external web clients can reach it after deployment. Using the reserved property for HTTPS port ensures the listener uses the exact port CloudHub exposes for secure traffic, enabling external access.

The HTTP port would be for non-secure traffic, which isn’t what external HTTPS clients use. The other reserved properties aren’t the standard ones CloudHub provides for HTTPS access, so they wouldn’t guarantee connectivity.