Free Salesforce MuleSoft-Integration-Architect-I Practice Exam with Questions & Answers | Set: 5

Explanation

Key to this question lies in the fact that Process API are not meant to be accessed directly by clients. Lets analyze options one by one. Client ID enforcement : This is applied at process API level generally to ensure that identity of API clients is always known and available for API-based analytics Rate Limiting : This policy is applied on Process Level API to secure API's against degradation of service that can happen in case load received is more than it can handle Custom circuit breaker : This is also quite useful feature on process level API's as it saves the API client the wasted time and effort of invoking a failing API. JSON threat protection : This policy is not required at Process API and rather implemented as Experience API's. This policy is used to safeguard application from malicious attacks by injecting malicious code in JSON object. As ideally Process API's are never called from external world , this policy is never used on Process API's Hence correct answer is JSON threat protection MuleSoft Documentation Reference : https://docs.mulesoft.com/api-manager/2.x/policy-mule3-json-threat

Explanation

As the Anypoint Platform organization administrator, you can configure identity management in Anypoint Platform to set up users for single sign-on (SSO).

Configure identity management using one of the following single sign-on standards:

1) OpenID Connect: End user identity verification by an authorization server including SSO

2) SAML 2.0: Web-based authorization including cross-domain SSO

Anypoint Exchange is the Anypoint Platform component that helps integration developers discover and share reusable APIs, connectors, and templates. It acts as a central repository where developers can publish and access various assets, facilitating reuse and collaboration within the organization. By using Anypoint Exchange, developers can reduce duplication of effort, speed up development processes, and ensure consistency across integrations.

Other components like API Manager, Anypoint Studio, and Design Center serve different purposes, such as managing APIs, developing Mule applications, and designing API specifications, but they are not specifically focused on discovering and sharing reusable assets.

References

MuleSoft Documentation on Anypoint Exchange

Best Practices for Asset Reuse on Anypoint Platform

When a batch job instance running on a runtime fabric environment with two cluster replicas encounters an unexpected failure, the following sequence of events occurs:

Failure Detection: The runtime fabric environment detects the failure of the replica running the batch job.

Replica Replacement: A new replica is provisioned to replace the failed one.

Batch Job State Recovery: MuleSoft’s batch processing mechanism ensures that the state of the batch job is periodically saved (checkpointing). This allows the new replica to resume processing from the last saved state.

Resumption of Processing: The new replica takes over the batch job, continuing from where the previous one left off, thus processing the remaining 99,000 records without starting from scratch or causing duplicate processing.

MuleSoft Documentation on Batch Processing

Runtime Fabric Guide

=======================

To ensure the high availability and reliability of critical APIs, it is essential to monitor their liveliness and readiness. Anypoint Monitoring provides comprehensive monitoring capabilities for Mule applications. Here’s how it can be implemented:

Application Monitoring: Enable monitoring for each individual Mule application. This allows for real-time visibility into the performance and health of each API.

Custom Dashboards: Create custom dashboards in Anypoint Monitoring to track key metrics such as response time, error rates, and throughput.

Alerts and Notifications: Configure alerts based on specific failure conditions or performance thresholds. These alerts can notify the Ops team immediately when an outage or performance degradation is detected.

Proactive Management: With detailed insights and proactive alerts, the Ops team can quickly respond to issues, ensuring that the APIs remain available and meet the defined SLAs.

Anypoint Monitoring

Configuring Alerts

Explanation

Below Anypoint Connectors support transactions ● JMS – Publish – Consume ● VM – Publish – Consume ● Database – All operations

AnTo resolve performance issues with the Master Look Up API, the following methods can be applied:

Implement the HTTP caching policy for all GET endpoints for the Master Look Up API: This caching policy helps reduce the number of database queries by storing frequently accessed data in cache, thus improving response times for subsequent requests.

Upgrade the vCore size from 0.1 vCore to 0.2 vCore: Increasing the vCore size can provide more computational resources, which can improve the processing power and overall performance of the API, particularly under high load conditions.

A core pillar of the MuleSoft Catalyst delivery approach is focusing on business outcomes. This approach ensures that the integration and API strategies are aligned with the organization’s overall business objectives. By emphasizing business outcomes, MuleSoft Catalyst helps organizations realize measurable benefits such as increased efficiency, faster time to market, and improved customer experiences. This outcome-driven methodology ensures that IT initiatives deliver tangible value to the business.

Explanation

* The Object Store V2 API enables API access to Anypoint Platform Object Store v2.

* You can configure a Mule app to use the Object Store REST API to store and retrieve values from an object store in another Mule app. However, Object Store v2 is not designed for app-to-app communication. To share data between two Mule4 apps, use a queue in Anypoint MQ.

* The Object Store v2 APIs enable you to use REST to perform the following:

- Retrieve a list of object stores and keys associated with an application.

- Store and retrieve key-value pairs in an object store.

- Delete key-value pairs from an object store.

- Retrieve Object Store usage statistics for your organization.

- Object Store provides these APIs:

Object Store API

Object Store Stats API