In order to most easily store Mule application logs ONLY in Splunk, how must Mule application logging be configured in Runtime Manager, and where should the log4j2 splunk appender be defined?

An organization will deploy Mule applications to Cloudhub, Business requirements mandate that all application logs be stored ONLY in an external splunk consolidated logging service and NOT in Cloudhub.

In order to most easily store Mule application logs ONLY in Splunk, how must Mule application logging be configured in Runtime Manager, and where should the log4j2 splunk appender be defined?
A . Keep the default logging configuration in RuntimeManager
Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manager to support at Mule application deployments.
B . Disable Cloudhub logging in Runtime Manager
Define the splunk appender in EACH Mule application’s log4j2.xml file
C . Disable Cloudhub logging in Runtime Manager
Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manger to support at Mule application deployments.
D . Keep the default logging configuration in Runtime Manager Define the Splunk appender in EACH Mule application log4j2.xml file

View Answer

Answer: B

Explanation:

By default, CloudHub replaces a Mule application’s log4j2.xml file with a CloudHub log4j2.xml file. In CloudHub, you can disable the CloudHub provided Mule application log4j2 file. This allows integrating Mule application logs with custom or third-party log management systems