Free Salesforce Comm-Dev-101 Practice Exam with Questions & Answers | Set: 5

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().

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

The Request Log usesin-memory loggingon supported non-production instances. The " Log Files " checkboxes control whether a particular severity is persisted into a physical custom log file; they are not required merely to make the message visible in the Request Log Viewer.

However, the category filter still matters.myLogCategoryis currently configured at INFO, so DEBUG—the lower-severity level—is filtered out. The developer therefore must change the category ' s threshold toDEBUG. Salesforce explains that configured levels represent minimum severity and that DEBUG in-memory logging supports theShow Request Logfeature without necessarily creating a debug log file.

Checking the DEBUG target would generate persistentcustomdebugoutput where supported, but that is separate from the stated requirement to inspect the Request Log. Therefore option C performs an unnecessary operation and option B does not change the category threshold.

Study Guide reference:Application Development — Custom Log Settings, category thresholds, DEBUG severity, in-memory logging, and Storefront Toolkit Request Log.

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

< isif > is appropriate forconditional presentation logicinside an ISML template. Showing or hiding a page fragment according to information already provided to the view—such as whether the current shopper is authenticated—is exactly the kind of lightweight rendering decision for which < isif > is intended.

Salesforce explicitly states that < isif > , < iselseif > , and < iselse > provide conditional template constructs but should containno business logic, only conditional visualization of data. SFRA customization guidance reinforces this architectural separation by stating that business logic generally does not belong inapp_storefront_basetemplates; templates should concentrate on rendering.

Option B therefore violates SFRA separation-of-concerns practices because involved business logic belongs in controllers, models, helpers, or services. Option C is also unsuitable because routing and redirects are HTTP response-control operations that should be performed by the controller rather than an ISML presentation template.

Study Guide reference:Application Development — ISML conditional rendering, < isif > , template responsibilities, controllers, and separation of business logic from presentation.

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

A storefront filter is represented in B2C Commerce product search as asearch refinement. Therefore, after creating or selecting an appropriate product attribute, the administrator must create a Search Refinement Definition that associates the refinement with that attribute and the appropriate category/search context.

Merely marking an attribute searchable is not equivalent to defining it as a refinement. " Searchable " primarily determines participation in keyword-search behavior, while a refinement definition instructs the search system to expose attribute values as shopper-selectable filters. The attribute must also contain values on relevant products and be represented in the search index for the refinement to produce useful values.

Changingproductsearchrefinebar.ismlis not normally required. SFRA retrieves available refinements dynamically from the Product Search Model, so configured refinements can appear through the standard refinement components without hard-coding each attribute into the template.

Salesforce confirms that custom Product attributes can be created forsite search, search refinements, or sorting rules, demonstrating that refinement configuration is a distinct use of the attribute.

Study Guide reference:Data Management Using Business Manager Usage — Search Refinement Definitions, custom Product attributes, search indexing, and storefront product filtering.

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

CallingsetFilteredByFolder(false)tells theContentSearchModelthat search results mustnot be restricted by folder membership. This is specifically important for Page Designer because Page Designer pages and components are persisted as content-related objects but can exist outside the conventional folder structure used for ordinary content assets.

Salesforce ' s Script API states explicitly thatsetFilteredByFolder(false)must be used to return content assets that don ' t belong to a folder, including Page Designer content. The SFRA Page Designer development documentation uses the same statement insetupContentSearchso that Page Designer content can participate in storefront content search.

Option B reverses the actual behavior: the method isn ' t extending the model to add folder filtering; it is disabling folder filtering. Option C is likewise opposite to the purpose. The change broadens the searchable content population rather than preventing pages or components from appearing.

Additional Page Designer attributes still need the appropriate searchable metadata where attribute-value searching is required, but removing the folder restriction is the necessary step for discovering otherwise un-foldered Page Designer content.

Study Guide reference:Application Development — Page Designer,ContentSearchModel, storefront content search, searchHelpers, and searchable Page Designer content.

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

A task-oriented custom job step controls its execution result by returning adw.system.Statusobject. BecauseNO_FILES_FOUNDis explicitlynot an error condition, the status object ' s severity must beStatus.OK, withNO_FILES_FOUNDsupplied as the custom status code.

Salesforce ' s custom-job-step documentation states that a task-oriented script module can returndw.system.Statusto control the step ' s exit status. When the Status object ' s error flag is false and its code is a custom value, that custom value becomes the step status and job processing can continue unless the job flow defines a transition for it.

Option A returns an arbitrary object rather than a B2C CommerceStatus. Option C similarly returns a plain JavaScript object. Salesforce specifically notes that if a script returns an object that isnotadw.system.Status, the Job Framework treats the execution as ordinaryOK; the custom code isn ' t established through that object.

new Status(Status.OK, ' NO_FILES_FOUND ' )is therefore the correct implementation.

Study Guide reference:Application Development — Job Framework, custom job steps,steptypes.json,dw.system.Status, custom exit codes, and task-oriented script modules.

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