Why is the use of a standard Visualforce control such as apex:form discouraged in Salesforce B2B Commerce page includes and subscriber pages?

• A.Apex:form render DOM components slowly
• B.Visualforce "scopes" controls that are present on a page and scope of the control will be set to "ccrz"
• C.Javascript events are not supported within an apex:form control
• D.The CCRZ Javascript object is not accessible within an apex:form control.

Comment: *

Name: *

Email: *

Verification: *

Witch static method invocation is used to initialize ccrz.cc_CallContext with information from ccrz.cc_RemoteActionContext and return an instance of ccrz.cc_RemoteActionResult in an apex
@RemoteAction methos?

• A.ccrz.cc_CallContext.initCallContext(ccrz.cc_RemoteActionContext)
• B.ccrz.cc_CallContext.init(ccrz.cc_RemoteActionContext)
• C.ccrz.cc_CallContext.initializeCallContext(ccrz.cc_RemoteActionContext)
• D.ccrz.cc_CallContext.initRemoteActionContext(ccrz.cc_RemoteActionContext)

Comment: *

Name: *

Email: *

Verification: *

What is a valid way of referencing the CC Cart Object whose API name is E_Cart__c in a SOQL query?

• A.c.E_Cart__c
• B._Cart__c
• C.ccrz__E_Cart__c
• D.cloudcraze__E_Cart__c

Comment: *

Name: *

Email: *

Verification: *

How do the REST APIs in Salesforce B2B Commerce support pass-through parameter handling

• A.An exception is generated for unknown API keys
• B.Parameters are separated, but unused
• C.Parameters are passed through the service handlers
• D.Parameters are filtered out before the request is processed

Comment: *

Name: *

Email: *

Verification: *

What is default behavior for how the Salesforce B2B Commerce Global APIs transform Salesforce data?

• A.Fields names are returned using the Salesforce naming convention.
• B.Fields names are returned with "c." prepended in their name.
• C.Fields names are returned with a lowercase first letter, camelcase convention
• D.Fields names can be mapped to any naming convention desired

Comment: *

Name: *

Email: *

Verification: *