Free Adobe AD0-E722 Practice Exam with Questions & Answers | Set: 2

• 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

This solution ensures that the new plugin will execute after all the existing plugins for the ServiceClass::getData method, and will be able to log the final result of the method execution. The afterGetData method of the new plugin will receive the result of the method as a parameter, and can use any logging mechanism to record it. The sortOrder value of the new plugin should be higher than the highest declared plugin sortOrder, so that it will run last in the sequence of plugins. The after type of plugin is preferred over the around type of plugin, because it is simpler and more efficient, and does not require calling the proceed() method.

References:

• Plugins (Interceptors) | Adobe Commerce Developer Guide
• Plugin best practices | Adobe Commerce Developer Guide

• Option A is correct because updating the session host value to a shared Redis instance in the “app/etc/env.php” file will allow the session to be saved properly and prevent users from being redirected to the sign-in page after logging in. Redis is a fast and reliable in-memory data store that can be used for session storage in Magento 2. By using a shared Redis instance, the session data can be accessed by any of the backend web servers behind the load balancer, regardless of which server handled the initial request. This ensures that the user’s session is maintained and consistent across different servers1.
• Option B is incorrect because increasing the session size with the command config:set system/security/max_session_size_admin will not solve the issue of session not being saved properly. This command only affects the admin session size limit, not the customer session size limit. Moreover, this command does not address the root causeof the issue, which is that the session data is not shared among the backend web servers2.
• Option C is incorrect because utilizing the Remote Storage module to synchronize sessions between the servers is not a viable solution for this issue. The Remote Storage module is a feature of Magento Commerce Cloud that allows storing media files and other static content on a remote storage service such as AWS S3 or Azure Blob Storage. This module does not support synchronizing sessions between servers, as sessions are dynamic and transient data that need to be stored in a fast and accessible data store such as Redis3.

References:

• 1: Use Redis for session storage | Adobe Commerce Developer Guide
• 2: Security | Adobe Commerce User Guide
• 3: Remote storage | Adobe Commerce Developer Guide