Free Salesforce Order-Management-Administrator Practice Exam with Questions & Answers | Set: 2

Two statements about the Order Summary object that are accurate are:

• It does not exist without the original Order object.An Order Summary is a record that represents the financial summary of an order that is received from an external system, such as B2C Commerce or B2B Commerce. An Order Summary has a master-detail relationship to the Order object, which means that it cannot exist without its parent Order record.
• It is read-only for financial order data. An Order Summary contains financial order data, such as total amount, tax amount, discount amount, etc., that are populated from the external system when the order iscreated. These fields are read-only and cannot be edited in Order Management.

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

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 References: https://help.salesforce.com/s/articl eView?id=sf.order_management_credit_memo.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.compact_layouts_overview.htm &type=5

The Analyze function in the Lightning Record Page editor helps an administrator analyze the performance of a Lightning Record Page. It provides recommendations on how to improve the page load time, such as removing unused components, reducing the number of fields, or using conditional visibility rules.

Two likely causes that could make the second submission of the same JSON payload fail are:

• The payment data must be updated. The payment data in the JSON payload contains information such as the payment method, amount, and authorization code. If the same payment data is used for the second order, it may cause a duplicate payment error or an invalid authorization error.
• The Order Reference Number must be updated. The Order Reference Number is a unique identifier for each order that is generated by the external system and sent in the JSON payload. If the same Order Reference Number is used for the second order, it may cause a duplicate order error or an invalid order error.

Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_order_api.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_payment_api.htm &type=5

Three steps that are required when deploying changes via change sets are:

• Create the change set in the sandbox org. This is the first step where the administrator selects the metadata components that they want todeploy and adds them to a change set in the source org, which is usually a sandbox org.
• Upload the change set to the target org. This is the second step where the administrator sends the change set from the source org to the destination org, which is usually a production org or another sandbox org. The administrator needs to have a deployment connection with the target org and permission to upload change sets.
• Deploy the change set in the target org. This is the final step where the administrator validatesand deploys the change set in the destination org. The administrator needs to have permission to deploy change sets and resolve any deployment errors or warnings.

Verified References: https://help.salesforce.com/s/articleView?id=sf.changesets_create_outbound.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.changesets_deploy.htm &type=5

Two APIs that an admin can suggest so that customers can initiate order cancellations and returns from theB2C Commerce storefront and have their action carry out the cancel and return operations in Order Management are:

• Connect APIs. These are RESTful APIs that expose resources in Order Management, such as orders, payments, shipments, etc. They allow customersto perform CRUD (create, read, update, delete) operations on these resources from external systems, such as B2C Commerce.
• REST APIs. These are HTTP-based APIs that enable developers to access data in Order Management using standard HTTP methods, such as GET, POST, PUT, PATCH, and DELETE. They allow customers to interact with Order Management resources using JSON or XML formats.

Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_connect_api.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_rest_api.htm &type=5

Three steps that the administrator should do to implement this functionality are:

• Create an email template. An email template is a reusable message that contains merge fields that are populatedwith data from records when the email is sent. The administrator can create an email template for the Payment Summary object that includes information such as the payment amount, date, status, etc.
• Create an email alert action. An email alert action is atype of action that sends an email to one or more recipients when a flow executes. The administrator can create an email alert action that uses the email template created in the previous step and sends it to the owner of the associated account when a new Payment Summary is created.
• Create an approval process on the Payment Summary object. An approval process is a way to automate the approval of records based on certain criteria and actions. The administrator can create an approval process on the Payment Summary object that requires an approval after review from a designated approver.

Verified References: https://help.salesforce.com/s/articleView?id=sf.email_templates_create.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_action_email.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_creating_approval_processes.htm &type=5

Three advantages of using Flow Builder vs writing Apex code to manage the main flow of Order data are:

• The admin can attach a debugger to live customersessions. This allows the admin to monitor and troubleshoot the flow execution in real time, without affecting the customer experience or data integrity.
• The admin can easily debug specific business cases visually. This allows the admin to test the flow with different input values and see how the flow behaves in a graphical interface, without writing any code.
• Because it is visual it is also self-documenting as changes are made. This allows the admin to easily understand and maintain the flow logic, as wellas track the changes and versions of the flow.

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

The object that is created and linked to the Order Summary when a customer cancels an order prior to fulfillment is Cancel Order. A Cancel Order is a record that represents a cancellation request for an order or part of an order. A Cancel Order has a lookup relationship to both Order Summary and Change Order objects, and it contains information such as the cancellation reason, status, date, etc. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_cancel_order.htm &type=5

The Ensure Funds process works on only the items passed into the Ensure Funds method. This method is a flow core action that verifies that there are enough funds available for each Order Item passed into it, and updates their payment status accordingly. The administrator can pass any Order Items into this method, regardless of their status or delivery group. Verified References:https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_om_actions_ensure_funds_async.htm &type=5