Most Recent Adobe AD0-E718 Exam Questions & Answers

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

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=''

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

The 'after' plugin is not suitable for modifying the arguments or return value of the original method. The 'around' plugin allows the plugin method to wrap around the original method and modify its behavior and output. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/plugins.html#around-methods

To implement the new code rule, the Architect should create a new class that extends the \PHP_CodeSniffer\Sniffs\Sniff interface and implements the register() and process() methods. The register() method should return an array of tokens that the rule applies to, such as T_STRING for class names. The process() method should contain the logic to check if the class name contains Helper and report an error if so. The Architect should also add a reference to the new class in the ruleset.xml file under the <rule> element with a ref attribute. This will enable PHPCS to use the new rule when checking the code.

The Architect should add a new handler with name can_void to virtualType based on type Magento\Payment\Gateway\Config\ValueHandlerPool in payment method facade configuration. This handler will be responsible for determining whether the payment method can void transactions or not, based on the custom logic of the paid amount range. The handler should implement \Magento\Payment\Gateway\Config\ValueHandlerInterface and override the handle() method to return true or false depending on the payment amount. Option A is incorrect because extending Magento\Payment\Model\Method\Adapter and reimplementing method void will not change the can_void option, but rather the logic of voiding transactions. Option B is incorrect because declaring a new plugin for class Magento\Payment\Gateway\Config\ConfigValueHandler and using the afterHandle method will affect all payment methods that use this class, not just the specific one that needs customization. Reference: https://devdocs.magento.com/guides/v2.4/payments-integrations/base-integration/integration-model.html