If the certificate of the target API is signed by a certificate authority (CA), what is true about the HTTP Request operation when the flow executes?

The flow is invoicing a target API. The API’s protocol is HTTPS. The TLS configuration in the HTTP Request Configuration global element is set to None. A web client submits a request to http:localhost:8081/vehicles.

If the certificate of the target API is signed by a certificate authority (CA), what is true about the HTTP Request operation when the flow executes?
A . The HTTP Request operation will succeed if the CA’S certificate is present in the JRE’s default keystore
B . The HTTP Request operation will succeed if the CA’s certificate is present in the JRE’s default truststore.
C . The HTTP Request operation will always succeed regardless of the CA
D . The HTTP Request operation will always fail regardless of the CA

Answer: B

Explanation:

The HTTP Request operation will use the default truststore of the JRE to validate the certificate of the target API. If the CA’s certificate is present in the truststore, the operation will succeed. Otherwise, it will fail with a handshake exception.

References: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#tls-default