Adobe AD0-E718 Practice Test - Questions Answers, Page 2

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.

Implementing setCachedQuotes () andgetCachedQuotes() in the carrier model can allow the store to store the cart data in a cache, so that repeated requests with the same content can be retrieved from the cache instead of sending a new request to the API. This can reduce the number of requests and avoid hitting the quota limit.

Reference: [1] https://docs.adobe.com/content/help/en/experience-manager-65/commerce/commerce-payment-shipping-modules/shipping/shipping-carrierapis.html [2] https://docs.adobe.com/content/help/en/experience-manager-65/commerce/commerce-payment-shipping-modules/shipping/developing-shipping-carrierintegrations/shipping-carrier-model.html

The best approach to meet the business needs is to utilize a trusted signed certificate issued by a Certification Authority (CA) to secure each connection made by the payment solution protocol via

HTTPS. This will ensure that the data exchanged between the application, the payment provider, andthe customer is all encrypted and secure. Additionally, this approach will help to reduce the list ofcontrols identified in the Self-Assessment Questionnaire, as it is a secure and approved method ofprotecting customer data.

Based on web searches, it seems that Adobe Commerce uses different XML configuration files to define various aspects of message queues, such as consumers, publishers, and topology123.

According to the documentation3, queue_consumer.xml defines the relationship between an existing queue and its consumer, which is a class that processes messages from a queue. queue_publisher.xml defines the exchange where a topic is published, which is a name that identifies a message for routing. queue_topology.xml defines the message routing rules and declares queues and exchanges.

Based on these definitions, I would say that three possible AMQP configurations that should be considered to meet the requirements are:

1. Create a queue_publisher.xml configuration file for Customer Address messages

2. Create a queue_topology.xml configuration file for Customer Address messages

3. Create a queue_consumer.xml and communication.xml configuration files for Customer Address messages

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.

According to the documentation1, token-based authentication is a simple way to access resources using an access token that is generated when an integration is activated. OAuth-based authentication is a more secure way to access resources using a consumer key, consumer secret, access token, and access token secret that are generated when an integration is registered and authorized.

Based on these definitions, I would say that the type of authentication that should be used and implemented in a third-party system for this integration is:

1. Use OAuth-based authentication to provide access to system resources. Integration will be registered by the merchant in the panel an OAuth handshake during activation. The third-party system should follow OAuth protocol to authorize.

According to some tutorials45, creating a custom product type in Adobe Commerce involves several steps, such as:

Creating a product_types.xml file in etc folder to declare the new product type

Creating a custom type model that extends from an abstract product type model

Creating a custom price model that extends from an abstract price model

Creating a layout file for the new product type

Creating a data patch to register the new product type

Based on these steps, I would say that three possible developments that are valid when reviewing the implementation are:

1. Content of the etc/product_types.xml file

2. Custom type model extended from the abstract Product Type model

3. New price model extending \Magento\Catalog\Model\Product\Type\Price

These developments would allow creating a new product type with its own custom pricing logic and attributes.

This is because, in order to change the attribute when scheduling new category updates, the attribute must be added to the view/adminhtml/ulcomponent/catalogstagingcategoryupdateform.xml file in order to be displayed in the additional form when scheduling updates. This additional form is used to set the values for the category attributes when scheduling updates.

https://docs.magento.com/user-guide/v2.3/stores/attributes-customer.htmldisplaying custom customer attributes on cached pages using best practices involves several steps,such as:

Creating a custom block and a phtml template with the content to display Adding the custom block to the layout file of the page where it should appear Creating a section.xml file to declare a new section for the custom attribute Creating a plugin for Magento\Customer\CustomerData\SectionPoolInterface to add the custom attribute value to the section data Using customer-data JS library to retrieve and display the custom attribute value in the phtml template