- Email support@dumps4free.com
A global organization operates datacenters in many countries. There are private network links between these datacenters because all business data (but NOT metadata) must be exchanged over these private network connections. The organization does not currently use AWS in any way. The strategic decision has Just been made to rigorously minimize IT operations effort and investment going forward. What combination of deployment options of the Anypoint Platform control plane and runtime plane(s) best serves this organization at the start of this strategic journey?
A. MuleSoft-hosted Anypoint Platform control plane CloudHub Shared Worker Cloud in multiple AWS regions
B. Anypoint Platform - Private Cloud Edition Customer-hosted runtime plane in each datacenter
C. MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in multiple AWS regions
D. MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in each datacenter
Explanation
Correct answer is MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in each datacenter There are two things to note about the question which can help us figure out correct answer.. * Business data must be exchanged over these private network connections which means we can not use MuleSoft provided Cloudhub option. So we are left with either customer hosted runtime in external cloud provider or customer hosted runtime in their own premises. As customer does not use AWS at the moment. Hence that don't have the immediate option of using Customer-hosted runtime plane in multiple AWS regions. hence the most suitable option for runtime plane is Customer-hosted runtime plane in each datacenter * Metadata has no limitation to reside in organization premises. Hence for control plane MuleSoft hosted Anypoint platform can be used as a strategic solution.
Hybrid is the best choice to start. Mule hosted Control plane and Customer hosted Runtime to start with.Once they mature in cloud migration, everything can be in Mule hosted.
What is maximum vCores can be allocated to application deployed to CloudHub?
A. 1 vCores
B. 2 vCores
C. 4 vCores
D. 16 vCores
When the mule application using VM is deployed to a customer-hosted cluster or multiple cloudhub workers, how are messages consumed by the Mule engine?
A. in non-deterministic way
B. by starting an XA transaction for each new message
C. in a deterministic way
D. the primary only in order to avoid duplicate processing
Explanation:
When a Mule application using VM (Virtual Machine) queues is deployed to a customer-hosted cluster or multiple CloudHub workers, the messages are consumed by the Mule engine in a non-deterministic way. Here’s an in-depth explanation:
VM Queues Overview:
Deployment in Clusters or Multiple Workers:
Non-Deterministic Message Consumption:
Advantages:
Considerations:
References:
MuleSoft Documentation on VM Connector
MuleSoft Documentation on High Availability Clustering
MuleSoft Documentation on Deploying to CloudHub
A rale limiting policy has been applied to a soap VI.2 API published in Clondhub. The API implementation catches errors in a global error handler on error propagate in the main flow for HTTP: RETRY_EXHAUSTED with HTTP status set to 429 and any with the HTTP status set to 500. What is the expected H1TP status when the client exceeds the quota of the API calls?
A. HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API B. HTTP status 500 as defined in the ANY error handler in the API since an API:RETRY_EXHAUSTED will be generated
B. HTTP status 401 unauthorized for policy violation
C. HTTP status 400 from the rate-limiting policy violation since the call does not reach the back-end
Explanation:
In the given scenario, a rate limiting policy has been applied to the SOAP API and a global error handler is configured to handle HTTP:RETRY_EXHAUSTED errors with a 429 status code. The rate limiting policy will trigger when the client exceeds the allowed quota of API calls. Since the HTTP:RETRY_EXHAUSTED error specifically catches quota exhaustion errors and the error handler is configured to return a 429 status code, the expected HTTP status returned to the client when the quota is exceeded will be 429. This error code indicates that the user has sent too many requests in a given amount of time ("rate limiting").
References:
MuleSoft Documentation on Error Handling
HTTP Status Codes
What Anypoint Connectors support transactions?
A. Database, JMS, VM
B. Database, 3MS, HTTP
C. Database, JMS, VM, SFTP
D. Database, VM, File
Explanation
Below Anypoint Connectors support transactions
● JMS – Publish – Consume
● VM – Publish – Consume
● Database – All operations
| Page 11 out of 54 Pages |
| Previous |