Adobe AD0-E722 - Adobe Commerce Architect Master

The issue here is that the site breaks every time the users change interface locale in the Admin Panel. This is because the static content for the different locales is not generated during the deployment process. The solution is to adjust the tools build script and specify required locales during *setup:static-content:deploy’ command. This will ensure that the static content for all the needed locales is generated and deployed to the project servers. References: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/static-content.html?lang=en#deploy-static-view-files 1

To make sure the vcl_hash function of Varnish considers the newly created attribute, the Architect needs to do the following steps:

Create a new class that implements the Magento\GraphQlCache\Model\CacheId\CacheIdFactorProviderInterface interface. This interface defines two methods: getFactorName and getFactorValue. The getFactorName method should return the name of the attribute, in this case, my_attribute. The getFactorValue method should return the value of the attribute for the current customer, which can be obtained from the customer session or customer repository1.

Add this class to the idFactorProviders array of Magento\GraphQlCache\Model\CacheId\CacheIdCalculator through dependency injection. The CacheIdCalculator is responsible for generating a cache ID for each GraphQL request based on the factors provided by the idFactorProviders. By adding the new class to this array, the Architect ensures that the cache ID will include the value of my_attribute1.

The cache ID is then used by Varnish to hash and lookup the cached response for each request. By including my_attribute in the cache ID, the Architect ensures that Varnish will serve different responses based on the attribute value of the customer2. References:

Magento_GraphQlCache module | Magento 2 Developer Documentation

Varnish caching | Adobe Commerce 2.4 User Guide - Magento

Option A is correct because setting the consumers_wait_for_max_messages variable true in the deployment stage is the best way to meet the requirement. This variablecontrols whether the queue consumers should wait for a maximum number of messages to process before terminating. If this variable is set to true, the consumers will not terminate after processing the available messages in the queue, but will wait until they reach the max_messages limit or the cron job timeout. This way, the consumers can keep the TCP connections open and avoid delays in processing messages1.

Option B is incorrect because increasing the multiple_process limit to spawn more processes for each consumer will not solve the issue of queue consumers closing TCP connections too often. The multiple_process limit determines how many parallel processes can be run for each consumer. Increasing this limit may improve the throughput of message processing, but it will also consume more server resources and may cause conflicts or errors. Moreover, it will not prevent the consumers from terminating after processing the available messages in the queue2.

Option C is incorrect because changing the max_messages from 10,000 to 1,000 for CRON_CONSUMERS_RUNNER variable will worsen the issue of queue consumers closing TCP connections too often. The max_messages variable defines how many messages each consumer should process before terminating. Decreasing this variable will make the consumers terminate more frequently, which will result in more TCP connections being closed and reopened. This will increase the delays in processing messages3.

References:

1: Configure message queues | Adobe Commerce Developer Guide

2: Configure message queues | Adobe Commerce Developer Guide

3: Configure message queues | Adobe Commerce Developer Guide

These two options are both valid ways to manage routing for the bespoke news section and adhere to best practice. Option B leverages the existing URL rewrite functionality of Adobe Commerce, which allows creating custom URLs for any entity type and storing them in the database. This option requires creating a standard controller route for the news entity type, such as news/article/view/id/i, where i is the news article ID. Then, on saving each news article, a rewrite rule is generated that maps the internal URL to the desired SEO-friendly URL, such as news/{date}/{article_url_key}. The rewrite rule is stored in the url_rewrite table, which is used by the standard router to match and redirect requests.

Option C involves creating a custom router class that implements \Magento\Framework\App\RouterInterface and runs before the standard router in the routing process. The custom router class can match the news portion of the URL and extract the date and URL key parts from it. Then, it can look for and load a news articlethat matches those values using a model or repository class. If a match is found, it can set the request parameters accordingly and dispatch the request to a controller action that renders the news article page.

References:

Routing | Adobe Commerce Developer Guide

URL Rewrites | Adobe Commerce Developer Guide

Custom Router | Adobe Commerce Developer Guide