MuleSoft MCIA-Level-1 valid exam dumps : MuleSoft Certified Integration Architect - Level 1

What aspect of logging is only possible for Mule applications deployed to customer-hosted Mule runtimes, but NOT for Mule applications deployed to CloudHub?

• A. To change tog4j2 tog levels in Anypoint Runtime Manager without having to restart the Mule application
• B. To send Mule application log entries to Splunk
• C. To directly reference one shared and customized log4j2.xml file from multiple Mule applications
• D. To log certain messages to a custom log category

An organization plans to extend its Mule APIs to the EU (Frankfurt) region.
Currently, all Mule applications are deployed to CloudHub 1.0 in the default North American region, from the North America control plane, following this naming convention: {API-name}-{environment} (for example, Orderssapi-dev, Orders-sapi--qa, Orders-sapi--prod, etc.).
There is no network restriction to block communications between APIs.
What strategy should be implemented in order to deploy the same Mule APIs to the CloudHub 1.0 EU region from the North America control plane, as well as to minimize latency between APIs and target users and systems in Europe?

• A. In Runtime Manager, for each Mule application deployment, leave the Region property blank (default) and change the Mule application name to {API-name}-
  {environment).de-cl.
  Communicate the new urls {API-name}-{environment}.de-ci1.cloudhub.io to the consuming API clients in Europe.
• B. In Runtime Manager, for each Mule application deployment, set the Region property to EU (Frankfurt) and reuse the same Mule application mame as in the North American region.
  Communicate the new urls {API-name}-{environment}.de-ci.cloudhub.io to the consuming API clients In Europe.
• C. In API Manager, leave the Region property blank (default) to deploy an API proxy named
  {API-name}~proxy~- (environment}.de-cl for each Mule application.
  Communicate the new url {API-name}-proxy-{environment}.de-cl.cloudhub.io to the consuming API clients in Europe.
• D. In API Manager, set the Region property to EU (Frankfurt) to create an API proxy named {API-name}-proxy-{environment} for each Mule application.
  Communicate the new url {API-name}-proxy-{environment}.de-c1.cloudhub.io to the consuming API clients In Europe.

A Mule application uses APIkit for SOAP to implement a SOAP web service. The Mule application has been deployed to a CloudHub worker in a testing environment.
The integration testing team wants to use a SOAP client to perform Integration testing. To carry out the integration tests, the integration team must obtain the interface definition for the SOAP web service.
What is the most idiomatic (used for its intended purpose) way for the integration testing team to obtain the interface definition for the deployed SOAP web service in order to perform integration testing with the SOAP client?

• A. Retrieve the OpenAPI Specification file(s) from API Manager
• B. Retrieve the RAML file(s) from the deployed Mule application
• C. Retrieve the WSDL file(s) from the deployed Mule application
• D. Retrieve the XML file(s) from Runtime Manager

A large life sciences customer plans to use the Mule Tracing module with the Mapped Diagnostic Context (MDC) logging operations to enrich logging in its Mule application and to improve tracking by providing more context in the Mule application logs. The customer also wants to improve throughput and lower the message processing latency in its Mule application flows.
After installing the Mule Tracing module in the Mule application, how should logging be performed in flows in Mule applications, and what should be changed In the log4j2.xml files?

• A. In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.
  In log4j2.xmI files, change the appender's pattern layout to use the %MDC placeholder and then assign the appender to an AsyncLogger element.
• B. In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.
  In log4j2.xml files, change the appender's pattern layout to use %MDC and then assign the appender to a Logger or Root element.
• C. In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.
  In log4j2.xmI files, change the appender''s pattern layout to use %asyncLogger placeholder and then assign the appender to an AsyncLogger element.
• D. In the flows, wrap Logger components in Async scopes. In log4j2.xmI files, change the appender's pattern layout to use the %asyncLogger placeholder and then assign the appender to a Logger or Root element.

As a part of project requirement, Java Invoke static connector in a mule 4 application needs to invoke a static method in a dependency jar file. What are two ways to add the dependency to be visible by the connectors class loader?
(Choose two answers)

• A. Use Maven command to include the dependency jar file when packaging the application
• B. Update mule-artefact.json to export the Java package
• C. In the Java Invoke static connector configuration, configure a path and name of the dependency jar file
• D. Configure the dependency as a shared library in the project POM
• E. Add the dependency jar file to the java classpath by setting the JVM parameters