AD0-E722 Adobe Commerce Architect Master Questions and Answers

The issue here is that the Approval Rules tab does not appear in the Company section in the Customer Account Menu when the Architect logs in using the Company Administrator account. This is because the Approval Rules feature requires two settings to be enabled: the Purchase Orders feature and the Purchase Order payment method. The solution is to set ‘Enable Purchase Orders’ in the B2B Admin to TRUE and make sure that the ‘Purchase Order’ payment method is active. This will allow the Architect to create and manage Approval Rules for orders.

References : https://experienceleague.adobe.com/docs/commerce-admin/b2b/purchase-orders/account-dashboard-approval-rules.html?lang=en#account-dashboard 1  https://experienceleague.adobe.com/docs/commerce-admin/b2b/purchase-orders/purchase-order-payment-method.html?lang=en#payment-method 2

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

Option A is correct because updating the session host value to a shared Redis instance in the “app/etc/env.php” file will allow the session to be saved properly and prevent users from being redirected to the sign-in page after logging in. Redis is a fast and reliable in-memory data store that can be used for session storage in Magento 2. By using a shared Redis instance, the session data can be accessed by any of the backend web servers behind the load balancer, regardless of which server handled the initial request.  This ensures that the user’s session is maintained and consistent across different servers 1 .

Option B is incorrect because increasing the session size with the command config:set system/security/max_session_size_admin will not solve the issue of session not being saved properly. This command only affects the admin session size limit, not the customer session size limit.  Moreover, this command does not address the root cause of the issue, which is that the session data is not shared among the backend web servers 2 .

Option C is incorrect because utilizing the Remote Storage module to synchronize sessions between the servers is not a viable solution for this issue. The Remote Storage module is a feature of Magento Commerce Cloud that allows storing media files and other static content on a remote storage service such as AWS S3 or Azure Blob Storage.  This module does not support synchronizing sessions between servers, as sessions are dynamic and transient data that need to be stored in a fast and accessible data store such as Redis 3 .

References :

1 : Use Redis for session storage | Adobe Commerce Developer Guide

2 : Security | Adobe Commerce User Guide

3 : Remote storage | Adobe Commerce Developer Guide

The issue is that the export file is not shown in the list of generated files. This is because the export path is not set correctly. The solution is to execute the command config:set export/customr/files_directory /var/releases/{release_nunber} to set the new export path.  This will ensure that the export file is saved in the correct directory and can be accessed from the Admin Panel.  References : https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/staging-production.html?lang=en#deploy-to-staging-and-production 1

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

The magento-vars.php file is used to set the website or store view based on the HTTP host, but it does not affect GraphQL requests. GraphQL requests are handled by a separate controller that does not use the magento-vars.php file. Instead, GraphQL requests use the default store view of the default website, unless a store header or store cookie is provided in the request. The store header or cookie should contain the store code of the desired store view.  For example, to query data from website_two, the request should include a header like  store: store_two  or a cookie like  store=store_two 1 2 .  References :

GraphQL overview | Adobe Commerce 2.4 User Guide - Magento

How to set up multiple websites with Magento 2 - Mageplaza

The product price index can be optimized by using parallel mode and customer group merging. Parallel mode allows the indexer to run multiple threads simultaneously, which can speed up the indexing process. Customer group merging reduces the number of rows in the price index table by merging customer groups that have the same product prices. This can improve the performance of the price index queries and reduce the index size.  References :  Indexing optimization ,  Price index customer group merging

Option A is correct because enabling asynchronous indexing can improve the checkout performance by reducing the database load and avoiding locking issues. Asynchronous indexing allows the indexers to run in the background without affecting the frontend operations.  The command  bin/magento config:set dev/grid/async_indexing 1  can be used to enable this option in the production mode 1 .

Option C is correct because creating a new database and splitting the sales tables can also improve the checkout performance by distributing the database load and avoiding contention. Splitting the database allows the checkout and order management operations to use a separate master database from the rest of the Magento application tables.  The command  bin/magento setup:db-schema:split-sales --host=" < checkout db host or ip > " --dbname=" < name > " --username=" < checkout db username > " --password=" < password > "  can be used to configure this feature 2 .

Option B is incorrect because enabling asynchronous email notifications does not affect the checkout performance directly. Asynchronous email notifications allow the order confirmation emails to be sent in batches by a cron job instead of immediately after placing an order.  This option can reduce the server load and improve the customer experience, but it does not impact the checkout process itself 3 .

Option D is incorrect because there is no such deploy mode as siege in Magento 2. The available deploy modes are default, developer, and production.  Changing the deploy mode can affect the performance, caching, and error handling of the Magento application, but it does not directly affect the checkout performance 4 .

Option E is incorrect because there is no such admin panel setting as multithreaded checkout processing in Magento 2. The number of PHP threads used for checkout is determined by the web server configuration and the PHP-FPM settings, not by the Magento application settings.  Increasing the number of PHP threads may improve the checkout performance, but it also requires more server resources and may cause other issues 5 .

References :

1 : Asynchronous indexing | Adobe Commerce Developer Guide

2 : Split database performance solution | Adobe Commerce Developer Guide

3 : Sales Emails | Adobe Commerce User Guide

4 : Set up Magento modes | Adobe Commerce Developer Guide

5 : PHP-FPM configuration settings | Adobe Commerce Developer Guide

The error is caused by the missing class declaration for the custom condition class. According to the Adobe Commerce documentation, to create a custom customer segment condition, the class must extend the \Magento\CustomerSegment\Model\Condition\AbstractCondition class and implement the \Magento\CustomerSegment\Model\Condition\Combine\Interface interface. The class must also declare its name, label, value type, and attribute code properties. Option B is the only option that correctly declares the class with the required properties and inheritance. Option A and Option C are incorrect because they do not extend the AbstractCondition class or implement the CombineInterface interface, and they do not declare the name, label, value type, or attribute code properties.

References :

Create a customer segment condition | Adobe Commerce Developer Guide

AbstractCondition | Adobe Commerce Developer Guide

Option C is correct because adjusting the ruleset.xml file with the new rule is the simplest and most effective way to implement the new code rule. The ruleset.xml file defines the coding standards that are applied by PHP_CodeSniffer. By extending the Magento 2 Coding Standard and adding a new rule, the Architect can customize the code analysis and enforce the company coding standards.  The new rule can use the Magento2.Namespaces.ForbiddenNamespaces sniff to check for any usage of Helper classes in the code and report them as errors or warnings 1 .

Option A is incorrect because creating a new composer package under the AwesomeAgency\CodingStandard\ namespace is not enough to implement the new code rule. The composer package is just a way to distribute and install the coding standard, but it does not define the rules themselves.  The Architect still needs to create a ruleset.xml file and register it with PHP_CodeSniffer 2 .

Option B is incorrect because creating a new class \AwesomeAgency\CodingStandard\Ruleset\ForbiddenNamespaces and specifying the rule inside the process method is unnecessary and complicated. The Architect does not need to create a new class or a new sniff for this rule, as there is already an existing sniff in the Magento 2 Coding Standard that can be used for this purpose.  The Magento2.Namespaces.ForbiddenNamespaces sniff can be configured with an include-pattern element to specify which namespaces are forbidden 1 .

References :

1 : Magento 2 Coding Standards | Adobe Commerce Developer Guide

2 : How to create a custom coding standard | PHP_CodeSniffer Documentation