An Adobe Commerce Architect is creating a new GraphQL API mutation to alter the process of adding configurable products to the cart. The mutation accepts configurable product ID. If the given product has only one variant, then the mutation should add this variant to the cart and return not nullable cart type. If the configurable product has more variants, then the mutation should return not nullable conf igurableProduct type.
The mutation declaration looks as follows:
How should the Adobe Commerce Architect declare output of this mutation?
A merchant is using a unified website that supports native Adobe Commerce B2B and B2C with a single store view.
The merchant wants to show the B2B account features like negotiable quotes and credit limits in the header of the site on every page for the logged-in users who are part of a B2B company account.
Each B2B company has its own individual shared catalog and customer group, and many customer groups for non B2B customers change. The merchant requests that this should not be tied to customer groups.
Which two solutions should the Architect recommend considering public data and caching? (Choose two.)
Since the last production deployment, customers can not complete checkout. The error logs show the following message multiple times:
The Architect finds a deployed feature that should limit delivery for some specific postcodes.
The Architect sees the following code deployed in/webapi_rest \di .xml and etc\frontend\di xml
Which step should the Architect perform to solve the issue?
An Adobe Commerce Architect needs to set up two websites on a single Adobe Commerce instance with base URLs: example.com and website2.example.com.
How should the Architect configure this project so that both websites can use the same customer base?