A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the
AWS VPC.
To what TCP port do API invocations to that Mule application need to be sent?
A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the
AWS VPC.
To what TCP port do API invocations to that Mule application need to be sent?
When a Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud, the invocations should be sent to port 443. This is the standard port for HTTPS traffic and is used for secure communications over the internet. MuleSoft documentation and general network standards support that HTTPS traffic typically utilizes port 443.
8091 AND 8092 used for Http and Https traffics only in local or private vpc, it didnt allow you to use in mule worker shared cloud
Should be 8082
It is 8092, which is for the private vpc, not 8082. Hence it is not an option
A. 443
D. HTTPS port for shared load balancer is enabled though 8092.
A is correct
Should be A. port 8092 is the port on SLB for access within VPC. Mule application will expose common 443 port for SSL traffic. Unless you modified it.
A is correct. The other ones are irrelevant. 8091 and 8092 are only for private VPC, not shared VPC. 8081 is for HTTP in the shared vpc. Which leaves A 442 as the correct answer
D is correct : must stay inside the AWS VPC is a key word
Answer: A
HTTP and HTTPS requests (web API invocations) sent to a CloudHub Shared Load Balancer on port 80 and 443 are forwarded by the CloudHub Shared Load Balancer to one of the Mule application’s CloudHub workers (approximately round-robin), where they reach the Mule application on port 8081 and 8082, respectively
A. 443
443 , https://docs.mulesoft.com/cloudhub-1/vpc-architecture-concept
D is the correct answer.
The question mentions a SHARED WORKER CLOUD but at the same time it also mentions ALL TRAFFIC TO THAT MULE APP MUST STAY IN THE AWS VPC --> which means that we should treat this as an private VPC --> 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). Correct answer is D. 8092