An Adobe Commerce Architect gets a request to change existing payment gateway functionality by allowing voided transactions only for a certain range of paid amounts. In the vendor module file etc/config.xml, payment method has an option can,_void set to 1.How should this customization be done?
Answer(s): C
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.
https://devdocs.magento.com/guides/v2.4/payments- integrations/base-integration/integration-model.html
An Adobe Commerce Architect needs to customize the workflow of a monthly installments payment extension. The extension is from a partner that is contracted with the default website PSR which has its own legacy extension (a module using deprecated payment method). The installment payment partner manages only initializing a payment, and then hands the capture to be executed by the PSP. Once the amount is successfully captured, the PSP notifies the website through an IPN. The goal of the IPN is only to create an "invoice" and save the 'capture information' to be used later for refund requests through the PSP itself. The Architect needs the most simple solution to capture the requested behavior without side effects.Which solution should the Architect implement?
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.
https://devdocs.magento.com/guides/v2.4/payments-integrations/base- integration/facade-configuration.html
An Architect needs to integrate an Adobe Commerce store with a new Shipping Carrier. Cart data is sent to the Shipping Carrier's API to retrieve the price and display to the customer. After the feature is implemented on the store, the API hits its quota and returns the error "Too many requests". The Shipping Carrier warns the store about sending too many requests with the same content to the API. In the carrier model, what should the Architect change to fix the problem?
Answer(s): A
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.
[1] https://docs.adobe.com/content/help/en/experience-manager- 65/commerce/commerce-payment-shipping-modules/shipping/shipping-carrier- apis.html [2] https://docs.adobe.com/content/help/en/experience-manager- 65/commerce/commerce-payment-shipping-modules/shipping/developing-shipping-carrier- integrations/shipping-carrier-model.html
A representative of a small business needs an Adobe Commerce Architect to design a custom integration of a third-party payment solution. They want to reduce the list of controls identified in their Self-Assessment Questionnaire as much as possible to achieve PCI compliance for their existing Magento application.Which approach meets the business needs?
The Architect should utilize the payment provider iframe system to isolate content of the embedded frame from the parent web page. This approach will reduce the list of controls identified in their Self- Assessment Questionnaire as much as possible to achieve PCI compliance for their existing Magento application. By using an iframe, the payment provider handles all customer-sensitive data and Magento does not store or process any cardholder data. This reduces the PCI scope and simplifies the compliance process. Option B is incorrect because utilizing the Advanced Encryption Standard (AES- 256) algorithm to encrypt all customer-sensitive data from the payment module will not reduce the PCI scope, but rather increase it. Magento will still store and process cardholder data, which requires more controls and validation. Option C is incorrect because utilizing a trusted signed certificate issued by a Certification Authority (CA) to secure each connection made by the payment solution protocol via HTTPS will not reduce the PCI scope, but rather ensure the security of data transmission. Magento will still store and process cardholder data, which requires more controls and validation.
https://devdocs.magento.com/guides/v2.4/payments-integrations/payment- gateway/integration.html
An Architect is working to implement Adobe Commerce into a pre-built ecosystem in a company. Communication between different company domains uses event-driven design and is driven viaAMQP protocol with using RabbitMQ.The Architect needs to establish the data flow between the ERP system and Adobe Commerce. The ERP system stores only customer data excluding customer addresses. The role of Adobe Commerce is to provide Customer Address data to the enterprise ecosystem. Primary Customer data should not be changed from Adobe Commerce side; it should only be updated by messages data from ERP.Which three AMQP configurations should be considered to meet these requirements? (Choose three.)
Answer(s): 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.
11: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/message-queues/config-mq.html
Post your Comments and Discuss Adobe AD0-E718 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AD0-E718 content, but please register or login to continue.