AD0-E722 Exam Questions and Answers

QUESTION: 6

A client has multiple warehouses where orders can be fulfilled. The cost of shipping goods from each warehouse varies by day, due to the number of workers available. The Architect needs to make sure that when an order is shipped, it is shipped from the lowest cost warehouse that is open.
How should this functionality be implemented?

Create a new class as a preference for
Magento\inventoryShipping\piugin\Sales\shipment\AssignSourceCodeToShipmentPlugin to set the lowest-cost warehouse on a shipment.
Create a new class implementing
Magento\invtntorysourceSelectionApi\Modei\sourceSelectioninterfacece. which returns open warehouses sorted by cost.
Create an after plugin On
Hagento\InventoryDistanceBasedSourceSelection\Hodel\Algorithms\DistanceBasedAlgorithto sort to Warehouse sources by cost

Answer(s): B

Explanation:

According to the Adobe Commerce documentation, the Source Selection Interface is the main interface for implementing custom source selection algorithms. The interface defines a method called execute(), which takes a list of items to be shipped and a stock ID as parameters, and returns a SourceSelectionResultInterface object, which contains the recommended sources and quantities for each item. The Architect can create a new class that implements this interface and provides the logic for finding the lowest-cost warehouse that is open for each item. The Architect can then register the new class as an option for the source selection algorithm in the di.xml file of the custom module.

Reference:

Source Selection Algorithm | Adobe Commerce Developer Guide Source Selection Interface | Adobe Commerce Developer Guide

Reveal Solution Next Question

QUESTION: 7

A merchant is using a unified website that supports native Adobe Commerce B2B and B2C with a single store view.
The merchant's objective is to display the B2B account features, such as negotiable quotes and credit limits, in the header of the site on every page for logged-in users who belong to a B2B company account.
Each B2B company possesses its unique shared catalog and customer group, while numerous customer groups for non-B2B customers undergo changes. The merchant insists that this association should not be linked to customer groups.
Which two solutions should the Architect recommend for consideration, taking into account public data and caching? (Choose two.)

Create a Virtual Type that switches the theme when a user is part of a B2B company so the output can be modified accordingly in the alternate theme.
Create a new HTTP Context variable to allow for separate public content to be cached for users in B2B companies where the output can be modified accordingly.
Set whether the current user is part of a B2B company in the customer session and use that data directly to modify the output accordingly.
Create a new custom condition for customer segments that allow for choosing whether a user is part of a B2B company and then use this segment to modify the output accordingly.
Check if the current user is part of a B2B company within a block class and modify the output accordingly.

Answer(s): B,D

Explanation:

Option B is a valid solution because creating a new HTTP Context variable can allow for differentiating the public content cache for users who belong to a B2B company account. The HTTP Context variable can be used to modify the output of the header block accordingly, without affecting the performance or scalability of the site1
Option D is also a valid solution because creating a new custom condition for customer segments can enable targeting users who are part of a B2B company account. The customer segment can be used to modify the output of the header block accordingly, using layout updates or dynamic blocks. This solution can also leverage the existing customer segment functionality and avoid custom coding2 Option A is not a valid solution because switching the theme based on a virtual type can cause performance issues and increase the complexity of the site maintenance. Moreover, switching the theme can affect the entire site appearance, not just the header block3 Option C is not a valid solution because using the customer session data directly to modify the output of the header block can prevent the public content cache from working properly. The customer session data is private and cannot be cached, so this solution can negatively impact the performance and scalability of the site4
Option E is not a valid solution because checking if the current user is part of a B2B company within a block class can also prevent the public content cache from working properly. The block class logic is executed on every request, so this solution can negatively impact the performance and scalability of the site5

Reference:

1: https://experienceleague.adobe.com/docs/commerce-cloud-service/user- guide/architecture/starter-architecture.html?lang=en#http-context 2:
https://experienceleague.adobe.com/docs/commerce-cloud-service/user- guide/marketing/customer-segments.html?lang=en 3:
https://experienceleague.adobe.com/docs/commerce-cloud-service/user- guide/design/themes.html?lang=en 4: https://experienceleague.adobe.com/docs/commerce-cloud- service/user-guide/architecture/starter-architecture.html?lang=en#private-content 5:
https://experienceleague.adobe.com/docs/commerce-cloud-service/user-

guide/architecture/starter-architecture.html?lang=en#public-content

Reveal Solution Next Question

QUESTION: 8

An Adobe Commerce Architect needs to customize the workflow of a monthly installments payment extension. The extension is from a partner who is contracted with the default website Payment Service Provider (PSP), 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 a webhook. The goal of the webhook 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.
Which solution should the Architect implement?

Add a plugin before the $invoice->capture() and change Its input to prevent the call of the $Payment->capture()
Change the can_capture attribute for the payment method under config.xml to be <can_capture>0</can_capture>
Declare a capture Command with type Magento\Payment\Gateway\Command\NullCommand for the payment method CommandPool in di.xml

Answer(s): C

Explanation:

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 <can_capture>0</can_capture> 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

Reference:

1: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/payments- integrations/payment-gateway/gateway-command.html?lang=en 2:
https://github.com/magento/magento2/blob/2.4-
develop/app/code/Magento/Payment/Gateway/Command/NullCommand.php 3:
https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/customization/best- practices.html?lang=en#do-not-modify-core-code 4:
https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/payments- integrations/payment-gateway/payment-gateway-configuration.html?lang=en#payment-method-

configuration

Reveal Solution Next Question

QUESTION: 9

An existing Adobe Commerce website is moving to a headless implementation. The existing website features an "All Brands'' page, as well as individual pages for each brand. All brand-related pages are cached in Varnish using tags in the same manner as products and categories. Two new GraphQL queries have been created to make this information available to the frontend for the new headless implementation:

During testing, the queries sometimes return out-of-date information. How should this problem be solved while maintaining performance?

Specify a @cacgecacheable(cacheable: false) directive for each GraphQL query, making sure that the data returned is not cached, and is up to date
Specify a $cache(cacheidentity: Path\\To\\identityclass) directive for each GraphQL query, corresponding to a class that adds cache tags for relevant brands and associated products
Each GraphQL query's resolver class should inject
\Magento\GraphQlcache\Model\cacheableQuery and call setcachevalidity(true) on it as part of the resolver's resolve function.

Answer(s): B

Explanation:

This solution ensures that the data returned by the GraphQL queries is up to date, while also maintaining performance. By specifying a $cache(cacheidentity: Path\To\identityclass) directive for each GraphQL query, the relevant brands and associated products will be added as cache tags.

Reveal Solution Next Question

QUESTION: 10

An Adobe Commerce Architect is investigating a case where some EAV product attributes are no longer updated.
· The catalog is composed of 20.000 products with 100 attributes each. · The product updates are run by recurring Adobe commerce imports that happen multiple times a day.
· The Architect finds an error in the logs that indicates an integrity constraint while trying to insert row with id 2147483647.
What is causing this error?

Magento framework uses INSERT on DUPLICATE, which leads to reaching the max limit of the increment of the column.
Integrity constraints were dropped after upgrading to the latest version, and the integrity checks were missed.
EAV attribute import uses REPLACE, which leads to reaching the max limit of the increment of the column

Answer(s): C

Explanation:

EAV attribute import uses the REPLACE statement, which deletes and inserts a new row with the same primary key value. This causes the auto-increment column to increase by one for each row, even if the row already exists. If the auto-increment column reaches its maximum value, which is 2147483647 for a signed INT, then any further REPLACE statement will fail with an integrity constraint violation error.

Reference:

EAV and extension attributes | Magento 2 Developer Documentation GitHub - techdivision/import-attribute: This library provides the functionality for the Magento 2 import of EAV attributes
Data integrity in JSON (B) when replacing EAV - Stack Overflow

Reveal Solution Next Question

Adobe AD0-E722 Exam (page: 2) Adobe Commerce Architect Master Updated on: 25-Dec-2025

QUESTION: 6

Explanation:

Reference:

QUESTION: 7

Explanation:

Reference:

QUESTION: 8

Explanation:

Reference:

QUESTION: 9

Explanation:

QUESTION: 10

Explanation:

Reference:

Adobe AD0-E722 Exam (page: 2)
Adobe Commerce Architect Master
Updated on: 25-Dec-2025