MCIA-Level-1 무료 덤프문제 온라인 액세스

An insurance company has an existing API which is currently used by customers. API is deployed to customer hosted Mule runtime cluster. The load balancer that is used to access any APIs on the mule cluster is only configured to point to applications hosted on the server at port 443.
Mule application team of a company attempted to deploy a second API using port 443 but the application will not start and checking logs shows an error indicating the address is already in use.
Which steps must the organization take to resolve this error and allow customers to access both the API's?

• A.Move the HTTP listener configurations from the API's and package them in a mule domain project using port 443
• B.Change the base path of the HTTP listener configuration in the second API to a different one from the first API
• C.Set the HTTP listener of the second API to use different port than the one used in the first API
• D.Set HTTP listener configuration in both API's to allow for connections from multiple ports

A project uses Jenkins to implement CI/CD process. It was observed that each Mule package contains some of the Jenkins files and folders for configurations of CI/CD jobs.
As these files and folders are not part of the actual package, expectation is that these should not be part of deployed archive.
Which file can be used to exclude these files and folders from the deployed archive?

• A.mulelnclude
• B._muleExclude
• C._unTrackMule
• D.muleignore

According to MuteSoft, which principle is common to both Service Oriented Architecture (SOA) and API-led connectivity approaches?

• A.Service statefulness
• B.Service centralization
• C.Service reusability
• D.Service interdependence

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, 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.
• 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, 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.

Mule application is deployed to Customer Hosted Runtime. Asynchronous logging was implemented to improved throughput of the system. But it was observed over the period of time that few of the important exception log messages which were used to rollback transactions are not working as expected causing huge loss to the Organization. Organization wants to avoid these losses. Application also has constraints due to which they cant compromise on throughput much. What is the possible option in this case?

• A.Mixed configuration of asynchronous or synchronous loggers should be used to log exceptions via synchronous way
• B.Persistent memory storage should be used in such scenarios
• C.Logging needs to be changed from asynchronous to synchronous
• D.External log appender needs to be used in this case