Adobe AD0-E718 Adobe Commerce Architect Master Exam Practice Test

Answer : C, E, F

To troubleshoot this issue, the Architect should check three requirements:

The composer.json file is present and defines the module as a composer package. This is necessary for the module:uninstall command to work properly, as it only applies to modules installed via composer.

The --remove-data option is specified as an argument for the CLI command. This will trigger the uninstallData() method in the Uninstall class and remove any database data related to the module.

The uninstall() method is implemented in the Uninstall class. This will trigger the uninstallSchema() method and remove any database schema related to the module. Alternatively, the uninstallSchema() method can be invoked directly in the Uninstall class.

Answer : A

The preload.keys should be configured as shown in option A. This will allow Redis to preload the cache keys that are loaded on every page request, such as eav_entity_types, GLOBAL_PLUGIN_LIST, DB_IS_UP_TO_DATE , SYSTEM_DEFAULT. The keys should include the database prefix (061_) and the :hash suffix for L2 caching. The :hash suffix tells Redis to load only the hashes from Redis and the data from local storage. This will reduce the pressure on Redis and improve the performance of Magento.

Answer : A, C, E

To establish the data flow between the ERP system and Adobe Commerce using AMQP protocol with RabbitMQ, you need to consider the following AMQP configurations:

Create a queue_consumer.xml and communication.xml configuration files for Customer data messages. These files will define the topics, handlers, and consumers that will receive and process the messages from the ERP system. The communication.xml file will also specify the schema for the Customer data messages.

Create a queue_publisher.xml configuration file for Customer Address messages. This file will define the exchange where the Customer Address messages will be published to. The exchange will route the messages to the appropriate queues based on the binding rules.

Create a queue_topology.xml configuration file for Customer Address messages. This file will define the message routing rules and declare the queues and exchanges for the Customer Address messages. The queue_topology.xml file will also specify the connection name and type for RabbitMQ.

1: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/message-queues/config-mq.html

Answer : C, E

Based on web searches, it seems that Magento uses different classes and interfaces to interact with configuration files, such as Data, Reader, and Converter12.

According to the documentation1, Data is a class that provides access to configuration data using a scope. Reader is an interface that reads configuration data from XML files. Converter is an interface that converts XML data into an array representation.

Based on these definitions, I would say that two possible steps that the Architect should make to meet the requirement are:

1. Create a Data class that implements ''\Magento\Framework\Config\Data''

2. Make a Reader class that implements ''\Magento\Framework\Config\Reader\Filesystem''

These steps would allow the custom module to read all the XML configuration files declared in the system, merge them together, and use their values in PHP class.

The Architect should make two steps to meet this requirement: C) Create a Data class that implements ''\Magento\Framework\Config\Data''. This class will be responsible for reading and merging the custom xml configuration files and providing access to their values. The Data class should extend \Magento\Framework\Config\Data and use the constructor to inject the Reader class and the cache type. E) Make a Reader class that implements ''\Magento\Framework\Config\Reader\Filesystem''. This class will be responsible for loading and validating the custom xml configuration files from different modules. The Reader class should extend \Magento\Framework\Config\Reader\Filesystem and use the constructor to specify the file name, schema file, and validation state of the custom xml configuration files. Option A is incorrect because writing a plugin for \Magento\Framework\Config\Data::get() will not define a new xml configuration file, but rather modify the existing one. Option B is incorrect because appending the custom xml file name in ''Magento\Config\Model\Config\Structure\Reader'' in di.xml will not define a new xml configuration file, but rather add it to the system configuration structure. Option D is incorrect because injecting a ''reader'' dependency for ''Magento\Framework\Config\Data'' in di.xml will not define a new xml configuration file, but rather use an existing one. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/build/XSD-XML-validation.html

Answer : C

The best solution for the Adobe Commerce Architect to implement in order to capture the requested behavior without side effects is to declare a capture command with type Magento\payment\Gateway\Command\NullCommand for the payment method CommandPool in di.xml. This will allow the partner to initialize the payment and then hand the capture over to the PSP, while also preventing the website from calling the $payment->capture() method. It will also allow the PSP to notify the website through an IPN, which will create an 'invoice' and save the 'capture information' to be used later for refund requests through the PSP itself.

The Architect should implement the solution of declaring a capture command with type Magento\Payment\Gateway\Command\NullCommand for the payment method CommandPool in di.xml. This command will do nothing when the capture method is called on the payment method, which is the desired behavior since the capture is handled by the PSP. The NullCommand class implements \Magento\Payment\Gateway\CommandInterface and overrides the execute() method to return null. Option A is incorrect because adding a plugin before the $invoice->capture() method and changing its input will not prevent the call of the $payment->capture() method, but rather change the invoice object that is passed to it. Option B is incorrect because changing the can_capture attribute for the payment method under config.xml to be <can_capture>0</can_capture> will not prevent the capture method from being called, but rather disable the capture option in the Admin panel. Reference: https://devdocs.magento.com/guides/v2.4/payments-integrations/base-integration/facade-configuration.html

Answer : B

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

Answer : A

The best way to fix the code so that it complies with the coding standard rule is to introduce a new class accepting those five scalars and use it in the constructor and the remaining logic of Myservice. This will reduce the number of different classes, interfaces, and scalar types used as parameters in the constructor and other methods to less than 13, which is the limit set by the coding standard. Additionally, any extra code that is not necessary can be removed to reduce the general complexity of the class and improve readability.

The coding standard rule that is violated by the code is the Coupling Between Objects (CBO) metric. This metric measures the number of different classes and interfaces that a class depends on. A high CBO value indicates that the class is tightly coupled with other classes and interfaces, which makes it harder to maintain and test. The recommended CBO value for Adobe Commerce classes is less than 13. To reduce the CBO value of Myservice, the Architect should introduce a new class that encapsulates the five scalar parameters that configure the behavior of Myservice. This way, the constructor of Myservice will only depend on one additional class instead of five scalars, and the CBO value will be reduced by four. Reference: https://devdocs.magento.com/guides/v2.4/coding-standards/code-standard-php.html#coupling-between-objects