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

If a service is being classified as unavailable because legitimate responses are taking longer than the configured timeout, increasing the service timeout can reduce timeout-generated failures. B2C Commerce service profiles define the number of milliseconds the platform waits for a service response before treating the operation as an error.

Salesforce ' s Service Framework documentation states that the configured timeout is used for connection and socket operations. If no response arrives within the configured interval, the service operation fails. Thedw.svc.ResultAPI further identifiesTIMEOUTas an explicit reason forSERVICE_UNAVAILABLE.

Option B changes error-propagation behavior;throwOnErrordetermines how a failed result is surfaced to application code, but it does not make the external service more available. Option C can improve exception handling and prevent uncaught application failures, but wrapping the call intry/catchdoes not alter Service Framework availability metrics or prevent timeouts.

The timeout should still be increased cautiously. Excessive timeouts can worsen shopper-facing latency and interact poorly with circuit-breaker behavior.

Study Guide reference:Application Development — Service Framework, service profiles, connection/socket timeouts, Service Status monitoring, and service availability.

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

The B2C Commerce Service Framework provides native support for mocked services, so the developer should implement themockFullcallback and configure the service to operate in mock mode. This enables application development and testing before the external provider exposes the real endpoint.

Salesforce documents that when a service is operating in mocked mode, the framework can use its configured mock callback instead of making the live network request.mockFullis particularly useful because it can replace the full service execution sequence and return a controlledResultsuitable for testing dependent application logic.

A custom site preference is unnecessary because the Service Framework already contains an administrative mechanism for selecting mocked operation. Introducing application-specific conditionals or preferences duplicates platform functionality and makes the integration harder to administer consistently.

This approach also preserves separation of concerns: application code continues calling the same service abstraction, while environment configuration determines whether the real provider or the mock implementation is used. When the remote API becomes available, the service can be switched from mocked to live behavior without redesigning its callers.

Study Guide reference:Application Development — LocalServiceRegistry, Service Framework callbacks, mocking external integrations, and service testing.

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

CustomObjectMgr.createCustomObject()expects two parameters for this use case: thecustom object type IDfollowed by thekey valuefor the new instance. Salesforce defines the relevant signature as:

createCustomObject(type, keyValue)

Therefore, ' NewsletterSubscription ' is supplied first as the custom object type andnewsletterForm.email.valueis supplied second as the unique key value. This makes option A correct.

The key attribute has already been established in the metadata definition of theNewsletterSubscriptioncustom object type. The API therefore does not require the developer to pass the literal attribute nameemailas a separate parameter. This makes option C invalid. Option B reverses the expected argument order and would attempt to interpret the email value as the custom object type name.

Custom-object keys must be unique within the object ' s applicable storage scope. Because creation changes persistent business data, the operation must also execute within an appropriate transaction when performed through server-side application code.

Study Guide reference:Application Development —dw.object.CustomObjectMgr, custom-object creation, custom-object keys, persistent business objects, and transaction handling.

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

A cartridge that registers B2C Commerce hooks traditionally uses apackage.jsonfile at the cartridge root and points its " hooks " property to the hook registration file located under the cartridge ' s scripts directory. The correct relative path is therefore:

" ./cartridge/scripts/hooks.json "

Salesforce ' s SFRA documentation describes the hook-registration pattern as a root-levelpackage.jsonaccompanied byhooks.jsonundercartridge/scripts. The cartridge containing the implementation must also participate in the relevant site ' s cartridge configuration for the extension to be available.

Option B is not valid JSON syntax because JSON property names and string values must be quoted. Option C uses the wrong relative location;scriptsis below the cartridge directory, not directly below the package root.

Thehooks.jsonfile then maps extension-point names to implementing script modules. Runtime code can invoke those extension points through mechanisms such asHookMgr.callHook(), while the registration metadata tells B2C Commerce which implementation is associated with each hook.

Study Guide reference:Application Development — hooks,package.json,hooks.json, extension-point registration, cartridge structure, and extensibility architecture.

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

Cache partitions are managed as part of the storefront site ' s cache configuration rather than through ordinary merchant Site Preferences. The appropriate administrative path is therefore the site ' s configuration underAdministration > Sites > Manage Sites, followed by the relevant site ' sCacheconfiguration.

Salesforce ' s Business Manager site-administration documentation identifiesManage Sitesas the area used to administer storefront-site configuration and exposes site-specific configuration after an administrator selects the applicable site.

A cache partition allows related cached content to be grouped so that invalidation can target a more restricted scope instead of unnecessarily clearing the entire page cache. For a frequently edited home page, isolating its cached content can reduce the performance impact of merchant changes because unrelated cached storefront pages do not need to be invalidated at the same time.

Option B uses an incorrect administrative hierarchy, while option C incorrectly treats cache partition configuration as a normal site preference.

The developer must still ensure that the application uses the intended partition consistently in its cache behavior; creating the partition alone does not automatically reassign every cacheable response.

Study Guide reference:B2C Commerce Setup — site cache administration, cache partitions, targeted invalidation, and Business Manager site configuration.

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

The service credential is the correct B2C Commerce configuration object for an environment-specific service endpoint. Service credentials can hold connection information such as the URL and, where applicable, authentication credentials. This allows administrators or developers to change the sandbox endpoint through Business Manager without modifying cartridge code.

Salesforce ' s Service Framework documentation describes the service configuration as being associated with a service profile and credential, and the credential contains the service URL used to connect to the remote system. The API representation ofServiceCredentiallikewise exposes the URL as part of that configuration.

Creating a custom global preference for the endpoint would duplicate functionality already provided by the platform and would require additional application code to read and apply that preference. Option C also confuses service monitoring/status functionality with endpoint configuration. The service-status area is intended for operational information and service behavior rather than being the canonical storage location for the configured endpoint.

Using the credential URL field keeps connectivity information externalized from source code and allows different URLs to be maintained independently in development, staging, and production environments.

Study Guide reference:B2C Commerce Setup — Service Framework configuration, services, profiles, credentials, and environment-specific endpoints.

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

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.

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

The B2C Commerce Service Framework provides arate limiterspecifically for controlling the maximum number of outbound service calls permitted during a defined time interval. This configuration belongs to theService Profileassociated with the service. The profile exposes values equivalent to the maximum permitted calls and the rate-limit interval in milliseconds.

Salesforce documents that the Service Profile controls timeout, rate-limit, and circuit-breaker behavior. The rate limiter is evaluated before every service invocation. If the configured maximum number of calls has already been reached within the interval, B2C Commerce prevents another remote request and returns service-unavailable behavior instead.

This mechanism counts service invocations irrespective of whether the previous remote calls succeeded or failed, which directly matches the requirement to restrict overall calls per second. A circuit breaker is different: it reacts specifically to accumulated failures. Option C incorrectly treats this as a general platform quota, while option A refers to configuration that is not the standard Service Framework mechanism.

Study Guide reference:Application Development — Service Framework, Service Profiles, rate limiting, circuit breakers, and external integration governance.

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

ThePayment Methodsconfiguration is the appropriate Business Manager location because payment-method applicability can be restricted according to criteria that include the shopper ' s billing country. The merchant can therefore configure the relevant payment method so that it is not available where the country condition excludes Denmark.

Salesforce ' s Business Manager documentation for payment methods describes configuration controls for availability based on customer groups, billing countries, and order-amount conditions. The underlying payment-management logic evaluates these configured applicability rules when determining which methods are available for the current basket and shopper context.

A payment processor represents the back-end processing integration or transaction handler associated with one or more payment methods; it is not the primary mechanism for defining a country ' s storefront eligibility. “Locale Payments” is not the appropriate Business Manager module for this requirement.

This separation is important: thepayment methoddescribes whether a shopper can select a payment option under particular storefront conditions, while thepayment processordetermines how an accepted payment is technically processed.

Study Guide reference:Data Management Using Business Manager Usage — payment methods, payment applicability, billing-country restrictions, payment processors, and checkout configuration.

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

Among these choices, aproduct custom attributeprovides the cleanest and most maintainable data-driven solution. B2C Commerce allows the Product system object to be extended with custom attributes, enabling merchandising metadata such as a permitted region, market code, or eligibility classification to live with the product data rather than being hard-coded in controller logic.

The storefront or search-layer implementation can then evaluate that attribute against the shopper ' s applicable regional context and filter products accordingly. This approach scales better than embedding specific product IDs or regional rules directly into scripts.

Creating an entire catalog for every region may be justified when each market has substantially different assortments, categories, navigation, prices, or merchandising operations, but it is excessive for a requirement centered on a specific product ' s regional eligibility. Option C also places business data in code, making merchant maintenance and expansion harder.

The custom attribute should be modeled with an appropriate data type and, where needed, indexed if search-result filtering is involved.

Study Guide reference:Data Management Using Business Manager Usage — Product system object extensions, custom attributes, merchandising metadata, search filtering, and regional product eligibility.

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