Due to a marketing campaign, a website is experiencing a very large number of simultaneously...

Adobe AD0-E722 Question Answer

Due to a marketing campaign, a website is experiencing a very large number of simultaneously placed orders, which is affecting checkout performance. The website is in the production deploy mode.

Which two website settings can an Architect optimize to decrease the impact on checkout performance? (Choose two.)

Asynchronous indexing admin panel Setting (Stores > Settings > Configuration > Advanced> Developer > Grid Settings > Asynchronous indexing) can be enabled by executing the following CLI Command: bin/Magento config:set dev/grid/async_indexing 1

Asynchronous email notifications admin panel setting (stores > settings > configuration > sales > sales Emails > General settings > Asynchronous) can be enabled

A new database can be created and the Split Database feature can be automatically configured with the following command: bin/Magento setup:db-schema:spiit-sales –host"- --dbnanie""" --username""

The website deploy mode can be set to siege by executingthe following CLI command: bin/Magento deploy:mode:set siege, provided that it will be changed back to production as soon as the number of simultaneously placed orders decreases to acceptable levels

Multithreaded checkout processing admin panel setting (stores > settings > configuration > sales > checkout > General settings > Asynchronous) can be set to a higher value representing the number of PHP threads used exclusively for checkout

Explanation:

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 mode1.

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="" --dbname="" --username="" --password="" can be used to configure this feature2.

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 itself3.

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 performance4.

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 thecheckout performance, but it also requires more server resources and may cause other issues5.

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

Adobe AD0-E722 View All Questions