Salesforce Updated Comm-Dev-101 Exam Questions and Answers by artemis

B2C Commerce custom attributes are defined through the platform ' smetadata system, not dynamically declared by application JavaScript. Therefore, the first step is to create the required attribute definition in Business Manager on the appropriate extensible system object or custom-object type.

Salesforce documents the process under Administration > Site Development > System Object Types or Custom Object Types. The developer selects the target object, opens Attribute Definitions, clicks New, and defines the attribute ID, display name, and data type.

Once the attribute exists, it can be assigned to an attribute group where required for Business Manager visibility, populated through Business Manager or integrations, and accessed through the object ' scustomproperty in application code.

Option B is incorrect because source code cannot create an undeclared persistent custom attribute merely by referencing a property name. Option C also comes later because application logic needs the metadata definition to exist before reliably reading or writing the value.

The type and characteristics of the attribute should be designed carefully because changing an existing attribute ' s type can cause stored values to be lost.

Study Guide reference:Data Management Using Business Manager Usage — System Object Types, Custom Object Types, Attribute Definitions, attribute groups, and custom metadata.

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

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.

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

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.

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