AD0-E718 Adobe Commerce Architect Master Questions and Answers

Option A is correct because it will migrate data from one table to another based on the attribute id, which is required when changing the attribute type14. Option D is correct because it will create a data patch that will update ‘my.attribute’ type from “text” to “int”, which is a recommended way of changing the attribute type programmatically4.

To change the type of “my.attribute” from text to int, the Architect should take two steps: A) Migrate data from table “catalog_product_entity_text” to “catalog_product_entity_int” for the attribute_id. This step will move the existing values of the attribute from the text table to the int table, which corresponds to the new type. D) Create a Data Patch and update ‘my.attribute’ type from “text” to “int”. This step will update the attribute metadata in the database and reflect the new type. Option B is incorrect because the Admin panel does not allow changing the type of an existing attribute. Option C is incorrect because writing a plugin for \Magento\Eav\Model\Entity\Attribute\Backend\AbstractBackend::afterLoad() will not change the type of the attribute, but only load data from a different table. Option E is incorrect because running the command bin/magento indexer:reset catalog_product_attribute will not change the type of the attribute, but only reset the indexer status. References: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/attributes.html

To meet the requirements, the Architect should use the following solution: • Create Fixed Bundle Product for gathering simple products. This will allow the purchase of a pre-defined set of products with a discount and separate stock and tax class for each product. • Manage price for every selected option. This will allow setting the original and sales price for each product in the bundle. • Add extension attribute original_simple_price for \Magento\Sales\Api\Data\OrderItemExtensionInterface and populate value with price of simple product. This will allow exposing the original price of the simple product via REST API along with other required data. Option B is incorrect because Dynamic Bundle Product will not allow setting a pre-defined set of products with a discount. Option C is incorrect because Grouped Product will not allow setting a discount for the whole set of products. References: https://docs.magento.com/user-guide/catalog/product-create-bundle.html https://devdocs.magento.com/guides/v2.4/extension-dev-guide/extension_attributes/adding-attributes.html

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.

Developer Mode is the mode best suited to achieve the requirements set out by the Adobe Commerce Architect. In Developer Mode, errors are logged and hidden from the user, and the cache mode can only be changed from the command line. Additionally, static files are created dynamically and then cached, which is the desired behavior for this project.

Developer Mode is required to achieve the requirements. This is because developer mode enables the following features: Errors are logged and hidden from the user; cache mode can only be changed from command line; static files are created dynamically and then cached. See Application modes in the Adobe Commerce Help Center1. References: https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/setup/application-modes.html?lang=en 1