Free Order-Management-Administrator Practice Test Questions and Answers (2026)

Debugging a flow with input data allows the administrator to test the flow with specific values and

see how the flow behaves. The Debug with inputs option is available in the Flow Builder toolbar and

lets the administrator provide input values for each flow variable before running the flow. Verified

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

The administrator can use two tools to debug an issue with an Apex trigger: Log Inspector in the

Developer Console and Debug Logs in Setup. The Log Inspector is a tool that displays a graphical

representation of a debug log, which is a record of database operations, system processes, and errors

that occur when executing a transaction or running unit tests. The Log Inspector helps you analyze

and troubleshoot your code by highlighting errors, checkpoints, and execution times. The Debug Logs

page in Setup lets you monitor and retain debug logs for users, Apex classes, Apex triggers, and

Lightning components. You can view, download, or delete debug logs from this page.

An administrator would enable Person Accounts during Order Management setup for the use case of

connecting Order Management to B2C Commerce. B2C Commerce is a cloud-based platform that

enables businesses to create and manage online storefronts for consumers. B2C Commerce uses

Person Accounts to represent individual shoppers who place orders on the storefronts. Person

Accounts are a type of account that combines account and contact information into a single record.

To connect Order Management to B2C Commerce, an administrator needs to enable Person Accounts

in Order Management and install the B2C Commerce Integration package from AppExchange.

Reference: B2C Commerce Integration, [Person Accounts]

Thank you for your visit.

When a customer applies a discount when placing an order, an order adjustment group summary is

created. An order adjustment group summary is a record that represents a modification to the order

amount, such as a discount, a surcharge, or a tax. An order adjustment group summary can have one

or more order adjustments, which are the individual modifications that are applied to the order or

the order items. An order can have one or more order adjustment group summaries, depending on

how many types of modifications are applied to the order. Reference: Order Management Objects,

[Order Adjustments]

The best place for a service agent to go first to view process exceptions related to a specific Order is

the Order Record - Process Exception Details Tab. This tab shows a list of process exceptions that

occurred during the order lifecycle, such as errors in payment authorization, inventory allocation,

fulfillment location assignment, etc. The service agent can use this tab to identify and resolve the

issues that affect the order processing. Verified Reference:

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

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 Order Delivery Method and Delivery Method objects are used to configure delivery methods for

orders. A delivery method is a way of delivering an order to a customer, such as standard shipping,

express shipping, or in-store pickup. A Delivery Method record defines the name, description, type,

and cost of a delivery method. An Order Delivery Method record associates an order with a delivery

method and stores additional information such as the delivery address, tracking number, and status.

Reference: Order Management Objects, [Delivery Methods]

Two objects that are found within Order Management are:

Fulfillment Order. A Fulfillment Order is a record that represents a group of products in an order that

are fulfilled together from the same location. A Fulfillment Order has a lookup relationship to the

Order Summary object, and it contains information such as the fulfillment location, delivery method,

status, etc.

Payment Summary. A Payment Summary is a record that represents a payment made for an order or

part of an order. A Payment Summary has a lookup relationship to both Order Summary and Invoice

objects, and it contains information such as the payment amount, method, status, etc.

Verified Reference:

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

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

5

Dynamic Actions allow an administrator to add visibility rules for the buttons in the Highlights Panel

on the Lightning Record Page. Dynamic Actions let you configure when and where actions appear on

a record page based on criteria such as record field values, user permissions, or device type.

The best way for the administrator to satisfy this requirement is to edit the Lightning Record Page

and change the Template to Three Regions. A Lightning Record Page is a type of page that displays

details and related information about a specific record in Lightning Experience or Salesforce mobile

app. A Lightning Record Page can be customized using the Lightning App Builder, which is a tool that

allows administrators to drag and drop components onto a page layout. A Template is a predefined

layout that determines how components are arranged on a page. A Three Regions template is a type

of template that divides the page into three columns or regions. The administrator can edit the

Lightning Record Page for the Order Summary object, and change the Template to Three Regions in

the Lightning App Builder. Verified Reference:

https://help.salesforce.com/s/articleView?id=sf.lightning_app_builder_customize_lex_pages.htm&t

ype=5

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

The best way for the administrator to meet this requirement is to create an External Data Source in

Setup that

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

Two ways that an administrator can query Order Summaries using APIs in Workbench are:

Platform API. The Platform API is a set of REST and SOAP APIs that allow developers to access data

and functionality in Salesforce from external systems. The Platform API includes various resources

and operations for querying, creating, updating, or deleting records in Salesforce, such as Order

Summaries. The administrator can use the Platform API in Workbench by selecting the REST Explorer

or SOAP Explorer tabs, and entering the appropriate request URL and parameters.

Composite API. The Composite API is a type of REST API that allows developers to execute multiple

subrequests in a single HTTP request. The Composite API includes various resources and operations

for batching, tree, sObject collections, or transactions in Salesforce, such as Order Summaries. The

administrator can use the Composite API in Workbench by selecting the REST Explorer tab, and

entering the appropriate request URL and JSON body.

Verified Reference: https://developer.salesforce.com/docs/atlas.enus.api_rest.meta/api_rest/intro_what_is_rest_api.htm

https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite.htm

The best way for the administrator to meet this requirement is to modify the compact layout on the

Credit Memo object. A Credit Memo is a record that represents a refund or credit issued to a

customer for an order or part of an order. A Credit Memo has various fields and related lists that

display information such as the credit amount, status, reason, etc. A compact layout is a type of

layout that determines which fields appear in the highlights panel at the top of a record page in

Lightning Experience or Salesforce mobile app. The administrator can use the Object Manager to

modify the compact layout on the Credit Memo object and add the Total Amount field to the

compact layout. This way, the sales team can see the Total Amount field in the highlights panel at the

top of the Credit Memo record page. Verified Reference:

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

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

The feature that supports this use case is the Unmanaged Order Checkbox. This is a standard field on

the Order Summary object that indicates whether the order is managed by Order Management or

not. If this field is checked, then the order is not actioned on by Order Management, and it does not

trigger any flows or processes. The administrator can use this field to import Order Summary records

containing historical data without affecting the order lifecycle. Verified Reference:

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