Comm-Dev-101 Exam Dumps - Salesforce Developers Questions and Answers

The required information is structured application data that is specific to one site but must move consistently from staging to production. Asite-scoped, replicable Custom Objectis therefore the correct model.

Salesforce custom-object definitions provide two relevant controls.Storage Scopedetermines whether custom-object instances are organization-wide or site-specific, whileData Replicationdetermines whether custom-object data can participate in replication between environments. Salesforce specifically documents that custom objects can be local to a site and that custom object types can be configured as replicable.

The developer can define one object per country with attributes such as country code, price book ID, flag image URL, display name, and ordering information. The storefront can query these records to construct the country selector dynamically.

Option A attempts to overload the Locale system object with business configuration that is not fundamentally locale metadata. Option C stores structured application configuration in content assets, which are primarily merchandising/content entities and would be less suitable for strongly structured programmatic lookup.

Study Guide reference:Data Management Using Business Manager Usage — Custom Objects, site-specific storage scope, data replication, structured application configuration, and multi-country storefront design.

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

Custom Object attributes must be assigned to anAttribute Groupbefore Business Manager can expose them in the Custom Object editing interface. Defining an attribute creates its metadata, but grouping controls its administrative presentation.

Salesforce explicitly states that after creating custom-object attributes, developers must add them to an Attribute Group in order to manage the custom object through Business Manager. Salesforce also notes that the custom object ' s key attribute must be included in an attribute group; otherwise, administrators cannot create instances of the custom object definition through the Custom Object module.

Option A is unrelated. Changing the data type modifies how an attribute stores information and can even destroy existing values, but it does not solve the Business Manager visibility issue. Option C confuses attribute presentation with custom-object scope and replication. Site-specific storage determines where object instances exist, while replication configuration governs movement between instances; neither causes fields to appear in the editor.

The correct workflow is therefore to define the attributes, create the appropriate Attribute Group, assign the desired fields—including the key—to the group, and then manage object instances through the site ' s Custom Objects module.

Study Guide reference:Data Management Using Business Manager Usage — Custom Object Types, Attribute Definitions, Attribute Groups, Custom Object Editor, and Business Manager metadata.

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

ThePipeline Profileris the appropriate performance-analysis tool because it reports execution statistics for storefront controllers and their underlying scripts, including hit counts, total processing time, andaverage response/run time.

Salesforce ' s performance troubleshooting documentation specifically recommends Pipeline Profiler for measuring deployed storefront-code performance and identifying expensive pipelines or controllers. The profiler presents high-level response-time information and allows the developer to drill down into individual scripts contributing to the controller ' s execution time.

This makes it appropriate for diagnosing reports that a product-details route has become slow. After identifying the expensive controller, the developer can inspect its script-level execution data to determine whether custom models, service calls, product logic, templates, or other components are contributing excessive processing time.

Request logs are useful for examining the sequence and context of individual requests but are not the principal tool for aggregating controller average processing times. The URL Request Analyzer is likewise not the intended answer for this performance metric.

Study Guide reference:Application Development — Pipeline Profiler, controller performance, average execution time, script profiling, and storefront performance troubleshooting.

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

The correct behavior is suspension of additional custom logging for the remainder of the logging day. Salesforce documents that custom log files are governed by daily size restrictions per application server. Once the permitted volume has been reached,logging is suspended until 00:00 GMT on the next day.

This limit is distinct from ordinary archival. Log files can later be compressed and moved to thelog_archivedirectory according to standard retention processing, but B2C Commerce does not bypass its daily governance limit by opening another unrestricted file.

Option C is similarly incorrect because the platform does not delete diagnostic evidence merely to obtain more writing capacity.

This behavior is particularly relevant to heavily trafficked custom controllers, jobs, import processes, and third-party integrations. Developers should avoid logging entire payloads or repetitive informational messages at high volume and should use categories and severity thresholds deliberately.

Verification correction:the source marks B for Q146, but Salesforce ' s current official Log Files documentation explicitly states that logging is suspended after the daily limit is reached.

Study Guide reference:Application Development — logging governance, custom-log limits, log suspension, archival, retention, and performance protection.

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

WARNis the appropriate severity because the operation technically succeeded, yet the result is abnormal enough to require attention and could produce undesirable side effects. A warning signals a recoverable or unexpected condition without incorrectly classifying the operation as an outright failure.

Salesforce logging guidance identifies custom WARN logs as appropriate for warnings in application areas such as integrations and payment processing that can impact users. WARN messages are also available under normal production logging configurations, making them suitable for operational conditions that administrators should be able to investigate.

DEBUG is intended for detailed development/troubleshooting information and is disabled for persistent production logging by default. It would therefore understate a potentially consequential condition. ERROR should represent an operation or state that actually failed or cannot be processed successfully; the question explicitly states that the operation succeeded.

Using the correct severity improves alerting, log filtering, and incident analysis while preventing routine recoverable situations from being mistaken for application failures.

Study Guide reference:Application Development —dw.system.Logger, WARN/DEBUG/ERROR severity, Service Framework troubleshooting, and operational logging practices.

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

In SFRA ' s MVC-style architecture, a controller owns the HTTP request/response workflow. Consequently, generating aJSON HTTP responseis an appropriate controller responsibility. The SFRA response API exposesres.json(data)specifically for this purpose and Salesforce notes that it is useful for AJAX service endpoints called by client-side code.

The other two choices describe responsibilities that belong more appropriately to the model/ViewModel layer. Salesforce explains that SFRA models obtain data from B2C Commerce Script API objects and convert those objects intopure serializable JavaScript objectssuitable for views. Models also encapsulate storefront-oriented business logic. Controllers request or coordinate the required data and pass it through the model layer rather than becoming the primary object-transformation layer themselves.

This separation improves testability and maintainability. Controllers stay focused on routing, request validation, response selection, redirects, rendering, and JSON output, while models isolate the transformation of Commerce platform objects into view-friendly structures.

Study Guide reference:Application Development — SFRA MVC architecture, controllers, ViewModels,res.json(), Script API objects, and separation of concerns.

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

For a newly added product to participate correctly in storefrontproduct search, the product must be online, marked searchable, and represented in a current product search index. Salesforce ' s official indexing documentation states that a product appears in search results only when it issearchable, online, and assigned to at least one online category. The scenario already states that the product has been added to the Storefront catalog, so the remaining examination requirements are the online/searchable flags and an updated index.

A product does not have to be a child of a master product; standalone products are completely valid B2C Commerce merchandise. A price is commercially important, but price is not the platform criterion that makes a product eligible for the search index. Product pricing is separately incorporated into search indexes from applicable price books.

Therefore, A is the technically supported choice. After catalog changes, the product index must reflect the new assignment and current searchable/online status.

Study Guide reference:Data Management Using Business Manager Usage — Product visibility, online/searchable flags, Storefront catalogs, categories, and Product Search indexing.

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

For an independent external web application, the appropriate legacy B2C Commerce integration surface is theShop API Product Search resource. The application can retrieve structured product-search results for the desired category and use that data to construct a completely different presentation layer.

Salesforce ' s OCAPI documentation defines the Shop APIGET /product_searchresource and corresponding product-search extension points. The resource returns structured Product Search Result data rather than storefront-rendered HTML. This separation is important because the new application can independently control CSS, layout, rendering technology, and interaction behavior instead of attempting to reuse or scrape the existing storefront.

Search-Showis an SFRA controller designed to render the storefront search experience. Crawling its HTML creates unnecessary coupling to existing presentation markup and is not an integration architecture. A generic category endpoint can return category metadata, but the Product Search resource is designed to obtain product listing/search results.

Current platform note: Salesforce now marks OCAPI as deprecated for new implementations and recommends SCAPI for modern headless development, but the supplied certification question is explicitly testing the Shop OCAPI architecture.

Study Guide reference:Application Development — OCAPI Shop API, Product Search, headless/external storefront integrations, structured search results, and API-based storefront development.

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

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.

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

CSRF validation must occurwhen the state-changing request is submitted, before protected business logic executes. In SFRA this is implemented as middleware in the controller ' s POST route, using the appropriate CSRF middleware—validateRequestfor standard submissions orvalidateAjaxRequestfor AJAX-based requests.

Salesforce ' s SFRA Forms documentation specifically states that CSRF protection is supplied as middleware and demonstrates CSRF checks as middleware steps. The underlyingdw.web.CSRFProtection.validateRequest()API verifies that the request contains the system-generated token and that the token has not expired.

Generating the token in the template only establishes the client-side value; it does not provide security unless the receiving POST endpoint validates it. Placing validation only in the form-display route would validate the wrong request. Performing validation in a persistence model is also too late because request security should be enforced before mutation logic is invoked.

Study Guide reference:Application Development — CSRF protection, SFRA middleware, POST routes,validateRequest,validateAjaxRequest, and secure form processing.

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