An Adobe Commerce Architect is troubleshooting an issue on an Adobe Commerce Cloud project that is not yet live.
The developers migrate the Staging Database to Production in readiness to Go Live. However, when the developers test their Product Import feature, the new products do not appear on the frontend.
The developers suspect the Varnish Cache is not being cleared. Staging seems to work as expected. Production was working before the database migration.
What is the likely cause?
The Fastly credentials in the Production Database are incorrect. This means that the Varnish cache cannot be cleared by Commerce when new products are imported. The Fastly credentials should be updated to match the Production environment.Â See Configure Fastly credentials in the Adobe Commerce Help Center. References: https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/cache/use-varnish-cache.html?lang=en 1Â https://support.magento.com/hc/en-us/articles/360006008192-Configure-Fastly-credentials
An Adobe Commerce Architect is asked by a merchant using B2B features to help with a configuration issue.
The Architect creates a test Company Account and wants to create Approval Rules for orders. 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.
Which two steps must be taken to fix this issue? (Choose two.)
Enabling Purchase Orders at both the B2B Admin and the Company Record levels is necessary for Approval Rules to appear in the Company section of the Customer Account Menu. When 'Enable Purchase Orders' is set to TRUE, the system assumes that the company will be making purchases using purchase orders, and the Approval Rules tab becomes visible.
To create Approval Rules for orders, the Architect needs to enable Purchase Orders both in the B2B Admin and on the Company Record. This will allow the Company Administrator to access the Approval Rules tab in the Customer Account Menu and create rules based on various criteria. The Purchase Order payment method and the B2B Quote feature are not required for this functionality. References: https://docs.magento.com/user-guide/customers/account-dashboard-approval-rules.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. References: https://devdocs.magento.com/guides/v2.4/payments-integrations/payment-gateway/integration.html
A company wants to build an Adobe Commerce website to sell their products to customers in their country. The taxes in their country are highly complex and require customization to Adobe Commerce. An Architect is trying to solve this problem by creating a custom tax calculator that will handle the calculation of taxes for all orders in Adobe Commerce.
How should the Architect add the taxes for all orders?
you can create tax rules in Magento 2 by going to Stores > Taxes > Tax Rules and choosing or adding tax rates. However, this may not be enough for complex tax scenarios that require customization.
To add a new total to the order, the Architect should declare a new total collector in the â€œetc/sales.xmlâ€ file of a custom module. This file defines the order of calculation and rendering of totals. The Architect should also implement a model class that extends \Magento\Quote\Model\Quote\Address\Total\AbstractTotal and overrides the collect() and fetch() methods to handle the logic of adding the custom tax to the quote and order. References: https://devdocs.magento.com/guides/v2.4/howdoi/checkout/checkout_new_total.html