Prep and try our AD0-E702 valid and latest training questions & answers

A merchant is interested in setting different prices for the same products in different store scopes.
What do you reply to this inquiry?

• A. The price scope can be set to store but this will lead to performance degradation of category pages
• B. The prices can be scoped per store
• C. The prices can only be scoped per website or globally
• D. The prices do not support scopes

You need to find all orders in the processing state. You have written the code:

How do you resolve the exception?

• A. Use dependency injection to load an instance of the SearchCriteria class
• B. Specify a preference in di.xml to map SearchCriteriaBuilder to SearchCriteriaInterface
• C. Change the getList parameter to: $searchCriteraBuilder->addFilter('state','processing')->create()
• D. Clear generated code to get a new version of SearchCriteriaBuilder

How do you obtain customer information in a JavaScript module?

• A. Customer information is available in localStorage and be retrieved by calling window.localStorage.getItem('customer')
• B. Magento does not expose customer information in JavaScript for security reasons
• C. By sending an AJAX request to the url: /customer/account/info/?json=1
• D. By using customerData.get('customer') call, where customerData is an instance of Magento_Customer/js/customer-data

A merchant asks you to extend customer functionality to allow customer accounts to be associated with two or more billing addresses.
How is this implemented?

• A. This is out-of-the box functionality
• B. By changing the System Configuration setting: Customer>Allow multiple billing addresses to Yes
• C. By altering the customer_entity table, adding the field billing_address2, and customizing both My Account and Checkout functionality to use that new field
• D. By adding the attribute like customer_address_billing2 and customizing both My Account and Checkout functionality to use that new attribute

A custom module must make changes to the schema following each setup:upgrade run. This must be done after all other module's schema updates have been applied.
How is this accomplished?

• A. Update the module's setup_priority in etc/modules.xml
• B. Create an UpgradeSchemaAfter class which implements InstallSchemaInterface
• C. Write a plugin intercepting \Magento\Setup\Model\Installer::handleDBSchemaData
• D. Create a Recurring class which implements InstallSchemaInterface