- Email support@dumps4free.com
A project team uses RAML specifications to document API functional requirements and deliver API definitions. As per the current legal requirement, all designed API definitions to be augmented with an additional non-functional requirement to protect the services from a high rate of requests according to define service level agreements. Assuming that the project is following Mulesoft API governance and policies, how should the project team convey the necessary non-functional requirement to stakeholders?
A. Create proxies in API manager for the non functional requirement and publish to exchange
B. Add all non functional requirements as comments to RAML specification and publish to exchange
C. Create various SLA's in API manager for the non functional requirement and publish to exchange
D. Update API definitions with the fragment for the appropriate policy and publish to exchange
Explanation:
To ensure that non-functional requirements, such as rate limiting, are clearly communicated and enforced in the designed API definitions, the project team should use API fragments for the appropriate policy. Here's why option D is correct:
API Governance and Policies: Mulesoft's API governance framework allows the definition and enforcement of policies across APIs to ensure consistency and compliance with organizational standards. These policies can include security, rate limiting, logging, and more.
Policy Fragments: By updating API definitions with policy fragments, the team can encapsulate the non-functional requirements within the API specification itself. This approach ensures that these requirements are an integral part of the API design and are automatically applied whenever the API is deployed.
Publishing to Exchange: Publishing the updated API definitions with the policy fragments to Anypoint Exchange makes them available for reuse and ensures that all stakeholders have access to the latest, compliant API specifications.
Example of adding a rate limiting policy fragment to a RAML file:
#%RAML 1.0 title: Example API version: v1 baseUri: https://api.example.com/v1 ... /* Include the rate limiting policy fragment */ uses: rateLimitPolicy: !include rate-limit-policy.raml
The rate-limit-policy.raml fragment might define the specific rate limiting rules as per the service level agreements.
References
MuleSoft API Manager
Defining and Using API Fragments
An architect is designing a Mule application to meet the following two requirements:
1. The application must process files asynchronously and reliably from an FTPS server to a back-end database using VM intermediary queues for
load-balancing Mule events.
2. The application must process a medium rate of records from a source to a target system using a Batch Job scope.
To make the Mule application more reliable, the Mule application will be deployed to two CloudHub 1.0 workers.
Following MuleSoft-recommended best practices, how should the Mule application deployment typically be configured in Runtime Manger to best
support the performance and reliability goals of both the Batch Job scope and the file processing VM queues?
A. Check the Persistent VM queues checkbox in the application deployment configuration
B. Check the Non-persistent VM queues checkbox in the application deployment configuration
C. In the Runtime Manager Properties tab, disable persistent VM queues for Batch Job scopes
D. In the Runtime Manager Properties tab, enable persistent VM queues for the FTPS connector
Explanation:
Requirements:
Persistent VM Queues:
MuleSoft Best Practices:
Configuration in Runtime Manager:
References:
MuleSoft Documentation on VM Queues: VM Queues
MuleSoft Best Practices: MuleSoft Best Practices
CloudHub Deployment Guide: CloudHub Deployment
An organization designing a hybrid, load balanced, single cluster production environment. Due to performance service level agreement goals, it is looking into running the Mule applications in an active-active multi node cluster configuration. What should be considered when running its Mule applications in this type of environment?
A. All event sources, regardless of time , can be configured as the target source by the primary node in the cluster
B. An external load balancer is required to distribute incoming requests throughout the cluster nodes
C. A Mule application deployed to multiple nodes runs in an isolation from the other nodes in the cluster
D. Although the cluster environment is fully installed configured and running, it will not process any requests until an outage condition is detected by the primary node in the cluster.
Explanation:
In a hybrid, load-balanced, single cluster production environment running Mule applications in an active-active multi-node configuration, several considerations are critical for ensuring performance and reliability. The key consideration is the use of an external load balancer:
Active-Active Multi-Node Cluster Configuration:
External Load Balancer Requirement:
Load Balancer Configuration:
Mule Application Isolation:
Handling Requests:
Benefits:
References:
MuleSoft Documentation on Mule Clustering
Best Practices for Load Balancing
An application load balancer routes requests to a RESTful web API secured by Anypoint Flex Gateway. Which protocol is involved in the communication between the load balancer and the Gateway?
A. SFTP
B. HTTPS
C. LDAP
D. SMTP
Explanation:
An application load balancer routes requests to a RESTful web API secured by Anypoint Flex Gateway using the HTTPS protocol. HTTPS (HyperText Transfer Protocol Secure) ensures that the communication between the load balancer and the gateway is encrypted and secure, protecting the data from eavesdropping and tampering. HTTPS is the standard protocol for secure communication over the internet, especially for APIs handling sensitive data.
References:
Securing APIs with HTTPS
Understanding HTTPS
A set of integration Mule applications, some of which expose APIs, are being created to enable a new business process. Various stakeholders may be impacted by this. These stakeholders are a combination of semi-technical users (who understand basic integration terminology and concepts such as JSON and XML) and technically skilled potential consumers of the Mule applications and APIs. What Is an effective way for the project team responsible for the Mule applications and APIs being built to communicate with these stakeholders using Anypoint Platform and its supplied toolset?
A. Use Anypoint Design Center to implement the Mule applications and APIs and give the various stakeholders access to these Design Center projects, so they can collaborate and provide feedback
B. Create Anypoint Exchange entries with pages elaborating the integration design, including API notebooks (where applicable) to help the stakeholders understand and interact with the Mule applications and APIs at various levels of technical depth
C. Use Anypoint Exchange to register the various Mule applications and APIs and share the RAML definitions with the stakeholders, so they can be discovered
D. Capture documentation about the Mule applications and APIs inline within the Mule integration flows and use Anypoint Studio's Export Documentation feature to provide an HTML version of this documentation to the stakeholders
Explanation
As the stakeholders are semitechnical users , preferred option is Create Anypoint Exchange entries with pages elaborating the integration design, including API notebooks (where applicable) to help the stakeholders understand and interact with the Mule applications and APIs at various levels of technical depth
| Page 14 out of 54 Pages |
| Previous |