AD0-E722 Exam Dumps : Adobe Commerce Architect Master

Option C is the correct solution because declaring a capture command with type Magento\Payment\Gateway\Command\NullCommand for the payment method command pool in di.xml will prevent the default capture logic from being executed. The NullCommand class is a dummy implementation of the CommandInterface that does nothing. This way, the payment capture will be handled by the PSP webhook, and the invoice will be created accordingly12

Option A is not a correct solution because adding a plugin before the $invoice->capture() and changing its input to prevent the call of the $payment->capture() will require modifying the core Magento code, which is not recommended. Moreover, this solution will affect all payment methods that use the invoice capture logic, not just the monthly installments payment extension3

Option B is not a correct solution because changing the can_capture attribute for the payment method under config.xml to be 0 will disable the capture functionality for the payment method entirely. This means that the invoice cannot be created or captured, even by the PSP webhook4

References:

1: 2: 3: 4: guide/payments-integrations/payment-gateway/payment-gateway-configuration.html?lang=en#payment-method-configuration

The issue here is that the Approval Rules tab does not appear in the Company section in the Customer Account Menu when the Architect logs in using the Company Administrator account. This is because the Approval Rules feature requires two settings to be enabled: the Purchase Orders feature and the Purchase Order payment method. The solution is to set ‘Enable Purchase Orders’ in the B2B Admin to TRUE and make sure that the ‘Purchase Order’ payment method is active. This will allow the Architect to create and manage Approval Rules for orders.

References: 1 2

To add a product type with custom pricing, the Architect needs to do the following steps:

• Create a content of the etc/product_types.xml file that defines the new product type, its label, model, index priority, and price model. This file is used to register the new product type and its associated classes in Magento1.
• Create a new price model that extends \Magento\Catalog\Model\Product\Type\Price and implements the custom pricing logic for the new product type. The price model is responsible for calculating the final price of the product based on various factors, such as special price, tier price, catalog price rules, etc2.
• Create a custom type model that extends from the abstract Product Type model (\Magento\Catalog\Model\Product\Type\AbstractType) and overrides the methods related to the product type behavior, such as prepareForCart, getAssociatedProducts, etc. The type model defines how the product type interacts with other components, such as quote, order, cart, etc3. References:
• How to add a new product type in Magento 2? (MageStackDay mystery question 1) - Magento Stack Exchange
• Magento 2: How to create custom product types - BelVG Blog
• Magento 2: How to create custom product types - BelVG Blog