QUESTION: 37

A new Mule application under development must implement extensive data transformation logic. Some of the data transformation functionality is already available as external transformation services that are mature and widely used across the organization; the rest is highly specific to the new Mule application.
The organization follows a rigorous testing approach, where every service and application must be extensively acceptance tested before it is allowed to go into production.
What is the best way to implement the data transformation logic for this new Mule application while minimizing the overall testing effort?

Implement and expose all transformation logic as mlaoservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application
Implement transformation logic in the new Mute application using DataWeave, replicating the transformation logic of existing transformation services
Extend the existing transformation services with new transformation logic and Invoke them from the new Mule application
Implement transformation logic in the new Mute application using DataWeave, invoking existing transformation services when possible

Answer(s): D

Explanation:

Correct answer is Implement transformation logic in the new Mule application using DataWeave, invoking existing transformation services when possible. * The key here minimal testing effort, "Extend existing transformation logic" is not a feasible option because additional functionality is highly specific to the new Mule application so it should not be a part of commonly used functionality. So this option is ruled out. * "Implement transformation logic in the new Mule application using DataWeave, replicating the transformation logic of existing transformation services" Replicating the transformation logic of existing transformation services will cause duplicity of code. So this option is ruled out. * "Implement and expose all transformation logic as microservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application" as question specifies that the transformation is app specific and wont be used outside

Reveal Solution Next Question

QUESTION: 38

A Mule application uses the Database connector.
What condition can the Mule application automatically adjust to or recover from without needing to restart or redeploy the Mule application?

One of the stored procedures being called by the Mule application has been renamed
The database server was unavailable for four hours due to a major outage but is now fully operational again
The credentials for accessing the database have been updated and the previous credentials are no longer valid
The database server has been updated and hence the database driver library/JAR needs a minor version upgrade

Answer(s): B

Explanation:

* Any change in the application will require a restart except when the issue outside the app. For below situations , you would need to redeploy the code after doing necessary changes
-- One of the stored procedures being called by the Mule application has been renamed. In this case, in the Mule application you will have to do changes to accommodate the new stored procedure name.
-- Required redesign of Mule applications to follow microservice architecture principles. As code is changed, deployment is must
-- If the credentials changed and you need to update the connector or the properties.
-- The credentials for accessing the database have been updated and the previous credentials are no longer valid. In this situation you need to restart or redeploy depending on how credentials are configured in Mule application.
* So Correct answer is The database server was unavailable for four hours due to a major outage but is now fully operational again as this is the only external issue to application.

Reveal Solution Next Question

QUESTION: 39

Refer to the exhibit.

Anypoint Platform supports role-based access control (RBAC) to features of the platform. An organization has configured an external Identity Provider for identity management with Anypoint Platform.
What aspects of RBAC must ALWAYS be controlled from the Anypoint Platform control plane and CANNOT be controlled via the external Identity Provider?

Controlling the business group within Anypoint Platform to which the user belongs
Assigning Anypoint Platform permissions to a role
Assigning Anypoint Platform role(s) to a user
Removing a user's access to Anypoint Platform when they no longer work for the organization

Answer(s): B

Explanation:

* By default, Anypoint Platform performs its own user management
– For user management, one external IdP can be integrated with the Anypoint Platform organization (note: not at business group level)
– Permissions and access control are still enforced inside Anypoint Platform and CANNOT be controlled via the external Identity Provider * As the Anypoint Platform organization administrator, you can configure identity management in Anypoint Platform to set up users for single sign-on (SSO).
* You can map users in a federated organization’s group to a role which also gives the flexibility of controlling the business group within Anypoint Platform to which the user belongs to. Also user can nbe removed from external identity management system when they no longer work for the organization. So they wont be able to authenticate using SSO to login to Anypoint Platform. * Using external identity we can no change permissions of a particular role in Mulesoft Anypoint platform.
* So Correct answer is Assigning Anypoint Platform permissions to a role

Reveal Solution Next Question

QUESTION: 40

An organization uses Mule runtimes which are managed by Anypoint Platform - Private Cloud Edition. What MuleSoft component is responsible for feeding analytics data to non-MuleSoft analytics platforms?

Anypoint Exchange
The Mule runtimes
Anypoint API Manager
Anypoint Runtime Manager

Answer(s): D

Explanation:

Correct answer is Anypoint Runtime Manager
MuleSoft Anypoint Runtime Manager (ARM) provides connectivity to Mule Runtime engines deployed across your organization to provide centralized management, monitoring and analytics reporting. However, most enterprise customers find it necessary for these on-premises runtimes to integrate with their existing non MuleSoft analytics / monitoring systems such as Splunk and ELK to support a single pane of glass view across the infrastructure.
* You can configure the Runtime Manager agent to export data to external analytics tools.
Using either the Runtime Manager cloud console or Anypoint Platform Private Cloud Edition, you can:
--> Send Mule event notifications, including flow executions and exceptions, to Splunk or ELK.
--> Send API Analytics to Splunk or ELK. Sending data to third-party tools is not supported for applications deployed on CloudHub.
You can use the CloudHub custom log appender to integrate with your logging system.

Reference:

https://docs.mulesoft.com/runtime-manager/
https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-release-notes

Additional Info:
It can be achieved in 3 steps:
1) register an agent to a runtime manager,
2) configure a gateway to enable API analytics to be sent to non MuleSoft analytics platform (Splunk for ex.) – as highlighted in the following diagram and
3) setup dashboards.

Reveal Solution Next Question

MuleSoft Certified Integration Architect - Level 1 MCIA-LEVEL-1 Exam

QUESTION: 37

Explanation:

QUESTION: 38

Explanation:

QUESTION: 39

Explanation:

QUESTION: 40

Explanation:

Reference:

MuleSoft Certified Integration Architect - Level 1
MCIA-LEVEL-1 Exam