What should the Architect do to resolve this issue and maintain the business requirement?

An ecommerce site has dynamic shipping cost calculation. it allows the customers to see their potential shipping costs on the Product Detail Page before adding an item to the cart.

For this feature, shipping touts are calculated using the following logic:

• Set the shipping method on the Basket

• Add the item to the basket, calculate the basket total and get the shipping cost for this method

• Remove the item from the Basket to restore the original state

• The above process is repeated for each shipping method

During the testing it was discovered that the above code violates the spi.basket.addResolveInSameResquest quota.

What should the Architect do to resolve this issue and maintain the business requirement?
A . Omit the removal of the Item and speed up the process for the customer by adding the product to the basket for them.
B. Omit the calculation of shipping cost until the customer is ready to check out and has chosen the shipping method they want to
C. Wrap each Individual step of the process its own transaction Instead of using one transaction for all steps.
D. Wrap the adding of product and shipping cost calculation in a transaction which Is then rolled back to restore the original state