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?
To meet the requirement of storing Mule application logs ONLY in an external Splunk consolidated logging service and NOT in CloudHub, CloudHub logging must be disabled in Runtime Manager. The log4j2 Splunk appender needs to be defined in each Mule application's log4j2.xml file because there is no functionality to upload a global log4j2.xml file to Runtime Manager for all Mule applications. Each application must be individually configured to ensure logs are routed correctly to Splunk.
C. Disable CloudHub logging in Runtime Manager Define the Splunk appender in EACH Mule application's log4j2.xml file
Made the official Mulesoft practice exam and C is the correct answer
Should be C. There is nothing like global log4j configuration in runtime manager. Its either cloudhub logger or custom log4j which is set in each mulesoft application in src/main/resources folder. https://docs.mulesoft.com/mule-runtime/3.9/logging-in-mule