AD0-E722 Adobe Commerce Architect Master Questions and Answers

According to the Adobe Commerce documentation, to create a new xml configuration file, the Architect needs to create a Data class and a Reader class for the custom module. The Data class is responsible for storing and retrieving the configuration data from the cache or the Reader class. The Data class should implement the “\Magento\Framework\Config\Data” interface or extend the “\Magento\Framework\Config\Data” class. The Reader class is responsible for reading and validating the xml configuration files from the file system. The Reader class should implement the '\Magento\Framework\Config\Reader\Filesystem" interface or extend the '\Magento\Framework\Config\Reader\Filesystem" class. The Architect also needs to declare the Data class and the Reader class in the di.xml file of the custom module, and specify the name of the xml configuration file, the converter class, and the schema locator class for the Reader class.

References:

• Configuration types | Adobe Commerce - Experience League
• Create configuration types | Adobe Commerce - Experience League

To display additional content on the home page based on a custom customer attribute, the Architect needs to do the following steps:

• Add a new context value of “my_attribute” to Magento\Framework\App\Http\Context. This will allow the Full Page Cache to generate different versions of the page for customers with different values of “my.attribute”. The context value can be set using a plugin on the Magento\Customer\Model\Context class.
• Add a dynamic block with the content to the Home Page. A dynamic block is a type of content block that can be configured to display only to specific customer segments or conditions. The Architect can use the ‘my.attribute’ in the conditions of the dynamic block and assign it to the Home Page in the Content > Blocks section of the Admin Panel. References:
• Private content | Magento 2 Developer Documentation
• Dynamic Blocks | Adobe Commerce 2.3 User Guide - Magento

This action is necessary to make the attribute available for content staging and preview. According to the Adobe Commerce documentation, the catalogstaging_category_update_form.xml file defines the fields that are displayed in the Scheduled Changes section of the category form. The file extends the category_form.xml file and adds additional fields that are specific to content staging, such as start and end dates, campaign name, description, etc. To include a custom category attribute in the Scheduled Changes section, the attribute must also be declared in the catalogstaging_category_update_form.xml file with the same configuration as in the category_form.xml file.

References:

• Content staging | Adobe Commerce Developer Guide
• Create a category attribute | Adobe Commerce Developer Guide

According to the Adobe Commerce documentation, the correct approach to change the stopwords directory inside a custom module is to use dependency injection to override the default values of the stopwordsDirectory and stopwordsModule parameters of the \Magento\Elasticsearch\SearchAdapter\Query\Preprocessor\Stopwords class. The stopwordsDirectory parameter specifies the relative path of the stopwords directory from the module directory, while the stopwordsModule parameter specifies the name of the module that contains the stopwords directory. By adding these parameters to the di.xml file of the custom module, the Architect can change the location of the stopwords files without modifying the core code or database.

References:

• To change the directory from your module
• Configure Elasticsearch stopwords

• Option C is correct because it configures the preload.keys correctly for Redis L2 caching on an Adobe Commerce on-premise instance. Redis L2 caching is a feature that allows storing the cache data in both Redis and the local file system. This way, the cache data can be loaded faster from the local storage, while Redis acts as a cache invalidation service. To use Redis L2 caching, the backend option for both frontend => page_cache and frontend => default must be set to Magento\Framework\Cache\Backend\RemoteSynchronizedCache1. To enable the preload feature, which reduces the number of requests to Redis, the preload.keys option must be specified with the cache keys that are loaded on each frontend request. However, unlike Redis L1 caching, the preload.keys must include the suffix :hash to indicate that only the hash values of the cache data are stored in Redis2. Therefore, the correct configuration for preload.keys is:

[ ‘762_EAV_ENTITY_TYPES:hash’, ‘762_GLOBAL_PLUGIN_LIST:hash’, ‘762_DB_IS_UP_TO_DATE:hash’, ‘762_SYSTEM_DEFAULT:hash’, ],

• Option A is incorrect because it configures the preload.keys incorrectly for Redis L2 caching. It uses the id_prefix of frontend => page_cache (063_) instead of frontend => default (762_) for the cache keys. This will cause a mismatch between the cache keys and the cache data, and result in incorrect or missing cache data. Moreover, it does not include the suffix :hash for the preload.keys, which is required for Redis L2 caching2.
• Option B is incorrect because it configures the preload.keys incorrectly for Redis L2 caching. It does not include the suffix :hash for the preload.keys, which is required for Redis L2 caching2. It also uses a wrong cache key (GLOBAL_PLUGIN_LIST) instead of GLOBAL_PLUGIN_LIST.
• Option D is incorrect because it configures the preload.keys incorrectly for Redis L2 caching. It uses a wrong id_prefix (162_) instead of frontend => default (762_) for the cache keys. This will cause a mismatch between the cache keys and the cache data, and result in incorrect or missing cache data. It also uses a wrong cache key (EAV_ENTITY_TYPES) instead of EAV_ENTITY_TYPES.

References:

• 1: Two-level caching | Adobe Commerce Developer Guide
• 2: Use Redis for default cache | Adobe Commerce Developer Guide

This solution ensures that the new plugin will execute after all the existing plugins for the ServiceClass::getData method, and will be able to log the final result of the method execution. The afterGetData method of the new plugin will receive the result of the method as a parameter, and can use any logging mechanism to record it. The sortOrder value of the new plugin should be higher than the highest declared plugin sortOrder, so that it will run last in the sequence of plugins. The after type of plugin is preferred over the around type of plugin, because it is simpler and more efficient, and does not require calling the proceed() method.

References:

• Plugins (Interceptors) | Adobe Commerce Developer Guide
• Plugin best practices | Adobe Commerce Developer Guide

The issue here is that the product price changes are not reflected on the storefront, even though the indexes are set to update by schedule and there are no items in the backlog. This indicates that there might be some problem with the changelog and indexing process, which are responsible for tracking and applying the data changes to the index tables. Therefore, the Architect should recommend the developer to check if any custom or third-party modules interfere with the changelog and indexing process, and disable or fix them if needed. Additionally, the Architect should recommend the developer to verify that the version_id for the price indexer in the mview_state table is consistent with the last entry for the same column in the changelog table, and re-synchronize them if they are out of sync. This will ensure that the indexer can process all the data changes correctly and update the index tables accordingly. References: https://experienceleague.adobe.com/docs/commerce- admin/systems/tools/index-management.html?lang=en#cron-groups-and-processes1 https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#m2devgde-mview 2

Using an iframe system for payment integration can help reduce the PCI scope and compliance burden for the merchant, as the payment data is collected and processed by the payment service provider (PSP) within the iframe, without touching the merchant’s website or server. This way, the merchant can leverage the PSP’s PCI certification and avoid storing or transmitting any sensitive cardholder data on their own system. The iframe also provides a secure barrier between the host webpage and the loaded page, preventing any access or manipulation of the payment data by malicious actors. To implement this approach, the merchant needs to embed the PSP’s payment form in their checkout page using an iframe element, and configure the communication between the iframe and the host page using JavaScript123.

The issue here is that the database storage is not being fully cleaned after the test is run. The solution is to modify the method PHPDoc and change the annotation @magentoDbIsolation to enabled. This will ensure that the database storage is fully cleaned after the test is run. References: https://developer.adobe.com/commerce/testing/guide/integration/#database-isolation 1

• Option C is correct because the developer did not check for an active content staging campaign and emulate the campaign state when retrieving product data. Content staging campaigns can modify the product data such as price, name, description, and so on, based on a schedule. To get the correct product data for a specific date and time, the developer needs to use the Magento\Staging\Model\VersionManager class to set the current version ID and emulate the campaign state1. Otherwise, the product data will be retrieved from the default store view without applying the campaign changes.
• Option A is incorrect because retrieving product data directly from the database using the entity_id column is not necessarily wrong. It may not be the best practice, but it does not cause the feed output to be incorrect for products in the content staging campaign. The content staging campaigns are stored in separate tables with a version ID that links to the main product table2. The developer can still join these tables and query the product data based on the version ID and date.
• Option B is incorrect because there is no such method as getContentStagingValue in Magento 2. The developer cannot use this method to retrieve the active campaign value of the product data. The correct way to get the product data for a specific campaign is to use the Magento\Staging\Model\VersionManager class as mentioned above.

References:

• 1: Content Staging | Adobe Commerce Developer Guide
• 2: Content Staging | Adobe Commerce Developer Guide

This solution ensures that the data returned by the GraphQL queries is up to date, while also maintaining performance. By specifying a $cache(cacheidentity: Path\To\identityclass) directive for each GraphQL query, the relevant brands and associated products will be added as cache tags.