Which line of code should a developer add for custom category debug logging?

Logger.getLogger( " contact " )returns a logger associated with the custom categorycontact. Invoking.debug()on that logger writes the message at DEBUG severity under the specified category, assuming the corresponding category configuration permits DEBUG logging.

Salesforce ' sdw.system.LoggerAPI documents the one-argumentgetLogger(String)method as returning the logger for the supplied category. It also exposes DEBUG, INFO, WARN, ERROR, and other severity operations on the resulting logging object.

Option B uses the static root-style debug call and therefore does not explicitly bind the entry to the requested custom category. Option A is invalid becauseLogger.customLogger()is not a supported Script API method.

Category-based logging is useful for service integrations because Business Manager administrators can selectively increase diagnostic verbosity for a specific subsystem such ascontactwithout globally enabling excessive DEBUG output. Category rules can also be hierarchical, allowing narrower categories such ascontact.submitorcontact.response.

Study Guide reference:Application Development —dw.system.Logger,getLogger(), custom logging categories, DEBUG severity, and Service Framework diagnostics.

===============