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
A corporation has deployed Mule applications to different customer-hosted Mule runtimes. Mule applications deployed to these Mule runtimes are managed by Anypoint Platform. What needs to be installed or configured (if anything) to monitor these Mule applications from Anypoint Monitoring, and how is monitoring data from each Mule application sent to Anypoint Monitoring?
A. Enable monitoring of individual Mule applications from the Runtime Manager application settings. Runtime Manager sends monitoring data to Anypoint Monitoring for each deployed Mule application.
B. Install a Runtime Manager agent on each Mule runtime. Each Runtime Manager agent sends monitoring data from the Mule applications running in its Mule runtime to Runtime Manager, then Runtime Manager sends monitoring data to Anypoint Monitoring.
C. Leave the out-of-the-box Anypoint Monitoring agent unchanged in its default Mule runtime installation. Each Anypoint Monitoring agent sends monitoring data from the Mule applications running in its Mule runtime to Runtime Manager, then Runtime Manager sends monitoring data to Anypoint Monitoring.
D. Install an Anypoint Monitoring agent on each Mule runtime. Each Anypoint Monitoring agent sends monitoring data from the Mule applications running in its Mule runtime to Anypoint Monitoring.
Explanation:
To monitor Mule applications deployed to different customer-hosted Mule runtimes using Anypoint Monitoring, follow these steps:
Install Anypoint Monitoring Agent: Install an Anypoint Monitoring agent on each Mule runtime. This agent is responsible for collecting monitoring data from the Mule applications running on that runtime.
Data Transmission: Each Anypoint Monitoring agent sends the collected monitoring data directly to Anypoint Monitoring. This ensures that performance metrics, logs, and other relevant data are available for analysis and monitoring within the Anypoint Platform.
By using the Anypoint Monitoring agent, organizations can effectively monitor their Mule applications across various environments, ensuring visibility and operational efficiency.
References
MuleSoft Documentation on Anypoint Monitoring
Installing and Configuring Anypoint Monitoring Agent
An organization heeds to procure an enterprise software system to increase cross-selling opportunities and better rack prospect data. Which category of enterprise software has these core capabilities, when used for its typical and intended purpose?
A. Supply Chain Management (SCM)
B. IT Service Management (ITSM)
C. Business-to-Business (A2B)
D. Customer Relationship Management (CRM)
Explanation:
Customer Relationship Management (CRM) systems are designed to manage a company’s interactions with current and potential customers. They provide capabilities for tracking prospect data, managing customer interactions, and analyzing customer information to improve cross-selling opportunities. By using a CRM system, organizations can consolidate customer information, enhance customer relationships, and leverage data analytics to drive sales and marketing efforts.
References:
What is CRM?
Benefits of CRM Systems
An organization is designing an integration Mule application to process orders by submitting them to a back-end system for offline processing. Each order will be received by the Mule application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a back-end system. Orders that cannot be successfully submitted due to rejections from the back-end system will need to be processed manually (outside the back-end system).
The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed. The ActiveMQ broker is located inside the organization’s firewall. The back-end system has a track record of unreliability due to both minor network connectivity issues and longer outages.
What idiomatic (used for their intended purposes) combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the back-end system while supporting but minimizing manual order processing?
A. An Until Successful scope to call the back-end system
One or more ActiveMQ long-retry queues
One or more ActiveMQ dead-letter queues for manual processing
B. One or more On Error scopes to assist calling the back-end system An Until Successful scope containing VM components for long retries A persistent dead-letter VM queue configured in CloudHub
C. One or more On Error scopes to assist calling the back-end system One or more ActiveMQ long-retry queues A persistent dead-letter object store configured in the CloudHub Object Store service
D. A Batch Job scope to call the back-end system An Until Successful scope containing Object Store components for long retries A dead-letter object store configured in the Mule application
What is a defining characteristic of an integration-Platform-as-a-Service (iPaaS)?
A. A Cloud-based
B. No-code
C. Code-first
D. On-premises
Explanation:
A defining characteristic of an Integration-Platform-as-a-Service (iPaaS) is that it is cloud-based. iPaaS provides a cloud-based platform to enable integration of applications and data across various environments. This approach leverages the scalability, flexibility, and accessibility of the cloud to facilitate seamless integrations, reduce on-premises infrastructure requirements, and improve the speed of deployment and maintenance of integration solutions.
References:
What is iPaaS?
Benefits of iPaaS
An Organization has previously provisioned its own AWS VPC hosting various servers. The organization now needs to use Cloudhub to host a Mule application that will implement a REST API once deployed to Cloudhub, this Mule application must be able to communicate securely with the customer-provisioned AWS VPC resources within the same region, without being interceptable on the public internet. What Anypoint Platform features should be used to meet these network communication requirements between Cloudhub and the existing customer-provisioned AWS VPC?
A. Add a Mulesoft hosted Anypoint VPC configured and with VPC Peering to the AWS VPC
B. Configure an external identity provider (IDP) in Anypoint Platform with certificates from the customer provisioned AWS VPC
C. Add a default API Whitelisting policy to API Manager to automatically whitelist the customer provisioned AWS VPC IP ranges needed by the Mule applicaton
D. Use VM queues in the Mule application to allow any non-mule assets within the customer provisioned AWS VPC to subscribed to and receive messages
Explanation
Correct answer is: Add a Mulesoft hosted Anypoint VPC configured and with VPC Peering to the AWS VPC * Connecting to your Anypoint VPC extends your corporate network and allows CloudHub workers to access resources behind your corporate firewall.
* You can connect on-premises data centers through a secured VPN tunnel, or a private AWS VPC through VPC peering, or by using AWS Direct Connect.
MuleSoft Doc Reference : https://docs.mulesoft.com/runtime-manager/virtual-private-cloud
| Page 6 out of 27 Pages |
| Previous |
Copyright © - All Rights Reserved