Order failure informationis appropriate operational data for diagnostic logging when it is implemented without exposing protected shopper information. Checkout failures, error codes, integration outcomes, or non-sensitive order-processing context can provide developers and support teams with the information needed to diagnose failed purchases.

Passwords must never be written to application logs. Likewise, complete credit-card information is sensitive payment data subject to stringent PCI controls and should not be placed into custom log files. Salesforce specifically warns developers to filter sensitive or private data—such as credit-card numbers—from service logs, and B2C Commerce payment APIs treat cardholder and financial information as PCI-sensitive data.

Option B would create an obvious credential-disclosure risk because anyone with log access could potentially recover customer authentication data. Option C would unnecessarily persist cardholder information outside the platform ' s protected payment-data handling mechanisms.

The proper logging strategy captures enough contextual data to diagnose checkout problems while excluding passwords, full payment credentials, authentication secrets, and similar sensitive values.

Study Guide reference:Application Development — secure logging, checkout diagnostics, PCI considerations, payment data handling, and protection of customer credentials.

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

B2C Commerce logging uses ahierarchical category model. When WARN is enabled onproduct, WARN and all higher-severity levels are available forproductand descendant categories. A more specific configuration onproduct.importcan then lower that subcategory ' s threshold to DEBUG.

Salesforce gives essentially this exact example in its server-side JavaScript documentation: when WARN is enabled forproductand DEBUG is configured forproduct.import, WARN and ERROR are logged for the parent and its subcategories, whileproduct.importadditionally logs DEBUG and INFO.

The reason is that the configured level is aminimum severity threshold. DEBUG is lower than INFO, WARN, ERROR, and FATAL, so selecting DEBUG permits the entire severity range for that category. The more specific child-category setting overrides the inherited parent threshold for that branch.

This hierarchical design lets administrators keep broad logging conservative while temporarily increasing diagnostic detail for one subsystem such as product import processing.

Study Guide reference:Application Development — custom logging hierarchy, parent/child categories, log-level inheritance, DEBUG, INFO, WARN, and granular diagnostics.

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

The two-argument overload ofLogger.getLogger()has the signaturegetLogger(fileNamePrefix, category). Therefore, inLogger.getLogger( " products " , " export " ),productsis the developer-defined filename prefix andexportis the logging category.

Salesforce documents that custom application log files begin withcustom, while the suppliedfileNamePrefixidentifies the named custom log file. Consequently, the resulting filename begins withcustom-products, making option B correct. The category valueexportcontrols filtering through the custom-log category hierarchy but does not replace the filename prefix.

The configured root level of INFO also permits thislog.info()message because INFO is at the configured threshold. Higher-severity WARN, ERROR, and FATAL entries would likewise pass the root filter unless a more specific category rule superseded it.

This distinction between filename prefix and category is significant in production diagnostics. The prefix controls which named custom file receives the entries, while categories provide hierarchical filtering and operational control through Business Manager.

Study Guide reference:Application Development —dw.system.Logger, custom named logs, filename prefixes, categories, and log-level filtering.

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

SFRA storestemplate resource bundlesin the cartridge ' stemplates/resourcesdirectory. Locale selection is represented in the propertiesfilename, rather than by creating a separatefrsubdirectory for ordinary SFRA resource bundles.

For example, a default bundle might be:

account.properties

while its French translation would be:

account_fr.properties

Both belong under:

cartridge/templates/resources

Salesforce ' s localization documentation explicitly states that template resource bundles are stored in/templates/resourcesand gives examples such asaccount_en_GB.properties,account_en_US.properties, andaccount_en.properties. Thedw.web.Resourcedocumentation likewise describes resource bundles as properties files with a common name located in thetemplate/resourcesdirectory.

Option B omits the required template-resource location. Option C incorrectly assumes that locale resolution for properties bundles uses a dedicatedfrfolder. Locale-specifictemplatescan use locale directories, but localized properties bundles follow the filename-suffix convention.

This separation permits one common set of ISML templates to reference resource keys while B2C Commerce automatically resolves the appropriate translated properties bundle for the active request locale.

Study Guide reference:Application Development — localization, template resource bundles,.propertiesfiles, locale fallback, andResource.msg().

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

Page-Includeis explicitly protected withserver.middleware.include, meaning it is designed to execute as aremote include, not as a shopper ' s top-level browser request. Salesforce ' s SFRA Page controller documentation describesPage-Includeas an endpoint triggered when content assets are embedded within a rendered page and identifiesserver.middleware.includeas its middleware.

The appropriate ISML mechanism is therefore:

< isinclude url= " ${URLUtils.url( ' Page-Include ' , ' cid ' , ' about-us ' )} " >

Using theurlattribute makes < isinclude > perform a remote include. Salesforce documents that this causes the web adapter to execute another request and insert the endpoint ' s returned content into the surrounding template.

Option A creates a shopper-clickable top-level URL, which fails the include middleware condition and explains the error described in the scenario. Option C is not the remote-include tag.

Study Guide reference:Application Development —Page-Include,server.middleware.include, remote includes, < isinclude url > , and SFRA content rendering.

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

WARNis the appropriate logging severity when an operation completed but produced an unexpected condition that may warrant investigation. It communicates that the application has encountered an abnormal or potentially consequential situation without falsely classifying the request as a complete processing failure.

Salesforce ' s B2C Commerce logging guidance identifies warning logs as appropriate for custom jobs, payment integrations, imports, and application code conditions that can affect users. WARN output is also normally available in operational logging, making it more appropriate than DEBUG for a potentially significant production condition.

DEBUGis intended for detailed development-oriented diagnostics and is not available as persistent debug file logging on production in the same manner.ERRORshould generally be reserved for an operation that actually failed, an exception, or another state requiring error-level treatment.

For Service Framework integrations, logs should contain useful but sanitized diagnostic context. Salesforce strongly recommends filtering requests and responses so credentials, payment data, tokens, and personal information are not exposed.

Study Guide reference:Application Development — Logger severity, WARN messages, Service Framework diagnostics, secure service logging, and troubleshooting external integrations.

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

Logger.getLogger( ' contact ' )creates or retrieves a logger associated with thecontactcategory. Calling.debug()on that logger writes the message at DEBUG severity, subject to the configured category and log-target rules.

B2C Commerce custom logging uses hierarchical category names patterned after log4j. Categories can be activated at particular severity levels inAdministration > Operations > Custom Log Settings. Salesforce explains that child categories inherit applicable settings from their parent categories unless they have more specific configuration.

Option B uses the generic staticLogger.debug()call and does not explicitly associate the statement with the required customcontactcategory. Option C refers to a nonexistentcustomLogger()API.

The category-specific approach is operationally superior when troubleshooting a third-party integration because administrators can selectively enable DEBUG logging forcontactwithout enabling extensive debugging across unrelated application code. Once the issue is diagnosed, that category ' s verbosity can be reduced again.

Study Guide reference:Application Development —dw.system.Logger, custom categories, DEBUG logging, Service Framework diagnostics, and hierarchical logging configuration.

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

SFRA ' s response object provides thesetViewData()method specifically for adding data to the view-data object that will be available during rendering. Therefore, option A follows the supported controller pattern: callres.setViewData()with the additional object, render the template, and then invokenext()to continue the middleware chain.

Salesforce ' s SFRA documentation explains thatsetViewData(data)adds or merges data into the response ' s view-data object. This behavior is particularly important for an appended route because earlier middleware may already have established view data.setViewData()allows the appended function to add its contribution without replacing the response object ' s internal handling.

Directly assigningres.viewData, as shown in option B, bypasses the supported response API and is not the documented SFRA mechanism. Option C is also invalid because route appending expects a middleware function; data cannot be supplied by chaining an object through.append()after rendering.

This pattern is central to cartridge extensibility because multiple middleware functions can progressively enrich a response while preserving previously established data and route behavior.

Study Guide reference:Application Development — SFRA controllers, response objects, middleware chains,setViewData(), and template rendering.

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

AProduct Bundlerepresents several component products that are offered together as one orderable product. Salesforce distinguishes bundles from product sets specifically on purchasing behavior: a product bundle represents products sold together, while a product set is primarily a merchandising grouping that permits customers to select and purchase the individual members.

Salesforce ' s product-type documentation characterizes a Product Bundle as a product containing several products that areonly sold together, whereas a Product Set contains products that can be purchased together or separately.

A bundle also has its own product identity and bundle pricing/availability behavior. Availability normally depends on the availability of the bundled components unless bundle-specific inventory behavior is configured. A Variation Group is fundamentally different: it groups selected variation values belonging to a base product, such as several colors or styles, and does not represent a mandatory multi-product purchase.

Therefore, when the business concept is " these items constitute one sellable group, " a Bundle is the correct product model.

Study Guide reference:Data Management Using Business Manager Usage — Product Bundles, Product Sets, product types, bundled-product availability, and catalog configuration.

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

B2C Commerce provides a dedicatedAvailability Low Ranking Thresholdsetting for exactly this search-merchandising requirement. It is configured in Business Manager under Search Preferences and specifies the availability percentage at or below which products should be pushed toward the end of search results.

Salesforce gives the example that a threshold of0.3causes products with availability of 0.3 or lower to be ranked lower in storefront search. This preserves product discoverability while prioritizing merchandise that has healthier inventory.

Option A is unnecessarily destructive and operationally inefficient. Hiding products through an hourly job changes catalog state and can create delays or merchandising side effects. It also does not distinguish between temporarily low inventory and true unavailability. Option C confuses availability ranking with Searchable Attribute boost configuration. The platform already exposes a specific preference for low-availability ranking, so custom boosting is unnecessary.

This feature is particularly useful when merchants want low-stock merchandise still discoverable but not prominently ranked, balancing inventory awareness with conversion-oriented search results.

Study Guide reference:Data Management Using Business Manager Usage — Search Preferences, Availability Low Ranking Threshold, product availability, and search-result ranking.

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