Free Adobe AD0-E704 Exam Dumps Questions & Answers

You are working on a project where many catalog managers often change products in the admin panel.
The merchant is considering changing the indexers mode to "Update on Schedule" from "Update on Save" to achieve better performance. However, the merchant is concerned about data consistency and the probability of the scheduled updates being lost.
How does Magento store the IDs of updated products for reindex in "Update on Schedule" mode?

• A.Magento enables database triggers which collect updated IDs and saves them in special changelog tables.
• B.Magento is gathering updated IDs using catalog_product_save_commit_after events and publishes them into the Message Queue.
• C.Magento sets a reindex_required flag on updated products and a later reindex run by the cron will pick up IDs based on that flag.
• D.Using the Staging update scheduled for every minute, which includes modified products, Magento will automatically reindex affected products when the update is applied.

Magento can load the configuration file di.xml area-specific. During bootstrapping, each application entry point loads the appropriate di.xml files for the requested are
a. Please select the set of correct areas, where this file can be loaded by Magento:

• A.adminhtml, frontend, webapi_rest, webapi_soap, system
• B.backend, frontend, webapi_rest, webapi_soap, system
• C.backend, frontend, webapi_rest, webapi_soap, crontab
• D.adminhtml, frontend, webapi_rest, webapi_soap, crontab

Suppose you are building an inquiry form using uicomponent. It has a feature that customer can edit the submitted data later if he wants to edit. What should the logic here to implement, in order to enable the form for re-edit:

• A.DataProvider class provides getDataSourceData() method which is responsible for data loading.
• B.DataProvider class provides getData() method which is responsible for data loading.
• C.DataProvider class provides execute() method which is responsible for data loading.
• D.DataProvider class provides prepare() method which is responsible for data loading.

Consider below example of etc/di.xml: Magento\Filesystem\Adapter\Local Please select correct statement based on shared="false" attribute in the example:

• A.Magento\Filesystem is not shared, so no clients will retrieve any instances of Magento\Filesystem. Also, no instance of Magento\Filesystem will get any instance of $adapter, because it is non-shared too.
• B.None of these.
• C.Magento\Filesystem is not shared, so all clients will retrieve separate instances of Magento\Filesystem. Also, every instance of Magento\Filesystem will get separate instance of $adapter, because it is non-shared too.
• D.Magento\Filesystem is not shared, so all clients will retrieve same instances of Magento\Filesystem. Also, every instance of Magento\Filesystem will get same instance of $adapter, because it is non-shared too.

You are working on a project which uses Staging for different entities. You are considering the option to stage and rollback different entities independently. What is the scope of a Staging version in Magento?

• A.Global, such that stage and rollback affect the whole database
• B.Group of entities (catalog, customer, cms), which makes only possible to stage and rollback the whole group
• C.Table, which makes it possible to stage and rollback the data from each table separately
• D.Website, such that all entity values for the website are affected with a stage and rollback