MuleSoft Certified Integration Architect – Level 1 — Question 55
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?
Answer options
- A. Disable CloudHub logging in Runtime Manager Define the Splunk appender in ONE global log4j2.xml file that is uploaded once to Runtime Manager to support all Mule application deployments
- B. Keep the default logging configuration in Runtime Manager Define the Splunk appender in ONE global log4j2.xml file that is uploaded once to Runtime Manager to support all Mule application deployments
- C. Disable CloudHub logging in Runtime Manager Define the Splunk appender in EACH Mule application's log4j2.xml file
- D. Keep the default logging configuration in Runtime Manager Define the Splunk appender in EACH Mule application's log4j2.xml file
Correct answer: C
Explanation
The correct answer, C, ensures that each Mule application's logging is configured individually to direct logs to Splunk, thereby meeting the requirement to avoid CloudHub logs. Options A and B do not meet the requirement of storing logs only in Splunk, while option D does not disable CloudHub logging, which is necessary for compliance with the business requirements.