1z0-1068-22 Sample Questions Answers

display product images

save local data to disk

connect to source control repositories

format date and numbers

publish messages to other websites

The Profile Navigation – Account Shoppers widget instance settings was not configured to include an

option for Account Address Book

By default, the account buyer needs to create an order before the Account Address Book is displayed

The account buyer did not have the correct storefront role to access the Account Address Book

The Contact Login (for Managed Accounts) element is configured on the header widget which only

supports B2C login

shopper profiles

promotions

email templates

catalog data

catalog media content

A displaying products and prices that are specific to the logged in contact’s account

managing account buyers and addresses on the storefront by contacts with account specified storefront

roles

simultaneously logging into multiple accounts in order to compare product items and prices

requiring an order approval based on a specified price threshold associated with the account

sharing a purchase list with a contact from another account

Create a new layout instance by cloning an existing layout instance

Upload a new storefront extension that defines the new layout instance

Determine the type of layout and create a new blank instance

You cannot create a new layout instance since there is a fixed number of layouts that cannot be updated

Type the names for each language directly into the field, using a comma delimited format

Configure three different Profile Navigation – Account Shoppers widget instances, one for each locale

Specify the option names using the Administration UI on the Setting Page

Configure using Text Snippets on Design page after selecting the respective language

Each layout will use different instances of the Secondary Navigation widget, depending if the shopper is

account based or not.

If implemented, delegated administrators can view a list of all previous orders placed from the account

shopper.

Account-based orders are tied to an Account, and the Order History Layout for B2B needsa B2B Order

History widget instance.

You cannot have one layout used for both B2B and B2C shoppers.

You can reference the configuration in the widget JavaScript aswidget.enabled()

The widget configuration setting does not have a default value

You can reference the configuration inthe widget JavaScript assite.enabled()

The value can be either true or false

The widget configuration setting will appear as a dropdown

React

JavaScript

Node.js

HTML 5

CSS/Less

Set product pricing discounts for the Account contract per site

Create, edit, and delete contacts

Specify an order approval threshold value

Approve or reject a registration request fora contact

Approve or reject an order that requires approval

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

A B2B Storefront implementation can include B2B-specific widgets as well as standard widgets that

support both B2B and B2C implementations.

Out-of-the-box B2B-specific storefront layouts and associated components must be used for the accountbased

implementation and cannot be customized.

“Display layout to account shoppers only”must be selected in the layout settings in order to restrict the

layout to account-based shoppers only.

A B2B storefront implementation can only support one site per Account.

At any time, because updates to shared configuration to the default site alter the child sites.

Create the additional sites before configuring anything on the default site.

Configure the Oracle integrations for the default site and then create additional sites.

Configure the default site fully and then add the additional sites.

They cannot do this in the Administration UI. They must use the/ccadmin/v1/sitesendpoint

On the Design page, select the site and create a new theme under that site

Edit the theme’s JavaScript code to limit it to the seasonal site

On the Settings page, navigate to the seasonal site and select the new theme in the Theme property

TheconfigTypeproperty must beset to the value payment

Valid values for theinstancesproperty areagent,preview,test, andstorefront

No additional properties are needed to enable a payment method for scheduled orders

The configuration must include a property with the IDpaymentMethodTypes

Option A

Option B

Option C

Option D

On the Metadata tab, add the German translations in addition to the English metadata

On the Metadata tab, overwrite the English metadata with the German translations

Create a duplicate set of the products and collections in German

Switch to Site B to add the German translations for product and collection names and descriptions

Select German as the content language and enter the Germantranslations for product and collection names and descriptions

Locale strings

REST endpoint specifications

Images

Java code