Free 1z0-1068-22 – Oracle CX Commerce 2022 Implementation Essentials Practice Test Question

Select all that apply, then click Submit answer.

• ○

  Add order approval functionality into the B2B Checkout Layout

• ○

  Specify a Price Hold Period for an approved order

• ○

  Set the frequency of the Order Cancellation service

• ○

  Ensure that an invoice payment type is configured in the Payment Methods widget instance

• ○

  Configure B2B Storefront administrative privileges for account shoppers to request an order approval

Select all that apply, then click Submit answer.

• ○

  The generic option will appear as a checkbox in the Administration UI

• ○

  The default value is set to generic, which means that option will be selected in the Administration UI

• ○

  Other paymentMethodTypes options defined in the gateway.json file will appear in the Administration UI,
  even though not explicitly defined in config.json

• ○

  The property is public by default and can be used in a custom widget

Select all that apply, then click Submit answer.

• ○

  to expose parameters that may vary between widget instances

• ○

  to provide an increased level of merchandiser control over widget behavior and display

• ○

  to determine whether a widget can be placed on a layout

• ○

  to provide links to 3rd party JavaScript libraries

Select all that apply, then click Submit answer.

• ○

  Merchants can leverage the provided payment webhooks or create their own custom webhooks

• ○

  Merchants can change the underlying payment service provider without affecting their integration

• ○

  Merchants can store credit cards on the Commerce Cloud server in its PCI-compliant zone

• ○

  Merchants can apply their own business rules on top of each transaction

Select all that apply, then click Submit answer.

• ○

  Webhooks can be created for your custom integration

• ○

  The Credit Card Payment webhook is used for most credit cards, except 3D Secure cards and stored
  cards

• ○

  The Secure Credit Card Payment webhook is used for 3D Secure cards and stored cards

• ○

  The Generic Payment webhook is used for most payment types

• ○

  Webhooks can be configured in the Administration UI or using REST APIs

• ○

  The Custom Currency Payment webhook is used for loyalty points

Select an option, then click Submit answer.

• ○

  Item #2 will never be displayed

• ○

  if the Product view model is available on the page

• ○

  Item #2 will always be displayed

• ○

  If the shopper has a product in his/her cart

Select an option, then click Submit answer.

• ○

  The imports attribute should contain the value “user” because the cart view model belongs to the user

• ○

  The imports attribute is only valid for global widgets and is not relevant

• ○

  The imports attribute can be empty because the Cart view model is global

• ○

  The imports attribute should contain the value “cart”

Select an option, then click Submit answer.

• ○

  Create a custom widget extension called Loyalty Payment and add it to the checkout layout

• ○

  Create a new checkout layout with custom widgets for payment

• ○

  Nothing. The Payments Method widget already includes loyalty points as a payment option

• ○

  Add the baseline Loyalty Payment widget to the checkout layout on the Design page

Select an option, then click Submit answer.

• ○

  for ensuring the correct layout is displayed

• ○

  for ensuring a link does not cause a full page reload

• ○

  for ensuring that your URL is correctly formatted

• ○

  for ensuring images are sized for the current viewport

Select an option, then click Submit answer.

• ○

  Deselect Auto Redirect and click the Build URL Slugs button for the collection page

• ○

  Deselect Auto Redirect and click the Build URL Slugs button for the product page

• ○

  Select Auto Redirect and click the Build URL Slugs button for the product page

• ○

  Select Auto Redirect for collections, deselect it for products, and click the Build URL Slugs buttons