Salesforce Certified Order Management Administrator Practice Test - Questions Answers, Page 6

The best way for the administrator to recommend tracking the kits so that they remain grouped together during returns in Order Management is to use custom attributes. Custom attributes are fields that can be added to objects to store additional information that is not available in standard fields. The administrator can create custom attributes for the Order Item Summary object to indicate whether an item is part of a kit, and what are the other items in the kit. This way, the kits can be easily identified and handled during returns. Verified

Reference: https://documentation.b2c.commercecloud.salesforce.com/DOC2/topic/com.demandware.dochelp/OrderManagement/Administration/AdminAttrMgrCustomAttributes.html

Two practices that are needed for a custom attribute to map into Order Management assuming the attribute has been created on the necessary objects are:

The types must match within reason. The data type of the custom attribute in Order Management must match or be compatible with the data type of the corresponding attribute in the external system, such as B2C Commerce or B2B Commerce. For example, if the attribute is a string in B2C Commerce, it must also be a string in Order Management.

The names must be an exact match. The name of the custom attribute in Order Management must be exactly the same as the name of the corresponding attribute in the external system, including capitalization and punctuation. For example, if the attribute is named ''kitItem'' in B2C Commerce, it must also be named ''kitItem'' in Order Management.

Verified

Reference: https://documentation.b2c.commercecloud.salesforce.com/DOC2/topic/com.demandware.dochelp/OrderManagement/Administration/AdminAttrMgrCustomAttributes.html

The type of relationship that exists between FulfillmentOrder and Location is Many-to-One Lookup (Location) FulfilledFrom Location Id. A Lookup field is a type of custom field that creates a relationship between two objects, but does not support rollup summary fields. A Many-to-One relationship means that many child records can be related to one parent record, but not vice versa. In this case, a FulfillmentOrder has a Lookup field named FulfilledFrom Location Id that references a Location record. A Location is a record that represents a physical location from which order product items are fulfilled, such as warehouses and retail stores. A Location can have many FulfillmentOrders associated with it, but a FulfillmentOrder can only have one Location. Verified

Reference: https://help.salesforce.com/s/articleView?id=sf.custom_field_types.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_location.htm&type=5

The type of relationship that exists between FulfillmentOrder and Order Delivery Method is Lookup (Order Delivery Method). A Lookup field is a type of custom field that creates a relationship between two objects, but does not support rollup summary fields. In this case, a FulfillmentOrder has a Lookup field named Order Delivery Method that references an Order Delivery Method record. An Order Delivery Method is a record that represents a delivery option for fulfilling orders, such as standard shipping, express shipping, in-store pickup, etc. An Order Delivery Method can have many FulfillmentOrders associated with it, but a FulfillmentOrder can only have one Order Delivery Method. Verified

Reference: https://help.salesforce.com/s/articleView?id=sf.custom_field_types.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_order_delivery_method.htm&type=5

The correct statement about Person Accounts and Contacts is that Person Accounts are appropriate for B2C transactions while Account-Contact model is appropriate for B2B transactions. A Person Account is a type of account that represents an individual consumer, rather than a business or organization. A Person Account combines the features and fields of both the Account and Contact objects, and it does not require a Contact record to be associated with it. A Person Account is suitable for B2C transactions, where the customers are individual consumers who purchase products or services for personal use. An Account-Contact model is a type of data model that represents a business or organization as an account, and its employees or affiliates as contacts. An account can have many contacts associated with it, but a contact can only belong to one account. An Account-Contact model is suitable for B2B transactions, where the customers are businesses or organizations that purchase products or services for professional use. Verified

Reference: https://help.salesforce.com/s/articleView?id=sf.accounts_person.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.accounts_contacts.htm&type=5

The best way for a user to view the information exchanged between the payment platform and the external payment gateways is to navigate to Payment Gateway Logs related list on the corresponding Order Payment Summary. A Payment Gateway Log is a record that captures the request and response messages between the payment platform and the external payment gateways, such as Stripe, PayPal, etc. A Payment Gateway Log has a lookup relationship to the Order Payment Summary object, which represents a payment made for an order or part of an order. A user can use the Payment Gateway Logs related list on the Order Payment Summary page to view the details of the payment transactions, such as the request and response payloads, status codes, timestamps, etc. Verified

Reference: https://help.salesforce.com/s/articleView?id=sf.order_management_payment_gateway_log.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_order_payment_summary.htm&type=5

Three possible causes of this issue are:

The administrator has duplicate Product SKUs in the JSON query. A Product SKU is a unique identifier for a product that is used to track inventory and sales. A Product SKU must be unique within an org, and it cannot be duplicated in a composite API call. If the administrator has duplicate Product SKUs in the JSON query, it will cause an error when loading test orders via the Workbench.

The number of subrequests in the JSON query exceeds the 20 subrequest limit. A subrequest is a single HTTP request that is part of a composite API call. A composite API call can contain up to 20 subrequests in a single JSON body. If the administrator has more than 20 subrequests in the JSON query, it will cause an error when loading test orders via the Workbench.

Record IDs used within the request are incorrect. A record ID is a unique identifier for a record that is used to reference and manipulate data in Salesforce. A record ID must be valid and exist in the org, and it must match the data type and format of the corresponding field. If the administrator has incorrect record IDs in the JSON query, such as using 15-character IDs instead of 18-character IDs, or using IDs from a different org, it will cause an error when loading test orders via the Workbench.

Verified

Reference: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_composite.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_composite_sobject_tree_flat.htm

The best way for an administrator to synchronize licenses from the production org when preparing a sandbox for development is to run the Match Production Licenses to Sandbox without a Refresh tool in Setup. This tool allows administrators to match their sandbox licenses with their production licenses without refreshing their sandbox. This way, the administrator can ensure that the sandbox has the same number and type of licenses as the production org, and avoid any license-related issues when developing or testing in the sandbox. Verified

Reference: https://help.salesforce.com/s/articleView?id=sf.data_sandbox_licenses.htm&type=5

Two ways that Order Management licenses can be assigned are:

By Permission Set. A Permission Set is a collection of settings and permissions that give users access to various tools and functions in Salesforce. A Permission Set can be assigned to individual users or groups of users, regardless of their profile or role. An administrator can create a Permission Set that includes the Order Management User permission, which enables users to access Order Management features and data. The administrator can then assign this Permission Set to the users who need Order Management licenses.

By User. A User is a record that represents a person who can log in and access Salesforce. A User has various fields and settings that determine their access and permissions in Salesforce, such as profile, role, license type, etc. An administrator can assign an Order Management license to a user by editing the user record and selecting Order Management User from the License Type picklist. The administrator can also enable the Order Management User permission on the user record.

Verified

Reference: https://help.salesforce.com/s/articleView?id=sf.order_management_user_permission.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.users_understanding_license_types.htm&type=5