Deal of The Day! 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 US
Mob_nav_barsMENU

Adobe AD0-E722 Exam - Topic 7 Question 50 Discussion

Actual exam question for Adobe's AD0-E722 exam
Question #: 50
Topic #: 7
[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? (Select two.)

Show Suggested Answer Hide Answer
Suggested Answer: C, A

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 Lauran at Jan 27, 2026, 05:38 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Herman
16 days ago
Load balancing could also be a game changer here!
upvoted 0 times
...
Delmy
21 days ago
Really? I doubt just those two will fix the issue.
upvoted 0 times
...
Novella
26 days ago
What about caching strategies? They could help too.
upvoted 0 times
...
Candra
1 month ago
Totally agree, those are key factors!
upvoted 0 times
...
Ayesha
1 month ago
Increase the server capacity and optimize database queries.
upvoted 0 times
...
Lili
1 month ago
I'd suggest a good old-fashioned ritual sacrifice to the server gods.
upvoted 0 times
...
Royal
2 months ago
Haha, just throw more servers at the problem! That'll fix it.
upvoted 0 times
...
Alexis
2 months ago
Definitely cache the checkout page and use a content delivery network.
upvoted 0 times
...
Lashawn
2 months ago
Optimize the database queries and implement load balancing.
upvoted 0 times
...
Elenora
2 months ago
Increase the number of concurrent connections and enable server-side caching.
upvoted 0 times
...
Ira
2 months ago
I think we discussed reducing the number of API calls during checkout as a way to improve performance. That might be one of the settings we need to consider.
upvoted 0 times
...
Brynn
2 months ago
I feel like load balancing might be relevant here too, but I can't recall if it was specifically mentioned in our study materials.
upvoted 0 times
...
Arlene
3 months ago
I remember a practice question about caching strategies that helped improve performance during high traffic. Maybe implementing a cache could be one of the settings?
upvoted 0 times
...
Jacqueline
3 months ago
I think one setting could be to optimize the database connections, but I'm not entirely sure how that would directly impact checkout speed.
upvoted 0 times
...
James
4 months ago
I've got a strategy for this. I'll start by considering the most resource-intensive parts of the checkout process and see what settings could be optimized there.
upvoted 0 times
...
Lashon
4 months ago
I've seen questions like this before. I think the key is to focus on the most critical areas that could be bottlenecks during high traffic, like the database and server configurations.
upvoted 0 times
...
Broderick
4 months ago
I'm a bit confused on this one. What kind of website settings would affect checkout performance specifically? I'll have to review my notes.
upvoted 0 times
...
Daisy
4 months ago
Okay, let me see. I'm guessing we'll need to look at things like caching, load balancing, or maybe even database optimization.
upvoted 0 times
...
Avery
4 months ago
Hmm, this seems like a tricky one. I'll need to think through the different website settings that could impact checkout performance.
upvoted 0 times
...

Save Cancel