Adobe Commerce Architect Master AD0-E718 Exam Practice Test

Answer : C, E

Based on web searches, it seems that Magento uses different classes and interfaces to interact with configuration files, such as Data, Reader, and Converter12.

According to the documentation1, Data is a class that provides access to configuration data using a scope. Reader is an interface that reads configuration data from XML files. Converter is an interface that converts XML data into an array representation.

Based on these definitions, I would say that two possible steps that the Architect should make to meet the requirement are:

1. Create a Data class that implements ''\Magento\Framework\Config\Data''

2. Make a Reader class that implements ''\Magento\Framework\Config\Reader\Filesystem''

These steps would allow the custom module to read all the XML configuration files declared in the system, merge them together, and use their values in PHP class.

The Architect should make two steps to meet this requirement: C) Create a Data class that implements ''\Magento\Framework\Config\Data''. This class will be responsible for reading and merging the custom xml configuration files and providing access to their values. The Data class should extend \Magento\Framework\Config\Data and use the constructor to inject the Reader class and the cache type. E) Make a Reader class that implements ''\Magento\Framework\Config\Reader\Filesystem''. This class will be responsible for loading and validating the custom xml configuration files from different modules. The Reader class should extend \Magento\Framework\Config\Reader\Filesystem and use the constructor to specify the file name, schema file, and validation state of the custom xml configuration files. Option A is incorrect because writing a plugin for \Magento\Framework\Config\Data::get() will not define a new xml configuration file, but rather modify the existing one. Option B is incorrect because appending the custom xml file name in ''Magento\Config\Model\Config\Structure\Reader'' in di.xml will not define a new xml configuration file, but rather add it to the system configuration structure. Option D is incorrect because injecting a ''reader'' dependency for ''Magento\Framework\Config\Data'' in di.xml will not define a new xml configuration file, but rather use an existing one. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/build/XSD-XML-validation.html

Answer : A

The best way to fix the code so that it complies with the coding standard rule is to introduce a new class accepting those five scalars and use it in the constructor and the remaining logic of Myservice. This will reduce the number of different classes, interfaces, and scalar types used as parameters in the constructor and other methods to less than 13, which is the limit set by the coding standard. Additionally, any extra code that is not necessary can be removed to reduce the general complexity of the class and improve readability.

The coding standard rule that is violated by the code is the Coupling Between Objects (CBO) metric. This metric measures the number of different classes and interfaces that a class depends on. A high CBO value indicates that the class is tightly coupled with other classes and interfaces, which makes it harder to maintain and test. The recommended CBO value for Adobe Commerce classes is less than 13. To reduce the CBO value of Myservice, the Architect should introduce a new class that encapsulates the five scalar parameters that configure the behavior of Myservice. This way, the constructor of Myservice will only depend on one additional class instead of five scalars, and the CBO value will be reduced by four. Reference: https://devdocs.magento.com/guides/v2.4/coding-standards/code-standard-php.html#coupling-between-objects

Answer : B

This is because, in order to change the attribute when scheduling new category updates, the attribute must be added to the view/adminhtml/ulcomponent/catalogstagingcategoryupdateform.xml file in order to be displayed in the additional form when scheduling updates. This additional form is used to set the values for the category attributes when scheduling updates.

To change the new category attribute when scheduling new category updates, you need to add the attribute to view/adminhtml/ui_component/catalogstaging_category_update_form.xml. This file defines the form fields that appear in the Schedule New Update form for categories.By adding the attribute to this file, you will be able to schedule and review changes to the new mobile image field using the content staging and preview feature in Adobe Commerce. Reference:1

1: https://docs.magento.com/user-guide/v2.3/cms/content-staging-category.html

Answer : A, C

To display customer-specific content on the home page to Customers with ''my.attribute'' greater than 3, you need to use the following steps:

Use customer-data JS library to retrieve ''my.attribute'' value. The customer-data JS library allows you to access the customer data stored in the local storage of the browser. You can use the get() method to get the value of ''my.attribute'' for the current customer.

Add a new context value of ''my.attribute'' to Magento\Framework\App\Http\Context. The HTTP context is a mechanism that allows you to vary the cache of a page based on some parameters. By adding a new context value of ''my.attribute'', you can cache separate versions of the home page for customers with different values of ''my.attribute''.

Add a custom block and a phtml template with the content to the cms_index_index.xml layout. This step will create a block that will display the customer-specific content on the home page. You can use the phtml template to check the value of ''my.attribute'' and render the content accordingly.

: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/cache/page-caching/public-content.html : https://devdocs.magento.com/guides/v2.3/howdoi/checkout/checkout_customize.html

Answer : A, C, F

To create a new product type with its own custom pricing logic, you need to consider the following developments:

Content of the etc/product_types.xml file. This file will define the name, label, modelInstance, and priceModel of the new product type. The modelInstance will specify the custom type model that extends from the abstract Product Type model. The priceModel will specify the new price model that extends \Magento\Catalog\Model\Product\Type\Price.

Custom type model extended from the abstract Product Type model. This model will implement the logic and behavior of the new product type, such as how to prepare product for cart, how to process buy request, how to check product options, etc.

New price model extended \Magento\Catalog\Model\Product\Type\Price. This model will implement the custom pricing logic for the new product type, such as how to calculate final price, tier price, minimal price, etc.

1: https://meetanshi.com/blog/create-custom-product-type-in-magento-2/

Answer : B

When using multiple backend servers behind a load balancer, the session data must be stored in a shared location that is accessible by all servers. Otherwise, the session data will be inconsistent and users may experience issues such as being logged out unexpectedly. Redis is a recommended option for storing session data in a distributed architecture, as it provides fast and reliable access to the data. The session host value in the env.php file must point to the Redis instance that is used for session storage. Reference: https://devdocs.magento.com/guides/v2.4/config-guide/redis/redis-session.html

Answer : C

The @magentoStoreContext annotation allows the test to run in the context of a specific store view. This annotation can be used on the method level to specify different store views for different test methods. This way, the product creation and the tested logic will be executed in the context of the same store view for each test method. Reference: https://devdocs.magento.com/guides/v2.4/test/integration/annotations/magento-store-context.html