Free Adobe AD0-E703 Exam Dumps Questions & Answers

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

In a code review of a merchant's site you have discovered that there are multiple observers for the checkout_submit_all_after event. After closer inspection, you notice one of these observers is relying on the others being executed before it is called.
What risk does this pose, and how can it be mitigated?

• A.  Event observers are fired in alphabetical order of the observer name. There is no risk here.
• B.  There is no risk posed as long as each event observer specifies a correct sortOrder. Nothing needs to be changed.
• C.  Order of listener execution cannot be guaranteed, resulting in a fragile implementation. This code should be re-worked using plugins
• D.  Magento only supports one observer per event. These observers will need to be combined into a single point of customization.

You have been asked to display details from the customer's latest order on the customer's account dashboard (customer/account/). You create a new custom template to show the information.
How do you obtain an order repository so you can fetch an order?

• A.  In your block, add a method with the following:return
  ObjectManager::getInstance()->get(OrderRepositoryInterface::class);
• B.  In your template, add the following:$orderRepository = new OrderRepository();
• C.  In your template, add the
  following:$orderRepository=ObjectManager::getInstance()->get(OrderRepositoryInterface::class);
• D.  Create a view model and specify an OrderRepositoryInterface argument in the _construct method

You are developing a new theme which inherits from the Magento_Luma theme.
How is this accomplished?

• A.  Specify the parent theme in Magento admin > Design > Configuration
• B.  Add Magento/luma to etc/view.xml
• C.  Add Magento/luma to theme.xml
• D.  Run the CLI command bin/magento dev:theme:inherit Magento_Luma

A third-party module uses a layout update that changes the template path for a core block from product/view/addto/compare.phtml of the Magento_Catalog module to custom/view/addto/compare.phtml of your custom module. The merchant has a customized version of this template in their custom theme.
What is a consequence of this setup?

• A.  This setup will throw an IllegalStateException
• B.  If another module is installed which also customizes the same core template, the templates will be rendered sequentially
• C.  If a preference for the core block is set, the template will no longer apply
• D.  If the custom module is removed, the custom template will no longer apply