Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Adobe
  5. AD0-E718

Adobe AD0-E718 Exam
Adobe Commerce Architect Master (Page 5 )

Updated On: 1-Feb-2026
Page 2 of 11
PDF with 50 Questions

A company wants to build an Adobe Commerce website to sell their products to customers in their country. The taxes in their country are highly complex and require customization to Adobe Commerce. An Architect is trying to solve this problem by creating a custom tax calculator that will handle the calculation of taxes for all orders in Adobe Commerce. How should the Architect add the taxes for all orders?

  1. Write a before plugin to \Magento\Quote\Model\QuoteManagement::placeOrder() and add the custom tax to the quote
  2. Declare a new total collector in "etc/sales.xml" in a custom module
  3. Add a new observer to the event 'sales_quote_collect_totals_before" and add the custom tax to the quote

Answer(s): B

Explanation:

you can create tax rules in Magento 2 by going to Stores > Taxes > Tax Rules and choosing or adding tax rates. However, this may not be enough for complex tax scenarios that require customization. https://amasty.com/knowledge-base/how-to-configure-tax-calculation-in-magento-2.html To add a new total to the order, the Architect should declare a new total collector in the "etc/sales.xml" file of a custom module. This file defines the order of calculation and rendering of totals. The Architect should also implement a model class that extends \Magento\Quote\Model\Quote\Address\Total\AbstractTotal and overrides the collect() and fetch() methods to handle the logic of adding the custom tax to the quote and order.


Reference:

https://devdocs.magento.com/guides/v2.4/howdoi/checkout/checkout_new_total.html



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

  1. Asynchronous indexing admin panel Setting (Stores > Settings > Ccr.f iguraticr. > Advanced > developer > Grid Settings > Asynchronous indexing) can be enabled by executing the following CLI command: tm/magento config:set dev/grid/async_ini*xmg 1
  2. Multithreaded checkout processing admin panel setting (stores > s ettmgs > Configuration > Sales > Checkout > General Settings > Asynchronous) can be set to a higher value representing the number of PHP threads used exclusively for checkout
  3. Asynchronous email notifications admin panel Setting (stores > Settings > Configuration > Sales >
    Sales Emails > General Settings > Asynchronous) can be enabled
  4. A new database can be created and the Split Database feature can be automatically configured with the following command: bin/Magento setup:db-schema:split-sales-sales --host=''<checkout db host or ip>" --dbname="<name>" -- username""<checkout db username>'' --password=" <password>"
  5. The website deploy mode can be set to si-g- by executing the 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

Answer(s): A,D

Explanation:

Asynchronous indexing allows Magento to process indexers in the background without affecting the storefront performance. Splitting the database allows Magento to use a separate database for checkout-related tables, which reduces the load on the main database and improves checkout performance.


Reference:

https://devdocs.magento.com/guides/v2.4/extension-dev- guide/indexing.html#asynchronous-indexing https://devdocs.magento.com/guides/v2.4/config- guide/multi-master/multi-master.html

To decrease the impact on checkout performance, the Architect should do two things:
Enable asynchronous indexing admin panel setting. This will allow Magento to update indexes using cron jobs instead of doing it on the fly during checkout. This option can be found under Stores > Settings > Configuration > Advanced > Developer > Grid Settings > Asynchronous indexing. It can also be enabled by executing the following CLI command: bin/magento config:set dev/grid/async_indexing 1
Create a new database and use the Split Database feature. This will allow Magento to separate the sales data from the main database and reduce the load on the database server. This option can be configured with the following command: bin/magento setup:db-schema:split-sales -- host=`<checkout db host or ip>' --dbname=`<name>' --username=`<checkout db username>' -- password=`<password>'


https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#m2devgde- asynchronous-indexing https://devdocs.magento.com/guides/v2.4/config-guide/multi-master/multi-master.html



An Adobe Commerce Architect is reviewing api-functional test code. Some tests send errors to indicate that the customer address does not exist.
The test codes show the following:



Which steps should the Architect take to fix the test errors? A)



B)



C)

  1. Option A
  2. Option B
  3. Option C

Answer(s): B

Explanation:

The test errors are caused by using the wrong customer ID and address ID in the request. The correct customer ID and address ID should be obtained from the response of the previous request to create a customer and an address. The test code should use $this->customer->getId() and $this->address- >getId() instead of hard-coded values.


Reference:

https://devdocs.magento.com/guides/v2.4/get- started/web-api-functional-testing.html



An Adobe Commerce Architect creates a new functionality called Customs Fee, which adds a new total that applies to additional costs for handling customs clearance expenses. The extension allows specifying fee value for every website separately via the Adobe Commerce Configuration System. The Architect plans to cover new functionality with integration tests. One test case needs to confirm if the total is calculated correctly on different websites. How should the Architect make sure that test configuration data is added to test methods according to best practices?

  1. Override setuo () method, receive instance of \Magento\TestFramework\App\config, and specify value via setValue () method
  2. Specify @magentoconfigFixture annotations for the test methods in PHPDoc
  3. Create a fixture file to configure Adobe Commerce and specify it in test method PHPDoc using the @magentoconfigFixture annotation

Answer(s): C

Explanation:

The best practice for adding test configuration data is to use a fixture file that contains the configuration values for different websites. The fixture file can be specified in the test method PHPDoc using the @magentoconfigFixture annotation. This way, the configuration data is isolated from the test code and can be reused for other tests.


Reference:

https://devdocs.magento.com/guides/v2.4/test/integration/annotations/magento-config-

fixture.html



An Architect wants to create an Integration Test that does the following:
· Adds a product using a data fixture
· Executes $this->someLogic->execute($product) on the product · Checks if the result is true.
Sthis->someLogic has the correct object assigned in the setup () method-Product creation and the tested logic must be executed in the context of two different store views with IDs of 3 and 4, which have been created and are available for the test.
How should the Architect meet these requirements?

  1. Create one test class with one test method. Use the \Magento\testFramework\ store\Executionstorecontext class once in the fixture and another time in the test.
  2. Create two test Classes With one test method each. Use the @magentoExecuteInStoreContext 3 and @magentoExecuteInStoreContext 4 annotations on the class level.
  3. Create one test class with two test methods. Use the @magentoStoreContext 3 annotation in one method and @magentoStoreContext 4 in the other one.

Answer(s): C

Explanation:

The @magentoStoreContext annotation allows the test to run in the context of a specific store view. This annotation can be used on the method level to specify different store views for different test methods. This way, the product creation and the tested logic will be executed in the context of the same store view for each test method.


Reference:

https://devdocs.magento.com/guides/v2.4/test/integration/annotations/magento-store- context.html



Viewing page 5 of 11
Viewing questions 21 - 25 out of 50 questions



Post your Comments and Discuss Adobe AD0-E718 exam prep with other Community members:

Join the AD0-E718 Discussion