Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Adobe Exam AD0-E722 Topic 1 Question 15 Discussion

Actual exam question for Adobe's AD0-E722 exam
Question #: 15
Topic #: 1
[All AD0-E722 Questions]

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

Show Suggested Answer Hide Answer
Suggested Answer: A, C

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 commandbin/magento config:set dev/grid/async_indexing 1can 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 commandbin/magento setup:db-schema:split-sales --host='<checkout db host or ip>' --dbname='<name>' --username='<checkout db 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 the checkout performance, but it also requires more server resources and may cause other issues5.


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

by Desmond at Apr 27, 2024, 07:49 AM

Limited Time Offer

25%

Off

Get Premium AD0-E722 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Verda
6 months ago
Makes sense, but splitting the database could balance the load better. I'm leaning towards A and C with strong rationale.
upvoted 0 times
...
Antonio
6 months ago
I'm thinking option E, multithreaded checkout, could be worth considering too. It would use more PHP threads.
upvoted 0 times
...
Antonio
6 months ago
True, but option C, creating a new database, also seems like a viable solution.
upvoted 0 times
...
Verda
7 months ago
Enabling Asynchronous indexing might help. It’s option A.
upvoted 0 times
...
Antonio
7 months ago
I agree. Looks like we need to reduce the load on the checkout process.
upvoted 0 times
...
Veronika
7 months ago
This question about optimizing website performance during a marketing campaign seems challenging.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77