B2C Commerce imposes a daily size quota on custom logs to prevent unlimited logging from consuming storage or degrading instance performance. Once the applicable custom-log size limit is reached, additional custom logging issuspended until the next logging dayrather than rolling immediately to another unlimited file.

Current Salesforce documentation states that each application server can write up to the defined daily amount into the custom debug, info, fatal, error, and warn logs, and that logging is suspended until the next day once the limit is reached. The logging day is based on GMT.

Option A describes normal archival/retention handling rather than quota behavior. Existing log files can later be compressed and moved according to retention policy, but reaching the daily file-size quota doesn ' t simply bypass the quota by opening another unrestricted file. Option B is also incorrect because B2C Commerce doesn ' t delete the current log merely to continue writing.

Developers should therefore avoid excessive diagnostic logging, particularly in frequently executed storefront code, and choose appropriate log levels and categories.

Study Guide reference:Application Development — custom logging quotas, log-file management, Business Manager log settings, WebDAV logs, and production diagnostics.

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