SalesForce SALESFORCE-MULESOFT-DEVELOPER-II - Questions & Answers

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.
https://docs.mulesoft.com/mule-runtime.3/tlsconfiguration#
tls-default

A cipher suite is a set of cryptographic algorithms that are used to secure the communication between a client and a server. A cipher suite consists of four components: a key exchange algorithm, an authentication algorithm, an encryption algorithm, and a message authentication code (MAC) algorithm.
During the cipher suite exchange, the client and the server agree on which encryption algorithm to use for encrypting and decrypting the data.
References:
https://docs.mulesoft.com/mule-runtime.3/tls-configuration#cipher-suites

The http-policy:processor element is used to intercept outbound HTTP requests made by Mule applications. It allows customizing the request before it is sent to the target API and modifying the response after it is received from the target API.
https://docs.mulesoft.com/apimanager/2.x/policy-mule4-custom-policy#policy-xml-file

The validate-customer flow uses an until-successful scope to validate each field of the customer data. The until-successful scope executes its processors until they succeed or exhausts the maximum number of retries. If any processor fails, it raises an error and stops executing the remaining processors. Therefore, if only the email address is invalid, a VALIDATION.INVALID_EMAIL error is raised and the validation of appointment date and customer name is skipped.
References:
https://docs.mulesoft.com/mule-runtime.3/until-successful-scope

When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically propagates some message attributes between flows via outbound and inbound properties. One of these attributes is correlation ID, which is returned to the caller in the response header by default as MULE_CORRELATION_ID.
https://docs.mulesoft.com/muleruntime/4.3/about-mule-message#message-attributes

Mutual TLS (mTLS) is an extension of TLS that requires both parties (client and server) to present their certificates to each other during the handshake process. This way, both parties can verify each other's identity and establish a secure connection. The authentication of the server happens before the authentication of the client, as the server sends its certificate first and then requests the client's certificate.
https://docs.mulesoft.com/mule-runtime.3/tls-configuration#mutualauthentication

When using XML SDK for creating custom message processors, all operations are public by default and can be used by any Mule application that imports them. There is no way to make an operation private or
protected in XML SDK.
https://docs.mulesoft.com/mule-sdk.1/xmlsdk#
operations

The Cache scope supports time to live (TTL) as a cache invalidation strategy without having to write any additional code. TTL specifies how long the cached response is valid before it expires and needs to be refreshed. The Cache scope also supports custom invalidation strategies using MEL or DataWeave expressions.
https://docs.mulesoft.com/mule-runtime.3/cachescope#
cache_invalidation

The MuleSoft recommended method to encrypt sensitive property data is to use the Secure Properties Tool that comes with Anypoint Studio. This tool allows encrypting properties files with a secret key and then decrypting them at runtime using the same key. The encryption key and sensitive data should be different for each environment to ensure security and avoid accidental exposure of sensitive data.
https://docs.mulesoft.com/mule-runtime.3/secure-configurationproperties

To package a custom policy using the HTTP Policy Transform Extension, the developer needs to create an XML template file and a YAML configuration file. The XML template file defines the policy logic using Mule components and placeholders for user-defined properties. The YAML configuration file defines the metadata of the policy, such as its name, description, category, parameters, and dependencies.
https://docs.mulesoft.com/api-manager.x/http-policytransform#packaging-the-policy