- Email support@dumps4free.com
Two APIs are deployed to a two-node on-prem cluster. Due to a requirements change, the two APIs must communicate to exchange data asynchronously.
A.
If the two APIs use the same domain, the VM Connector can be leveraged
B.
The VM Connector is used to inter-application communication, so it is not possible to use the VM Connector
C.
Instead of using the VM Connector use <flow-ref>directly
D.
It is not possible to use the VM Connector since the APIs are running in a cluster mode and each mode has it own set of VM Queues
If the two APIs use the same domain, the VM Connector can be leveraged
Explanation
To communicate asynchronously between two APIs deployed to a two-node on-prem cluster, the developer can use the VM Connector if the two APIs use the same domain. The VM Connector allows passing messages between different Mule applications within a single Mule runtime instance or across different instances using shared memory or persistent storage. If two APIs are deployed under the same domain, they can share resources such as VM queues and communicate asynchronously using VM Connector operations.
References:
https://docs.mulesoft.com/mule-runtime/4.3/vm-connector
https://docs.mulesoft.com/mule-runtime/4.3/shared-resources
Which configurations are required for HTTP Listener to enable mTLS authentication?
A.
Set an appropriate reconnection strategy and use persistent connections for the listener
B.
Set an appropriate keystore configuration and use persistent connections for the listener
C.
Set an appropriate keystore and truststore configuration for the listener
D.
Set an appropriate truststore configuration and reconnection strategy for the listener
Set an appropriate keystore and truststore configuration for the listener
To enable mTLS authentication for HTTP Listener, the developer needs to set an appropriate keystore and truststore configuration for the listener. The keystore contains the certificate and private key of the Mule application that are used to prove its identity to clients. The truststore contains the certificates of trusted clients that are allowed to access the Mule application.
References:
https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#mutual-authentication
A new Mule project has been created in Anypoint Studio with the default settings.
Which file inside the Mule project must be modified before using Maven to successfully deploy the application?
A.
Settings.xml
B.
Config.yaml
C.
Pom.xml
D.
Mule.artificact.json
Pom.xml
Explanation
To use Maven to successfully deploy the application, the developer needs to modify the pom.xml file inside the Mule project. The pom.xml file contains the configuration and dependencies of the Mule application, as well as the deployment information such as the CloudHub region, environment, and worker size. The developer needs to specify these properties in the pom.xml file before using Maven to deploy the application.
References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#application-deployment-descriptor
When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?
A.
A protocol
B.
The TLS version
C.
An encryption algorithm
D.
The Public key format
An encryption algorithm
Explanation
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/4.3/tls-configuration#cipher-suites
A mule application exposes and API for creating payments. An Operations team wants to ensure that the Payment API is up and running at all times in production. Which approach should be used to test that the payment API is working in production?
A.
Create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API
B.
Configure the application to send health data to an external system
C.
Create a health check endpoint that reuses the same port number and HTTP Listener configuration as the API itself
D.
Monitor the Payment API directly sending real customer payment data
Create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API
Explanation:
To test that the payment API is working in production, the developer should create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API. This way, the developer can isolate the health check endpoint from the API traffic and avoid affecting the performance or availability of the API. The health check endpoint should return a simple response that indicates the status of the API, such as OK or ERROR.
References:
https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor#create-a-monitor
| Page 1 out of 10 Pages |