MuleSoft MCIA - Level 1 Practice Test - Questions Answers, Page 4

Answer: XSD In this approach to developing a web service, you begin with

Explanation:an XML schema (XSD file) that defines XML data structures to be used as parameters and return types in the web service operations.

----------------------------------------------------------------------------------------------------------------- Reference:

https://www.w3schools.com/xml/schema_intro.asp

* "Create a Mule domain project that maintains the credentials as Mule domain-shared resources" is wrong as domain project is not supported in Cloudhub

* We should Avoid Creating duplicates in each Mule application but below two options cause duplication of credentials - Store the credentials in properties files in a shared folder within the organization's data center. Have the Mule applications load properties files from this shared location at startup - Segregate the credentials for each backend system into environment-specific properties files. Package these properties files in each Mule application, from where they are loaded at startup So these are also wrong choices

* Credentials service is the best approach in this scenario. Mule domain projects are not supported on CloudHub.

Also its is not recommended to have multiple copies of configuration values as this makes difficult to maintain Use the Mule Credentials Vault to encrypt data in a .properties file. (In the context of this document, we refer to the .properties file simply as the properties file.) The properties file in Mule stores data as key-value pairs which may contain information such as usernames, first and last names, and credit card numbers. A Mule application may access this data as it processes messages, for example, to acquire login credentials for an external Web service. However, though this sensitive, private data must be stored in a properties file for Mule to access, it must also be protected against unauthorized ñ and potentially malicious ñ use by anyone with access to the Mule application

Correct answer is Database polling continues Only HTTP requests sent to the remaining nodecontinue to be accepted. : Architecture descripted in the question could be described asfollows.When node 1 is down , DB polling will still continue via node 2 . Also requests which arecoming directly to node 2 will also be accepted and processed in BAU fashion. Only thing that wontwork is when requests are sent to Node 1 HTTP connector. The flaw with this architecture is HTTPclients are sending HTTP requests directly to individual cluster nodes. By default, clustering Muleruntime engines ensures high system availability. If a Mule runtime engine node becomesunavailable due to failure or planned downtime, another node in the cluster can assume theworkload and continue to process existing events and messages

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.

* An object store is a facility for storing objects in or across Mule applications. Mule uses object stores to persist data for eventual retrieval.

* Mule provides two types of object stores:

1) In-memory store ñ stores objects in local Mule runtime memory. Objects are lost on shutdown of the Mule runtime.

2) Persistent store ñ Mule persists data when an object store is explicitly configured to be persistent.

In a standalone Mule runtime, Mule creates a default persistent store in the file system. If you do not specify an object store, the default persistent object store is used.

MuleSoft Reference: https://docs.mulesoft.com/mule-runtime/3.9/mule-object-stores

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

* 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.

* 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

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/runtimemanager-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.